towson%amsaa@sri-unix.UUCP (01/06/84)
From: David Towson (CSD) <towson@amsaa> During 1983, there was considerable discussion (and confusion) in these newsgroups concerning the mysteries of the Terminal Access Controller (TAC), that frustrating device by which one can access the Defense Digital Network of computers. Soon, passwords will be required for TAC access, so this message will not be of interest to all. However, for those in a position to benefit, the TAC Users Guide can be obtained by anonymous FTP from machine usc-isia. Login with username anonymous and password ftp (or any non-null string), and ask for file <documentation>tac-user-guide. You might also like to get a directory listing for the <documentation> directory, which is quite large, and which has many goodies. Dave Towson towson@amsaa
ABN.ISCAMS%usc-isid@sri-unix.UUCP (01/16/84)
The TAC User Guide ain't so very small either! However I find it invaluable. I've also gained a certain amount of notoriety (justly so, I suppose) for "blowing up the TAC" as my local operators fondly call it -- by following instructions exactly (well, best as I can interpret them) for transferring binary (8-bit) files from our host (like .COM files at SIMTEL20) through the TAC to a micro. B O S and B I S (the commands to switch the TAC to binary mode don't work exactly as described -- mainly because some sort of bug (discussed elsewhere) won't permit the TAC to reset to its normal config- uration. We haven't found the bug, but I have finally discovered how to log back on to the TAC at another port (carefully writing down the number of the original port I jammed open), and resetting that jammed port. TAC operators are much relieved, they quit teasing me at parties, no more threats -- but don't have it all for certain yet. Once I figure it out, will put a wee little supplement out on the net. (For those poor souls with the same brain-damaged software on the host or TAC that causes that problem.) Regards, David Kirschbaum Toad Hall (HQ XVIII Abn Corps, Ft Bragg)