joelpatrick

Hi, I installed pocketnester and got plenty of roms and it was working great. But today I went to open one of my roms and it gets an error that says "emu->do_frame() error". It then freezes nester so that I must stop it so it will reset. I thought that it may have been that particular rom so I tried others that I already played, same thing happened!! I saved nester and the roms on main memory, so I decided to delete them all and put them back. This time I put it on my SD card, but the same thing occurs! Why did it work flawlessly and then all of a sudden refuse to play roms that it had played previously. Can anyone help me out there?? By the way, it was the Beta .8 pocketnester. I also tried to install the v7 of nester and my axim wouldn't recognize it. Also, its a 624 Axim51v with WM5, if you need to know that. Any help would be GREATLY appreciated

badbob001

v8 doesn't run on WM5. It may work the first time but will fail after that. After the first run, it sets the program configuration to full screen and that causes it to fail afterwards. I have found no practical workaround for that since the author states that it requires fullscreen to run optimally.

I tried contacting the author but he has not responded.

joelpatrick

Well that figures. Thanks for the info. This site is the main reason I got the axim. How many other pda's have such a active forum community?

JonMisurda

Originally Posted by badbob001

v8 doesn't run on WM5. It may work the first time but will fail after that. After the first run, it sets the program configuration to full screen and that causes it to fail afterwards. I have found no practical workaround for that since the author states that it requires fullscreen to run optimally. I tried contacting the author but he has not responded.

I replied to your email quite a while back. I stated that I have not had time to look at it, and I'm not sure what all is going wrong, since I've only modified a portion of the program. I didn't write the original. I thanked you for your investigation into a source of the error, and promised I'd look at it as soon as possible.

Jon