home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HomeWare 14
/
HOMEWARE14.bin
/
bbsutils
/
pcbfv35.arj
/
FEATURES.NEW
< prev
next >
Wrap
Text File
|
1993-08-06
|
33KB
|
571 lines
PCBFV (C) Copyright 1990-1993 Yandell Computer Services
This file describes the new features in recent PCBFV releases.
Please refer to PCBFV.DOC for a basic description of PCBFV.
-------------------------------------------------------------------------
[ PCBFV 3.5 New Features 8/6/93 ] ---------------------------------------
-------------------------------------------------------------------------
* If the caller is using RIP graphics mode in PCBoard, PCBFV will clear the
caller's RIP screen and set it to 25-line mode when first run. This is
useful where RIP menus are used in PCBoard that set the caller's screen as
a full graphics window and leave little or no areas for a process such as
PCBFV to display regular text characters.
* The "(Z)ip extra technical info" command is now "(E)xtra technical info".
This now displays information for ARJ files that is similar to ZIP files.
The differences for ARJ files are:
- The "Type" field to indicate binary or text compression will most likely
always say "binary" for ARJ files, as ARJ requires special command line
switches to force it to try to use text mode compression.
- The "Made By" field will indicate the ARJ "revision" number as assigned
by the ARJ author. This does not correspond to the "version" number. For
instance ARJ 2.41 is considered "Rev 6".
- The equivalent of a ZIP -AV field is not possible since a security stamp
on each member of an ARJ file is not publicly available.
* The enclosed FVMNU (menu) and FVHLP (help) files reflect the change of the
(Z) command to (E) (described above).
* The memory requirement tests for ARJ use in PCBFV have been modified for
the new requirements of ARJ 2.41. This does not affect the (R)ead command
much, but if your flagged file is an .ARJ file (FLAGGED.ARJ), the memory
required for the (F)lag command has increased by 60K. PCBFV.DOC contains
ARJ memory requirements and PCBoard/PCBFV "swap" recommendations.
* The (D) command, which can only be entered when PCBFV is used in LOCAL /L
mode (such as in PCBFiler, FVMM, or local utility) now supports ARJ files.
Sysops using PCBFV in PCBFiler, FVMM or as a LOCAL utility with /L on the
command-line may now (D)elete files from ZIP and ARJ files. As with ZIP
files, PCBFV will warn if the ARJ file might contain a security envelope.
See the section "Notes on the (D)elete command" in PCBFV.DOC for more.
* New Sysop diagnostic command: "(W)atch" allows the local Sysop to see what
the compression utilities are displaying on the screen as PCBFV calls them
when (R)eading or (F)lagging files. (W) is toggled on and off at the PCBFV
prompt by any local use except PCBoard's in-house /LOCALON mode. It is not
available to remote callers, including the Sysop. When "W" is toggled on,
the compression utility will run, then PCBFV will display a "Press (Enter)
to Continue" prompt so the message written by the compression utility will
not be erased. This information could be useful for diagnosing problems
as it could contain error messages from the compression utility.
* PCBFV will now use appropriate language "Y" and "N" (Yes/No) characters if
configured in the PCBoard 15.0 multi-language data file.
* The Sysop configurable prompts in PCBFV configuration files (PCBFV.CNF)
can be made "language aware". Simply create a duplicate PCBFV.CNF file,
giving it the appropriate EXTension. For instance with French, use French
for the prompts in PCBFV.FRE and PCBFV will automatically use PCBFV.FRE
instead of PCBFV.CNF as the configuration file. You do not need to worry
about the configuration file name passed to PCBFV in PCBVIEW.BAT. If it is
PCBFV.CNF and the language is .FRE, PCBFV will look for PCBFV.FRE before
using PCBFV.CNF. If you make changes to PCBFV.CNF in the future you will
need to duplicate the changes in all "language versions" of the file.
* In previous versions of PCBFV, if the caller did not have security to use
the (D)ownload command in PCBoard, they could FLAG the entire file in
PCBFV, only to return to PCBoard and be told they could not download the
file. When the FLAG command is entered to flag the entire file, PCBFV now
checks if the caller has access to the (D)ownload command in PCBoard. If
not, the caller cannot FLAG the entire file.
* PCBFV now performs a signature test on files not having a file extension
of ZIP, ARJ, LZH, ARC, PAK or GIF. PCBFV tests to see if files ending with
other extensions could be ZIP, ARJ or LZH files. If so, they are viewed as
if they had ZIP, ARJ or LZH extensions (respectively). It is not practical
to increase PCBFV's size to test for old ARC and PAK files under similar
circumstances since ARC and PAK files use the same signature and formats,
and to tell them apart requires extra testing. To view ARC and PAK files
with PCBFV they must continue to have .ARC and .PAK extensions.
* Files ending with a .SDN extension will now be tested for the compression
utility used to make them. Previous versions of PCBFV assumed these files
were PAK files. In July 1993 SDN files were changed to the ARJ format. For
this release (PCBFV 3.5) only, if a SDN file is not an ARJ file PCBFV will
assume it is an old PAK file.
FVMM (File View Maintenance Manager) Enhancements (in PCBFV 3.5):
-----------------------------------------------------------------
* INSTANT file profiles with FVMM's "View DOWNLOAD.TXT transfer information"
command. This requires use of the DOWNLOAD.TXT database created by the
PCBFX 2.0 (and later) utility from YCS. All that is needed for FVMM to use
the PCBFX database is to replace the location and name of DOWNLOAD.TXT in
FVMM.CNF with the location AND name of the PCBFX database (the database is
always named PCBFX.DAT). This capability also exists in the FVMM released
with PCBFV version 3.4, but was not documented because PCBFX 2.0 had not
been released. PCBFX is available separately.
* FVMM performs three tasks for handling ZIP comments: View, add & delete.
The wording of two of these functions on the FVMM menu was ambiguous and
caused some people to think FVMM should add and delete advertisement files
inside ZIPs. These FVMM menu selections (wording) are changed as follows:
Old: View ZIP file advertisement (comment)
New: View ZIP file comment (advertisement)
Old: Delete ZIP advertisement (comment)
New: Delete ZIP comment (advertisement)
-------------------------------------------------------------------------
[ PCBFV 3.4 New Features 5/7/93 ] ---------------------------------------
-------------------------------------------------------------------------
* A (T)ransfer Information command has been added. This will display the
approximate amount of time needed (based on the caller's connect speed) to
download the compressed file currently being viewed and the caller created
flag file.
* The FVMNU and FVHLP files contained in PCBFV34.ZIP contain the (T)ransfer
Information command (above).
* Pressing ESC at any input prompt will clear any input and move the cursor
to the beginning of the field. This makes PCBFV behave like PCBoard 15.0
in this area.
* If a caller presses "N" to not continue the FIRST listing of member files
while viewing a compressed file, PCBFV continues reading in certain pieces
of information from the rest of the file. In compressed files that contain
hundreds of member files, this would create the effect of PCBFV pausing
before displaying FVMNU or the PCBFV main prompt. PCBFV will now display
"Reading file" followed by a few dots racing back and forth during this
initial read. This will let the caller know something is happening during
this time.
* LHA is now a valid extension for LZH files (along with .LZH). Some of the
LZH utilities give the compressed file .LHA extensions instead of .LZH.
* PCBFV now supports PCBoard's /LOCALON "in-house" network mode with a local
status line (like PCBoard's) and suspended function key activity.
* The "maximum size to extract" and "maximum lines to (R)ead" settings were
not being ignored as they should in the Sysop /L local and PCBFiler modes.
This has been corrected.
* On certain rare occasions, PCBFV would only display the first member file
of a compressed file if the compressed file had been chosen with PCBFV's
(S)elect command. This has been corrected.
* Update: PCBFV 3.4 and earlier versions work with both PCBoard v.15.0 (in
beta test as of this writing) and PCBoard 14.5/14.5a. You are NOT required
to upgrade to PCBFV 3.4 for use with PCboard 15.0.
* Update: PCBFV 3.4 and earlier versions work with MS-DOS v.6.0 (recently
released as of this writing). You are NOT required to upgrade to PCBFV 3.4
for use with MS-DOS 6.0.
-------------------------------------------------------------------------
[ PCBFV 3.3 New Features 1/29/93 ] --------------------------------------
-------------------------------------------------------------------------
* PKZIP 2.04e support has been added. Please also read the following section
titled "PCBFV 3.2 New Features".
- ZIP -AV stamps have changed from PKZIP 2.04c to 2.04e. The PCBFV
(Z)ip-extra function now displays the -AV status from PKZIP versions
1.10, 2.04c and 2.04e. The PCBFiler-mode (D)elete command also detects
and warns of possible -AV presence from these versions of PKZIP.
-------------------------------------------------------------------------
[ PCBFV 3.2 New Features 1/09/93 ] --------------------------------------
-------------------------------------------------------------------------
* PKZIP 2.04c support has been added. Please read the following thoroughly
before attempting to use PCBFV 3.2 (now 3.3) with PKZIP\PKUNZIP 2.0.
- The compression methods are correctly displayed while (L)isting the
ZIP file contents.
- If a ZIP file contains a PKZIP 2.0 -AV, this is displayed using the
(Z)ip-Extra command. PCBFV will continue to display this information
for PKZIP 1.10 -AV stamps, at least for the time being.
- The standard memory requirements for PKZIP *HAVE* changed. The memory
requirement for PKZIP.EXE 2.0 is now 80K higher when used with PCBFV's
(F)lag command. See the next paragraph on how to continue using
PKZIP.EXE from version 1.10. If you intend to use PKZIP.EXE from
version 2.0 and have been able to use PCBFV without swapping PCBoard
to EMS or disk during shells (/SWAP), or swapping PCBFV to EMS or disk
during (R)eads or (F)lags (FVSETUP), you must now do one or the other.
See the PCBoard manual for information on how to swap PCBoard out of
memory, and the PCBFV documentation for information on swapping PCBFV
from memory. See the paragraph below labeled "MEMORY CONSIDERATIONS".
NOTE: Swapping PCBFV from memory "may" provide enough memory for the
(F)lag function, swapping PCBoard will definitely provide enough.
- The standard memory requirements for PKUNZIP.EXE have NOT changed. See
the paragraph below labeled "MEMORY CONSIDERATIONS".
- A special PKZIP.EXE 1.10 command line switch has been added. Using the
the older version will reduce the memory requirements for (F)lagging
files to the same requirements prior to PCBFV 3.2 and PKZIP 2.0, and
will insure compatibility with the caller's version of the extraction
program. To continue using PKZIP.EXE version 1.10 for caller created
(F)lagged files, follow these steps:
(1) Copy PKZIP.EXE (version 1.10) to PKOLD.EXE.
(2) Copy PKOLD.EXE to the "Location of Compression Utils" as set in
the PCBFV configuration files with FVSETUP.EXE.
(3) Add /OLDZIP to the END of the PCBFV command line in PCBVIEW.BAT.
If this switch is used in PCBFV's Sysop /L local mode, the Delete
command will not be available using PKZIP.EXE version 1.10.
- Memory Considerations: It is realized that with PKZIP 2.0 the memory
requirements mentioned above could actually be reduced rather than
raised if PKZIP and PKUNZIP are used on systems where there is memory
above the standard 640K. Future versions of PCBFV may be made to use
those memory requirements if appropriate. For now, "the lowest common
denominator" (640K only) had to be used in deciding the amounts of
memory that must be available before PCBFV uses PKZIP or PKUNZIP. See
the paragraph above on how to use PKZIP.EXE version 1.10.
* A (P)rogram Information command has been added. This displays the PCBFV
version number and registration information.
* The FVMNU and FVHLP files contained in PCBFV34.ZIP contain the (P)rogram
Information command (above).
-------------------------------------------------------------------------
[ PCBFV 3.1 New Features 11/27/92 ] -------------------------------------
-------------------------------------------------------------------------
* The (L)ist contents and (B)rief list (contents) commands may now be passed
filename specifications. If a filename specification is passed, PCBFV will
then list only those files in a compressed file which match. This is very
helpful in situations where there are many files in a compressed file and
the caller only wants to review listing information on certain files while
viewing the compressed file on-line.
- To pass the (L)ist and (B)rief commands a filename, simply enter a
[SPACE] or semi-colon (;) after the command (L or B), followed be the
filename specification.
- The filename may be any complete filename, or may contain wildcards.
- For example, to list all filenames with an extension of .DOC, the
caller would enter the "L *.DOC" (without the quotes) at the PCBFV
main prompt.
- Entering L or B alone will cause all files to be listed, just as PCBFV
has always worked.
* PCBoard /M multi-port software is now supported by PCBFV. PCBFV will read
PCBOARD.DAT on the node where it is running and automatically determine if
PCBoard /M multi-port software is in use on that node. If it is, PCBFV
will automatically use the FOSSIL interface in the PCBoard /M multi-port
communications driver. No special configuration is necessary when using
PCBFV version 3.1 with PCBoard /M multi-port software.
* The (PAB) (Printer, Alarm, Bell) indicators on the status line will also
include M for multi-port if PCBFV is being used with PCBoard /M software.
FVMM (File View Maintenance Manager) Enhancements (in PCBFV 3.1):
-----------------------------------------------------------------
* Sysops that allow Co-Sysops to use PCBFiler and FVMM through DOORWAY to do
maintenance have been requesting a way to prevent them from using FVMM's
"shell to DOS" menu selection. A password feature has been added to this
function and requires a new entry in FVMM.CNF if used. Instructions for
using a password here are located in FVMM.DOC.
* FVMM will follow the environment BOX=NO setting. This setting prevents the
outer borders from being drawn in PCBoard utilities (PCBSM, PCBSetup, and
PCBFIler) and is helpful when they are used on-line with utilities such as
DOORWAY. When SET BOX=NO is used FVMM will not draw its borders either.
* When using FVMM as the viewer in utilities other than PCBFiler, a problem
could arise if the utility did not strip spaces from the filename as it is
passed to FVMM. FVMM will now strip any spaces as the information comes
in, making it more flexible for use with programs other than PCBFiler.
------------------------------------------------------------------------
[ PCBFV 3.0 New Features 7/31/92 ] -------------------------------------
------------------------------------------------------------------------
* The ability to PageUp while reading text files has been added. This new
command is "P" for PageUp and is available at the "More?" prompt while
reading text. When the Sysop is using PCBFV in any local mode, the actual
PgUp on the keyboard cursor pad may be used. Callers may also use their
PgUp key, but only if their communications program is in "Doorway" mode.
* The ability to scroll the screen left and right for text longer than 79
characters has been added. These commands are "<" and ">" and are
available at the "More?" prompt while reading text. When the Sysop is
using PCBFV in any local mode, the left and right arrow keys on their
cursor pad may be used. Callers may also use their left and right arrow
keys, but only if their communications program is using "Doorway" mode.
NOTE: This enhancement removes the need for the (T)runcate command from
earlier versions of PCBFV. All text is now truncated at column 79. If
text exists past column 79 the caller may scroll the screen to see it.
* When the Sysop is reading text with PCBFV in any local mode, the Home key
on the cursor pad may be used for the (T)op of file command. Also in this
mode the Sysop may use the PgDn key on their cursor pad to advance one
page (the same as pressing [Enter] at the More? prompt). Callers may also
use their Home and PgUp keys, but only if they have enabled the "Doorway"
mode of their communications program.
NOTE: It is up to the individual Sysop to educate their callers on the
advanced use of the cursor pad direction keys and "Doorway" mode
described in the above three paragraphs. Cursor pad direction keys
are NOT required for reading text files. They are only duplications
of other commands and have been added mainly for local Sysop use.
* The (Z)ip-AV command has been CHANGED. It is an all new command called
(Z)ip-extra, which will display extra technical information about a ZIP
file. This extra information includes whether or not member files contain
-AV authenticity stamps, the version of PKZip used to compress the member
file, whether each member file is text or binary, and the host operating
system the ZIP was created in (MS-DOS, Amiga, Unix, etc.). NOTE: Other
file types (non-ZIP) do not contain as readily available (or consistent)
enough) information to use in an "extra" report. As this changes, they
will be added to PCBFV's "Z" function or equivalent command.
* New command: (B)rief contents list. Entering (B) will display the file-
name, the uncompressed length, and the "Other Information" columns. This
is the same brief listing now used at the (R)ead and (F)lag input prompts
when "L" is entered for a list of file names to Read or Flag (see below).
* When requesting a Listing of files at the (R)ead or (F)lag input prompts,
the list of files displayed has been changed from a "5-up" to a "1-up"
format. Previous versions of PCBFV displayed 5 file names across each row
of the screen, in order to display as many file names to the caller as
quickly as possible. This however sacrificed information the caller
could use during file selection. This display is now the same as the one
used for the new (B)rief list command (described above).
* The (FLAG) command may now be entered at the "More?" prompt while reading
text files. This allows a caller to immediately FLAG a file for download
if they determine the file meets their needs. If a caller is viewing a
text file directly (not compressed i.e. F V FILENAME.TXT) they may FLAG
it for download at the "More?" prompt while reading it (FILENAME.TXT will
be flagged for download upon return to PCBoard). If FLAG is entered at
the "More?" prompt while reading a text file from a COMPRESSED file, the
entire compressed file will be flagged for download (this is the same as
entering FLAG at the PCBFV main command prompt). This will only work with
text files long enough to require a "More?" prompt to appear. The (FLAG)
command should not be confused with the "(F)lag individual file" command,
which is available only at the PCBFV main command prompt.
* Security specific PCBFV menu and help files are now permitted. To make
this feature possible, the names of these files had to be changed. You
may use the default files distributed in PCBFV30.ZIP. These contain the
new commands and features found in PCBFV 3.0. If you use your own menu
and help files, be sure to ADD THE NEW COMMANDS, and RENAME these files:
If using PCBFV 2.4 thru 2.5:
- Rename FVMENU to FVMNU
- Rename FVHELP to FVHLP
If using versions earlier than 2.4:
- Rename MENU to FVMNU
- Rename PCBFV.HLP to FVHLP
SUMMARY OF COMMAND CHANGES (if modifying existing text files):
"(T)runcate" is no longer a valid PCBFV command.
"(Z)ip-AV stamp display" is now "(Z)ip extra technical data".
"(B)rief contents listing" should be added.
* A Zero byte message may now be displayed if a caller tries to view a zero
byte file. Many Sysops use zero byte files to designate off-line files
on their systems, or to block certain file names from being uploaded. If
a zero byte file is found by PCBFV, a file called FVZRO is displayed.
Security designations (FVZRO25) and/or language extensions may be used.
* When a caller is in color and performs a text search in a text file, all
"finds" are now colorized on the initial screen displayed after the text
is found.
* Limited PKZIP 1.93a BETA support has been temporarily added. If a ZIP
file is encountered which has been created by this utility, the method of
compression will be displayed. The new (Z)ip-extra command will report
that it was created by PKZip 2.0. The PKUNZIP utility from this package
may be used with PCBFV, however there are no guarantees of compatibility.
If a caller attempts to read a file created with this version of ZIP and
PCBFV is using PKUNZIP ver. 1.1, the message "Error extracting file (2)"
will appear on the screen. The PKZIP from this utility should NOT be used
for compressing member files for the PCBFV (F)lag command.
* Added support for extended IRQ use (above IRQ 7). Previous versions of
PCBFV provided non-standard COM support with IRQ 1 through 7. The IRQ
value may now be 1 through 15. PCBFV reads this information from the
appropriate PCBoard system files. Use of PCBFV with non-standard COM
ports requires no additional installation by the Sysop.
* Some "byte-count", "bank", "file-ratio", etc. type doors require PCBoard
to be installed in different manners regarding how many bytes a caller
receives per day (usually zero). PCBFV makes some attempt to verify that
the caller has sufficient bytes to download a compressed file's member
before allowing it to be (F)lagged for separate download. Installation
requirements required by some of these utilities make it impossible for
other third party programs such as PCBFV to accurately determine this
information. If you are using one of the aforementioned utilities and
PCBFV seems to erroneously state the caller has insufficient daily bytes
to download the (F)lagged member file, add /NOBYTE to the end of the
PCBFV command line in PCBVIEW.BAT. This will allow callers to (F)lag the
individual files, then it will be up to PCBoard and the other process to
determine if they have sufficient bytes to download it.
* Added support for the PCBoard PCBDAT environment variable. This is only
used if PCBOARD.DAT is not found in the node's home directory where
PCBOARD.SYS is located.
* PCBFV will place "Activity not allowed" in the "Other Information" column
for any compressed file member which has a file name that is also a
reserved device name. The (R)ead and (F)lag functions will skip any
requests made on files with these names.
* PCBFV will now view (list only) ARC-7 files. When a file of this type is
encountered, the (R)ead and (F)lag commands will be unavailable.
* A question mark (?) is now valid at the "More?" prompt while reading text
files. This is the same as entering (H) for (H)elp at that prompt.
* In order to accommodate feature and performance enhancements, PCBFV will
no longer view GIF resolutions for GIF files STORED in ZIP files. PCBFV
will still display GIF resolutions for GIF files viewed directly, for
example F V FILENAME.GIF.
* While earlier versions of PCBFV were DESQview aware and behaved, some
performance degradation was discovered when using "virtualized" screens
with DESQview-386. PCBFV's performance is now improved in these cases.
* In PCBFV version 2.5, the ability to detect (while reading) if a text
file turned into a binary file was greatly enhanced. Unfortunately, this
inadvertently removed PCBFV's ability to read non-DOS text files such as
Unix, Amiga, and Mac (which contain line-feeds only, instead of carriage-
returns AND line-feeds like DOS text files). This has been corrected.
* The method used to echo events to a printer (if printer logging has been
turned on in PCBoard) has been made more "generic" in PCBFV.
* Three command line parameters have been added. These are not likely to be
needed by most Sysops, but if you need them, you REALLY need them. Adding
them to FVSETUP is not planned since they should rarely be used.
/NOLPT - PCBFV follows the printer toggle in PCBoard. If you wish only
for PCBoard to echo caller log activity to the printer, add
this to the end of the PCBFV.EXE command line as shown below.
/NOBEEP - PCBFV follows the F7 local alarm in PCBoard. If you wish only
for PCBoard to beep locally at caller input errors, etc. add
this to the end of the PCBFV.EXE command line as shown below.
/NOCALLER - PCBFV writes appropriate entries to the current node's caller
log file (see PCBFV.DOC for a complete list of entries). If you
wish only for PCBoard to place entries in caller log files, add
this to the end of the PCBFV.EXE command line as shown below.
To add any of these toggles, edit your PCBVIEW.BAT batch file as follows:
d:\pcbfv\pcbfv.exe pcbfv.cnf %1 /NOLPT /NOBEEP /NOCALLER
All three are shown in the example above for illustration purposes only.
You may enter one, two, or all three of them in any order desired. Again,
it is recommended to use these toggles only if they are REALLY needed.
FVMM (File View Maintenance Manager) Enhancements (in PCBFV 3.0):
-----------------------------------------------------------------
* In the FVMM selection screen, ESC is used to quit the session. The last
option on the menu was "Shell to DOS". Since this was the last option on
the menu, this was often mistaken for a way to quit the FVMM session. To
help prevent this from occurring, another option was added to the end of
the selection list, which is indeed "Quit". ESC is also still valid for
terminating the FVMM session. The "Shell to DOS" selection has also been
more clearly labeled as "Temporarily exit to DOS command prompt".
-------------------------------------------------------------------------
[ PCBFV 2.5 New Features 12/20/91 ] -------------------------------------
-------------------------------------------------------------------------
* New FVMM (File View Maintenance Manager) utility. Designed for use as
PCBoard's PCBFiler ALT-V utility. Uses PCBFV for viewing, reading, etc.
Allows installation of a GIF (etc.) picture viewer. Allows installation of
a test facility (such as those used in PCBTEST). View, add, or delete ZIP
file comments. Quickly scans DOWNLOAD.TXT (or equivalent) and reports the
uploader's name, upload date, number of downloads, and the date of last
download. Swaps to EMS or disk for minimal memory consumption during shell
functions. Free when PCBFV is registered!
* New (Z)ip-AV display command. PCBFV will display "-AV found" in the "other
information" column when viewing a ZIP with files which contain an -AV
(Authenticity Verification) stamp. NOTE: PCBFV does not check the validity
of the -AV stamps, it simply displays the files which contain them when a
(Z) command is entered. *See PKZIP NOTE below.
* New FLAG (or FL) command will cause the entire file being viewed to be
flagged for download upon return to PCBoard. (FLAG) is fully compatible
between files while selecting other compressed files to view with PCBFV's
"(S)elect new file" feature. If a file is viewed from PCBoard's F V, and
four additional compressed files are (S)elected while using PCBFV and FLAG
is entered while viewing each of these five files, each will be flagged
for download upon return to PCBoard! If individual (F)lagging is performed
on some files, and other files are (FLAG)'ed completely, the FLAG files
plus the file containing individual files (FLAGGED.ZIP) are all flagged
for download upon return to PCBoard!
* Added a new Sysop local (only) maintenance command which may be used by
the Sysop in PCBFV's /L local maintenance mode. It is the (D)elete file in
a ZIP (only) file command. The (D) command can only be entered when PCBFV
is in a LOCAL /L mode (such as in PCBFiler, FVMM, or local utility). This
command is completely disabled when PCBFV is being used remotely. The (D)
cannot be entered at the PCBFV prompt while PCBFV is running with PCBoard.
When a filename is entered for (D)elete, PCBFV will prompt the Sysop to
make sure that everything is correct.
If the Sysop enters a (D) command while viewing a ZIP file which contains
ANY files with an -AV stamp, PCBFV will warn the Sysop that the ZIP file
MIGHT be an -AV file and prompt the Sysop if to continue or not. *See the
PKZIP NOTE below.
* Local Sysop text reading capability has been enhanced so that the top line
of text does not scroll of the screen while being used locally (this did
not happen to on-line callers). PCBFV will now compensate for the "two-
line" status line at the bottom of the screen so that the top line of text
will not scroll off of the screen while the Sysop is reading text files in
any of PCBFV's local modes (Sysop on locally, PCBFiler, etc.).
* PCBFV will now accept uncompressed text file names with no extensions when
a period has been added to the file name at the PCBoard F V prompt. PCBFV
will also allow the caller to (S)elect an uncompressed text file without
an extension by adding a period to the filename in PCBFV's (S)elect prompt
(as in PCBoard's F V prompt).
-------------------------------------------------------------------------
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Very early PCBFV versions are listed below with their version numbers and
release dates only. The detail has been omitted to keep the size of this
file lower. Contact the author if this detail is needed.
(Versions 2.5 through 3.5 are all listed in detail above)
Version 2.45 - 08-24-91
Version 2.4 - 07-24-91
Version 2.3 - 04-26-91
Version 2.2 - 02-22-91
Version 2.1 - 11-21-90
Version 2.0 - 10-19-90
Version 1.1 - 08-02-90
Version 1.0 - 07-19-90