Re: Help! What did my new SATA drive do to XP?
From: johnf (john_f_at_bigREMOVEpond.net.au)
Date: 07/03/04
- Next message: veris and amee young: "Norton disk doctor or XP scan disk not working in XP pro."
- Previous message: John R Weiss: "Re: Java Virtual Machine"
- In reply to: BAR: "Re: Help! What did my new SATA drive do to XP?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 3 Jul 2004 11:34:33 +1000
Thanks, just what I needed to know, that explains why it wouldn't boot from
the SATA.
Repair Install is no problem, I've done that before - now to make sure I
have the right drivers for the floppy.
Would you know whether that is the MaxBlast 3.6 software (which I've already
downloaded & transferred to floppy?)
Now I only have to resolve the slow boot problem :(
-- johnf > OK Johnf > > You have severral key problems. > > No. 1 - It's fine to install a new device [including HDD] and Windows > wioll recognise it and install drivers etc. Just as you did and have > found that the SATA HDD worked fine. > > No. 2 - XP is very fussy regarding moving System image to a new HDD and > then attempting to boot off it. Now many of us have moved systems > across to new drives and found that the disk would boot. However, a > SATA drive is so different that Windows will not boot. > > You will need to do a repair installation. > > Get the XP CD and also make up a floppy with the RAID drivers for the > SATA disk. Boot off the XP CD and when prompted to type in F6 to > install SCSI or RAID drives, make sure you press the F6 key. Load in > the Flkopp and then it will proceed. At the first installation window, > choose install. AT the second installation window choose REPAIR. > > > > "Nospam" wrote: > >> johnf, >> >> I'd check the bios and ensure the proper settings are set and that it >> is the latest bios. >> >> I have an Albatron 865 pro ver 2 mobo and I recently found out that it >> won't overclock if SATA drives are connected to the mobo (go >> figure)...Albatron is working on that. >> >> Nospam >> >> "johnf" <john_f@bigREMOVEpond.net.au> wrote in message >> news:eJKuc2CYEHA.2364@TK2MSFTNGP12.phx.gbl... >>> >>>> "johnf" <john_f@bigREMOVEpond.net.au> wrote in message >>>> news:uAo$SMCYEHA.3100@TK2MSFTNGP09.phx.gbl... >>>>> I just bought a Maxtor 6Y080M0 S-ata drive, temporarily replaced my >>>>> second (data only) HD with it, partitioned it & imaged across both >>>>> my OS & data partitions from my first HD. >>>>> Checked in Explorer and everything looked fine on the new drive, so >>>>> I made it the 1st. boot device. >>>>> On startup, it took 10 minutes to get to the point where it wouldn't >>>>> recognise the new drive (that's a problem to be resolved later). >>>>> >>>>> Now, on putting my original 2 drives back, it still takes abt 10 >>>>> minutes to >>>>> boot up - the boot sequence goes through all the screens and >>>>> processes it's >>>>> supposed to, but in slo-mo, once XP loads, it's back to full speed, >>>>> Ai Booster says it's running at 2.806GB. >>>>> If I go into BIOS, it takes abt. 10 seconds to react after arrowing >>>>> to a new >>>>> field, so even that's affected. >>>>> >>>>> That's all I did, partition & drive-copy across - no software >>>>> changes, does >>>>> anyone have a clue what may have changed? >>>>> BTW, sys restore has no impact. >>>>> >>>>> P4 / 2.8, Asus P4P800-E Deluxe Mobo, 512 RAM. >>>>> >>>>> -- >>>>> johnf >>>>> >>>> XP does not like to be moved. Have you tried to do a Repair Install? >>>> You'll have to download all the updates again but that might get you >>>> running good again. IMO fixing xp is just adding problems. Like >>>> fixing a flat tire by putting a patch on top of a previous patch. >>>> Best to reinstall xp if you can. >>> >>> Hi, Rob, thanks, I thought about that but it doesn't add up. >>> I've imaged XP a few times as I upgraded my drives, but only IDE to >>> IDE, >> not >>> SATA. >>> But that doesn't explain how I've inherited this problem which is >>> still there even after removing the new drive & reinstating the >>> original (unchanged) XP drive as it was originally. >>> It's not as though it's a problem caused by a faulty copy to the SATA. >>> -- >>> >>> johnf
- Next message: veris and amee young: "Norton disk doctor or XP scan disk not working in XP pro."
- Previous message: John R Weiss: "Re: Java Virtual Machine"
- In reply to: BAR: "Re: Help! What did my new SATA drive do to XP?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
