HDD detection problem on Asus A7V8X-MX

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

Machine spec:
Asus A7V8X-MX
Athlon XP2600
512MB DDR266
Integrated audio, video
WDC WD800JB-00FMA0 HDD 80 GB
ASUS CRW5232AS CD rewriter

There have been a few instances of it failing to detect the HDD on
startup, or taking a very long time to complete detection. The BIOS
settings are to auto detect the HDD each time the machine starts. This
is a new computer only 3 months old.

On this occasion after "Primary master hard disk fail" was reported I
went into the BIOS settings and attempted to have the drive auto
detected by the setup program, which also failed. However on the next
power up of the machine the HDD was detected and I was able to get the
HDD parameters entered into the BIOS.

On other occasions that I have observed, auto detection has been
extremely slow, and/or boot times have been extremely slow to complete
booting and loading Windows XP.

The power supply voltage monitor reads the following voltages:

Vcore 1.71 V
3.3v 3.34 V
5.0v 4.91 V
12v 11.55 V

CPU temp 32°C
MB temp 25°C

Bios revision: 1003 (current release is 1006). No specific related
issues addressed by any released BIOS updates.

Have looked in the case and can see no problems, all connectors and
jumpers on the HDD appear to be properly seated.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

WD. Yep, use those alot.
My standard blurb for WDs standalone is do not use CS. Do not use any
ribbon cable except spec 80 wire, 18 inches long. Do not place on middle,
use end of ribbon cable connection. Remove all jumpers from the drive, this
is standalone or master w/o slave setting.
"Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
news:1vENc.753$zS6.97531@news02.tsnz.net...
> Machine spec:
> Asus A7V8X-MX
> Athlon XP2600
> 512MB DDR266
> Integrated audio, video
> WDC WD800JB-00FMA0 HDD 80 GB
> ASUS CRW5232AS CD rewriter
>
> There have been a few instances of it failing to detect the HDD on
> startup, or taking a very long time to complete detection. The BIOS
> settings are to auto detect the HDD each time the machine starts. This
> is a new computer only 3 months old.
>
> On this occasion after "Primary master hard disk fail" was reported I
> went into the BIOS settings and attempted to have the drive auto
> detected by the setup program, which also failed. However on the next
> power up of the machine the HDD was detected and I was able to get the
> HDD parameters entered into the BIOS.
>
> On other occasions that I have observed, auto detection has been
> extremely slow, and/or boot times have been extremely slow to complete
> booting and loading Windows XP.
>
> The power supply voltage monitor reads the following voltages:
>
> Vcore 1.71 V
> 3.3v 3.34 V
> 5.0v 4.91 V
> 12v 11.55 V
>
> CPU temp 32°C
> MB temp 25°C
>
> Bios revision: 1003 (current release is 1006). No specific related
> issues addressed by any released BIOS updates.
>
> Have looked in the case and can see no problems, all connectors and
> jumpers on the HDD appear to be properly seated.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

"Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
news:1vENc.753$zS6.97531@news02.tsnz.net...
> Machine spec:
> Asus A7V8X-MX
> Athlon XP2600
> 512MB DDR266
> Integrated audio, video
> WDC WD800JB-00FMA0 HDD 80 GB
> ASUS CRW5232AS CD rewriter
>
> There have been a few instances of it failing to detect the HDD on
> startup, or taking a very long time to complete detection. The BIOS
> settings are to auto detect the HDD each time the machine starts. This
> is a new computer only 3 months old.
>
> On this occasion after "Primary master hard disk fail" was reported I
> went into the BIOS settings and attempted to have the drive auto
> detected by the setup program, which also failed. However on the next
> power up of the machine the HDD was detected and I was able to get the
> HDD parameters entered into the BIOS.
>
> On other occasions that I have observed, auto detection has been
> extremely slow, and/or boot times have been extremely slow to complete
> booting and loading Windows XP.
>
> The power supply voltage monitor reads the following voltages:
>
> Vcore 1.71 V
> 3.3v 3.34 V
> 5.0v 4.91 V
> 12v 11.55 V
>
> CPU temp 32°C
> MB temp 25°C
>
> Bios revision: 1003 (current release is 1006). No specific related
> issues addressed by any released BIOS updates.
>
> Have looked in the case and can see no problems, all connectors and
> jumpers on the HDD appear to be properly seated.

