
Raising a funding campaign as I came across the story of Marc Alexander, 18 month baby boy born in Haiti and diagnosed bilaterally deaf (both ears). I still prefer to save to VHD format for Windows 2000.Help fund a cochlear implant surgery for 18 month old baby You can save them to a local drive or if you have a fast network (from my experience 1 Gbps LAN connection would save a 40 GB hard disk in a matter of 15 minutes via network) you can use an existing sharedįolder.

So there are no integration components - all devices must be emulated.Īlso, be sure that your application can handle running in a VM. Because Server 2000 was never a supported OS. The same process that you used with 20 to move a server to new hardware and carry forward the installed applications and system settings.īackup, install OS on new hardware (VM in this case), restore into new OS install / new hardware. Now, you can use the Windows Server Backup and restore process. There is no free tool that will give you much success, but instead long hours of pain. P2V of 'old' operating systems is actually very complex, due to the OS not handling device and hardware changes (like current OS versions do).

Back in the day PlateSpin were the only option for 'P2V'.
