home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Share Gallery 1
/
share_gal_1.zip
/
share_gal_1
/
UT
/
UT100.ZIP
/
CHECKUP.DOC
< prev
next >
Wrap
Text File
|
1988-06-06
|
33KB
|
842 lines
Checkup (tm)
CHECKUP.DOC
Copyright (c) 1988 Richard B. Levin
All Rights Reserved
Program: Checkup
Version: 1.7
Compiled: June 6, 1988
Function: Detects file size and incremental checksum changes
Class: Anti-virus program
Price: $5.00 per copy/per PC
Editor: Norton Editor v.1.3C
Compiler: Microsoft BASIC v.6.0
Math LIB: Alternate (/FPA)
External: AdvBAS CHECKSUM v.9a
Trace: AddLine v.1.3
Author: Richard B. Levin
Contact: BBSoft, P.O. Box 14546, Phila., PA, 19115
Lab: (215) 677-9782
BBS's: (215) 969-8379 or (215) 635-5226 (300/1200/2400)
Archiver: PKARC v.3.5 (-oc switch used)
Beta testers: Katherine Margolis
Keith R. Russell
Scott M. Russell
Documentation written by: Richard B. Levin
Documentation edited by: Carol J. Levin
Katherine Margolis
Principal distribution points: BBSoft Support BBS's (see above)
CompuServe Information Service IBMNET
CHECKUP is published by:
BBSoft
9405 Bustleton Ave.
P.O. Box 14546
Phila., PA 19115
"Since 1982"
BBSoft Lab: (215) 677-9782 *
BBSoft Support BBS's: The eYE oPENeR BBS - (215) 969-8379 *
The Line Noise BBS - (215) 635-5226
* Beginning July 1, 1988, our telephone numbers will be:
Lab: (215) 333-6922
BBS: (215) 333-6923
BBS: (215) 635-5226
The latest version of CHECKUP is available for downloading on the
BBSoft Support BBS's. Support is also available through the BBSoft Lab.
Please leave a message on our answering machine if we are unable to answer
your call personally. We return long distance calls after 6:00 PM EST,
collect.
==============
IMPORTANT NOTE
==============
Please read this document in its entirety before using CHECKUP.
========================
DOCUMENT FORMATTING NOTE
========================
This document is formatted for 80 columns, no margins, with tabs set
every 8 characters.
================
ARCHIVE CONTENTS
================
The CHKUP17.ARC archive contains four files:
CHECKUP.BAT - example of CHECKUP batch file procedures
CHECKUP.DOC - this file
CHECKUP.EXE - Checkup v.1.7 executable
REGISTER.DOC - BBSoft owner registration form
================
COPYRIGHT NOTICE
================
The names "BBSoft," "CHECKUP," and the CHECKUP program, documentation,
CHECKUP-created input and output files, interface, look, and feel (hereinafter
referred to as "the CHECKUP system") are copyright (c) and trade mark (tm)
1988 Richard B. Levin (hereinafter referred to as "the author"), all rights
reserved.
The author reserves the right to make changes to the CHECKUP system at
any time without prior notice. The CHECKUP system is provided to the end user
"as is" without warranty of any kind, either express or implied. No part of
the CHECKUP system may be reproduced without the express written permission of
the author.
The CHECKUP system is protected by United States Copyright Law (Title
17 United States Code). Unauthorized reproduction, duplication, transfer,
and/or sales may result in imprisonment of up to one year and fines of up to
$10,000.00 (17 USC 506). Copyright infringers may also be subject to civil
liability. The Federal Bureau of Investigation investigates allegations of
criminal copyright infringement.
==================
OWNER REGISTRATION
==================
------------------------------
CORPORATE AND GOVERNMENT USERS
------------------------------
For-profit, non-profit, and not-for-profit corporations, governmental
offices and agencies, and/or private individuals using CHECKUP within one of
these classifications, are required to register their ownership of the CHECKUP
system with the author. Every registration must be accompanied by a
registration fee of $5.00 for each computer being protected by the CHECKUP
system.
-------------
PRIVATE USERS
-------------
Private, individual users of CHECKUP are required to register their
ownership of the CHECKUP system with the author, but are not required to remit
the $5.00 registration fee. Donations are accepted.
---------
ALL USERS
---------
CHECKUP USERS WHO FAIL TO REGISTER THEIR OWNERSHIP OF THE CHECKUP
SYSTEM ARE IN VIOLATION OF UNITED STATES COPYRIGHT LAW.
=================
REGISTRATION FORM
=================
ALL USERS ARE REQUIRED BY LAW TO COMPLETE AND RETURN THIS FORM
WITHIN TEN DAYS OF THE ACQUISITION OF THE CHECKUP SYSTEM
- - - - - - - - - - - - - - - - - Tear Here - - - - - - - - - - - - - - - - - -
Print, complete, and mail to: BBSoft
CHECKUP v.1.7 Registration
P.O. Box 14546
Phila., PA 19115
>>>-> IMPORTANT: Make checks payable to "Richard B. Levin"
Do not make checks payable to BBSoft or CHECKUP
Registered Owner Name: _______________________________________________________
_______________________________________________________________________________
Title: _______________________________________________________________________
_______________________________________________________________________________
Department: __________________________________________________________________
_______________________________________________________________________________
Company: _____________________________________________________________________
_______________________________________________________________________________
Address: _____________________________________________________________________
_______________________________________________________________________________
P.O. Box: ____________________________________________________________________
_______________________________________________________________________________
Mail stop: ___________________________________________________________________
_______________________________________________________________________________
City: ________________________________________________________________________
State: _______________________________________________________________________
Zip: _________________________________________________________________________
Phone: _______________________________________________________________________
Total number of PC's at site using CHECKUP: __________________________________
Registration fee enclosed ($5.00 per PC): $ __________________________________
- - - - - - - - - - - - - - - - - Tear Here - - - - - - - - - - - - - - - - - -
=======================
NOTE TO USERS OF MS DOS
=======================
The files IO.SYS and MSDOS.SYS are the MS DOS equivalents to PC DOS's
IBMBIO.COM and IBMDOS.COM.
===================
THE PROBLEM DEFINED
===================
Computer programs that appear to be normal applications but, after one
or more uses, destroy data stored on the host system are popularly called
"Trojan horse" programs. Trojans are often distributed by unsuspecting
bulletin board system operators and attack users who do not know, or care to
follow, the proper precautions for evaluating BBS downloads.
After a Trojan is run, it usually obliterates itself as it erases or
scrambles the host system's hard disk. The affected computer user can (and
generally will) warn other users to beware of the program. Consequently, the
active lives of most Trojans are limited.
The newest form of computer terrorism is known as the "computer
virus." A computer virus differs from a Trojan horse program in that it is
infectious. It can replicate, spread, and contaminate other computer systems
in secret, effectively extending its useful life.
The well written computer virus is difficult to detect using modern
file management and anti-Trojan techniques. It is an ingenious bit of code,
infecting systems by inserting itself into a benign program's executable file.
An expertly crafted virus will not change the host file's date or time stamps,
nor will it alter the host file's size or checksum.
Converting the attributes of potential virus targets (such as
COMMAND.COM, IBMBIO.COM, or IBMDOS.COM) to "read-only" might prevent some
viral infections. The intelligently designed virus, however, will first check
the host file's attribute, reset it if necessary, infect, then return the
attribute to its original state.
When an infected program is copied and distributed, the latent virus
exploits the opportunity to spread to other systems. After invisibly
infecting a new host (and often remaining dormant for months), this
clandestine invader will suddenly emerge and do its dirty work. By the time a
virus reveals itself, numerous offspring may have been spawned, each waiting
for its day in the sun.
===========================================
DIFFICULTIES WITH OTHER ANTI-VIRUS PROGRAMS
===========================================
Since the advent of the virus scare of '88, many public domain,
shareware, and commercial utilities for the detection and prevention of
viruses have appeared.
------------------------------------------------
COMMERCIAL SOLUTIONS (or "Hey! What a market!")
------------------------------------------------
Let us examine the commercial programs first. They are overpriced,
over-hyped, underpowered, and provide none of the benefits their shareware
counterparts cannot provide for less money.
Some commercial packages claim to provide a "software antigen." These
programs also infect executables, but in a benign fashion, to prevent
infections by other viruses. This approach can be compared to the way the
polio vaccine protects humans from the polio virus.
We believe users will be uncomfortable injecting a virus, antigen or
otherwise, into all of their executable files. Further, hardware and software
experts are still debating the protective value of software antigens.
------------------------------------------------------------------
PUBLIC DOMAIN AND SHAREWARE SOLUTIONS (and commercial equivalents)
------------------------------------------------------------------
One group of anti-virus offerings compares two mirror-image copies of
a target filespec. There are several problems with this technique:
1. The same level of protection can be achieved
using any file-comparison utility, including those provided
with DOS.
2. Each compared file needs a mirror-image of
itself stored in another directory, a waste of valuable disk
space.
3. A crafty virus will check the "FATs" (File
Allocation Tables) for duplicate files and infect both
copies of the target filespec.
Another group of anti-virus programs (terminate and stay resident,
a/k/a "TSR" programs) remain in memory and monitor for unauthorized disk
writes to selected programs. There are numerous problems with this method:
1. Some computer configurations may not respond
well to particular groupings of TSR programs.
2. Available RAM space may be at a premium.
3. The periodic interruptions caused by TSR
anti-virus programs annoy many users.
4. TSR anti-virus programs frequently generate
false alarms.
5. Only a few files may be monitored at any one
time. All other files are unprotected.
6. An anti-virus TSR is easily detected by an
incoming virus, which is not surprising, since the TSR is
always floating in RAM. A virus could disable or remove the
TSR and proceed with the infection of the host system. For
this reason alone, the anti-virus TSR provides a false sense
of security to the system operator.
Theoretically, a virus has complete control of PC system resources at
the moment of infection. Anti-virus programs renamed and stored in hidden
subdirectories, "write-protected" hard disks, TSR programs, device drivers,
etc., are all subject to the scrutiny of a virus as it examines its host.
Obviously, then, any anti-virus system stored on non-removable media, relying
on support files stored on non-removable media, or residing in memory, is
itself subject to infection.
=================
HOW CHECKUP WORKS
=================
CHECKUP detects viral infections by comparing a target file's size,
its incremental checksum, and its total checksum to previously stored baseline
values.
CHECKUP breaks the target filespec down to a series of randomly sized
blocks of data. These data blocks may vary from one byte to near total file
size. If the size of the file being checked is less than the block size
selected, CHECKUP revises the block size downward. CHECKUP's dynamic block
size allocation allows files as small as one byte to be accurately checked.
CHECKUP scans and compares every byte of the target filespec on a
block-by-block basis. If the recorded file size, any of the block checksum
comparisons, or the checksum totals do not match, CHECKUP alerts the user that
the target file has been altered and possibly infected.
CHECKUP's incremental file checksum technique is preferable to simply
adding up the bytes in a file and comparing past and present checksum totals.
Future viruses may be intelligent enough to calculate a host file's checksum
total, pad their own code with dummy characters to maintain total checksum
integrity, and then infect. Such viruses would defeat other checksum
calculation programs, but not CHECKUP.
We believe it is impossible for a virus to maintain an accurate
intra-block checksum. This is especially true when the checked block size
varies from one byte to near the total file size, the method for calculating
the checksum is unknown, and the results are encrypted.
To survive CHECKUP's scrutiny, a virus would need to know the block
size, exact calculation entry point, checksum calculation algorithm, and the
encryption key CHECKUP used on the target filespec at initialization. The
encroaching virus would then have the difficult (if not impossible) task of
padding its own code with dummy characters, since the adjustments would have
to occur every few hundred bytes. If a super-virus were able to achieve this
high degree of adaptability, it would still be unable to operate in an
internally scrambled condition.
===============
RUNNING CHECKUP
===============
Launch syntax is:
CHECKUP [d:][path]filename[.ext]
Drive letters and path names are optional. Complete filenames and
extensions are required. If you launch CHECKUP without any parameters, the
proper invocation syntax will be displayed.
For example, to check COMMAND.COM on the logged default drive in the
logged default directory, the launch syntax would be:
CHECKUP COMMAND.COM
To check FOO.EXE (a very popular program) on the C: drive in the
\PLOP\PLOP\FIZZ\FIZZ directory, the launch syntax would be:
CHECKUP C:\PLOP\PLOP\FIZZ\FIZZ\FOO.EXE
Any legal DOS path/file name is accepted by CHECKUP. CHECKUP also
supports redirection of standard input and output.
Launch CHECKUP for each file you wish to check. CHECKUP may be
launched as many times as necessary.
------------------------------------
CREATING A CLEAN CHECKUP FLOPPY DISK
------------------------------------
We suggest CHECKUP be run via an AUTOEXEC.BAT file launched from a
"clean" floppy disk. This ensures that files are checked by a pure copy of
CHECKUP booted using uninfected system files, and that the .XUP files have not
been illegally altered.
The following steps explain how to create a clean CHECKUP floppy disk,
using an IBM PC compatible with 2 floppy disk drives (experienced computer
users can adapt these steps to accommodate different hardware configurations):
1. Turn off your computer. Remove all floppy
disks. Wait 60 seconds.
2. Insert a factory master copy of PC or MS DOS
into drive A. Close the disk drive door, and turn your
computer on.
3. After your computer has completed the boot
process, insert a NEW, never used, unformatted floppy disk
into drive B. Close the disk drive door.
4. Enter the command:
FORMAT B: /S
5. After the floppy disk in drive B has been
formatted and the system files transferred, copy CHECKUP.BAT
and CHECKUP.EXE to the floppy disk in the B drive.
6. After CHECKUP.BAT and CHECKUP.EXE have been
copied to the floppy disk in the B drive, enter the
following commands:
REN B:\*.BAT AUTOEXEC.BAT
COPY CON CONFIG.SYS
BUFFERS=33
7. Press F6, then press <CR>.
8. Remove the factory master PC or MS DOS disk from
drive A. Replace it with the factory master copy of your
favorite ASCII editor.
9. Run your ASCII editor, and edit the AUTOEXEC.BAT
file on drive B to reflect those files you want to have
CHECKUP process.
10. After you have finished editing the
AUTOEXEC.BAT file on drive B, remove the factory master copy
of your ASCII editor from drive A. Replace it with the
clean CHECKUP floppy disk from drive B.
11. Press and hold the Ctrl+Alt+Del keys to re-boot
your system. CHECKUP will process the files as specified in
the AUTOEXEC.BAT file and will copy the .XUP files back to
the A drive when finished.
12. After CHECKUP's AUTOEXEC.BAT file has completed
its run, remove the clean CHECKUP floppy disk from drive A
and store it in a safe place.
13. Press and hold the Ctrl+Alt+Del keys to re-boot
your system.
Use the clean CHECKUP floppy disk to boot your system whenever you
want to check files again.
Remember that all viruses, no matter how sophisticated, share the
same, simple weakness: They cannot affect programs or data unless they can
access them. By storing CHECKUP, the CHECKUP AUTOEXEC.BAT file, and the .XUP
files on a clean, bootable floppy disk, and by inserting the clean disk into
your system *ONLY* to re-boot into CHECKUP, you prevent viruses from adversely
affecting CHECKUP's operation.
---------------------------------------
CHECKUP'S CHECKUP.BAT/AUTOEXEC.BAT FILE
---------------------------------------
The following is an example of the suggested CHECKUP AUTOEXEC.BAT file
for a hard disk drive system. This batch file automatically runs CHECKUP and
backs up .XUP files as they are created. It is included in the CHKUP17.ARC
file (under the name of CHECKUP.BAT), and may be edited as necessary:
REM CHECKUP.BAT
REM Copyright (c) 1988 Richard B. Levin
REM All Rights Reserved
REM
REM this batch file maintains clean copies of checkup and .xup files
REM
REM rename to autoexec.bat and store on a clean floppy disk
REM (see CHECKUP.DOC for more info on creating clean floppy disks)
REM
REM make sure we're on the root directory of the hard disk
REM (substitute the disk drive letter of your choice)
REM
C:
CD \
REM
REM copy checkup and any .xup files from a: drive to hard disk
REM
COPY A:\CHECKUP.EXE
COPY A:\*.XUP
REM
REM check files
REM (substitute your list of input files here)
REM
CHECKUP IBMBIO.COM
CHECKUP IBMDOS.COM
CHECKUP COMMAND.COM
REM
REM copy .xup files to the clean floppy disk
REM
COPY *.XUP A:\
REM
REM delete checkup and .xup files from the hard disk
REM
DEL CHECKUP.EXE
DEL *.XUP
REM
REM End of CHECKUP.BAT
COMMAND.COM, IBMBIO.COM, and IBMDOS.COM should be checked on a daily
basis, because they are the most likely targets of a spreading virus.
CHECKUP does not require that the attributes of hidden and/or system
files be changed prior to checking. As long as the correct name of the hidden
and/or system files are specified on the CHECKUP command line, CHECKUP will
successfully check the files.
The first time a file is checked, CHECKUP will create an .XUP file in
the same directory as the target file. CHECKUP creates one .XUP for each
checked file, and requires access to a file's .XUP file during future checks.
For this reason, do not delete .XUP files unless they are backed up first and
restored before running CHECKUP.
If CHECKUP, or any .XUP files, are mysteriously deleted or altered, a
CHECKUP-aware virus may have landed on your system. To prevent a
CHECKUP-aware virus from gaining control of CHECKUP files, use the clean
floppy disk/batch file method described above when running CHECKUP.
CHECKUP will also create and maintain a CHECKUP.LOG file on the root
directory of the logged disk. You can view the CHECKUP.LOG file with any
ASCII editor, and you can delete the CHECKUP.LOG file at any time. The
CHECKUP.LOG file is generated as an informational tool only; CHECKUP does not
not require it to run.
================================================
INCOMPATIBILITIES WITH OTHER ANTI-VIRUS PROGRAMS
================================================
Flu_Shot, a popular anti-virus TSR program, incorrectly flags CHECKUP
as attempting to write to the input file being checked. CHK4BOMB, a popular
anti-Trojan program, incorrectly identifies CHECKUP as capable of reformatting
a hard disk.
CHECKUP's output is restricted to the .XUP files and the CHECKUP.LOG
file. CHECKUP cannot overwrite an input file, reformat a disk, or perform any
other destructive actions.
If you are concerned about the integrity of your copy of CHECKUP, feel
free to visit a principal BBSoft distribution point and download the latest
version. See the top of this document for a list of authorized distribution
points.
==================================================
A COLLECTION OF ANTI-VIRUS, ANTI-TROJAN TECHNIQUES
==================================================
By employing some, or all, of the techniques described below, you will
severely restrict the ability of Trojan horse programs and computer viruses to
affect your system. We welcome your additions to this list.
* Run CHECKUP daily, using the clean floppy disk/batch file method
described above.
* Change executable file attributes to read-only. Poorly engineered
viruses may not be able to alter read-only files.
Executable files include those ending in a .BAT, .COM, or .EXE
extension, or any files loaded in a CONFIG.SYS file. (Some executable files,
such as many Borland International products, actually write to the master
executable when saving configuration information. If such a file has been
converted to read-only, you will have to remove the read-only attribute before
reconfiguring, and reset it afterwards.)
Many public domain and shareware utilities can be used to reset a
file's attributes, including ATTR.COM, available for downloading from the
PC-Magazine IRS (212-696-0360 or 415-598-9100). CompuServe users can GO
PCMAGNET to download ATTR.COM.
If you own the Norton Utilities, you can use Norton's FA.EXE to change
a file's attributes to read-only. To change COMMAND.COM to read-only using
Norton's FA, enter:
FA COMMAND.COM /R+
* Use the SYS command at least once a week to reinstall the system
files onto your boot disk(s). This will eliminate viruses lurking within your
system files.
* Use CONFIG.SYS's SHELL command to rename and/or relocate
COMMAND.COM. See your PC or MS DOS reference manual for more information.
* Use a file-viewing utility (such as Vernon Buerg's LIST) to examine
executable programs. Review ASCII text messages embedded in files.
* Install a hard disk protection utility such as WPT (Write Protect
Tab) or BOMBSQAD (a sophisticated resident read/write manager).
* Do not run files downloaded from public access BBS's that do not
validate new users, or at least those users who upload. If the SysOp of a
board did not contact you personally (either by phone, mail, or automatic
callback), you can be reasonably certain that other users of that system have
not been validated.
SysOps: If validating all new users is a burden, an effective
alternative is to validate them after they upload their first executable file.
* Do not run files downloaded from public access BBS's where the
SysOps do not test and approve all files.
* Beware of suspicious-looking files. A 128 byte .COM file that
unarchives without documentation and whose description reads "Great Word
Processor" should certainly be suspect.
* Do not run files unaccompanied by well written documentation
prepared by the author.
* Do not run files that do not include the name, address, and
telephone number(s) of the author in either the documentation or the program
executable(s).
* Call the program's author and verify the version number, time and
date stamps, file size(s), and archive contents of the files you have
received. Ask the author where you can secure a certified clean copy of the
program and proceed to do so. Then discard the original file and use the
certified copy.
* Download shareware from the shareware author's BBS. Most
professional shareware authors provide support BBS's for their products. You
are guaranteed an uncorrupted version of software when you download it
directly from the source. You are also assured of getting the latest program
versions.
* Inexperienced users should use extreme caution when working with
public domain and shareware FAT/directory editors, directory sorters,
unerasers, disk optimizers, format-recover systems, file movers, or other
low-level DOS utilities. These programs manipulate critical data, and one bug
or errant keystroke can wipe out a hard disk.
Public domain and shareware DOS shells should be treated with care as
they also handle critical disk information. The safest bet for low-level hard
disk management is the Norton Utilities, v.4.0, Advanced Edition, available at
most computer retailers.
* Do not use hacked or pirated software. Software pirates have the
skills and tools needed to create Trojans and viruses. While we are not
suggesting that pirates are definitely the authors of all Trojans and viruses,
the fact remains that some of the deadliest Trojans have been hacked versions
of well-known applications.
* Back up your system regularly. No system exists in a vacuum, nor is
any anti-virus or anti-Trojan technique foolproof. Back up your system on a
daily, weekly, and monthly basis. When and if a disaster strikes, users who
have religiously backed up their systems will have the last laugh!
=====================================
WHAT TO DO IF YOUR SYSTEM IS AFFECTED
=====================================
1. Don't panic.
Many of the allegations of Trojan and viral attacks have been either
unsubstantiated or flatly incorrect. An exploded hard disk is usually the
result of users working with public domain and shareware FAT/directory
editors, directory sorters, unerasers, disk optimizers, format-recover
systems, file movers, or other low-level DOS utilities. Remember, these
programs manipulate critical data, and one bug or errant keystroke can wipe
out a hard disk.
2. Notify other users.
If you are certain your system has been attacked by a Trojan or a
virus, immediately advise other users. If you are a telecommunicator, post a
warning notice on as many BBS's as possible. If you know the name of the BBS
you downloaded the malicious program from, advise the board's SysOp.
3. Contact the proper authorities.
The FBI, state, and local law enforcement agencies have investigated
and solved many cases of computer fraud, break-ins, Trojans, and viruses. In
fact, the FBI is currently investigating the much publicized "Scores" virus.
Concern over computer system security is nothing new. Vandals
injecting Trojan horses or computer viruses into the nation's telephone
network is akin to hackers breaking into mainframe systems and scrambling
data. Their techniques are different, but their intentions, and results, are
the same.
Contrary to popular belief, a Trojan or virus can be traced to its
source. All popular BBS software programs log the date and time of every
call, the caller's name, and any files uploaded. Serious SysOps archive this
data on a regular basis. Technology available to law enforcement agencies can
trace calls to their points of origin using the information stored in BBS log
files. By reconstructing the download/upload history of a suspect file, the
file's author can be located.
The conspiracy theory: Some computer viruses may have been planted by
agents of foreign government(s) to disrupt data and undermine public
confidence in our national computer networks. A "spy" virus might conceivably
find a way to monitor sensitive data and regularly transmit it back to "enemy
headquarters." Clearly, then, the Federal government has a valid interest in
tracking, preventing, and ultimately eliminating the distribution of malicious
software programs. Some might say it's a matter of national security.
===============================
SHAREWARE AUTHORS SUPPORT BBS'S
===============================
The following list contains the names and access numbers of BBS's
operated by the authors of some popular shareware software products. This
list is not complete; we invite your additions. Please send them to:
BBSoft
Shareware Authors Support BBS List
P.O. Box 14546
Phila., PA 19115
You can also phone in your additions to this list via the BBS Lab Line
or the BBSoft Support BBS's (see top of this document for access numbers).
-----------------------------------------------
System Name Access # Product
-----------------------------------------------
ASCII Exchange 1 416 622 8254 TELIX
Aero 1 919 682 4225 BOYAN
CompuServe 1200 1 215 977 9758 CIS
CompuServe 2400 1 215 977 9794 CIS
DataStorm 1 314 449 9401 PROCOMM
* Eye Opener 1 215 969 8379 BBSOFT SUPPORT BBS
Forbin Project 1 319 233 6157 QMODEM
GEnie 1200 1 215 284 9343 GE
GEnie 2400 1 215 284 0206 GE
HomeBase 1 414 962 1097 RYBBS
Interconnect 1 703 827 5762 NOVIRUS
* Line Noise 1 215 635 5226 BBSOFT SUPPORT BBS
MAGPIE HQ Node 1 1 212 420 0527 MAGPIE
MAGPIE HQ Node 2 1 212 677 9487 MAGPIE
MIS 1 215 692 8623 POSTMASTER USER DOCUMENTATION
MiniHost 1 415 373 0954 MINIHOST
PC Mag IRS East 1 212 696 0360 PC-MAGAZINE UTILITIES
PC Mag IRS West 1 415 598 9100 PC-MAGAZINE UTILITIES
PC Pub 1 416 487 4134 TELIX
PC-Rockland 1 914 353 2176 FMAC2COM
PKWARE 1 414 352 7176 PKARC/PKXARC/OTHERS
QFiler 1 608 271 3685 QFILER
Software Connection 1 212 889 6438 FLU_SHOT/RAMNET
TeleGodzilla 1 503 621 3746 ZCOMM/DSZ/OTHERS
Tom Mack's RBBS 1 203 334 4227 RBBS
Vernon D. Buerg 1 415 994 2944 LIST/OTHERS
Your Place 1 703 978 6360 RBBS
Please support the shareware concept by registering the shareware
programs you own.
==============================
REVISION NOTES FOR VERSION 1.7
==============================
The CHECKUP documentation has been revised, with each section reviewed
and updated, a Shareware Authors Support BBS list added, and the new CHECKUP
clean floppy disk/batch file procedure introduced.
We have attempted to maintain compatibility with the after-market
public domain and shareware utilities that support CHECKUP.
====================================================
SOFTWARE PRODUCTS USED IN THE DEVELOPMENT OF CHECKUP
====================================================
Vendor Name
Product(s)
BBSoft
9405 Bustleton Ave.
P.O. Box 14546
Phila., PA 19115
AddLine v.1.3
Postmaster v.2.0
Thomas G. Hanlin III
1712 Maple Hill Place
Alexandria, VA 22302
AdvBAS v.9a
Microsoft Corporation
16011 NE 36th Way
Box 97017
Redmond, WA 98073-9717
Microsoft BASIC v.6.0
Microsoft WORD v.4.0
Peter Norton Computing
2210 Wilshire Blvd.
Suite 186
Santa Monica, CA 90403-5784
The Norton Commander v.1.1
The Norton Editor v.1.3C
The Norton Utilities v.4.0, Advanced Edition
PKWARE, Inc.
7032 Ardara Ave.
Glendale, WI 53209
PKARC v.3.5
===============
RELEASE HISTORY
===============
Ver. Release Date
--------------------
1.0 April 1, 1988
1.1 April 2, 1988
1.2 April 20, 1988
1.3 May 2, 1988
1.4 May 3, 1988
1.5 June 5, 1988
1.6 June 6, 1988
1.7 June 6, 1988
*=============================================================================*
This program must be distributed AS IS without alterations of any kind.
No files may be added to the CHKUP17.ARC file without the express written
permission of the author. This DOC file must be included with CHECKUP.BAT,
CHECKUP.EXE and REGISTER.DOC in the CHKUP17.ARC file.
Released And Distributed Through BBS's All Across America on June 6, 1988
*=============================================================================*
BBSoft "Since 1982" Your Shareware Solution
- End of CHECKUP.DOC -