SD> OS/2 can be a bitch to get working properly in a VM.  It requires some
SD> odd
SD> CPU calls that some VMs don't support and in some cases, it requires
SD> hardware acceleration that some modern computers can't support properly
SD> in a
SD> VM.  I'm not an expert in this, of course, but I've enough experience to
SD> not
SD> be bothered.

Since my original physical BBS computer ran several version of OS/2 (Warp
3, Warp Connect, and Warp 4), that is what I tried to get working under
VMware.  I never was able to get any of those version to run under VMware,
but later found out what was causing the problem.

In order to get OS/2 to run in a VM, you can't use HPFS.  I was never able
to get it past loading the HPFS driver.  

I decided to try the latest eCommstation, which added the JFS file system.
That file system worked like a champ in VMWare.  

Once I had a working VM with JFS, I manually moved the data from my Warp 4
physical system's image to the VM (SIO drivers, OS/2 Flash Policy Server,
etc).

Either physical or VM, I would go with the latest eCommstation.  I also
loaded Samba for eCommstation to support SMB 2.0 file sharing so that I
could map back to my Active Directory shares from the VM.

- Mark

--- WWIVToss v.1.50