bruce@bmhalh.UUCP (Bruce M. Himebaugh) (10/28/90)
I haven't been able to get through to osu-cis for over 9 days now. Is it still
out there? The number I had been using is:
osu-cis: (614) 292-5112
Has it changed? I had been connecting at 2400bps.
Please e-mail responses to address in .sig.
Thanks for any information!
Bruce
--
Bruce M. Himebaugh Voice: 216-484-3528
PATHS: uunet!{ncoast,aablue}!fmsystm!mrsmouse!bmhalh!bruce
(NOTE: the system name "fmsystm" is with no "e", NOT "fmsystem")
*NOTE*: Please do not use bruce@bmhalh.UUCP -- I'm not registered yet.karl_kleinpaste@cis.ohio-state.edu (10/29/90)
bruce@bmhalh.uucp writes:
I haven't been able to get through to osu-cis for over 9 days now.
Is it still out there?
Yes, it's still out here.
The number I had been using is:
osu-cis: (614) 292-5112
Has it changed? I had been connecting at 2400bps.
Ick. 5112 is where the TB live[sd]. Using it for bland 2400bps
connections is a horrible waste of a fast modem.
Anyhow, the problem is that the TB appears to have died. I am trying
to resurrect it, but it looks pretty close to the bitter end just now.
You can still do 1200/2400/9600 via 29231##, ## = {12,24,96}, which
gets you the Micom port selector.
osu-cis Any ACU ##00 1-614-292-31## "" \r\c Name? osu-cis nected \c GO \d\r\d\r\d\r in:--in:--in: Uanon
If you're doing 9600bps V.32, you may have to adjust things a bit to
do longer delays and more \r hammering; the Micom doesn't appear to
autobaud as well at 9600bps as at other speeds. About 5 seconds'
delay before the initial \r seems to help; and an extra few \d\r
sequences after GO may also help.
depressed,
--karl
osu-cis' admin