Hard
Disk
|
Currently
supports connecting only to a hard disk image file. You cannot
connect to a hard disk and share it between a host and guest. You can use networking to get files between guest to host.
|
CD
Rom
|
Supports
Booting and connecting to CD Rom Drive and a CD Rom Image file.
It only supports 1 CD Rom Drive. Does support Data DVD disks but not Movie DVDs.
|
Floppy
Drive
|
Supports
Booting and connecting to Floppy Drive and a Floppy Drive Image
file. It only supports 1 Floppy Drive.
|
Shared
Folders
|
This may work for you but you should back up your hard disk image before you install. It could be that this is only supported
by Windows 95 (by default) and I think there are now additions
(what they call plug-in's). I tried this on NT 4.0 and could no
longer use it - had to re-install NT 4 on the session.
|
Mouse
|
Works
|
COM
Ports
|
Work
for COM1 and COM2. When Guest has a port, Host cannot use it.
Recommend using shared networking and connect to internet from
Host.
|
LPT1
|
Works,
but its better to share your printer over your Virtual LAN so
all sessions can use the printer. If you have a printer that has
no OS/2 driver, you'll want to have that session grab the port
directly but you won't be able to use your Guest Printer from
your OS/2 Host.
|
Networking
|
|
Sound
|
Works
fine on all Windows Guests, and on some Linux guests. I have Sound Blaster
LIVE!, other devices may not work as well.
Sound
driver for Sound Blaster Live that ships with eComStation 1.2
did not work on my machine. Here
is a prior version that did work, I just copied on top of the
drivers that shipped.
|
Video
|
|
| To
enable sound in VPC/2 guests: |
-Open
regedit2.exe
-Add
the following new key:
HKEY_LOCAL_MACHINE\Software\VPCWIN\HKEY_LOCAL_MACHINE\System\CustomBuild
-Under
this key add a DWORD entry named "DisableAudio" and
set the value to "0"
You
may also create a Program Object that runs CMD.EXE and for a
parameter paste
"/c start /f /c /min /pgm
I:\VirtualPC\VPCSETUP.EXE /tweakvpc" which will allow you
to turn the sound on through a configuration screen. |
| How to fix VPC from an exception error: | There
is a bug in the OS/2 Version of Virtual PC that causes an exception
error if the name of the virtual machine is too long. If you name
or rename a virtual machine longer than about 24 characters, you may
find that you get an exception error and VPC will terminate.
Nothing seems to fix the problem. There is one thing that
will fix the problem without rebooting or reinstalling Virtual PC. The
properties of each virtual machine, including the name are stored in
the registry. You can find the offending entry in regedit2 and
delete it. Here are the steps: Open
regedit2.exe Look for
the following new key: Navigate to:
HKEY_CURRENT_USER\SOFTWARE\VPCWIN\REGROOT_HKEY_CurrentUser\Software\Connectix\Virtual PC\4.0\Configuration\<name of Virtual Machine>
HKEY_USERS\.default\SOFTWARE\VPCWIN\REGROOT_HKEY_CurrentUser\Software\Connectix\Virtual PC\4.0\Configuration\<name of Virtual Machine> You
will see the name of the virtual machine which has the new name and the
old name and maybe an incomplete set of parameters. You should
delete the offending entries in both places. The virtual hard
disk will still be there, but you will need to recreate the entries
which will add all the parameters correctly back in. A rename
wont work because there will be missing parameters from when VPC
crashed. After you delete both entries, Virtual PC should start up and all your other virtual machines will still be there.
|
| What if VPC Hangs when I start it? | Sometimes VPC hangs when started. There are a couple of things that can be done to solve this problem: Run chkdsk on all your disks. Have a copy of the VPC EXE and DLL files handy so you can copy/replace any file that may be corrupt. Run Checkini (see Hobbes Archive for WPTOOLS).
|
|
