🚀 go-pugleaf

In article <3937@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>In article <0048.AA0048@julie>, mcr@julie.UUCP (Michael Richardson) writes:
>>   And of course "dir AUX:amiga/1200/8n1/2317144" --- at this point
>> it doesn't make sense not to provide complete, intelligent modem
>> support.
>
>AAAAAAAAARRGH!!!!!!
>
>I'll tell you what. *you* design the interface, then I'll find a modem it
>won't work with. THIS IS THE WRONG PLACE TO PUT ASSUMPTIONS ABOUT WHAT THE
>SERIAL PORT IS CONNECTED TO.
>Peter "Have you hugged your wolf today" da Silva

    A clear and guiding light to solve the continuing modem worries
  might be....    MODEM.DEVICE   !!!!!!  (in lower case, of course)
  This way, you can talk to any modem (or networked modem server) you 
  have somehow attached to your amiga.  This new device would be a 
  value-added server to (most likely) the serial.device.  No, I 
  haven't seen the 1.4 specs :-)

   The modem.device would provide "typical" modem services to its clients.
  Upon opening the modem.device, you inform it of a "physical layer" device
  to use for communications.  If you're networked, this could actually
  be a socket driver (ie, DNET or sockets) that would move your data
  over to a modem server computer.  If you have a modem on the ?parallel?
  port, just tell the modem device so.  Another desired feature the
  modem.device would provide is:  DROP DTR (or CMD_HANG_UP).  Ohhh....
  I feeel a light headedness coming on.

   For those who are truely amibition, see RS-366A spec.  Here, EIA
  went and speced out a modem interface.  Wasn't that sweet of them :-)
  Can you say ""Circuit CRQ - Call Request", "Circuit DLO - Data Line
  Occupied",? :-) :-) :-) :-)  Why, this document even specs pins for
  sending dialcodes to the DCE (ie modem) unit.

   
   Lay your head back
   And let your hair fall all around
   Open [ "layers.library" ]
   This is the end of the innocence...
                          --- Don Henley, mostly

--- brian witt
--- USENET:  well!aleks@ucbvax.berkeley.EDU