> Seeing that this is the second device that has shown these symptoms, I
> would consider it *extremely unlikely* that this is the problem.
So do I.
Here is what should have been done to diagnose a burner problem:
Check for software problems. These can be caused by hardware problems
and can at times be difficult to distinguish from hardware problems.
Check syslog - this indicates a hardware problem.
Possibilities:
Media I/O errors cause IDE busses to lock up. Check with different
media.
Defective drive - connect to another computer
Defective cable - replace cable, preferably with an unused one
Defective motherboard - connect a different drive
Two pieces of hardware being fine by themselves, but mutually
incompatible.
Make sure you connect only one drive per cable for testing.
In theory, it could be a kernel driver problem. Test with OtherOS if
possible.
At this point, the defective piece of hardware should be located, and
the tests shouldn't have taken long. Now's the time to go back to the
shop. I wouldn't request a replacement drive unless I had at least
somewhat excluded other hardware. If the parts were purchased at the
same time to make a system, one can argue it's the shop's problem to
sort the lot.
> I have also had similar problems when I tried to jumper devices to
> *anything but* cable select.
Ah yes, *very* good point. Mutually incompatible hardware... and it is a
possible cause for the observed symptoms.
> Do I take it from your comments Volker that BTC is another brand that we
> must not buy (:
I didn't say that, I only said I remain unconvinced by BTC burners, but
don't have hard facts to sway me either way. Personally I wouldn't buy a
BTC for $90 when I can get a confirmed good drive for $100.
Volker
--
Volker Kuhlmann is possibly list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.
