In one of the VMs that I'm running. Windows 3.0 is currently installed on a 1,000 MB SCSI hard disk with a BusLogic SCSI controller with 16 MB of system RAM. When running Windows 3.0 in 386 Enhanced Mode, attempting to click on the one of the icons in Program Manager throws this error message:
Terminating current application.
After clicking on OK, I get kicked out of Windows 3.0 and into the MS-DOS prompt.
In a MS-DOS 6.22 VM, I'm currently emulating four 2,000 MB SCSI hard disks (8,000 MB total) with the virtual CD-ROM on the primary master with 64 MB of memory allocated. The problem here is that when I try to load a driver into high memory, this error message throws up:
Abort, Retry, Ignore, Fail?
If I press A to abort the second time, this results in a fatal error message:
Cannot load COMMAND, system halted
To fix this, I had to press CTRL+ALT+Insert to reset. And when I attempted to run Windows for Workgroups 3.11 on a emulated SCSI hard disk, it will display the splash screen, but when it attempted to run, it just kicked me out and got thrown back to the C prompt. And in some cases, attempting to run WIN at the command prompt and the VMware Player will end up rebooting by itself.
The hard disks are running under the MS-DOS 6.22 VM use the LSILogic Virtual Host Adapter.
I'm sorry if this fails to make sense, but is there a way to fix this to make MS-DOS and Windows 3.x work properly with a SCSI hard drive under VMware?
This post has been edited by ppgrainbow: 27 May 2012 - 02:54 AM