Atari800 - latest version?

Hi people,

As part of my continuing work on UberCassette, I've managed to make a .cas image of an Atari 800 tape. However, looking for Atari800 for AmigaOS reveals a very old (2004) version 2.3.0 on OS4Depot. Googling it finds even older versions.

I tried running it but it doesn't work in BASIC (and probably not anywhere else, but it's BASIC I need). I'm not sure if it's running horrendously slowly or whether it's the input that's not getting through (though it certainly crippled OWB so it's probably some kind of hiccup in running).

System is an OS 4.1 Pegasos2 G3.

Anybody have any advice?

It would seem we have a naming incongruity there. Dr.Hirudo keeps the AmigaOS Atari emulators up to date with windows versions, however it could be that "2.3" on OS4 Depot is refering to the 2.3 version of the Amiga port (Amiga port of a 2.0x version, for example on PSP they are using version 2.0.3) or something.

The latest Windows version as far as I know is version 2.1 (also check THIS thread on emulator zone), and it's the same you can downolad here from Dr.Hirudo's webpage:

http://hirudov.com/amiga/Atari800.php

P.S
Dr.Hirudo does NOT upload his stuff to OS4 depot.

Thanks Dax,

That's the version I tried though - I tried the Dr. Hirudo version and the OS4 depot version and they're the same codebase - and neither work...

Are we without a working 8-bit Atari emulator then..?

Have you tried your experiment with the 2.1 windows version on sourceforge.net?

I've been using Atari800Win to test my tape images.. all is fine there...

I think I tracked down the error.

The keyboard handling loop is receiving many IDCMP_RAWKEY pressed with a key code of $FF. Filtering out those keycodes seems to help.
No idea why this happens though yet...

Is this something that happens always, or only when you are experimenting with cassette stuff? and is it only on AOS4 or does it happen in the windows version too?

It's an IDCMP_RAWKEY message - nothing to do with Atari800 itself.

It's either a problem in Atari800's GUI, or a problem with AmigaOS 4.1 on the Peg2. If it's the former, then for some reason it keeps sending itself this message with a code of 0xFF, but I don't see why it would do that. If it's the latter, goodness knows what else it could affect.

I've told Dr. Hirudo of this and he's going to look into improving it.