Category : Communication (modem) tools and utilities
Archive   : FONDIR59.ZIP
Filename : FONERR.DOC

 
Output of file : FONERR.DOC contained in archive : FONDIR59.ZIP
FONDIR Diplay Information and Error List
Copyright (C) 1988-1991 Henry C. Clark
All right reserved.



>> BBS List to "Comm Program" Import

The normal message for BBS List to Comm Program translation. You
are making a Comm Program Phone Directory from a text BBS list.


>> "NNN" entries in "NNN" records for "filename"

The normal message for import telling how many records in the
Comm Program file.


>> , renamed to "filename"

The normal message for import telling about file renames because
the BBS list had more entries than the Comm Program supports in a
single file.


>> Normal completion.

The normal message when no fatal errors have occurred.


>> No parms Help Screen for "program"

The message displayed when no parameters were input on the program
call, ie. help was desired.


>> Only a WARNING : Exchange code file not found for : "NNN"

A warning only, this will not stop processing. FONDIR can not find
an LDAREA or METRO exchange code file for the area codes you
specified with the /l: or /d: parameters.


>> "Comm Program" to BBS List Export

The normal message for Comm Program to BBS List translation. You
are making a text BBS List from a Comm Program Phone Directory.


>> "NNN" entries out of "NNN" records appended.

The normal message for export, telling how many records where
added to the BBS List file.


>> ERROR : No BBS List File Specified, must specify file name.

You must specify a BBS List file name for either import or export.
For example, in the command : FONDIR BBS.LST /O:B the BBS list
file name is 'bbs.lst'. You probably tried something like :
FONDIR /O:B.


>> ERROR : No Output Type Specified, must use /o: parameter.

You must specify a Comm Program type with the /o: parameter. There
is no default. For example, in the command : FONDIR BBS.LST /O:B
the Comm Program type is 'b' or Boyan. You probably tried something
like : FONDIR DFW.LST.


>> ERROR : No drive, path or extension allowed on "filename"

On export, you can specify the Comm Program Phone Directory file to
export, but you may only specify the file 'name' portion of the file.
For example, in the command : FONDIR NEW.LST /O:B /X:BOYA1 the
specified Comm program file is 'boya1'. You probably tried something
like : FONDIR NEW.LST /O:B /X:BOYA1.FON.


>> ERROR : Can't find "Parm Type" separator in "parameter"

You entered a parameter on the command line that did not have a ':'
separator in it. For example, all parameters use the colon
separator, as in : FONDIR BBS.LST /O:B /P:Z except for the /k
parameter, which is OK by itself. You probably tried something like
: FONDIR BBS.LST /OB /PZ.


>> ERROR : Invalid Switch, as in "parameter"

FONDIR will not run if you mistype a parameter, or enter an unknown
parameter type. You probably tried something like :
FONDIR BBS.LST /R. The "/R" is an invalid parameter.


>> ERROR : File Open on "parameter"

FONDIR tries to open various files, the program could not correctly
open the specified file. FONDIR will attempt to open the BBS list
file, the Comm Program Directory file and possibly a Comm Program
auxiliary file. Most likely, you specified a file name on the
command line which FONDIR wants to read, and which doesn't exist.
Perhaps you have run out of disk space, or have too many files in the
current directory and FONDIR can not open a file for writing.


>> ERROR : Invalid Type Code in parm "parameter"

Using the /o: parameter, you tried to specify a Comm Program type
which is not one of the codes supported. For example, an error :
FONDIR BBS.LST /O:?.


>> ERROR : Invalid Speed Digit in parm "parameter"

Using the /b: or /m: parameter, you tried to specify a speed code
which is not one of the codes supported. For example, an error :
FONDIR BBS.LST /O:B /M:X


>> ERROR : Format specifier error "format key"

Within the BBS list, there must be a Format Key, a line of text
telling where the columns of data are located. The displayed "format
key" is not supported by FONDIR, and must be corrected.


>> ERROR : Format length error "format key" "format key length"

The displayed "format key" has been coded with an invalid length (
data column width ), such as too long, or missing. Correct the key
with an editor and try again.


>> ERROR : BBS File error, or no phone number key available in text file.

FONDIR must find the Phone Number key ( |#nn ) in the BBS list text
file. Actually, that's all FONDIR really requires. Typically the
BBS list file doesn't contain a Format Key Specification at all. Put
one in and retry your command. Another possibility is that you
specified a BBS list file that did not exist.


>> ERROR : Format specifier error "format key"

FONDIR has found the Format Key Specification, but one of the
Format Keys is invalid or not supported. Fix it and retry.


>> ERROR : Disk (protected or full) Open on "filename"

FONDIR has tried to open the "filename" for writing and had a fatal
error. Check your disk statistics.


>> ERROR : Disk (full) Write on "filename"

FONDIR has tried to write to the "filename" and had a fatal error.
Check your disk statistics.


>> ERROR : File read-open on "filename"

FONDIR could not open the "filename" for reading. You probably
mistyped the filename.


>> ERROR : File size on "filename"

On export ( comm program to BBS list ), FONDIR was reading records
from the Comm Program Directory file, and encountered a 'short'
record, which usually implies the file is corrupted.



  3 Responses to “Category : Communication (modem) tools and utilities
Archive   : FONDIR59.ZIP
Filename : FONERR.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. 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/