Atari 800 [v0.8] For Gp2x

[telengard]

Wow at someone noticed. This has been out for weeks Anyway happy Christmas everyone.

Anyway here are the directory details you need.

The GP2X dirs are hardcoded to (GP32 are under gpmm/a800 etc):
/mnt/sd/roms/a800/state
/mnt/sd/roms/a800/menu
/mnt/sd/roms/a800/disk
/mnt/sd/roms/a800/rom
/mnt/sd/roms/a800/exe

As a minimum the menu dir must have the ui.men and default.men files. Also you really needs the os roms in the rom dir. There are available on my site in the atari800_parts.tar.bz2 on my site. I will upload a stripped one at some point with just the bare minimum.

Basically the ui.men is needed for the menu controls. Without it there is no control definition and you can't do anything! This is the "freezing" at the menu issue...

Several people have had trouble setting this up. I will probably put defaults in the next version. Or at least display a big fat error message telling them what to do.

Good luck,

Mark

-----------------
Something else important...
WARNING
*** Be careful with the gp2x version***
The atari800 gp2x version writes temporary ATR files to /tmp when using ZIP, ATZ or DCM files. This should be fine since Gamepark Holdings wouldn't have been stupid enough to put /tmp on a soldered in limited write device such as Nand right? WRONG!

I am going to move my temporary files from /tmp in a later version when I get home.

Some suggestions for people who mostly know what they're doing with Linux:
I recommend you remount / with ro,noatime options. This can be done at the start of profile and prevents apps accidentally writing to the nand (including patches, so you have to change it for that...). Also it is worth changing it to mount the sd card with noatime. Without noatime it writes to the NAND or SD on every file read. This obviously wears them out quickly.

​

Hi there,

I'm also getting the lock-up mentioned earlier and I do have the men files present. Are the directories mentioned above absolute or will they work relative to where the executable is installed?

I have /mnt/sd/emu/atari_800/.gpe file
and then underneath that I have roms/doc etc.

From the looks of it the files need to be copied to the root of the mounted volume. I will try that now just looking to see if that is the case.

~telengard

 

[Reaperman93010]

they are partially absolute. the actual emulator gpe, doesn't care where it's at, but the supporting directory tree does.

from the directories in the tree, hunt for one called 'a800'
this directory and all its subdirectories have to be in your sd card under the '/roms/' folder on the root of the SD card.
(/roms/a800/all-the-subdirectories-intact) on the sd card at exactly that path.
after that it won't freeze up at the menu.

foft> I nearly was so excited that I didn't read your warning. This disk writing is certainly frightening, and worthy of its own topic. It definately needs amplified beyond this thread since there are other programs out there which may be writing in this manner.

 

[JaqMs]

I'm having trouble with the GP32 version. I used the version that wouldn't crash my GP32 (the 132 mhz version), and placed the a800 directory in my GPMM folder. When I run the emulator, it goes to a screen full of faintly-colored lines (not like when the batteries are low). It does not show a menu at all. Any ideas?

 

[foft]

I'm having trouble with the GP32 version. I used the version that wouldn't crash my GP32 (the 132 mhz version), and placed the a800 directory in my GPMM folder. When I run the emulator, it goes to a screen full of faintly-colored lines (not like when the batteries are low). It does not show a menu at all. Any ideas?

​

Sounds like you've done everything correctly. I've not seen that before though. Do you even get the splash screen?

Thanks,

Mark

 

[foft]

I'm also getting the lock-up mentioned earlier and I do have the men files present. Are the directories mentioned above absolute or will they work relative to where the executable is installed?

Yep they're absolute at present. I think I'll make them relative in the next version, with an optional command line are to specify where they are.

Mark

 

[telengard]

I'm also getting the lock-up mentioned earlier and I do have the men files present. Are the directories mentioned above absolute or will they work relative to where the executable is installed?

Yep they're absolute at present. I think I'll make them relative in the next version, with an optional command line are to specify where they are.

Mark

​

That would be awesome, thanks. I was able to play MULE and 'One on One' last night and I had a total blast. Thanks so much for working on this.

I'm trying to decide which emu I'm going to attempt to port. I'm thinking either Coco or TI 99/4a. I have a whole week off and need to do more than just game.

~telengard

 

[Optimus]

About the freeze. When I had the older version of this emulator, there were two versions, the 133 and 166(iirc) versions. The second probably started the menu at this high speed which my handheld can't stand so it freezed in the menu before I could be fast enough to lower the speed from some submenu there ;P So, I used the second one.

But now I just downloaded and tried the new version of this emulator and put the 133 filename as usual at my SMC and I get these freezes like I was running the 166 version. It's like the file with 133 at it's end is not really the 133Mhz startup version but something was confused in the compile? (I don't know if I try the 166 file and that works at 133 . I would prefer a menu in emulators at 100 or 66, and the overclocking to only apply when the emulation starts.

 

[foft]

About the freeze. When I had the older version of this emulator, there were two versions, the 133 and 166(iirc) versions. The second probably started the menu at this high speed which my handheld can't stand so it freezed in the menu before I could be fast enough to lower the speed from some submenu there ;P So, I used the second one.

But now I just downloaded and tried the new version of this emulator and put the 133 filename as usual at my SMC and I get these freezes like I was running the 166 version. It's like the file with 133 at it's end is not really the 133Mhz startup version but something was confused in the compile? (I don't know if I try the 166 file and that works at 133 . I would prefer a menu in emulators at 100 or 66, and the overclocking to only apply when the emulation starts.

​

I see. Mine runs at 166, so I probably would miss that if I'd messed up. I'll check.

Thanks,

Mark

 

[TelcoLou]

I'm also getting the lock-up mentioned earlier and I do have the men files present. Are the directories mentioned above absolute or will they work relative to where the executable is installed?

Yep they're absolute at present. I think I'll make them relative in the next version, with an optional command line are to specify where they are.

Mark

​

That would be awesome, thanks. I was able to play MULE and 'One on One' last night and I had a total blast. Thanks so much for working on this.

I'm trying to decide which emu I'm going to attempt to port. I'm thinking either Coco or TI 99/4a. I have a whole week off and need to do more than just game.

~telengard

​

:blink: :blink:
:wub: The TI 99/4a was my first computer!

 

[remowilliams]

I'm trying to decide which emu I'm going to attempt to port. I'm thinking either Coco or TI 99/4a. I have a whole week off and need to do more than just game.

~telengard

​

Definitely the TI 99/4a! Tunnels of Doom on my GP2X? That would ROCK!!

 

[foft]

Optimius: Hmmm, looks like its running at 132MHz. I'm not sure what is causing your freezes.

Anyone else getting freezes on the new version?

I did notice I introduce sound issues on 0.8 non cycle-exact version though. Odd...

Mark

edit: Optimus: Which version did you upgrade from? If it was pre-0.7 I think I may know whats going on. There was a change in 0.7 to allow configuration of keys for the menu. You need a ui.men config file, otherwise you can't select anything in the menu.

 

[Greenchili]

Just got this sucker going the other night! Nice!!

Looks like it will need some optimizing though. I had the sucker running full throttle with frameskip on and boulderdash ran pretty decent bad had sound problems here and there (usually after completing a level).

I may be a little crazy but pacman seemed just a tad slow as well.

But what can I say? I'm in hog heaven.

Keep up the good work. I'm a big fan of your emulator for the GP32 as well.