ccarr690 wrote:ok,
well I would strongly suggest going into native dos and having the appropriate dos drivers for your hardware. When you say that windows doesnt need the mouse drivers and mscdex. to run a windows dosbox - thats because windows is already loading all of those drivers and utilizing memory that could be used for your game. If you check your available ram within your dosbox versus a native box. You will see a lot more available ram in the native dos mode. The goal in running dos apps is to get the most conventional and extended memory as possible out of the 640k.
1.- Under Win9x DOSBoxes (And 3.11 for Workgroups 386 Dosboxes) VXDs will take care of CDROM and MOUSE. No need of any real mode TSR or *.SYS device driver. VXDs don't use memory in the first megabyte (conventional/upper/extended). Taken from Undocumented DOS book.
2.- Without any drivers loaded from Config/Autoexec at windows bootime you will see more ram free for DOS apps in the 1MB area. In effect, you shouldn't load any old TSR or Real Mode driver from config.sys if isn't really necessary, because in effect you will fuck your amount of conventional RAM, and the effects will persist across all your VM DOSBoxes. More details about this in the Undocumented DOS book.
3.- And there are less probabilities to get that under plain DOS + TSR & *.SYS Drivers, specially if you have not-so-friendly-with-DOS hardware like many PCI soundcards with awful big TSRs, or TSRs which require EMM386. As gold rule, if your game/app works friendly under a DOS Box, you will want to run it always under a DOS Box to take advantage of all the facilities and free conventional memory that VMM offers to DOS applications. For max performance, you will want also run these machines using VXD-only drivers for all the hardware. WDM Win98 drivers aren't DOS box friendly.