This Mr. Anonymous 😀
Sorry about my abiguous naming of stuff. I know about the *nix and x86, I should have been a little more specific about what I was aiming for. And yes, *nix can run on pretty much any hardware that has a general processor (and even a few specialized pieces).
I am aiming to have an emulator/simulator that can run DOS games under a Win2K client to play a few old games and to help a few others out that are on Win2K as well.
The game that I am aiming to get running is System Shock 1 on Win2K and WinXP with full support of sound and graphics. The graphics are not the biggest problem though... sound has been until VDMSound. VDMSound does a GREAT job of getting the sound up and running but now my last issue to work out is memory. The game really does not like the memory manager under Win2K and so I have been looking into alternatives. The game's own manager is DOS/4GW and between the manager and the game, the game complains about memory allocation. The game will boot to the intro and even show the game menu, but attempts to start a game crash out with their version of a, "Not enough memory" issue.
Bochs is pretty impressive as well. Getting the images going was not a problem for me as I have dealt with this type of manipulation under Windows before. Once you have a bootable floppy image with a CD-ROM setup, you can move data into the hard drive image without too much problem as long as the data can be put on a CD-ROM, otherwise you will need to move data floppy-by-floppy and making the floppy images and mounting them in Bochs is not instantaneous. Supposedly there are a couple of utils to work inside drive images easily, but I did not need them for this project.
On the Bochs to-do list, the Windows port person was talking about the work to allow full screen soon, but that it wasn't available yet. I am still not complete sure that is the reason for the failure though. I need to work on it some more once I get off work tonight and see if I can track the error a little better than simply refering to the error message that the program is outputing.
This whole thing is getting WAAAY off VDMSound topic though and I don't like to hijack anyone's forums no matter what the cause.