home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!pipex!bnr.co.uk!uknet!bcc.ac.uk!link-1.ts.bcc.ac.uk!ucacmsu
- From: ucacmsu@ucl.ac.uk (Mr Stephen R Usher)
- Newsgroups: comp.sys.atari.st.tech
- Subject: A Tail of 24 Bombs and a TT.
- Message-ID: <1993Jan05.090243.35649@bas-a.bcc.ac.uk>
- Date: 5 Jan 93 09:02:43 GMT
- Sender: news@ucl.ac.uk (Usenet News System)
- Organization: Bloomsbury Computing Consortium
- Lines: 30
-
-
- The story so far....
-
- Over Christmas I was running my TT as a multi-user system (as I
- always do :-)) using my old 520ST as a terminal on the serial2 port, when
- all of a sudden the machine locked up. I rebooted the machine and as soon as
- the getty process accessed the serial2 port the machine locked up again.
-
- After some investigation I found that under MiNT (0.98, no memory
- protection) the system would either go into a recursive bus error or halt as
- soon as either of the two serial ports which use the Zilog SCC chip were
- sent data. About two characters of the data would actually appear on the
- serial port before the lock-up, however.
-
- Under TOS (3.05) attempting to print to either of the SCC serial
- ports caused 24 bombs and the current disk drive to be accessed! The same
- would happen if the RTS line on the serial2 port was toggled. This happens
- both on a "clean" machine and one with serpatch2 installed.
-
- So.... What I would like to know from people in the know is...
-
- Could a fried SCC chip cause this fault?
-
- Steve
-
- PS. The other two serial ports work fine.
- --
- Addresses:-
- JANET:- ucacmsu@uk.ac.ucl or steve@uk.ac.ox.earth (preferable)
- Internet:- ucacmsu@ucl.ac.uk or steve@earth.ox.ac.uk (preferable)
-