Ghost and XP

[reboot]

Here's the scenario. I just wondered if there were an easier fix than a "Repair" to get it all working.
Good running system XP Pro on an 8 gig HD, FAT32.
Ghosted it to a 30 gig Maxtor.
Pulled the old drive, insert new, set BIOS, restart.
Computer boots to the fancy blue XP screen, and stops.
I'm thinking it's because XP doesn't know that it's a different hard drive, and can't update the reg.
Tried safe mode, tried command prompt, tried a whole bunch of things.
Doesn't matter what keys one presses, nor in what order, the only way to do anything is to give it a hard reset.
I'm running a repair as I type this, and it's doing a complete install, even prompted for the CD key. I'm probably going to end up with 2 versions of XP on the thing, or some other ridiculous configuration.
There must be a better way.
Any ideas why it won't boot all the way, other than what I suggested?
Any better fixes than running the repair option (which I'm still not sure will work).
As a last resort, I'll wipe the 30 gig again, restart to the 8 gig, do GLC's enum trick for XP, ghost the drive again, and see what happens...I still have a feeling I'm going to be doing a complete install.

[reboot]

OK, got it all back, except my internet has gone south on the comp. I've removed and reinstalled all networking components, run the wizard on a working comp, and made the diskette, gone through all the motions, released and renewed the IP, flushed the DNS cache, and STILL can't get on the net...sigh...

[Floppyman]

Can you ping? How about a local network (i.e. like simple filesharing)? Just wondering whether it might be the hardware. Also does the access come through the router or straight to the ISP (was thinking of MAC addresses)? HTH

[reboot]

Access is through router. It can't seem to get a connection of any sort. No packets sent/recieved.
Can ping 127.0.0.1 no problem.
Can't share files.
IE gives it's typical DNS server unavailable error.
Seems the computer is getting a very strange IP from the router, and not one that's within it's 192.168.2.100-192.168.2.199 range. It's getting one that is 169.254.95.228, which is IANA special use IP, NameServer: BLACKHOLE-1.IANA.ORG
Why can't the comp get it's IP from the router like it's supposed to? DHCP is enabled on the router, and working perfectly for two others on the LAN...

[Floppyman]

Hi Jim,

Are you sure they NIC is functioning properly? Have you tried reinstalling the drivers? Have you tried assigning in an IP address? Can you ping to this machine (both with/without an assigned IP address)?

[reboot]

I can't ping TO it nor FROM it. All link lights are lit.
Uninstalled and removed NIC, restart, shutdown, reinstall NIC, restart, reinstall networking components (TCP/IP, Sharing, MS), same problem.
Reset router to factory defaults, turned off firewall...
Is there a way to save the configuration from the old HD (networking stuff) and copy it to the new? What files/folders would I need to do that?
I'd ghost again, but then I'd be back to the original problem.
Not sure which is the easiest to solve.
Maybe I could boot to safe mode on the old disk, remove hard drives and IDE controllers from device manager, then ghost, then swap drives...
Maybe just clone the Windows folder from old to new in a different computer? But that would probably get me back to an invalid boot because of the hard drive again.

[TEEB]

Have you tried powering down everything, computer router and modem. The power up Modem let it boot up then the router let it boot up and then the computer. Worked for me when I was having problems!!

[reboot]

Yup, been there, done that, got the T-shirt.
The other two systems log on right away, and start surfing.
This one, keeps getting the IP I mentioned above. I can't figure out how the router would let the computer get an IP from an external source.
I even installed a different NIC.
I've wasted 2 days on this, and it's getting to me.
There has to be a solution for either problem A (getting it to boot to the new hd after a ghost), or B getting it to get a REAL IP from the router.
Tomorrow I'm going to try removing the hard drives and IDE controllers from device mangler, then ghosting it, then see if it will boot, in the mean time I sure would like an answer to both problems for future reference.

[glc]

169.254.x.x IP's are indicative of a bad NIC, bad cable, bad router port, or trashed TCP/IP. That's the IP range that Windows gives itself when it can't see past its own nose.

[David_Jones]

With respect to problem A, I wonder if it would make any difference to restore the Ghost image to a partition that is exactly the same size as the original was (assuming a partition image)?

Don't see why, but you never know....

David.

[reboot]

I have a feeling it's a trashed TCP/IP, because the other computers get an IP and log onto the net no matter what port I use on the router.
Rebuilding TCP/IP on a WinXP box isn't as easy as it sounds. Uninstall is not available. I'm working through a manual delete of it, but what a headache, trying to find just the right file(s) and place(s) in the registry to delete...
Might have to search the MSKB for this one too.

[doctorgonzo]

The IS guy I work with just recently me an article on rebuilding TCP/IP in XP. I will try to find it.

Ah, here it is: http://www.mikeshardware.com/tips/ti...ml#anchor12531

[reboot]

Excellent, thankyou! Going to try it this afternoon.

[TEEB]

JIm: After all the time you've spent on this? Wouldn't it have been easier to just do a format and reinstall? I'm sure you must have a reason for not doing this, but, I don't know what it is.

[TEEB]

How's this for a coincidence? After I made the above post my wife calls me from work and tells me she couldn't get on the internet this morning before work, and could I fix it?

I checked it out and sure enough she can't get on. So I do the unusual things and still can't get on. So I change the cable. That' doesn't help. I look at the NIC and can't see a link light. So I replace the NIC, still can't get on. So I check my settings and find my IP address is 169.254 and 2 other numbers. I think about your problem and go to my computer and find this thread to check the numbers you reported, after confirming the first two numbers were the same I went back to see if the last two were the same.
When I got back the IP had changed to 192.168.1.102 . My little network now seems to be working fine.
Don't know if this will help you but it can't hurt!!!

[reboot]

A format/reinstall is an option, but I'm a stubborn cuss, and want it to work the other way, for my own satisfaction in getting it sorted, as well as not having to reinstall all the software and updates, which would probably have been quicker in hindsight.

[reboot]

I got it sorted. I'm not exactly sure which bit I did that allowed it to work, but here's what I did.
I booted to the old disk, cleaned everything out that I could find, temp, cookies and stuff.
Removed the disk drives and IDE controllers from device mangler.
Refdisked the new drive.
Put them both in the system, booted to the ghost disk, and did a partition to partition ghost.
Took the old drive out, mount the new as primary master, and it worked.