WD 30 gig HD
Results 1 to 6 of 6

Thread: WD 30 gig HD

  1. #1
    Registered User
    Join Date
    Nov 1999
    Location
    Pocatello, ID, USA
    Posts
    99

    Wink WD 30 gig HD

    I spent part of my weekend, doing what I thought would be a simple installation of an additional, and larger hard drive.

    It started out great...the screws fit, the cable matched (pin 1 to pin 1), even had the right number of available molex connectors.

    I set the old drive as a Slave, and the new drive as a Master, ran Autodetect in the BIOS. Everything checked out beautifully. The BIOS detected everything. WOOHOO!!

    I booted using the WD Data Lifeguard utility, ran EZ Install, and got the new drive ready to accept data.

    I ghosted the information from the old drive to the new drive, with absolutely no problems whatsoever.

    EGADS!!.....WD Data Lifeguard converted the new drive to FAT32...my old drive was FAT16. No problem, Norton's Ghost did it's job beautifully. I'm using the new drive now.

    Where my problem lies, is that after ghosting the data from the old drive to the new, and running the checks on the new drive to make sure that everything is cool (and it is). I formatted the old drive, and set it as the Slave. Yup, jumper setttings are correct, BIOS detects it as a Primary Slave, C.H.S. is correct. Couldn't ask for anything more right??

    Wrong. For some reason, when I start the computer, it hangs a little during the boot. I corrected that by going back into the BIOS, and going from Autodetect to User defined settings, using the C.H.S. information from each drive. When Windows (ME) starts, it tries to detect the new hardware, and then it hangs up. The Windows detection stops responding, and the only way I can shut down is by the ole Ctrl-Alt-Del method.

    To make matters worse. I attempted to partition the new drive using Partition Magic 5.0. When applying the changes, I got a message saying the computer would reboot, and make the changes in DOS. The computer didn'treboot into DOS, and the changes didn't take.

    Has anyone else run into these problems? If so, what were the fixes? Do I need to clean everything off both drives and start fresh?
    I really am trying to understand your point of view, but I can't seem to stick my head that far up my A$$

  2. #2
    Registered User Lycia's Avatar
    Join Date
    Feb 2001
    Location
    San Francisco, CA USA
    Posts
    1,862

    Post

    First off, when I set up a new hardrive to replace the old one I usually set the new one to slave old is still master. If it's a Western Digital Drive, I always use the Data Lifgaurd tools to copy the contents of old to new. Data Lifeguard will automatically partition and set at fat32 the new drive.

    Have you tried booting with jsut one or the other hard drive?
    "There is always a need for intoxication: China has opium, Islam has hashish, the West has woman."
    André Malraux
    (1901-1976)


    "Don't let worry kill you -- let the church help."

  3. #3
    Registered User
    Join Date
    Nov 1999
    Location
    Pocatello, ID, USA
    Posts
    99

    Wink

    Originally posted by Lycia:
    First off, when I set up a new hardrive to replace the old one I usually set the new one to slave old is still master. If it's a Western Digital Drive, I always use the Data Lifgaurd tools to copy the contents of old to new. Data Lifeguard will automatically partition and set at fat32 the new drive.

    Have you tried booting with jsut one or the other hard drive?
    Thanks for your reply.

    So right off the bat, I did things backwards by not setting the old as master? Sheesh.

    I am able to boot up completely with the new drive set as the master, and I'm currently using it. I'm just not able to boot up completely with both drives installed, the new one being the master, and the old one being the slave. Currently, I have the old drive disconnected.

    I didn't use Data Lifeguard to transfer files because I understood it would not transfer all the files like Norton's Ghost would. Perhaps my cockiness of thinking this would be a cakewalk got the better of me. :-/

    As far as the new drive being FAT32, that really isn't an issue with me, I had planned on converting anyway, and it saved me a few steps. Especially since I'd have more freedom to partition to a desired number and size of partitions.

    I really am trying to understand your point of view, but I can't seem to stick my head that far up my A$$

  4. #4
    Junior Member
    Join Date
    May 2001
    Location
    Midwest
    Posts
    4

    Post

    I have also a Western Digital hard drive and I had the same problems... When the EZ Bios comes up it hangs just for a few seconds.. then goes.. I corrected this by changing the jump on the hard drive... I found out there is two ways to make it primary.. but the best way to make it stop hanging is to have it the way it came in the package... the jumper on the bottom middle of the pins. After I did this.. it didn't stop to think which is the primary.. it loaded a lot faster... I don't know if this is the same for you but that may give you an idea.. It seems more just like a BIOS or Jumper setting than the information on it... I would format the drive but just back up the programs you want to get a fresher start..

  5. #5
    Registered User Lycia's Avatar
    Join Date
    Feb 2001
    Location
    San Francisco, CA USA
    Posts
    1,862

    Post

    Originally posted by Dav:
    Originally posted by Lycia:
    First off, when I set up a new hardrive to replace the old one I usually set the new one to slave old is still master. If it's a Western Digital Drive, I always use the Data Lifgaurd tools to copy the contents of old to new. Data Lifeguard will automatically partition and set at fat32 the new drive.

    Have you tried booting with jsut one or the other hard drive?
    Thanks for your reply.

    So right off the bat, I did things backwards by not setting the old as master? Sheesh.

    I am able to boot up completely with the new drive set as the master, and I'm currently using it. I'm just not able to boot up completely with both drives installed, the new one being the master, and the old one being the slave. Currently, I have the old drive disconnected.

    I didn't use Data Lifeguard to transfer files because I understood it would not transfer all the files like Norton's Ghost would. Perhaps my cockiness of thinking this would be a cakewalk got the better of me. :-/

    As far as the new drive being FAT32, that really isn't an issue with me, I had planned on converting anyway, and it saved me a few steps. Especially since I'd have more freedom to partition to a desired number and size of partitions.

    If you have a drive over 2 gigs, you want Fat32.

    As for how you set up your drive, well, you seem to be doing to many steps...

    WD's Data Lifeguards drive setup copies the entire contents of a drive and sets the partition onto the new drive. Whoever told you it didn't copy the entire contents of the drive was confused.

    What you should do is...Since the new drive works by itself, then there is a setting wrong on one of the drives. In order to use both drives there has to be a Master/Slave relation. So leaving the new drive in it's default pin position will not work, it has to be at master. Also, make sure the second drive is set to Slave and not cable select.
    Also check the cables themselves, are you sure that the Slave/Old Drive is pin 1 to the cable's pin 1. Have you tried setting both to master, and setting the old drive to the secondary IDE channel as master.

    This is my procedure on setting up new drives, I usually always use WD drives..
    1. Power off system, install new drive as slave, making sure old drive is master.
    2. Insert Data Lifeguard Tools disk, power on system.
    3. Choose Drive set up, make sure that I use the maximum amount of space on drive, such as Fat32. Also, need to make sure the Destination Drive is drive 2 and source drive is Drive 1.
    4. sit back and wait. After it's copied, reverse the master/Slave setting, and reverse the drive on the end of the IDE Cable. Reboot.
    "There is always a need for intoxication: China has opium, Islam has hashish, the West has woman."
    André Malraux
    (1901-1976)


    "Don't let worry kill you -- let the church help."

  6. #6
    Registered User
    Join Date
    Nov 1999
    Location
    Pocatello, ID, USA
    Posts
    99

    Talking

    Originally posted by Lycia:
    <STRONG>

    If you have a drive over 2 gigs, you want Fat32.

    As for how you set up your drive, well, you seem to be doing to many steps...

    WD's Data Lifeguards drive setup copies the entire contents of a drive and sets the partition onto the new drive. Whoever told you it didn't copy the entire contents of the drive was confused.

    What you should do is...Since the new drive works by itself, then there is a setting wrong on one of the drives. In order to use both drives there has to be a Master/Slave relation. So leaving the new drive in it's default pin position will not work, it has to be at master. Also, make sure the second drive is set to Slave and not cable select.
    Also check the cables themselves, are you sure that the Slave/Old Drive is pin 1 to the cable's pin 1. Have you tried setting both to master, and setting the old drive to the secondary IDE channel as master.

    This is my procedure on setting up new drives, I usually always use WD drives..
    1. Power off system, install new drive as slave, making sure old drive is master.
    2. Insert Data Lifeguard Tools disk, power on system.
    3. Choose Drive set up, make sure that I use the maximum amount of space on drive, such as Fat32. Also, need to make sure the Destination Drive is drive 2 and source drive is Drive 1.
    4. sit back and wait. After it's copied, reverse the master/Slave setting, and reverse the drive on the end of the IDE Cable. Reboot.</STRONG>
    Comparing your steps, to what I did, your absolutely correct. I did way too much. I also believe I added to the problem when I formatted the old drive (the 10 gig), as I formatted it by booting with a system disk, then ran format.

    Thinking about it, doing that formats the drive in FAT16, and not FAT32. I'm thinking this may be part of why Windows is having difficulty detecting the new drive, as the new drive is FAT32.

    No one told me that "Data Lifeguard" would only copy system files...thats what I read. Again, it becomes apparent I didn't read it close enough, and got too darn cocky for my own good.

    I will go back, and repostion the jumper on the drive. Yes, I did set it to the "Master" position. A real good suggestion there by the way.

    I really want to thank you for your assistance. I guess it's a male thing, or just something I do to make things harder than what it needs to be.
    <IMG SRC="smilies/eek.gif" border="0">
    I really am trying to understand your point of view, but I can't seem to stick my head that far up my A$$

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •