HDD detection problem on Asus A7V8X-MX

  • Thread starter Thread starter Patrick Dunford
  • Start date Start date
Patrick said:
Common in OEM machines (e.g. Compaq), I've seen a lot of these set up
that way.
Click to expand...

Pretty much Compaq only IME. And that's just laziness/expediency so their
support people can plug in a drive set to CS without having to check where
it is on the IDE cable or what other devices are set to on that controller.
They only do it because they sell a lot of machines with support contracts
and the quicker their support guy can be in and out of the premises the less
it costs them/more profit they can make. Real computers use master/slave (or
'single'/master/slave if they have WD drives).

You want to emulate Compaq? Yech!

I tried using CS for a while as it seemed like a good idea. It wasn't.
 
That's what the BIOS reports on startup. I haven't looked at the RAM to
see what is marked on it.
Click to expand...

My Athlon (XP 1800, BIOS AMI) does the same thing, however it is
intermittent.

It seems to have **** all to do with jumpers and IDE cables.

Possibly related behaviour is ACPI breaking down. The machine no longer
powers down in windows. If I put one of my other drives in IDE Channel one
as master it powers down properly.


Let me know if you find anything useful out please.
 
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
 
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 :)
Click to expand...

As I understand it certain brands (including WD) are preconfigured as CS
 
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
 
D said:
Its a while since I purchased a WD, but as I recollect it certainly
wasnt supplied jumpered to CS.
Click to expand...

The last time I bought a WD drive it was jumpered to 'single' when I got it.
 
[email protected] said:
Its a while since I purchased a WD, but as I recollect it certainly wasnt
supplied jumpered to CS.
Click to expand...

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.
Click to expand...

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
 
misfit61nz@yahoo- said:
It does indeed. Two possible reasons I can think of. Firstly the RAM and CPU
FSB could be running asynchronously. (not good performance-wise) or secondly
it could be one of the older XP2600+'s, T'bred core, 256KB L2cache, 133Mhz
FSB.
Click to expand...

It is indeed a XP2600+
 
Back
Top