Does everything I've read on the postings of this thread, as well as the linked reinstall site I've gone to, apply to Dell's OS XP SP2 version - just as if it were/is a normal store-bought version?
My Dell disk says line by line:
Operating System
Already installed on your computer
Reinstallation CD
Microsoft Windows XP Home Edition
Service Pack 2
I just now broke the CD seal and used it to format and install XP SP2 onto a brand new Barracuda. I did this in order to see if I could see what's on my unbootable disk.
My OS was installed by Dell and I've done nothing to it except the MS patches.
Now it won't boot, and it's because I just installed Ghost from Systemworks 2003. It installed OK but when I stuck two SD readers in the two USB slots and tried to use Ghost to clone one SD from another, the machine hangs.
I went through the on-screen choices and think I made all the correct ones (it's the first time I've ever tried to use Ghost), Ghost went into its process and quickly locked up on a DOS-shell type screen with an hourglass figure that hung. Locked the machine and required a re-boot, wherein it then booted to a brand new DOS partition with nothing but some primitive DOS stuff and some Norton files.
Norton had created it's own little 8MB boot partition at the C:> prompt.
Using DIR and trying all the drive letters I couldn't find any other drives or files, but I probably don't know how to look. That scared me though.
When I booted from the new Barracude I could see all of my system (whew) and the new Ghost-created partition named "-V???????? (question marks stand for whatever the actual numbers & letters were). I thought if I deleted the partition I would be back to having a machine that boots into XP instead of Norton's DOS partition. Duh.
The primary drive won't boot now. If I knew what I was doing with Windows I'm sure I could go in and replace or repair a file or two and make it bootable again, since I'm pretty sure now Norton didn't ruin underlying structure, or maybe it did. I've always heard that Ghost in the hands of a fool can do terrible things and I first thought I'd done a terrible thing. But since my stuff is all still there and I can get to it via another bootable disk, it's not too terrible.
Should I try and do a repair/reinstall of my installed OS and will I be given the "R" choice (not the R in Recovery Console, I'm reading to stay away from that) at the last minute before pushing the button and possibly wiping out everything? Is it true I _won't_ wipe out everything if I do push the button?
If I don't get the R and don't want to push the button, can I safely back out at that point?
What's the best way to back up the stuff on the HD that won't boot? I need to do that before I start messing with reinstalling/repairing the OS.
Do you think the reason Ghost hung up in my system (Pentium D, 3GB, XP SP2 is because Systemworks 2003 isn't compatible with newer, faster hardware? My SW2003 is regstered to me so I should have done an update check before running it. I probably also should have disabled my virus/spyware checkers just because it's a good idea.
Since the two drives I was trying to clone were external SD cards, I figured if I messed anything up it would only affect the two external SD drives. I didn't expect Norton to go in and corrupt the basic structure of my system like it has. Once it hung, the damage was done. There's no way to escape the hang and allow Norton to clean itself up.
The Ghost menu made it look so simple and easy, cloning one disk to another. This is first serious mistake I've made with my new computer.
Ghost is the only thing Norton on my HD.
I also have a squeaky clean disk with no accumulated or other crud (all the Dell crap was the first stuff to go). It's also defragged frequently, so all the OS stuff should be in the same place.
I'm not trying to redirect this thread to Ghost problems. I'm just giving background for how I wound up needing to do a repair/reinstall of XP Home, SP2
Also, what utility should I have in my arsenal of problem solvers that would boot the system and automatically find whatever the XP boot problem is and then repair it? Surely something like that must exist.
Any responses/comments appreciated.
Thanks, Mike