Darn! Thats what I feared. 😢

Is DOSBox able to make use of a 16-bit PCI Ethernet ODI driver for DOS? I am running DOSBox 0.72 under Windows 2000 and one of the Ethernet cards that I have installed is a PCI Realtek RTL8139/810X Family Fast Ethernet NIC. I have recently installed Breadbox Ensemble (a GEOS Based GUI) in DOSBox and …

Maybe you could try placing share.exe in the mapped root for drive C:\ and then place the following in the autoexec section of the DOSBox.conf file: [autoexec] # Lines in this section will be run at startup. path=z:\;c:\ Not sure if this will solve your difficulty, but it might offer a solution if …

I agree entirely. For the record - the fact that Duke was installed outside of DOSBox is completely irrelevant.

Ok... well those were some pretty weird results. Under Windows 98 SE, Both NDO 3.2a and Breadbox Ensemble had lots of trouble loading DOS applications, whether inside of DOSBox or not. It did attempt to run the programs and had occasionally been successful, but more often than not games that rely of …

Hmmm... interesting. I went hunting for my earlier version of New Deal Office 3.2a so that I could install this and see if the same error would occur. I installed NDO3, and while it did not produce the FM-27 error, it did attempt to run the DOS applications before crashing DOSBox with an illegal …

I don't imagine that there are many people using Breadbox Ensemble under DOSBox, so if no one knows of a solution to this problem it will be perfectly understandable. I have installed Breadbox Ensemble 4.010 and it runs fine under DOSBox 0.72, but I have noticed that if I try to launch any DOS …

Yay! This works. There is a weird side effect making it difficult (but not impossible) to get to the game menu option at first, but I can live with that. Once I am in the game is completely playable in its original format. :happyhappy: Thanks again! I hope that a future release of DOSBox may offer …

Thank you very much wd. I'll have to try this tonight (Unfortunately, work beckons right now). If I can get this to work then it will at least offer a temporary solution until a more permanent fix comes down the road. I do appreciate all the information that you have provided so far. Thanks again.

Just zero out int34 and it should work. Its been a while and I'm a bit rusty at manually manipulating executable files. I don't know a lot about assembly language either. Is this change something that I would/could do with a hex editor to modify the games main executable (SW.EXE)? If so, could I …

Thanks wd. I do greatly appreciate your taking the time to determine the cause. Given the nature of the problem, I'm surprised that the program doesn't bail out when executed under POD. Although the problem is actually caused by the application (and appeared to be an oversight since it was …

Here is a link to a single zip file with both versions: SW10-11.zip Edit: I just tried binding DOS32a 9.1.2 to the SW.EXE file hoping that this might resolve the issue. Unfortunately it did not. :sad: If anyone should feel compelled to investigate this issue it would certainly be very much …

Ripsaw8080 is correct. Duke Nukem 3D 1.5 Atomic version needs to be able to locate the 'Support' folder from the CD. Whether this is accomplished by mounting an image of the CD or just copying the files over to your hard drive does not matter, but you do need to modify the CDROM.INI file so that it …

I don't understand why you want to run versions <1.2. They have probably fixed some bugs. True enough... I just enjoy playing multiple versions of my games, especially during the developmental stages, to see changes (some big and some small) that took place during the design process. Of all of my …

I have been unable to get Shadow Warrior 1.0 or 1.1 (Shareware versions) to run under any version of DOSBox. Version 1.2 (shareware and retail) works fine, but the earlier shareware versions mentioned above display the text "loading sounds and graphics", but then a blank screen appears with the …