Xp wont boot after Ghosting with Norton 9.0

[jpope1979]

The hard drive here at my office is heading south. I'm buying time as we speak. My pc is a crucial unit and has a gob of information needed to run the business. The owner bought a new HD (WD Caviar, 7200rpm 160gig EIDE) for me to copy to so things would set right.


I first used WD's Datalife copy utilities they rave about on their website. After doing so the Hard drive shows XP booting but, when normally you'd get your login screen, i got the pretty blue login looking screen with only a small winXP logo showing. From there nothing happens.

Thinking it may be the WD's software i purchased Norton Ghost 9.0(Which BTW, Microsoft lists on their site as a premier copy/backup utility). Anyhoo, I first made a Copy using Ghost this time but it did the same thing. After struggling with the thought of "why this isn't working" i decided to try just doing a Backup/restore using norton and see what happens. I made a backup then used nortons recovery tools to restore the backup file i had made previously to the old drive. Norton followed through with no errors and everything looked fine. I then set the new drive as the master in the bios and booted up and the same damn thing happend. Mind you i don't think it supposed to be this hard to copy something. Am i missing something? A process or step. I've been doing stuff like this since i was 15 and it doesn't make sence that it would not fully work properly. Which leads me to beleive theres something i'm not doing. Any help would be awesomely appreciated or any point in the right direction too. Thanks in advance to anyone who reads this whole thing and replies.

sincerely,
Jason Pope

[sataraid0]

Hmmm, Welcome to PCMechanic, and don't panic.

Sorry that I am unable to help you at this point, however, please be patient and I'm sure someone here will have some good advise for you.

The biggest mistake of someone in your position right now, is to panic and do some things that should not be done. Wait and get the right advise before doing anything to destroy data you want to save.

Sorry, that is the best I can do right now..............Regards.........Sterling

[Roadie]

jason pope .. i am having the exact same prob as you are
i used WD's tool to copy the partition of c: to my new drive
...3 hrs ... sick ..it didnt work .. but i got an error .. missing ntdlr .. or whatever
i copied it from the other drive .. it booted .. to the same screen you said you got ... a small xp logo with working mouse
... not being discouraged .. i tried norton ghost 9.0
ghosted my c drive
booted to same logo
i have also tried making a backup image of c drive and using it on new hd .. i have many hds .. so no prob for space that way ..but to no avial again .. it booted to the little logo .. no user accounts .. no desktop .. nothing

please if anyone knows whats wrong .. please help .. im self taught over many years ..and this is the largest pain in the arse i have ever dealt with ..
ive done this before .. but not on xp .. and had no problem. . so whats the deal .. is microsoft worried that we are selling hdds with their os on it ?

i just want to put my bigger drive in without having to install the million progs i have on it .. it takes too long and my os is stable and works great now as it is


im new to this forum and joined so i could post this . i hope to find a solution soon .. this is very discouraging

Frustrated

[GraemeM]

I cloned using WD Data Lifeguard 11. It loads XP but get stuck on teh blue loading screen or whatever it is. THen I used Norton Ghost from SystemWorks 2003, and it worked fine. With the WD program, it said there were 2 errors, but they weren't ciritical files. But one of them was a pagefile, which I think XP needs. What about backing up all the data onto DVD's or something and starting fresh? I don't really know how to fix the problem, there isn't a lot you can do wrong in the cloning process, so I'm not sure

[glc]

When cloning fails like this, I assume that there's file corruption. In these cases, it's best to install your operating system and applications fresh on the new drive, then slave the old drive in to copy over the files you need.

[Skalar]

Hi,
Just face the same problem a week ago using GHOST 7.5.
Symantech recommended using the advanced option: add -IR to the ghost command line -> it should work (it works 4 me).

Skalar

[commach]

Set Source hdd to master. Destination ( new ) hdd to slave.
Assign any letter to the new hdd.
Then switch the letters of both hdd,
that means desinationt hdd becomes C and old hdd becomes the letter that u chose.
On how to do that, refer to the following website:
http://support.microsoft.com/?kbid=223188
The step for switching the drive letters is very important. *Take note*
I rebooted after this step ... but I don't think its necessary.
After switching, use ghost to clone the hdd.

[Roadie]

YES >> Finally !!!

after doing multiple ghosts . i went back and tried the image i originally made .

i used the back up image on my new drive ... it worked .. i unpluged c:
plugged in K: as the master on ide 1 and that was it .. it booted .. everything works
its like nothing happened
so try it .. make a back up image on a separate hard drive .. cuz the image was the size of the hd i was backing up as i used no compression
then run the restore drive to your new drive .. this may cause a problem for those of you who do not have more then 2 hdds .. you would have to use compression on the drive ..and copy it to your c: .. or to your new hd .. but have it partitioned to 2 hds .. then you could copy it to the extended partition and back up the primary partition from the extended partition where you have the backup image
.
i hope all the above makes sense .. ihave a few beers in me now
and im quite happy to be working on my new .. faster hd ... from 8min boot to less then 2 .. im very happy

[je1279]

i have been having this same exact issue and i have tried about everything i could think of to fix it. hopefully restoring the image from the new drive will work. i was just so happy to find a post where others were having the same problems.