I would be inclined suspect the hard drive being dicky before the
motherboard. Have you run diagnostics on the hard drive?

Rider

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

Rider wrote:
> "Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
> news:1vENc.753$zS6.97531@news02.tsnz.net...
>
>>Machine spec:
>>Asus A7V8X-MX
>>Athlon XP2600
>>512MB DDR266
>>Integrated audio, video
>>WDC WD800JB-00FMA0 HDD 80 GB
>>ASUS CRW5232AS CD rewriter
>>
>>There have been a few instances of it failing to detect the HDD on
>>startup, or taking a very long time to complete detection. The BIOS
>>settings are to auto detect the HDD each time the machine starts. This
>>is a new computer only 3 months old.
>>
>>On this occasion after "Primary master hard disk fail" was reported I
>>went into the BIOS settings and attempted to have the drive auto
>>detected by the setup program, which also failed. However on the next
>>power up of the machine the HDD was detected and I was able to get the
>>HDD parameters entered into the BIOS.
>>
>>On other occasions that I have observed, auto detection has been
>>extremely slow, and/or boot times have been extremely slow to complete
>>booting and loading Windows XP.
>>
>>The power supply voltage monitor reads the following voltages:
>>
>>Vcore 1.71 V
>>3.3v 3.34 V
>>5.0v 4.91 V
>>12v 11.55 V
>>
>>CPU temp 32°C
>>MB temp 25°C
>>
>>Bios revision: 1003 (current release is 1006). No specific related
>>issues addressed by any released BIOS updates.
>>
>>Have looked in the case and can see no problems, all connectors and
>>jumpers on the HDD appear to be properly seated.
>
>
> I would be inclined suspect the hard drive being dicky before the
> motherboard. Have you run diagnostics on the hard drive?

How do you do that?

I just checked the IDE channels in Device Manager and found XP is only
using PIO mode on device 0 of the primary (the HDD) even though it is
supposed to use DMA if available. What does this mean?

 

[Paul]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article <kEENc.755$zS6.97461@news02.tsnz.net>, Patrick Dunford
<patrickdunford@nomail.invalid> wrote:

> Rider wrote:
> > "Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
> > news:1vENc.753$zS6.97531@news02.tsnz.net...
> >
> >>Machine spec:
> >>Asus A7V8X-MX
> >>Athlon XP2600
> >>512MB DDR266
> >>Integrated audio, video
> >>WDC WD800JB-00FMA0 HDD 80 GB
> >>ASUS CRW5232AS CD rewriter
> >>
> >>There have been a few instances of it failing to detect the HDD on
> >>startup, or taking a very long time to complete detection. The BIOS
> >>settings are to auto detect the HDD each time the machine starts. This
> >>is a new computer only 3 months old.
> >>
> >>On this occasion after "Primary master hard disk fail" was reported I
> >>went into the BIOS settings and attempted to have the drive auto
> >>detected by the setup program, which also failed. However on the next
> >>power up of the machine the HDD was detected and I was able to get the
> >>HDD parameters entered into the BIOS.
> >>
> >>On other occasions that I have observed, auto detection has been
> >>extremely slow, and/or boot times have been extremely slow to complete
> >>booting and loading Windows XP.
> >>
> >>The power supply voltage monitor reads the following voltages:
> >>
> >>Vcore 1.71 V
> >>3.3v 3.34 V
> >>5.0v 4.91 V
> >>12v 11.55 V
> >>
> >>CPU temp 32°C
> >>MB temp 25°C
> >>
> >>Bios revision: 1003 (current release is 1006). No specific related
> >>issues addressed by any released BIOS updates.
> >>
> >>Have looked in the case and can see no problems, all connectors and
> >>jumpers on the HDD appear to be properly seated.
> >
> >
> > I would be inclined suspect the hard drive being dicky before the
> > motherboard. Have you run diagnostics on the hard drive?
>
> How do you do that?
>
> I just checked the IDE channels in Device Manager and found XP is only
> using PIO mode on device 0 of the primary (the HDD) even though it is
> supposed to use DMA if available. What does this mean?

