>
> Badly configured baud rate? IRQ conflict? Badly written program? Bad
> connection? Corrupted buffer?
Yeah, but why suddenly? It worked fine after I first set it up... For weeks.
> I thought it's interesting to note that the serial port is reported to be
> okay for exactly 3 seconds, then times out exactly 7 seconds later. It
> seems to be synchronizing/unsynchronizing at a constant rate, which may
> be due to the baud rate problem. Did you set the serial port baud rate
> to the proper rate using setserial or a similar program?
Umm... the only recent baud rate changes I made were ones specificially used
by the 'pilot-xfer' family of programs.
setenv PILOTRATE 57600
in my .cshrc
But, why would this affect my OTHER serial port? And why would it happen
on virtual consoles where I'm _not_ logged in?
> Just a guess.
Thanks! :)
-bill!
****************************************************************************
* To UNSUBSCRIBE from the list, send a message with "unsubscribe lug-nuts"
* in the message body to majordomo@saclug.org. Please direct other
* questions, comments, or problems to lug-nuts-owner@saclug.org.
This archive was generated by hypermail 2b29 : Fri Feb 11 2000 - 16:20:23 PST