As most of you are aware, the GBBS ‘Pro’ manual leaves a lot to be desired.
However, after several all-nighters and a few 6-packs of Mtn. Dew, I
uncovered a few tidbits of information on the ACOS device # drivers that you
may want to try out if you feel ambiious.
#0 Local console & modem. Works for both input and output. This is the
standard output mode, and the “#0″ is not required (ie. PRINT
#0,”Text” and PRINT “Text” function identically)
#1 File buffer #1. Must be OPENed first. Input and output.
#2 File buffer #2. Same as above.
#3 Local console ony Text displayed will NOT be shown on a remote
user’s screen. Output only, I think.
#4 Remote console (modem) only. Text printed will be dumped to the
modem only and NOT show up on your local screen. Backdoor possi-
bilites exist here, SO WATCH IT! Output only, I beleive.
#5 Printer output channel. Text printed will be dumped to a printer if
you have one online. Output only, of course.
#6 Output to last-used message number. i.e. PRINT #Msg(5),”Text”:PRINT
#6,”More text” will put both strings in message #5 of the currently
active message number. NOTE: You must do at least one READY #Msg(x)
or PRINT #Msg(x) before using this device driver. Output only.
#7 Same as above, but input only.
#8 Input or output to the editor buffer. Works very nicely. Very useful
for storing information to be later displayed in one
“fell swoop” using the COPY #8 command. If used correctly, your
SETINT/INPUT problems can be alleviated.
#9 The top-of-screen “template” that displays the user’s stats. Writing
info to this “device” must be done carefully and in a fairly pre-
cise format for it to display correctly. One thing that the GBBS
manual forgets to mention is that the top-of-screen display is
NOT updated on your console until a special “PRINT ^” command
is issued. Look at your LOGON.SEG source at label “login2” for
#10 The 128-byte “Ram drive”. Works exactly like file devices #1 & #2,
without the need of the OPEN command. To initialize it, use a