Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!sdd.hp.com!elroy.jpl.nasa.gov!zardoz.cpd.com!tmiuv0!rick
From: rick@tmiuv0.uucp
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Dual Serial Boards
Message-ID: <1946@tmiuv0.uucp>
Date: 31 May 90 12:17:48 GMT
References: <2787@crash.cts.com> <1759@tmiuv0.uucp> <23336@uflorida.cis.ufl.EDU> <1359@madnix.UUCP>
Organization: Technology Marketing Inc., Irvine, CA
Lines: 46

In article <1359@madnix.UUCP>, aaron@madnix.UUCP (Aaron Avery) writes:
> In article <23336@uflorida.cis.ufl.EDU> jma@beach.cis.ufl.edu (John 'Vlad' Adams) writes:
>>I've a question about any of the multi-serial-port boards (i.e.
>>Checkpoint, ASDG, or Commodore's.)  I know the ASDG uses a
>>requestor.  What about the others?  What happens if you are
>>running a multiline BBS and have a power-out?  When the
>>system reboots with power, would you get that requestor which
>>would effectively make the BBS unoperable till the Sysop got
>>home?  Or is there a way to select ports in a script or
>>mountlist? This is especially important to me as I'm
>>considering a multiline bbs on a 2000.  Thanks in advance.
> 
> Well, the requester is only there to allow you to use your additional ports
> with programs which only know about the Amiga's internal serial port (and don't
> go directly to the hardware!). Any multi-line BBS program will allow you to
> specify the alternate device drivers and unit (port) numbers to use for the
> BBS. Thus, you would not need to install the requester (Serial DisPatcher, in
> this case) at all.
> 
> Other programs, such as A-Talk III, also allow you to specify which serial
> port you wish to use, thus no requester need come up.
[some stuff deleted]
> Aaron Avery, ASDG Inc.         "A mime is a terrible thing to waste."
>                                                              -- Robin Williams
> ARPA: madnix!aaron@cs.wisc.edu   {uunet|ncoast}!marque!
> UUCP:   {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!aaron

You can also (very carefully!!!) use an editor (TxED, CEDPro or another which
won't barf on binary codes) to change occurances of "serial.device" to
"siosbx.device", which will cause the application to use the ASDG DSB's port
0. I've done this, and it works just hunky.  You've GOTTA be careful, though,
and trying to use port 1 can be tough because you have to find the "0" which
refers to the device number and change it to a "1".  Chances are that you'll
find LOTS of "0"s in there.

-- 
  .-------------------------------------------------------------------------.
 / [- O] Rick Stevens (All opinions are mine. Everyone ignores them anyway.) \
|    ?   +--------------------------------------------------------------------|
|    V   | uunet!zardoz!tmiuv0!rick             (<-- Work (ugh!))             |
|--------+ uunet!zardoz!xyclone!sysop           (<-- Home Unix (better!))     |
|  uunet!perigrine!ccicpg!conexch!amoeba2!rps2  (<-- Home Amiga (Best!!)      |
 \ 75006.1355@compuserve.com (CIS: 75006,1355)  (<-- CI$)                    /
  `-------------------------------------------------------------------------'
"I was Caesarean born.  When I leave the house, I use the window."
                                         - Steven Wright