Disk manufacturers have a "Drive Fitness Test" for their drives,
and this test is typically used to determine whether the drive
should be RMAed or not under warranty. Such a test can be destructive
(i.e. if it does writes to the drive), so a backup wouldn't be a bad
idea. Check the WD site to see if they have such a test.

Another test is to find a utility that can read the drive S.M.A.R.T
statistics. SMART is intended to give an early warning that the drive
is not healthy, by counting detected errors and the like.

As for your observation that Windows is running in PIO mode, this
can happen if Windows is having trouble talking to the drive.
There is a knowledgebase article that talks about the algorithm
that Windows uses to throttle the communications rate to a
drive it is having trouble with. This could be why you are in
PIO mode.

http://support.microsoft.com/default.aspx?scid=kb;en-us;817472

"After the Windows IDE/ATAPI Port driver (Atapi.sys) receives a
cumulative total of six time-out or cyclical redundancy check
(CRC) errors, the driver reduces the communications speed (the
transfer mode) from the highest Direct Memory Access (DMA) mode
to lower DMA modes in steps. If the driver continues to receive
time-out or CRC errors, the driver eventually reduces the transfer
mode to the slowest mode (PIO mode)."

Workaround:
http://groups.google.com/groups?selm=%23V1uvk8pDHA.688%40TK2MSFTNGP10.phx.gbl

I notice you have one hard drive and one CDRW. Try placing them
on separate cables, so the troubles of one drive are not
upsetting the other drive.

Your three PSU voltages look fine, as they are within the normal
tolerance of +/- 5%.

HTH,
Paul

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article Patrick Dunford says...
> I just checked the IDE channels in Device Manager and found XP is only
> using PIO mode on device 0 of the primary (the HDD) even though it is
> supposed to use DMA if available. What does this mean?
>
How is the drive connected? If the WD is the only device on a channel it
has to be jumpered as such not master

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

colinco wrote:
> In article Patrick Dunford says...
>
>>I just checked the IDE channels in Device Manager and found XP is only
>>using PIO mode on device 0 of the primary (the HDD) even though it is
>>supposed to use DMA if available. What does this mean?
>>
>
> How is the drive connected? If the WD is the only device on a channel it
> has to be jumpered as such not master

Yep.... jumpered to use CS (as should all devices on this channel) and
as addressed as the master by being connected to the end connector on
the (80 pin) cable.

--
EMB
change two to number to reply

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

colinco wrote:
> In article Patrick Dunford says...
>
>>I just checked the IDE channels in Device Manager and found XP is only
>>using PIO mode on device 0 of the primary (the HDD) even though it is
>>supposed to use DMA if available. What does this mean?
>>
>
> How is the drive connected? If the WD is the only device on a channel it
> has to be jumpered as such not master

It has the standard jumpers (not the funny ones that earlier Caviars and
such like had) e.g. MA SL CS and is jumpered CS

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

EMB wrote:
> colinco wrote:
>> In article Patrick Dunford says...
>>
>>> I just checked the IDE channels in Device Manager and found XP is
>>> only using PIO mode on device 0 of the primary (the HDD) even
>>> though it is supposed to use DMA if available. What does this mean?
>>>
>>
>> How is the drive connected? If the WD is the only device on a
>> channel it has to be jumpered as such not master
>
> Yep.... jumpered to use CS (as should all devices on this channel) and
> as addressed as the master by being connected to the end connector on
> the (80 pin) cable.

Colinco's point is that Western Digital drives have two jumper settings
where most other drives have one that does the same thing. With a WD drive
it can either be set as 'master' which is the setting you use if there is a
slave drive present or 'single' if there is no slave. Having it set as
master when there is no slave causes problems, it needs to be set as single.
WD are the only ones who do this AFAIK, other drives are fine just set to
master whether there is a slave present or not.
--
~misfit~


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.727 / Virus Database: 482 - Release Date: 26/07/2004

 

[d]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

The reason for using CS is???

"Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
news:TrFNc.760$zS6.97761@news02.tsnz.net...
> colinco wrote:
> > In article Patrick Dunford says...
> >
> >>I just checked the IDE channels in Device Manager and found XP is only
> >>using PIO mode on device 0 of the primary (the HDD) even though it is
> >>supposed to use DMA if available. What does this mean?
> >>
> >
> > How is the drive connected? If the WD is the only device on a channel it
> > has to be jumpered as such not master
>
> It has the standard jumpers (not the funny ones that earlier Caviars and
> such like had) e.g. MA SL CS and is jumpered CS

 

