Can't detect secondary master and slave

  • Thread starter Thread starter cp
  • Start date Start date
C

cp

Hi,

My two CD-ROMs have completely stopped responding. Yesterday, if
I clicked on the drives in win explorer enough times I'd get a listing but
today nothing! When the computer boots up, NO secondary devices
are detected any more. Anyone have any idea what could be wrong?
Could it be the IO controller on my motherboard? Cable? My motherboard
is an Asus CUVX4

Thank you in advance for any help!
cp
 
db said:
Swap your ide cables over, see what happens.
If it doesn't boot get a new ide cable.
Click to expand...

Very unlikely indeed that BOTH cables would go bad
at once with BOTH secondary drives not being seen.
Check your hardware devices, see if they are still listed and enabled.
Click to expand...

Very unlikely indeed that BOTH secondary drives wouldnt
be enabled. If they arent visible they likely wont be listed.
 
in message

Very unlikely indeed that BOTH cables would go bad
at once with BOTH secondary drives not being seen.
Click to expand...

Who said anything about BOTH cables going bad?
You put the hdd ide cable on the cds, and the cd cable on the hdd. If it
boots ok the cd cable is working ok, if you didn't have an ide cable on
the hdd how can you test the cd ide cable?
What are you suggesting ?
Very unlikely indeed that BOTH secondary drives wouldnt
be enabled. If they arent visible they likely wont be listed.
Click to expand...

Still check to see if they are there. BOTH OF THEM.

Apart from trying to make a mockery of my suggested answers which he should
try out, what exactly did you add to the answer? bugger all as far as i
can see :)

db
 
My two CD-ROMs have completely stopped responding.
He clearly said that BOTH secondary drives stopped working.
Click to expand...
Exactly. He said both SECONDARY, not both SLAVES. The secondary Master and
Slave are both on the SAME cable that goes into the secondary IDE controller
on the motherboard.

My initial feeling is that if they sometimes work and sometimes don't then
it's probably a flaky connection somewhere, either in the cable or the
connection to the motherboard.
 
Back
Top