Problems with Installing a fresh copy of HP, Norton, Master / Slave Issues, Disk Management

    Date: 04/30/06 (Computer Geeks)    Keywords: software, virus, antivirus, spyware



    An aging HP Walmart computer.  After a few years of it's user not taking care of it, we decided it was time to start from scratch.  Got a new(er) HDD, 7200 to replace it's stock 5400 drive.  The old drive had the 2 partitions, the 35GB Windows Install, and a 5 GB Restore Partition (C:\ and D:\, respectively)
     
    Because i wanted to transfer data from the old HD to the new one, I installed the new HDD in the machine as a slave to the first drive, on the same chain.  Loaded up the old HDD and it's copy of Windows, did a Quick NTFS format on the new HDD, and labeled it drive N:\.  I shut down, and put a new XP SP2 disc in the drive and attempted to boot from the CD to do the install.  Each time, I got a BSOD (Session_3) error.  Disc diagnostics show the HD is ok.  So, I booted into Windows off the old drive, and ran the XP SP2 installer from within windows.(Complete install on the new, empty drive)  Targeted the new drive as the volume for install, and let 'er rip.  All is good.
     
    When I finish with all of the updates, software installs, etc, I install Norton Systemworks 2006.  No flames here, please, this was at the CPU owners request.  This of course, installs Norton GoBack.  Whether this plays a role in this, I don't know, but I place it here in case it shed light on anything.  Install goes fine, system runs much smoother.
     
    As I am finishing up, I power down the machine, and disconnect the old HDD.  Big Problem, I get a gb_ui_support (1147) error.  This is, of course, a Goback error.  I cannot seem to get passed this.  The new OS will not boot without the old drive being installed (and still set as master, BTW)  I attempted to disable goback on the volume, but got the same boot issue.
     
    I go into the BIOS, set them to defaults, no change.  I then boot into the new HDD and go into disk management, and see this:
     
    So...the OLD HDD is the System drive?  Or is it just seeing the old windows install on there? Shouldn't it just be a standard volume? I thought about the issues of the drive letter being the culprit, but I find I am unable to change the drive letters in Windows (it will not allow me to change it) and before I attempt to do it via command line, I thought I'd ask here first. To add insult to injury, the old HDD with Windows spontaneously reboots when I try and boot into it. I'm assuming Windows is corrupted. I also ran Norton AntiVirus on ALL drives. Spyware was found, but no viruses.
     
    In any event, I'm out of ideas to get the system to boot with just the new HDD. Any thoughts? Thanks!

    Source: http://community.livejournal.com/computergeeks/918594.html

« translate this script for me || What do we think »


antivirus | apache | asp | blogging | browser | bugtracking | cms | crm | css | database | ebay | ecommerce | google | hosting | html | java | jsp | linux | microsoft | mysql | offshore | offshoring | oscommerce | php | postgresql | programming | rss | security | seo | shopping | software | spam | spyware | sql | technology | templates | tracker | virus | web | xml | yahoo | home