Category : Communication (modem) tools and utilities
Archive   : PROFON10.ZIP
Filename : PFE-READ.ME
save the directory to disk when you leave PFE! The results are
unpredictable. At this time, ProComm is not aware of PFE, and
cannot be expected to suspect that you have changed the disk file
while through the gateway.
Profonedit ("PFE") requires MS-DOS or PC-DOS 2.0
or later, and a computer with a display compatible with the IBM
CGA or MDA or the Hercules monochrome graphics adapters, and an
IBM PC or AT compatible keyboard. (Some keyboard commands
described here may work differently or not at all on an IBM PC
jr.) PFE requires a minimum of 125K bytes of available RAM.
To print out the users' manual, use your favorite word processor
or printing program, or: Put the file PFE.DOC into the current
subdirectory of the logged drive, turn on your printer, position
the paper at the top of a sheet, and type COPY PFE.DOC
PRN[Enter]. ("[Enter] means to press the Enter or Return key.
Don't press the [].) You may also view the users' manual on the
screen, by typing TYPE PFE.DOC | MORE[Enter] or (much,MUCH
better) by using Vern Buerg's LIST.COM: LIST PFE.DOC[Enter].
Place the files PFE.COM, PFE.000, and PFE.HLP in the same
subdirectory on the same disk. If you can, put them in the same
subdirectory on the same disk as the files PROCOMM.DIR and
PROCOMM.PRM, or any other ProComm directory files you want to
process.
Make the PFE subdirectory the current one (using the dos CD
command). If you want to process PROCOMM.DIR, and it is in the
PFE subdirectory, then at the DOS prompt, just type:
PFE[Enter]
If you want to process a different directory, or PROCOMM.DIR is
not in the PFE subdirectory, then at the DOS prompt type:
PFE dr:\path\filename[Enter]
where "dr:" is the drive the directory is on (if not the same as
the one PFE is on), "\path\" is the "path" to that file (if not
the PFE subdirectory), and "filename" is the name of the file.
For example, if the file PFE.DIR (included as a sample directory
file) were in subdirectory \COM\PROCOMM on the C: drive, and PFE
were in the \UTIL subdirectory of the D: drive, you might start
like this:
C>d:
D>cd \util
D>pfe c:\com\procomm\pfe.dir
That would (1)log you on to the D: drive, where PFE was located;
(2)change to the \UTIL subdirectory, where PFE was located; and
(3)tell DOS to load PFE and PFE to look for PFE.DIR in the
subdirectory \COM\PROCOMM on the C: drive.
For starters, put PFE.DIR in the PFE subdirectory, and command
"PFE PFE.DIR" to see the sample directory file.
To leave PFE and return to DOS, press Alt-X. ("Alt-X" means to
hold the "Alt" key down while pressing "X" or "x".) If you made
changes to the directory while in PFE, you will be prompted to
save it to disk. If you do, and disk space permits, the original
disk file will be saved, with the extension .BAQ (eg,
PROCOMM.BAQ). Note that the original disk file must be present
for PFE to save the directory.
Files on this disk or in this .ARC file should include:
PFE.COM program main file
PFE.000 program overlay file
PFE.HLP on-line help
PFE.DOC users' manual
PFE-READ.ME this file
PFE.DIR sample ProComm directory file
PFE-ASP.TXT information on ASP
Additionally, you may have the file PROFON10.ARC, even if you
received PFE on disk, in unarchived form. If you did receive the
unarchived files, and all of the files listed above were
included, you do NOT need anything from PROFON10.ARC. It is
included as a convenience to you, should you be so kind as to
distribute PFE to friends, coworkers, user group libraries, etc.
By distributing only the .ARC file, you can be sure of including
everything that will be required for use of PFE, as well as
satisfying all of the license requirements regarding material to
be distributed with copies. If you do distribute PFE, thank you!
Note that all of the files listed above, and only those files,
should be in the .ARC file.
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/