Converting a physical XP machine to VMware - issue booting

Hi!

I have a cousin who is a realtor, and she has custom made software on an XP machine. She wants to get it on her Windows 10 laptop. I tried copying the program and installing all the same .NET and runtime stuff that was on the XP box on the 10 box. I used procexp to see what files it interacts with and what registry keys it uses and migrated them over but no matter what I do, it crashes when I try to run it.

So my next idea was to just virtualize the machine. I figured she could run it on the 10 machine in a VMware player. Cloned the disk, used a convertor to make it a VMware vmdk disk, created a XM and stuck the disk in. XP boots, I get the logo, but then it BSOD's with 0x0000007B (0xF789E640, 0xC0000034, 0x0, 0x0). Looking it up, it appears XP is unhappy that the boot controller has changed. I tried the boot repair and stuff like that, but to no avail.

Anyone know how to make it work? Anyone have experience with migrating XP to virtual? Thanks!
 
Surely she have the installer program for custom made software? If not then what did she plan to do if the computer hard drive failed?
If so, then why don't you create a new Windows XP virtual machine and install the custom software in it?
 
Last edited:
Hi!

I have a cousin who is a realtor, and she has custom made software on an XP machine. She wants to get it on her Windows 10 laptop. I tried copying the program and installing all the same .NET and runtime stuff that was on the XP box on the 10 box. I used procexp to see what files it interacts with and what registry keys it uses and migrated them over but no matter what I do, it crashes when I try to run it.

So my next idea was to just virtualize the machine. I figured she could run it on the 10 machine in a VMware player. Cloned the disk, used a convertor to make it a VMware vmdk disk, created a XM and stuck the disk in. XP boots, I get the logo, but then it BSOD's with 0x0000007B (0xF789E640, 0xC0000034, 0x0, 0x0). Looking it up, it appears XP is unhappy that the boot controller has changed. I tried the boot repair and stuff like that, but to no avail.

Anyone know how to make it work? Anyone have experience with migrating XP to virtual? Thanks!

Hi Straham.

Interesting question, intelligently put and polite. A problem, that needs fixing. I will describe the path to solving the problem after explanations as to why I choose that path.

I have discovered over the years, many problems with Virtual XP of any description. People that don’t have to run serious business, industrial, or scientific programs play around with it. If one tries using it on serious stuff like Autodesk Revit, or AutoCad, Solidworks, Inventor, you will have nothing but problems.

The simplest solution is always the best. Plus there is no use instantly abandoning something that you have obviously dedicated a lot of time to trying. So, I have put you a cloning program I use, on my OneDrive. So you can give VM one last try. I personally feel this is the best cloning software, that has least problems.

Here are the 32bit and 64bit versions.

Ghost This is all You need.zip

Some links below, for some instructions.

https://www.cybernetman.com/kb/article/how-to-create-a-bootable-usb-with-ghost64

https://knowledge.broadcom.com/external/article/171757/how-to-perform-disk-to-disk-imaging-usin.html


If this does not work then your best option is to still clone the hard drive and either service, or rebuild your friends old machine.

Then you will use the inbuilt “Remote Desktop Connection” from your friend’s main laptop, workstation or desktop to access the program from the XP computer in a window. The reason you will do this – is because your friend will need to be able to cut and paste and access files across different programs I am guessing. Yes unfortunately it means booting two computers. But this is a must have solution driven problem.

Remote Desktop Connection is easy to set up, works well; And if the main computer is fast with multiple cores is pretty seamless. To give an idea of how good it can be. I have seen another contributor on this site use it to remote into a Windows 10 machine from an XP machine in order to use Office 2022 and AutoCAD 2019 to copy and paste into AutoCad 2012 and Inventor on the XP system. It is seamless.

Your friend may be disappointed with this solution. However, when its money and business. Put it this way. They will end up with a system that can multitask faster and it is tax deductable.

Alternatively: If the program is not too bespoke, let me know what it is. I will see if I have it or can get it. You will then just need to transfer the database over.

Furthermore: If you need further help. Please give me the exact model of both machines and the exact components of each, including CPU’s, memory, graphics, hard drives etc.

Hope this helps.

Madu
 
Interesting. I run several OSes in VMWare including XP but have never attempted to migrate physical to virtual. A cursory search reveals it may be possible with a few caveats. Maybe if I have time I will attempt to migrate my XP laptop to VMWare and list the steps I took If I am successful.
 
Hi!

I have a cousin who is a realtor, and she has custom made software on an XP machine. She wants to get it on her Windows 10 laptop. I tried copying the program and installing all the same .NET and runtime stuff that was on the XP box on the 10 box. I used procexp to see what files it interacts with and what registry keys it uses and migrated them over but no matter what I do, it crashes when I try to run it.

So my next idea was to just virtualize the machine. I figured she could run it on the 10 machine in a VMware player. Cloned the disk, used a convertor to make it a VMware vmdk disk, created a XM and stuck the disk in. XP boots, I get the logo, but then it BSOD's with 0x0000007B (0xF789E640, 0xC0000034, 0x0, 0x0). Looking it up, it appears XP is unhappy that the boot controller has changed. I tried the boot repair and stuff like that, but to no avail.

Anyone know how to make it work? Anyone have experience with migrating XP to virtual? Thanks!
I am surprised this question is not asked every week. It seems such a sensible thing to do. I looked at this a couple of years ago. I am the person Madeleine was referring to.

I decided not to bother with a virtual box because of the huge amount of work and steep learning curve involved. It is not just a case of installing Virtual Box and then installing a fresh version of XP. It is real hard graft and research.

The procedure (That I have not tried, or attempted to do) would be:

  1. Make sure your friend’s laptop is a high-end workstation Laptop. With Multicore CPU minimum of 4 cores and at the very minimum, 32gb of ram preferably 64gb. Or give up
  1. Download ones preferred VMware. For instance, VirtualBox 7.1 or whatever VMware most lets you follow procedures below.
  1. Install a fresh version of Windows XP on the virtual machine
  1. Try to configure Virtual machine, so that it matches the hardware as closely as possible to your friend’s old machine. With two virtual hard drives.
  1. Install the cloning software and drop over the large backup/clone file on first drive with virtual XP on. In your case, you used something to convert backup to VMware vmdk disk. I.e. a VM back up. Something I wouldn’t do, as you are now adding another point of unsolvable possible failure.
  1. Now within the virtual environment restore the back up on to the second virtual drive.
  1. Reboot Virtual machine from the second virtual drive and pray.
It sounds like you a smart enough to have got to this point already. The problem I suspect you are having is that, you were unable to replicate the hardware of your friend’s old machine closely enough.
  1. I suggest you restore the back up the way I have suggested using Ghost or any other back up within the virtual environment. Then you will be able to see if that works. After that you will definitely be able to say it is the hardware replication problem.
  1. Wait and see if ClippyBeer can come up with something.
  1. If he can’t. Give up on VMWare and follow Madeleines advice.
 
no matter what I do, it crashes when I try to run it.
I am pretty sure you will tried this, but just in case. You will need to run the program in compatibility mode and probably 32bit on Windows 10. You would do this by right-clicking on the .exe and setting parameters.
 
Back
Top