First post, by valnar
In addition to DOSBox, I keep a running collection of DOS 6.22 + Windows 3.1 images for MS Virtual PC 2007 and VMware 6.x. Since these are known, unchanging machines, I am posting my DOS boot files below for everyone to use or critique. (I've also played with QEMU, Parallels and VirtualBox, but none of them are as compatible or stable as VPC & VMware Workstation.)
While both Microsoft and VMware emulate the 440BX chipset, they are not fully compatible with real machines. This is most evident in alternate memory managers and disk caching programs. Quarterdeck's QEMM386 and Qualitas 386Max flat out don't work. They will crash the VM. I've had good luck with UMBPCI, which is a great way to create UMB's without forcing the processor into protected mode like EMM386. Nevertheless, I use both in my boot files since in some cases I want to use expanded memory.
I use a combination of native Microsoft files (like himem.sys) and freeware alternatives that have been proven to be reliable and consume less memory. As for disk caching programs, just use Smartdrv - period. All the others have various problems that I stopped documenting awhile ago. I also use the latest versions when possible. ie. HIMEM.SYS, EMM386.EXE and SMARTDRV.EXE are all from Win98SE. (Windows ME does not exist to me)
I used to be pretty good at configuring boot files back in the day, but AXCEL216 is even better, so to give credit where its due, I got a lot of info from here: http://www.mdgx.com/umb.htm
Note that I couldn't take verbatim what he wrote since both VM's have their own peculiarities. These are tried and tested configs. If it looks like I left out some things AXCEL216 recommends or arranged them in a different order, it was done on purpose.
I also took some of the VPC specific info from here: http://blogs.msdn.com/virtual_pc_guy/archive/ … /21/246136.aspx
My VPC image uses DOS 6.22 and Windows 3.1. Since VPC comes with their fshare program, I can use that to transfer files between the VM and host. With VMware Workstation, I use WFWG 3.11 and do it through Windows file sharing. I don't care that I "only" use Windows 3.1 with VPC since I don't surf the Internet with either VM. That would just be an exercise in torture.
Edit: The VMware Workstation image is a 5.x compatible image, not 6.x
Below are the config.sys and autoexec.bat files I use for each VM, and a MEM /C/P output.