[HarrY]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

Patrick Dunford wrote:

> Have looked in the case and can see no problems, all connectors and
> jumpers on the HDD appear to be properly seated.

What disk jumper setting have you set?
Cable-select or master or slave?

 

[HarrY]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

EMB wrote:

> colinco wrote:
>> In article Patrick Dunford says...
>>
>>>I just checked the IDE channels in Device Manager and found XP is only
>>>using PIO mode on device 0 of the primary (the HDD) even though it is
>>>supposed to use DMA if available. What does this mean?
>>>
>>
>> How is the drive connected? If the WD is the only device on a channel it
>> has to be jumpered as such not master
>
> Yep.... jumpered to use CS (as should all devices on this channel) and
> as addressed as the master by being connected to the end connector on
> the (80 pin) cable.
>

Isn't the master the connector in the middle, not the end?

 

[HarrY]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

~misfit~ wrote:

> EMB wrote:
>> colinco wrote:
>>> In article Patrick Dunford says...
>>>
>>>> I just checked the IDE channels in Device Manager and found XP is
>>>> only using PIO mode on device 0 of the primary (the HDD) even
>>>> though it is supposed to use DMA if available. What does this mean?
>>>>
>>>
>>> How is the drive connected? If the WD is the only device on a
>>> channel it has to be jumpered as such not master
>>
>> Yep.... jumpered to use CS (as should all devices on this channel) and
>> as addressed as the master by being connected to the end connector on
>> the (80 pin) cable.
>
> Colinco's point is that Western Digital drives have two jumper settings
> where most other drives have one that does the same thing. With a WD drive
> it can either be set as 'master' which is the setting you use if there is
> a slave drive present or 'single' if there is no slave. Having it set as
> master when there is no slave causes problems, it needs to be set as
> single. WD are the only ones who do this AFAIK, other drives are fine just
> set to master whether there is a slave present or not.

But it is set for cable-select!
There should be no jumper on master or slave pins whatever they are.
Master/slave is determined by cabling.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

~misfit~ wrote:
> EMB wrote:
>
>>colinco wrote:
>>
>>>In article Patrick Dunford says...
>>>
>>>
>>>>I just checked the IDE channels in Device Manager and found XP is
>>>>only using PIO mode on device 0 of the primary (the HDD) even
>>>>though it is supposed to use DMA if available. What does this mean?
>>>>
>>>
>>>How is the drive connected? If the WD is the only device on a
>>>channel it has to be jumpered as such not master
>>
>>Yep.... jumpered to use CS (as should all devices on this channel) and
>>as addressed as the master by being connected to the end connector on
>>the (80 pin) cable.
>
>
> Colinco's point is that Western Digital drives have two jumper settings
> where most other drives have one that does the same thing. With a WD drive
> it can either be set as 'master' which is the setting you use if there is a
> slave drive present or 'single' if there is no slave. Having it set as
> master when there is no slave causes problems, it needs to be set as single.
> WD are the only ones who do this AFAIK, other drives are fine just set to
> master whether there is a slave present or not.

Old WD drives have strange odd jumper settings (I have one in my machine
at home, you may recall) with 8 - 10 pins on the jumpers.

But this drive has the standard jumpers: MA, SL, CS with 6 pins on the
jumpers.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article Patrick Dunford says...
> Old WD drives have strange odd jumper settings (I have one in my machine
> at home, you may recall) with 8 - 10 pins on the jumpers.
>
> But this drive has the standard jumpers: MA, SL, CS with 6 pins on the
> jumpers.
>
>
http://support.wdc.com/techinfo/general/jumpers.asp

They still have a single setting

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

Patrick Dunford wrote:
> Machine spec:
> Asus A7V8X-MX
> Athlon XP2600
> 512MB DDR266
> Integrated audio, video
> WDC WD800JB-00FMA0 HDD 80 GB
> ASUS CRW5232AS CD rewriter

