Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!mit-eddie!ll-xn!cit-vax!oberon!sdcrdcf!ism780c!tim
From: tim@ism780c.UUCP (Tim Smith)
Newsgroups: comp.sys.mac
Subject: Re: RAMSDClose() vs. Modem
Message-ID: <6534@ism780c.UUCP>
Date: Thu, 4-Jun-87 19:19:12 EDT
Article-I.D.: ism780c.6534
Posted: Thu Jun  4 19:19:12 1987
Date-Received: Tue, 9-Jun-87 02:27:34 EDT
References: <6458@ism780c.UUCP>
Reply-To: tim@ism780c.UUCP (Tim Smith)
Organization: Interactive Systems Corp., Santa Monica CA
Lines: 19

I have found out what was happening.  I was doing reads by starting
up an asynchronous read.  When it finishes, I pass the data back to
my program, and queue up another read.

Thus, I always have a read pending.

RAMSDClose() waits for IO to complete before closing the driver.
Thus, it hangs.  Flicking the modem off and on causes it to send
a couple characters of garbage, which satisfy the read, and then
RASDClose() finishes.

Now I call KillIO() before calling RAMSDClose(), and everything
works.

( by the way, the reason I am using the RAM serial driver rather
than the ROM serial driver ( which are the same on a plus, I think ),
is so that I will also run under the 64k rom. )
-- 
Religion: just say "no"         Tim Smith  {seismo,sdcrdcf}!ism780c!tim