Xref: utzoo comp.unix.sysv386:1631 comp.unix.questions:26547 comp.unix.misc:439
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cis.ohio-state.edu!karl_kleinpaste
From: karl_kleinpaste@cis.ohio-state.edu
Newsgroups: comp.unix.sysv386,comp.unix.questions,comp.unix.misc
Subject: Re: Is osu-cis still out there?  Has the number changed?
Message-ID: <KARL.90Oct29092936@giza.cis.ohio-state.edu>
Date: 29 Oct 90 14:29:36 GMT
References: <55@bmhalh.UUCP>
Sender: news@tut.cis.ohio-state.edu
Followup-To: comp.unix.sysv386
Organization: Ohio State Computer Science
Lines: 30

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