mithomas@bsu-cs.UUCP (Michael Thomas Niehaus) (03/23/89)
Maybe someone out there can answer my questions. First of all, I am running
HyperCard 1.2.1 (no, I don't have 1.2.2). I am using Apple's serial
XCMDs.
Here is what I am trying to do: I want to dial up our campus network, log
into our mainframe, and have HyperCard check my mail. (I don't care if you
think this is stupid :-).) Here's where I run into problems.
First, I thought that I could use HyperCard's "dial...with modem" command,
but this causes an interesting problem: any subsequent calls to the
serial XCMDs fail, reporting a SerGetBuf error (problem getting the port's
buffer) as if to tell me that the serial port is in use by someone else.
Is it possible that HyperCard forgets to release the serial port after
it dials? Or maybe it does this purposely? Can anyone explain?
Since that didn't work, I figured I could dial my Apple modem myself.
So I sent the "ATDT1000" command to the modem to dial the campus net (at
the number 1000, of course). It would "pick up" the phone and dial, but
the script would send the next characters (returns) which caused the modem
to report NO CARRIER. No suprise. So I wanted to make it wait until the
"CONNECT" string was received. But as soon as the "recvUpTo" or "recvChar"
routines are called, the modem hangs up. To be more specific, any subsequent
call to one of the XCMDs causes the modem to hang up. Any ideas?
I suppose that I could rewrite the XCMDs, but that sounds like too much
trouble. I would appreciate any ideas.
Thanks,
Michael
--
Michael Niehaus UUCP: <backbones>!{iuvax,pur-ee}!bsu-cs!mithomas
Apple Student Rep ARPA: mithomas@bsu-cs.bsu.edu
Ball State University AppleLink: ST0374 (from UUCP: st0374@applelink.apple.com)