home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS 1
/
BBS#1.iso
/
document
/
fdrus.arj
/
FD_RUSS.5
< prev
Wrap
Text File
|
1991-03-21
|
39KB
|
1,190 lines
Appendix A
Help systems
The following systems and persons can be contacted if you have
problems or questions regarding FrontDoor. You will most likely
find the latest noncommercial version on these systems as well.
Chris Homrighausen Europe (main)/Sweden
9600 HST 2:2/106
Lars Eriksson Finland
9600 HST V32 2:2/109
Ulrich Bartelt West Germany
9600 HST 2:241/2
Peter Janssens The Netherlands
9600 HST V32 2:28/2
Luc Schoofs Belgium
9600 HST 2:29/100
Patrick Oetiker Switzerland
9600 HST 2:30/5
Orlando Castillo Spain
9600 HST V32 2:34/2
Felix Kasza Austria
9600 HST V32 2:310/11
Luca Leone Italy
2400 2:33/108
- 107 -
Help systems (cont'd)
Stig Jacobsen Denmark
2400 2:231/16
David Nugent Australia (West)
9600 PEP 3:3/101
Andrew Khoo Australia (East)
9600 V32 PEP 3:711/805
Pablo Kleinman South America
9600 PEP V32 4:4/104
Bruce Bodger USA (main)
9600 HST 1:1/101
Mark Howard USA
9600 HST 1:260/340
Bryan Bucci Canada
9600 HST 1:153/133
Some of these systems are also listed in other network's
nodelists. Such as SIGNet, AlterNet and the Network.
- 108 -
Appendix B
FOSSIL drivers
A FOSSIL (or Fido/Opus/SEAdog Standard Interface Layer) driver is
a memory resident program that works as a layer between the
application program and your computer's hardware. The mailer
requires a FOSSIL driver to function. The advantages of the
standard FOSSIL interface is that programs can be ported easily
to other machines and/or operating systems.
There are several FOSSIL drivers available. The mailer has been
tested with OpusComm, X00 and BNU with good results. X00 and BNU
will be described here.
B.1 BNU
BNU, written by David Nugent, comes in two flavors. One is a
device driver, similar to X00.SYS. The second flavor is a .COM
file, loaded from AUTOEXEC.BAT or another batch file. I use the
.COM flavor. For a detailed description of the BNU driver, read
the documentation included in the BNU distribution archive.
[AUTOEXEC.BAT]
BNU /R=1024 /T=512 /L1:38400
/R=1024 Specifies a transmit buffer of 1024 bytes.
/T=512 Specifies a receive buffer of 512 bytes.
/L1:38400 Locks COM2 at 38,400 bps (for use with the
14400 HST or DS modems).
If you are not using a high-speed modem the above example
should most likely be modified to not lock COM2.
- 109 -
B.2 X00.SYS
X00, written by Ray Gwinn, is a device driver, it's loaded from
your CONFIG.SYS file when your machine is started. For a detailed
description of the X00 driver, read the documentation included in
the X00 distribution archive.
[CONFIG.SYS]
device = X00.SYS E 1 B,1,38400 T=512 R=1024
E Disable 5 second "commercial" when X00 is
first loaded.
1 Number of COM ports X00 should allow to be
accessed at one time.
B,1,38400 Locks COM2 at 38,400 bps (for use with the
14400 HST or DS modems).
T=512 Specifies a transmit buffer of 512 bytes.
R=1024 Specifies a receive buffer of 1024 bytes.
If you are not using a high-speed modem the above example
may not be what you want. The most common command line for
X00 is:
device = X00.SYS E 1
- 110 -
Appendix C
Modems
FrontDoor works with several modems, including USR HST, Telebit's
Trailblazer, ANC, Everex and Hayes. The general rule is that the
modem must be able to send alphanumeric result strings. For most
modems, the basic configuration is all that is required. For
high-speed modems such as the HST, a few extra settings are
necessary. The reason HST is the only modem described here is
because it's the only modem I've used with FrontDoor.
C.1 General requirements
The modem must not echo characters sent by FrontDoor, it must not
have CD (carrier detect) forced. It should support disconnecting
by lowering DTR (data terminal ready), but it's not necessary.
DTR must not be forced.
The current version of FrontDoor does not support manually
operated modems with fixed speeds since most of them do not send
any type of messages to the terminal (program). This is expected
to be implemented in future versions.
To use FrontDoor with high-speed modems such as the HST and
Trailblazer, it is often necessary to lock your COM port (using
fixed speed). In general, this improves throughput. For more
information about this, see FOSSIL drivers.
- 111 -
C.2 USR HST
DIP Switches:
0 (big) OFF
1 OFF
2 OFF
3 ON
4 OFF
5 ON
6 OFF
7 OFF
8 ON
9 ON
0 OFF
Command/modem strings:
CONNECT 300 CONNECT|
RING RING|
OffHook ATH1|
OnHook ~ATH0|
Init-1 AT&G1&K0&M4S19=2B&B1&H1&R2&N0S15=8|
Init-2 ATV1X6S7=55EQM0S11=50S0=0|
Down AT|
Reset AT|
Modem hardware:
Lock port YES
Baudrate 38400, 19200 or 9600
Answer control:
Manual answer Yes
Force answer ATA|
Delay 5
- 112 -
Appendix D
Multitasking
FrontDoor can be used together with most multitasking programs.
It has been tested with DESQview, DoubleDOS, Multilink and
Taskview. It will automatically detect most multitasking
software. My personal suggestion would be DESQview. One of the
best multitaskers around for PC/MS-DOS.
D.1 NS16550
If you're running FrontDoor under a multitasker or in a LAN
environment, I suggest you replace your 8250 or 16450 UART chip
with a NS16550AN or NS16550AFN. These are available from several
electronics outfits for somewhere between USD 17 and USD 23.
The 16550 family of UARTs have internal buffering and will
improve performance in multitasking and LAN environments. Both
BNU and X00 has direct support for the 16550 family and can be
used without modifying your command-line paratmeters when loading
them.
- 113 -
D.2 DESQview
FrontDoor will request a virtual screen buffer from DV and write
to it. The result is very fast and very well behaved screen
writes. I have successfully used FrontDoor's mailer under
DESQview 2.21 (and 2.25) with 180KB. Here're the settings I use
with DESQview:
Keys to Use on Open Menu FD
Memory Size (in K) 250
Options:
Writes text directly to screen N
Displays graphics information N
Virtualize text/graphics (Y,N,T) N
Uses serial ports (Y,N,1,2) 2
Requires floppy diskette N
Advanced Options:
System Memory (in K) 0
Maximum Program Memory Size (in K) <empty>
Script Buffer Size 0
Maximum Expanded Memory Size (in K) 0
Text Pages 1
Graphics Pages 0
Initial Mode <empty>
Interrupts 00 to FF
Maximum Height 25
Starting Height 25
Starting Row 1
Maximum Width 80
Starting Width 80
Starting Column 1
Close on exit (Y,N,blank) N
Uses its own colors Y
Allow Close Window command Y
Runs in background (Y,N,blank) Y
Uses math coprocessor N
Keyboard conflict (0-4) 0
Share CPU when foreground Y
Share EGA when foreground/zoomed Y
Can be swapped out (Y,N,blank) N
Protection level (0-3) 0
- 114 -
D.3 DoubleDOS
Smart multitasking software allocates a virtual screen buffer for
each task. Applications can then ask the multitasking software
where it should write and the multitasker handles the screen
updates. DoubleDOS, however, is using a different method.
Every time you switch tasks from the keyboard, the screen-buffers
change. So there's no easy way for the software running under
DoubleDOS to detect this. In DoubleDOS 5.00, there are two
options that allows you to run FrontDoor under DoubleDOS just
fine. You MUST run FrontDoor in the TOP section for the two
methods below to work.
DISPLAY=TEXT If your system has a MCGA, CGA, EGA or VGA
card installed, there's extra memory
available on those cards for graphics, etc.
DoubleDOS can use some of that memory for
each of its screen buffers. To enable this,
add DISPLAY=TEXT to your DDCONFIG.SYS file.
REFRESH If you have a text-only adapter (MDA) there's
most likely no extra memory available on the
card. Add REFRESH by itself on a line to your
DDCONFIG.SYS file. This will tell DoubleDOS
to repaint the screen if the other task is
bleeding through.
X00 and DoubleDOS When using FrontDoor, X00.SYS and DoubleDOS,
there are a few rules that must be followed:
Do not assign the COM ports in DDCONFIG.SYS
Make sure you execute CAPTURE (supplied with
X00) after you execute DOUBLEDO (the
DoubleDOS executable). To be safe, execute
CAPTURE in both partitions.
If you have problems with your clock, try the
DEFER option in X00.
Make sure you replace ANSI.SYS with
DBLDANSI.SYS.
The BOTTOM partition should initialize before
the TOP partition. In other words, if you're
loading FrontDoor in the BOTTOM partition,
try to delay the initialization of the TOP
partition.
- 115 -
D.4 Multilink
I would personally not recommend anyone using FrontDoor with
Multilink. I have never successfully executed any program under
Multilink for longer periods of time than momentarily.
- 116 -
Appendix E
Converting from other mail systems
If you were using SEAdog or D'Bridge before you started using
FrontDoor, you should have little trouble converting to
FrontDoor. The routing and message handling used by these two
mail systems is very similar to the way things are done with
FrontDoor.
If you are converting from Binkley, Opus, or Dutchie, however,
there are a few things you should know and make sure you have
done before you install FrontDoor.
The main difference between FrontDoor and Binkley or Opus is that
FrontDoor doesn't use oMMM, the static message packer written by
Bob Hartman. We see the oMMM approach as a black hole from which
there's no return. This is not true in some cases and there are
advantages of using oMMM type packers instead of the method used
by FrontDoor.
oMMM will create what we call static bundles, where each system
has a control file that tells the mailer what files and messages
to send to what systems. FrontDoor will NOT recognize oMMM type
bundles (packets) so before you fully convert to FrontDoor, you
must make sure that all the oMMM type mail is sent before you
convert to FrontDoor.
You can use FrontDoor to send the remaining oMMM type mail by
attaching the files manually with FrontDoor's editor or a robot
utility such as XRobot, but you'll need a utility with which you
can determine which file belongs to which system before you can
do this. So it might be easier for you to tell Binkley or Opus to
send its remaining mail before you do the conversion.
- 117 -
Appendix F
Sample (PCP) script
This script was written by Eric Larson, FidoNet.1:260/330 and is
intended as a sample PC Pursuit script.
; PCP script for FrontDoor 1.99b and above
; Eric Larson, 1:260/330.0, 8/30/89
; modified from script supplied in FD 1.99 documentation
debug ON
setport 2400 ; Redundant if you have locked your FOSSIL
; If you have a 1200 indial :-(, use 1200
; here and change the hunt-confirm sequence
; to @ wait 1 <CR>
;----------------------------------
; Your Indial Phone Number Here
;----------------------------------
;
; Users with MNP modems should disable MNP as the buffering
; combined with PCP's packet latency will cause block position
; errors during error recovery. For HST owners, use:
;
send AT&M0<CR>
waitfor OK
;
; Others should comment out the above two lines
;
; Now, your local indial modem
;
send ATDT4795395<CR>
case
CONNECT : >whackit
RING<CR> : fail
BUSY<CR> : fail
"NO " : fail
@default : fail
endcase
- 118 -
:whackit ; Attempt to "wake-up" PCP
purgein ; Telenet recommends at least
wait 2 ; a 200 ms pause between
send @ ; characters in the hunt-confirm sequence
wait 1 ; change the @ to <CR> if you
send D ; call a 1200 bps indial modem
wait 1
send <CR>
waitfor TERMINAL=
send D3<CR> ; Preferred terminal type
waitfor @
:outdial ; Dial PCP city
purgein
retrycount 5
send C @OUTBOUND,xxxxxxxxxx<CR> ; Your ID Here
waitfor PASSWORD
send xxxxxx<CR> ; Your Password Here
case
CONNECT : >local ; Gotcha!
BUSY : >outdial
"NOT " : fail
@nocarrier : fail
@default : fail
endcase
:local ; Initialize Outdial
purgein
send <CR>
wait 1
send I<CR>
send ATZ|
timerset 15
waitfor OK
send @|
waitfor @
- 119 -
send SET?<sp>1:0,7:8<CR>
waitfor @
send CONT<CR>
send ATH0Z<CR>
waitfor OK|IDLE
send <ENQ><CR> ; Turn on RV Mode
waitfor *
purgein
clearcount
timerset 35
wait 1
send D@LOCALNUM<CR>
purgein
case
ONTROL : >landing
ANSWER : >landing
BUSY : fail
FAILED : fail
"NO DIAL TONE" : fail
"NO DTR" : fail
"NO CARRIER" : fail
VOICE : fail
@default : fail
@nocarrier : fail
endcase
:landing ; Landing on Pluto
wait 7
purgein
session
- 120 -
Appendix G
Commercial inquiries
The FD package is free of charge if it's used in a noncommercial
environment. If it's used in a commercial environment, you may
NOT use the noncommercial version - period. Please send
commercial inquiries to:
Australia Workware Australia Pty, Ltd
attn: Kim Nugent
Suite 3.03, 620 St. Kilda Road
Victoria, Australia, 3004
Europe Computer-Laser Systems
attn: Felix Kasza
Technical Services Group
Hetzendorfer Strasse 191
A-1130 Vienna
Austria
Bremin & Co. AB
Pontonjargatan 1
S-112 22 Stockholm
Sweden
USA OCI - Online Communications, Inc.
22 State Street
Bangor Maine 04401
USA
Canada 1B Systems Management, Ltd.
5761 Ascot Road
Nanaimo BC V9V 1E6
Canada
- 121 -
G.1 Pricing
FrontDoor and TosScan for commercial use:
Suggested retail price: USD 189
FrontDoor and TosScan for commercial use (SysOps):
Suggested retail price: USD 120
FrontDoor for commercial use (SysOps):
Suggested retail price: USD 99
TosScan
If you have purchased a copy of FrontDoor, you may purchase
TosScan at the price of USD 30. If you are running the
noncommercial version of FrontDoor, the price for TosScan is
USD 45.
G.2 Shipping and handling
Make sure you include sufficient funds for shipping and handling
(around USD 6-10). If sales tax apply to your order, you must
include funds to cover it.
G.3 Dealers
Please contact the appropriate dealer (previous page) for
commercial inquiries and any questions you may have regarding the
purchase of FrontDoor and/or TosScan.
- 122 -
Appendix H
Developer notes
A separate package with information regarding FrontDoor is
distributed under the name FDDEV. It contains structures and
technical information directed towards authors of FrontDoor
utilities.
If you are planning on writing a utility with explicit support
for FrontDoor, make sure you grab a copy of the FDDEV package and
look at it.
- 123 -
Appendix I
Credits
Thanks to..
..Anders Johansson, Andrew Khoo, Bill Bolton, Bill Dunn,
Bjorn Bogfelt, Bob Rudolph, Boris Osadciw, Chris Homrighausen
(hey bro!), Chris Van Tuin, Chris Baker, Clement Studer, David
Kerley, Dieter Soltau, Eelco de Graaff, Felix Kasza, Fred
Vlinkervleugel, 1B Systems Management Ltd, Ken McVay, Gareth
McClean, Horst Buhl, James Henthorn, James Smith, Jan
Crommenacker, Jan Jonsson, Jeff Wolach, Jerry Hindle, Jim
Faucette, Joakim Hernberg, John Huls, Jon Schneider, Ken Doebler,
Kim Lykkegard, Lasse B, Malte Erikson, Mario Diaz, Mark Howard,
Mats Knuts, Mats Wallin, Peter Adenauer, Randy Harner, Rick
Petersen, Rick Siegel, Robin Valle', Ruud de Bruin, Scott Samet,
Thomas Stjernstrom, Thomas Sundblom, Todd Lehr, Tomas Bremin,
Bremin & Co AB, Tony Wagner, Ulf Hedlund, Ulf Jungjohann, Andreas
Polz, David Nugent, Workware Australia Pty Ltd, Steve Froeschke,
Eric Larson, Bob Beilstein, Bruce Bodger, Michele Hamilton, Phil
Mackay, Michael Butler, Paul Schlyter, Bill Kraski, Alexander
Holy, Lars Eriksson, Fabiano Fabris, Aaron Schmiedel, Mike Janke,
Peter Janssens, Jeff Murphy, Gary Funk, Luca Leone, Andrew
Milner.
..Tom Jennings, Bob Hartman, Chris Irwin, Chuck Forsberg,
Henk Wevers, Randy Bush, Ray Gwinn, Thom Henderson, Vince
Perriello, Wynn Wagner III, Mike Ratledge, Rick Moore, George A.
Stanislav, jim nutt.
- 124 -
Contents
Chapter 1 Preface 3
1.1 Hardware requirements . . . . . . . . . . . . 3
1.2 Software requirements . . . . . . . . . . . . 3
1.3 BBS software . . . . . . . . . . . . . . . . 4
1.4 History . . . . . . . . . . . . . . . . . . . 4
Chapter 2 Installation 7
2.1 CONFIG.SYS . . . . . . . . . . . . . . . . . 7
2.2 AUTOEXEC.BAT . . . . . . . . . . . . . . . . 8
2.3 Directories . . . . . . . . . . . . . . . . . 8
2.4 Files . . . . . . . . . . . . . . . . . . . . 8
Chapter 3 Setup 9
3.1 FD environment variable . . . . . . . . . . . 9
3.2 Getting started . . . . . . . . . . . . . . . 9
3.3 Menus . . . . . . . . . . . . . . . . . . . . 9
3.3.1 File . . . . . . . . . . . . . . . . . 10
3.3.2 Global . . . . . . . . . . . . . . . . 10
3.3.3 Mailer . . . . . . . . . . . . . . . . 13
3.3.4 Editor . . . . . . . . . . . . . . . . 20
3.3.5 Terminal . . . . . . . . . . . . . . . 22
3.3.6 Modem . . . . . . . . . . . . . . . . 24
3.3.7 Printer . . . . . . . . . . . . . . . 28
3.4 Manager . . . . . . . . . . . . . . . . . . 28
3.4.1 Events . . . . . . . . . . . . . . . . 28
3.4.1.1 External event behavior . . . . . 30
3.4.1.2 Mail event behavior . . . . . . . 31
3.4.1.3 The @ event . . . . . . . . . . . 33
3.4.1.4 Overlapping events . . . . . . . 33
3.4.2 Folders . . . . . . . . . . . . . . . 34
3.4.3 Security . . . . . . . . . . . . . . . 35
3.4.4 Requests . . . . . . . . . . . . . . . 36
Chapter 4 Mailer 37
4.1 Menus . . . . . . . . . . . . . . . . . . . 37
4.1.1 Alt-P Programs . . . . . . . . . . . 37
4.1.2 Alt-U Utilities . . . . . . . . . . . 38
4.1.3 Alt-M Mail . . . . . . . . . . . . . 39
4.1.4 Alt-Y Your profile . . . . . . . . . 39
4.2 Alt-B Mail queue . . . . . . . . . . . . . 40
4.3 Call progress . . . . . . . . . . . . . . . 41
4.4 Waiting mail indicator . . . . . . . . . . 42
i
4.5 Undialable . . . . . . . . . . . . . . . . 42
4.6 Command line switches . . . . . . . . . . . 42
Chapter 5 Editor 44
5.1 Menus . . . . . . . . . . . . . . . . . . . 44
5.1.1 Alt-M Main . . . . . . . . . . . . . 44
5.1.2 Alt-E Edit . . . . . . . . . . . . . 46
5.1.3 Alt-T in edit mode . . . . . . . . . . 46
5.1.4 Toggle menu . . . . . . . . . . . . . 47
5.1.5 Other keys in edit mode . . . . . . . 48
5.1.6 Other keys in view (read) mode . . . . 48
5.1.7 Alt-U Utilities . . . . . . . . . . . 49
5.1.8 Alt-P Purge . . . . . . . . . . . . . 50
5.2 Entering messages . . . . . . . . . . . . . 51
5.2.1 Message status bits . . . . . . . . . 51
5.3 Alt-F9 Management . . . . . . . . . . . . 53
5.3.1 Main menu . . . . . . . . . . . . . . 53
5.3.2 Continuoues tagging . . . . . . . . . 54
5.3.3 Range select . . . . . . . . . . . . . 54
5.4 Keyboard macros . . . . . . . . . . . . . . 55
5.5 Carbon copies (CC) . . . . . . . . . . . . 55
5.5.1 Hidden CCs . . . . . . . . . . . . . . 56
5.5.2 Using files as input to CCs . . . . . 56
5.5.3 Address expansion . . . . . . . . . . 66
5.6 Cross-posting (XC) . . . . . . . . . . . . 56
5.7 Command line switches . . . . . . . . . . . 57
Chapter 6 Terminal 58
6.1 Menus . . . . . . . . . . . . . . . . . . . 58
6.1.1 Alt-F File . . . . . . . . . . . . . 58
6.1.2 Alt-L Line settings . . . . . . . . . 59
6.1.3 Alt-S Session . . . . . . . . . . . . 61
6.1.4 Alt-O Options . . . . . . . . . . . . 62
6.2 Keyboard macros . . . . . . . . . . . . . . 62
6.3 Raw mode . . . . . . . . . . . . . . . . . 62
6.4 Keypad modes . . . . . . . . . . . . . . . 62
6.4.1 PC keyboards . . . . . . . . . . . . . 63
6.5 Alt-P Phone directory . . . . . . . . . . 63
6.5.1 Queue status . . . . . . . . . . . . . 64
6.5.2 Adding/changing entries . . . . . . . 64
6.6 Inactivity timer . . . . . . . . . . . . . 64
6.7 File transfers . . . . . . . . . . . . . . 64
6.8 On-line timer . . . . . . . . . . . . . . . 64
Chapter 7 Miscellaneous 65
7.1 Destination of messages . . . . . . . . . . 65
7.1.1 Name lookups . . . . . . . . . . . . . 65
7.1.2 Address browsing . . . . . . . . . . . 65
7.1.3 Address macros . . . . . . . . . . . . 65
7.2 File requests . . . . . . . . . . . . . . . 66
7.2.1 Update requests . . . . . . . . . . . 66
7.3 Swapping . . . . . . . . . . . . . . . . . 66
ii
7.4 CRT environments . . . . . . . . . . . . . 67
Chapter 8 Mail routing 68
8.1 Default routing . . . . . . . . . . . . . . 69
8.1.1 Message status . . . . . . . . . . . . 69
8.1.2 Host/hub routing . . . . . . . . . . . 69
8.1.3 Qualifying systems . . . . . . . . . . 70
8.2 Route commands . . . . . . . . . . . . . . 70
8.2.1 LIST specifications . . . . . . . . . 72
8.2.2 Using nodelist flags . . . . . . . . . 73
8.2.3 File routing/forwarding . . . . . . . 73
8.2.4 Message forwarding . . . . . . . . . . 73
8.2.5 Multiple zones . . . . . . . . . . . . 74
8.2.6 Examples . . . . . . . . . . . . . . . 75
8.2.7 Dynamic packing . . . . . . . . . . . 75
8.2.8 Regarding points . . . . . . . . . . . 75
Chapter 9 EMSI 76
9.1 Passwords . . . . . . . . . . . . . . . . . 76
9.2 Mail . . . . . . . . . . . . . . . . . . . 77
Chapter 10 Script language 78
10.1 What can I do with it? . . . . . . . . . . 78
10.2 Commands . . . . . . . . . . . . . . . . . 79
10.2.1 Labels . . . . . . . . . . . . . . . 83
10.2.2 Node block . . . . . . . . . . . . . 83
10.3 PC Pursuit . . . . . . . . . . . . . . . . 84
10.3.1 How do I update PCP.DAT? . . . . . . 84
10.4 MNEMONICS . . . . . . . . . . . . . . . . 84
Chapter 11 Nodelist 85
11.1 FDNODE.CTL . . . . . . . . . . . . . . . . 85
11.2 Compiling the nodelist . . . . . . . . . . 88
Chapter 12 FDServer 89
12.1 What is a FDServer request? . . . . . . . 89
12.2 Request message . . . . . . . . . . . . . 89
12.2.1 Internal commands . . . . . . . . . . 90
12.3 Using it . . . . . . . . . . . . . . . . . 90
12.4 Keeping calls to a minimum . . . . . . . . 91
12.5 A word of caution . . . . . . . . . . . . 91
Chapter 13 Service requests 92
13.1 Service requests vs FDServer . . . . . . . 92
13.2 Setting up . . . . . . . . . . . . . . . . 92
13.2.1 Service name . . . . . . . . . . . . 92
13.2.2 Program . . . . . . . . . . . . . . . 93
13.2.3 Parameters . . . . . . . . . . . . . 93
13.3 Macros . . . . . . . . . . . . . . . . . . 93
13.4 ^ - + . . . . . . . . . . . . . . . . . . 94
13.5 Security . . . . . . . . . . . . . . . . . 94
13.6 A word of wisdom . . . . . . . . . . . . . 95
iii
Chapter 14 Points 96
14.1 Pointlist . . . . . . . . . . . . . . . . 96
14.2 FDNODE.CTL . . . . . . . . . . . . . . . . 97
14.3 Point handling . . . . . . . . . . . . . . 98
14.4 Remapping . . . . . . . . . . . . . . . . 98
14.4.1 POINTNET . . . . . . . . . . . . . . 98
14.4.2 Echomail . . . . . . . . . . . . . . 99
Chapter 15 Batch files 100
15.1 Errorlevels . . . . . . . . . . . . . . . 100
15.2 Categories . . . . . . . . . . . . . . . . 100
15.3 Loading BBS software . . . . . . . . . . . 101
15.3.1 Different labels . . . . . . . . . . 102
15.3.2 Same label . . . . . . . . . . . . . 103
15.3.2.1 DOBBS.BAT . . . . . . . . . . . 104
15.3.2.2 EXEBBS.BAT . . . . . . . . . . . 105
15.3.2.3 Flow (batch files) . . . . . . . 106
Appendix A Help systems 107
Appendix B FOSSIL drivers 109
B.1 BNU . . . . . . . . . . . . . . . . . . . . 109
B.2 X00.SYS . . . . . . . . . . . . . . . . . . 110
Appendix C Modems 111
C.1 General requirements . . . . . . . . . . . 111
C.2 USR HST . . . . . . . . . . . . . . . . . . 112
Appendix D Multitasking 113
D.1 NS16550 . . . . . . . . . . . . . . . . . . 113
D.2 DESQview . . . . . . . . . . . . . . . . . 114
D.3 DoubleDOS . . . . . . . . . . . . . . . . . 115
D.4 Multilink . . . . . . . . . . . . . . . . . 116
Appendix E Converting from other mail systems 117
Appendix F Sample (PCP) script 118
Appendix G Commercial inquiries 121
G.1 Pricing . . . . . . . . . . . . . . . . . . 122
G.2 Shipping and handling . . . . . . . . . . . 122
G.3 Dealers . . . . . . . . . . . . . . . . . . 122
Appendix H Developer notes 123
Appendix I Credits 124
iv