-
Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!
SOLVED [Q]Installing an OS from within an OS?
- Thread starter Mario1
- Start date
OP
- Joined
- Nov 14, 2009
- Location
- Pleven, Bulgaria
- Thread Starter
- #22
Tried with safe mode, same thing.
Tried with another PSU, since that's the only component that runs on my old PC (from the new one), the PSU I tested with was a Corsair Builder 500w, same thing.
I guess we're out of options?
- Joined
- May 19, 2006
- Location
- Where angels carry savage weapons
Since you're getting the same error every time, I'm reluctant to believe that any other component in your system is faulty; usually hard drive issues cause such consistent stop codes.
That said, I suspect the reason for the BSOD's is due to XP not recognizing the SATA controller on your motherboard. This usually happens when a hard drive is either moved from one motherboard to another with differing controllers, or the operation mode is changed on the motherboard after Windows is installed.
I'm a bit surprised that interrupting the first reboot and bringing the installation back up on the bare-metal hardware didn't rectify this issue; however, I'm also going to suspect that installing XP entirely on the bare-metal box will yield the same results if you use the same installation media. BTW, what service pack does your XP installation media have on it?
My last-ditch suggestion to get it up by installing it within Windows is to use the Sysprep utility. I will warn you, this may be tricky and may be more effort than it's worth:
1) Completely Install XP onto the physical drive entirely within VMWare
2) Boot up the VM with XP; if it's not up to date with the latest service pack, download and install SP3 (you could also run Windows update to get all the other updates.
3) Create a new folder on the C: drive of XP called 'Sysprep'
4) Insert the XP installation media CD/ISO into the VM and copy the contents of D:\SUPPORT\TOOLS\DEPLOY.CAB into the Sysprep folder (the .CAB file is like a folder and it has stuff in it)
5) Run Sysprep.exe from the Sysprep folder
6) Acknowledge the warnings and Click the 'Factor' button and shutdown (DO NOT let the machine reboot in the VM)
7) Boot to the XP hard drive on the bare-metal machine and go through the Windows setup, product key, activation etc. again
Sysprep is a utility used in enterprise environments that basically will "reset" a Windows install's identity and low-level configurations while preserving certain settings and installed programs. This enables system administrators to build and deploy 'images' of a Windows install that is already compliant, for the most part, with the organizations requirements.
We're using this to clear out the hardware configurations created when XP was installed on the virtual hardware in hopes that it will re-detect and properly install the hardware on your bare-metal system. I seriously do not know if this will work, but it's just about the last thing I can think of right now.
That said, I suspect the reason for the BSOD's is due to XP not recognizing the SATA controller on your motherboard. This usually happens when a hard drive is either moved from one motherboard to another with differing controllers, or the operation mode is changed on the motherboard after Windows is installed.
I'm a bit surprised that interrupting the first reboot and bringing the installation back up on the bare-metal hardware didn't rectify this issue; however, I'm also going to suspect that installing XP entirely on the bare-metal box will yield the same results if you use the same installation media. BTW, what service pack does your XP installation media have on it?
My last-ditch suggestion to get it up by installing it within Windows is to use the Sysprep utility. I will warn you, this may be tricky and may be more effort than it's worth:
1) Completely Install XP onto the physical drive entirely within VMWare
2) Boot up the VM with XP; if it's not up to date with the latest service pack, download and install SP3 (you could also run Windows update to get all the other updates.
3) Create a new folder on the C: drive of XP called 'Sysprep'
4) Insert the XP installation media CD/ISO into the VM and copy the contents of D:\SUPPORT\TOOLS\DEPLOY.CAB into the Sysprep folder (the .CAB file is like a folder and it has stuff in it)
5) Run Sysprep.exe from the Sysprep folder
6) Acknowledge the warnings and Click the 'Factor' button and shutdown (DO NOT let the machine reboot in the VM)
7) Boot to the XP hard drive on the bare-metal machine and go through the Windows setup, product key, activation etc. again
Sysprep is a utility used in enterprise environments that basically will "reset" a Windows install's identity and low-level configurations while preserving certain settings and installed programs. This enables system administrators to build and deploy 'images' of a Windows install that is already compliant, for the most part, with the organizations requirements.
We're using this to clear out the hardware configurations created when XP was installed on the virtual hardware in hopes that it will re-detect and properly install the hardware on your bare-metal system. I seriously do not know if this will work, but it's just about the last thing I can think of right now.
OP
- Joined
- Nov 14, 2009
- Location
- Pleven, Bulgaria
- Thread Starter
- #24
Problem solved.
I moved my lazy *** to the laptop and made a bootable flash drive.
Long waiting, but it did the job.
Huge thanks to everyone who tried helping (TempliNocturnus, c627627 & etc) it really means a lot to me!
I believe the last tip TempliNocturnus gave would of probably worked so yeah, if anyone wants to do the same thing, than follow his guide.
If it doesn't work hit me up with a PM for a long and extremely boring tutorial on how to make it with PeToUSB, HP format tool, aprogramwhichnameIforgot 8 & etc..
I moved my lazy *** to the laptop and made a bootable flash drive.
Long waiting, but it did the job.
Huge thanks to everyone who tried helping (TempliNocturnus, c627627 & etc) it really means a lot to me!
I believe the last tip TempliNocturnus gave would of probably worked so yeah, if anyone wants to do the same thing, than follow his guide.
If it doesn't work hit me up with a PM for a long and extremely boring tutorial on how to make it with PeToUSB, HP format tool, aprogramwhichnameIforgot 8 & etc..
OP
- Joined
- Nov 14, 2009
- Location
- Pleven, Bulgaria
- Thread Starter
- #26
http://www.overclockers.com/forums/showthread.php?p=7059979#post7059979
Made a new thread on how to do it, hope it helps someone.
Made a new thread on how to do it, hope it helps someone.
This just makes me want to ask... Why? 7 isn't required for games any more than XP. XP is outdated, vulnerable and from day zero, ugly.
OP
- Joined
- Nov 14, 2009
- Location
- Pleven, Bulgaria
- Thread Starter
- #28
Because I was on a PC with 1GB RAM back when I made this topic.
On Windows 7 atm with 10, seems to run better than it used to on the old PC, haha.
Similar threads
