🚀 go-pugleaf

In <14137@grebyn.com>, ckp@grebyn.com (Checkpoint Technologies) writes:
>In article <7970@nigel.udel.EDU> new@udel.edu (Darren New) writes:
>>I understand that there are multi-port serial boards out there.
>>I also understand that the device-level interfaces are essentially
>>the same as serial.device (mod Open parameters).  My question is this:
>>Do the current boards support 'AUX:' style devices?  That is,
>>can I Open("AUX:1", MODE_???) and Open("AUX:2", MODE_???) and
>>read/write these (in a blocking way, of course)?  (Or whatever the
>>device names may be.)
>>
>	Due to it's limited usefulness, we (Checkpoint Technologies)
>decided not to include an AUX:-style handler with the Serial Solution
>board, but we do supply a utility which can make one. The ZapPort
>utility on the driver disk automatically patches executable programs to
>use our serial driver.  This works just fine on aux-handler as well, so
>you can make a duplcicate for the Serial Solution card.

While I am glad to see that the aux-handler can be patched, I am a little
shocked that you see AUX: as having limited usefulness. Indeed, for some folks,
it is far more useful than SER:, allowing as it does, an easy way to use a
shell or an application normally run using stdin/stdout over a serial port.

Does your ZapPort utility patch executables in a generic manner? The reason I
ask is that the aux-handler I use is not the one supplied by CBM, but has been
improved significantly.

-larry

--
"Cavett Emptor - Let the talk show host beware!" - Evan Marcus
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+