That DDR266 on an XP2600 looks suspicious to me
(unless you're one of the lucky few).

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article <nmKNc.830$zS6.102561@news02.tsnz.net>, joe_90
@invalid_address.com says...
> Patrick Dunford wrote:
> > Machine spec:
> > Asus A7V8X-MX
> > Athlon XP2600
> > 512MB DDR266
> > Integrated audio, video
> > WDC WD800JB-00FMA0 HDD 80 GB
> > ASUS CRW5232AS CD rewriter
>
> That DDR266 on an XP2600 looks suspicious to me
> (unless you're one of the lucky few).

That's what the BIOS reports on startup. I haven't looked at the RAM to
see what is marked on it.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

"Paul" <nospam@needed.com> wrote in message
news:nospam-2807040052270001@192.168.1.177...
> In article <kEENc.755$zS6.97461@news02.tsnz.net>, Patrick Dunford
> <patrickdunford@nomail.invalid> wrote:
>
> > Rider wrote:
> > > "Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
> > > news:1vENc.753$zS6.97531@news02.tsnz.net...
> > >
> > >>Machine spec:
> > >>Asus A7V8X-MX
> > >>Athlon XP2600
> > >>512MB DDR266
> > >>Integrated audio, video
> > >>WDC WD800JB-00FMA0 HDD 80 GB
> > >>ASUS CRW5232AS CD rewriter
> > >>
> > >>There have been a few instances of it failing to detect the HDD on
> > >>startup, or taking a very long time to complete detection. The BIOS
> > >>settings are to auto detect the HDD each time the machine starts. This
> > >>is a new computer only 3 months old.
> > >>
> > >>On this occasion after "Primary master hard disk fail" was reported I
> > >>went into the BIOS settings and attempted to have the drive auto
> > >>detected by the setup program, which also failed. However on the next
> > >>power up of the machine the HDD was detected and I was able to get the
> > >>HDD parameters entered into the BIOS.
> > >>
> > >>On other occasions that I have observed, auto detection has been
> > >>extremely slow, and/or boot times have been extremely slow to complete
> > >>booting and loading Windows XP.
> > >>
> > >>The power supply voltage monitor reads the following voltages:
> > >>
> > >>Vcore 1.71 V
> > >>3.3v 3.34 V
> > >>5.0v 4.91 V
> > >>12v 11.55 V
> > >>
> > >>CPU temp 32°C
> > >>MB temp 25°C
> > >>
> > >>Bios revision: 1003 (current release is 1006). No specific related
> > >>issues addressed by any released BIOS updates.
> > >>
> > >>Have looked in the case and can see no problems, all connectors and
> > >>jumpers on the HDD appear to be properly seated.
> > >
> > >
> > > I would be inclined suspect the hard drive being dicky before the
> > > motherboard. Have you run diagnostics on the hard drive?
> >
> > How do you do that?
> >
> > I just checked the IDE channels in Device Manager and found XP is only
> > using PIO mode on device 0 of the primary (the HDD) even though it is
> > supposed to use DMA if available. What does this mean?
>
> Disk manufacturers have a "Drive Fitness Test" for their drives,
> and this test is typically used to determine whether the drive
> should be RMAed or not under warranty. Such a test can be destructive
> (i.e. if it does writes to the drive), so a backup wouldn't be a bad
> idea. Check the WD site to see if they have such a test.
>
> Another test is to find a utility that can read the drive S.M.A.R.T
> statistics. SMART is intended to give an early warning that the drive
> is not healthy, by counting detected errors and the like.
>
> As for your observation that Windows is running in PIO mode, this
> can happen if Windows is having trouble talking to the drive.
> There is a knowledgebase article that talks about the algorithm
> that Windows uses to throttle the communications rate to a
> drive it is having trouble with. This could be why you are in
> PIO mode.
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;817472
>
> "After the Windows IDE/ATAPI Port driver (Atapi.sys) receives a
> cumulative total of six time-out or cyclical redundancy check
> (CRC) errors, the driver reduces the communications speed (the
> transfer mode) from the highest Direct Memory Access (DMA) mode
> to lower DMA modes in steps. If the driver continues to receive
> time-out or CRC errors, the driver eventually reduces the transfer
> mode to the slowest mode (PIO mode)."
>
> Workaround:
>
http://groups.google.com/groups?selm=%23V1uvk8pDHA.688%40TK2MSFTNGP10.phx.gbl
>
> I notice you have one hard drive and one CDRW. Try placing them
> on separate cables, so the troubles of one drive are not
> upsetting the other drive.
>
> Your three PSU voltages look fine, as they are within the normal
> tolerance of +/- 5%.
>
> HTH,
> Paul
Don't mean squat if the jumpers are not configured for proper operation
considering position on ribbon cable, and any other device on that cable.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article <giQNc.575$89.82@newsfe3-gui.ntli.net>, anon@spoof.notme
says...
> The reason for using CS is???

Common in OEM machines (e.g. Compaq), I've seen a lot of these set up
that way.

 

[d]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

I'd dump the CS, of course you may enjoy pain

"Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
news:MPG.1b72f57749b53a69989ed4@news.paradise.net.nz...
> In article <giQNc.575$89.82@newsfe3-gui.ntli.net>, anon@spoof.notme
> says...
> > The reason for using CS is???
>
> Common in OEM machines (e.g. Compaq), I've seen a lot of these set up
> that way.
>

 

[Tim]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

CS is most commonly used by Western Digital. Once upon a time (apparently)
CS was going to eliminate Master / Slave, but only WD jumped on the band
wagon. May be a bunch of fibs, but I read that so it must be true
- Tim

"Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
news:MPG.1b72f57749b53a69989ed4@news.paradise.net.nz...
> In article <giQNc.575$89.82@newsfe3-gui.ntli.net>, anon@spoof.notme
> says...
>> The reason for using CS is???
>
> Common in OEM machines (e.g. Compaq), I've seen a lot of these set up
> that way.
>

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article <mxXNc.2257$vF6.907@newsfe6-gui.ntli.net>, anon@spoof.notme
says...
> I'd dump the CS, of course you may enjoy pain
>
> "Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
> news:MPG.1b72f57749b53a69989ed4@news.paradise.net.nz...
> > In article <giQNc.575$89.82@newsfe3-gui.ntli.net>, anon@spoof.notme
> > says...
> > > The reason for using CS is???
> >
> > Common in OEM machines (e.g. Compaq), I've seen a lot of these set up
> > that way.

The computer is under warranty, it is up to the manufacturers to set the
hardware up properly when they supply it. If not they can fix it at their
expense.

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article <ceahoc$qev$1@lust.ihug.co.nz>, Tim@NoSpam.com says...
> CS is most commonly used by Western Digital. Once upon a time (apparently)
> CS was going to eliminate Master / Slave, but only WD jumped on the band
> wagon. May be a bunch of fibs, but I read that so it must be true

As I understand it certain brands (including WD) are preconfigured as CS

 

[d]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

Its a while since I purchased a WD, but as I recollect it certainly wasnt
supplied jumpered to CS.
Having said all that if the sys is still under warranty, and if you fiddle
too much, you may find the warranty dissappears.
You might want to simply check for 'tight' connections, run the hd manu
checking utility and then go back to the warranty. You should ensure that
ALL data is backed up, prior to any warranty repair.
If this is an intermittant problem I would tend towards a hardware fault, eg
hd or mobo, may be just a bad connection on a circuit board

"Patrick Dunford" <patrickdunford@nomail.invalid> wrote in message
news:MPG.1b73ad3766f9cb18989edc@news.paradise.net.nz...
> In article <ceahoc$qev$1@lust.ihug.co.nz>, Tim@NoSpam.com says...
> > CS is most commonly used by Western Digital. Once upon a time
(apparently)
> > CS was going to eliminate Master / Slave, but only WD jumped on the band
> > wagon. May be a bunch of fibs, but I read that so it must be true
>
> As I understand it certain brands (including WD) are preconfigured as CS

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus,nz.comp (More info?)

In article <PV7Oc.880$tW2.68@newsfe1-gui.ntli.net>, anon@spoof.notme
says...
> Its a while since I purchased a WD, but as I recollect it certainly wasnt
> supplied jumpered to CS.

WD state on their website that this is default config

> Having said all that if the sys is still under warranty, and if you fiddle
> too much, you may find the warranty dissappears.
> You might want to simply check for 'tight' connections, run the hd manu
> checking utility and then go back to the warranty. You should ensure that
> ALL data is backed up, prior to any warranty repair.

It's a network computer, all important data is on the network server.

How do you back up a HDD if you can't access it? LOL