Sorry but I'm not a Dosbox 'newbie', as I'm using it since the very 1st release. And I've read all your instructions and everything I did is 5 by 5 according to your posts.
- I've mounted the c drive as c:\temp\supremewarrior
- I've mounted my CD drive as d
- I've disabled Gravis sound system and I'm working with SB16
- The amount of memory configured is more that the game needs
- I've tested ALL the CPU cores (auto/normal/full/dynamic) with different clocks
The game has a "setup.bat" file that opens a graphical screen, so I can select my sondcard in the menu and I hear the samples correctly. After that, the setup pops up a screen asking me if I want to play the game, I answer "YES" (see screen attached - note at the bottom that it takes my soundcard settings automatically correct), then it goes to another screen, where it shows me the text: "Universal VESA driver loaded!(see the 2nd screen attached). At this point, when I hit any key to continue, the screen becomes white and after 2 seconds, it closes with that error I've posted in my first message here.
This setup creates a folder inside my c:\temp\supremewarrior folder called "DIGPIX" with a sound.cfg file. So my c is mounted correctly and the game setup engine is saving my settings. Also the setup program only let's you to select the soundcard; video modes and input settings are selected on-the-fly and are ok aswell.
Just to mention, that 1st screen I posted here before is the Test Screen, that is another file inside the CD that allows you to test everything and show the results on screen, so I can see that the keyboard is compatible, the sound card is properly selected and is working, the amount of memory available is ok, the vesa video drivers are ok and it also has a self-test, where it tests the entire CD contents, and the test runs flawlessly, with 0 errors!
I've pushed it to the limit, by creating an ISO image of the CD and I've used a Virtual CD program to mount the ISO as a second CD drive (like I do with The Need For Speed 1 (and it works), but neither this worked. It gives the very same results.
If you have another suggestions, I'm all ears, but I have strong reasons to say that it's something related to the Dosbox opcodes not properly emulated, and not to the game or Dosbox config issue.
Anyway, thanks for the replies.
Regards,
RC.