Im convinced this IS Zsnes related so bear with me.
Im building myself a DOS 7.1 based games system and have included Zsnes and some games. I have also included a few DOS games, Duke Nukem 3D for example.
In my AUTOEXEC.BAT file i load the CWSDPMI.EXE file into HIGH memory as my Front End requires it. (in case its relevant).
When in DOS, i can run Duke Nukem 3D without a problem - as can i the other DOS games.
I can also run Zsnes no problem.
The problem is, if i run Zsnes and then afterwards try and run a DOS game, I get an 'invalid opcode error' which hangs the system and requires a hard reboot.
Does Zsnes have any TSR style elements that i need to unload after i run it?
Any help would be greatly appreciated.
After running Zsnes, DOS games get 'invalid opcode' error
Moderator: ZSNES Mods
it must be cwsdpmi and/or your front end. i believe cwsdpmi is loaded only when needed by whatever needs it as long as it is set correctly in the PATH environment. add its location in the autoexec.bat:
set path=%path%;c:\dos
in my case, all my dos utilities, tsr's and memory extenders are in c:\dos. i have a dedicated dos machine for gaming and i have no problems with zsnes.
what is a front end and which one do you use? i'm guessing it is some kind of menu system for the games. i use file wizard's menu system.
set path=%path%;c:\dos
in my case, all my dos utilities, tsr's and memory extenders are in c:\dos. i have a dedicated dos machine for gaming and i have no problems with zsnes.
what is a front end and which one do you use? i'm guessing it is some kind of menu system for the games. i use file wizard's menu system.
Thank you for your help on this.
You were spot on, it was cwsdpmi - as i expected.
I was loading it high, in autoexec.bat thinking it would carry over no problem.
Setting it to its own c:\cwsdpmi\cwsdpmi.exe directory and adding it to the path stting in CONFIG.SYS seems to have fixed it.
Thanks again.
You were spot on, it was cwsdpmi - as i expected.
I was loading it high, in autoexec.bat thinking it would carry over no problem.
Setting it to its own c:\cwsdpmi\cwsdpmi.exe directory and adding it to the path stting in CONFIG.SYS seems to have fixed it.
Thanks again.
-
- Veteran
- Posts: 970
- Joined: Fri Jan 21, 2005 11:15 am
- Location: Montana, United States