![]() ![]() Summary on how to fix the Windows XP crash (BSOD) on boot after hardware has changed: I've tried a lot of things, of which I will spare you, the fix was to change the type of IDE storage controller: ICH6 Windows XP would not boot, throwing a BSOD and immediately rebooting. 1, ie \192.168.8.1\c$ in Acronis to search for backup that you copied to the VirtualBox host machine. Search VirtualBox settings for it's DHCP range and use. Note: You can try to plug the external drive directly to VM (Acronis support of that drive pending), or you can use windows network share on VirtualBox host as I did. I created a new Windows XP VM following instructions from VirtualBox and used Acronis rescue media ISO to boot the new VM and restore the backup. I used Acronis bootable rescue media on a USB stick to backup Windows XP HDD to an external drive. My attempt to use Clonezilla was semi-successful, as I needed to move a large HDD to a smaller virtual drive and after a few attempts I bailed in favor of Acronis True Image, since I had previous experience using it. Moving that Windows XP installation to VirtualBox 5.0.14 has proven to be more difficult that I estimated, probably because nobody uses XP anymore. I didn't want to keep a dedicated piece of hardware for this single purpose and don't want to re-install the specialized dealer software - so migration to a VM was commenced. It's proven itself very useful for car troubleshooting, primarily reading and resetting OBD (error) codes. In my case I had a beater Windows XP PC with XP-only software to connect to my car. First off, I feel sorry if you need to touch Windows XP, especially in 2016, but hopefully this will save you a few hours nonetheless. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |