MiSTer FPGA Forum

zorrobandito wrote: ↑Thu Sep 02, 2021 12:11 am I can't help with the Win98 aspect but can confirm that Duke Nukem runs fine on MISTer from Flynn's pack. The Atomic Edition struggles with framerate and is basically unplayable but loads to the title screen and runs the demo.

I select EMM386 and Soundblaster as my startup options.

zorrobandito wrote: ↑Thu Sep 02, 2021 11:14 pm "The thing is the game still crashes if I leave it on for an hour."

Clearly I don't play it as much as you

I'll give it a try today and report back.

zorrobandito wrote: ↑Sun Sep 05, 2021 4:12 am OK, so it took me a bit longer but I left it running last night for about 3 hours on the demo. There were points where it seemed to have crashed - wouldn't respond to keypresses, even Ctrl-Alt-Del, but it came back after a few mins as if nothing had happened.

Obviously I wasn't actively playing it for that long but perhaps it's worth trying the same experiment on yours?

Caldor wrote: ↑Tue Sep 07, 2021 9:14 am Ahh, that is my video

Yes, I run DOS 7.0 I think it is, which comes from Windows 98. It seems to be more compatible than FreeDOS while having most of the features of FreeDOS as well. Mainly support for large partitions / FAT32.

One problem I ran into when it came to optimizing Duke3D that confused me at first, was that it seemed to by default run at 640x480. That runs very badly on AO486, it has to be set to 320x240 instead or something like that. There are some other settings that might also help.

I do think there were some audio issues as well, where I had to use specific settings or memory managers to be able to have music and sound effects.

If you are still having issues, I can check up on what my exact boot settings are and such when I get home.

Caldor wrote: ↑Wed Sep 08, 2021 12:38 pm The resolution is adjusted in game. There should be a graphics setting under the options if I remember correctly.

akeley wrote: ↑Fri Sep 10, 2021 1:14 pm The main resolution is set outside of the game, in the "setmain.exe" or "setup.exe" files.

I've tried the standard, shareware version and it crashed when using standard setup, but with some tweaking I was able to play for a longer time. Still, it was only 320x200 and yet quite choppy. If you really want to play it I'd suggest just sticking with Dosbox, where it should just work with no problems and fast performance in high VESA resolutions (800x) .

Captain FPGA wrote: ↑Thu Sep 16, 2021 11:08 am Where can I find "setmain.exe" or "setup.exe" files? Do I activate them from my pc or Mister OSD when the core isn't active?

akeley wrote: ↑Thu Sep 16, 2021 11:58 am

Captain FPGA wrote: ↑Thu Sep 16, 2021 11:08 am Where can I find "setmain.exe" or "setup.exe" files? Do I activate them from my pc or Mister OSD when the core isn't active?

They're in the game's directory, on MiSTer's SD card. I assume you're using flynnsbit's pack, so then I suppose you're starting Duke through The Dos Launcher (long list of games with blue background). So once you choose Duke3D from this list, it should show a little window with "Multiple Components Found". Choose setup.exe from this sub-list and then go to Screen Setup and pick 320x200. You can also choose sound options in Sound Setup (eg you can run No Sound to see if the game still crashes without any sound drivers). Then "Save and launch", it should go back to main TDL screen, then run Duke as you normally would (via duke3d.exe).

akeley wrote: ↑Thu Sep 16, 2021 11:58 am

Captain FPGA wrote: ↑Thu Sep 16, 2021 11:08 am Where can I find "setmain.exe" or "setup.exe" files? Do I activate them from my pc or Mister OSD when the core isn't active?

They're in the game's directory, on MiSTer's SD card. I assume you're using flynnsbit's pack, so then I suppose you're starting Duke through The Dos Launcher (long list of games with blue background). So once you choose Duke3D from this list, it should show a little window with "Multiple Components Found". Choose setup.exe from this sub-list and then go to Screen Setup and pick 320x200. You can also choose sound options in Sound Setup (eg you can run No Sound to see if the game still crashes without any sound drivers). Then "Save and launch", it should go back to main TDL screen, then run Duke as you normally would (via duke3d.exe).

akeley wrote: ↑Thu Sep 16, 2021 2:36 pm I doubt OG Xbox can handle Duke. But am pretty sure anything you write these posts on can

Caldor wrote: ↑Sat Sep 25, 2021 6:55 am Okay, seems to be working for me.

My settings are that I am using EMM386, set AO486 to 16MB RAM, using MIDI for the music, with the PiMidi, not sure if that makes a difference. I played for 1 hour playing the game, now its just running and it has run a total of 1 hour 30 minutes. I ran it using DOS32A, so the command line is
"DOS32A DUKE3D".
Resolution set to 320x200 or whatever that default low res setting is. Oh, and no mouse. That might be relevant, because I have gotten several mouse games bugging out on me.

Did some more tests... crashed when I ran the same settings but without DOS32A. So even with the 16MB setting it crashes with DOS4GW. Now I am trying with mouse enabled but using DOS32A. So far no crashes, but it has only run for 10 minutes. The first game ran for more than 3 hours, so that certainly seemed to not have the issue. Other test done, still running without crashing as long as I use DOS32A. Using mouse did not cause a crash. Been running for 50 minutes now.

SuperBabyHix wrote: ↑Thu Sep 16, 2021 11:05 pm If you want to pay Duke 3D on an Xbox it looks like there is a homebrew source port: https://www.gamebrew.org/wiki/Duke_Nukem_3D_XBOX

Captain FPGA wrote: ↑Sat Oct 02, 2021 8:52 am

Caldor wrote: ↑Sat Sep 25, 2021 6:55 am Okay, seems to be working for me.

My settings are that I am using EMM386, set AO486 to 16MB RAM, using MIDI for the music, with the PiMidi, not sure if that makes a difference. I played for 1 hour playing the game, now its just running and it has run a total of 1 hour 30 minutes. I ran it using DOS32A, so the command line is
"DOS32A DUKE3D".
Resolution set to 320x200 or whatever that default low res setting is. Oh, and no mouse. That might be relevant, because I have gotten several mouse games bugging out on me.

Did some more tests... crashed when I ran the same settings but without DOS32A. So even with the 16MB setting it crashes with DOS4GW. Now I am trying with mouse enabled but using DOS32A. So far no crashes, but it has only run for 10 minutes. The first game ran for more than 3 hours, so that certainly seemed to not have the issue. Other test done, still running without crashing as long as I use DOS32A. Using mouse did not cause a crash. Been running for 50 minutes now.

I know I'm getting to this late but wanted to tell you my situation has been resolved. I replaced DOS4G using the stub extender for 32a now, the game is forced to boot using DOS32A each time.

I performed a 10 hour stress test afterwards to make certain the thing is working this is both with 250 something megs of RAM and with a mouse, it works. Thanks for trying to help!