Ok guys, he doesn't like the virtual machine and wanted to dual boot instead. Xp installed to the partition no problem until it boots up in xp...I get the xp splash screen for a second and then the BSOD about windows closing to protect my system. Think it might be the chipset drivers? I didn't slipstream anything but the sata drivers into the install disc.
If it took the SATA drivers for XP to see the HD partitions for install then those worked and shouldn't be the problem. You full-formatted the partition?
Can you browse into XP from Win7 to see if you can copy the crash dump file from the root drive? If you zip up the file it's possible one of our analysts in Crashes forum can see the problem even though it's XP.
Other than that all I can recommend is an Repair Windows XP by Performing a Repair Install (Part 1 of 2)
Hi Gregg and thanks for answering. I't done for the night but I'm still trying from home to figure it out. Yes, the sata drivers took okm but I'm wondering if I needed to stream in the chipset drivers also. I get that same BSOD screan I got before when I didn't have the sata drivers slipstreamed only now it happens at first reboot. I'll try to copy the files tomorrows because I can access the partition from windows 7. I might have screwed up and formatted, I'm not sure. Prior to the install I had wiped the partition and formatted it NTFS.
Ok, I tried again. I slipstreamed every available xp driver from the MOB manufacturer into the XP disc. All drives have been converted to MBR and bios is set to legacy. The disc recognizes the SSD and both HDDs and all partitions. So I power down, unplug every drive except the one HDD that I want to install it on and boot up with the disc in. It boots to the install, format's the partition and loads the files just fine. then comes the first reboot and I get the windows XP splash screen like it's going to load to continue the install...then the blue screen comes up with the 0x0000007b code. I tried accessing the files on the partition from windows 7 after re-connecting everything and booting up in 7 but I can't find the crash dump file. Perhaps it's not written because XP isn't fully installed or perhaps I just don't know where to find it. I'm also now wondering if it's the RAM. I'm running 16GB of DDR3 G Skill 1600. Any help would be appreciated.
Last edited by jmicardo; 28 Nov 2012 at 20:47. Reason: spelling
Try removing all one stick of RAM to see if it makes a difference.
There are also reports that slipstreaming more drivers than needed to get installed can cause problems.
One experiment you can try is to install XP to it's native PC or an older one that accepts it, then move HD or an image to the newer hardware. From Win7 HD or partition run Paragon Virtualization Manager on the XP partition supplying the same drivers which will only be loaded as needed.
This is a much more advanced method that always works to adjust an OS bootable on other hardware to new hardware unless it reports it cannot find a key storage driver.
Gregg, first thanks so much for hanging with me on this. I am out in the sticks so my DL speeds are next to nothing. gonna be another 2 hrs for the download. I just want to understand what I need to do here. The HDD is SATA so it won't work in the native computer but I can get an image of the OS from the native computer. I can then transport that image to the SATA drive and restore it to the partition on the HDD in the Win 7 computer. Do I then run this program with the WIN OS and direct it to the partition with XP on it? What is it that it's going to tell me? Also, Since the files did copy already from the XP install disc onto the partition, can I just use this program to diagnose what the problem is without migrating the old OS? I'm not really all that savy so I'm hoping you can decode what I'm saying.
What the program does is adjust the drivers, HID and SID so that the OS will start on different hardware. It has the ability to process drivers you Manually provide and decide whether they are needed on that hardware pro actively whereas slipstreaming doesn't - it just fails if a driver interferes and of course doesn't have the ability to decide what is needed and what's not since no hardware is being queried.
I have moved many OS's to different hardware using Paragon Adaptive Restore and never had it fail. If it won't adjust it will even apply the image for you while adjusting it at the same time - the same thing expensive Acronis True Image with Univ. Restore does.
Ok Gregg, I think I'm set to do this first thing in the morning. I did a clean install on my own computer of XP plus just the SATA drivers that are needed on My friends computer. I then imaged a backup of it using Macrium reflect that we both use for our backups and will use it to restore the clean OS onto his hard drive. I'm unsure of what to do next. Can I run the Paragon VM in windows 7 and fix the xp OS or do I need to make a live cd to do it? If I have to make a live CD I am not sure how to do that. We both have AIK installed on our computers and I figure it has something to do with that but not sure how to do it. Any suggestion is appreciated.
Last edited by jmicardo; 29 Nov 2012 at 10:14.
I'm looking for SIW2's post showing how to make the Paragon LiveCD but it will probably be easier to just run the installed program from Win7. I did this awhile back for another PC's Win7 image I wanted to boot.
Then install EasyBCD (click Download - no Name or Email required) to add XP by name and drive letter, accepting it's boot files if offered.
Gregg, thanks so much for hanging in here. Did the imaging and ran paragon on the OS. It asked for drivers that I could not find on any of the hardware CD's containing drivers. It has to do with the LAN drivers for the PCI express, I found out that much. It was asking me to direct it to the window/win2000/Rtenic64.sys driver which doesn't exist in that folder. I found the Rtenic64.sys file in the XP window/XP folder and tried using that instead. Now it will boot from the HDD but still crashes immediately. Now that I do have an installed and bootable XP OS can you tell me how to get to the crash dump file? Thanks.
Last edited by jmicardo; 29 Nov 2012 at 19:24. Reason: spelling
Quote