Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!ames!lll-winken!uunet!microsoft!bradch
From: bradch@microsoft.UUCP (Bradford Christian ms1)
Newsgroups: comp.sys.amiga.tech
Subject: Re: I wanna have a DOSGate!
Keywords: Citadel, DOSGate, door, bbs
Message-ID: <6013@microsoft.UUCP>
Date: 13 Jun 89 01:43:27 GMT
References: <16317@gryphon.COM> <5866@microsoft.UUCP> <682@madnix.UUCP>
Reply-To: bradch@microsoft.UUCP (Bradford Christian ms1)
Distribution: na
Organization: Microsoft Corp., Redmond WA
Lines: 56

In article <682@madnix.UUCP> aaron@madnix.UUCP (Aaron Avery) writes:
>AUX: does do raw mode. It understands the ACTION_SCREEN_MODE packet, and if
>you put the line 'Startup = raw' in the mountlist entry for AUX:, it should
>default to raw mode.

Hmmm..  I guess I have a different problem.  All I know is I tried running
ARC from a CLI connected to AUX: and when it asked me a question (and expected
a single Y/N character response), it just started printing the question over
and over (as if I typed something other than Y or N).

>I'm sure your method of writing your own AUX: handler to support things like
>carrier checking and timeouts is the proper way to go.

Thanks, me too!

>I have to warn you, though, that doing it right (like supporting asynchronous
>reads and writes) is not trivial. I'd suggest finding the 1988 DevCon software
>disks which include an excellent example to work from written by Andy Finkel.
>This is a SER: type example, and not an AUX:, so there are many more CON:-like
>issues you need to worry about.

To tell you the truth, I was going to punt asynch requests.  I don't know of
any programs that use async I/O with the console.  If this does turn out to
be a problem, I'll just queue requests...  Hopefully, there aren't too many
things that I need to do to "do it right" that I haven't thought of (although
there usually are :-)  Thanks for the pointer, I'll look for that example.

>Since you're doing work on a BBS which should, I believe, support multiple
>lines, please include support for drivers other than serial.device, and unit
>numbers. Multiple serial port hardware is here now, and the public deserves
>good multi-line BBS support for this multi-tasking computer.

Actually two BBSs.  An Amiga port of Citadel and my own design.  The Citadel
port is being done at the request of a local sysop and I hope to see it reduce
the number of BBS-PC boards around here.  I really doubt that I'll ever even
think about supporting multiple users with the Citadel code I have, however,
as it was never intended to run multiple users at once..  It will, of course, 
work with any named device and unit number provided said device acts like 
serial.device.  

My own program is a different story.  It was designed from the start with
multiple ports in mind.  Unfortunatly, I'm too stingy to buy a multi-port
board at their current price :-(  I don't even know if my program will 
ever be publicly available, anyway.

I agree, it is definatly time for multi-user boards.  Anyone creating a new
BBS program on the Amiga without this feature may as well write it for a
lesser machine.

>-- 
>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

	BradCh