danwinslow

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.

That's kind of what conio.h does already. I don't think you are way offbase with your typed prints printu, printc, etc., as a smaller printf replacement, but they should be thin wrappers on top of the basic CIO calls that support outputting things to screen. So I wouldn't call it entirely unnecessary, but I wouldn't call it really valuable either.

Harry - you're missing a point of the OS architecture of the Atari. If you want to be compatible, use the OS-supplied CIO handlers rather than directly calling OS routines when you get ready to actually do the IO itself.

JSON is data transport, not language, and I like it too. I didn't mean to say you couldn't be productive in javascript, I said it's not a 'real' language, by which I mean complete. It's great for small glue and so forth and whipping stuff up, but try doing a large, complex development project with multiple programmers in it and you'll see what I mean. The build chains for large javascript projects are packed full of linters and ECMA script rule enforcers for a reason, and any schmoe who feels like it can break an interface contract by randomly adding items, the language does not care and will never tell you until you get a runtime failure. The type conversion issues are numerous and bizarre, and any language that actually needs a '===' operator is broken. You CAN do lots of things in it, but its more painful and dangerous than it needs to be. It does not do what an actual language should do -- be consistent, enforce contracts, provide actual threading constructs, and many other things. All my opinion, of course, but that's what I think. *edit* and thus the push for Typescript. It goes a long way, but still kind of lipstick on a pig. There's tons of libraries you can get that add utilities and add structure to javascript but that's kind of my point - the language itself is just not well designed and not complete. All the linters and structure/feature addition libraries are there because the language itself. Of course you can do stuff with it, but looked at as a formal computer language it's lacking. *last edit* sorry for the opinionated rant, and I'll stop derailing now.

I assume you meant Javascript there. No relation between the two, completely different things. I hate them both, but at least Java is an actual language. I'm trying to decipher the 'vscode language server' stuff now and yeah docs are kind of mediocre at best.

Noted, thanks Jon.

Yep, is definitely an option.

OK, I just bought one too. I will experiment with it, hopefully I can support both it and a software E:/S: driver.

Good info in that thread, thanks.

I am planning on messing around with my fujinet some, and there's a mostly text-based game I wrote that I'd like to try and hook the Atari up to. My question is, what are my options for software 80 columns? (Note - this is not something that ICE-T can handle, it's not TELNET either). I am going to write a custom client, and I'd like to know what my options are for software 80 columns and whether it would be able to keep up with a lot of text, say a screenful of 80 column text every few seconds. Thanks.

Well, what's the issue then? Start with googling for contractor companies on the B2 program in the right time frame, google his name and some of the companies, contact the HR departments of the companies, etc. There's no other way that I know of, unless you want to pay a PI. *edit* For instance, googling '"phillip price" cybersecurity' produces some interesting hits.

You mean without a name? good luck. If you have a name, then use the usual methods.

BLASPHEMER! Buuuuuuuuuuuurn! I have to admit, I have a bunch of old sinclair zx-80/81 stuff lying around. Never had a commodore, though.

The "high speed" part...do you mean speed of execution or speed of coding? If you mean speed of execution, then an assembler toolchain. Assuming you mean speed of coding, then a C or Pascal toolchain; you can write quickly to set up and test your code, and then go back and optimize parts you need by dropping in assembler where needed. I'd recommend either CC65 or Mad Pascal. If you are writing anything that will need most of the resources of the machine, you might as well bite the bullet and use assembler.

Now THIS is pretty cool. Nice. I'll have to finally set up my Fuji.

Ok, fine...why are are you designing an assembler-level output so different from anything else? It appears to have REBOL-like control structures in it. This is what confused me. You further state that 'this is a huge advantage'. Why is it a huge advantage? And after having read through the referenced post to figure out what you're citing, I assume you mean this is the 'output listing' from compiling this: unsafe!!! constant reference volatile byte! [ ; OS RTCLOK3= ~14 ; ANTIC COLPF2= ~D018 WSYNC= ~D40A VCOUNT ; ~D40B ] forever [COLPF2: WSYNC: overflow VCOUNT + RTCLOK3 << 1]