Re: 160 WD slave drive
From: jimy (jimy_at_discussions.microsoft.com)
Date: 12/21/04
- Next message: Doug: "Network, high traffic on network adapter but nothing running."
- Previous message: Adrian: "Deleting Registry Keys"
- In reply to: Richard Urban: "Re: 160 WD slave drive"
- Next in thread: Nepatsfan: "Re: 160 WD slave drive"
- Reply: Nepatsfan: "Re: 160 WD slave drive"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Dec 2004 08:23:07 -0800
"Richard Urban" wrote:
> I just installed a WD 160 gig drive. It states emphatically in their
> instruction *** to use "their" supplied cables if you are going to be
> using cable select. I did - it works!
>
> --
>
> Regards:
>
> Richard Urban
>
> aka Crusty (-: Old B@stard :-)
>
> If you knew half as much as you think you know,
> You'd realize you didn't know what you thought you knew!
>
>
>
> "Menno Hershberger" <mhersh22@nosuchplace.net> wrote in message
> news:Xns95C5BB9F3C3ADbutter@daisymae.com...
> > I've dealt with three new Western Digital hard drives in the past two
> > weeks, one of which was a 160. The 160 had overlay software included to
> > make the >137 gig limit useable. Could be that wasn't installed properly.
> > What is interesting is that the cables that Western Digital includes with
> > their drives are NOT cable select, but the default jumper settings on the
> > drives ARE cable select.
> >
> > "Nepatsfan" <nepatsfan@SBXXXVIII.com> wrote in news:VqqdnfsrnN-L9VrcRVn-
> > gA@comcast.com:
> >
> >> How did you set up the jumpers? If you use the cable that came
> >> with your new drive and connect the first drive to the black
> >> connector and the second drive to the gray connector then you can
> >> set the jumpers on both drives to cable select. That's the
> >> preferred method.
> >>
> >> If you don't want to go this route then make sure that the first
> >> drive is set to master and the second to slave.
> >>
> >> If you want some better advice you might want to post this
> >> question to a newsgroup that's deals with hardware related
> >> issues.
> >>
> >> Nepatsfan
> >> "jimy" <jimy@discussions.microsoft.com> wrote in message
> >> news:888474DA-5757-4C9B-B0EA-7D405DC73D61@microsoft.com...
> >>> Installed a 160 gb WD slave drive, on startup the black screen
> >>> used to be on
> >>> for about 3 secs, now it is on for about 25 secs , with the
> >>> white dash
> >>> flashing. I know it has to do with the new slave, is there
> >>> anyway to shorten
> >>> startup on the slave.
> >>>
> >>> --
> >>> jimy
> >>
> >>
> >>
> >
> >
> >
> > --
> > -- Puritanism: the haunting fear that someone somewhere may be happy. --
>
>
>
Thanks for all the replys. I install the wd 160 using the oem cable and set
the wd 160 to slave, the oem drive is seagate 160 and Win XP even recognized
the drive as soon I booted. I then used the wd cd to set up the wd 160.
Everything works great except for the slow boot on the wd 160.
- Next message: Doug: "Network, high traffic on network adapter but nothing running."
- Previous message: Adrian: "Deleting Registry Keys"
- In reply to: Richard Urban: "Re: 160 WD slave drive"
- Next in thread: Nepatsfan: "Re: 160 WD slave drive"
- Reply: Nepatsfan: "Re: 160 WD slave drive"
- Messages sorted by: [ date ] [ thread ]