In message <[EMAIL PROTECTED]>, "Prologix" writes:
>Hi Chuck,
>
>Good work identifying the problem! Leaving out the bus driver chips was a
>conscious decision based on available board space and was not made lightly.
>Extensive testing had shown that not to be an issue, so far. In fact, yours
>is the first reported case of a drive related problem. However, we consider
>even one incident to be one too many, and will be revisiting the decision
>during a future release.

I think I can report having seen the problem as well, only not
realizing the cause, because it worked flawlessly when I put my
HP59401A Bus Analyser on the bus.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Reply via email to