danwinslow

So, this line of argument has been done to death. We all know where we stand. I would want to use this board as an accelerator plugin to enhance the machine, not render it unnecessary. No 100hz, no thousands of of softsprites....just a little faster of a machine but hopefully more compatible than Rapidus.

Yeah, it's not going to be a 100MHZ atari. But, I think maybe with some work we could turn it into something that would allow extra processing capability during vblank or dli's, that could be very useful. Yes, it's got to live with the external bus speeds, and access to RAM will be as slow. Even just a system that doubled the 1.79 speed exactly would be an mprovement. I don't know if it makes sense to think about some kind of faster RAM local to the cpu, kind of like a cpu cache that it could use, off the bus and free to use at a faster rate while still being able to use the regular RAM. There's a lot I don't know, but we've seen some amazing things done and this just seems really promising.

ah. Thanks.

They said it was 6502C compatible...I thought that was what we used? Anyway, I bet you guys could do something cool with this.

http://www.e-basteln.de/computing/65f02/65f02/ Seems like a neat idea.

-lc C lib maybe? https://stackoverflow.com/questions/6240639/where-is-the-standard-c-library-on-mac-os-x

Well, maybe you can get a 9th byte in there. Progress!

Nice. That's a great bit of syntactic sugar. This is getting to be pretty amazing.

The mystery is revealed in the first post. Anytime somebody posts "This is not a troll"...well, y'know. It is.

I think he just wants some attention.

You can use a few bits and pieces here and there, but it's generally not worth it as a utility library for general programming. You can use anything that isn't used by the DOS....and you can figure out where DOS stops by using some memory values. You need to READ mapping the atari and de re atari, not just peruse them. You don't need to write us a utility to use low memory, we all pretty much know what is there and can use it if we feel like it. There really is no magical piece of low memory that you can make useful to anybody in the general case, there are way too many failure cases.

Oh, the irony!

Harry, some friendly advice : Stop trying to do something so difficult. You do not understand the Atari well enough yet. You need to read, thoroughly, all of the available documentation and try some smaller projects first.

So....which are the lines in question, and why are they disabled? When you post something, the people you are asking help from should be able to compile and run and re-create the error. Don't make them have to guess. You are asking for people's time and effort, so you should set them up to be able to re-create the error. Typically, you should: 1. Create an example that exhibits the error 2. Include information about how to compile and run 3. Post everything required to do the compile and run

People are probably going to want you to post all your code, along with the .lst and .map files, as they have mentioned in the past.

Thought you guys might find this interesting. https://boingboing.net/2021/09/30/atari-st-in-daily-use-since-1985-to-run-campground.html

Perhaps you could read some documentation, such as this : https://www.atariarchives.org/dere/ MOre specifically, this section: https://www.atariarchives.org/dere/chapt08.php#H8_6

As far as the accelerator topic, I would just like something like the Rapidus, but that is more compatible. 400MHZ is not an Atari accelerator, it's a different computer.

Ok, I stand corrected. Must have been thinking about 3.2. Thanks.

You can download one of the cartridge versions and install in Altirra as a cartridge. There's an emulators selection at the very bottom of that list.

If you are learning programming from scratch, BASIC is probably a good way to start. If you have some background, you could consider Action! or Mad-pascal or C. If you plan to do anything that really needs all of the machine's power you will wind up in assembly at least partly anyway eventually.

Or, more generally, just SDX installed anywhere. http://sdx.atari8.info/index.php?show=en_download_release It can be run from cart, from disk, from specialized devices as above.

Well I guess. It's been a while and I can't remember if &arrayname gives you the array start anyway, or it gives you an address formed from the contents of the first 2 bytes at arrayname. If you get a ** back he would be overwriting page 0 probably. Anyways, I'm out.

Unless you've modified it, the problem is not in the crt0.s file. aux_memcpyto (j, &auxbufx, i); Aren't you taking an address of an address here?

I think one of the crucial steps would be an exposed API and an SDK with examples, so people can write apps and drivers. That way, you don't have to write it all. Put up the OS itself on github with an API (or at least the OS binaries and an API), and then sit back and be Lord Of The Pull Requests :). Y'know, like Linus.