Category : Pascal Source Code
Archive   : PPC50S.ZIP
Filename : PICSPC.INF
(*****************************************************************************)
(* *)
(* PICSPC - Pascal Integrated Communications System *)
(* *)
(* Copyright (c) 1986, 1987 *)
(* by Les Archambault *)
(* Version for IBM PC'S & Clones *)
(* *)
(* All commercial rights reserved. *)
(* *)
(* This program is based on ROS Vers 3.4 by Steve Fox. It is released *)
(* into the public domain for private use only. Additional thanks to: *)
(* Irv Hoff whose 1k protocal in KMD was invaluable in writing the *)
(* Turbo Pascal routines. The authors of DEARC for the basic code that *)
(* deals with Arc files. The author of ASYNC.ARC for the code to make *)
(* possible the interupt service routines. *)
(* Special thanks to Lindsay Jones, Eric Daniel, Freeman Bradford and *)
(* John Van Hengel for beta testing and support. *)
(* *)
(*****************************************************************************)
The PC version of PICS is operationally equal to the CP/M version. The
main differences are in the directory structure and machine dependent
code. In operation, users will not be able to see any differences
between the two implementations.
PICSPC requires a MSDOS/PCDOS machine with at least 256K of memory and
one serial port. It has been tested with several external modems, and
should also work with internal modems. PICSPC supports 300, 1200, and
2400 baud settings for Com1 or Com2. PICSPC has been tested on a PC-AT
(with hard drive) and XT (with two 360 drives) computers.
Be sure that you have a statement in your CONFIG.SYS file that sets
at least 16 files, as PICSPC uses almost that many at the same time.
PICSPC is configured to use only smart modems that utilize the
Hayes compatible command structure. Your modem must be able to send
results as digits (including the ring indication).
The following modem configuration is assumed:
DCD (pin 8) is supported - (not forced high)
DTR (pin 20) is supported - (not forced high)
RI (pin 22) is not supported (modem result codes are used for ring)
The following modem default switches are assumed:
1 = up DTR supported, do not force to always logic true.
2 = down Send result codes as digits.
3 = down Send result codes to the host.
4 = down Do not echo characters when in command state (off line).
5 = down Do not answer the telephone.
6 = up DCD supported, do not force to always logic true.
7 = up Single line RJ11 telephone connection to modem.
8 = down Enables modem command recognition when in command state.
As an example, your modem initialization string should look something
like...AT E0 V0 Q0 X1 M0 (minimum).
If your initialization string does not include them, PICSPC will add
H0 (to make sure the phone is hung up) and S2=3 (setting up the proper
escape character for this program).
The documentation for PICSPC is the same as for PICS CP/M. The file
PICSPC-2.ARC has been created for this version and includes the
applicable portions of the PICS CP/M documentation. The source code
for PICSPC is in a separate ARC file named PICSPC5x.ARC (the current
version is 5.0).
It is ABSOLUTELY VITAL that you read the Sysop and User documentation
completely before trying to run the PICSPC program! If you do not, you
will not know how to enter the program locally or establish the Sysop
access level for yourself!
It was my intention that the CPM and PC versions of PICS would be
file compatable. Due to the fact that Borland chose to change the
way that random files are stored to disk, this will not be possible
at this time. It will be however, after I write c small conversion
utility, for each operating system, that will modify the files
before they are used. That will be released later.
The included PCSETUP.COM file should be run first. It will generate
the SECTION.BB# file. This file contains the names, descriptions,
access levels and drive locations for all of the named file and
message locations in PICS. In addition, this file contains the
initialization string for your modem, it's top speed and the com
port that PICS will use. (Com1 and Com2 are supported). In addition,
the PCSETUP program will create sub-directories for file sections and
message areas on the drives that you specify when asked.
PICSPC may be run from the root directory or a sub-directory. The only
requirement is that the overlay files ( .000-.003) and the SECTION.BB#
file be located in the same directory as PICSPC5x.COM. PICSPC will make
all of the additional system files that it needs. After creation,
these files must remain in the directory with the PICSPC5x.COM program.
Although you may rename the PICSPC5x.COM file, the overlay files must
NOT be renamed, as they are called from the main program by name.
Once again, I must thank Eric Daniel, Lindsay Jones, Freeman Bradford,
John Van Hengel and the others that have helped make this program
possible. Without them i'm sure it never would have been completed.
Any questions, problems or bugs should be sent via modem to the
DESKTOP PUBLISHING BBS system at 415-856-2771. I will try and reply as
quiclkly as possible.
Les Archambault
2/10/87 Support for entering an ARC type file has been added. It works
just like the feature for LIBrary files. At this time users can not
view the contents (using the Type command) of an ARC member file.
Downloading is possible in all but the batch mode. The individual file
is sent as a separate ARC type file and must be un-arced at the
remote end.
LA
Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!
This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.
But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/