I just managed to install a second HDD, and my OS sees it.
However, Partition Wizard does not let me initialize to MBR.
When I go to "Disc" on the top bar, everything in the drop down menu is grayed out. It is NTFS formatted, made Primary, Status is "none". I want to prepare it to install Windows XP. What do I have to do to make this work?
However, Partition Wizard does not let me initialize to MBR.
When I go to "Disc" on the top bar, everything in the drop down menu is grayed out. It is NTFS formatted, made Primary, Status is "none". I want to prepare it to install Windows XP. What do I have to do to make this work?
Forget using Partition Wizard and take a fast trip into the the Disk Management tool there to simply delete the present volume to see a new replacement using the add new volume wizard. The default option will be MBR automatically not the second GUID option you wouldn't use.
One possible problem for running into this would be a bad burn for a live cd for the PW program. This is one reason I have GParted on both live cds as well as written on a small bootable flash drive since the drive tool never seems to run into problems like this. That's another free option to consider besides going into the DM tool.
One possible problem for running into this would be a bad burn for a live cd for the PW program. This is one reason I have GParted on both live cds as well as written on a small bootable flash drive since the drive tool never seems to run into problems like this. That's another free option to consider besides going into the DM tool.
Thanks, Night Hawk! I did what you wrote with the Disk Management tool. It did not offer to initialize to MBR - is that automatic?
Is the drive ready now for XP installation?
Is the drive ready now for XP installation?
If you deleted the first and simply went ahead and created the new one the XP installer will format it for you during the custom install as well as place it's own mbr entries in. You should be set.
To avoid the need to repair the 7 boot information as mentioned in the Method Two for seeing XP installed after 7, Dual Boot Installation with Windows 7 and XP you may want to first unplug the 7 drive to prepare for a stand alone install of XP.
Once XP is on you can simply copy the boot files over to the root of the 7 host drive and edit the boot.ini file(copy of) there to point at the second drive as well as use EasyBCD to add a new boot entry into the 7 boot options. Instead of "rdisk(0)partition 1)" you would see "rdisk(1)partition 1" making that small change using NotePad and use the "save as all files" option not txt to see that taken care of.
You usually have to take ownership if you unable to uncheck the "read only" box on the copy however. Another tip is simply lowering the default 30 seconds for seeing the boot options screen displayed way down to only 5 seconds. Here I have lowered down to only 3. That will speed up the boot time quite a bit!
To avoid the need to repair the 7 boot information as mentioned in the Method Two for seeing XP installed after 7, Dual Boot Installation with Windows 7 and XP you may want to first unplug the 7 drive to prepare for a stand alone install of XP.
Once XP is on you can simply copy the boot files over to the root of the 7 host drive and edit the boot.ini file(copy of) there to point at the second drive as well as use EasyBCD to add a new boot entry into the 7 boot options. Instead of "rdisk(0)partition 1)" you would see "rdisk(1)partition 1" making that small change using NotePad and use the "save as all files" option not txt to see that taken care of.
You usually have to take ownership if you unable to uncheck the "read only" box on the copy however. Another tip is simply lowering the default 30 seconds for seeing the boot options screen displayed way down to only 5 seconds. Here I have lowered down to only 3. That will speed up the boot time quite a bit!
�� Quote: Originally Posted by Alsenor 
I just managed to install a second HDD, and my OS sees it.
However, Partition Wizard does not let me initialize to MBR.
When I go to "Disc" on the top bar, everything in the drop down menu is grayed out. It is NTFS formatted, made Primary, Status is "none". I want to prepare it to install Windows XP. What do I have to do to make this work?
However, Partition Wizard does not let me initialize to MBR.
When I go to "Disc" on the top bar, everything in the drop down menu is grayed out. It is NTFS formatted, made Primary, Status is "none". I want to prepare it to install Windows XP. What do I have to do to make this work?
You can try with Disk Management in Windows. Just open Computer Management in Administrative Tools, then select Disk Management. Note the middle-bottom area. All your storage device (including optical drives, USB flash drives, external HDDs) are listed here. Drive 0 is your main HDD that current Windows version is installed on. And drive 1 is your second HDD (if you have only 2 HDDs). Right-click on drive 1 and select "Initialize Disk", then follow on-screen instructions
. �� Quote: Originally Posted by Night Hawk If you deleted the first and simply went ahead and created the new one the XP installer will format it for you during the custom install as well as place it's own mbr entries in. You should be set.
Quote:
To avoid the need to repair the 7 boot information as mentioned in the Method Two for seeing XP installed after 7, Dual Boot Installation with Windows 7 and XP you may want to first unplug the 7 drive to prepare for a stand alone install of XP.
Once XP is on you can simply copy the boot files over to the root of the 7 host drive and edit the boot.ini file(copy of) there to point at the second drive as well as use EasyBCD to add a new boot entry into the 7 boot options. Instead of "rdisk(0)partition 1)" you would see "rdisk(1)partition 1" making that small change using NotePad and use the "save as all files" option not txt to see that taken care of.
You usually have to take ownership if you unable to uncheck the "read only" box on the copy however. Another tip is simply lowering the default 30 seconds for seeing the boot options screen displayed way down to only 5 seconds. Here I have lowered down to only 3. That will speed up the boot time quite a bit!
Once XP is on you can simply copy the boot files over to the root of the 7 host drive and edit the boot.ini file(copy of) there to point at the second drive as well as use EasyBCD to add a new boot entry into the 7 boot options. Instead of "rdisk(0)partition 1)" you would see "rdisk(1)partition 1" making that small change using NotePad and use the "save as all files" option not txt to see that taken care of.
You usually have to take ownership if you unable to uncheck the "read only" box on the copy however. Another tip is simply lowering the default 30 seconds for seeing the boot options screen displayed way down to only 5 seconds. Here I have lowered down to only 3. That will speed up the boot time quite a bit!
Here's a few screens that show how the add new volume wizard works. DiskPart was used at the time to clean the drive off followed by the trip into the DM.
I ran it again and wrote down that text on the blue screen:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this screen, restart your computer. If it happens again, do the following:
Check for viruses on your computer.
Remove newly installed hard drives or hard drive controllers.
Run CHKDSK /F to check for HD corruption, then restart.
My repeated tries made no difference, it keeps happening.
I have no viruses (AVG installed).
Should I really pull out my new drive, after it is recognized?
Should I run CHKDSK /F?
A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this screen, restart your computer. If it happens again, do the following:
Check for viruses on your computer.
Remove newly installed hard drives or hard drive controllers.
Run CHKDSK /F to check for HD corruption, then restart.
My repeated tries made no difference, it keeps happening.
I have no viruses (AVG installed).
Should I really pull out my new drive, after it is recognized?
Should I run CHKDSK /F?
Yes, my trip to the DM looked the same as your images. But I still can't install XP.
�� Quote: Originally Posted by Alsenor I ran it again and wrote down that text on the blue screen:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this screen, restart your computer. If it happens again, do the following:
Check for viruses on your computer.
Remove newly installed hard drives or hard drive controllers.
Run CHKDSK /F to check for HD corruption, then restart.
My repeated tries made no difference, it keeps happening.
I have no viruses (AVG installed).
Should I really pull out my new drive, after it is recognized?
Should I run CHKDSK /F?
A problem has been detected and Windows has been shut down to prevent damage to your computer.
If this is the first time you've seen this screen, restart your computer. If it happens again, do the following:
Check for viruses on your computer.
Remove newly installed hard drives or hard drive controllers.
Run CHKDSK /F to check for HD corruption, then restart.
My repeated tries made no difference, it keeps happening.
I have no viruses (AVG installed).
Should I really pull out my new drive, after it is recognized?
Should I run CHKDSK /F?
Now are you trying this with the partition created with the PW program or did you create a new primary before booting from the XP cd?While booted in 7 you can schedule another run another run of checkdisk with the /r switch but may want to start off with a second fresh primary once the problem partition is gone. Simply right click on the drive in the DM in order to see it deleted. You can then create a new primary with the wizard or when going to boot from the XP cd the next time allowing the XP installer to format it during the next attempt.
By first using the DM to see the new one created and formatted there you can try copying some files over to it to see if the drive itself has any defects like bad sectors however. That will save you some time as well.
�� Quote: Originally Posted by Night Hawk We just missed each other on the last post I see! Now are you trying this with the partition created with the PW program or did you create a new primary before booting from the XP cd?
Now are you trying this with the partition created with the PW program or did you create a new primary before booting from the XP cd?Quote:
While booted in 7 you can schedule another run another run of checkdisk with the /r switch but may want to start off with a second fresh primary once the problem partition is gone.
Simply right click on the drive in the DM in order to see it deleted.
Simply right click on the drive in the DM in order to see it deleted.
Quote:
You can then create a new primary with the wizard or when going to boot from the XP cd the next time allowing the XP installer to format it during the next attempt.
Quote:
By first using the DM to see the new one created and formatted there you can try copying some files over to it to see if the drive itself has any defects like bad sectors however. That will save you some time as well.
Formatted in DM and put a file in it. Result is the same blue screen text. But I did not delete the drive and run the wizard to create it new. Will do that now.
I would try that first to make sure the drive is working as it should. You may have to run a diagnostics tool from the manufacturer if you are having problems in order to determine if it needs to be returned or sent back. Dumping a likely corrupted partition table would be the first thought however if PW saw a glitch of some type when used.
Now I deleted the volume, ran the wizard to create it new, and formatted it. Result of XP installation was the same text on blue screen as before.
Currently I am running a surface test in PW.
OUCH! Something is certainly wrong somewhere!
With a fresh primary to work with XP as well as any other version should go on without problems unless you are looking at a hardware fault with the drive or possible memory problem now being realized.
A run of memtest or the option seen for that on the 7 disk as well as at startup would be a thought to rule out any possible problem there. I suspect you may have a drive problem of some type like bad sectrors or worse having defective read/write heads if you are not able to simply copy any files over to it once partitioned and formatted.
Unfortunately that sounds a bit too more likely then the first assumption of problems seen with PW since many here seem to have good results but couldn't be ruled out either until seeing this. The test results may show the worst of course.
With a fresh primary to work with XP as well as any other version should go on without problems unless you are looking at a hardware fault with the drive or possible memory problem now being realized.
A run of memtest or the option seen for that on the 7 disk as well as at startup would be a thought to rule out any possible problem there. I suspect you may have a drive problem of some type like bad sectrors or worse having defective read/write heads if you are not able to simply copy any files over to it once partitioned and formatted.
Unfortunately that sounds a bit too more likely then the first assumption of problems seen with PW since many here seem to have good results but couldn't be ruled out either until seeing this. The test results may show the worst of course.
�� Quote: Originally Posted by Night Hawk OUCH! Something is certainly wrong somewhere!
With a fresh primary to work with XP as well as any other version should go on without problems unless you are looking at a hardware fault with the drive or possible memory problem now being realized.
A run of memtest or the option seen for that on the 7 disk as well as at startup would be a thought to rule out any possible problem there. I suspect you may have a drive problem of some type like bad sectrors or worse having defective read/write heads if you are not able to simply copy any files over to it once partitioned and formatted.
Unfortunately that sounds a bit too more likely then the first assumption of problems seen with PW since many here seem to have good results but couldn't be ruled out either until seeing this. The test results may show the worst of course.
With a fresh primary to work with XP as well as any other version should go on without problems unless you are looking at a hardware fault with the drive or possible memory problem now being realized.
A run of memtest or the option seen for that on the 7 disk as well as at startup would be a thought to rule out any possible problem there. I suspect you may have a drive problem of some type like bad sectrors or worse having defective read/write heads if you are not able to simply copy any files over to it once partitioned and formatted.
Unfortunately that sounds a bit too more likely then the first assumption of problems seen with PW since many here seem to have good results but couldn't be ruled out either until seeing this. The test results may show the worst of course.
Night Hawk, I appreciate your help, but can't keep up with you! My 71-year-old eyes are ON FIRE! I will check in the morning for new ideas, thanks for now!
So now you know the heads are working as well as seeing a working partition you can access on the drive. The next steps would be inspecting the XP disk for any scratches or smudge marks from handling and if you have one onhand a drive lens cleaner.
One other thing I could ask here would be if you were attempting to install XP while booted in 7? That would immediately run into problems from the start. You have to be booted live from the XP disk itself in order to run the installer.
The only time you can be booted in 7 and run the older version's installer is when setting up a custom install on a virtual machine where the program(VBox, VM ware, etc.) requires bootable media be inserted in the optical drive.
Also to prevent seeing the 7 drive made bootable to XP only you would need to shutdown and simply unplug the host drive's data cable until XP is on and running. Then you would replug the data cable back in once powered down the second time. The guide will cover the rest as far as seeing it turned into a dual boot as far as copying the XP boot files over.
Missed each other's posts again! Take your time and go over things carefully.
One other thing I could ask here would be if you were attempting to install XP while booted in 7? That would immediately run into problems from the start. You have to be booted live from the XP disk itself in order to run the installer.
The only time you can be booted in 7 and run the older version's installer is when setting up a custom install on a virtual machine where the program(VBox, VM ware, etc.) requires bootable media be inserted in the optical drive.
Also to prevent seeing the 7 drive made bootable to XP only you would need to shutdown and simply unplug the host drive's data cable until XP is on and running. Then you would replug the data cable back in once powered down the second time. The guide will cover the rest as far as seeing it turned into a dual boot as far as copying the XP boot files over.
Missed each other's posts again! Take your time and go over things carefully.
�� Quote: Originally Posted by Night Hawk So now you know the heads are working as well as seeing a working partition you can access on the drive. The next steps would be inspecting the XP disk for any scratches or smudge marks from handling and if you have one onhand a drive lens cleaner.
Quote:
One other thing I could ask here would be if you were attempting to install XP while booted in 7? That would immediately run into problems from the start. You have to be booted live from the XP disk itself in order to run the installer.
Quote:
Also to prevent seeing the 7 drive made bootable to XP only you would need to shutdown and simply unplug the host drive's data cable until XP is on and running. Then you would replug the data cable back in once powered down the second time. The guide will cover the rest as far as seeing it turned into a dual boot as far as copying the XP boot files over.
And then give up on computers?
Quote:
Missed each other's posts again! Take your time and go over things carefully.
Anyone else up yet to guide me on during the day?
Update:
I tried to clean the XP installation CD first, but it still failed. Then I put on my analytical hat and tried another old XP installation CD, which did the same thing. Conclusion - its not the CD's fault! With regard to the read head of the CD drive, it reads all CDs fine otherwise. What next?
I tried to clean the XP installation CD first, but it still failed. Then I put on my analytical hat and tried another old XP installation CD, which did the same thing. Conclusion - its not the CD's fault! With regard to the read head of the CD drive, it reads all CDs fine otherwise. What next?
Your optical drive may be bad which is less likely and the board sounds too new to be requiring a sata driver disk for XP. But that is another possibility if the XP installer wasn't seeing the drive.
The idea of first unplugging the present 7 drive was simply to maintain the present master boot record entries for 7 on it. The guide explains that when custom installing XP after 7 is on will make 7 unbootable at first requiring the use of the 7 dvd repair tools>startup repair to correct that.
Out of curiosity I have to ask this one. Are you using pre-SP1 XP cds by chance? Those would have problems without the first service pack like breaking the 137gb barrier for the drive depending on how large the new one is.
Another thing of course would be the driver disk. Out of curiosity I have to ask another one here as to the make, model, and most importantly the type of drive the new is?
For an ide or Sata drive(possible driver disk need for onboard sata/Raid controllers) XP should go right on without a hitch. If the new drive was an SSD however that might be a problem. As a last resort however if nothing works to get XP on the alternative would be the XP Mode.
The idea of first unplugging the present 7 drive was simply to maintain the present master boot record entries for 7 on it. The guide explains that when custom installing XP after 7 is on will make 7 unbootable at first requiring the use of the 7 dvd repair tools>startup repair to correct that.
Out of curiosity I have to ask this one. Are you using pre-SP1 XP cds by chance? Those would have problems without the first service pack like breaking the 137gb barrier for the drive depending on how large the new one is.
Another thing of course would be the driver disk. Out of curiosity I have to ask another one here as to the make, model, and most importantly the type of drive the new is?
For an ide or Sata drive(possible driver disk need for onboard sata/Raid controllers) XP should go right on without a hitch. If the new drive was an SSD however that might be a problem. As a last resort however if nothing works to get XP on the alternative would be the XP Mode.
�� Quote: Originally Posted by Night Hawk The idea of first unplugging the present 7 drive was simply to maintain the present master boot record entries for 7 on it. The guide explains that when custom installing XP after 7 is on will make 7 unbootable at first requiring the use of the 7 dvd repair tools>startup repair to correct that.
Quote:
Out of curiosity I have to ask this one. Are you using pre-SP1 XP cds by chance? Those would have problems without the first service pack like breaking the 137gb barrier for the drive depending on how large the new one is.
My new drive is a WD 500 GB.
Quote:
Another thing of course would be the driver disk. Out of curiosity I have to ask another one here as to the make, model, and most importantly the type of drive the new is?
CD-ROM Drive
hp DVD A DH16AAL SCSI CdRom Device
Model Number hp DVD A DH16AAL
Drive Serial Number 3B9944001287
Quote:
For an ide or Sata drive(possible driver disk need for onboard sata/Raid controllers) XP should go right on without a hitch. If the new drive was an SSD however that might be a problem. As a last resort however if nothing works to get XP on the alternative would be the XP Mode.
For adding a new boot entry into the 7 boot loader the guide posted earlier covers all this. Unplugging the 7 drive does two things for you to make like a little easier. Note the boot order as far as hard drives will be changed by the unplugging and replug of the 7 later.
The first thing is seeing the 7 drive remain bootable for 7 as is without the need for the startup repair or use of the command prompt option while booted with the 7 dvd later. That will save you some repair steps after XP is installed and suddenly you find 7 won't start? due the XP installer replacing that 7 entries with those needed for XP.
You would need to copy the boot files over however doing that way and edit the boot.ini to point at the second drive. Once you go into the Windows Explorer menu bar>Tools>Folder options>View tab you would uncheck the "extensions for known file types" and "hidden protected systems files" item to have the boot files visible to copy over to the root of the 7 drive since XP would be isolated at first.
The advantage? Each drive can be booted independently of each other rather then counting solely on the present 7 host/boot drive if you later had to replace or decided to upgrade that.
The second item is seeing the new drive XP is going onto made bootable on it's own when the 7 drive isn't present. You can still add XP into the 7 boot loader easy enough however. The same method for a dual boot of Vista with XP applies to an XP/7 dual boot setup.
You could be having a problem of one type with the optical drive itself. One idea would be making a temp folder on the second drive and simply copy + pasting a large amount of files into the temp folder to watch how things go from a disk in the drive.
If copying a large amount of files is a problem while the optical drive maybe good the new cable you added in recently could be at fault. installing IDE in new tower.
As for the Home Premium not supporting the Virtual PC from running there the alternative for the XP Mode is the WM Lite Workstation for the XP Mode. Just of late I had been running an old Socket A build without any virtualization support being too old but still saw the XP Mode running with the alternate program.
VMLite Workstation/VMLite XP Mode v3.2.6 binaries (x86/amd64)
What was interesting about the first install of that there still saw the integrated components supported. That was still on the Ultimate while another tryout with the Home Premium is a thought since I am just finishing a new build that will run that edition. But the VM ware would still run on HP as well as Ultimate.
The first thing is seeing the 7 drive remain bootable for 7 as is without the need for the startup repair or use of the command prompt option while booted with the 7 dvd later. That will save you some repair steps after XP is installed and suddenly you find 7 won't start? due the XP installer replacing that 7 entries with those needed for XP.
You would need to copy the boot files over however doing that way and edit the boot.ini to point at the second drive. Once you go into the Windows Explorer menu bar>Tools>Folder options>View tab you would uncheck the "extensions for known file types" and "hidden protected systems files" item to have the boot files visible to copy over to the root of the 7 drive since XP would be isolated at first.
The advantage? Each drive can be booted independently of each other rather then counting solely on the present 7 host/boot drive if you later had to replace or decided to upgrade that.
The second item is seeing the new drive XP is going onto made bootable on it's own when the 7 drive isn't present. You can still add XP into the 7 boot loader easy enough however. The same method for a dual boot of Vista with XP applies to an XP/7 dual boot setup.
You could be having a problem of one type with the optical drive itself. One idea would be making a temp folder on the second drive and simply copy + pasting a large amount of files into the temp folder to watch how things go from a disk in the drive.
If copying a large amount of files is a problem while the optical drive maybe good the new cable you added in recently could be at fault. installing IDE in new tower.
As for the Home Premium not supporting the Virtual PC from running there the alternative for the XP Mode is the WM Lite Workstation for the XP Mode. Just of late I had been running an old Socket A build without any virtualization support being too old but still saw the XP Mode running with the alternate program.
VMLite Workstation/VMLite XP Mode v3.2.6 binaries (x86/amd64)
What was interesting about the first install of that there still saw the integrated components supported. That was still on the Ultimate while another tryout with the Home Premium is a thought since I am just finishing a new build that will run that edition. But the VM ware would still run on HP as well as Ultimate.
�� Quote: Originally Posted by Night Hawk For adding a new boot entry into the 7 boot loader the guide posted earlier covers all this. Unplugging the 7 drive does two things for you to make like a little easier. Note the boot order as far as hard drives will be changed by the unplugging and replug of the 7 later.
1. Unplug the data connector from drive 0 (W7).
2. Reboot with XP installation CD in CD drive.
3. Reconnect drive 0 with W7.
4. Pray.
5. reboot and add a new boot entry into the 7 boot loader
Question: when you say the boot order will be changed - it will boot into W7, so I can add the new boot entry into the 7 boot loader?
If you install XP fresh without the 7 drive plugged in that will set up the drive as a stand alone install rather then placing the XP boot files on the 7 host drive and replace the 7 boot entries in the master boot record(mbr). For a short time the XP drive will be the default hard drive.
Once the XP installation is complete and you know that is running normal without problems you can then shutdown and replug the 7 drive back in. This will prevent any changes to the 7 boot information. But you will then need to go into the bios setup when powering up again to see that reset or insure it is set as the first hard drive in the list of drives to insure it is the default in order to boot into 7.
Basically that's a fast trip to see that done in there and then simply choose the "exit and save" option if pressing the F10 doesn't save any change right away. From there once back in 7 you can copy the needed XP boot files over to the root of C on the W7 host drive now made the default boot device if you follow me so far.
The next step as you will also see in the guide pointed to earlier is simply copying the XP boot files as shown in the attached image being the boot.ini file mentioned before and a few others being indicated in the screen below. NTLDR in lower case is required as well as the NTDETECT.COM, IO.SYS, MSDOS.SYS files while the CONFIG.SYS is simply mixed in there and won't do anything.
Once those are copied over you will need to download and install the latest 2.0.2 version of EasyBCD available free at Download EasyBCD 2.0.2 - NeoSmart Technologies
Before you can add the new entry for XP however you first have to uncheck the "read only" box in the properties screen for the boot.ini file in order to be able to edit the copy you then have on the 7 drive. A fast edit when opened by a double click bringing up the NotePad window will allow you make a simple change to the "rddisk(0)partition 1" to "rdisk(1)partition 1) since XP is now on the second not first hard drive.
Once that change is seen to simply drop down the File menu and save as "all files" not txt for the NotePad default in order to see the change overwrite the copy of the file now present on the 7 drive. You don't want it saved in text file format but still see the .ini extension at the end.
The EasyBCD options are easy to follow as for adding the new entry in for XP. First however a quick trip into the 7 Disk Management to see what the drive letter is and even change it to another is seen to since that will be the drive letter selected when going to add the new boot entry into the 7 BCD store(boot loader info).
The things to remember of course if you are able to see a working install of XP going you first shutdown to replug the 7 back in and check to see which drive is set as default in the bios. If you install XP without unplugging the 7 drive 7 won't boot later since the XP installer would have replaced the 7 mbr entries requiring you boot up with the 7 dvd and use the startup repair or command prompt option to enter the "Fixmbr" and "Fixboot" commands until seeing the "boot sector successfully written" confirmation.
The unplug first step will see the XP drive made bootable while leaving the 7 drive plugged through all this would see the XP boot files placed on the 7 drive only plus the need for repairing the 7 boot problem you would see. The guide however is what to refer to there if you have any problems since that covers each step except for isolation of the 7 drive when XP is being installed.
Once the XP installation is complete and you know that is running normal without problems you can then shutdown and replug the 7 drive back in. This will prevent any changes to the 7 boot information. But you will then need to go into the bios setup when powering up again to see that reset or insure it is set as the first hard drive in the list of drives to insure it is the default in order to boot into 7.
Basically that's a fast trip to see that done in there and then simply choose the "exit and save" option if pressing the F10 doesn't save any change right away. From there once back in 7 you can copy the needed XP boot files over to the root of C on the W7 host drive now made the default boot device if you follow me so far.
The next step as you will also see in the guide pointed to earlier is simply copying the XP boot files as shown in the attached image being the boot.ini file mentioned before and a few others being indicated in the screen below. NTLDR in lower case is required as well as the NTDETECT.COM, IO.SYS, MSDOS.SYS files while the CONFIG.SYS is simply mixed in there and won't do anything.
Once those are copied over you will need to download and install the latest 2.0.2 version of EasyBCD available free at Download EasyBCD 2.0.2 - NeoSmart Technologies
Before you can add the new entry for XP however you first have to uncheck the "read only" box in the properties screen for the boot.ini file in order to be able to edit the copy you then have on the 7 drive. A fast edit when opened by a double click bringing up the NotePad window will allow you make a simple change to the "rddisk(0)partition 1" to "rdisk(1)partition 1) since XP is now on the second not first hard drive.
Once that change is seen to simply drop down the File menu and save as "all files" not txt for the NotePad default in order to see the change overwrite the copy of the file now present on the 7 drive. You don't want it saved in text file format but still see the .ini extension at the end.
The EasyBCD options are easy to follow as for adding the new entry in for XP. First however a quick trip into the 7 Disk Management to see what the drive letter is and even change it to another is seen to since that will be the drive letter selected when going to add the new boot entry into the 7 BCD store(boot loader info).
The things to remember of course if you are able to see a working install of XP going you first shutdown to replug the 7 back in and check to see which drive is set as default in the bios. If you install XP without unplugging the 7 drive 7 won't boot later since the XP installer would have replaced the 7 mbr entries requiring you boot up with the 7 dvd and use the startup repair or command prompt option to enter the "Fixmbr" and "Fixboot" commands until seeing the "boot sector successfully written" confirmation.
The unplug first step will see the XP drive made bootable while leaving the 7 drive plugged through all this would see the XP boot files placed on the 7 drive only plus the need for repairing the 7 boot problem you would see. The guide however is what to refer to there if you have any problems since that covers each step except for isolation of the 7 drive when XP is being installed.
Ok, I will start the process and install XP (the computer gods willing!).
Then I will reconnect the 7 drive and try to follow your instructions to get those files in there. I suppose I can always disconnect the XP drive again if for some reason it doesn't boot to the 7 drive. Wish me luck!
).Then I will reconnect the 7 drive and try to follow your instructions to get those files in there. I suppose I can always disconnect the XP drive again if for some reason it doesn't boot to the 7 drive. Wish me luck!
Well once XP is on hopefully as you were having problems with the installation part you wouldn't want to replug and then unplug the 7 drive once XP is running but set the 7 drive to be the default host/boot drive once again in order to be able to add the XP entry in. That has to be the default drive in order to work.
That's a quick browse in the bios setup there where once you find the "hard drive" item and highlight it you simply hit the enter button to bring up the list of drives screen. The plus and minus keys over on the NumPad are used to move a particular drive to the top of the list setting that as the default. From there you simply exist the bios with the save option.
For now take your time and go over each step as well as the guide. Method Two is what you want to read carefully. Dual Boot Installation with Windows 7 and XP
That's a quick browse in the bios setup there where once you find the "hard drive" item and highlight it you simply hit the enter button to bring up the list of drives screen. The plus and minus keys over on the NumPad are used to move a particular drive to the top of the list setting that as the default. From there you simply exist the bios with the save option.
For now take your time and go over each step as well as the guide. Method Two is what you want to read carefully. Dual Boot Installation with Windows 7 and XP
I unplugged the data connector of the 7 drive, and rebooted with the XP CD in the CD drive.
Sorry to tell you this, but the result is still the same error msg on blue screen.
I tried 3 different XP installation CDs to eliminate the possibility of a bad CD. They all went through the file loading process, but when they got to the "Starting Windows" point the same error screen came up and I had to cut the power to shut down.
To get access to this forum I connected the 7 drive again.
What now?
Sorry to tell you this, but the result is still the same error msg on blue screen.
I tried 3 different XP installation CDs to eliminate the possibility of a bad CD. They all went through the file loading process, but when they got to the "Starting Windows" point the same error screen came up and I had to cut the power to shut down.
To get access to this forum I connected the 7 drive again.
What now?
Now with each disk did you see all setup files copied over and then the automatic restart? Remember you left the optical set as the first in the boot order rather then calling up the boot device menu for a one time session while leaving the hard drive set as first and default.
I'm trying to rule various possible causes for why you continue to see the same problem. As you have noted before you tried other disks ruling out the XP cd as one item.
Apparently one thing is off since the new drive is known to be good while the optical drive also appears to be copying all the setup files over without problem as well. Since the XP installer on each clearly has the drive present you are not in need of a driver disk for sata controllers apparently.Other then the optical drive being a little flaky and missing a file or two "something" not found yet seems to be preventing a working XP install there.
If you system came with the 6gb of memory as listed in the specifications a bad dimm would be a cause for the blue screens during each attempt. The last thought would be removing all but one dimm for a last attempt as well as running memtest on each dimm by itself to be able to rule any bad ram out entirely.
If you ran memtest as advised earlier in the thread but not long enough to repeat the series of stress you may not have run it long enough to reveal any faults. This would be one item to followup on just in case you need to replace one or two of them.
In the event the memory is found defect free your options for XP left would be the XP Mode run on the VM Lite Workstation or a custom install of XP on VHD running VIrtual Box and dedicating the new drive for storage and backup purposes. I did that here as well while trying out the XP Mode on the VM ware and on VBox there as well as other OSs and never ran into any installation problem except for 3.1, 95, 98SE made it once!
It used to be the chipsets not allowing XP's installer to see sata drives where a fluppy had to have sata controller drivers that would be a stumbling block for the most part. Apparently something new is preventing a normal install if nothing else is found bad or not set correctly.
I'm trying to rule various possible causes for why you continue to see the same problem. As you have noted before you tried other disks ruling out the XP cd as one item.
Apparently one thing is off since the new drive is known to be good while the optical drive also appears to be copying all the setup files over without problem as well. Since the XP installer on each clearly has the drive present you are not in need of a driver disk for sata controllers apparently.Other then the optical drive being a little flaky and missing a file or two "something" not found yet seems to be preventing a working XP install there.
If you system came with the 6gb of memory as listed in the specifications a bad dimm would be a cause for the blue screens during each attempt. The last thought would be removing all but one dimm for a last attempt as well as running memtest on each dimm by itself to be able to rule any bad ram out entirely.
If you ran memtest as advised earlier in the thread but not long enough to repeat the series of stress you may not have run it long enough to reveal any faults. This would be one item to followup on just in case you need to replace one or two of them.
In the event the memory is found defect free your options for XP left would be the XP Mode run on the VM Lite Workstation or a custom install of XP on VHD running VIrtual Box and dedicating the new drive for storage and backup purposes. I did that here as well while trying out the XP Mode on the VM ware and on VBox there as well as other OSs and never ran into any installation problem except for 3.1, 95, 98SE made it once!
It used to be the chipsets not allowing XP's installer to see sata drives where a fluppy had to have sata controller drivers that would be a stumbling block for the most part. Apparently something new is preventing a normal install if nothing else is found bad or not set correctly.
�� Quote: Originally Posted by Night Hawk Now with each disk did you see all setup files copied over and then the automatic restart? Remember you left the optical set as the first in the boot order rather then calling up the boot device menu for a one time session while leaving the hard drive set as first and default.
Quote:
If you system came with the 6gb of memory as listed in the specifications a bad dimm would be a cause for the blue screens during each attempt. The last thought would be removing all but one dimm for a last attempt as well as running memtest on each dimm by itself to be able to rule any bad ram out entirely.
Quote:
If you ran memtest as advised earlier in the thread but not long enough to repeat the series of stress you may not have run it long enough to reveal any faults. This would be one item to followup on just in case you need to replace one or two of them.
Mine was part of the HP proprietory support application health check that came installed on the PC.
Should I do it differently, and how?
Quote:
In the event the memory is found defect free your options for XP left would be the XP Mode run on the VM Lite Workstation or a custom install of XP on VHD running VIrtual Box and dedicating the new drive for storage and backup purposes.
Quote:
It used to be the chipsets not allowing XP's installer to see sata drives where a fluppy had to have sata controller drivers that would be a stumbling block for the most part. Apparently something new is preventing a normal install if nothing else is found bad or not set correctly.
As for memtest that's a free Linux memory tester now seen as an option in the 7 startup options! It's easy to start up there or download a live cd image. But it sounds like you have that ruled out as far as defects while the overall hardware configuration could be another possible block for XP.
The XP Mode wouldn't do for running old games while many old pc games are fairing quite well on the 64bit 7 here! Have you tried installing it on 7 using the compatibility mode? Are you running the 32bit or 64bit 7 there?
Surprisingly one older XP game that would not go on Vista under any circumstance was suddenly found to install on the 32bit 7 RC last year without issue while looking over what would go on 7. Unfortunately I still have to find the sleeve with the game's product key to try it out again on the 64bit retail.
The XP Mode wouldn't do for running old games while many old pc games are fairing quite well on the 64bit 7 here! Have you tried installing it on 7 using the compatibility mode? Are you running the 32bit or 64bit 7 there?
Surprisingly one older XP game that would not go on Vista under any circumstance was suddenly found to install on the 32bit 7 RC last year without issue while looking over what would go on 7. Unfortunately I still have to find the sleeve with the game's product key to try it out again on the 64bit retail.
�� Quote: Originally Posted by Night Hawk As for memtest that's a free Linux memory tester now seen as an option in the 7 startup options! It's easy to start up there or download a live cd image. But it sounds like you have that ruled out as far as defects while the overall hardware configuration could be another possible block for XP.
The XP Mode wouldn't do for running old games while many old pc games are fairing quite well on the 64bit 7 here! Have you tried installing it on 7 using the compatibility mode? Are you running the 32bit or 64bit 7 there?
The XP Mode wouldn't do for running old games while many old pc games are fairing quite well on the 64bit 7 here! Have you tried installing it on 7 using the compatibility mode? Are you running the 32bit or 64bit 7 there?
However, that still leaves the mystery unsolved of having a new WD 500GB SATA drive installed properly, and not accepting an OS!
I readily agree on the "Unsolved Mystery" part having WD 500gb models on the last build and multi as well as dual booted XP along with Vista and the 7 betas and RCs!
This one is a kind of stumper since the only last item in the chain would be a flaky optical drive that works part of the time while booted in Windows but fails to copy fully the setup files or even boot live from disk.
On the last build here one drive was replaced when suddenly hearing grinding sounds. You would have to shutdown completely and power up again in order to boot from any disk with the old drive there.
The new HD on the other hand seems to be ok without any bad sectors found as far as you know. Files copied and pasted manually went right on for you ruling that out.
As for the 64bit 7 and seeing an immediate compatibility issue the only that may work would be to right click on the setup or installer.exe file when browsing to the game's disk in an explorer. On the properties screen you will find the compatibility tab there and set it to XP with SP2 as well as check off the run as admin box. If the game installs but won't run you then go into the main folder and do the same for the game's main executable there too.
In some cases simply choosing the "troubleshoot compatibility" item in the right click menu will troubleshoot installation problems while others require the 32bit not 64bit 7 where you would be stuck. The Metal of Honor: Allied Assault title was one found to go on the 32bit 7 but not on Vista with any option. That was one written for XP only not older versions like 98 or 2000.
For games 9x-XP compatible on the other hand they go right onto the 64bit 7 with ease and seem to run just as they did on the previous versions being more let's say "cross version compatible" and see excellent 32bit emulation. Funny how all that goes!
As for the optical drive trying a different data cable or even swapping that out for another would see if XP suddenly went on without any fuss. Even brand new drives can be a problem at times where that appears to be the last link in the chain as to why XP is not seeing a full working install.
If you had a different version you could test the drive itself keeping the 7 drive out of the loop by trying a temp install of Vista or 7 if you had another OS disk available for a fast look. If that also saw problems then you would know it wasn't limited to XP alone.
That would be another "food for thought" idea to run past you. With 3 separate XP disks however I would still tend to lean at the optical drive as far as a possible hardware concern however.
This one is a kind of stumper since the only last item in the chain would be a flaky optical drive that works part of the time while booted in Windows but fails to copy fully the setup files or even boot live from disk.
On the last build here one drive was replaced when suddenly hearing grinding sounds. You would have to shutdown completely and power up again in order to boot from any disk with the old drive there.
The new HD on the other hand seems to be ok without any bad sectors found as far as you know. Files copied and pasted manually went right on for you ruling that out.
As for the 64bit 7 and seeing an immediate compatibility issue the only that may work would be to right click on the setup or installer.exe file when browsing to the game's disk in an explorer. On the properties screen you will find the compatibility tab there and set it to XP with SP2 as well as check off the run as admin box. If the game installs but won't run you then go into the main folder and do the same for the game's main executable there too.
In some cases simply choosing the "troubleshoot compatibility" item in the right click menu will troubleshoot installation problems while others require the 32bit not 64bit 7 where you would be stuck. The Metal of Honor: Allied Assault title was one found to go on the 32bit 7 but not on Vista with any option. That was one written for XP only not older versions like 98 or 2000.
For games 9x-XP compatible on the other hand they go right onto the 64bit 7 with ease and seem to run just as they did on the previous versions being more let's say "cross version compatible" and see excellent 32bit emulation. Funny how all that goes!
As for the optical drive trying a different data cable or even swapping that out for another would see if XP suddenly went on without any fuss. Even brand new drives can be a problem at times where that appears to be the last link in the chain as to why XP is not seeing a full working install.
If you had a different version you could test the drive itself keeping the 7 drive out of the loop by trying a temp install of Vista or 7 if you had another OS disk available for a fast look. If that also saw problems then you would know it wasn't limited to XP alone.
That would be another "food for thought" idea to run past you. With 3 separate XP disks however I would still tend to lean at the optical drive as far as a possible hardware concern however.
�� Quote: Originally Posted by Night Hawk If you had a different version you could test the drive itself keeping the 7 drive out of the loop by trying a temp install of Vista or 7 if you had another OS disk available for a fast look. If that also saw problems then you would know it wasn't limited to XP alone.
That would be another "food for thought" idea to run past you. With 3 separate XP disks however I would still tend to lean at the optical drive as far as a possible hardware concern however.
That would be another "food for thought" idea to run past you. With 3 separate XP disks however I would still tend to lean at the optical drive as far as a possible hardware concern however.
Can you believe:
I am working in W7 Ultimate on my new second drive. I had an old CD and it installed fine. Not at first, but after I figured out to hit F10 and get into the BIOS, where I changed the boot priority to the HD group. Then it installed without a hitch. All I need to know now is how to get it to work in XP mode!
I am working in W7 Ultimate on my new second drive. I had an old CD and it installed fine. Not at first, but after I figured out to hit F10 and get into the BIOS, where I changed the boot priority to the HD group. Then it installed without a hitch. All I need to know now is how to get it to work in XP mode!
As far as BattleGroup you likely won't get anywhere trying to install the game on the XP Mode since that is limited to a form of virtual video memory without direct access to the video card itself as well as not seeing any Direct X or OpenGL support. The XP Mode was developed mainly for businesses to be able to upgrade to 7 from XP but still run many of their present desktop softwares.
The one item I didn't get to on the last post would seem to suggest the need for a sata controller driver disk in order to get XP to install instead. The install success seeing 7 go on the new drive now shows how Vista and 7 have generic controller drivers to work with while the older version sadly lacked those considering when XP was first seen.
This also rules out the optical drive however since 7 went right on. That brings us to the end of the chain now that the last link is found good. The old version simply needs some help being installed!
You may have to contact the HP support to ask why XP won't install on that particular model as a second OS when you have a second drive added in for just that since everything else has been ruled out so far.
The one item I didn't get to on the last post would seem to suggest the need for a sata controller driver disk in order to get XP to install instead. The install success seeing 7 go on the new drive now shows how Vista and 7 have generic controller drivers to work with while the older version sadly lacked those considering when XP was first seen.
This also rules out the optical drive however since 7 went right on. That brings us to the end of the chain now that the last link is found good. The old version simply needs some help being installed!
You may have to contact the HP support to ask why XP won't install on that particular model as a second OS when you have a second drive added in for just that since everything else has been ruled out so far.
�� Quote: Originally Posted by Night Hawk As far as BattleGroup you likely won't get anywhere trying to install the game on the XP Mode since that is limited to a form of virtual video memory without direct access to the video card itself as well as not seeing any Direct X or OpenGL support. The XP Mode was developed mainly for businesses to be able to upgrade to 7 from XP but still run many of their present desktop softwares.
The one item I didn't get to on the last post would seem to suggest the need for a sata controller driver disk in order to get XP to install instead. The install success seeing 7 go on the new drive now shows how Vista and 7 have generic controller drivers to work with while the older version sadly lacked those considering when XP was first seen.
The one item I didn't get to on the last post would seem to suggest the need for a sata controller driver disk in order to get XP to install instead. The install success seeing 7 go on the new drive now shows how Vista and 7 have generic controller drivers to work with while the older version sadly lacked those considering when XP was first seen.
Quote:
This also rules out the optical drive however since 7 went right on. That brings us to the end of the chain now that the last link is found good. The old version simply needs some help being installed!.
Quote:
You may have to contact the HP support to ask why XP won't install on that particular model as a second OS when you have a second drive added in for just that since everything else has been ruled out so far.
I just ran a quick install attempt to see that text when I load the old XP CD. It says "press F6 if you need to install a third party RAID or SCSI driver". That is probably what is missing? Where do we get that from?
Something maybe as simple as the need for sata drivers is preventling XP but not 7 from going on. I know the 64bit Vista was the one that saw problems originally when having more then 2-3gb of memory installed where you would simply install only 2gb until the previous version was running.
The XP installer may be where the problem is actually stemming from however. Besides the HP support site lacking anything in their FAQs section as usual about custom install of any OS, HP Pavilion p6300 Desktop PC series*-* Windows XP - HP Business Support Center
we back track in one search when looking up this particular model series to discover something found about another which could be the source of the problem. How-to Install Windows Xp on HP Pavilion dv6236EA
According to that disabling the Native ide mode for sata drives allowed XP to install while previous attempts failed while the mode was enabled. I know Gigabyte boards see this setting in the bios while Asus boards don't. The Foxconn board in yours however may also see this option usually in the "Integrated Peripherals"or "Onboard" sections depending on the bios used.
Again we just missed each other! For all drver updates including a set for creating a driver disk of some type(floppy, cd) you need to go to the HP support site itself. Unfortunately you may still need to contact HP to see if they have XP drivers for that model to start with since the search comes up with Vista and 7 only at present!
You can see that bad news for the too new of model as I suspected by clicking on the "Software & Driver Downloads" link on the page for this model. http://h10025.www1.hp.com/ewfrf/wc/p...&cc=us&lang=en
Apparently your only place now for XP support if found would be at Foxconn and to find out if they list that particular model board or use the System Info for Windows tool, http://www.gtopala.com/ to see just model board that is.
The XP installer may be where the problem is actually stemming from however. Besides the HP support site lacking anything in their FAQs section as usual about custom install of any OS, HP Pavilion p6300 Desktop PC series*-* Windows XP - HP Business Support Center
we back track in one search when looking up this particular model series to discover something found about another which could be the source of the problem. How-to Install Windows Xp on HP Pavilion dv6236EA
According to that disabling the Native ide mode for sata drives allowed XP to install while previous attempts failed while the mode was enabled. I know Gigabyte boards see this setting in the bios while Asus boards don't. The Foxconn board in yours however may also see this option usually in the "Integrated Peripherals"or "Onboard" sections depending on the bios used.
Again we just missed each other! For all drver updates including a set for creating a driver disk of some type(floppy, cd) you need to go to the HP support site itself. Unfortunately you may still need to contact HP to see if they have XP drivers for that model to start with since the search comes up with Vista and 7 only at present!
You can see that bad news for the too new of model as I suspected by clicking on the "Software & Driver Downloads" link on the page for this model. http://h10025.www1.hp.com/ewfrf/wc/p...&cc=us&lang=en
Apparently your only place now for XP support if found would be at Foxconn and to find out if they list that particular model board or use the System Info for Windows tool, http://www.gtopala.com/ to see just model board that is.
�� Quote: Originally Posted by Night Hawk we back track in one search when looking up this particular model series to discover something found about another which could be the source of the problem. How-to Install Windows Xp on HP Pavilion dv6236EA
According to that disabling the Native ide mode for sata drives allowed XP to install while previous attempts failed while the mode was enabled. I know Gigabyte boards see this setting in the bios while Asus boards don't. The Foxconn board in yours however may also see this option usually in the "Integrated Peripherals"or "Onboard" sections depending on the bios used.
According to that disabling the Native ide mode for sata drives allowed XP to install while previous attempts failed while the mode was enabled. I know Gigabyte boards see this setting in the bios while Asus boards don't. The Foxconn board in yours however may also see this option usually in the "Integrated Peripherals"or "Onboard" sections depending on the bios used.
Guess what!
I went into the BIOS and found a submenu under SATA II with 3 options: IDE, AHCI, and RAID. I enabled IDE, loaded the XP CD, and hooorray, it installed!
Turned off PC, and rebooted right into XP again.
I was elated, reconnected the 7 drive, went back into the BIOS to switch back to AHCI, to see whether I could boot into W7 as well. No such luck! "The boot selection failed because a required device is inaccessible".
Now I can't boot into either drive!
When I disconnect the 7 drive and switch the BIOS back to IDE, I get the "NTLDR is missing" notice on booting!
How come it wasn't missing before?
And how do I get those 2 drives to boot, or at least one of them for now?
I went into the BIOS and found a submenu under SATA II with 3 options: IDE, AHCI, and RAID. I enabled IDE, loaded the XP CD, and hooorray, it installed!
Turned off PC, and rebooted right into XP again.
I was elated, reconnected the 7 drive, went back into the BIOS to switch back to AHCI, to see whether I could boot into W7 as well. No such luck! "The boot selection failed because a required device is inaccessible".
Now I can't boot into either drive!
When I disconnect the 7 drive and switch the BIOS back to IDE, I get the "NTLDR is missing" notice on booting!
How come it wasn't missing before?
And how do I get those 2 drives to boot, or at least one of them for now?
Leave it in ide mode for the time being and boot up from the recovery disk if you were provided with or burned one to use the startup repair tool. First make sure the 7 drive is the default drive however.
If you don't a set of recovery like most new systems won't and didn't use the option seen in 7 to create a repair cd you can download an ISO image from Neosmart and use a program that supports burning ISO images to disk. Since 7 is temporarily out of commission the system you are on or another will need a burning program unless 7 is also on for the support now seen.
The 64bit as well as 32bit repair tool cd images are available for download at Download Windows 7 System Recovery Discs — The NeoSmart Files
Once you have the image burned onto a cd-r you boot up from that and run the startup repair tool. You might have to do that more then once. The command prompt prompt option is also available for the "bootrec /fixmbr" and "bootrec /fixboot" commands while the startup repair tool should clean that up for you.
The bios can be reset to the defaults while the Native ide mode should have already been the default setting. But I suspect HP had it setup for the AHCI mode to begin with. But depending on how you found the settings you simply only have to go back in and disable the ide mode to see 7 going again. The repair tools cd however is still good to have onhand in case something trashes the boot sector or something else goes wrong where the repair tools can help.
Nothing to panic about with the XP "missing ntldr" error there however. That one goes back to 2000 as well as an annoyance seen often with XP! A few simple tips for this are seen at NTLDR is Missing Error Resolution
Did you set the optical drive as first in the boot order this time around by chance? An empty drive is one thing pointed to there if you removed the XP cd as soon as the install went well.
If you don't a set of recovery like most new systems won't and didn't use the option seen in 7 to create a repair cd you can download an ISO image from Neosmart and use a program that supports burning ISO images to disk. Since 7 is temporarily out of commission the system you are on or another will need a burning program unless 7 is also on for the support now seen.
The 64bit as well as 32bit repair tool cd images are available for download at Download Windows 7 System Recovery Discs — The NeoSmart Files
Once you have the image burned onto a cd-r you boot up from that and run the startup repair tool. You might have to do that more then once. The command prompt prompt option is also available for the "bootrec /fixmbr" and "bootrec /fixboot" commands while the startup repair tool should clean that up for you.
The bios can be reset to the defaults while the Native ide mode should have already been the default setting. But I suspect HP had it setup for the AHCI mode to begin with. But depending on how you found the settings you simply only have to go back in and disable the ide mode to see 7 going again. The repair tools cd however is still good to have onhand in case something trashes the boot sector or something else goes wrong where the repair tools can help.
Nothing to panic about with the XP "missing ntldr" error there however. That one goes back to 2000 as well as an annoyance seen often with XP! A few simple tips for this are seen at NTLDR is Missing Error Resolution
Did you set the optical drive as first in the boot order this time around by chance? An empty drive is one thing pointed to there if you removed the XP cd as soon as the install went well.
�� Quote: Originally Posted by Night Hawk Leave it in ide mode for the time being and boot up from the recovery disk if you were provided with or burned one to use the startup repair tool. First make sure the 7 drive is the default drive however.
I went into the BIOS to make sure that IDE is selected for now. I had to leave the CD drive first in the boot order to use the rescue CD. I made sure that the W7 drive is first in the HD group boot order.
When I select to "run start-up repair from CD" it loads , then tells me "cannot repair automatically".
When I select to run from HD it ends in "the boot selection failed because a required device is inaccessible".
I am stuck again!
@Night Hawk:
In my desperation about being unconnected I tried the following, successfully:
Disconnected the new drive
Set the BIOS to default
Ran my rescue CD
Ran "repair" off the CD
Selected reboot normally.
Basta! Got back into W7!
This is where I am now. How do we get to use our XP drive now?
In my desperation about being unconnected I tried the following, successfully:
Disconnected the new drive
Set the BIOS to default
Ran my rescue CD
Ran "repair" off the CD
Selected reboot normally.
Basta! Got back into W7!
This is where I am now. How do we get to use our XP drive now?
What was the mode setting now seen at? AHCI or ide? If AHCI you may be pooched as far as XP not running. Note the following reference on AHCI.
That's part of the 2009 wikipedia information seen at Advanced Host Controller Interface - Wikipedia, the free encyclopedia
I'm certainly glad you saw 7 load immediately showing there wasn't a problem with that drive to work through. I can imagine you are relieved as far as the preinstall!
To get the XP install running again you will likely need to switch back to the ide mode if it isn't that way with the defaults as well as make sure the Plug'n'Play and OS2 support settings are enabled in the bios long enough to install any AHCI driver set for XP.
For that you may want to contact the HP or Foxconn support. But first for Foxconn you may want to get the SIW program look at the model number of the board using the System Info for Windows tool. You will only need to download the freeware with installer version of that however. SIW | Download
The only thing the installer does is create a desktop shortcut still being a stand alone program without any registry involvement. Once on look under the Hardware>Motherboard item. (note image attached below)
If you are able to locate and install the drivers on the XP install you should be able to run XP without problems. The support would be a help.
One thing if you find it set to AHCI by default you could try to switch to the ide mode to see if 7 will still run before replugging the XP drive back in. If 7 runs well you should be able to replug the new drive and run XP normally.
Quote:
AHCI is fully supported out of the box for Windows Vista and Linux operating systems from kernel 2.6.19, as well as later operating systems such as Windows 7. NetBSD also supports drivers in AHCI mode out of the box in certain versions. OpenBSD has had an AHCI driver starting with OpenBSD 4.1. DragonFlyBSD based its AHCI implementation on OpenBSD's and added extended features such as port multiplier support. FreeBSD supports AHCI as well. Solaris 10 introduced AHCI support in the 8/07 release [3]. Older operating systems require hardware-specific drivers to support AHCI.
I'm certainly glad you saw 7 load immediately showing there wasn't a problem with that drive to work through. I can imagine you are relieved as far as the preinstall!
To get the XP install running again you will likely need to switch back to the ide mode if it isn't that way with the defaults as well as make sure the Plug'n'Play and OS2 support settings are enabled in the bios long enough to install any AHCI driver set for XP.
For that you may want to contact the HP or Foxconn support. But first for Foxconn you may want to get the SIW program look at the model number of the board using the System Info for Windows tool. You will only need to download the freeware with installer version of that however. SIW | Download
The only thing the installer does is create a desktop shortcut still being a stand alone program without any registry involvement. Once on look under the Hardware>Motherboard item. (note image attached below)
If you are able to locate and install the drivers on the XP install you should be able to run XP without problems. The support would be a help.
One thing if you find it set to AHCI by default you could try to switch to the ide mode to see if 7 will still run before replugging the XP drive back in. If 7 runs well you should be able to replug the new drive and run XP normally.
�� Quote: Originally Posted by Night Hawk What was the mode setting now seen at? AHCI or ide? If AHCI you may be pooched as far as XP not running.
Someone on Tom's hardware forum suggested this: Make sense to you? This is the site for it: http://www.maximumpc.com/article/how..._and_vista_sp1
Quote:
You need to slipstream the SATA drivers onto your XP CD. It is easy to do. Just Google "slipstream XP". Put your network driver on it and you can go online as soon as you finish installing XP. Slipstream SP3 too. Make sure you use the correct method for whichever service pack you choose. I think it is different for each one.
First you may want to see if 7 will still run when switching to the ide mode unless it's already that way when you restored the factory defaults for the board. Once you are set with 7 in the ide mode you should be able to simply plug the XP drive back in and boot from it to see XP load or add the new entry into the 7 boot loader once the XP files are copied over seeing the boot.ini edit as well.
For slipstreaming sata/Raid controllers you first would need them available. Or only with a second optical drive installed you would burn them to separate cd to have onhand when pressing the F6 option during the installation. But you already installed XP where now you would simply install the drivers onto the older version.
When looking earlier HP only showed Vista/7 updates at the support site and why the SIW tool for finding out the model number of the board is the big step needed. Once you have the model number you can look up the specifications which should show who made the chipset. NVidia, AMD, etc. From there you would be able to look up any XP drivers sets for that particular board at the chipset manufacturer if needed.
The one thing most don't realize is that OEM manufacturers will no longer be supporting XP by providing drivers for newer products coming out. Years back the same was seen for 98 when moving up from an old Socket A build. The time for 98 then ME and 2000 later went by for them and now XP is on the way out.
Hopefully newer releases of the XP Mode or improved VM wares will see more direct access to hardware resources where you will be able to tuck the old version away. These are all things to come there however.
The alternate option would be seeing if the game will install on the 32bit 7 where you would simply dual boot that with the 64bit host and bypass the hassles you are running into. Know anyone running the 32bit 7 who could try that out for you?
If they could install the game on the 32bit 7 you would still need to buy another 7 disk however to custom install on the new drive but be running the game on the latest Windows version.
The problem there is while XP was installed the support for the old version will hamper the gaming since you won't have drivers available for that model through the HP support itself unless contacting their own support for additional information on how to run XP.
For now however try the SIW tool there to find out the board model number. From there a good search can reveal if any XP drivers were actually written. You will need them anyways.
For slipstreaming sata/Raid controllers you first would need them available. Or only with a second optical drive installed you would burn them to separate cd to have onhand when pressing the F6 option during the installation. But you already installed XP where now you would simply install the drivers onto the older version.
When looking earlier HP only showed Vista/7 updates at the support site and why the SIW tool for finding out the model number of the board is the big step needed. Once you have the model number you can look up the specifications which should show who made the chipset. NVidia, AMD, etc. From there you would be able to look up any XP drivers sets for that particular board at the chipset manufacturer if needed.
The one thing most don't realize is that OEM manufacturers will no longer be supporting XP by providing drivers for newer products coming out. Years back the same was seen for 98 when moving up from an old Socket A build. The time for 98 then ME and 2000 later went by for them and now XP is on the way out.
Hopefully newer releases of the XP Mode or improved VM wares will see more direct access to hardware resources where you will be able to tuck the old version away. These are all things to come there however.
The alternate option would be seeing if the game will install on the 32bit 7 where you would simply dual boot that with the 64bit host and bypass the hassles you are running into. Know anyone running the 32bit 7 who could try that out for you?
If they could install the game on the 32bit 7 you would still need to buy another 7 disk however to custom install on the new drive but be running the game on the latest Windows version.
The problem there is while XP was installed the support for the old version will hamper the gaming since you won't have drivers available for that model through the HP support itself unless contacting their own support for additional information on how to run XP.
For now however try the SIW tool there to find out the board model number. From there a good search can reveal if any XP drivers were actually written. You will need them anyways.
�� Quote: Originally Posted by Night Hawk First you may want to see if 7 will still run when switching to the ide mode unless it's already that way when you restored the factory defaults for the board. Once you are set with 7 in the ide mode you should be able to simply plug the XP drive back in and boot from it to see XP load or add the new entry into the 7 boot loader once the XP files are copied over seeing the boot.ini edit as well.
That would be one way to find out for sure! Hopefully 7 will still run normally. But this is the one thing about premade OEM systems where they configure everything by their methods where their techs already know just where to look when problems come up.
That won't make life any easier for you however! This is why you may have to consider the 32bit 7 as the second OS if you find the game will go on and run. I found that here when some refused to install or run on the 32bit Vista but went right on the 32bit 7! That has a great deal of backward compatibility with XP written type games and apps it seems.
That won't make life any easier for you however! This is why you may have to consider the 32bit 7 as the second OS if you find the game will go on and run. I found that here when some refused to install or run on the 32bit Vista but went right on the 32bit 7! That has a great deal of backward compatibility with XP written type games and apps it seems.
�� Quote: Originally Posted by Night Hawk That would be one way to find out for sure! Hopefully 7 will still run normally. But this is the one thing about premade OEM systems where they configure everything by their methods where their techs already know just where to look when problems come up.
�� Quote: Originally Posted by Night Hawk That won't make life any easier for you however! This is why you may have to consider the 32bit 7 as the second OS if you find the game will go on and run. I found that here when some refused to install or run on the 32bit Vista but went right on the 32bit 7! That has a great deal of backward compatibility with XP written type games and apps it seems.
If you find it set at AHCI and switch to ide and it fails you simply re-enter the bios to change it back. A quck return trip there would be all you needed.
As for the game itself what "failed to install or run" on the 32bit Vista doesn't mean it won't go the 32bit 7! What I am pointing out is that 7 is now seeing an improved backward compatibility to XP softwares over what had been seen with Vista.
All you can do however is see if someone you know running the 32bit 7 can try out it out on their machine to see if the installation works unless you have a cd key requirement for that or a log into an online account situation like many games see. You simply want to find out if it will.
Recently I tossed a temp install of the 32bit 7 on a real old case and saw XP device drivers work like they had been written for 7 specifically! Never rule anything out completely with 7! until tested that is.
As for the game itself what "failed to install or run" on the 32bit Vista doesn't mean it won't go the 32bit 7! What I am pointing out is that 7 is now seeing an improved backward compatibility to XP softwares over what had been seen with Vista.
All you can do however is see if someone you know running the 32bit 7 can try out it out on their machine to see if the installation works unless you have a cd key requirement for that or a log into an online account situation like many games see. You simply want to find out if it will.
Recently I tossed a temp install of the 32bit 7 on a real old case and saw XP device drivers work like they had been written for 7 specifically! Never rule anything out completely with 7!
until tested that is. I connected the XP drive as well this morning, without changing the default BIOS, and W7 can see it. That means I could use it for storage, but so far not for booting into it. Maybe if I slip stream SP3 into the OS it will be possible?
You would need to slipstream SP3 into the XP install disk to add the service pack into the installation process.
With 7 up and running again it comes as no surprize it immediately saw the new drive once plugged back in. You can also try getting the new entry for XP as if XP was running to take care of that part.
The boot files copied over as well as the boot entry can always be removed easily later if XP doesn't run or succeed the next time around. But if XP loads right away you would have the entry part for the dual boot already taken care of. Once booted in XP you would then simply go for the SP3 install.
With 7 up and running again it comes as no surprize it immediately saw the new drive once plugged back in. You can also try getting the new entry for XP as if XP was running to take care of that part.
The boot files copied over as well as the boot entry can always be removed easily later if XP doesn't run or succeed the next time around. But if XP loads right away you would have the entry part for the dual boot already taken care of. Once booted in XP you would then simply go for the SP3 install.
�� Quote: Originally Posted by Night Hawk You would need to slipstream SP3 into the XP install disk to add the service pack into the installation process.
�� Quote: Originally Posted by Night Hawk With 7 up and running again it comes as no surprize it immediately saw the new drive once plugged back in. You can also try getting the new entry for XP as if XP was running to take care of that part. The boot files copied over as well as the boot entry can always be removed easily later if XP doesn't run or succeed the next time around. But if XP loads right away you would have the entry part for the dual boot already taken care of. Once booted in XP you would then simply go for the SP3 install.
That's what slipstreaming refers to. Not the otiginal but adding drivers or an SP into a backup copy or ISO image in order to have everything install at the same time. You are still using the same product key on the same machine.
For your situation however first you have an XP install present and if able to boot into it can simply download and install the redistributed SP3 to a temp folder if not through the MS update site. The full package however can be saved to disk if any reinstall is needed later rather then repeat downloads or visits to the update site in order to save time. You've spent quite a bit already so far!
The full 316mb for SP3 is ready for download at Download Windows XP Service Pack 3 Build 5512 FINAL Free Trial - Microsoft periodically combines updates, fixes, and other improvements into a single package - Service Pack - Softpedia That has it's own installer to start up while booted in XP.
First you want to see if XP will load once the entry is added in or simply using the boot device menu option to boot from that drive while you have it set to the ide mode. If XP loads right up the SP3 can simply go on once downloaded. That will take about 20minutes requiring a couple of full restarts to finish. Then you simply follow the guide on seeing the new entry for XP added into the 7 boot loader.
Once you have the new entry in for XP in the 7 BCD store and have SP3 on you should be all set to simply install the game you want once all the other updates available for things like adobe reader and a few other items are set. If the game lacks the DX 9c installer you will want to download that for XP however. Download details: DirectX End-User Runtime
For your situation however first you have an XP install present and if able to boot into it can simply download and install the redistributed SP3 to a temp folder if not through the MS update site. The full package however can be saved to disk if any reinstall is needed later rather then repeat downloads or visits to the update site in order to save time. You've spent quite a bit already so far!
The full 316mb for SP3 is ready for download at Download Windows XP Service Pack 3 Build 5512 FINAL Free Trial - Microsoft periodically combines updates, fixes, and other improvements into a single package - Service Pack - Softpedia That has it's own installer to start up while booted in XP.
First you want to see if XP will load once the entry is added in or simply using the boot device menu option to boot from that drive while you have it set to the ide mode. If XP loads right up the SP3 can simply go on once downloaded. That will take about 20minutes requiring a couple of full restarts to finish. Then you simply follow the guide on seeing the new entry for XP added into the 7 boot loader.
Once you have the new entry in for XP in the 7 BCD store and have SP3 on you should be all set to simply install the game you want once all the other updates available for things like adobe reader and a few other items are set. If the game lacks the DX 9c installer you will want to download that for XP however. Download details: DirectX End-User Runtime
�� Quote: Originally Posted by Night Hawk For your situation however first you have an XP install present and if able to boot into it can simply download and install the redistributed SP3 to a temp folder if not through the MS update site.
Have you tried copying the boot files over to the 7 drive, editing the boot.ini file to point at the second drive where XP is located, and added a new entry for XP in the 7 boot loader with EasyBCD?
This is what you wanted to set up a dual boot with 7. The guide posted earlier will take you through each step there in Method Two for installing XP after 7. Once the new entry is added in the boot options menu you can boot into XP when the system starts rather then the default 7 install.
The error is seen when going to boot from the second drive when changing the boot order or simply selecting the second drive from the boot device menu(one of the F keys assigned like F4, F11, F12) which still seems a bit odd unless something pooched the XP boot sector when swapping modes?
For now however getting the new entry in and then selecting XP at startup will reveal if all is still well with the XP install you got on. You still have to have 7 running however in order to see a working dual boot with half the problem solved already. Once the new entry is in we can work out the error if that is still seen after.
This is what you wanted to set up a dual boot with 7. The guide posted earlier will take you through each step there in Method Two for installing XP after 7. Once the new entry is added in the boot options menu you can boot into XP when the system starts rather then the default 7 install.
The error is seen when going to boot from the second drive when changing the boot order or simply selecting the second drive from the boot device menu(one of the F keys assigned like F4, F11, F12) which still seems a bit odd unless something pooched the XP boot sector when swapping modes?
For now however getting the new entry in and then selecting XP at startup will reveal if all is still well with the XP install you got on. You still have to have 7 running however in order to see a working dual boot with half the problem solved already. Once the new entry is in we can work out the error if that is still seen after.
My BIOS is set to RAID, so I suppose this applies to me:
If you have a RAID setup, you will need to have the XP RAID drivers on a Floppy disc available to select and load at the F6 prompt while installing XP.
But I already installed XP!
Do I have to worry about that now?
If you have a RAID setup, you will need to have the XP RAID drivers on a Floppy disc available to select and load at the F6 prompt while installing XP.
But I already installed XP!
Do I have to worry about that now?
You set the Raid mode?! 
That will automatically prevent XP from loading not being set up for any array to begin with for either version!
Arrays are for using one OS across more then one drive or for storage. For individual OSs each on a separate drive you would never use the Raid setting since that is intended to sync more then one drive together. You can still switch back now however. Setting up an array would mean wiping 7 out as well as the XP install you finally got on.
With XP already on the idea was simply to add a new entry into the 7 boot loader to see the option to boot into XP at startup added not reconfigure everything all over again. When 7 didn't run following the XP install the switch of drive modes was to get both working.
That will automatically prevent XP from loading not being set up for any array to begin with for either version!Arrays are for using one OS across more then one drive or for storage. For individual OSs each on a separate drive you would never use the Raid setting since that is intended to sync more then one drive together. You can still switch back now however. Setting up an array would mean wiping 7 out as well as the XP install you finally got on.
With XP already on the idea was simply to add a new entry into the 7 boot loader to see the option to boot into XP at startup added not reconfigure everything all over again. When 7 didn't run following the XP install the switch of drive modes was to get both working.
�� Quote: Originally Posted by Night Hawk You set the Raid mode?! That will automatically prevent XP from loading not being set up for any array to begin with for either version!
That will automatically prevent XP from loading not being set up for any array to begin with for either version!�� Quote: Originally Posted by Night Hawk Arrays are for using one OS across more then one drive or for storage. For individual OSs each on a separate drive you would never use the Raid setting since that is intended to sync more then one drive together. You can still switch back now however. Setting up an array would mean wiping 7 out as well as the XP install you finally got on.
�� Quote: Originally Posted by Night Hawk With XP already on the idea was simply to add a new entry into the 7 boot loader to see the option to boot into XP at startup added not reconfigure everything all over again. When 7 didn't run following the XP install the switch of drive modes was to get both working.
I didn't say you set up an array. But you wouldn't want to leave it set at Raid. This is why I mentioned going back in the bios once you had reset everything back to the defaults as well as looking over the guide there.
Most recent and new boards will see the options for setting up an array often with a second pair of drives typically for expanding your storage capacity. A few posts back you mentioned seeing the missing ntldr error message apparently when trying to boot from the second drive if I am correct on that.
That doesn't have to be a bootable drive however to see XP load when the 7 host drive has the XP boot files present and the entry for XP in the 7 BCD. With 7 running the next step would be finding out if XP will load with the option seen in the 7 boot loader the way it is or to see if a change of the drive mode is needed.
If you already copied the boot files over and added the entry in for XP and ran into the error that would be a result of not having edited the boot.ini file to point to the correct drive which should be seen as "rdisk(1)partition(1)" rather then the default install's "rdisk(0)partition(1)" since XP went on without the 7 drive present. The boot files and mbr entries originally went to the second drive now being seen as the second not first.
The next two screens here will show the correction with the first being the default taken from the XP Mode which of course is the Pro edition there. The second will show the correction for the second drive needed in order to see XP load.
The third shows how to overwrite the original copy of the boot.ini by using the "all files" not "Text Documents [*.txt]" format since you want an exact match not a text file to see this part done. These will give you a reference to work with once you have the "read only" box unchecked in the copy. You may need to take ownership in order to keep the read only box cleared however.
Most recent and new boards will see the options for setting up an array often with a second pair of drives typically for expanding your storage capacity. A few posts back you mentioned seeing the missing ntldr error message apparently when trying to boot from the second drive if I am correct on that.
That doesn't have to be a bootable drive however to see XP load when the 7 host drive has the XP boot files present and the entry for XP in the 7 BCD. With 7 running the next step would be finding out if XP will load with the option seen in the 7 boot loader the way it is or to see if a change of the drive mode is needed.
If you already copied the boot files over and added the entry in for XP and ran into the error that would be a result of not having edited the boot.ini file to point to the correct drive which should be seen as "rdisk(1)partition(1)" rather then the default install's "rdisk(0)partition(1)" since XP went on without the 7 drive present. The boot files and mbr entries originally went to the second drive now being seen as the second not first.
The next two screens here will show the correction with the first being the default taken from the XP Mode which of course is the Pro edition there. The second will show the correction for the second drive needed in order to see XP load.
The third shows how to overwrite the original copy of the boot.ini by using the "all files" not "Text Documents [*.txt]" format since you want an exact match not a text file to see this part done. These will give you a reference to work with once you have the "read only" box unchecked in the copy. You may need to take ownership in order to keep the read only box cleared however.
�� Quote: Originally Posted by Night Hawk I didn't say you set up an array. But you wouldn't want to leave it set at Raid. This is why I mentioned going back in the bios once you had reset everything back to the defaults as well as looking over the guide there.
�� Quote: Originally Posted by Night Hawk Most recent and new boards will see the options for setting up an array often with a second pair of drives typically for expanding your storage capacity. A few posts back you mentioned seeing the missing ntldr error message apparently when trying to boot from the second drive if I am correct on that.
I also don't understand why I originally was able to boot into XP, right after installing it, and no NTLDR missing came up!
I am getting more confused over what to do next every day I see more instructions!
This is pretty good instruction on the slip streaming process: How To: Slipstream Windows XP SP3 and Vista SP1 | Maximum PC
Only trouble is that I was not able to download the SP3 package from the MS site - it repeatedly stopped, claiming it couldn't read from the source file. So I had to give up!
Does anyone have that file, or know how to get it?
Only trouble is that I was not able to download the SP3 package from the MS site - it repeatedly stopped, claiming it couldn't read from the source file. So I had to give up!
Does anyone have that file, or know how to get it?
I posted the link for the full redistributed page back a page in the thread here. You simply download that to a folder until you can run in XP. Windows XP Service Pack 3 Download - Softpedia
(Note: Use Mirror #2 not the first IT developers version! Mirror #3 for ISO dvd image)
Due to that being over 300mb in size once downloaded you can burn it to a cd-r to have onhand. In fact MS originally had a 522mb ISO image for the SP3 for seeing it installed on several machines you burned to a dvd-r when the service pack was first released.
Softpedia still carries SP2 for XP as well and both SPs for Vista. You can expect to eventually see the redistributable form of SP1 for 7 there at some point as well.
Now as far as XP still not loading which mode and which drive was set as default when seeing it run the first time? I thought you mentioned you had the bios set in the ide mode and saw XP installed. You might want to list the steps you have taken so far in order to backtrack a little to see what changes you have made since XP was running.
Once you replugged the 7 drive back in the XP was moved to the second drive status as the 7 drive should have automatically been made the default boot device. Have you copied the XP boot files over to the 7 drive?
These are the things you have to look at now in order to find out why XP is not starting up for you.
1) Windows Explorer menu bar>Tools>Folder options>View tab uncheck "files with known extension types" and "protected operating system files" in order to make all boot files visible.
2) copy not edit XP boot files from second drive onto the root of the W7 host drive.
3) edit copy of not original boot.ini file to point copy of ntldr at second drive.
4) add new entry into W7 BCD store and boot options menu with EasyBCD once XP drive provided a drive letter in 7 Disk Management tool. Then associate XP entry to that drive letter in EasyBCD.
5) Verify new entry in EasyBCD view settings prior to system restart to select XP option at startup.
From what you said the XP drive was immediately available showing a trip into the DM to assign a drive letter wouldn't be needed. When adding in the new entry however the correct drive letter will be needed and why you should always verfiy the entry was correct before a full restart with any dual boot setup.
(Note: Use Mirror #2 not the first IT developers version! Mirror #3 for ISO dvd image)
Due to that being over 300mb in size once downloaded you can burn it to a cd-r to have onhand. In fact MS originally had a 522mb ISO image for the SP3 for seeing it installed on several machines you burned to a dvd-r when the service pack was first released.
Softpedia still carries SP2 for XP as well and both SPs for Vista. You can expect to eventually see the redistributable form of SP1 for 7 there at some point as well.
Now as far as XP still not loading which mode and which drive was set as default when seeing it run the first time? I thought you mentioned you had the bios set in the ide mode and saw XP installed. You might want to list the steps you have taken so far in order to backtrack a little to see what changes you have made since XP was running.
Once you replugged the 7 drive back in the XP was moved to the second drive status as the 7 drive should have automatically been made the default boot device. Have you copied the XP boot files over to the 7 drive?
These are the things you have to look at now in order to find out why XP is not starting up for you.
1) Windows Explorer menu bar>Tools>Folder options>View tab uncheck "files with known extension types" and "protected operating system files" in order to make all boot files visible.
2) copy not edit XP boot files from second drive onto the root of the W7 host drive.
3) edit copy of not original boot.ini file to point copy of ntldr at second drive.
4) add new entry into W7 BCD store and boot options menu with EasyBCD once XP drive provided a drive letter in 7 Disk Management tool. Then associate XP entry to that drive letter in EasyBCD.
5) Verify new entry in EasyBCD view settings prior to system restart to select XP option at startup.
From what you said the XP drive was immediately available showing a trip into the DM to assign a drive letter wouldn't be needed. When adding in the new entry however the correct drive letter will be needed and why you should always verfiy the entry was correct before a full restart with any dual boot setup.
�� Quote: Originally Posted by Night Hawk I posted the link for the full redistributed page back a page in the thread here. You simply download that to a folder until you can run in XP. Windows XP Service Pack 3 Download - Softpedia
�� Quote: Originally Posted by Night Hawk Due to that being over 300mb in size once downloaded you can burn it to a cd-r to have onhand.
�� Quote: Originally Posted by Night Hawk Now as far as XP still not loading which mode and which drive was set as default when seeing it run the first time? I thought you mentioned you had the bios set in the ide mode and saw XP installed. You might want to list the steps you have taken so far in order to backtrack a little to see what changes you have made since XP was running.
�� Quote: Originally Posted by Night Hawk Once you replugged the 7 drive back in the XP was moved to the second drive status as the 7 drive should have automatically been made the default boot device.
�� Quote: Originally Posted by Night Hawk Have you copied the XP boot files over to the 7 drive?
�� Quote: Originally Posted by Night Hawk These are the things you have to look at now in order to find out why XP is not starting up for you.
1) Windows Explorer menu bar>Tools>Folder options>View tab uncheck "files with known extension types" and "protected operating system files" in order to make all boot files visible.
2) copy not edit XP boot files from second drive onto the root of the W7 host drive.
1) Windows Explorer menu bar>Tools>Folder options>View tab uncheck "files with known extension types" and "protected operating system files" in order to make all boot files visible.
2) copy not edit XP boot files from second drive onto the root of the W7 host drive.
�� Quote: Originally Posted by Night Hawk 3) edit copy of not original boot.ini file to point copy of ntldr at second drive.
OK! You just confirmed that you haven't attempted any edits of the boot.ini file itself. I was trying to find out why you were running into the missing ntldr error if you weren't even booting from the second but first drive where 7 is.
As for SP3 not having an XP SP3 installation disk you will likely want to back it up on a cd-r for availability in case you have an oops! of some type and need another XP install at some point. That will save the download time at least.
Step #1 is unhiding the protected system files by going into any Windows Explorer window and running a fast trip upto the menu bar there. You go across to the Tools and drop the menu there and scroll down to "Folder options". Once the next screen appears you want to open the View tab since you are going to change a pair of view settings to make all system files visible.
Once you uncheck the two items named and click the apply button you will be prompted by Windows with the typical warning and confirmation screen. While you won't be changing any 7 files at the root you will want to get to know which ones are present to tell them apart from the XP files coming over. This will also prevent any inability to see them on the XP drive since those are also protected files for the older version.
Simply copy and paste the 3 XP boot files onto the root of C on the 7 drive. NTDETECT.COM, ntldr, and boot.ini You certainly won't need or want the other files or even XP's paging file copied over as useless clutter!
As for SP3 not having an XP SP3 installation disk you will likely want to back it up on a cd-r for availability in case you have an oops! of some type and need another XP install at some point. That will save the download time at least.
Step #1 is unhiding the protected system files by going into any Windows Explorer window and running a fast trip upto the menu bar there. You go across to the Tools and drop the menu there and scroll down to "Folder options". Once the next screen appears you want to open the View tab since you are going to change a pair of view settings to make all system files visible.
Once you uncheck the two items named and click the apply button you will be prompted by Windows with the typical warning and confirmation screen. While you won't be changing any 7 files at the root you will want to get to know which ones are present to tell them apart from the XP files coming over. This will also prevent any inability to see them on the XP drive since those are also protected files for the older version.
Simply copy and paste the 3 XP boot files onto the root of C on the 7 drive. NTDETECT.COM, ntldr, and boot.ini You certainly won't need or want the other files or even XP's paging file copied over as useless clutter!
There is a check at "Show hidden drives, folders and files". That is the only one present.
On the XP drive I looked under the Windows folder, then under the system folder, and system32 folder, but not a single one of these 3 files shows up. In the system32 folder are 3 boot*** files, but not the boot.ini!
You are looking in the wrong place for those! Those are found at "C:\" not "C:\Windows\System32\" being the "root" of the drive itself.
If you go back to the 3 screens posted earlier the 3rd shows the root of C while the XP Mode is running. For the root of C on XP Home as well as for XP Pro or the MCE edition the same boot files will be seen there too.
As for the View tab when you look under the "Show hidden files, folders, or drives" the next 3 items are for:
-Hide empty drives in the Computer folder-
-Hide extensions for known file types-
-Hide protected operating system file types-
Once you uncheck those 3 as well Windows will prompt you with the warning where you simply click to confirm the change being made to see them made visible. When you go back to the root of C afterwards the previously hidden boot files will then be seen.
If you go back to the 3 screens posted earlier the 3rd shows the root of C while the XP Mode is running. For the root of C on XP Home as well as for XP Pro or the MCE edition the same boot files will be seen there too.
As for the View tab when you look under the "Show hidden files, folders, or drives" the next 3 items are for:
-Hide empty drives in the Computer folder-
-Hide extensions for known file types-
-Hide protected operating system file types-
Once you uncheck those 3 as well Windows will prompt you with the warning where you simply click to confirm the change being made to see them made visible. When you go back to the root of C afterwards the previously hidden boot files will then be seen.
�� Quote: Originally Posted by Night Hawk You are looking in the wrong place for those! Those are found at "C:\" not "C:\Windows\System32\" being the "root" of the drive itself.
If you go back to the 3 screens posted earlier the 3rd shows the root of C while the XP Mode is running. For the root of C on XP Home as well as for XP Pro or the MCE edition the same boot files will be seen there too.
If you go back to the 3 screens posted earlier the 3rd shows the root of C while the XP Mode is running. For the root of C on XP Home as well as for XP Pro or the MCE edition the same boot files will be seen there too.
You don't have to be booted into XP or be running the XP Mode to see the boot files copied over to the 7 host drive. You will have to change the view settings however in the Folder options in 7 for the time being in order to see the new entry for XP added into the 7 BCD store and boot options once the XP files are copied over from the second drive.
The reason you are not able to see the boot files is from still having those files hidden from view. I think this is where you are getting a bit confused there.
Once you have that taken care of that first step of unchecking those items where 3 of the 4 there are a mandate you can continue to copy them over and edit the boot.ini file. You then continue to the next step of adding in the new entry for XP using the EasyBCD program being a BCD editing program.
From that point on you would simply reboot and select the option for XP to see if it will load up for you. As for the missing ntldr error you have been seeing is that from setting the XP drive as first in the boot order? Likely something went wrong along the way there.
Once you have the boot files copied over, the boot.ini edit is seen to, and the new entry added into the 7 loader you will be bypassing the boot informaion on the second drive entirely using the 7 boot loader instead with the XP Loader present on the 7 host/boot drive.
I added a screen for which items in the View tab to see unchecked to help you a bit further. You get in there by the "menu bar>Tools>Folder options>View" tab with any WE window open or simply go into the "Control Panel>Folder options" sub there to see those taken care of.
The reason you are not able to see the boot files is from still having those files hidden from view. I think this is where you are getting a bit confused there.
Once you have that taken care of that first step of unchecking those items where 3 of the 4 there are a mandate you can continue to copy them over and edit the boot.ini file. You then continue to the next step of adding in the new entry for XP using the EasyBCD program being a BCD editing program.
From that point on you would simply reboot and select the option for XP to see if it will load up for you. As for the missing ntldr error you have been seeing is that from setting the XP drive as first in the boot order? Likely something went wrong along the way there.
Once you have the boot files copied over, the boot.ini edit is seen to, and the new entry added into the 7 loader you will be bypassing the boot informaion on the second drive entirely using the 7 boot loader instead with the XP Loader present on the 7 host/boot drive.
I added a screen for which items in the View tab to see unchecked to help you a bit further. You get in there by the "menu bar>Tools>Folder options>View" tab with any WE window open or simply go into the "Control Panel>Folder options" sub there to see those taken care of.
�� Quote: Originally Posted by Night Hawk The reason you are not able to see the boot files is from still having those files hidden from view. I think this is where you are getting a bit confused there.
Once you have that taken care of that first step of unchecking those items where 3 of the 4 there are a mandate you can continue to copy them over and edit the boot.ini file. You then continue to the next step of adding in the new entry for XP using the EasyBCD program being a BCD editing program.
From that point on you would simply reboot and select the option for XP to see if it will load up for you. As for the missing ntldr error you have been seeing is that from setting the XP drive as first in the boot order? Likely something went wrong along the way there.
Once you have the boot files copied over, the boot.ini edit is seen to, and the new entry added into the 7 loader you will be bypassing the boot informaion on the second drive entirely using the 7 boot loader instead with the XP Loader present on the 7 host/boot drive.
I added a screen for which items in the View tab to see unchecked to help you a bit further. You get in there by the "menu bar>Tools>Folder options>View" tab with any WE window open or simply go into the "Control Panel>Folder options" sub there to see those taken care of.
Once you have that taken care of that first step of unchecking those items where 3 of the 4 there are a mandate you can continue to copy them over and edit the boot.ini file. You then continue to the next step of adding in the new entry for XP using the EasyBCD program being a BCD editing program.
From that point on you would simply reboot and select the option for XP to see if it will load up for you. As for the missing ntldr error you have been seeing is that from setting the XP drive as first in the boot order? Likely something went wrong along the way there.
Once you have the boot files copied over, the boot.ini edit is seen to, and the new entry added into the 7 loader you will be bypassing the boot informaion on the second drive entirely using the 7 boot loader instead with the XP Loader present on the 7 host/boot drive.
I added a screen for which items in the View tab to see unchecked to help you a bit further. You get in there by the "menu bar>Tools>Folder options>View" tab with any WE window open or simply go into the "Control Panel>Folder options" sub there to see those taken care of.
You missed one! Now try unchecking the "Hide empty drives in Computer folder" item to see if that helps any when going back to browse the root of the XP drive to see if you now are able to view the files outside of the Windows directory there.
Now try unchecking the "Hide empty drives in Computer folder" item to see if that helps any when going back to browse the root of the XP drive to see if you now are able to view the files outside of the Windows directory there. �� Quote: Originally Posted by Night Hawk You missed one! Now try unchecking the "Hide empty drives in Computer folder" item to see if that helps any when going back to browse the root of the XP drive to see if you now are able to view the files outside of the Windows directory there.
Now try unchecking the "Hide empty drives in Computer folder" item to see if that helps any when going back to browse the root of the XP drive to see if you now are able to view the files outside of the Windows directory there. You shouldn't be having any problem seeing the files at the root if you had XP running while the 7 drive was unplugged. If you simply went ahead and got XP while the 7 drive was plugged in that would explain why 7 wouldn't start up afterwards until you corrected that with the startup repair tool.
In that case the missing ntldr error would be seen when setting the XP drive as first due to the various attempts you made collectively seeing mbr entries on both drives for XP without any boot files there instead of simply seeing a flashing dash in the upper left hand corner of the screen.
If you discover that the boot files are present your next two steps would simply be editing the boot.ini file to insure that correction is addressed and adding the new entry into the 7 boot loader.
In that case the missing ntldr error would be seen when setting the XP drive as first due to the various attempts you made collectively seeing mbr entries on both drives for XP without any boot files there instead of simply seeing a flashing dash in the upper left hand corner of the screen.
If you discover that the boot files are present your next two steps would simply be editing the boot.ini file to insure that correction is addressed and adding the new entry into the 7 boot loader.
�� Quote: Originally Posted by Night Hawk You shouldn't be having any problem seeing the files at the root if you had XP running while the 7 drive was unplugged. If you simply went ahead and got XP while the 7 drive was plugged in that would explain why 7 wouldn't start up afterwards until you corrected that with the startup repair tool.
�� Quote: Originally Posted by Night Hawk In that case the missing ntldr error would be seen when setting the XP drive as first due to the various attempts you made collectively seeing mbr entries on both drives for XP without any boot files there instead of simply seeing a flashing dash in the upper left hand corner of the screen.
If you discover that the boot files are present your next two steps would simply be editing the boot.ini file to insure that correction is addressed and adding the new entry into the 7 boot loader.
If you discover that the boot files are present your next two steps would simply be editing the boot.ini file to insure that correction is addressed and adding the new entry into the 7 boot loader.
Here is an update on what I did today.
By a stroke of brilliance (ha!) I cranked up my second PC, an old Compaq with XP), copied the boot files on a little flash drive, and added them to my W7 root. Then I downloaded EasyBCD and added the XP drive.
Then I held my breath, and rebooted my machine.
Low and behold, it gave me a choice of both drives!
However, when I select the XP drive, it asks how I want to open it (the 5 options from "SAFE MODE" over "SM with Networking", "SM with Command Prompt", to "Open Windows normally")
I tried all 5 except "SM with Command Prompt", and none opens XP, but keeps repeating the boot process, offering both OSes.
Could this be the reason:
In EasyBCD the XP drive shows as "D", not "F".
I made sure not to let EBCD "select automatically", but manually entered F as the drive. It just ignored me!
By a stroke of brilliance (ha!
) I cranked up my second PC, an old Compaq with XP), copied the boot files on a little flash drive, and added them to my W7 root. Then I downloaded EasyBCD and added the XP drive.Then I held my breath, and rebooted my machine.
Low and behold, it gave me a choice of both drives!
However, when I select the XP drive, it asks how I want to open it (the 5 options from "SAFE MODE" over "SM with Networking", "SM with Command Prompt", to "Open Windows normally")
I tried all 5 except "SM with Command Prompt", and none opens XP, but keeps repeating the boot process, offering both OSes.
Could this be the reason:
In EasyBCD the XP drive shows as "D", not "F".
I made sure not to let EBCD "select automatically", but manually entered F as the drive. It just ignored me!
You first have to verify which drive letter is assigned in the DM for the XP drive. If F you apparently used D when adding the new entry in offsetting things a bit but wouldn't be seeing the XP boot options menu!
In the 7 DM first make sure the XP drive is set with the letter you want to use for the XP drive if not already seen in WE as F. The options found in the EasyBCD's Advanced Settings will allow you to reassociate the XP entry with the correct drive letter as well.(see attached image) Once you change and even rename the entry simply click on the "save" button to save the change made.
The F8 boot menu shows that XP is loading but having a problem of some type where you will want to take notice of any error messages like those seen if a blue screen appears in order to trace the problem.
Knowing that XP made the attempt however is certainly good news for you. Now to get it running normally! You may end up needing another full install to replace the present following the guide or a repair install if the option is seen during the setup to correct initial installation problems.
Once you are at the XP desktop and can connect online the first item will be the optional hardware updates for XP. The MS update may just locate and display the needed sata/Raid controller drivers as part of the total number you can expect! Often that's how you can get the "hard2find" type. Go for it!
In the 7 DM first make sure the XP drive is set with the letter you want to use for the XP drive if not already seen in WE as F. The options found in the EasyBCD's Advanced Settings will allow you to reassociate the XP entry with the correct drive letter as well.(see attached image) Once you change and even rename the entry simply click on the "save" button to save the change made.
The F8 boot menu shows that XP is loading but having a problem of some type where you will want to take notice of any error messages like those seen if a blue screen appears in order to trace the problem.
Knowing that XP made the attempt however is certainly good news for you. Now to get it running normally!
You may end up needing another full install to replace the present following the guide or a repair install if the option is seen during the setup to correct initial installation problems.Once you are at the XP desktop and can connect online the first item will be the optional hardware updates for XP. The MS update may just locate and display the needed sata/Raid controller drivers as part of the total number you can expect! Often that's how you can get the "hard2find" type. Go for it!
�� Quote: Originally Posted by Night Hawk You first have to verify which drive letter is assigned in the DM for the XP drive. If F you apparently used D when adding the new entry in offsetting things a bit but wouldn't be seeing the XP boot options menu!
�� Quote: Originally Posted by Night Hawk In the 7 DM first make sure the XP drive is set with the letter you want to use for the XP drive if not already seen in WE as F. The options found in the EasyBCD's Advanced Settings will allow you to reassociate the XP entry with the correct drive letter as well.(see attached image)
�� Quote: Originally Posted by Night Hawk Once you change and even rename the entry simply click on the "save" button to save the change made.
�� Quote: Originally Posted by Night Hawk The F8 boot menu shows that XP is loading but having a problem of some type where you will want to take notice of any error messages like those seen if a blue screen appears in order to trace the problem.
Knowing that XP made the attempt however is certainly good news for you. Now to get it running normally! You may end up needing another full install to replace the present following the guide or a repair install if the option is seen during the setup to correct initial installation problems.
Knowing that XP made the attempt however is certainly good news for you. Now to get it running normally!
You may end up needing another full install to replace the present following the guide or a repair install if the option is seen during the setup to correct initial installation problems. Well, it offers the options on bootup, but when I select XP I get an error msg, saying I should insert the installation disc and do a "repair", as well as this:
FILE \NST\ntldr
The selected entry could not be located because the application is either missing or corrupted.
Last time this happened I reinstalled XP, then had to use the rescue CD to get into W7 again. This time I just rebooted and it did allow me to select W7 again.
Anyway, we only put a "ntldr" file in the root, not a NST\ntldr. No wonder it can't be found!
FILE \NST\ntldr
The selected entry could not be located because the application is either missing or corrupted.
Last time this happened I reinstalled XP, then had to use the rescue CD to get into W7 again. This time I just rebooted and it did allow me to select W7 again.
Anyway, we only put a "ntldr" file in the root, not a NST\ntldr. No wonder it can't be found!
After checking to see if F was set in the 7 DM did you go into the Advanced Settings in the EasyBCD program and try reassociating the entry to F from D? If that doesn't work you simply delete the present XP entry and add a new one pointing at F.
You're still making progress despite a few obstacles from where you were. The important will getting XP to run. Minor adjustments can be taken care of after.
As for a repair install of XP that wouldn't trash the 7 part of the mbr like a full clean install would since you are in a sense performing an upgrade repair install without using the upgrade option in Windows. Basically it does the same thing as far as replacing the main system files whille leaving the rest intact.
You're still making progress despite a few obstacles from where you were. The important will getting XP to run. Minor adjustments can be taken care of after.
As for a repair install of XP that wouldn't trash the 7 part of the mbr like a full clean install would since you are in a sense performing an upgrade repair install without using the upgrade option in Windows. Basically it does the same thing as far as replacing the main system files whille leaving the rest intact.
�� Quote: Originally Posted by Night Hawk After checking to see if F was set in the 7 DM did you go into the Advanced Settings in the EasyBCD program and try reassociating the entry to F from D? If that doesn't work you simply delete the present XP entry and add a new one pointing at F.
Did I edit the boot.ini file correctly?
The boot.ini file looks good there. You have it pointing to the second as it should be.
Hopefully you remembered to choose the "all files" option when going to save it by overwriting the original and didn't end up seeing "txt" instead of "ini" for the 3 digit file extension.
The reassociation of drive letter trick doesn't work in all occassions unfortunately where you then have to remove the first entry once everything is set to add a totally new in with the correct drive letter. That's about the only minor annoyance ever run into with the program but easy to fix with the new entry pointing to F not D.
If the XP install itself was complete you should be able to boot right into XP with the new entry seeing the correct drive letter. Provided everything else is in working order you should see XP load up without problems. Otherwise there will be a few last minute items that would need to worked out.
Hopefully you remembered to choose the "all files" option when going to save it by overwriting the original and didn't end up seeing "txt" instead of "ini" for the 3 digit file extension.
The reassociation of drive letter trick doesn't work in all occassions unfortunately where you then have to remove the first entry once everything is set to add a totally new in with the correct drive letter. That's about the only minor annoyance ever run into with the program but easy to fix with the new entry pointing to F not D.
If the XP install itself was complete you should be able to boot right into XP with the new entry seeing the correct drive letter. Provided everything else is in working order you should see XP load up without problems. Otherwise there will be a few last minute items that would need to worked out.
�� Quote: Originally Posted by Night Hawk The boot.ini file looks good there. You have it pointing to the second as it should be.
Hopefully you remembered to choose the "all files" option when going to save it by overwriting the original and didn't end up seeing "txt" instead of "ini" for the 3 digit file extension.
Hopefully you remembered to choose the "all files" option when going to save it by overwriting the original and didn't end up seeing "txt" instead of "ini" for the 3 digit file extension.
�� Quote: Originally Posted by Night Hawk The reassociation of drive letter trick doesn't work in all occassions unfortunately where you then have to remove the first entry once everything is set to add a totally new in with the correct drive letter. That's about the only minor annoyance ever run into with the program but easy to fix with the new entry pointing to F not D.
�� Quote: Originally Posted by Night Hawk If the XP install itself was complete you should be able to boot right into XP with the new entry seeing the correct drive letter. Provided everything else is in working order you should see XP load up without problems. Otherwise there will be a few last minute items that would need to worked out.
The default letter would be D. But you simply bring the droplist down when going to select another drive letter when in the Advanced Settings or when adding a new entry since that assumes the next drive letter available following C would be D.
When going to restart what was seen when you selected the XP entry?
Hopefully you removed the first and saw the new corrected one added in for the F letter. You're much closer now to having everything running. We simply have to find the last holdup and see that fixed to the need for a full reinstall of XP plus another repair of the 7 mbr.
When going to restart what was seen when you selected the XP entry?
Hopefully you removed the first and saw the new corrected one added in for the F letter. You're much closer now to having everything running. We simply have to find the last holdup and see that fixed to the need for a full reinstall of XP plus another repair of the 7 mbr.
�� Quote: Originally Posted by Night Hawk When going to restart what was seen when you selected the XP entry?
FILE \NST\ntldr
The selected entry could not be located because the application is either missing or corrupted.
�� Quote: Originally Posted by Night Hawk Hopefully you removed the first and saw the new corrected one added in for the F letter.
�� Quote: Originally Posted by Night Hawk You're much closer now to having everything running. We simply have to find the last holdup and see that fixed to the need for a full reinstall of XP plus another repair of the 7 mbr.
Since XP didn't load it's likely you will need to reinstall or perform a repair install of XP if you are not able to fix the "FILE \NST\ntldr" error you are mentioning. That tends to suggest that the installation may have incomplete to start with.
If you are forced into one of those two one guide explaining how to go about a repair install is seen at How to Perform a Windows XP Repair Install
If you are forced into one of those two one guide explaining how to go about a repair install is seen at How to Perform a Windows XP Repair Install
I already did a repair install, which didn't change anything except that I couldn't boot into either OS after, and had to use the rescue CD to get W7 working again.
So all I can think of is doing a new clean install of XP, and see if that works. Where is that damn "NST/ntldr" supposed to come from, if it didn't get installed the first time around?
So all I can think of is doing a new clean install of XP, and see if that works. Where is that damn "NST/ntldr" supposed to come from, if it didn't get installed the first time around?
Did you delete the entry for XP and then see a new one replace it in EasyBCD? When setting up dual boots here and having any problems loading any second even third installation the firrst set of entries would be wiped seeing a fresh entry even for the host OS.
Since you verfied all necessary boot files were present the refresh on them can sometime be all it takes to get a stubborn OS moving. For XP boot problems of all types there's a roubdup of all types with various other solutions. Boot Dual Missing Ntldr Vista Xp
(Note 7 still uses same type boot loader as Vista)
Since you verfied all necessary boot files were present the refresh on them can sometime be all it takes to get a stubborn OS moving. For XP boot problems of all types there's a roubdup of all types with various other solutions. Boot Dual Missing Ntldr Vista Xp
(Note 7 still uses same type boot loader as Vista)
Yes, I entered both drives new in EasyBCD.
I also just found out in the NeoSmart forum that I have to let EasyBCD add the drive "automatically", otherwise it will not work right! See "NST/ntldr" - The NeoSmart Forums, where I am advised to: Read the last two lines of my previous post, and stop changing the disk assignment.
That's why it's auto configure, to stop people pointing it to the wrong place.
I made a new clean install of XP tonight, and it booted fine, but W7 did not boot until I changed the BIOS back to default (RAID).
Then XP doesn't boot, neither in "normal" nor in "last good config".
I also just found out in the NeoSmart forum that I have to let EasyBCD add the drive "automatically", otherwise it will not work right! See "NST/ntldr" - The NeoSmart Forums, where I am advised to: Read the last two lines of my previous post, and stop changing the disk assignment.
That's why it's auto configure, to stop people pointing it to the wrong place.
I made a new clean install of XP tonight, and it booted fine, but W7 did not boot until I changed the BIOS back to default (RAID).
Then XP doesn't boot, neither in "normal" nor in "last good config".
I saw the thread you started over there while looking for some additional references and the reply as well about not all of the older wikis catching with the latest changes seen in the 2.0.2 release. "typical"!
As far as the drive mode that's been the main obstacle for XP all along and why I suggested finding someone running the 32bit flavor to see if the game would run on that. The 32bit 7 has quite a bit more backward compatibility to more then seen with the previous version it has been found.
In fact I slapped a fast install lately on an old XP clunker where every XP driver worked on 7! onboard sound, old video card, main chipset drivers, the works! But since that was to donated for student use the drive was wiped and I spent a good night downloading and installing the 100+ updates found for XP with SP3 already installed!
(Try 5am closing time for that one! sssslowww with repeat trips to the Windows update site)
If it runs on the 32bit the problem with drive modes would be solved for you rather then fussing with constant trips into the bios since XP isn't actually supported on that model to begin with. It would save all the headaches you've been running into.
At least you now know why the entry in the latest version of EasyBCD wasn't working for you. But the best idea is still considering a try of the game on the 32bit 7 especially since MS plans to repeat their reduced prices for the Home Premium edition this fall a year after 7's release.
"typical"!As far as the drive mode that's been the main obstacle for XP all along and why I suggested finding someone running the 32bit flavor to see if the game would run on that. The 32bit 7 has quite a bit more backward compatibility to more then seen with the previous version it has been found.
In fact I slapped a fast install lately on an old XP clunker where every XP driver worked on 7! onboard sound, old video card, main chipset drivers, the works! But since that was to donated for student use the drive was wiped and I spent a good night downloading and installing the 100+ updates found for XP with SP3 already installed!
(Try 5am closing time for that one! sssslowww with repeat trips to the Windows update site)
If it runs on the 32bit the problem with drive modes would be solved for you rather then fussing with constant trips into the bios since XP isn't actually supported on that model to begin with. It would save all the headaches you've been running into.
At least you now know why the entry in the latest version of EasyBCD wasn't working for you. But the best idea is still considering a try of the game on the 32bit 7 especially since MS plans to repeat their reduced prices for the Home Premium edition this fall a year after 7's release.
It's not just for the game I want to get XP working on the second drive. Now that I have an actual dual boot screen popping up it seems a shame we can't overcome the last hurdle of XP actually booting up! It booted fine as long as I had the BIOS set to IDE, but that didn't work for W7, so I had to reset it to default.
Have you gone to the Windows update site since you got XP running again? You might just run into some optional hardware updates for the sata/Raid controllers there as well as anything else not seen at the HP support site. You'll need them!
�� Quote: Originally Posted by Night Hawk Have you gone to the Windows update site since you got XP running again? You might just run into some optional hardware updates for the sata/Raid controllers there as well as anything else not seen at the HP support site. You'll need them!
That's always fun! What type of connection are you running there?
I know when swapping cases back and forth while working on a new build that will be seeing the 64bit Home Premium and reconnecting the main case later I had some fun getting back on with cable here.
The modem was turned off, unplugged, replugged, powered up again due to the other build grabbing it's own cofiguration. Looking under network adapters in the device manager is the first place to see is listed there. If you see more then one item the default you use is left enabled while anything else has to be disabled if not uninstalled.
I know when swapping cases back and forth while working on a new build that will be seeing the 64bit Home Premium and reconnecting the main case later I had some fun getting back on with cable here.
The modem was turned off, unplugged, replugged, powered up again due to the other build grabbing it's own cofiguration. Looking under network adapters in the device manager is the first place to see is listed there. If you see more then one item the default you use is left enabled while anything else has to be disabled if not uninstalled.
�� Quote: Originally Posted by Night Hawk That's always fun! What type of connection are you running there?
At first you may have to follow similar footsteps by looking over the ISP's own FFAQs. Adding a router in at first was a pain here for sure! That was solved however with a fast trip through the ISP's support pages.
I can't say this method would work well for you however depending on if you plugging into the router by usb or by a nic card installed in a pci slot to be hardwired out to the router. This would be a quick set of steps to take.
1) Review support for router as well as installation of software/drivers on XP
2) Review the Device Manager>network adapter sub section to if the adapter item is working properly with a right click for the properties screen and not seeing any yellow or red marked item(s).
Now depending on your ISP if you have an assigned user name/password you would then set up a new account in Outlook Express using that information to get mail going while if nothing is yellow marked in the network adapter sub.
3) Look at the "Network Connections" in the CP being XP there. It wouldn't be any good showing screens from the XP Mode for sure since that uses NAT virtual networking.
Your interest would be looking at the Local Area Connection Status to see if XP is all set as far as the router is concerned. Most likely XP is already synced with the router but may still need to get past that.
Have you connected with the same connection with XP previously with the router inline? If you start recycling power on both router and modem and synce the modem with the ISP while everything is shutdown you could lose the connection for 7.
The methods can be different at times between the two versions. Here while the router was inline it was still hardwired by the RJ-45 cables for both pc and modem.
That was solved however with a fast trip through the ISP's support pages.I can't say this method would work well for you however depending on if you plugging into the router by usb or by a nic card installed in a pci slot to be hardwired out to the router. This would be a quick set of steps to take.
1) Review support for router as well as installation of software/drivers on XP
2) Review the Device Manager>network adapter sub section to if the adapter item is working properly with a right click for the properties screen and not seeing any yellow or red marked item(s).
Now depending on your ISP if you have an assigned user name/password you would then set up a new account in Outlook Express using that information to get mail going while if nothing is yellow marked in the network adapter sub.
3) Look at the "Network Connections" in the CP being XP there. It wouldn't be any good showing screens from the XP Mode for sure since that uses NAT virtual networking.
Your interest would be looking at the Local Area Connection Status to see if XP is all set as far as the router is concerned. Most likely XP is already synced with the router but may still need to get past that.
Have you connected with the same connection with XP previously with the router inline? If you start recycling power on both router and modem and synce the modem with the ISP while everything is shutdown you could lose the connection for 7.
The methods can be different at times between the two versions. Here while the router was inline it was still hardwired by the RJ-45 cables for both pc and modem.
I have a cable connection that is "always on", and usually gets picked up by any system without entering user/pass, which I don't have anyway.
The only time you see that is with dsl more often where the ISP will provide the user name/password for their own mail servers. This would be mainly for OE, WMail, etc there.
The network connections however should show the incoming and outgoing packets. When first adding on a router here for 7 however you could see the established connection to the router using a wireless usb adapter even but not getting past the router to connect online.
The images attached here will basically show what to look for while in the Control Panel if you are still having connection problems. While this is all on the XP Mode here using the NAT option for network adapter these show a few different ways to tell if you are configured correctly.
You have to use the Network setup wizard or open up a command prompt to enter the "IPconfig /release" and "IPconfig /renew" commands as well as go through the wizard itself. If the few steps still get nowhere you will likely need to start a new thread since that gets into a different problem with wireless routers and XP for sure!
When talking with tech support when one ISP first started using them over strictly staying with the outdated hardwiring their visit the home techs were having a field day with the older version!
The network connections however should show the incoming and outgoing packets. When first adding on a router here for 7 however you could see the established connection to the router using a wireless usb adapter even but not getting past the router to connect online.
The images attached here will basically show what to look for while in the Control Panel if you are still having connection problems. While this is all on the XP Mode here using the NAT option for network adapter these show a few different ways to tell if you are configured correctly.
You have to use the Network setup wizard or open up a command prompt to enter the "IPconfig /release" and "IPconfig /renew" commands as well as go through the wizard itself. If the few steps still get nowhere you will likely need to start a new thread since that gets into a different problem with wireless routers and XP for sure!
When talking with tech support when one ISP first started using them over strictly staying with the outdated hardwiring their visit the home techs were having a field day with the older version!
Không có nhận xét nào:
Đăng nhận xét