No Login screen after using Ghost

[Noghri2112]

I am trying to help my brother-in-law move his data on a 20GB drive to a new 80GB drive. The 20GB is setup in 2 partitions(10GB each). Right now, he has the 20GB setup as primary hard drive. When I have him ghost the C: partition to the first partition on the 80GB, it ghosts fine. But when he disconnects the 20GB drive and I have him set the 80GB as Primary and move it to the Primary connector on IDE cable, it starts to boot up. He gets the Windows XP Home screen, but when it is supposed to show all the user accounts to login, they never show up. It just shows a blue screen(NOT Blue screen of death) that says Windows XP. If I have him install the 20GB as the slave device, it boots up fine.

I've done this many times before with my Windows XP(going from 40GB to 120GB) using ghost.

Any ideas?

 

[tomwolfman]

ive had the exact same problem with my 2 drives .when i transfer everything it'll boot to the xp screen but works fine as a slave .i'm goin to try again shortly maxtor say to set the new drive jumpers for cable select ,did you auto detect it in the bios when booting or try checking it with partition magic boot floopies.can't think of anything else not too well up on it

 

[tomwolfman]

i got mine to work this time.connected the new 80gb on its own(connected it to prim master and set jumper for cs) and ghosted it from a dvd-r.then added the old drive to prim slave (also set to cs).Had a lot of trouble the last time

 

[redbeard1]

It may be that it has to do with that he tried to do a single partition, instead of the whole driven including both partitions, at once. A friend was having this issue and found some info on it, unfortunately I forget where, though I think it may have been from the symantec knowledge base. Part of how he fixed it was to boot from a 98/me boot disk and use the fdisk /mbr command. Even though the drive is ntfs, there is some sort of ID stored in the master boot record that fdisk removes and then on the next normal boot, XP recreates it. This issue sometimes comes up when you use ghost to only do a partition instead of the whole drive, which then causes some sort of issue with that ID and XP.

What version of ghost is he using. There was some issues with older versions and XP. Ghost 2003 fixed those problems.

 

[Noghri2112]

Thanks for the suggestions! I will have to have him try it tonight if he has time. I forgot to mention, we did try setting the drive to Cable Select and still same issue. I did a search on Google and found a couple other sites where people had the same exact issue. I think we have Ghost 2002. I'll have to double check.

I think the BIOS is set to AutoDetect for Hard drives, but I can't be too sure. I'll have him check that too. I had him go into FDISK after setting new hard drive to primary drive and setting the 1st partition to active, but that didn't fix issue. I will try your suggestions of running the fdisk /mbr to fix boot record and also setting both drives to CS. I know the new 80GB is a Maxtor. It was the one on sale at Office Depot couple weeks ago for like $30 after rebates and coupons. The old drive is a Maxtor too I think.

Specs of the machine are:
AMD XP2500+
MSI K7N2L(i think)
Sounblaster Live
TNT2
256MB RAM DDR

 

[tomwolfman]

is it the maxtor 80gb 7200 8mb cache? ,same one i had prob with