It wants to see the MSCDEX driver. You can enable it in DOSBox by mounting any folder you like with the commandline option -t cdrom. E.g.: mount e: c:\ -t cdrom

It seems to be problem with your PoP version. I tried to reproduce this behaviour with my version and I didn't work. If you press shift+l you'll be transported to the next level, and if try to reach lvl 12 that way you'll only have 3 minutes to rescue the princess.. I tried the cheatmode thingie as …

if you want extended memory then you must disable both xms and ems in dosbox. 😕 Isn't XMS=Extended Memory? So why do we have to disable it to get extended memory?

Make sure that you use the -t cdrom commandline parameter. So you mount your CD-Rom drive like that: mount d: d:\ -t cdrom

Maybe it's compatible but I doubt that it will run in DOSBox since MS DOS utilities usually have a version check but you can try it. I have to program assembler code applications for school on a 8086 in MS-DOS debug I'd personally prefer to use an assembler and linker to write these apps since it is …

Obviously sound is very important for gameplay in FPS so running without sound is not an option. Well it is the only option if it runs too slow with sound and if you don't have any other possibility to run it (e.g. a real DOS/Win9x installation or sth like that). And if you can't live without sound …

Hm I have to say that BLOOD runs with acceptable speed on my P3 1.2 GHz with Dynamic Core, SoundBlaster 16 sound (22050Hz) and MPU 401 for music. OK there're some places where it runs quite slow and it sometimes crashes DOSBox :s-face: but in general it is playable. I'd suggest to turn off sound. …

This can have multiple reasons. Maybe the program tries to access some features DOSBox don't emulate (e.g. a particular graphics mode). It is also possible that you didn't configure DOSBox correctly. Maybe sth. goes wrong with the CPU. For example I noticed that Redneck Rampage only starts up when I …

It DOES already run in DOSBox, at least the 256 color version. The 24-bit color version doesn't run (yet).

Some time ago I used TSearch 1.6 to modify the amount of Money and the Division in Lamborghini: American Challenge. TSearch is a Win32 memory "hacking" app. I just opened the DOSBox process with it and looked for the money and division value. I didn't test it but I think if you restart DOSBox and …

Just tested it. You obviously used the normal core. When I run it under normal core it's really slow (just as you reported). Anyways switching to dynamic core makes the game playable @ 38000 cycles.

Hm FOR is a batch command for creating loops but I don't know whether it was already available in DOS... 😕

velvetmilk did you increase the cycles? By default DOSBox runs @ 2500 cycles and this might be a bit too slow. You can increase the cycles by pressing CTRL-F12 while DOSBox runs. If it's still running to slow you can try to use the dynamic core. Have a look @ the dosbox configuration file to find …

I get this "cant create ddraw surface" error whenever I choose ddraw output, and it switches back to surface. Why is that? Well it's a problem with the SDL library. The version you're using hasn't been compiled "correctly". You have to get the source code and find this in src\video\windx5\SDL_ …

I don't want to promote Warez or Cracking here but you can try to find a crack for your program (i.e. a version which was modified so it doesn't require the dongle anymore). Since you're obviously a licensed user of the software (you own the dongle) it shouldn't be a problem. If it is a problem for …

I have to agree with mirekluza. If you personally prefer statically linked libraries compile your own copy of DOSBox. Get the source code of DOSBox as well as of the libraries you want to link and compile the libraries as static libraries and link them with DOSBox. I did this with SDL, SDL_net, …

Hm it seems that the graphics mode Jack Orlando wants to use isn't supported by DOSBox. The DOSBox debugger sais it wants to set VESA mode 111h with INT 10 which is obviously not supported by DOSBox.

That sounds like it might very well be your problem. The gnu auto* utils are subtle and quick to breakage, and I wouldn't mix and match pieces from one tarball and another. Run autogen.sh to generate the configure file (note this usually requires having certain utilities installed, most likely …