Hi all, I've tried to run E-UAE several times on my A1-XE with OS4.1, and so far have not been able to do it. Basically, it seems to initialise fine, I get a black window and the debug output lists the screenmodes etc. However, after a couple of seconds I get these two lines:
Illegal instruction: 4e7b at 00f80c38 -> 00f80cc0 Illegal instruction: 4c41 at 00fbd99a -> 00f80ad2
followed by a pause (which I think is the emulation restarting), and then I get a reset at f800d0 message. The window refreshes and it just loops like that...
Any ideas what I'm doing wrong? I've downloaded the latest version from Richard Drummond's site, reinstalled it, and tried taking a new ROM dump from my A1200, but still no joy. It's a shame, I'd like to run stuff from OS4.1 with Gluae...
Okay, I found the problem - I was emulating a 68000, and was trying to run Kickstart 3.1. I was sure that combination would work, but for some reason it didn't. Now I have it set to 68020/881 and it's booting fine.
Another issue I'm having now is that it runs fine from the shell, but if I run it from the icon it crashes with a DSI followed by an ISI just as it reads the .uaerc file. The stack in the icon is 64k - the same as my shell, and it's set to launch from shell... Any ideas?
Fair enough, I'll try that when I get home tonight... Just seems strange that the same amount of stack works from the shell, but not from a Workbench icon which launches as Shell...
Okay, I've tried upping the stack to 1,000,000 bytes in UAE's icon, and still no joy - still get a crash as soon as it reads the config file. Running from the shell works fine every time...
@Daedalus #11 ...It's quite a strange one!... It's been a key feature of E-UAE since day one. Icon for system boot; shell for debug boot. I used E-UAE FreeList years ago.
It's been a key feature of E-UAE since day one. Icon for system boot; shell for debug boot. I used E-UAE FreeList years ago.
Oh, I don't mean no debug output when run from Workbench is strange - many programs do that, including apps I've written myself. What is strange is that if you set the icon to run from shell, you do get the debug output but it crashes when it reads the config file, whereas if you run it from a separately opened shell it works fine. Possibly a bug in the startup code, or a bug in the Workbench feature to start programs from a new shell automatically...