pct_v6-1of6
PC TOOLS VERSION 7
NEW INFORMATION
For the most up-to-date information about new menu items, command
buttons, and dialog boxes, and about features that work differently
than documented, press F1 in each PC Tools program for online help.
For a list of command-line options, type /? after the program name at
the DOS prompt.
WINDOWS SCHEDULER
=================
Windows Scheduler has been enhanced to schedule the following events:
Commute sessions
Backups
Email
DiskFix analyses
DiskFix will run in the background to perform a disk integrity check of
your local hard drive. If DiskFix detects any disk problems, it will
come to the foreground to report the error. Please see the online help
for additional details.
IF YOU HAVE QEMM OR 386MAX
==========================
If you have QEMM or 386MAX, and if memory is available between 640K and
1MB, Commute and Data Monitor will automatically load themselves high
to conserve conventional memory (memory below 640K).
LOADING PC SHELL AND DESKTOP INTO HIGH MEMORY
=============================================
Utilities that will automatically load Desktop and PC Shell into
expanded or extended memory during installation will soon be made
available free of charge from our BBS or by contacting Central Point
Software.
INTERNATIONAL CONFIGURATION
===========================
If you are using IBM international character set (Code Page 850) and
notice remapped fonts when viewing files, use the /NF option to disable
the alternate fonts. If you are using IBM US character set (Code Page
437), the alternate fonts look fine.
CENTRAL POINT BACKUP
====================
Do NOT use DiskFix to repair a CP Backup disk.
If you want to use Version 6 setup files for a tape backup that will
remain compatible with Version 6, change the Media Format command to
Central Point format before beginning your backup.
COMMUTE
=======
The memory saving utility COMMSML.EXE has not been provided on the
distribution disk. COMMSML.EXE will be available free of charge from
our BBS at a later date.
DATA MONITOR
============
Data Monitor should not be used with Central Point Version 6 programs
such as Backup or Compress. Use the Version 7 programs instead.
Directory Lock
--------------
Don't forget your Directory Lock password. If you do, all data in the
directory will be irrecoverably encrypted.
Delete Sentry
-------------
Always use Undelete to purge files from the hidden \SENTRY directory.
If you delete files from this directory manually or using a program
such as PC Shell (especially if you delete the master file
CONTROL.FIL), Undelete may not be able to recover the protected files.
DESKTOP
=======
Appointment Scheduler
---------------------
The printing capabilities of Appointment Scheduler have been enhanced.
Check the online help for these details and additional information
about enhancements in Desktop.
Electronic Mail
---------------
Electronic Mail can send messages to users on other electronic mail
services accessible through MCI Mail. Check the online help for
details.
DIRECTORY MAINTENANCE
=====================
To print the tree list using graphics characters on a laser printer,
the printer must be using a font that supports the standard extended
ASCII character set, which includes characters used to draw lines and
boxes. See your printer manual for details.
DISKFIX
=======
If you have a Hardcache card from CompuAdd, type DISKFIX /HCACHE to
start DiskFix. Type DISKFIX /HCARD if you have a HardCard from Plus
Development Systems.
PC SECURE
=========
When you run PC Secure from the DOS command line (by including a file
specification and other required parameters), the parameters control
the way files are processed and will override conflicting settings from
the PC Secure Options menu.
VDEFEND
=======
In order to have virus protection on a Novell network, load the network
drivers after VDefend, and add the /N parameter to the VDefend command
in your AUTOEXEC.BAT file:
VDEFEND /N
NOTE: You may not be able to remove some TSR programs from memory
after using this option.
VIEW
====
If you are using the Network Courier Email system on a Novell NetWare
server and run View from the DOS prompt, you may get the message:
"Could not find the file: SPWNVIEW.EXE." This occurs because NetWare
searches a directory used by Network Courier before it searches the
directory where PC Tools was installed.
To make PCTOOLS the first directory searched, use Novell's SYSCON
utility to add the following command to the end of your system login
script:
MAP INS S1:=C:\PCTOOLS
(For C:\PCTOOLS, substitute the drive and directory where PC Tools was
installed.)
Central Point PC Tools Version 8
GENERAL
=======
* For the most up-to-date information about new menu items, command
buttons, and dialog boxes, and about features that may work
differently than documented in the manuals, press F1 in each PC
Tools application for online help.
* For a list of command-line options, type /? after the program name
at the DOS prompt.
* Index entries for Volume 2 of the printed documentation are in
bold italic in the master index.
COMPATIBILITY
=============
Compaticard Users
-----------------
Compaticards that have 2.88MB floppy drives attached have
known incompatibility with PC Tools applications.
DESQview Users
--------------
* For optimum performance with DESQview, PC Tools applications
disable the use of the alternate fonts and the graphics mouse
cursor.
* If your video display blinks when using DESQview with PC Tools
applications, add the Palette utility to the DESQview menu and
turn off the Blink Enable option. Also, when running PC Tools
applications from DESQview, select DESQview in the PC Config
color scheme list to use the best display.
DOS APPEND Users
----------------
The DOS APPEND program has no effect while most PC Tools
applications are running.
Logitech Mouse Users
---------------------
The Logitech mouse driver version 4.10 has known compatibility
problems with DOS 4.0 or later. Upgrade to the newest mouse
driver, version 6.12.
Micrologic Infoselect Users
---------------------------
If you are using Infoselect (IS) 2.0, be sure it is
loaded before PC Tools Desktop in your AUTOEXEC.BAT file.
Novell Users
------------
If you are on a Novell network and load Commute from within
Windows, or map another SPX drive using DriveMap from within
Windows, the VIPX.386 Windows network driver may keep them from
working properly. To solve this problem:
1. Load Commute or DriveMap memory-resident before starting
Windows.
or
2. Edit the Windows SYSTEM.INI file to delete the reference to
VIPX.386 from the "network=" line. Leave the rest of the line
as it is.
Although most systems are unaffected by this, removing this driver
means that multiple DOS applications can no longer access Novell's
IPX services simultaneously.
Packard Bell Mouse Users
------------------------
The Packard Bell mouse driver version 4.0 is not fully compatible
with the Microsoft mouse driver (version 6.14 or later).
Use the Microsoft mouse driver (often provided in Windows)
with this mouse.
QEMM Users
----------
* PC Tools TSRs make use of new technology to load themselves into
high memory automatically. The QEMM Optimize program does not yet
detect TSRs using this new technology and incorrectly optimizes
memory. RAMBoost does detect programs that load automatically,
and should be used instead of QEMM Optimize.
* If you are using QEMM and Windows, and run the PC Tools
applications MI or SI, QEMM reports the wrong version number.
Exit from Windows, then run MI or SI.
* If you load Commute with the /r parameter, or load commsml, and
then run QEMM's Optimize program, Optimize incorrectly places a
LOADHI command in the Commute line. Commute detects this situation
when it tries to load and displays an error message.
SuperStor Users
---------------
SuperStor uses a non-standard boot record, which may cause PC
Format and the EDisk program to not find the system files needed
to create a bootable system disk. Run PC Format and the EDisk
program from the original boot drive (the one DCONFIG.SYS is on).
Example: D:EDISK /BOOT_DEV=x: (x=original boot drive)
SYSGEN Users
------------
PC Tools supports the SYSGEN bridge driver versions 3.44 and
above.
Tandy Users
-----------
PC Tools includes the FIXTANDY.EXE program. If you have a
Tandy system, and the Tandy Setup program sometimes runs
unexpectedly, make sure FIXTANDY is memory-resident before
you use any PC Tools application.
Toshiba 5100 Users
------------------
If some characters do not appear as expected when you run PC Tools
applications, run PC Config. Select Display, Text Mode, and OK.
Then select Color, and choose the Toshiba Gas Plasma color scheme.
Choose Save, then reboot the machine for the changes to take
effect.
UltraVision Users
-----------------
* For optimum performance with UltraVision, PC Tools applications
disable the use of alternate fonts.
* If your mouse does not function normally when using non-standard
line modes (modes other than 80x25, 80x28, 80x43, 80x50), disable
the Fast Mouse Reset option in PC Config, or use the /PS2 command-
line option when starting a PC Tools application.
INDIVIDUAL PC TOOLS APPLICATIONS
================================
Central Point Backup Users
--------------------------
* If you are using disk-caching software (such as SmartDrive or
PC-Kwik) while doing a medium-speed backup or restore, turn off
the delayed-write feature of the cache program to prevent DMA
conflicts. PC-Cache requires no changes.
* Two new command-line options have been added:
/DCHECK Turns on the drive integrity check
/NODCHECK Disables the drive integrity check
Specifying either option at the command line overrides the settings
in the configuration file.
* If you are backing up or restoring the bindery files (and have
sufficient rights to do so), they are automatically backed up or
restored, even though they are invisible on the directory tree.
* If you are restoring data backed up from a Novell network volume,
a new option appears in the Restore Bindery/Trustee/Info dialog
box--Restore Directory Information. When on, CP Backup attempts to
restore the attributes and inherited rights of each directory as
stored on the backup tape. If CP Backup encounters a NetWare
logical error, a message alerts you. The most common error is that
you do not have sufficient network rights to restore a particular
directory.
* CP Backup supports the following SCSI drives:
Archive Python DAT 1.3GB Mountain 7250 250MB
Archive Viper 2060 60MB Mountain 7500 500MB
Archive Viper 2150 150MB Mountain 1200 1.2GB
Archive Viper 2525 525MB NCR 6100 150MB
Archive Viper 5250 250MB NCR 6300 525MB
Cipher ST150 150MB NCR 2101 2.2GB
Compaq 320/525 525MB Tandberg 3600 150MB
Exabyte 8200C 2.5GB Teac MT-01 250MB
Exabyte EXB-8500 5GB Tecmar THS-2200 2.2GB
Exabyte EXB-8200SX 2.5GB Tecmar ProLine 250 250MB
Exabyte EXB-8200 2.5GB Tecmar ProLine 525 525MB
Hewlett Packard C1502A DAT 1.2GB Tecmar ProLine Data Vault 1.2GB
Hewlett Packard C2224 DAT 1.2GB WangDAT 1300 1.3GB
Maynard 250Q 250MB WangDAT 3100 1.3GB
Maynard 525Q 525MB WangDAT 3200 1.3GB
Maynard 1300+ 1.2GB Wangtek 5099ES 60MB
Maynard 2200+ 2.2GB Wangtek 51000ES
Mountain 2100 2.2GB Wangtek 5150ES 150MB
Mountain 7150 150MB Wangtek 5525ES 525MB
Wangtek 7200HS 2.2GB
Central Point Commute
---------------------
* If you have the Callback option selected, but you do not have a
password in your Give Control entry, the Callback feature is
ignored. In this situation, your PC waits for a call as if you had
chosen the Wait for Any Caller button.
* Start Commute with the /NE option if you plan to start Windows
during a Commute session, and you are using EMSNETX.EXE.
* During a file transfer, Commute may intentionally halt your system
if a pop-up warning appears from the memory-resident applications
VSafe, VWatch, or the Directory Lock feature of Data Monitor.
This protects your system from virus-infected files or from using
protected directories. If you want to give access to directories
protected by Directory Lock, run Data Monitor before the Commute
session, and turn off Directory Lock on the host PC.
* Change the following two entries in the Commute Command-Line
Options chapter in the printed manual:
/NCP is no longer a valid option.
/WR should be /WRD.
Datamon - Screen Blanker
------------------------
* To regain control of your computer after Screen Blanker clears the
screen, press any key or move the mouse. If you specified a Screen
Blanker password, type the password and press <ENTER> to regain
control. NOTE: You are not prompted to enter the password. If
you type anything other than the correct password, Screen Blanker
does not return control of the computer. To clear the incorrect
characters, press <ENTER>, then type the correct password and press
<ENTER> again.
DriveMap Users
--------------
* If you are using the parallel port of your AST notebook computer
with DriveMap, set the parallel port to standard mode. To do this,
add the following line to your AUTOEXEC.BAT file on the AST:
ASTPORT /S
* The BIOS of some computers, such as Compaqs, may not recognize the
parallel port of your PC if the cable is plugged into it when you
turn on the PC. DriveMap attempts to resolve this, but if it
cannot find the parallel port, power up your PC without the cable
plugged in. Then plug in the cable, and run DriveMap again.
Emergency Disk Users
--------------------
* The EDisk program automatically calculates the amount of disk space
needed for the options you have selected in the Configuration
dialog box. Many of the options use shared files, such as video
library files and font files. For this reason, the number of
kilobytes displayed may not change by the amount expected when
you select and deselect options.
* The EDisk program does not save the DOSOAD.SYS driver from Iomega
(used with their removable cartridge drives). This is because
Iomega uses a unique driver technology.
Install
-------
* If you are running DR DOS or a version of MS-DOS earlier than 5.0,
Install searches your drives for the first AUTOEXEC.BAT file
in the root directory. If Install cannot find the file, it
prompts you for your boot drive.
* Some PC Tools files are in a different directory than the one shown
in the File List in Volume 1 of the printed manuals. The following
files are now in the SYSTEM subdirectory of the PC Tools directory:
CPSHRINK.EXE CONVERT.EXE MENUCONV.EXE
COMMMAP.EXE MENUED.EXE PCRUN.EXE
* If you are using Direct Access, the PC Tools installation program
converts only version 5.1 files for use with PC Tools Desktop.
* If you install Version 8 files into a separate directory than
Version 7.x files, you will need to manually add the Version
7.x Windows programs--Undelete and CP Backup--to the PC Tools
group in Windows. This is done automatically if you install
Version 8 files over Version 7.x files.
* When you configure Startup Programs during installation,
the contents of batch files called from within your AUTOEXEC.BAT
file are not read. For example, your AUTOEXEC.BAT file may
contain a line like CALL NET.BAT, which loads your network drivers.
PC Tools memory-resident programs may not subsequently load in the
correct order because Startup Programs cannot find the network
drivers. If this is the case, temporarily edit your AUTOEXEC.BAT
file to directly load the contents of the batch files, run PC
Config and select the Startup Programs you want. Save the
configuration, and reboot your machine. After you have rebooted,
you can edit your AUTOEXEC.BAT file to the way it was.
Memory Info (MI)
----------------
If you are using NET5.COM, MI may not identify the DOS 5 Doskey
program.
PC-Cache
--------
SuperStor and Stacker drives default to read-caching only when
PC-Cache loads. You cannot specify a command-line parameter to
delay write-cache these drives. Although you can activate the
delay write-cache option after the cache is loaded, we do not
recommend it.
PC Tools Desktop
----------------
* A new command, Reset Window Size, has been added to the Windows
menu. This allows you to reset all PC Tools Desktop windows to
their default sizes and locations.
* If you change the video mode from large to small (such as from
50-line to 25-line), the open windows are reset to their default
size and position, IF any single window cannot fit on the
smaller screen. If you change the video mode from small to
large (such as 25-line to 50-line), the open windows remain in
their current position.
* A new option, Include Subdirectories in Drop, appears in the
Confirmation dialog box (accessed from the Configure menu). This
option applies when you drag a directory to an application in a
function key or the Menu Window that accepts drag-and-drop file
lists. When the option is off, the operation works only on the
files in the parent directory.
* The Disk menu has the following new commands:
Wipe Disk
Verify a Disk
DM Program now appears on the Directory Maintenance submenu
* Undelete is only available from the PC Tools Desktop when the Data
Monitor Delete Sentry method is turned on.
RAMBoost Users
--------------
* RAMBoost supports MS-DOS versions 3.3 to 5.0, and DR DOS version
6.0 only.
* Use PC Config's Startup Programs option to load RAMBoost,
especially if the RAMBoost directory is not in your path.
* RAMBoost works in conjunction with your memory manager to make
the best use of your memory. If you use RAMBoost, do not use
your memory manager's optimization program, because RAMBoost
replaces that functionality.
* If you want RAMBoost to load programs high that are in your
Novell login script, remove the ignore=login.exe line from the
RAMBOOST.INI file in the [completiontriggers] section.
* If you are using RAMBoost, Windows, and QEMM 6.0, and encounter
QEMM errors, upgrade to QEMM version 6.02 or later.
* RAMBoost does not strip LH and similar commands from batch files
that are called by your AUTOEXEC.BAT file. To ensure that RAMBoost
optimizes all memory-resident programs, remove the LH and similar
commands from all called batch files.
* If you are using a Token Ring adapter:
If you are using a memory manager other than the DOS 5 memory
manager, exclude the shared memory area used by the adapter
before running RAMSETUP. If you are using the DOS 5 memory
manager, log in to the network, and run RAMSETUP. Use the
Upper Memory Usage Editor to exclude the shared memory area
used by the adapter.
* Certain TSRs and device drivers may not get loaded high because
of an unusually large initialization size. You can edit your
RAMBOOST.INI file to instruct RAMBoost to try other optimization
methods. We recommend you use the optmethod option with a -1 value.
See "The RAMBoost Configuration File" section of the RAMBoost
chapter in Volume 1 for instructions.
* Three new options appear in the RAMBOOST.INI file:
ignore: Lets you specify a program file name in this
form: ignore=<filename.ext>. This option allows RAMBoost
in LEARN mode to not attempt to optimize the programs
specified. This option is in the [completiontriggers]
section of the RAMBOOST.INI file.
MinUMBs:Lets you specify minimum free memory in this form:
MinUMBs=<number>. Replace <number> with the number of
free kilobytes that must be available in upper memory for
RAMSetup to install RAMBoost in your CONFIG.SYS file. The
default value is 32, which is enough for most systems. This
option helps avoid low-memory conditions that occur with
some TSRs and device drivers. This option is in the
[system] section of the RAMBOOST.INI file.
TimerType:Lets you specify a display type in this form:
TimerType=<DisplayType>. Replace <DisplayType> with
Elapsed or ETA. These options change the way time appears
on the screen during the optimization process. The Elapsed
option displays the time elapsed from the beginning of the
optimization. The ETA option displays how long RAMBoost
estimates the optimization will take. This value is updated
dynamically during the optimization. This option is in the
[oui] section of the RAMBOOST.INI file.
System Information Users
------------------------
Because of demands Windows makes on system resources, the System
Information's performance results will be different when you run
the application from within Windows compared to DOS. Also, the Disk
Speed test is disabled in Windows.
Task Switcher Users
-------------------
* Some PC Tools applications provide only limited access to Task
Switcher to make sure your data stays intact during low-level disk
access. You cannot use the hotkey to open Task Switcher from within
the following applications:
FileFix Compress Wipe
Undelete Unformat PCFormat
DiskFix (while fixing or checking a disk) CP Backup
Desktop Accessories Telecom online screen
Similarly, while Task Switcher is open and at least one other
application is in the Task Switcher list, you cannot switch to
Compress or Undelete. If you switch to DiskFix in this situation,
you are notified of disk errors, but cannot fix them. To repair
errors, you must end all tasks, and restart DiskFix.
* Do not unload Task Switcher from a batch file. If you do so, no
commands following the CPTASK /u command are executed.
* Do not delete the primary DOS prompt from the Task Switcher list
if you are using NDOS or 4DOS. Task Switcher can only be unloaded
from the primary prompt.
SYSTEM ADMINISTRATORS
=====================
Custom Installation Slides
--------------------------
You can edit the slides that appear during a custom installation
to reflect specific information for your users. The file to edit
is _SLIDES.DOC. The following paragraphs explain how to do this:
All commands must begin in column 1 and start with a period. The
default action is for Install to automatically format running text
into paragraphs, with the left margin starting in column 4 of the
window containing the formatted slide. This window is 74-columns
wide, and the longest line that will display (with 4-character
left and right margins) will be 66 characters. Separate
paragraphs with a blank line.
Do not use tab characters in the file.
You can use the following commands:
.title Defines the beginning of a new slide and text to display
in the banner of the slide window. Insert a space
between the first character of the banner text and the
.title command.
.> Centers all text on the line following the .>. Insert
a space between the first character of the text to be
centered and the .> command.
.nofill Prints all lines following the .nofill command literally,
without any formatting, starting in the currently
defined left margin. All leading spaces are honored. To
return to paragraph fill mode, use the .fill command,
described next.
.fill [x] Blocks all lines following the .fill command into
paragraphs, with lines no longer than 66 characters that
normally start in column 4 (the default). The .fill command
is the default. The optional x parameter specifies the number
of characters each paragraph should be indented, either
negative or positive (for true indentations). However, if a
negative indentation causes a line to begin prior to column 4
of the window, it is treated as an error. If you omit the x
parameter, paragraphs have no indentation.
.lm x Adds x character positions to the default left margin of 4.
Stays in effect until the next .lm command is encountered.
This number must be positive.
.time x Specifies the time x in seconds for displaying this slide.
This command should immediately follow the .title command.
NEW FEATURES IN PC TOOLS GOLD (V9) 1. New Central Point Recuperator (CPR) Central Point Recuperator is an all-new utility that automatically and periodically saves the state of your PC's CPU and memory so you can restore the system in case of a crash, lock up or power failure. If such a crash occurs, you reboot the system and, if you desire, CPR will attempt to restore your system (including data files intact) to the same state that occured when it was last saved. Saves are done on timed intervals and only during "idle" periods to minimize disruption to your work. Setting up Recuperator Setup Procedure: * Enter CPRECUPE /SETUP on the DOS command line. Recuperator Setup asks if you are ready to reboot your machine so that it can write a configuration file for it. Choose OK to reboot the machine. * After Recuperator reboots the machine, you see a series of four dialog boxes that ask for information or provide progress information about the installation process. Select Drive Asks you to choose the drive where you want to store the system image files. These files require as much disk space as you have RAM on your system, including video and LAN card RAM, and 24 KB of overhead space, plus a maximum of 128 KB for the FAT of each local hard drive and compressed volume. Enter Windows Directory Asks you to enter the name of your Windows directory, if you have one. If you have a directory called WINDOWS in your path, Recuperator Setup assumes that this is your Windows directory. Create Startup Files Asks if you want to create the configuration file now, or edit the configuration choices before you save it. Accept the default configuration unless you know that your system has unique requirements. You can tune the configuration later to change hotkeys and other settings. Recuperator Setup adds lines to your AUTOEXEC.BAT and CONFIG.SYS files so that it is loaded when you boot your system. Building Files Shows that the configuration file and saved system file is being built. When the progress thermometer reaches 100%, the dialog box disappears automatically. * The system reboots. The new AUTOEXEC.BAT loads Recuperator in memory so that it can save your system state. * As soon as Recuperator loads, press Ctrl+Left Shift+Right Shift to save the system state manually. The manual save tests the configuration settings. NOTES: Recuperator Setup cannot install Recuperator if you have a multi-boot AUTOEXEC.BAT file. The mouse will be disabled during the second part of the setup. The save file cannot be created on a compressed drive. Recuperator cannot be run with Disk Manager. Recuperator does not work yet on microchannel systems. When you cancel the setup procedure your system will be restored to the original state and rebooted. If you change the Recuperator configuration the system must be rebooted for the changes to take affect. You must run setup again if your system hardware is changed or a new disk volume is added. If your system has a Diamond Viper or Hercules Graphite video card you will need to change the Primary Video Type in Advanced Configuration to VGA. If your system has a bus mouse it will not be automatically detected. You must set the Mouse Type in Advanced Configuation. To turn off automatic saves, You can press ALT-LEFT_SHIFT- RIGHT_SHIFT. You will hear the pc beep three times indicating Recuperator has been disabled. To reenable, press the same key sequence. The pc will beep twice indicating Recuperator is on. 2. Supports Stacker & DoubleSpace Drives, Large Volumes Optimizer (formerly Compress), DiskFix and Backup now support Stacker and DoubleSpace compressed drives. DiskFix can analyze and repair these volumes, in addition to doing a decompression on DoubleSpace to check for compression errors. Optimizer and DiskFix now support drives up to 2 gigabytes. 3. New Central Point Anti-Virus Technology (CPAV) PC Tools now features the same advanced AV technology that is in CPAV 2.0. A new Virus Analyzer uses an expert system to detect unknown viruses in files and boot sectors without requiring any prior infection information. CPAV also now uses SmartChecks to detect and clean unknown viruses without updated virus signatures. In addition, signature file updates contain more information about file, boot sector, and memory viruses and are now used by BOOTSAFE, CPAV.EXE and VSAFE. CPAV can now scan files compressed by both self-extracting and generic compression programs, including PKZIP, PKLITE, LZEXE and ARJ. Scans are up to 15X faster and TSR memory requirements have been reduced. 4. New Integrated Hardware Diagnostics (SI PRO) System Information Professional provides extensive information and diagnostic testing for your pc such as CPU, video, memory, CMOS, hard and floppy disk tests, sound card, and many others. 5. New High-Speed Floppy Duplicator with Media Conversion FastCopy quickly makes multiple copies of floppy disks. You can also use FastCopy to save an image of a floppy disk on a hard disk, allowing you to quickly create copies of the disk later. Media conversions are also featured, which let you copy disks from one format to another ( provided the destination size disk is smaller than the source ). 6. Task Switcher Improvements Task Switcher now launches scheduled events (formerly handled by CPSCHED) and allows you to specify a program to run during computer idle time. It will also now save high resolution video screens running in VESA mode. 7. DataMon Requires Less RAM DATAMON has been reduced in TSR memory size. The Disk Light feature has been removed from DATAMON and placed into another program, DSKLIGHT.EXE. Undelete now provides delete-protection configuration.
SYMANTEC--PETER NORTON GROUP
README.TXT--March 20, 1992
Copyright 1992 Symantec Corp. All Rights Reserved.
NORTON DESKTOP FOR WINDOWS
Version 2.0
Welcome to Norton Desktop for Windows!
--------------------------------------
Please read this document carefully; it contains important
information not included in the documentation. For easiest
reading, MAXIMIZE this window by clicking the Maximize button.
You may also want to print it for future reference.
Topics covered in this document include:
* Norton Desktop Install and Uninstall
* Norton Desktop Enhancements
* Norton Desktop and Other Products
* Notes and Tips
* Norton Backup for Windows
You will also find a helpful question-and-answer section in
Appendix A of "Using Norton Desktop for Windows." If you still
have questions after reviewing Appendix A and this ReadMe file,
call Technical Support for assistance. In the United States and
Canada, call (310)449-4900. In other areas, contact your local
distributor.
INSTALLING NORTON DESKTOP
=========================
Because the Norton Desktop install program launches Windows
as part of the install procedure, you should not try to install
Norton Desktop from a DOS window. That is, you should not
double-click the Program Manager "DOS Prompt" group item to shell
to DOS. Rather, choose Run from the Program Manager File menu and
type A:INSTALL (assuming the Norton Desktop installation diskette
is in drive A:). Or, exit Windows and at the DOS command-line
prompt, type A:INSTALL.
CREATING A NORTON DESKTOP (2.0) "DESKTOP APPLICATIONS GROUP"
============================================================
If you are installing over version 1.0 of Norton Desktop,
we retain your old Quick Access groups. This means that you
will not see your newly created Norton Desktop Applications
group with the new program items. To convert the Norton Desktop
Applications group from Program Manager, open a drive window and
select the Windows directory. Drag the NORTONDE.GRP file (it
could also be named NORTOND0.GRP, NORTOND1.GRP, etc.) from the
file pane and drop it in the Quick Access group window.
IMMEDIATELY AFTER INSTALLING
============================
Immediately after installing Norton Desktop for Windows, be
sure to run Norton AntiVirus to ensure that your computer is
virus-free. Choose Norton AntiVirus from the Tools menu, then scan all
of the drives to which your computer is connected. Though you've
specified particular drives, Norton AntiVirus will also scan your
computer's memory during the first scan of the session.
UNINSTALLING NORTON DESKTOP
===========================
You can easily uninstall Norton Desktop, removing some or all
of its related files, by launching the Norton Desktop Uninstall group
item in the Norton Desktop Applications group window. If you need
additional information about the uninstall process, start Uninstall
then consult the online help.
Even if you perform a total uninstall, removing all Norton Desktop
files, your Program Manager groups remain intact. Consequently, you
must manually delete the Norton Desktop Applications group from
Program Manager.
Note that you can find information about many of the Norton
Desktop files by reading CONTENTS.TXT in your Norton Desktop directory.
NORTON DESKTOP ENHANCEMENTS
===========================
Norton AntiVirus
----------------
Just as you can choose to hide or show the Sleeper screen saver
and the Scheduler application icons, you can also hide or show the
Norton AntiVirus Popup application icon. (Application icons, remember,
appear at the bottom of your desktop when a running application is
minimized.) The Norton AntiVirus Popup application icon is hidden by
default, but if you want to make it visible when Virus Intercept is
running, follow these steps:
1. Start Norton AntiVirus. (Double-click the Norton AntiVirus tool
icon or choose Norton AntiVirus from the Tools menu.)
2. Choose Intercept... from the Norton AntiVirus Options menu.
3. Check the Hide Popup Icon check box.
4. Click OK.
If you run Windows in Standard mode and have 2M (megabyte) RAM
or less, you should use NAV&.SYS /B as the Norton AntiVirus device
driver for best results.
If you are running Norton AntiVirus with SmartDrive, you should
add the /L switch to your DEVICE=Smartdrv line in your Config.sys file.
If you are running Norton AntiVirus with Stacker, you must
either load the Norton AntiVirus drivers from an unstacked volume or
move the DEVICE=NAV&.SYS /B (or similar) line in your Config.sys file
so that it follows the Stacker command.
Norton Viewer and Graphics Files
--------------------------------
In addition to the bitmap image sizing explained on page 7-8
of "Using Norton Desktop for Windows," you can also manipulate other
graphics files in the same way (including TIF, PCX and WordPerfect
graphics files). Thus, you can copy the current view to the
Clipboard by pressing Ctrl+Insert. To copy a piece of the image
the size of an icon to the Clipboard (starting at the upper-left
corner of the zoom rectangle), press Shift while zooming. Press
Ctrl while zooming to copy the area enclosed by the rectangle to
the Clipboard. You can then paste the contents of the Clipboard
into other applications.
NORTON DESKTOP AND OTHER PRODUCTS
=================================
Installing Other Applications
-----------------------------
When you choose to run Norton Desktop as your shell, you (of
course) choose not to run Program Manager as your shell. However,
there are some Windows applications that expect to find Program
Manager running as your shell. In many cases, though not all, these
programs are hard-coded to look for Program Manager. The applications
listed below most likely will not be able to create Norton Desktop groups
(.QAG files) or group items. Rather, if Program Manager is running, they
may create Program Manager groups (.GRP files) and group items. If you
experience problems installing applications when Norton Desktop is the
shell, the application is most likely looking for Program Manager. Try
running Program Manager by choosing Run from the Norton Desktop File menu.
Once Program Manager is running, try the install again.
Problem with Problem with
Application NDW & Windows 3.0 NDW & Windows 3.1
----------- ----------------- -----------------
Adobe Illustrator No Yes
Aldus PageMaker 4.0 Yes Yes
Central Point PC-Tools 7.1 Yes Yes
Computer Associates DBFast(*) Yes Yes
Corel Draw 2.0.1 Yes Yes
Foresight Drafix-1 Windows CAD Yes Yes
Informix Wingz Yes Yes
Microsoft Productivity Pack(*) Yes Yes
Microsoft Windows SDK Yes N/A
Que RightWriter for Windows Yes Yes
Software Publishing Harvard Draw Yes Yes
WordPerfect for Windows Yes Yes
(*)=Application always expects to find Program Manager on the shell=
line in the System.ini file.
In most cases, you can easily create a Norton Desktop group from
a Program Manager group by dragging the .GRP file from a drive window
file pane and dropping it in a Norton Desktop group window. (Drag it
to the Quick Access group if you want to create a top-level group.)
Refer also to pages A-8 and A-9 ("Using Norton Desktop for Windows")
for additional instructions. For general information about Norton
Desktop groups, refer to Chapter 2 of "Using Norton Desktop for Windows."
NOTES AND TIPS
==============
Calculators
-----------
If you are using a Hercules monochrome display adapter, the
keys on the Tape, Financial, and Scientific calculators may be
difficult to read. If this is the case, refer to the NDWINI.TXT file
for more information.
Documentation Corrections
-------------------------
(Note: Unless otherwise stated, all page references are for
"Using Norton Desktop for Windows.")
Collapse All: Page 3-9 indicates that there are several menu
items you can use to manipulate the tree pane displays in a drive
window. Though not mentioned, you can also collapse the entire tree
structure by choosing Collapse All from the Tree menu.
Fonts: Pages 3-14 and 3-15 explain how to change the font in a
drive window or a Norton Viewer window. However, you cannot save the
font change (there is no Set Default button in the Font dialog box).
Default Editor: Page 9-4 mentions that the Norton Desktop
Install programs asks whether you want to make Desktop Editor your
default text editor. Not mentioned, however, is how to change your
default editor once Norton Desktop is installed. To do so, choose
Default Editor from the Configure menu.
TrueType: In addition to the raster and vector fonts mentioned
on page 11-3, Windows 3.1 also supports a new outline font technology
licensed to Microsoft by Apple Computer: TrueType.
Sleeper default: Page 13-4 indicates that Randomizer is the
default Sleeper screen saver module. In fact, Randomizer is not a
Sleeper screen saver and Screen Shuffle is the default.
Macro Builder: Page 20-4 outlines the steps for recording a
macro with Macro Builder. Rather than specifying the macro filename
before recording (as wrongly indicated in the manual), you can record
the macro before determining its filename. By default, the Recording
Macro dialog box informs you that you are about to start recording a
macro. (This dialog box can be disabled.)
Additional Batch Runner functions: The following functions are
not documented in Chapter 21, "Using Batch Builder."
FileAppend ("from-spec", "[d:path]destination")
Appends one or more files to another file.
Example: FileAppend ("autoexec.bat config.sys", "startup.fil")
NetAttach ("server")
Creates an attachment between a workstation and a Novell NetWare
file server.
Example: NetAttach ("MAINSERVER")
NetDetach ("server")
Detaches a workstation from a Novell NetWare file server.
Example: NetDetach ("MAINSERVER")
Batch Runner SendKey function: In the "Using SendKey" section of
the Batch Builder chapter, {HELP} and {PRTSC} should be removed from
the list of SendKey equivalents. Rather than {HELP}, {F1} works for
those applications that assign help to the F1 key. Instead of {PRTSC},
use the SnapShot function.
Creating Dialog Boxes with Batch Builder: In the "Creating Your
Own Dialog Boxes" section in the Batch Builder chapter:
NOTE says that the maximum template file lines is 15; it should
say 20.
The "Option Buttons" subsection says the first option button in a
group of option buttons is selected by default. Rather, you can
control the default selection the same way you control whether or not
a check box defaults to checked: by setting the option button variable
equal to the desired option button's value on a line above the
DialogBox statement.
Norton Directory Trees: You can use either of two types of
directory trees--Norton trees, which produce the fastest displays,
or Collapsible trees, which can be expanded and collapsed. Rather
than checking a check box as shown on page 22-24 and described on
page 22-25, you can choose the tree type by toggling the Use
Collapsible Tree menu item in the Tree menu. (When it is not checked,
Norton trees are in use.) Refer to online help for more information.
Index Entries: You should add the following entries to the Index
on page I-7:
EDIT..., 9-1
files
editing, 9-1. See also Desktop Editor
NDW.INI
-------
For detailed information about the NDW.INI file, refer to the
NDWINI.TXT file in your Norton Desktop directory.
Sleeper Screen Saver
--------------------
Sleeper recognizes screen savers from After Dark, Intermission,
and Windows 3.1 if you have installed these applications. However,
Sleeper will not recognize the Intermission "Communique" saver module,
even if Intermission is installed.
If you have installed After Dark version 1.0 or 1.0a, each
saver module appears in the Sleeper list box. Simply select the module
you want to run. If you have installed After Dark 2.0, "After Dark
Runner" appears in the Sleeper list box. Select After Dark Runner, then
click Configure to launch After Dark 2.0. Make sure the After Dark
switch is turned ON, then select the saver module you want to use.
Avoid running Windows 3.1 savers with both a Sleeper password and
a Microsoft password. It is recommended to use the Microsoft password
only.
SmartCan and Erase Protect
--------------------------
Norton Desktop Version 2.0 uses an improved memory-resident program
to keep track of deleted files: SmartCan. SmartCan replaces the Erase
Protect program (EP.EXE) from Version 1.0. SmartCan, which is typically
loaded from your AUTOEXEC.BAT file, copies deleted files to a hidden
directory on your disk called SMARTCAN. You can read details about this in
Chapter 14 of "Using Norton Desktop for Windows." However, the SmartCan
TSR cannot access any files saved previously to the TRASHCAN hidden
directory (created by Erase Protect). To recover files from either the
TRASHCAN or the SMARTCAN hidden directory, use UnErase from Fix-It
Disk #1.
VDISK and Norton Desktop
------------------------
Norton Desktop is not compatible with VDisk. You should use
RamDrive instead.
MACRO RECORDER AND INTERNATIONAL KEYBOARDS
==========================================
Macro recorder will record characters generated with the Alt-GR
key on international keyboards incorrectly. If recording these keys,
you must edit the resulting macro file with the Batch Builder and
replace those keystrokes with the correct special key symbols to
generate the proper characters.
NORTON BACKUP FOR WINDOWS
=========================
Compatibility with Norton Backup for DOS (Versions 1.2 and 2.0)
---------------------------------------------------------------
* Using Backup Volumes Created with Norton Backup for DOS
-------------------------------------------------------
If you are a user of Norton Backup for DOS and are currently
in the middle of a FULL/INCREMENTAL or FULL/DIFFERENTIAL backup
cycle, you should not have to interrupt that cycle and start over.
In fact, you should be able to use either product to create your
next backup volume.
Symantec strongly recommends that you test whether you'll be
able to do this by using Norton Backup for Windows to restore some
files that were backed up with Norton Backup 1.2 or 2.0 for DOS. If
you encounter any errors while restoring, there may be some
limitation(s)--either hardware or software--that inhibits
compatibility with older Norton Backup volumes. If this is the
case, you should start the cycle over by making a full backup of
all your drives before resuming your routine.
If you are using Norton Backup version 2.0 for DOS to make backup
sets that you want to read with Norton Backup for Windows, you
should use enhanced ECC if you plan on restoring the backups using
Norton Backup 1.2 for Windows.
* Data Verification
-----------------
If data verification in your setup file was set for "Read
Only" in Norton Backup for DOS, be sure to check your settings in
Norton Backup for Windows when you first load that setup file.
The "Read Only" option does not exist in Norton Backup for Windows
and the setting will default to "Read and Compare." Change this
setting if you prefer one of the other options.
* Macro compatibility
-------------------
If you plan to use setup files that were created with Norton
Backup for DOS, you will need to re-create any macros that were
associated with those setup files.
Floppy Drive Setup
------------------
* Automatic Floppy Configuration
------------------------------
The Install program is able to detect the number and type of
floppy disk drives attached to your system. However, if the
incorrect floppy disk drive types are displayed, you should select
"Auto Floppy Config" from the Configure screen and make sure that
it correctly chooses the proper disk drive types.
If the problem persists, check your computer's CMOS setup to
be sure that your diskette drives are configured properly. This
can be done using your computer's SETUP program. If the drive types
are still not correct, set them manually.
* If Your Compatibility Test Fails
--------------------------------
If your compatibility test failed, there may be a hardware
compatibility problem with your PC or a software conflict. Try these
things to solve the compatibility problem:
1. Click the Configure button.
2. Change the Disk Log Strategy setting to Most Compatible.
3. Change the DMA Operation setting to Most Compatible.
4. Click Floppy Configuration and uncheck Disk Change Detection, then
click OK.
* Using a 360K Diskette in a 1.2M Drive
-------------------------------------
Norton Backup for Windows supports backups to 360K diskettes
in high density (1.2M) floppy drives. Though Symantec does not
recommend this, if you find that you must do this in order to
transfer files to a machine that only has a 360K drive, you
MUST be sure that you do extensive compatibility testing between
both machines. First, if you plan on doing backups to low density
disks in a high density drive, the best method to do this is to
back up using the "DOS Drive and Path" option with the component
size set to 360K. The diskettes should be formatted on a 360K
drive, since the tracks written to a disk in a 360K drive are
different from those written to a 360K disk in a 1.2M drive.
* Floppy Drive Contention
-----------------------
Norton Backup for Windows allows you to switch to other
applications while backing up or restoring data. To ensure that
access to the floppy drives is not interrupted during this
process, Norton Backup hides these drives from all other
applications. Programs that display a list of available drives
will not display drives A: and B: during these background
operations. For the same reason, you should not try to access your
floppy drives directly. For example, typing FORMAT A: in a DOS
window while using Norton Backup to backup to the A: drive will
produce an "invalid drive specification" system message. Normal
use of the drive will return once the backup is finished.
File Selection
--------------
* Manual File Selection
---------------------
When you select a directory in the tree pane, Norton Backup
for Windows stores the selection by directory name. When you
select files in the tree pane, Norton Backup for Windows stores
the selections by filename. Therefore, selecting all the files in
a directory is not the same as selecting that directory. For
example, if you were to select your Norton directory and back it
up, and at a later date add more files to it (such as data files),
then those new files would be included in future backups. On the
other hand, if you were to select all the files in your Norton
directory (as opposed to selecting the directory itself), any new
files added to that directory since the last backup will not be
backed up.
* Setup Files
-----------
If you are planning on using the same setup files for both Norton
Backup for DOS and Norton Backup for Windows 1.2, use include and
exclude statements to describe file selections. If you manually
select files by directory tree or by filename, the file selection
is stored in an .SLT file. The .SLT files are not compatible
between the Windows and the DOS products and the manual file selections
will not be applied.
* Directory Tree File Selection
-----------------------------
You can use the directory tree to quickly select groups of
related directories. When you collapse a branch on the tree and
then select it (the directory displays a plus sign on the folder),
you will be selecting all of the subdirectories under it as well.
Estimated Number of Disks for a Backup
--------------------------------------
The number of disks estimated for backup does not take
compression into account. This is because the amount of data
compression varies for different types of files. Therefore, it is
difficult to accurately estimate the amount of compression that
can be performed during any given backup. Norton Backup for
Windows will make the most conservative estimate in all cases.
Additional Command Line Option
------------------------------
In addition to those command line options listed in the
Norton Backup documentation, the Minimize switch (/m) allows you
to start Norton Backup as a background operation and display it as
an icon. For more information on this and other command line
options, refer to the Norton Backup online Help.
-----End of ReadMe-----
WELCOME TO SYMANTEC'S SPEEDRIVE VERSION 4.0!
Speedrive 4.0 Read Me
Please read this file for important information including:
* Hardware and Software Compatibility
* Troubleshooting
* Tips
To print this file, type the following at your DOS prompt:
TYPE README.DOC >PRN <ENTER>
TIPS
------
CACHE MANAGEMENT SIZE
-----------------------------------------------------------------
By default, Speedrive allocates about 80% of your available XMS
or expanded memory for the DOS cache size and 40% for the
Windows cache. In addition, Speedrive uses a small amount of
conventional or UMB memory to manage the cache. The management
requires more memory as the cache size increases. On systems
with 8 MB or more of RAM, the cache may be quite large and its
management may use more memory than desirable. To reset the
cache size, add appropriate switches to Speedrive's installation
line. Please see the User's Guide or on-line help for further
information.
UPPER MEMORY OPTIMIZATION
-----------------------------------------------------------------
After installing Speedrive, it is important to reoptimize your
upper memory area. Many memory managers provide tools that
perform this task automatically.
If you use: Run:
----------- --------
MS-DOS 6 MEMMAKER
QEMM OPTIMIZE
386MAX MAXIMIZE
USING SPEEDRIVE WITH COMPRESSED DRIVES
-----------------------------------------------------------------
When caching compressed volumes, Speedrive caches only host
(uncompressed) drives. Compressed volumes are actually hidden
files that reside on host drives. By caching the host drive,
Speedrive caches all files on that drive, including the
compressed volume file.
COMMAND LINE CONFIGURATION OF WINDOWS CACHE SIZE
-----------------------------------------------------------------
When configuring cache size from the command line, separate DOS
and Windows cache sizes with a comma. The amount before the
comma is the DOS cache size. The number following the comma is
the Windows cache size. For example, if you want a 4 MB DOS
cache and a 2 MB Windows cache, use the following syntax:
C:\SPEEDRV\SPEEDRV.EXE /INSTALL /EXT=4096,2048
CACHE SIZE FOR CD-ROMS
-----------------------------------------------------------------
SPEEDRIVE greatly improves CD-ROM performance. Below is a
breakdown of cache size and approximate speed gain.
CACHE SIZE % PERFORMANCE INCREASE
---------- ----------------------
<= 1 MB 0%
1 - 3 MB 1,000%
> 3 MB to 4,000%
SPEEDRIVE IN NORTON UTILITIES SYSINFO
-----------------------------------------------------------------
Norton Utilities SYSINFO lists Speedrive as "SMARTDrive (Disk
Cache)" in its "Device Driver" report. Speedrive masquerades as
Smartdrive for compatibility. In addition, SYSINFO calls
Speedrive NCACHE.EXE in the "DOS Memory Block" and "TSR Program"
reports.
TROUBLESHOOTING AND COMPATIBILITY
---------------------------------
LOCKUPS USING QEMM 7.0x or EMM386 from MS-DOS 6
-----------------------------------------------------------------
If you receive Exception 12 or 13 errors from QEMM version 7.0x
or lockups running EMM386.EXE with the HIGHSCAN parameter,
exclude the monochrome video region (B000-B0FF). These managers
aggressively use upper memory block areas and may access
B000-B0FF without claiming it. The system and Speedrive may see
this area as available and attempt simultaneous access. Below
lies an example CONFIG.SYS memory exclusion:
DEVICE=C:\QEMM\QEMM386.SYS RAM NOEMS X=B000-B7FF
PROBLEMS RUNNING ASSIST
-----------------------------------------------------------------
If you receive the ASSIST error, "Assist requires version 4.05
or later," check your AUTOEXEC.BAT file to make sure that
Speedrive installs before any program launches. If the command
to start Windows (WIN), or any other program, lies before
SPEEDRV /INSTALL in AUTOEXEC.BAT, Speedrive can't load until you
exit the program. You can move SPEEDRV /INSTALL by running
SDSETUP and selecting "Move Norton Speedrive installation line
in AUTOEXEC.BAT. Alternately, you can modify AUTOEXEC.BAT using
a text editor.
DISK CHANGE USING ADAPTEC DRIVERS WITH SOME CD-ROM DRIVES
-----------------------------------------------------------------
When running an Adaptec driver with some CD-ROM drives, such as
Hitachi or NEC CD-ROMs, Speedrive does not receive proper disk
change notification. If you change CDs and continue to receive
the first disk's directory after refresh, add the CHANGEFIX
switch to the SDCDEXT driver in CONFIG.SYS. Reboot and your
problem will disappear. For example:
DEVICE =C:\SPEEDRV\SDCDEXT.EXE /D:MSCD001 /CHANGEFIX
MSCDEX 2.21
-----------------------------------------------------------------
Many versions of MSCDEX 2.21 exist and some are incompatible
with Speedrive. It is difficult to determine which version you
have because the file dates, times, and sizes are identical.
However, you can use PKZIP's CRC32 to identify the version by
typing the following:
PKZIP JUNK.ZIP MSCDEX.EXE <ENTER>
PKUNZIP JUNK.ZIP -V <ENTER>
If the screen reads:
MSCDEX.EXE 25431 02-04-92 2:21am CRC32 = EB5CEF4
update the driver.
If the screen reads:
MSCDEX.EXE 25431 02-04-92 2:21am CRC32 = EB7846D3
the driver is fine.
There may be other versions of MSCDEX 2.21 that we have not
tested. If your CRC value is different, consider upgrading to
MS-DOS 6.0x. MS-DOS 6.0x comes with MSCDEX 2.22. This driver
is up to date and functions properly.
EMM386.EXE
-----------------------------------------------------------------
If you use EMM386.EXE as your memory manager, load Speedrive
from the AUTOEXEC.BAT file. EMM386.EXE hampers Speedrive's
ability to load itself into upper memory when loading Speedrive
through the CONFIG.SYS file. If you decide to leave Speedrive
in CONFIG.SYS, use EMM386.EXE's DEVICEHIGH command. For example:
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE NOEMS
DOS=HIGH,UMB
DEVICEHIGH=C:\SPEEDRV\SPEEDRV.EXE /INSTALL
QEMM 6.00 STEALTH MODE
-----------------------------------------------------------------
The Norton Speedrive is completely compatible with QEMM 6.01+
and QEMM 7.0x Stealth Mode. However, QEMM version 6.00's
WINSTLTH.VXD does not allow Speedrive to multitask in Window's
386 Enhanced Mode, which degrades cache performance.
WINSTLTH.VXD from QEMM 6.01 and later resolves the problem.
QEMM 6.00 users should contact Quarterdeck Office Systems and
upgrade to version 6.01 or later.
Alternatively, you can download the new WINSTLTH.VXD driver from
Quarterdeck's BBS. If you only upgrade this driver, use the
NEWSTEALTHVXD switch to inform Speedrive that you have the
correct VXD as follows:
C:\SPEEDRV\SPEEDRV /INSTALL /NEWSTEALTHVXD
QEMM 6.01 and later users do not need to use this switch.
CENTRAL POINT ANTIVIRUS
-----------------------------------------------------------------
If you have an early version of Central Point Antivirus (1.2 or
earlier), upgrade to version 1.3 or later (or use Norton
Antivirus instead). Early versions of Central Point Antivirus
immunize device drivers that load through CONFIG.SYS and damage
them. Such drivers include EMM386.EXE, SETVER.EXE, and
SPEEDRV.EXE. If Central Point Antivirus immunizes Speedrive,
you're computer may hang at boot. In this situation, boot from a
floppy, REM Central Point Antivirus from your startup files, and
reinstall Speedrive.
INTEL SATISFAXTION CARD
-----------------------------------------------------------------
If your system locks up while using Speedrive with Intel's
Satisfaxtion card, disable Speedrive's multitasking feature.
Specify MULTI=OFF on Speedrive's installation line. Note that
Windows performance is not affected by this switch.
ADAPTEC ASPI DRIVERS AND BERNOULLIS
-----------------------------------------------------------------
Adaptec ASPI drivers do not supply drive locking for Bernoullis.
Therefore, Speedrive can't protect you if you eject the disk
while it is writing to the disk. OAD and RCD drivers support
drive locking.
CHINON CD-ROM DRIVERS
-----------------------------------------------------------------
If you use the Chinon CDRVR.SYS CD-ROM driver, you may need to
add the /CDRVRFIX switch to the Speedrive installation line. If
you have more than one CD-ROM driver loaded, the /CDRVRFIX may
adversely affect the non-Chinon driver. Chinon is aware of the
incompatibility. Please call their technical support for
further information.
INVALID CD-ROM PARAMETERS
-----------------------------------------------------------------
If you specify an invalid or unavailable device name in your
SDCDEXT.SYS line, Speedrive does not cache any valid, available
CD-ROM drives.
End of Speedrive README.DOC
SYMANTEC LOCALISATION GROUP IRELAND
README.TXT--
Copyright 1993 Symantec Corp. All Rights Reserved.
NORTON COMMANDER
Version 4.0
Welcome to Norton Commander Version 4.0 !
------------------------------------------
Please read this document carefully, it contains important information not
included in the documentation.
Topics covered in this document include:
* Files that come with Norton Commander 4.0
* Compressing files from the Tree Panel
* Internal Editor & Viewer
* Password protected Compressed files
* Cloning using SHARE.EXE
* Filters
* Viewers
* Special Characters
* Norton Commander Environment Variables
* Limitations in Changing Drives
* Datex.p File
Files that come with Norton Commander 4.0
-----------------------------------------
The following files are shipped on the diskettes for Norton Commander
Version 4.0 :
Diskette 1 : Program Diskette
install.exe Install program
4372ansi.set Conversion table from CP437 to ANSI
8502ansi.set Conversion table from CP850 to ANSI
ansi2437.set Conversion table from ANSI to 437
ansi2850.set Conversion table from ANSI to 850
nc.cfg Configuration file for Filters and Viewers
nc.exe Norton Commander V4.0 Loader
nc.hlp Norton Commander V4.0 Help File
nc.ico Norton Commander V4.0 Icon
ncedit.exe Norton Commander V4.0 Editor
ncmain.exe Norton Commander V4.0 File Manager
nczip.exe Norton Commander V4.0 Compressor
packer.exe Norton Commander V4.0 Compressor Interpreter
packer.set Program file for PACKER.EXE
readme.txt Useful information not included in manual
term90.exe Terminal Emulation Program
term90.hlp Terminal Emulation Help
term90.res Terminal Emulation Resource File
testmdm.scx Script File for Terminal Emulation
cmpsrv.scx Script File for Terminal Emulation
genie.scx Script File for Terminal Emulation
datex.p Telephone number log file
Diskette 2 : Utilities Diskette
nc_arc.exe Compressed file containing Norton Commander
V4.0 Viewers
Compressing files from the Tree Panel
-------------------------------------
A powerful feature was added to Norton Commander Version 4.0 that is not
documented in the User's Guide. This is the ability to select a directory
from the Tree Panel and then compress is using Commander Compression or any
other packer defined in PACKER.SET.
Internal Editor & Viewer
------------------------
There is no internal editor built into NCMAIN.EXE in Commander Version 4.0. The
Commander Editor is now in the file NCEDIT.EXE. However a simple Internal
Viewer is still functional in the NCMAIN.EXE file. Use ALT+F3 to invoke this.
Password protected Compressed files
------------------------------------
As in any password protected file system, if you have protected your
compressed file with a password, you cannot uncompress it without specifying
it correctly. If you forget your password you will not be able to uncompress
the file correctly.
Cloning using SHARE.EXE
------------------------
A problem exists when you are trying to clone to a COM port on a machine that
has SHARE.EXE installed. A conflict exists between the Clone software opening
the device COMX and SHARE granting exclusive rights to this port to the Clone
Bootstrap loader. This results in sharing violation errors occuring during a
cloning session. To get around this problem use the CTTY AUX command
instead of CTTY COM1:.
Filters
-------
The definition of the Filters for Norton Commander Version 4.0 are defined
in the file NC.CFG. The Filters dialog box can be changed by modifying this
file. One good example of using this file is to create a filter for Program
Files. (ie Files with extensions such as CXX, HPP, C and H ). To create a
filter like this simply enter the following data into the NC.CFG file in the
filter section :-
!Program Files
;DevFiles
:*.c??
:*.h??
The text following the ! will appear in the Filter Selection Dialog box. The
text following the ; is the text that will appear in the Title Bar of the panel.
This is displayed when this filter is operational. The file specifications
following the : are the types of files that are to be associated with this
filter. All valid DOS wildcards are allowable.
Viewers
--------
All viewers that are supported by Norton Commander v4.0 are defined in the file
NC.CFG. You can modify this list of files that are associated with viewers. For
example, if your word processor documents have a special file extension such
as .DCC, then you can change the list of files that the wpview.exe file handles
by simply adding this file specification to the list of files that are defined
underneath WPVIEW.EXE.
Special Characters
------------------
To enter special European characters, it is sometimes neccessary to use the
CRTL+Q key first followed by the character you wish to enter. For example, to
enter the German paragraph character, type CRTL+Q followed by SHIFT+3.
Norton Commander Environment Variables
---------------------------------------
Norton Commander searches your environment for the following three
environment variables in order to determine where to locate and store
temporary work files :- TEMP, TMP, NC
Limitations in Compressed Files
-------------------------------
If the current panel contains an open compressed file, then it is not possible
to change the drive of that panel. This compressed file should be closed first
and then the drive selected in the normal manner.
Due to the wide range of different compression utilities on the market today
and the major differences in behaviour, you may find some features of Norton
Commander impossible to implement using your compression utility. This is
especially true of some compression utilities that do not support the
decompressing of files into a destination location other than the current
directory. In addition to this not all compression utilities support the
storing of full pathnames and directories.
Datex.p File
------------
The file DATEX.P contains a list of telephone numbers that can be used
when running the script file CMPSRV.SCX. This file is used by the Terminal
Emulation Program. The format of this file is a follows :-
Position 1 2 3 4 5 6
1 5 5 5 5 5 5
<City Name ><Prefix ><300 ><1200/75 ><1200 ><2400 ><9600 >
The telephone numbers that are stored in this file correspond to the numbers
that are used to connect to the CompuServe Bulletin Board System. The numbers
specified after position 25 are the different numbers to be used depending on
the baud rate that you wish to connect at. You can add in you own telephone
numbers easily by modifying this file using the Commander Editor.
SYMANTEC LOCALISATION GROUP IRELAND
README.TXT--
Copyright 1994 Symantec Corp. All Rights Reserved.
NORTON COMMANDER
Version 4.5
Welcome to Norton Commander Version 4.5 !
------------------------------------------
Please read this document carefully, it contains important information not
included in the documentation.
Topics covered in this document include:
* Files that come with Norton Commander 4.5
* Compressing files from the Tree Panel
* Internal Editor & Viewer
* Password protected Compressed files
* Cloning using SHARE.EXE
* Filters
* Viewers
* Special Characters
* Norton Commander Environment Variables
* Limitations in Changing Drives
* Datex.p File
Files that come with Norton Commander 4.5
-----------------------------------------
The following files are shipped on the diskettes for Norton Commander
Version 4.5 :
Diskette 1 : Program Diskette
install.exe Install program
4372ansi.set Conversion table from CP437 to ANSI
8502ansi.set Conversion table from CP850 to ANSI
ansi2437.set Conversion table from ANSI to 437
ansi2850.set Conversion table from ANSI to 850
nc.cfg Configuration file for Filters and Viewers
nc.exe Norton Commander V4.5 Loader
nc.hlp Norton Commander 4.50 Help File
nc.ico Norton Commander 4.50 Icon
ncedit.exe Norton Commander 4.50 Editor
ncmain.exe Norton Commander 4.50 File Manager
nczip.exe Norton Commander 4.50 Compressor
packer.exe Norton Commander 4.50 Compressor Interpreter
packer.set Program file for PACKER.EXE
readme.txt Useful information not included in manual
term90.exe Terminal Emulation Program
term90.hlp Terminal Emulation Help
term90.res Terminal Emulation Resource File
testmdm.scx Script File for Terminal Emulation
cmpsrv.scx Script File for Terminal Emulation
genie.scx Script File for Terminal Emulation
datex.p Telephone number log file
Diskette 2 : Utilities Diskette
nc_arc.exe Compressed file containing Norton Commander
V4.5 Viewers
Compressing files from the Tree Panel
-------------------------------------
A powerful feature was added to Norton Commander Version 4.5 that is not
documented in the User's Guide. This is the ability to select a directory
from the Tree Panel and then compress is using Commander Compression or any
other packer defined in PACKER.SET.
Internal Editor & Viewer
------------------------
There is no internal editor built into NCMAIN.EXE in Commander Version 4.5. The
Commander Editor is now in the file NCEDIT.EXE. However a simple Internal
Viewer is still functional in the NCMAIN.EXE file. Use ALT+F3 to invoke this.
Password protected Compressed files
------------------------------------
As in any password protected file system, if you have protected your
compressed file with a password, you cannot uncompress it without specifying
it correctly. If you forget your password you will not be able to uncompress
the file correctly.
Cloning using SHARE.EXE
------------------------
A problem exists when you are trying to clone to a COM port on a machine that
has SHARE.EXE installed. A conflict exists between the Clone software opening
the device COMX and SHARE granting exclusive rights to this port to the Clone
Bootstrap loader. This results in sharing violation errors occuring during a
cloning session. To get around this problem use the CTTY AUX command
instead of CTTY COM1:.
Filters
-------
The definition of the Filters for Norton Commander Version 4.5 are defined
in the file NC.CFG. The Filters dialog box can be changed by modifying this
file. One good example of using this file is to create a filter for Program
Files. (ie Files with extensions such as CXX, HPP, C and H ). To create a
filter like this simply enter the following data into the NC.CFG file in the
filter section :-
!Program Files
;DevFiles
:*.c??
:*.h??
The text following the ! will appear in the Filter Selection Dialog box. The
text following the ; is the text that will appear in the Title Bar of the panel.
This is displayed when this filter is operational. The file specifications
following the : are the types of files that are to be associated with this
filter. All valid DOS wildcards are allowable.
Viewers
--------
All viewers that are supported by Norton Commander 4.5 are defined in the file
NC.CFG. You can modify this list of files that are associated with viewers. For
example, if your word processor documents have a special file extension such
as .DCC, then you can change the list of files that the wpview.exe file handles
by simply adding this file specification to the list of files that are defined
underneath WPVIEW.EXE.
Special Characters
------------------
To enter special European characters, it is sometimes neccessary to use the
CRTL+Q key first followed by the character you wish to enter. For example, to
enter the German paragraph character, type CRTL+Q followed by SHIFT+3.
Norton Commander Environment Variables
---------------------------------------
Norton Commander searches your environment for the following three
environment variables in order to determine where to locate and store
temporary work files :- TEMP, TMP, NC
Limitations in Compressed Files
-------------------------------
If the current panel contains an open compressed file, then it is not possible
to change the drive of that panel. This compressed file should be closed first
and then the drive selected in the normal manner.
Due to the wide range of different compression utilities on the market today
and the major differences in behaviour, you may find some features of Norton
Commander impossible to implement using your compression utility. This is
especially true of some compression utilities that do not support the
decompressing of files into a destination location other than the current
directory. In addition to this not all compression utilities support the
storing of full pathnames and directories.
Datex.p File
------------
The file DATEX.P contains a list of telephone numbers that can be used
when running the script file CMPSRV.SCX. This file is used by the Terminal
Emulation Program. The format of this file is a follows :-
Position 1 2 3 4 5 6
1 5 5 5 5 5 5
<City Name ><Prefix ><300 ><1200/75 ><1200 ><2400 ><9600 >
The telephone numbers that are stored in this file correspond to the numbers
that are used to connect to the CompuServe Bulletin Board System. The numbers
specified after position 25 are the different numbers to be used depending on
the baud rate that you wish to connect at. You can add in you own telephone
numbers easily by modifying this file using the Commander Editor.
This file contains information that may be useful to you during the
installation of FastBack Plus Windows.
During installation, another file, called README.TXT, will be copied to
the directory in which you have installed FastBack Plus Windows.
README.TXT contains more comprehensive information about the use of
FastBack Plus Windows. You can use Windows' NOTEPAD program to view
README.TXT.
INSTALLATION TIPS
=================
- This version of Fastback Plus Windows was written to work with
versions 3.0 and 3.1 of Microsoft Windows.
- FastBack Plus Windows' installation program must be run from Windows.
While it can be run from Program Manager or File Manager, the simplest
way to run it is by typing "WIN A:INSTALL" or "WIN B:INSTALL" at the
DOS prompt.
- During installation, you may receive a warning if non-standard drivers
are detected in your Windows SYSTEM.INI file. These drivers are
sometimes installed by other backup programs during installation and,
since they replace the standard Windows drivers, can be detrimental to
other programs' operation. FastBack Plus Windows' installation
program will restore the drivers to Windows' default settings
(device=*VDMAD and device=*VFD). FastBack Plus Windows also adds its
own device driver, called FASTBACK.386 to the [386 Enh] section of
SYSTEM.INI. This device driver, though proprietary, does not
interfere with standard Windows functions. Keep in mind that if you
install another backup program after FastBack Plus Windows has been
installed, it may prevent FastBack Plus Windows from operating
properly.
- Occasionally, some computers have difficulty successfully performing a
restart of Windows while Network drivers are loaded (IPX and NETx) .
If this is occurs with your computer (the computer will hang with a
blank screen after trying to restart Windows), do not be alarmed.
Simply reboot your computer, reinsert FastBack Plus Windows disk #1 in
your floppy drive, and start Windows again. The installation will
continue automatically. In most cases, the installation program will
identify situations where this is likely to occur and provide you with
instructions on manually restarting Windows to continue the
installation.
MACRO/SETUP FILE COMPATIBILITY
==============================
Fastback Plus Windows is compatible with any Setup or Macro file created
for use with Fastback Plus version 3.0x. Commands that are not
applicable within Windows, such as the ColorWindow() command, will
simply be ignored during the processing of macros or setup files if the
MacroErrorAction() is set to "Continue If Possible".
DRIVE SELECTION OVERRIDE
========================
FastBack Plus Windows now relies on information provided by your
computer's BIOS to help in automatically identifying the types of floppy
drives attached to your system.
In the unlikely event the program improperly identifies the floppy drive
type, the following macro command can be added to the FastBack Plus
Windows setup file (usually DEFAULT.FB or USERNAME.FB) to override the
automatic device determination.
Syntax: DefineDrive("Drive Letter",Index,"Drive Type")
Drive Letter - can be any letter in the range A - Z.
Index - is a number from 0 - 3. Normally, the A: drive is index
0, and the B: drive is index 1. Index 3 is usually
reserved for an external floppy drive.
Drive Type - can be any of the following strings:
360K 5 1/4 Floppy
720K 5 1/4 Floppy
720K 3 1/2 Floppy
1.2Mb 5 1/4 Floppy
1.44Mb 3 1/2 Floppy
1.44Mb IBM 3 1/2 Floppy
Example: DefineDrive("A",0,"360K 5 1/4 Floppy")
****NOTE: We have experienced problems with overriding the definitions
of some external floppy drives within the Windows environment. Most
notably, this has been seen with Sysgen external floppy drives. If you
have an unsupported drive, we regret any inconvenience you may
experience as a result, and assure you that we will continue to expand
our support for non-standard, external floppy drives in the future.
Contact our Technical Support group for further details on this matter.
USERS OF HIGH SPEED COMPUTERS WITH ON-BOARD CACHES:
===================================================
On some computers with extremely fast processors and on-board caches,
we have observed an apparent conflict between rapid video updates and
Direct Memory Access (DMA) transfers. This conflict is inherent to the
Microsoft Windows environment and can affect any program that uses DMA
to transfer data on these computers. Since high-speed DMA transfers are
one of the techniques FastBack Plus Windows uses to achieve its superior
performance, the potential exists for this conflict to interfere with
the operation of FastBack Plus Windows.
This conflict results in diskettes being rejected by FastBack Plus
Windows with the error message "Skipping bad or full volume". This
condition exists due to the inability of these faster computers to
allow both the rapid video updates and FastBack Plus Windows' DMA data
transfers to occur before FastBack Plus Windows attempts to begin a new
DMA operation.
We are exploring methods to prevent this condition from interfering with
the operation of our program and expect to have the problem solved in
the near future. In the mean time, if you are running an extremely fast
computer and experience an abnormally high incidence of "Skipping bad or
full volume" conditions, there are a couple of things you can do to
eliminate the problem or reduce the likelihood of its occurrence:
- Disable your hardware cache. These caches increase the frequency of
video updates, thereby making it more likely that they will
interfere with Fastback Plus Windows' DMA transfer operations.
Disabling the hardware cache has been quite effective in eliminating
this problem.
- Avoid doing anything that will significantly increase the amount of
video activity during backups. For example, you should avoid
unnecessary movement of items on the screen during backups and
restores.
If you experience this problem, you can contact our Technical Support
group for the current status of our efforts to solve this problem.
CHANGES MADE DURING FASTBACK PLUS WINDOWS' INSTALLATION
=======================================================
During its installation procedure, if you allow FastBack Plus Windows to
make all of the suggested changes to your system, the following changes
are made:
- AUTOEXEC.BAT file: The directory in which you've installed FastBack
Plus Windows is added to your PATH= statement. The default is C:\FBW.
- WIN.INI file: The FBWSCHED.EXE command (for scheduling automatic
backups) is added to the Load= line in WIN.INI.
- SYSTEM.INI file: The line "device=FastBack.386" is added at the end
of the [386Enh] section of SYSTEM.INI.
- A file called FBW.INI is created in your Windows directory.
- A file called FASTBACK.386 is copied to the SYSTEM subdirectory under
the Windows directory.
All other files are kept in the FastBack Plus Windows directory.
Please note that any files changed during installation will be saved in
backup files with the .FBP extension.
This file contains information that may be useful to you during the
installation of FastBack Plus Windows.
During installation, another file, called README.TXT, will be copied to
the directory in which you have installed FastBack Plus Windows.
README.TXT contains more comprehensive information about the use of
FastBack Plus Windows. You can use Windows' NOTEPAD program to view
README.TXT.
INSTALLATION TIPS
=================
- This version of Fastback Plus Windows was written to work with
versions 3.0 and 3.1 of Microsoft Windows.
- FastBack Plus Windows' installation program must be run from Windows.
While it can be run from Program Manager or File Manager, the simplest
way to run it is by typing "WIN A:INSTALL" or "WIN B:INSTALL" at the
DOS prompt.
- During installation, you may receive a warning if non-standard drivers
are detected in your Windows SYSTEM.INI file. These drivers are
sometimes installed by other backup programs during installation and,
since they replace the standard Windows drivers, can be detrimental to
other programs' operation. FastBack Plus Windows' installation
program will restore the drivers to Windows' default settings
(device=*VDMAD and device=*VFD). FastBack Plus Windows also adds its
own device driver, called FASTBACK.386 to the [386 Enh] section of
SYSTEM.INI. This device driver, though proprietary, does not
interfere with standard Windows functions. Keep in mind that if you
install another backup program after FastBack Plus Windows has been
installed, it may prevent FastBack Plus Windows from operating
properly.
- Occasionally, some computers have difficulty successfully performing a
restart of Windows while Network drivers are loaded (IPX and NETx) .
If this is occurs with your computer (the computer will hang with a
blank screen after trying to restart Windows), do not be alarmed.
Simply reboot your computer, reinsert FastBack Plus Windows disk #1 in
your floppy drive, and start Windows again. The installation will
continue automatically. In most cases, the installation program will
identify situations where this is likely to occur and provide you with
instructions on manually restarting Windows to continue the
installation.
MACRO/SETUP FILE COMPATIBILITY
==============================
Fastback Plus Windows is compatible with any Setup or Macro file created
for use with Fastback Plus version 3.0x. Commands that are not
applicable within Windows, such as the ColorWindow() command, will
simply be ignored during the processing of macros or setup files if the
MacroErrorAction() is set to "Continue If Possible".
DRIVE SELECTION OVERRIDE
========================
FastBack Plus Windows now relies on information provided by your
computer's BIOS to help in automatically identifying the types of floppy
drives attached to your system.
In the unlikely event the program improperly identifies the floppy drive
type, the following macro command can be added to the FastBack Plus
Windows setup file (usually DEFAULT.FB or USERNAME.FB) to override the
automatic device determination.
Syntax: DefineDrive("Drive Letter",Index,"Drive Type")
Drive Letter - can be any letter in the range A - Z.
Index - is a number from 0 - 3. Normally, the A: drive is index
0, and the B: drive is index 1. Index 3 is usually
reserved for an external floppy drive.
Drive Type - can be any of the following strings:
360K 5 1/4 Floppy
720K 5 1/4 Floppy
720K 3 1/2 Floppy
1.2Mb 5 1/4 Floppy
1.44Mb 3 1/2 Floppy
1.44Mb IBM 3 1/2 Floppy
Example: DefineDrive("A",0,"360K 5 1/4 Floppy")
****NOTE: We have experienced problems with overriding the definitions
of some external floppy drives within the Windows environment. Most
notably, this has been seen with Sysgen external floppy drives. If you
have an unsupported drive, we regret any inconvenience you may
experience as a result, and assure you that we will continue to expand
our support for non-standard, external floppy drives in the future.
Contact our Technical Support group for further details on this matter.
USERS OF HIGH SPEED COMPUTERS WITH ON-BOARD CACHES:
===================================================
On some computers with extremely fast processors and on-board caches,
we have observed an apparent conflict between rapid video updates and
Direct Memory Access (DMA) transfers. This conflict is inherent to the
Microsoft Windows environment and can affect any program that uses DMA
to transfer data on these computers. Since high-speed DMA transfers are
one of the techniques FastBack Plus Windows uses to achieve its superior
performance, the potential exists for this conflict to interfere with
the operation of FastBack Plus Windows.
This conflict results in diskettes being rejected by FastBack Plus
Windows with the error message "Skipping bad or full volume". This
condition exists due to the inability of these faster computers to
allow both the rapid video updates and FastBack Plus Windows' DMA data
transfers to occur before FastBack Plus Windows attempts to begin a new
DMA operation.
We are exploring methods to prevent this condition from interfering with
the operation of our program and expect to have the problem solved in
the near future. In the mean time, if you are running an extremely fast
computer and experience an abnormally high incidence of "Skipping bad or
full volume" conditions, there are a couple of things you can do to
eliminate the problem or reduce the likelihood of its occurrence:
- Disable your hardware cache. These caches increase the frequency of
video updates, thereby making it more likely that they will
interfere with Fastback Plus Windows' DMA transfer operations.
Disabling the hardware cache has been quite effective in eliminating
this problem.
- Avoid doing anything that will significantly increase the amount of
video activity during backups. For example, you should avoid
unnecessary movement of items on the screen during backups and
restores.
If you experience this problem, you can contact our Technical Support
group for the current status of our efforts to solve this problem.
CHANGES MADE DURING FASTBACK PLUS WINDOWS' INSTALLATION
=======================================================
During its installation procedure, if you allow FastBack Plus Windows to
make all of the suggested changes to your system, the following changes
are made:
- AUTOEXEC.BAT file: The directory in which you've installed FastBack
Plus Windows is added to your PATH= statement. The default is C:\FBW.
- WIN.INI file: The FBWSCHED.EXE command (for scheduling automatic
backups) is added to the Load= line in WIN.INI.
- SYSTEM.INI file: The line "device=FastBack.386" is added at the end
of the [386Enh] section of SYSTEM.INI.
- A file called FBW.INI is created in your Windows directory.
- A file called FASTBACK.386 is copied to the SYSTEM subdirectory under
the Windows directory.
All other files are kept in the FastBack Plus Windows directory.
Please note that any files changed during installation will be saved in
backup files with the .FBP extension.
N O R T O N B A C K U P 2.0 F O R D O S
This readme file consists of three sections.
1. Recommendations
2. Questions and Answers
3. Hardware
Tape Drives
4. Incompatibilities
5. Limitations
R E C O M M E N D A T I O N S
1. Symantec strongly suggests after you do your first two backups,
you use the Compare function from the main menu, to compare the
contents of the backup diskettes or tape to the source data.
You should also use the Compare function, if you have made a change
to your hardware configuration. This will ensure the integrity of
the backup set. Although we try to test on as many different
computers and software as possible, we cannot test all possible
combinations. This is why it is essential for you to perform at
least two Compares. This confirms that Norton Backup is running
properly on your computer.
2. If you have a computer with 386-33MHz or faster processor, use the
following configuration:
Program Level Advanced
Compression Save Space High
3. Stacker and QEMM users see the software section.
4. If you do have problems, try booting your computer with a DOS
system disk that doesn't have a CONFIG.SYS or AUTOEXEC.BAT file and
see if the problem still occurs.
5. Check the Questions and Answers section of this file for a solution
to the problem.
If you are still having problems call Symantec Technical Support at
(310) 449-4900.
Q U E S T I O N S A N D A N S W E R S
1. Q: Norton Backup appears to lock-up during the backup, but it
passed the Compatibility test.
A: Try setting the compression to off or save space high these are
Advanced Program Level options. This is sometimes an indication
of a software conflict with a memory manager you have installed
on your system.
2. Q: Why do I get the message "Diskette in drive A is defective"?
A: This could be either a software or hardware conflict. On
rare occasions a disk drive will not be able to handle the
Norton Backup's proprietary format. Try the following things:
1. Deselect the Proprietary Format option in the Backup To
menu.
2. Remove all TSRs and optional device drivers from memory
by booting your computer with a DOS system disk that doesn't
have a CONFIG.SYS or AUTOEXEC.BAT file and see if the
problem
still occurs. If these two things don't work--
3. Set Norton Backup to use low speed DMA.
3. Q: What do the messages "Correcting Bad Disk" and "Cannot recover
data from damaged diskette using Error Correction" mean
when attempting to restore or compare a backup set.
A: There may be a software conflict, try removing all TSRs
and optional device drivers.
4. Q: What can I do if I get the messages "Files do not match" or
"Incorrect checksum for file"?
A: Try setting Norton Backup to use low speed DMA. If this
does not resolve the problem, then try removing all TSRs and
optional device drivers.
5. Q: Why doesn't Norton Backup allow me to change any of the
options in the program?
A: You need to press the <spacebar> in order to select any of
the options, such as Program Level, instead of the <ENTER>
key.
This will place a dot in the selection box next to the chosen
option. You can also use the hot keys (highlighted letters)
to select items.
6. Q: Is there an easy way to select/deselect All Files for either
Backup or Restore without going into Select Files and doing it
manually?
A: With the logical drive highlighted in the Backup From/Restore
Files window, press the <spacebar> or click the mouse
(double-clicking with the left button or single-clicking with
the right) to toggle between All Files and no files.
7. Q: I thought I backed up my files to floppy disk, however when
I look at the floppy with DIR, the files that were backed up
do not appear on the screen. Where are they?
A: The files cannot be retrieved through DOS; this can only be
done through the Restore function in the program. When Norton
Backup writes to a floppy, it creates a component file on the
disk. The filename of this file is the same as the catalog
name, with the extension that corresponds to the number of the
floppy in the backup set (e.g. CC10415.001 is the first
diskette created on April 15). The actual files are packed
into the data area of the component file.
To verify that the backup was successful, use the Compare
function from the main menu. You can run a compare immediately
following the backup.
8. Q: Why did Norton Backup require fewer floppy diskettes for a
backup than what the program indicated it was going to need?
A: Norton Backup's estimate of how many disks are required for
backup is a maximum based on the assumption of no data
compression. It would take a long time to estimate accurately
the amount of disk space saved with data compression, because
it depends on the nature of the data being compressed.
9. Q: I told the program to back up drive D, but it keeps backing
up drive C. What's wrong?
A: The DEFAULT.SET file is defined initially to back up all files
on the C drive. You will need to deselect the files for
the C drive by pressing the <spacebar> on the line that says
-C- All Files, in the Backup From box. Think of the Backup
From box as a list of drives to be backed up. In this case,
you will notice that next to the drive letter C it will be
either All Files or Some Files. The highlight bar allows you
to edit the list of your drives and therefore it does not
choose the drive to be backed up.
10. Q: The Backup program doesn't seem to be accepting my Includes
or Excludes. What am I doing wrong?
A: You have selected some of the files/directories from the
Select Files tree with the space bar or mouse. These are
manual file/directory selections and will take priority over
the Include/Exclude list. These directories should be in a
different color than unselected directories (usually red). To
use the Include/Exclude list, you need to tell Norton Backup
that you do not want to manually override the Include/Exclude
list. To do this:
1. Highlighting the red or yellow directory(s) on the
Select Files screen and pressing the <Alt-spacebar> keys.
Once this is done the Include/Exclude list is applied to
all non-red or yellow directories.
2. Make whatever manual selections are necessary (these will
override the Includes/Excludes if there is a conflict).
Or
1. Start all over again by deselecting all the files on the
drive by highlighting the drive letter in the Backup From
list box, by pressing the <spacebar> on the appropriate
drive letter.
11. Q: Why would Norton Backup indicate that a restore is complete
when it did not restore any files (as shown by no check marks
next to the filenames in the top right corner of the Restore
screen) and it only took a few seconds for this entire process
to finish?
A: Norton Backup is probably trying to restore some older files
over some newer files (for example, restoring to fix a
corrupted database).
1. Configure Norton Backup to the Advanced Restore program
level.
2. Choose Options followed by Overwrite Files.
3. Change this option to Always Overwrite
Or
Delete the unwanted files on the hard drive first.
12. Q: Why is there a dot to the left of the filenames in the
Select Files window instead of a checkmark after selecting the
files to be backed up or to be restored?
A: The dot means the file has been deselected. If you are
performing an incremental backup, the dot indicates that you
have tried to select a file that has not changed since the
last Full or Incremental backup. The file may have been
deselected from backup or restore because of a special
selection statement. To change the special selections choose
Select Files followed by Special. You can exclude files by the
attributes, date range, and/or copy protected files list.
13. Q: I'm trying to restore to a different computer and Norton
Backup says there are no catalogs found, or it tells me
that the incorrect disk has been inserted into the drive.
Why would this happen?
A: After performing a backup, a catalog will be created on both
the hard disk where the backup was done as well as on the last
disk of the floppy backup set, or at the end of the tape.
In order to transfer this catalog to the new hard disk:
1. Choose Catalog from the Restore screen.
2. Select Retrieve
Or
Copy this catalog (file with extension .FUL,.INC, .DIF or
.CPY) from the original computer into the Norton Backup
directory on the target computer.
If you have the incorrect catalog loaded:
1. Choose Catalog
2. Highlight the desired catalog and press the <spacebar> to
select it.
3. Choose Load to make it the current catalog.
You could also use the restore without a catalog feature to
restore the data. This is easier and quicker than using a
catalog, when you want to restore a whole backup set.
14. Q: Norton Backup is not using Norton Disk Doctor to scan the disk
before backing up, even though I selected that option.
A: Norton Backup looks for the NU environment variable to find
the Norton Disk Doctor. You will need to add "SET
NU=C:\NORTON" to your AUTOEXEC.BAT file. Replace the
"C:\NORTON" with the correct path name to Norton Utilities on
your hard disk.
H A R D W A R E
T A P E D R I V E S
1. Norton Backup only supports QIC 117 interface Tape Drive and QIC
40 or QIC 80 tape drives.
QIC 02 or other interface tape drives are not supported. Most high
speed/compression adapters are not currently supported.
2. Supported Tape drives are listed below:
Archive 5240 (XT only), 5540, 5580, 3580 (PS/2):
Some 5240s have hardware incompatibilities. Norton Backup
only supports tape drives that come with serial numbers
starting with BB or above. Serial numbers starting with AA
or AB are not supported.
Core Light QIC 80:
Some versions of the OEM software may not be compatible with
Norton Backup. You should therefore verify that backups
made with the OEM software can be restored with Norton
Backup, in the event you may need to restore old backups
that were not made with Norton Backup.
Colorado DJ-10 or DJ-20:
Also known as the "JUMBO 120" (40Mb) or "JUMBO 250" (80Mb)
The FC-10 Speed Card is not currently supported.
CMS Enhancement T2120/AT:
The T2120/PS2 is not QIC117 compatible at this time.
For T2120 (AT), you must change dip switch 5 at the back of
the tape drive from OFF to ON.
Irwin 40sx and 80sx:
Archive is the OEM. These drives are identical to the
Archive 5540 and Archive 5580.
Mountain 4000, 8000, 4740(PS/2):
This drive can be installed as a B-drive or you can use a
"third connector" cable.
Tallgrass FS120 & FS300:
Mountain is the OEM for the FS300. The FS300 drive is
identical to the Mountain 8000. Early Tallgrass FS120's were
produced by Mountain. They were Mountain 4440s. These drives
have a circuit board that extends past the chassis 1.5".
Recent FS120's are produced by Archive. They are referred
to by Tallgrass as Irwin Hornet drives, which are really
Archive 5540s. The circuit board on these drives are exactly
the same length as the chassis.
Tecmar QIC 40:
Wangtek is the OEM for the Tecmar QT40i
Wangtek QIC 3040F5 & 3080F5:
These tape drives are frequently setup incorrectly for Norton
Backup; the jumpers are factory set as B drive. If the tape
drive is to be configured as the third device, you must change
the jumper at the back of the tape drive.
Wangtek documentation refers to a unique setting for using
Wangtek drives (3080F5) as a third device on Compaq machines
which will not work with Norton Backup. Use the phantom drive
setting instead.
I N C O M P A T I B I L I T I E S
Accutrak
Including IBM PS/2 internal tape drives
DC6000
Archive, Wangtek, Cipher, Tanberg, Sankyo Seiki
Everex describes the 60F tape drive as QIC 40 compatible, however
it is only QIC40 formatted and not QIC 117 interface compatible.
Tapes can be interchanged between Everex Software and Norton
Backup.
The Northgate has an incompatible IDE hard/floppy disk drive
controller. Only some systems are shipped with a League IDE
controller card (IDE H/F disk drive). Norton Backup cannot run
with this IDE disk drive controller.
The Zenith Supersport has a DMA bus conflict condition with Norton
Backup. Norton Backup is not certified to run on this platform.
S O F T W A R E
In order to have Norton Backup run with best performance, a minimum
of 512K of RAM is recommended.
Erase Protect or File Save (Norton Utilities)
All of the files marked for deletion are placed in a hidden
directory called TRASHCAN. If you would like Norton Backup
not to backup these files then just deselect this one
directory (manually or with exclude statements)
PC-MOS is not supported.
Desqview
Desqview needs to assign 640KB for installation.
The advanced settings should be as follows:
close on exit N/A use own color YES
allow close window command NO run background NO
use math coprocessor NO keyboard conflict 0
share CPU NO share EGA foreground zoom NO
can be swapped out NO protection level 0
** other settings not mentioned are N/A.
See notes in the scheduler section concerning Desqview.
Running in different operating systems will force Norton Backup to
reconfigure.
QEMM
You may get a message from QEMM to "set DMA=xx" where xx is a
number. Just follow QEMM's instructions for adding this to the QEMM
device line in the CONFIG.SYS. QEMM needs this line to handle
Norton Backups use of the DMA channels.
Windows
Norton Backup must be running Full screen and be the only
application running. See the note about Windows in the Scheduler
section.
Stacker
Back up the Stacker drive instead of the STACVOL.xxx file (usually
found in the root directory). If you backup just the STACVOL.xxx
file then you will NOT be able to restore a particular file from
your Stacker drive. You will be forced to restore the whole drive.
If you lose or damage one disk containing this huge file then you
will lose all the data that was on your Stacker drive.
View
Norton Backup View does not support graphic files.
NSCHED.COM
This TSR should be the last TSR loaded. In most cases it will
detect if a TSR is loaded afterwards and will disable itself.
The TSR program "NSCHED.COM" always loads itself in high memory.
If there is no high memory or insufficient high memory. NSCHED.COM
loads itself in low memory. Using QEMM to load NSCHED.COM to high
memory will produce an error message "cannot load high".
BACKUP
If the Norton Backup directory is selected for backup, not all of
the files in the directory are backed up. Some dynamic files are
exempt from backup process; such as *.sav, *.bak, *.slt,
nbackup.log, restore.tmp, backup.tmp and compare.tmp. These files
do not need to be backed up, because they are temporary files that
change during the backup and restore processes.
The file system:
NB_____.__$ This is a temporary file that Norton Backup swaps in
and out of memory. This file can be deleted if it
exists in the directory.
nbackup.log: This is an internal picture of the logged drive.
*.set files saves program setting in ASCII
*.sav files when a .set file is changed, the old file is renamed
from .set to .sav.
*.slt files save current file selections
*.cat files used by backup engine; saves chksum, count of files,
count of directories.
nbackup.tmp link between interface and backup engine in ASCII.
dibmerg.tmp used by merging process; should be removed upon
merge completion.
fibmerg.tmp used by merging process; should be removed upon
merge completion.
nbackup.rst list of files to be restored out of catalog.
ecc_file.tmp used while Norton Backup is doing ecc corrections.
cat_file.tmp used while Norton Backup is doing ecc corrections.
Norton Backup sets the DMA speed to low if the compatibility test
is cancelled. Skipping the compatibility test will leave DMA
speed set to HIGH.
Setup Files, Tape Tools and Macros
Macros are only supported in the backup portion of Norton Backup.
Macros are not supported for the pull down menus.
Do not use a macro to load a setup file or for file selection,
the results are unpredictable.
DOS Path
A Backup made from a floppy disk drive through DOS path, can only
be restored through DOS path.
Scheduler
The Scheduler cannot schedule an event on the last day of the
month because there are 28 day, 29 day, 30 day, and 31 day
months. If you want to schedule regular monthly backups, schedule
them for the 1st day of the month. The following programs have
been found to disable the scheduler: Paradox 3.5, Borland C++ 2.0,
WordPerfect Office, and DOS PRINT. When running Windows or
Desqview the scheduler will wait until you exit that environment
before making a backup.
Norton Antivirus
Norton Backup does not backup "NAV_.SYS" and "NAV&.SYS". Norton
Antivirus is protecting these files and must be disabled to allow
backing up of these files.
Solution #1:
Add NAV_.SYS and NAV&.SYS to the Copy Protected Files list found
in the Special box in the Select Files screen.
This will tell Norton Backup not to attempt to backup these
files. In the event you need to restore NAV_.SYS or NAV&.SYS you
can do so from the original Norton AntiVirus disks. The benefits
from this solution are that unattended backups are possible,
Norton AntiVirus is active, and you do not need to remember to
disable Norton AntiVirus.
Solution #2:
To temporarily disable Norton AntiVirus, reboot the computer, press
and hold down the two SHIFT keys after you hear the first beep from
the computer. A message should display stating that Norton
AntiVirus has not been loaded. You may now release the keys and
make your backup. Remember to reboot again to reactivate Norton
AntiVirus. The benefit of this solution is that you have a backup
that contains all of the Norton AntiVirus files that were selected
for backup.
The NAV.SYS contained in versions of Norton AntiVirus prior to
2.0 are not compatible with NSCHED. If NSHED interrupts the
warning dialog box of Norton AntiVirus 1.5 or earlier, you will
need to reboot.
Q I C I N T E R C H A N G E
Norton Backup is able to restore backup tapes made with the
following OEM tape software:
Archive (QSXL), CMS Enhancements (Rescue), Corelite (Core),
Colorado (Tape), Irwin (Central Point 6.0), Mountain (Filesave),
Tallgrass (Filesecure), Tecmar (QT), Wangtek (Central Point 7.0),
and Central Point 7.1 (using the QIC format and no password)
The following OEM tape software was tested and will restore
Norton Backup tapes:
Colorado (Tape), Mountain (Filesave), Tallgrass (Filesecure), and
Central Point 7.1
The following OEM tape software was tested and will not restore
Norton Backup tapes:
Archive (QSXL), Corelight (Core), Irwin (Central Point 6.0),
Tecmar (QT), and Wangtek (Central Point 7.0)
LIMITATIONS:
Ideally, Norton Backup can log drives having 2040 directories and
65000 files but the maximum number of directories and files
depend on the system memory available for drive logging. If
Norton Backup does not have sufficient memory for drive logging,
end users need to use DOS "SUBST" or NETWORK "MAP" to partition
the drive they want to backup. Norton Backup will allocate 64KB
for logging 2040 directories. If there is insufficient memory,
Norton Backup will allocate 32KB for 1020 directories.
Each tape volume table can hold 256 entries. This means that
Norton Backup can save 256 backup sets to a single tape, if the
save catalog to tape option is turned off. If you turn on the
save catalog to tape option, then the maximum number of backups
to a single tape is 128.
SYMANTEC--PETER NORTON GROUP
Readme for Norton Backup Version 3.0 for Windows
September 15, 1993
Welcome to The Norton Backup for Windows!
=========================================
This document contains important information not included
in the user documentation. For easiest reading, maximize this
window by clicking the Maximize button (Alt+Spacebar, X). You
may also want to print it for future reference. This file
contains the following sections:
1. New Technical Support Address and Phone Number
2. Installing with Norton Desktop for Windows
3. Installing DOS 6.0 After Norton Backup for Windows
4. Install Disk Space Estimates
5. Conserving Disk Space During Installation
6. Norton Emergency Restore
7. Compatibility with Norton Backup for DOS (Ver. 1.2 & 2.2)
7.1 Setup Files
7.2 Data Verification
7.3 Macro Compatibility
8. Configuring SCSI Devices
8.1 Resolving Configuration Problems
8.2 Hanging When Searching for Devices
8.3 Multiple SCSI Adapters
8.4 PS/2 Model 30/Mountain Mach II Card
9. Networks/NetWare Bindery
9.1 Maximum Path Size Supported
9.2 Restoring NetWare Bindery
9.3 Trustee Information
10. Network Tape Sharing
10.1 Share Retries
10.2 Windows Standard Mode
11. Floppy Drives and DOS Path
11.1 Using a 360Kb Diskette in a 1.2Mb Drive
11.2 Floppy Drive Contention
11.3 Data Verification vs. Compare Function
11.4 Compare Function
12. SCSI/QIC-02 Tape Devices
12.1 Supported SCSI Tape Devices and Adapters
12.2 Supported QIC-02 Tape Devices and Adapters
12.3 Adaptec WINASPI and DOSASPI Drivers
12.4 SCSI Wangtek 6130/Adaptec 1520 or 1542C Card
12.5 SCSI Security Erase
12.6 Incompatible Tape Cartridges
12.7 Low Capacity DC6000 Tape Cartridges (250 Mb or Less)
12.8 SCSI - Tapes Used With Other Backup Software
12.9 SCSI Chain Termination
12.10 Manual Add - SCSI
12.11 QIC-02 Maynard Controllers and Drives
12.12 Hardware Compression
12.13 SCSI Device Troubleshooting
13. QIC-40/80 and IDE Tape Drives
13.1 Supported QIC-40/80 Tape Drives
13.2 Supported QIC-40/80 High-Speed Controllers
13.3 Supported IDE Tape Drive and Adapter
13.4 Colorado TC-15 Hardware Compression
13.5 Troubleshooting High-Speed Controllers
13.6 Video/DMA Conflict Problems
13.7 Hard Drive Cable Support - IDE
14. AccuTrak Tape Drives
14.1 Supported AccuTrak Tape Drives
15. InfoServer
16. Windows Standard Mode
16.1 Using DOS Boxes
16.2 NDW 2.0
17. System Font
17.1 Sharing Violation
18. Correctable Errors
18.1 How Many Correctable Errors are Acceptable?
19. Compressed Drives
20. Hardware/Software Incompatibilities
20.1 Notebook Power Management Feature
20.2 Alloy Retriever 40/60/60e, and 250cs
20.3 COREtape Light QIC-80
20.4 Iomega AccuTrak Read Mode
20.5 Maynard ArchiveXL 5240 (XT only), 5540,
5540e, 5580, 5580e, and 3580 (PS/2)
21. Limitations
21.1 Special Characters in Passwords
21.2 Logging Drives
1. NEW TECHNICAL SUPPORT ADDRESS AND PHONE NUMBER
=================================================
If you still have questions after reading this file, call
Technical Support for assistance. Symantec's new technical
support address is:
Symantec Corp.
175 W. Broadway
Eugene, OR 97401
In the United States and Canada, call:
Technical Support: 503-465-8450
Symantec BBS: 503-484-6669 (9600B)
503-484-6699 (2400B)
Fax Support: 503-334-7470
To call from other areas, please refer to the Customer
Service Plan in the Norton Backup for Windows user guide.
2. INSTALLING WITH NORTON DESKTOP FOR WINDOWS
=============================================
If you have the Norton Desktop for Windows Scheduler installed,
Norton Backup for Windows will not create a Scheduler icon.
The Scheduler icon can be found in the Norton Desktop
Applications group instead of the Norton Backup group.
3. INSTALLING DOS 6.0 AFTER NORTON BACKUP FOR WINDOWS
=====================================================
DOS 6.0 installs an older version of the VFINTD.386 into the
DOS directory and then modifies the SYSTEM.INI
(DEVICE=C:\DOS\VFINTD.386). If you install MS-DOS 6.0 after
Norton Backup 3.0, the next time you launch Norton Backup you
will be sent a warning dialog. This dialog notifies you that
the VFINTD.386 is the incorrect version. If you click Ok in
this dialog Norton Backup will save the existing SYSTEM.INI as
SYSTEM.NBW and make the necessary change to the "Device=" line
in the SYSTEM.INI. You can also make the changes manually by
performing the following steps:
1. Open the SYSTEM.INI file using a text editor.
2. Search for the VFINTD line (DEVICE=C:\DOS\VFINTD.386).
3. Change the line to: DEVICE = [Nbwin install path]\VFINTD.386.
4. INSTALL DISK SPACE ESTIMATES
===============================
To insure that the user always has enough disk space to
install Norton Backup, the Install program displays the
maximum amount of space that may be required for installation.
This estimate is affected by the actual options selected
for install and also includes some space that is necessary
in order to run the install program.
5. CONSERVING DISK SPACE DURING INSTALLATION
============================================
To conserve disk space, Norton Backup for Windows 3.0 offers
the Custom install option. This option allows for installing
just the options that are needed thereby saving valuable disk
space. For example, Norton Backup supports several types of
tape drives, but if you will only be using a QIC-40/80 drive
there is no reason to install all of the other tape drivers
on your hard disk. Norton Backup allows you the option to
install all or some of the following:
tape drive support
Network Tape Sharing
help files
Norton Scheduler
Norton Viewers
6. NORTON EMERGENCY RESTORE
===========================
The following tape drives and configurations are NOT supported
by Norton Emergency Restore:
-IBM PS/2 model 40 used with the Archive 5240 tape
drive as a B: drive
-Colorado AB-10 adapter card used with a Colorado
Jumbo 120 or DJ-10 tape drive that has a firmware
version of 39 or earlier
-SCSI and QIC-02 tape drives
-IDE tape drives
-Irwin AccuTrak tape drive series
7. COMPATIBILITY WITH NORTON BACKUP FOR DOS (VER. 1.2 & 2.2)
============================================================
If you are a user of Norton Backup for DOS and are currently
in the middle of a FULL/INCREMENTAL or FULL/DIFFERENTIAL
backup cycle, you should not have to interrupt that cycle and
start over. In fact, you should be able to use either product
to create your next backup volume.
Symantec strongly recommends however, that you confirm you'll
be able to do this by first using Norton Backup for Windows to
restore some files that were backed up with Norton Backup 1.2,
2.0, or 2.2 for DOS. If you encounter any errors while restoring,
there may be some limitation(s) --either hardware or
software--that inhibits compatibility with older Norton Backup
volumes. If this is the case, you should start the cycle
over by making a full backup of all your drives before resuming
your routine.
7.1 Setup Files
---------------
If you are planning on using the same Setup files for both
Norton Backup for DOS and Norton Backup for Windows, use
include and exclude statements to describe file selections.
Manual file selections made in the Windows product cannot be
read by the DOS product.
7.2 Data Verification
---------------------
If data verification in your setup file was set to "Read Only"
in Norton Backup for DOS (Ver. 1.0 and 1.2), be sure to check
your settings in Norton Backup for Windows when you first load
that setup file. The "Read Only" option does not exist in
Norton Backup for Windows and the setting will default to
"Read and Compare" or "Compare After Backup." Change this
setting if you prefer a different option.
7.3 Macro Compatibility
-----------------------
If you plan to use setup files that were created with Norton
Backup for DOS, you will need to re-create any macros that were
associated with those setup files.
8. CONFIGURING SCSI DEVICES
===========================
8.1 Resolving Configuration Problems
------------------------------------
If you are having trouble configuring your SCSI drive, try
the following:
1. Make sure that the drive supports the tape being used.
2. Make sure the chain is properly terminated (if using
only one device, it must be terminated).
3. Make sure the terminators are not plugged in backwards.
4. If an external device is the last device in the chain,
make sure that it is powered on (in order for the
terminators to be effective).
5. Try turning off sync negotiation.
6. Try turning off parity.
7. Try turning off disconnect.
8. Make sure 1-3 devices (including the adapter) are supplying
termination power.
9. Remove all but 1 device from the chain.
10. Minimize cable length (1 foot).
11. Remove disk cache programs.
12. Verify that each SCSI device on the chain is set to a
unique SCSI ID.
8.2 Hanging When Searching for Devices
--------------------------------------
If your system hangs while searching for SCSI devices, it
may be due to an address conflict with the SCSI host
adapter or a SCSI ID conflict. Verify the addresses or SCSI
ID's being used and try again.
8.3 Multiple SCSI Adapters
--------------------------
If you are using a Future Domain driver and also have
a path to WINASPI.DLL, strange characters may be
displayed on the screen when using Norton Backup for Windows.
To solve this you can either temporarily rename or delete
the WINASPI.DLL file.
8.4 PS/2 Model 30/Mountain Mach II Card
---------------------------------------
Using the default address settings on the Mountain Mach II
card in a PS/2 Model 30 will cause the system to lock up.
The default DMA setting on the high-speed controller and
the hard drive are both 3. Change the DMA setting on the
card before configuring with Norton Backup.
9. NETWORKS/NETWARE BINDERY
===========================
9.1 Maximum Path Size Supported
-------------------------------
Currently, Norton Backup does not support paths that are
greater than 63 characters.
9.2 Restoring NetWare Bindery
-----------------------------
After restoring netware bindery to a server, it is a good
idea to run BINDFIX from the server. Use the BINDFIX
command at the SYS:SYSTEM prompt to update the bindery with
any user changes that may have occurred since the backup.
For more information, refer to the Novell NetWare Utilities
Reference manual.
9.3 Trustee Information
-----------------------
Trustee information cannot be restored if you select a Restore
To option other than Original Location.
10. NETWORK TAPE SHARING
========================
The minimum requirements to run Share are: IPX 3.10 or
IPXODI 1.2. It is recommended that you use IPXODI. If you
experience network connection losses or timeout errors during
a share session, verify that the versions of IPX and Net Shell
are correct.
10.1 Share Retries
------------------
For networks with heavy traffic, the "Share Retries" setting
can be added to the NDW.INI file. This will allow you to
adjust the number of times Norton Backup will attempt to share
a device. By default, Norton Backup will attempt to share the
device every half a second, 220 times. This setting can be
adjusted according to your network's traffic.
To add this setting to the NDW.INI file:
1. Open the NDW.INI file using a text editor.
2. Search for the [NBACKUP] section.
3. Add the following line to the end of the
[NBACKUP] section:
share retries = x (where x represents the desired value).
10.2 Windows Standard Mode
--------------------------
Currently, when running in Windows Standard mode there may
be problems allocating enough memory to use the Share
feature. Attempting to share can cause the "Unable to create
DMA buffers" message and Norton Backup will quit on machines
with 2 to 4 Mb of installed memory.
11. FLOPPY DRIVES AND DOS PATH
==============================
11.1 Using a 360Kb Diskette in a 1.2Mb Drive
--------------------------------------------
Performing backups to 360Kb diskettes in a 1.2Mb floppy
drive is not recommended, and will almost surely result in
lost data when attempting to restore. However, Norton Backup
for Windows does support backups to 360Kb diskettes in 1.2Mb
floppy drives in order to allow file transfer between older
and newer computers. The best method to do this is to format
the diskettes in the 360Kb drive, then back up using the
"DOS Path" option in the Backup To combo box, and the 360Kb
component size setting in the backup options (General category).
Even when this procedure is used, these diskettes should not be
relied upon as the sole backup of a hard disk.
11.2 Floppy Drive Contention
----------------------------
Norton Backup for Windows allows you to switch to other
applications while backing up or restoring data. To insure
that access to the floppy drives or tape drive is not
interrupted during this process, Norton Backup hides these
drives from all other applications. Programs that display a
list of available drives may not display drives A: and B:
during these background operations. For the same reason, you
should not try to access your floppy drives directly. For
example, typing FORMAT A: in a DOS window while using Norton
Backup to back up to a floppy drive will produce an
"invalid drive specification" or "drive not ready" system
message. Normal use of the drive will return once the backup
is finished.
Note that this is also true when using a QIC 40/80 or
AccuTrak tape drive that is connected to the floppy
controller as a B: drive. When using high-speed controllers
or adapters with a QIC-40/80, AccuTrak, IDE, or QIC-02
drive, you will be prevented from using the floppy drives
only if the controller card is using DMA 2 or IRQ 6
(sharing the same addresses as the Floppy diskettes).
When using SCSI tape drives, floppy drive access is
not restricted.
11.3 Data Verification vs. Compare Function
-------------------------------------------
To safeguard your data you should take the time to check
that the data written to your diskettes matches the data
on your hard disk. You can do this through Data Verification
while the backup is in progress, or by using the Compare
function after the backup is completed.
Data verification during a floppy or DOS Path backup verifies
the reliability of the media more than the data itself. For
this reason, it is safest to also perform a Compare after
the backup (using the Compare function) which will verify that
the compressed form of the original data was not corrupted
when transferred into memory.
11.4 Compare Function
---------------------
Compare is a separate function designed to provide maximum
data security. The data in the backup set is compared to the
source data on the hard disk using the following procedure:
1. Reads the data on your backup medium exactly as if it were
going to restore the data to the hard disk.
2. Compares this data to the data found on the hard disk.
3. Verifies that the files are identical and displays a
message if they do not match.
12. SCSI / QIC-02 TAPE DEVICES
==============================
12.1 Supported SCSI Tape Devices and Adapters
---------------------------------------------
This section lists the SCSI tape devices that are supported
by Norton Backup.
MANUFACTURER MODEL NAME **ADAPTERS
------------------------------------------------------------------
Archive Corp. Viper 2150S 1-9
ArDAT, Inc. Python 4322, 4352XT 1-4, 7, 9
ArDAT, Inc. Turbo Python 4324, 4354XT 1-4
Cipher Data Products Mako 2.6GB, T826, C826 1-4
Cipher Data Products Mako 6.0GB, T860, C860 1-4
Cipher Data Products MiniLibrary 18GB, L7A-18 1-4
Cipher Data Products MiniLibrary 42GB, L7A-42 1-4
Exabyte Corp. EXB-4200C 1-4
Exabyte Corp. EXB-8200 1-5
Exabyte Corp. EXB-8500 1-6
Exabyte Corp. EXB-8500C 1-6
Exabyte Corp. EXB-8505 1-4
Hewlett-Packard 35470A, JetStore 2000 1-4
Hewlett-Packard 35480A, JetStore 5000 1-4
IBM 4 GB-4mm DAT Drive 1-4
Qualstar TS/1000 1-6
Tandberg Data TDC 4100, Panther 1000 1-6
Tandberg Data TDC 4220 1-9
Tecmar DATaVault 4000 1-5
WangDAT 1300XL 1-4, 7-9
WangDAT 3100 1-4
WangDAT 3200 1-5
Wangtek, Inc. 51000 1-6
Wangtek, Inc. 5150ES, SS 1-6
Wangtek, Inc. 5525 1-9
Wangtek, Inc. 6200 2, 3
**Supported SCSI Adapters:
(1) Adaptec 1520 (6) Future Domain 7000ex
(2) Adaptec 1640 (7) UtraStor 34F
(3) Adaptec 1742A (8) UtraStor 14F
(4) Adaptec 1542C (9) UtraStor 14N
(5) Future Domain MCS 700
12.2 Supported QIC-02 Tape Devices and Adapters
-----------------------------------------------
This section lists the QIC-02 tape devices that are supported
by Norton Backup.
MANUFACTURER MODEL NAME ADAPTER
--------------------------------------------------------------
Archive Corp. 100e Archive QIC-02 Adapter
Archive Corp. 250e Archive QIC-02 Adapter
Archive Corp. Viper 2060L, VP-60 Archive QIC-02 Adapter
Archive Corp. Viper 2150L, VP-150 Archive QIC-02 Adapter
Tecmar QT250, ProLine 250Q Wangtek QIC-02 Adapter
Wangtek, Inc. 5150PK, MK, EQ Wangtek QIC-02 Adapter
12.3 Adaptec WINASPI and DOSASPI Drivers
----------------------------------------
The SCSI drivers, Adaptec's WINASPI and DOSASPI, are not
automatically installed. You can install them using the
supplemental or custom install feature. The benefits of
using WINASPI are the ability to run multiple DOS boxes
and increased performance.
12.4 SCSI Wangtek 6130/Adaptec 1520 or 1542C card
-------------------------------------------------
The Wangtek 6130 tape drive and an Adaptec 1520 or 1542C
card are not supported configurations.
12.5 SCSI Security Erase
------------------------
Security Erase on some SCSI tape drives may take as long as
6 hours.
12.6 Incompatible Tape Cartridges
---------------------------------
Using tapes that are incompatible with the drive can cause
your system to "hang." Reboot your system and verify that
you are using a tape cartridge that is compatible with your
drive.
12.7 Low Capacity DC6000 Tape Cartridges (250 Mb or less)
---------------------------------------------------------
At this time, backups made with low capacity DC6000 tape
cartridges (250 Mb or less) can only be restored with Norton
Backup. If you plan on restoring a backup set made by Norton
Backup with another vendor's software, use high
capacity tapes (320 Mb or greater) to make the backup.
12.8 SCSI - Tapes Used With Other Backup Software
-------------------------------------------------
Tapes that have been used with other backup software
may cause unexpected behavior when used in Norton Backup.
Initializing these tapes with Norton Backup will solve
the problem.
To Initialize a tape:
1. Insert the tape in the SCSI device.
2. Select Initialize from the Tape Tools menu.
Note: If you experience this problem during the compatibility
test, initialize the tape and rerun the test.
12.9 SCSI Chain Termination
---------------------------
If you experience unusual problems during tape operations,
insure that the SCSI chain is properly terminated.
Please refer to your SCSI device installation manual
for more details.
12.10 Manual Add - SCSI
----------------------
You cannot manually add a SCSI or InfoServer device in
Norton Backup. The Manual Add feature, when used for
SCSI and InfoServer, is for troubleshooting purposes
only. However, this feature will display the number of
SCSI and InfoServer drives and/or errors detected.
12.11 QIC-02 Maynard Controllers and Drives
-------------------------------------------
At this time, Norton Backup does not support Maynard
controller cards or drives.
12.12 Hardware Compression
--------------------------
If your SCSI tape drive has hardware compression and Norton
Backup does not detect it, insure that the hardware compression
switch on the tape drive itself is on.
Hardware compression can be turned on and off from the Hardware
Compression checkbox in the Settings dialog (Configure window).
To change the compression setting:
1. Click the Configure button.
2. Select the desired SCSI device.
3. Select the Settings command... button.
4. Set the Hardware Compression checkbox to the
desired setting.
Note: When hardware compression is turned on, software
compression alternatives will not available in the Backup
General options window.
12.13 SCSI Device Troubleshooting
---------------------------------
If your SCSI device light begins to flashes or if Norton
Backup starts to hang during tape operations, it's possible
that the device needs to be cleaned. Please refer to
the users manual for information on the device's flash
codes and cleaning recommendations.
13. QIC-40/80 and IDE TAPE DEVICES
==================================
13.1 Supported QIC-40/80 Tape Drives
------------------------------------
This section lists the QIC 40/80 tape drives that are
supported by Norton Backup.
MANUFACTURER MODEL NAME
---------------------------------------------------------------------
Aiwa TD-803
Aiwa TD-811
Alloy Computer Products Retriever 250
Archive Corporation 5240
Archive Corporation 5580, 3580
Archive Corporation SuperHornet 51250/31250/11250
CMS Enhancements CMS-40
Colorado Memory Systems Jumbo 120
Colorado Memory Systems Jumbo 250
Compaq Computer Corp. 80/120
CORE International COREtape Light
Iomega Tape250 Insider, Insider HH, PC Powered
Irwin SX Series 40Mb and 80Mb
Mountain Network Solutions FileSafe 4000
Mountain Network Solutions FileSafe 8000 Plus, Mountain 80
Summit Memory Systems, Inc. SE250
Tallgrass Technologies FS120
Tecmar MiniVault 120
Wangtek, Inc. 3040
Wangtek, Inc. 3080
Note: Everex describes the 60F tape drive as QIC-40 compatible.
The tapes formatted by this machine are QIC-40 compatible
however, the tape drive is not QIC-117 interface compatible.
13.2 QIC-40/80 High-Speed Controllers
--------------------------------------
The following high-speed controller cards are supported by
Norton Backup:
Colorado FC-10
Colorado TC-15
Colorado TC-15MC
Iomega
Summit
Tecmar
Wangtek
Irwin 4100
Irwin 4100MC
Mountain MACH II
Mountain MACH II MC
13.3 Supported IDE Tape Drive and Adapter
-----------------------------------------
This section lists the IDE tape drive and adapter that
is supported by Norton Backup.
MANUFACTURER MODEL NAME ADAPTER
--------------------------------------------------------------
Summit Memory Systems, Inc. SE305 Summit Adapter
NOTE: Norton Backup may not be able to read or write to tapes
written to by the old Summit SE305 drive until they are formatted
by Norton Backup. The older Summit SE305 drive can be distinguished
by the orange logo on the face plate and the model number.
Old Summit Drives - FAB 03-33163-01 Rev. B
New Summit Drives - FAB 03-33205-01 Rev. B
13.4 Colorado TC-15 Hardware Compression
----------------------------------------
Hardware compression can be turned on and off from the
Compression drop-down list box in the Settings dialog
(Configure window). To change the compression setting:
1. Click the Configure button.
2. Select the QIC-80 device.
3. Select the Settings command... button.
4. Select the desired setting in the Compression
drop-down list box.
Note: When hardware compression is turned on, software
compression alternatives will not available in the Backup
General options window.
13.5 Troubleshooting High-Speed Controllers
-------------------------------------------
To properly set up your system, you should avoid using an
interrupt request (IRQ) that is used by another device
(i.e., mouse, sound card, network card, scanner, etc.).
Some common IRQs that may already be used in your
system include:
IRQ 3 COM 2-4 ports
IRQ 4 COM 1 port
Symptoms of an IRQ conflict include Norton Backup not
finding the tape controller and network problems when
backing up to tape.
13.6 Video/DMA Conflict Problems
--------------------------------
Norton Backup uses direct memory access (DMA) channels to
read and write data. Sometimes using a tape device that is
connected to the floppy controller causes conflicts with
the Windows 3.1 video drivers.
During the compatibility test, Norton Backup determines if
your system has a video/DMA conflict and if so, goes through
a series of tests in an effort to ensure your system runs
reliably with Norton Backup. After each test a message will
inform you that tests are still being performed. If Norton
Backup has attempted every test and your system will still not
work reliably, a message will inform you of the problem.
NOTE: If you experience video/DMA conflicts, try disabling the
Video Caching option (sometimes referred to as Video Shadowing)
in your CMOS setup.
13.7 Hard Drive Cable Support - IDE
-----------------------------------
Operating an IDE drive on the same cable as the hard drive is
supported in Windows Standard mode only.
14. ACCUTRAK TAPE DRIVES
========================
14.1 Supported AccuTrak Tape Drives
-----------------------------------
This section lists the AccuTrak tape drives that are supported
by Norton Backup. AccuTrak drives require pre-formatted tapes.
MANUFACTURER MODEL NAME
-------------------------------------------------
Irwin Magnetic Systems A120, 2040
Irwin Magnetic Systems A250, 2080
Irwin Magnetic Systems A250xxST, 2120
15. INFOSERVER
===============
Backups created on InfoServer tapes are only readable on
InfoServer tape drives. InfoServer tape drives cannot read
a backup made by a drive not connected to an InfoServer.
16. WINDOWS STANDARD MODE
=========================
16.1 Using DOS Boxes
--------------------
Shelling out to DOS under Windows Standard mode is not
supported when using Share, a SCSI, IDE, or InfoServer
tape device.
16.2 NDW 2.0
------------
If you are running Norton Desktop for Windows 2.0 in Standard
mode, you may experience memory errors when trying to launch
Norton Backup. Loading the Program Manager as the shell should
resolve the problem.
17. SYSTEM FONT
================
17.1 Sharing Violation
----------------------
If you have SHARE.EXE loaded, you may receive a sharing
violation on the file "Arial.ttf" during backups. Because
the file is being used by the system, it is open at the time
Norton Backup is trying to back it up. Skip this file and
continue with the backup.
18. CORRECTABLE ERRORS
======================
If you are getting excessive correctable errors during
compare or restore, check the following:
1. Make sure that the drive is grounded.
2. Make sure that the drive is clean.
3. Make sure that your "Buffers=" statement in your
config.sys is set to 30 or greater.
4. After you've retrieved the data from the tape,
use Tape Tools Format or [SCSI/QIC-02] Tape Tools
Erase. OR, use a newer tape.
Norton Backup recommends that the "Buffers=" statement be set
to 30 or greater even if using a disk caching program. A low
buffer statement may lead to excessive correctable errors and
thus directly affect the performance of your backup or restore.
Note: If the number of errors corrected is more than the errors
found, make sure that the Burst Mode setting is off. To change
the Burst Mode setting:
1. Click the Configure button.
2. Select the QIC-80 or AccuTrak device.
3. Select the Settings... command button.
4. If active, click the Burst Mode checkbox to
turn the option off.
18.1 How Many Correctable Errors are Acceptable?
------------------------------------------------
It is acceptable to have up to 50 correctable errors on a full
tape. If you have tried all the steps in section 18 above, but
are still exceeding 50 errors, contact technical support.
19. COMPRESSED DRIVES
=====================
If you are using compression software such as Stacker or
DoubleSpace, do not back up the compressed file (for example,
stacvol.* or the dblspace files), back up the logical drive
instead. Because these compressed files are typically very
large, attempting to restore may cause problems if you do not
have enough disk space to restore the compressed file.
20. HARDWARE/SOFTWARE INCOMPATIBILITIES
=======================================
20.1 Notebook Power Management Feature
--------------------------------------
Running some notebook computers with the power management
option on may cause problems when using Norton Backup. To
avoid power loss during backup operations, disable the power
management option:
Zenith - Set the Floppy Disk Drive Power Management option
to "Full Auto."
Gateway - Run SETPOWER /LO.
Texas Instruments - Run SETPOWER /LO.
If you experience problems with another brand of
notebook computer, see the users guide for information
on disabling the power management option.
20.2 Alloy Retriever 40/60/60e, and 250cs
-----------------------------------------
Some problems exist between older firmware and Norton Backup.
20.3 COREtape Light QIC 80
--------------------------
Some Core International software versions may not be compatible
with Norton Backup. Verify that you can restore backups made
with Core International software using Norton Backup. You may
want to keep the Core International software on your computer
in case you need to restore old backups made with that software.
20.4 Iomega AccuTrak Read Mode
------------------------------
Norton Backup does not support reading AccuTrak tapes in
the Iomega 250 QIC 40/80 tape drive at this time.
20.5 Maynard ArchiveXL 5240 (XT only), 5540, 5540e, 5580,
5580e, and 3580 (PS/2)
----------------------------------------------------------
Some 5240 drives have hardware incompatibilities.
Norton Backup only supports tape drives with serial numbers
starting with BB or above. Serial numbers starting with AA
or AB are not supported.
21. LIMITATIONS
===============
21.1 Special Characters in Passwords
------------------------------------
You can use characters typed directly from the keyboard for
passwords. If doing floppy, DOS Path, QIC 40-80, AccuTrak,
or IDE backups, do NOT enter characters in your password by
holding the Alt key and typing a three-digit number on the
numeric keypad. If you use these special characters in a
password, you must use the Emergency DOS Restore Disk or
Norton Backup for DOS to restore your backup set.
21.2 Logging Drives
-------------------
If you receive a message that Norton Backup for Windows
cannot log a drive because it contains too many directories,
you can work around this problem as described below.
If the drive is a local drive (as opposed to a network drive,
use the DOS SUBST command to map the directory you want to
back up to a new drive letter. For example, to substitute
the drive letter F: for the directory E:\SOFTWARE\DOS, type:
SUBST F: E:\SOFTWARE\DOS
If the large drive is a Novell NetWare file server, use the MAP
command with the ROOT option to map a drive letter to a
sub directory on the volume. For example, to map the drive
letter G: to a network directory called SERVERA\VOLUME1\PATHNAME,
type:
MAP ROOT G:=SERVERA\VOLUME1:\PATHNAME
If you experience problems using the MAP ROOT command, see
your Novell documentation. If you receive a message that
Norton Backup for Windows cannot log a drive because it
contains too many files in a single directory, the only
work around is to reduce the number of files by moving
them to another directory if possible.
-----End of Readme-----
READ ME FIRST
The programs and information contained on this media are
Copyright (c) 1993 Ziff-Davis Publishing Company, a division
of Ziff Communications Company ("Ziff"). All Rights Reserved.
BEFORE INSTALLING, USING OR REPRODUCING THE CONTENTS OF THIS MEDIA, YOU
MUST AGREE TO THE TERMS AND CONDITIONS OF THE ZIFF LICENSE AGREEMENTS,
WHICH CAN BE FOUND IN THE TEXT FILE LICSCRN.TXT (SEE LICENSING PROCEDURE
BELOW). BY INSTALLING, USING OR REPRODUCING THE CONTENTS OF THIS MEDIA,
YOU ARE AGREEING TO THE TERMS AND CONDITIONS OF THE LICENSE AGREEMENTS.
If you do not agree to the terms and conditions of the Ziff License
Agreements, please destroy or return the media to the Ziff-Davis Benchmark
Operation, One Copley Parkway, Suite 510, Morrisville, NC 27560.
PC Bench and DOSMark are trademarks of Ziff Communications Company.
System Requirements
To run all tests:
MSDOS(tm) Version 3 or higher
500KB free memory
40MB free disk space
Less than 40MB disk space is acceptable, but prohibits calculation of
the DOSMark(tm) score. Installation is accomplished in two stages,
file transfer and licensing. The first stage is performed via an
installation program that copies and decompresses the files to your
system hard disk. The files are stored on the diskette in compressed
form, and the installation program expands the compressed files to a
DOS-compatible format. The second stage of the installation procedure
requires you to run the licensing program. The licensing procedure
requires your consent to the terms and conditions, and you must enter
your name and organization at the licensing prompts. To run the
Install program:
1. Insert the disk in the drive. Make it the current drive by typing the
drive letter followed by a colon, then press the ENTER key. Type INSTALL
and press the ENTER key to activate the installation program. For example:
A:
INSTALL
Three menu choices are provided. Readme (R), Installation (I), Exit (X).
The letter in parentheses indicates the letter you may type to select the
menu choice. If your mouse is working, two mouse clicks on the menu item
will also select and activate the choice. Select -Installation-.
You are prompted for the Source Drive, the Destination Drive and the
Destination Path.
The installation process will create a new directory on your hard disk
drive according to the information provided for the destination path. It
will expand the contents of the diskette onto your hard disk drive into
standard DOS format.
NOTE: If a file is accidentally deleted, you may run the install program
again. If a file previously exists it will ask if you want to overwrite
the file. You may choose the letter -Y- for Yes or -N- for No. Data file
templates are included in the self-extracting file. Therefore, overwrite
them only if you desire to erase the data that you may have previously
created. The Database files have the suffix *.DBF and *.MDX.
2. Run the BENCH licensing utility. Example:
BENCH /L
The terms and conditions are presented on the screen. You are required to
provide your Name and Organization under the terms of the Licensing
Agreement. Follow the directions on the display. Bench is now installed.
3. At this point you should print or type the help file:
TYPE HELPME or
MORE < HELPME or
PRINT HELPME
WARNING: Additional information crucial to running the benchmark program
is contained in the help file called HELPME (This file is not available
until file installation is completed). Follow the instructions contained
therein.
======================================================
PRODUCT SUPPORT
You may FAX your questions to the Ziff-Davis Benchmark Operation at
(919) 380-2879. Or, send mail to:
Ziff-Davis Benchmark Operation
One Copley Parkway, Suite 510
Morrisville, NC 27560.
READ ME FIRST
The programs and information contained on this media are Copyright (c) 1993
Ziff-Davis Publishing Company, a division of Ziff Communications Company
("Ziff"). All Rights Reserved.
BEFORE INSTALLING, USING OR REPRODUCING THE CONTENTS OF THIS MEDIA, YOU MUST
AGREE TO THE TERMS AND CONDITIONS OF THE ZIFF LICENSE AGREEMENTS, WHICH CAN
BE FOUND BELOW. BY INSTALLING, USING OR REPRODUCING THE CONTENTS OF THIS
MEDIA, YOU ARE AGREEING TO THE TERMS AND CONDITIONS OF THE LICENSE
AGREEMENTS.
If you do not agree to the terms and conditions of the Ziff License
Agreements, please destroy or return the media to the Ziff-Davis Benchmark
Operation, One Copley Parkway, Suite 510, Morrisville, NC 27560.
WinBench and WinMark are trademarks of Ziff Communications Company.
WINBENCH(tm) SOFTWARE LICENSE AGREEMENT
READ THIS AGREEMENT carefully before using this software. By using this
software you agree to be bound by the terms of this Agreement. If you do not
agree to the terms of this Agreement, promptly return this software (or, if
downloaded, do not use this software) and any accompanying items (including
documentation and container) to the Ziff-Davis Benchmark Operation at the
address below.
The WinBench(tm) software and its related documentation (collectively, the
Software") encoded on this physical media (or available through an on-line
access service) is copyrighted, and all rights are reserved by Ziff-Davis
Publishing Company, a division of Ziff Communications Company ("ZIFF").
Limited License.
ZIFF grants you the non-transferable right to use the Software on a single
dedicated computer or a file server networked with multiple PCs solely for
internal use and evaluation purposes. You may also publish the test results
obtained by you from use of the Software, provided with each such result you:
A. Identify PC Magazine Labs, the name and version number of the
benchmark Software used (i.e., PC Magazine Labs' WinBench(tm) Ver. 3.11).
B. Identify the exact name, processor speed and type, amount of RAM,
amount of secondary RAM cache, if any, hard disk size, type of hard disk
controller, and size of hardware hard disk cache, if any, of the PC used
for the test (e.g., WXY Corp. Model 466 with 66-MHz Intel 486DX2-66 CPU,
8MB of RAM, 64KB RAM cache, 200MB hard disk, IDE controller, and no
hardware disk cache).
C. Identify the exact video adapter name, amount and type of RAM on it,
video driver name and date, and monitor refresh rate that produced the
result (e.g., XYZ Corp. XYZVideo adapter with 2MB VRAM, XYZ.DRV Version
1.1 driver dated 11 Feb 1993, and a monitor refresh rate of 72 Hz).
D. Identify the operating system version (e.g., MS-DOS 5.0), size and
type of software disk cache, if any (e.g., SMARTDRV 2MB cache), video
resolution and color depth (e.g., 800 by 600 pixels with 256 colors),
and any other special conditions used to achieve the result (e.g., disk
compression utility ABC Version 1.0 enabled).
E. State that all products used in the test were shipping versions
available to the general public.
F. State that the test was performed without independent
verification by ZIFF.
G. Follow proper trademark usage and acknowledge ZIFF's trademark
rights (e.g., "[ ] achieved a 4.5 million Graphics WinMark(tm) test
score. WinBench(tm) and WinMark(tm) are trademarks of Ziff Communications
Company").
In addition, you may either (a) make one copy of the Software solely for
backup or archival purposes, or (b) transfer a copy of the Software across a
network to PCs attached to that network. This license and your right to use
the Software automatically terminate if you fail to comply with any provision
of this Agreement. Upon such termination, you agree to destroy all copies of
the Software in your possession or under your control.
Restrictions.
I. You may not rent, lease, sell, sublicense, assign or otherwise transfer
the Software or this license.
II. You may not reverse engineer, decompile, disassemble, merge, modify,
include in other software or translate the Software, or use the Software for
any commercial purposes, except for the publication of test results, as
provided above.
III. You may not remove or obscure ZIFF's copyright and trademark notices.
Limited Warranty and Limited Liability.
THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE RESULTS AND
PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU, AND ZIFF ASSUMES NO
RESPONSIBILITY FOR THE ACCURACY OR APPLICATION OF OR ERRORS OR OMISSIONS IN
THE SOFTWARE. IN NO EVENT SHALL ZIFF BE LIABLE FOR DIRECT, INDIRECT, SPECIAL,
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE
THE SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
SPECIFICALLY, ZIFF IS NOT RESPONSIBLE FOR ANY COSTS INCLUDING, BUT NOT LIMITED
TO THOSE INCURRED AS A RESULT OF LOST PROFITS OR REVENUE, LOSS OF USE OF THE
SOFTWARE, LOSS OF DATA OR EQUIPMENT, THE COSTS OF RECOVERING SOFTWARE, DATA OR
EQUIPMENT, THE COST OF SUBSTITUTE SOFTWARE OR DATA, CLAIMS BY THIRD PARTIES,
OR FOR OTHER SIMILAR COSTS. ZIFF WARRANTS THE ORIGINAL PHYSICAL MEDIA
DISTRIBUTED BY ZIFF TO BE FREE OF DEFECTS IN MATERIALS AND WORKMANSHIP.
ZIFF'S ENTIRE LIABILITY AND THE USER'S EXCLUSIVE REMEDY SHALL BE REPLACEMENT
OF THE DEFECTIVE ORIGINAL PHYSICAL MEDIA. THE WARRANTIES AND REMEDIES SET
FORTH HEREIN ARE EXCLUSIVE AND IN LIEU OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS
OR IMPLIED. NO ZIFF AGENT OR EMPLOYEE, OR THIRD PARTY, IS AUTHORIZED TO MAKE
ANY MODIFICATION OR ADDITION TO THIS WARRANTY. SOME STATES DO NOT ALLOW
EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES OR LIMITATION OF LIABILITY FOR
INCIDENTAL OR CONSEQUENTIAL DAMAGES; SO THE ABOVE LIMITATIONS OR EXCLUSIONS
MAY NOT APPLY TO YOU.
U.S. Government Restricted Rights.
The Software is provided with RESTRICTED RIGHTS. Use, duplication or
disclosure by the Government is subject to restrictions as set forth in
subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software
Clause at DFARS 48 CFR 252.277-7013 for DoD contracts and 52.227-19(a) -(d)
for civilian agency contracts. Contractor/manufacturer is the Ziff-Davis
Benchmark Operation, One Copley Parkway, Suite 510, Morrisville, North
Carolina 27560.
General.
ZIFF retains all rights not expressly granted. Nothing in this license
constitutes a waiver of ZIFF's rights under the U.S Copyright Act or any other
Federal, state or foreign law. You are responsible for installation,
management, and operation of the Software. This Agreement, including the
limited warranty and limited liability, shall be construed, interpreted and
governed under New York law.
INTRODUCTION
WinBench
Version 3.11
Release date: February 1993
WinBench(tm) is the PC Magazine Windows Benchmark suite. It provides
comprehensive graphics benchmark tests using the Windows Graphical Device
Interface (GDI) and selected high-level user interface functions. Version 3.1,
the fourth major release of WinBench, added tests of hard disk subsystems.
Version 3.11 is a maintenance release.
WHAT YOU NEED TO RUN WINBENCH
To run WinBench, you need to have the following hardware and software.
WinBench requires:
. A PC that runs Windows 3.0 or 3.1
. A graphics adapter and Windows driver capable of a resolution of at
least 640x480 pixels. Correct operation and accurate results from
running WinBench are not guaranteed if the tested graphics resolution
is less than either 640 pixels wide or 480 pixels high.
. About 300,000 bytes available on your hard disk for the WinBench
software itself
. About 9 million bytes of available space on your hard disk for a
temporary file to run the WinBench disk tests, and to save the results
of any WinBench tests that you run. If your hard disk does not have
enough space for the work file, WinBench will not run the hard disk
tests.
. MS-DOS Release 3.1 or later (Release 5.0 recommended)
. Microsoft Windows 3.0 or later (Release 3.1 or later recommended),
running in either Standard or Enhanced mode.
BACKGROUND
WinBench 3.11 and the Graphics WINMARK reflect how the leading Windows
applications use the Windows environment. We used Microsoft Test to capture
repeatable scripts that represent typical use of eight Windows applications
which are market leaders in their respective product categories. Then, we ran
the scripts on standard configurations using Microsoft's Logger and Profiler
tools to record information about the Windows functions used by these
applications. Finally, we analyzed the log and profile data to construct a
composite picture of the most frequently used GDI functions and the
characteristics of these functions.
Ziff-Davis Publishing Company is committed to provide the PC industry with
high quality state-of-the-art benchmark software. The Ziff-Davis Benchmark
Operation carries out the on-going mission to develop benchmarks by
instrumenting and analyzing how major Windows applications use the Windows
environment, using the best profiling and instrumentation tools available.
Subsequent releases of WinBench may reflect adjustments in both the functions
used and their weights, depending on the results of the analysis.
INSTALLING WINBENCH
WinBench is distributed as a pair of files: this README file and a
self-extracting executable file, WINB311.EXE. The self-extracting file
contains WINBENCH.EXE, the benchmark program itself, and WINBENCH.HLP,
the on-line help for WinBench.
You will probably want to create a directory that contains the WinBench files,
and that will contain all of the report files generated by WinBench. For
example, you could use the following DOS commands to create the WINBENCH
directory on your C: drive, and to change to that directory:
MD C:\WINBENCH
CD C:\WINBENCH
Then, execute the self-extracting WINB31 program to install all of the
files from the WinBench diskette. If the WinBench diskette is in the
A: drive of your PC, and you created the WINBENCH directory as
shown above, do the following command:
A:WINB311
Finally, copy this file to the same directory:
COPY A:README
HOW TO USE WINBENCH
You launch WinBench just like any other Windows application:
1. After installing WinBench as shown above, you may execute the DOS
command:
WIN WINBENCH
2. You may open up the file manager, go to the WinBench directory on your C:
drive, and double-click on WINBENCH.EXE.
For other instructions, see the on-line help for WinBench.
PRODUCT SUPPORT
You may FAX your questions to the Ziff-Davis Benchmark Operation at
(919) 380-2879. Or, send mail to:
Ziff-Davis Benchmark Operation
One Copley Parkway, Suite 510
Morrisville, NC 27560.
┌──────────────────┐
│ │
│ README.1ST │
│ │
└──────────────────┘
INSTALLATION AND RELEASE NOTES
QAPLUS/WIN
5.0
(c) 1989 - 1992 DiagSoft, Inc.
All Rights Reserved.
The following files are contained on the QAPlus/WIN distribution disks:
DISK 1
*************************************************************
README 1ST - This file
SETUP EXE - Initialization program to install all files
INSTALL EX$ - Install program, compressed
INSTALL INI - Install script variables
INSTALL INS - Compiled install script
INSTALL DOC - Installation message file
QALOGO BMP - DiagSoft, Inc. logo bitmap for install program
QAPLUSW EX$ - QAPlus/WIN executable file, compressed
QAPLUSW HL$ - QAPlus/WIN help file, compressed
QAMATCH EX$ - QAPlus/WIN Match executable file, compressed
QAMATCH HL$ - QAPlus/WIN Match help file, compressed
M4DLL DL$ - QAPlus/WIN DLL file, compressed
QAWRCC EX$ - QAPlus/WIN Windows Control Center executable
file, compressed
QAPERF EX$ - QAPlus/WIN Disk Performance Tester executable
file, compressed
QAPERF HL$ - QAPlus/WIN Disk Performance Tester help
file, compressed
WIN0INI HL$ - QAPlus/WIN file, compressed
WIN0INI2 HL$ - QAPlus/WIN file, compressed
SYS0INI HL$ - QAPlus/WIN file, compressed
SYS0INI2 HL$ - QAPlus/WIN file, compressed
SYS0INI3 HL$ - QAPlus/WIN file, compressed
DISK 2
*************************************
WINTEXT WR$ - QAPlus/WIN User Guide additions in
Windows Write format, compressed
QABROWSE EX$ - QAPlus/WIN file, compressed
QAREPORT EX$ - QAPlus/Report file, compressed
QAREPORT WR$ - QAPlus/Report User Guide in
Windows Write format, compressed
QAREPORT CF$ - QAPlus/Report configuration file, compressed
BITFAX EX$ - BitFax program file, compressed
BITFAX INI - BitFax profile file
BITFAX HL$ - BitFax help file, compressed
QATEST BFX - Test FAX file
BFBMT4 DL$ - BitFax DLL file, compressed
BFCOMM DL$ - BitFax DLL file, compressed
BFCONF DL$ - BitFax DLL file, compressed
BFDIAL DL$ - BitFax DLL file, compressed
BFFILE DL$ - BitFax DLL file, compressed
BFJOBS DL$ - BitFax DLL file, compressed
BFPHBK DL$ - BitFax DLL file, compressed
BFPROF DL$ - BitFax DLL file, compressed
BFRECV DL$ - BitFax DLL file, compressed
BFSEND DL$ - BitFax DLL file, compressed
BFTR29 DL$ - BitFax DLL file, compressed
INSTALLATION NOTES:
To install the software:
1. Insert disk 1 into drive A.
2. Start Windows and choose Run from the File menu of the Program
Manager.
3. Type A:SETUP and click the OK button or press ENTER.
4. Respond to the prompts during the installation process.
Please review the file, INSTALL.DOC, on this disk for more information
about the installation process.
RELEASE NOTES:
Changes to the program were made after the printing deadline for the
User Guide. Please refer to the enclosed Addenda sheet for a summary of
those changes.
Two Windows Write files are enclosed which further document
the QAPlus/Report program, the Windows Control Center utility
(including QAMatch), and the Disk Performance Tester utility. You may
print or view these using the Windows Write program included with your
Microsoft Windows system.
Additionally, you may refer to the Help in the QAPlus/WIN program for
current information about all of the functions and commands of the program.
Best regards from DiagSoft, Inc.
▐██▓ . ▐██▓ . ▐██▓ ▓██▌ .
▀▀▀ ██▓▌ ▀▀ ██▓▌ ▀▀ ▐█▓█ ▀▀ ██▓▌ ▐▓██ ▀▀▀
.▐█▓█ █ ▐█▓█ . █▓█▌ .▐█▓█ █▓█▌ .
. █▓█▌ ·█ █▓█▌ ▐▓█▓ · █▓█▌▄▄▄▐█▓█
▐▓██ ▐▓██ ▓█▓▌ . ▐▓██ . ██▓▌ .
·▓██▌ . ▓██▌ · █▓▌ ▓██▌. ▐██▓
▐▓█ $*BR*$
The Nokturnal ▐█ Check-It Pro V1.04
Trading Alliance █ from Touchstone
PRESENTS : ▐ Disk (1 of 2)
■
README.TXT
Release notes for Microsoft Test, Version 2.0
(C) Copyright Microsoft Corporation, 1993
This document contains release notes for version 2.0 of
Microsoft Test. The information in this document and in the
online Help is more up-to-date than that in the books.
========
CONTENTS
========
Part Description
---- -----------
1 Documentation Errata and Additions
a Microsoft Test User's Guide
b Microsoft Test User Interface Editor User's Guide
2 New Dynamic-Link Library Procedures
New TESTCTRL.DLL Procedures
New TESTDLGS.DLL Procedures
New TEST TALK Procedures
New TESTUIL.DLL Procedures
3 Enhanced Functionality
Test Dialogs
User Interface Editor
Detecting a Disk in Drive A: or B:
RUN Statement/Function
NOT (!) Operator
Test Trap Additions, Corrections, and Changes
4 Miscellaneous
Using MS-DOS Boxes on the Novell Network
Test Talk Issues
Callbacks as Parameters
===========================================
PART 1: Documentation Errata and Additions
a: Microsoft Test User's Guide
===========================================
TESTDLGS.EXE and TESTSCRN.EXE Filenames
---------------------------------------
Please note the following changes:
TESTDLGS.EXE was renamed to TESTDLG.EXE
TESTSCRN.EXE was renamed to TESTSCN.EXE
These filenames were changed so that the .EXE files did not have
the same name as the dynamic link libraries (DLLs) TESTDLGS and
TESTSCRN. When the names were the same, you couldn't run the
.EXE if the DLL was already loaded. This situation occurred when
you ran a script that called a DLL, stopped it at a breakpoint,
and then tried to run the .EXE.
Page 58, Compiling Your Script
------------------------------
Before the sentence located at the end of the second paragraph
in this section that says:
You can run your pcode file by using WBRUN20.EXE
and passing it the pcode filename.
Insert the following paragraphs:
To run a pcode file, the following files must
be present:
The .PCD file
WBRUN20.EXE
WBEXEC20.DLL
RBHEAP.DLL
DLLs that you call from your script
(TESTCTRL, TESTEVNT, etc.)
Under Windows 3.0, the DLLs must be in either the current
directory, the WINDOWS or WINDOWS\SYSTEM directory, or a
directory in your path. Under Windows 3.1, the DLLs can be
in any of the above directories, and can also be in the
directory where WBRUN20.EXE is located.
Page 86, Saving a Reference Image to a File
-------------------------------------------
Add the following note after step 4 in the "To save an image
to a file" procedure:
NOTE: Screen files cannot contain images that were
captured using different video modes. If you captured
and saved screen images in a file using one video mode,
and try to capture and save a new screen image to the
same file using a different video mode, an "Invalid
Screen Mode" error occurs. See Appendix B for a list
of video modes.
Page 105, STRING *, Fixed-Length
--------------------------------
Add the following paragraphs:
The maximum size of a fixed-length string is 32767
bytes. If this size is exceeded, an 'Invalid Size for
Fixed-Length String' error occurs during compilation.
DIM S AS STRING * 32767 'this is valid
DIM Y AS STRING * 32768 'this fails with an error
NOTE: this limitation does not apply to variable-length
strings.
Page 111, User-Defined Data Types
---------------------------------
Add the following paragraph and examples after the TYPE LOGRECORD
example on this page:
The maximum size of a user-defined variable is 32,767 bytes.
If this size is exceeded, an "overflow" error occurs during
compilation. In the following examples Type1 is defined having
the maximum size. Type2 produces an "overflow" error.
TYPE Type1
x as string * 32767 'The maximum size
END TYPE
'This will produce an "overflow" error
TYPE Type2
x as string * 32767
y as string * 2
END TYPE
Page 212, Monitoring a Station's Status
---------------------------------------
The following status code needs to be added to the list in this
section:
Status Code Value Description
-------------------------------------------------------------
ST_RECONNECTED 5 If a station has disconnected
from the host and attempts to
reconnect, its old entry in the
station list is updated
to this status.
Page 324 and 325, SendData and SendDataFile Procedures
-----------------------------------------------------
The syntax for the DECLARE FUNCTION statements for these two
procedures is missing a parameter (wType%). These statements
should look like this:
DECLARE FUNCTION SendData LIB "TESTHost.dll" (StationNum%,
wType%, lpData AS ANY, DSize&) AS INTEGER
DECLARE FUNCTION SendDataFile LIB "TESTHost.dll" (StationNum%,
wType%, FileName$) AS INTEGER
wType%
Communicates to the station what kind of data you are sending.
For example, if you are sending a script to be executed,
set this parameter to DT_SCRIPT. When the station gets the data,
this parameter determines what gets returned by the
GetDataType() function on the station side.
Page 388, Return Values
-----------------------
Add the following Error messages to the end of the table on this page
(Value 29 is replaced):
Error message Value
-------------------------------------
ERR_CANT_MOVE_WND 29
ERR_CANT_SIZE_WND 30
ERR_CANT_ADJ_SIZE_POS_WND 31
ERR_CANT_FIND_LBBOX 32
ERR_NOT_OPERATOR_NOT_ALLOWED 33
ERR_CANT_ADD_NULL_ITEM 34
ERR_BAD_POINTER 35
MAX_ERROR 36
Pages 393-397, WFndWnd and WFndWndWait Procedures (TESTCTRL.DLL)
----------------------------------------------------------------
Add the following wFlags to the list starting on page 393:
FW_MAXIMIZE If a window is found, it is maximized.
FW_MINIMIZE If a window is found, it is minimized.
FW_RESTORE If a window is found, it is restored.
FW_DIALOG Find dialog boxes (class #32770) only.
FW_DIALOGOK Find either windows or dialog boxes
Additional Comments:
The first 3 wFlags in this list do not imply FW_FOCUS.
If the window is an MDI window, it can be maximized,
minimized, or restored without automatically gaining the
focus. Although FW_MAXIMIZE and FW_RESTORE do not imply
FW_FOCUS, top-level windows will get the focus because
of the way Windows works.
Some applications put up dialog boxes with the same
caption as the application's main window. If this happens,
you may find the wrong window if you use WFndWnd().
Instead, use WFndWndC() and specify a class when locating
windows in these cases.
To make things easier and more readable when looking for
a dialog, instead of using WFndWndC() and specifying the
class name "#32770" (the dialog class), you can use
WFndWnd() and use the FW_DIALOG flags.
Page 394, WFndWnd Procedure (TESTCTRL.DLL)
------------------------------------------
o In the description of FW_IGNOREFILE at the top of this page,
replace the word "following" with "preceding."
o In the first paragraph in the Comments section on this page,
after the first sentence, add the following:
NULL and an empty string ("") for the lpszCaption$
parameter are not treated the same:
("") The window must have an empty caption to match.
NULL The window caption/text is ignored; can be anything.
Page 475, FILELIST Statement
----------------------------
Add this note before the "Examples" heading:
NOTE: The maximum number of files in the file list is 65,000.
If a FILELIST ADD statement causes the file list to exceed
this size, a run-time error 11, "Filelist processing error,"
occurs. The file list will contain only the first 65,000
files added to it. No more files can be added until a
FILELIST REMOVE or a FILELIST CLEAR statement is used.
Page 488, LEN Function
----------------------
Add the following paragraphs to the "Remarks" section:
If <variablename> is a user-defined type, LEN returns
the size of the TYPE structure. For example:
TYPE MyType
elem1 As Integer
elem2 As String * 10
END TYPE
LEN(MyType) 'returns 12.
If <variablename> is an array, LEN returns the size of an
individual array element. For example:
DIM array(100) AS DOUBLE
LEN(array) 'returns 8.
Page 494, MSGBOX Statement
--------------------------
o MB_APPLMODAL Description
Add this note to the description in Table 9.4:
NOTE: When you set the MB_APPLMODAL flag, the
message box is modal to the script window for
that script, not to the Test Driver window in
which you are running the script.
o The example after the paragraph following Table 9.4 is not correct:
MB_OKCANCEL + MB_ICONSTOP + MB_DEFBUTTON1 + MB_APPLMODAL
It should look like this:
MB_OKCANCEL OR MB_ICONSTOP OR MB_DEFBUTTON1 OR MB_APPLMODL
o A new flag has been added for the MSGBOX statement and function.
It is:
Symbolic constant Value Description
-----------------------------------------------------------
MB_NOBEEP 32,768 Turns off the system beep
that sounds when you choose
an icon and its dialog box
appears.
Page 501, OPTION BASE Statement
-------------------------------
Additional Remarks:
The Microsoft Test OPTION BASE statement is different in
some ways from the OPTION BASE statement in QuickBasic and
Visual Basic. In QuickBasic and Visual Basic, you can use
OPTION BASE only once in a program. Also, you must use it
before any arrays are dimensioned.
The Microsoft Test OPTION BASE is a toggle switch. You
can use it more than once. For example:
DIM array1(10) AS INTEGER 'Defaults to base 0
OPTION BASE 1
DIM array2(20) AS SINGLE
OPTION BASE 0
DIM array3(30) AS DOUBLE
Page 501, OPTION INTEGER Statement
----------------------------------
The OPTION INTEGER statement affects the output of the RND function
and the TIMER function as follows:
If OPTION INTEGER is used, RND generates a random integer
between 1 and 32,767. Otherwise it generates a random number
between 0 and 1.
If OPTION INTEGER is used, TIMER returns a long integer
containing the number of milliseconds since the system started.
Otherwise, it returns a double-precision floating-point value
containing the number of seconds since the system started.
==========================================================
PART 1: Documentation Errata and Additions
b: Microsoft Test User Interface Editor User's Guide
==========================================================
Page 101, MSTLoadIcon Function Syntax
-------------------------------------
Add the following information to the paragraph that starts "icon ID
is the resource ID number... ":
To get the resource ID number of an icon
1. From the Icons dialog box, select an icon.
2. Press F2.
The resource ID number and the icon is displayed.
============================================
PART 2: New Dynamic-Link Library Procedures
============================================
The procedures in this section are "new" because they were created
after the books went to press.
New TESTCTRL.DLL Procedures
---------------------------
o WLabelLen()
Included if W_STATIC is defined.
Syntax:
Declare Function WLabelLen Lib "TestCtrl.DLL" Alias
"WLabelLen" (hwnd%) AS INTEGER
Returns:
Length of associated label; zero if no associated label.
Comments:
WLabelLen() obtains the length of the associated label
for the specified window. hwnd% is the Window to check.
If zero, check the control with the focus.
hwnd% must be a child (WS_CHILD) and cannot have a
caption (WS_CAPTION).
o WLabelText()
Included if W_STATIC is defined.
Syntax:
Declare Sub WLabelText Lib "TestCtrl.DLL" Alias
"WLabelText" (hwnd%, lpszBuffer$)
Declare Function LabelText (hwnd%) AS STRING
Returns:
Nothing.
Comments:
WLabelText() obtains the text of the associated label
for the specified window. hwnd% is the Window to check.
If hwnd% is zero, checks the control with the focus.
lpszBuffer$ is the buffer for label text.
hwnd% must be a child (WS_CHILD) and cannot have a
caption (WS_CAPTION).
Both of the above procedures can be used to determine whether a control
has an associated label. WLabelLen() returns zero if no label, and
LabelText() returns an empty string if no label.
o WListItem(action)Ex
Four new procedures are identical to their non-"Ex" counterparts,
except for the added parameter ixOffset%.
Syntax:
Declare Sub WListItemClkEx Lib "TESTCTRL.DLL" Alias
"WListItemClkEx" (lpszName$, lpszItem$, ixOffset%)
Declare Sub WListItemCtrlClkEx Lib "TESTCTRL.DLL" Alias
"WListItemCtrlClkEx" (lpszName$, lpszItem$, ixOffset%)
Declare Sub WListItemShftClkEx Lib "TESTCTRL.DLL" Alias
"WListItemShftClkEx" (lpszName$, lpszItem$, ixOffset%)
Declare Sub WListItemDblClkEx Lib "TESTCTRL.DLL" Alias
"WListItemDblClkEx" (lpszName$, lpszItem$, ixOffset%)
Comments:
The value of ixOffset% determines where the item is clicked:
= 0: item is clicked in the center of the item rectangle,
zooming is performed to support File Manager-type
list boxes.
> 0: item is clicked at ixOffset% from the left of the item
rectangle
< 0: item is clicked at ixOffset% from the right of the item
rectangle
New TESTDLGS.DLL Procedures
---------------------------
o SetMatchPreferences()
Syntax:
Declare Sub SetMatchPreferences (ExDlg%, FzDlg%, ExMenu%, FzMenu%)
CONST MATCH_TEXT = 1 'Text
CONST MATCH_CASETEXT = 2 'Text, case insensitive
CONST MATCH_CLASS = 4 'Class name
CONST MATCH_STATE = 8 'State
CONST MATCH_STYLE = 16 'Style
CONST MATCH_RECT = 32 'Rectangle
CONST MATCH_ALL = 63 'Match all
Comments:
This procedure sets the criteria for a Test Dialogs comparison.
The integer for each comparison type is some combination of the
MATCH_ flags. The default state is equivalent to the following:
MATCH_ALL 'Exact, Dialogs
MATCH_CLASS OR MATCH_STATE 'Fuzzy, Dialogs
MATCH_TEXT OR MATCH_CASETEXT OR MATCH_STATE 'Exact, Menus
MATCH_TEXT OR MATCH_CASETEXT 'Fuzzy, Menus
o GetMatchPreferences()
Syntax:
Declare Sub GetMatchPreferences (ExDlg AS POINTER TO INTEGER,
FzDlg AS POINTER TO INTEGER,
ExMenu AS POINTER TO INTEGER,
FzMenu AS POINTER TO INTEGER)
Comments:
This procedure gets the criteria for a Test Dialogs comparison.
The MATCH_ flags are the same as defined for SetMatchPreferences().
New Test Talk Procedures
------------------------
o SetLanaNum()
If you have more than one LAN adapter or protocol on your
machine, you can choose which adapter or protocol to use when
running Test Talk. Both Test Talk DLLs (TESTHOST.DLL and
TESTSTAT.DLL) contain this new procedure.
Syntax:
DECLARE FUNCTION SetLanaNum(LNum%) AS INTEGER
Return Values:
SetLanaNum() returns TRUE if the lananum can be used;
FALSE if not. If the function returns FALSE, it means either
that there is no adapter or LAN protocol for that lananum,
or that the adapter or LAN protocol exists and doesn't
support NETBIOS.
Comments:
This function checks the specified lananum to see whether it
supports NETBIOS. If it does, then that lananum is used by
Test Talk from then on.
When the Test Talk DLLs load, they automatically search the first
eight lananums (0 - 7) for the first one that supports NETBIOS.
The first one found is used unless you change it by using
SetLanaNum().
o NetBIOSAvailable
This procedure is included in both TESTSTAT.DLL and TESTHOST.DLL. It
checks the first eight (0 - 7) lananums for the first one that
supports NETBIOS. The first one found is used by Test Talk unless
you change it with SetLanaNum(). If NetBIOSAvailable returns
FALSE, it means that no adapter or LAN protocol on the machine
supports NETBIOS.
New TESTUI.DLL Procedures
-------------------------
MSTSysMenu()
Included if either W_MENU or TESTUI is defined.
Syntax:
Declare Sub MSTSysMenu Lib "TESTUI.DLL" Alias
"MSTSysMenu" (hwnd%, iMenuType%)
Const MST_GLOBAL = 1
Const MST_APP = 2
Const MST_WINDOW = 4 (only applies to User Interface Editor's
test mode windows)
Comments:
MSTSysMenu() drops the specified sysmenu on the specified window.
hwnd% is the Window to check. If zero, check the active window.
iMenuType% is the Type of the sysmenu. It can be any one of the
following:
MST_GLOBAL
MST_APP
MST_WINDOW
If the window doesn't have the specified sysmenu installed, nothing
happens. If the window has the specified sysmenu and it is not the
active window, it is made the active window.
MSTSysMenuExists()
Included if either W_MENU or TESTUI is defined.
Syntax:
Declare Function MSTSysMenuExists Lib "TESTUI.DLL" Alias
"MSTSysMenuExists" (hwnd%) AS INTEGER
Return Values:
The function returns a bit pattern:
bit 0 1 if a global sysmenu is installed
bit 1 1 if an application-specific sysmenu is installed
bit 2 1 if a window-specific sysmenu is installed
(NOTE: Bit 2 only applies to the User Interface Editor when in
test mode.)
Comments:
MSTSysMenuExists() determines if the specified window has an
MSTSysMenu installed. hwnd% is the Window to check. If zero,
check the active window.
Examples:
MSTSysMenuExists() returns the following values:
Zero If no sysmenus are installed.
MST_GLOBAL(1) If only a global sysmenu is installed.
MST_APP(2) If only an application-specific sysmenu
is installed.
MST_WINDOW(4) If only a window-specific sysmenu is
installed.
3 If both a global and an application-specific
sysmenu are installed.
o MSTLoadBitmap()
Syntax:
int = MSTLoadBitmap(bitmap ID, .RES file)
Return Value:
MSTLoadBitmap returns hBitmap (the bitmap handle)
which is used when calling MSTDestroyBitmap.
Comments:
See MSTLoadIcon() on page 100 in the Microsoft Test User Interface
Editor User's Guide.
To get the resource ID number of a bitmap:
1. From the Sysmenu Bitmaps dialog box, select a bitmap.
2. Press F2.
The resource ID number and the bitmap is displayed.
o MSTDestroyBitmap()
Syntax:
MSTDestroyBitmap(hBitmap)
Comments:
See MSTDestroyIcon() on page 101 in the Microsoft Test User Interface
Editor User's Guide.
===============================
PART 3: Enhanced Functionality
===============================
Test Dialogs
------------
o Converting Version 1.0 Files
Files created using version 1.0 are no longer readable by
Test Dialogs. To convert 1.0 files to 2.0 format:
1. Use the Test Dialogs user interface to create a new
2.0 file.
2. Use the new File.Convert 1.0 File command to import
the contents of the 1.0 file. This converts the dialogs
in the 1.0 file and appends them to the currently open
2.0 file.
It is better to recapture the dialogs using version 2.0, than to
convert them from version 1.0. Version 2.0 stores more information
about dialog controls making it possible to accurately preview and
export the dialogs. For this reason comparisons are more reliable.
For example, in 1.0 the coordinates for each control were saved
relative to the screen, and in 2.0 they are saved relative to their
parent. If the dialog is in a different screen location during
comparison, the rectangles will still match, provided their position
relative to the dialog window itself did not change. Also, style bits
are now stored for the controls, allowing Test Dialogs to distinguish
different controls within the same class.
In version 1.0, the following information was stored:
- Text (up to 256 characters)
- Class name (to 32 characters). Menu items are of the class
"MenuItem."
- State:
- for class BUTTON, 0 = unchecked, 1 = checked,
2 = undetermined
- for menu items, return value of GetMenuState() at time
of capture
- fVisible = TRUE if control is visible
- fEnabled = TRUE if control is enabled
- Rectangle. Screen-relative position and size of control
(GetWindowRect() at time of capture).
In version 2.0, the following information is stored:
- Text (up to 2048 characters)
- Class name (complete, no enforced length limit)
- Style bits:
- for menus, this field is used to identify pop-up menus;
contains the number of sub-menus in a pop-up menu
- for controls and windows, this field contains the
style bits
- State:
- for menu items, return value of GetMenuState() at the time
of capture
- for controls and windows, this field is a combination of bits:
1 if the control is visible
2 if the control is enabled
4 if the control is a button and is checked
8 if the control is a 3-state button and is indeterminate
- Font (for controls and windows only). Face name, height,
and weight of font used to paint the control at time of capture.
- Rectangle. Position and size of the control relative to its parent.
o Text Import and Export
You can create a text file in RC-like format, representing dialogs
and menu structures. You can edit the text file using any text editor,
and then import it into a dialog file using the import feature.
If you capture a menu and then remove items from it using the User
Interface Editor, you cannot preview or export the menu. If you convert a
menu from a 1.0 file, the converted menu won't be completely accurate.
If there are second- or higher-level menus, they will appear as top-level
menus. To fix this in import/export, do the following:
1. Create a text file.
2. Edit the text file to place the higher-level menu in a
pop-up structure.
3. Re-import the menu.
User Interface Editor
---------------------
o Dragging and Dropping Icons
In the User Interface Editor, you can add icons to the .RES
file by dragging them from the Preview window of the Icons
dialog box and dropping them into the Icons list.
To assign an icon to an item, you can drag it from the Icons
list box and drop it onto a sysmenu item in a sysmenu or onto
an icon control in a dialog box.
Double-clicking to assign the icon still works as before.
o Using the SPACE key with Icons and Bitmaps
In the User Interface Editor, pressing SPACE now acts just like
double-clicking the left mouse button in the Icons/SysMenu Bitmaps
dialog to assign icons to icon controls and sysmenu items.
o New Check Box in "Arrange.Settings" Dialog Box
The "Arrange.Settings" dialog box has an additional check box:
Hide &UI-Editor while in test mode
The check box is selected by default. If it is selected, only the
Test Mode Dialog or Test Mode Menu window is visible while in test
mode. If not selected, UIEditor items are visible as usual.
This option prevents access to the properties bar 3D and Iconbar
check boxes while in test mode. Therefore, a method was added to
select these check boxes if the User Interface Editor is hidden in
test mode. When you test a dialog, the following menu item is
added to the Test Dialogs system menu:
&View 3D 'Toggles 3D mode
If the dialog being tested has no system menu, and the User Interface
Editor is hidden, then you cannot toggle between 3D and 2D.
For testing an MSTSysMenu, the following items have been added to the
Test Windows system menu:
S&ysMenu 'Toggles from iconbar to sysmenu if currently iconbar
&Iconbar 'Toggles from sysmenu to iconbar if currently sysmenu
&View 3D 'Toggles 3D mode if sysmenu. Grayed if iconbar.
For testing an Application menu, no items have been added to the
system menu. For testing any item, the "Close" system menu item for
the Test Dialog and Menu Test window has been changed to:
&Design Mode Alt+F4
o Dialog Coordinates and Control Units
The coordinates displayed in the upper left of the User Interface
Editor's properties bar were formerly displayed in dialog units.
Now dialogs and controls are displayed in either "dialog units" or
"pixels." To change between the two, simply click with the right mouse
button anywhere in the dialog you are editing.
Detecting a Disk in Drive A: or B:
----------------------------------
The following example shows what happens for each statement,
assuming that drives A: and B: exist, but there is no disk in either
drive.
ON ERROR GOTO ErrorTrap
print exists("A:") 'This works, since the drive really is there
print exists("B:") 'This works, since the drive really is there
chdrive("A:") 'This works, since the drive really is there
print CURDIR$ 'This fails and can be trapped
OPEN "A:\temp.dat" for output as #1 'This fails and can be trapped
close
chdrive("B:") 'This works, since the drive really is there
print CURDIR$ 'This fails and can be trapped
OPEN "B:\temp.dat" for output as #1 'This fails and can be trapped
close
end
ErrorTrap:
PRINT
PRINT ERRORS
PRINT "The drive either does not have a disk"
PRINT "inserted or the drive door is open."
PRINT
RESUME NEXT
In summary:
1. In version 1.0, a sysmodal dialog would have occurred on the
CURDIR$ statement and the OPEN statement. This error ruins automated
tests since it can't be trapped. This no longer occurs. You can trap
and recover from these errors and your automated tests can continue
unattended.
2. If you are writing a program that must detect whether a disk is in
the drive (a setup program, for example), you can do this by using
CURDIR$ or OPEN, trapping the error, then prompting for a disk or
taking other appropriate action.
RUN Statement/Function
----------------------
The RUN function and statement have been modified to look in WIN.INI
for file extensions. If you run an extension (for example, .TXT) that
has an associated .EXE in WIN.INI, RUN will use the associated
extension and pass the string argument to it as the command line.
NOT (!) Operator
----------------
Using the NOT operator (!) with any of the W(type)SetClass procedures
makes no sense and can actually cause problems. Therefore, this
operator is no longer supported, and will cause the following error
if it is used with any W(type)SetClass procedure.
ERR_NOT_OPERATOR_NOT_ALLOWED = 33
The class name "NOT (!) operator" is supported only by WFndWndC() and
WFndWndWaitC().
Test Trap Additions, Corrections, and Changes
---------------------------------------------
For information on Microsoft Test event traps, please see the
file README.TXT in the V2SAMPLE\TRAPS subdirectory.
======================
PART 4: Miscellaneous
======================
Using MS-DOS Boxes on the Novell Network
----------------------------------------
If you are using the Novell network and experience intermittent
problems using an MS-DOS box, please change or add the following
line in your SYSTEM.INI 386enh section.
[386enh]
TimerCriticalSection = 5000
The SYSTEM.INI file is located in your Windows directory.
Test Talk Issues
----------------
o Procedures Fail when NETBIOS is not Available
The Test Talk procedurss now fail when NETBIOS is not available.
There is no error message; the routines simply do nothing or
functions return FALSE. If Test Talk scripts don't appear to be
working, you can call NetBIOSAvailable to see if this is the problem.
See the description of NetBIOSAvailable in Part 2.
o Declarations are Not Included in DECLARES.INC
Including the precompiled header DECLARES.INC (built as part of the
setup process) in your script doesn't pull in the Test Talk
declarations and constants. This is because several routines in
TESTHOST.DLL and TESTSTAT.DLL have the same names. To use
Test Talk, you must $DEFINE either TESTHOST or TESTSTAT and include
MSTEST.INC, rather than using DECLARES.INC. You can also build your
own precompiled headers for the host and station scripts (one header
for host scripts and another for station scripts).
o "Setup" Functions
Three functions in the Test Talk DLLs are considered "setup"
functions:
NetBiosAvailable(), SetLanaNum(), and SetMachineName()
You must call these at the beginning of your script, before you call
JoinGroup(). After you have joined a group, all three of these
functions will return FALSE. While you belong to a group, you can't
change the lananum or machine name.
Callbacks as Parameters
-----------------------
If a script gives the address of a routine (a callback) to a DLL
procedure, and that procedure takes SINGLE or DOUBLE parameter types,
it is the caller's responsibility to pass those values by reference.
All TestBasic procedures expect their parameters by reference, which
means a pointer to the data rather than the data itself. The only two
exceptions are:
INTEGER and LONG, which are special cases to be passed by value
from callbacks
STRING, which is converted to a temporary variable-length
string and essentially passed by value
Incorrect use of parameters in callbacks will cause your script to crash.
WindSock 3.10 - Windows Performance Analysis Utility FreeWare by Chris Hewitt Copyright (c) 1992, 1993 Technical Pixies This package consists of the following files: README.TXT - This File TOOLHELP.DLL - MicroSoft's ToolHelp DLL for Windows WINDSOCK.HLP - WindSock 3.10 Help File WINDSOCK.EXE - WindSock 3.10 Program In order to install WindSock 3.10: 1) Check to see if you already have a TOOLHELP.DLL in your Windows directory. If you do, check it's date stamp. If it is older than the TOOLHELP.DLL included in this package, replace it with this one, otherwise leave it. 2) Copy the WINDSOCK.EXE and WINDSOCK.HLP files to a directory on your hard disk. The windows directory is OK. 3) Use File...New in the program manager to add the WINDSOCK.EXE to one of your program groups.
All files in the GAMETOOL.ARJ
g3.exe - gametools normal version
g.doc - document of gametools
gt3-r.arj - garbled ARJ with the following files:
{
g3x.exe - gametools XMS version
g3e.exe - gametools EMS version
g3e.ovr - gametools EMS version overlay file
gtsreg.exe - gametools registerion program
up.exe - univeral compressed EXE/COM decompressor
it can unpack some extractable EXE
}
UP.EXE: This is an utility for executable files decompression. It can
decompress EXE or COM compressed by DIET, PKLITE, LZEXE, EXEPACK,
COMPACK. It can unpack unextractable EXE compressed by PKLITE.
Welcome to Sidekick 2.0
----------------------------------------------------------
This README file contains important information about
Sidekick 2.0. For the latest information about Sidekick 2.0
and the manuals, read this file in its entirety.
TABLE OF CONTENTS
-----------------
1. Important Information
2. Files on the Disks
1. IMPORTANT INFORMATION
------------------------
- INSTALLING: You MUST use the INSTALL program to install
Sidekick 2.0. The files on the distribution disks are
archived and have to be properly assembled. You cannot do
this.
- QEMM.SYS users: Do not use command line switch or parameter
"Frame =A000-AFFF". Sidekick uses this area.
- NETWORK Users: The User Dictionary (USER.DIC) is not a
sharable file. In SKCONFIG, under Network, User Dictionary
Directory should be your private directory.
- On a NOVELL network your CAPTURE command must contain "/NT"
for no tabs AND "/TI=15" for time out, for example,
capture /NT /TI=15
Other networks may require a similar statement.
- When converting SK 1.x Dialer files, you must define the
format of the dialer in a text file with the extension .fmt.
The following naming convention is used for these .fmt files.
SKCONVER will first look for a file called <fname>.fmt
where <fname> is the name of your Dialer file. Using the
SK Classic default, this would be "phone.fmt".
If no <fname>.fmt file is found, then SKCONVER will look
for a file named "default.fmt".
If neither of these files exist, then the conversion
will not continue.
The .fmt file must be in the same directory that contains
SKCONVER. For details on how to structure the .fmt file, read
the "default.fmt" file that is in your SK2 directory.
- CHANGING SORT ORDER:
Copy the appropriate .SOR file to PARADOX.SOR
Delete all .PX files
Run SKCONVER, using the Rebuild option, on each database
file.
- Sidekick Plus TimePlanner files that are converted will have
to be edited if any entries contained an alarm to dial a
VOICE/DATA number. Sidekick PLUS alarms used the "INDEX"
field to specify which number to dial. Sidekick 2.0 uses
"Last Name, First Name" fields for VOICE calls and "Service"
for DATA numbers.
- LOADING: SK2/? Use to see list of command line parameters,
when loading Sidekick.
- PRINTING: If printing using a "cut sheet feeder" make sure
you have set the dip switches correctly. Check the your
printer manual for "out of paper" situations.
- Monthly text prints out day titles only, NO appointments.
- When using opposed pages during printing, you will want
to increase the right margin to allow space for hole
punching.
Printer/mode/size Top Bottom Left Right
================= === ====== ==== =====
PostScript/text/letter 1.300 1.000 0.750 0.500
HP Laserjet/AB text/letter 0.500 1.400 0.750 1.000
QMS ColorScript/graphics/letter 1.200 0.700 0.750 0.500
HP Deskjet 500/graphics/A4 0.500 0.600 0.750 0.500
QMS PS-410a/graphics/A4 0.700 0.500 0.750 0.500
- When printing text to an HP Laserjet type printer, you
should select a font, on the printer, that supports the
extended ASCII character set.
- ATTACHED NOTES: Maximum file size for attached note in Time
Planner is 6,000 characters. Maximum size for attached notes
in Address Book and Communications is 48,000 characters.
2. FILES ON THE DISKS
---------------------
DISK 1
INSTALL EXE - Installation program
README - This file
README.COM - Program to view README
UNZIP EXE - Program to unpack the Sidekick program
SK2-1 ZIP
Containing:
SK2 EX1 - Part of Sidekick 2.0
DISK 2
SK2-2 ZIP
Containing:
ADDRESS DB - Sample Address Book file
ADDRESS PX - Index for Address Book file
APP DB - Sample Time Planner file
APP PX - Index for Time Planner file
BIX SCR - Script for BIX
CHARS BGI - File used during font building
CHARSALL BGI - File used during font building
COMMS DB - Sample Communications file
COMMS PX - Index for Communications file
CSERV SCR - Script for CompuServe
CUSTOMER TXT - Sample text file
DEFAULT FMT - File used by SKCONVER
DUT SFO - Font definition file
LETTER TXT - Sample text file
MCI SCR - Script for MCI
MODEMS SK - Modem initialization strings
NUMBERS BGI - File used during font building
SK2 EX2 - Part of Sidekick 2.0
SK2 OVL - Part of Sidekick 2.0
SWS SFO - Font definition file
SWSB SFO - Font definition file
DISK 3
SK2-3 ZIP
Containing:
SK2 EX3 - Part of Sidekick 2.0
THAM LEX - Thesaurus file
DISK 4
SK2-4 ZIP
Containing:
KERNEL BGI - Graphical print support file
POSTSCRP BGI - Graphical print support file
PREAMBLE BGI - Graphical print support file
PRINTERS BGI - Printer selection file
PXENGINE OVL - Program used by SKCONVER
SPMAIN LEX - Dictionary file
SPMAIN LNG - Part of dictionary
USER DIC - User dictionary
DISK 5
SK2-5 ZIP
Containing:
ASCII SOR - ASCII sort order definition
FONTBLD EXE - Program to build fonts
NORDAN SOR - Norway/Denmark sort order definition
PARADOX SOR - International sort order definition
SK2 HLP - Sidekick 2.0 help file
SK2 PIF - Program Information File for WINDOWS 3.0
SKCONFIG EXE - Sidekick 2.0 Configuration program
SKCONVER EXE - Sidekick 2.0 convertion program
SWEDFIN SOR - Sweden/Finland sort order definition
NOTE: For users with 3 1/2 inch disks, disk 1 and disk 2 are on
the first disk. Disk 3 and disk 4 are on the second disk.
Disk 5 is on the third disk.
-------------------END OF README------------------------
WELCOME TO SUPERKEY 1.1
-----------------------
This file contains information on how to get help, important
information, and a list of files on the distribution disk. Since this
file contains information important to you, please read it in its
entirety; it should answer questions you have.
┌──────────────────────REFLEX.MAC────────────────────────┐
│ Superkey now contains macros for Reflex, The Analyst. │
│ Reflex is the most amazing and easy-to-use database │
│ management system. And if you already use Lotus 123, │
│ dBase, or PFS:File, you need Reflex--because it's a │
│ totally new way to look at your data. It shows you │
│ patterns and interrelationships you didn't know were │
│ there, because they were hidden in data and numbers. │
│ It's also the greatest report generator for 1-2-3. │
│ │
│ Reflex 1.1 is available at your favorite dealer or │
│ directly from Borland for only $149.95. │
└────────────────────────────────────────────────────────┘
TABLE OF CONTENTS
-----------------
1. How to Get Help
2. Important Information
3. File List
1. HOW TO GET HELP
------------------
If you need help with SuperKey, please read this file and the Owner's
Handbook, especially Appendix D, HELP!!!. The sample macro files
included on this disk are also a good source of information on how
SuperKey may be used.
If you still have a question and need technical assistance, help is
available from the following sources:
1. Type GO BORLAND on the CompuServe bulletin board system.
2. Check with your local software dealer or user group.
3. Write to: Borland International
SuperKey Technical Support
4585 Scotts Valley Drive
Scotts Valley, CA 95066
4. If you have an urgent problem that cannot wait and you have sent
in the license agreement from the front of your manual, you may
call the Borland technical support department.
Please have the following information ready before calling:
1. Product name and disk serial number
2. Computer name, model and the names and model numbers of any
additional hardware.
3. Operating system and version number (the version number can be
determined by typing <VER> at any DOS prompt).
4. Contents of your AUTOEXEC.BAT file.
5. Contents of your CONFIG.SYS file.
2. IMPORTANT INFORMATION
------------------------
1. If you have a 101 key keyboard from IBM (one that has
function keys F11 and F12) please note that the Print Screen
and the grey * are not on the same key as the older style 83 key
keyboards. For this reason the Show Titles command becomes
<ALT><*> instead of <ALT><PRTSCR> where the <*> is on the numeric
keypad. Note that the <*> is different than a shifted 8.
2. Superkey's feature of blanking the screen over graphics may not
work properly with programs that do not tell the computer when
graphics are active. Typically, when you invoke Superkey over
a program such as this, you will get "modern art" on the screen
behind Superkey. To get your graphics back when you exit Super-
key you will have to issue a command to redraw the screen. An
example of this is invoking Superkey over a Lotus 1-2-3 graph.
To redraw your graph after exiting Superkey, simply press <ESC>
and then select View under the Graph menu of Lotus 1-2-3.
3. SuperKey and the IBM PCjr. Since the IBM PCjr cannot send the
keystroke <ALT></>, which is needed to invoke the SuperKey main
menu, it is necessary to change the "hot key" to <CTRL></>. This
is done by simply running the file PCJRINST.BAT located on the
disk. At the DOS prompt, simply type PCJRINST then press <ENTER>
before loading SuperKey for the first time. From then on, you can
load SuperKey by simply typing KEY and invoke the menu by pressing
<CTRL></>.
4. For more helpful information, be sure to refer to the manual,
including Appendix F. HELP!!! . This Appendix contains answers
to the most commonly asked questions regarding the use of
SuperKey.
3. FILE LIST
------------
NOTE: Several of the macro files (MAC) listed below are for use
with different word processors and spreadsheets. These are provided
to demonstrate how you can use SuperKey to make different programs
"look" and "feel" the same by providing the same keystrokes to do
similar functions. These files are for demonstration purposes
only and can be modified to suit your own needs.
File Description
--------------------------------------------------------------------
README COM - Program to display the README file on the screen
KEY COM - The SuperKey program
KEYDES COM - The SuperKey program with the DES encryption
implementation
KEY HLP - Help file for SuperKey
LAYOUT COM - The keyboard layout program
KEYINST COM - SuperKey installation program
PCJRINST BAT - This file contains the necessary commands to get
SuperKey running properly on the PCjr.
123 MAC - Macros to be used with LOTUS 1-2-3
123TRNSP MAC - Same macro file as above but with the transparent
(<TRANSP>) command included
BASICA MAC - Macros to be used with BASICA
DOS MAC - Macros that make common DOS commands a little
easier to use
DOSTRNSP MAC - Same macro file as above but with the transparent
(<TRANSP>) command included
EDIX MAC - Macros to be used with EDIX
FOREIGN MAC - Macros that allow you to use the letters most
commonly found in foreign languages
GRAPH MAC - Macros that allow you to use extended ASCII
characters to do graphics
GRAPH2 MAC - "
INVENT4 MAC - A Macro demonstrating what beautiful music you can
make with SuperKey's sound capability.
LUNCH MAC - A Macro that demonstrates keyboard lockout
MERGE1 MAC - Macros that demonstrate the merge facility in
SuperKey
MERGE2 MAC - "
MERGE3 MAC - "
REFLEX MAC - Macros to be used with Reflex, The Analyst from
Borland International.
SUPCALC3 MAC - Macros to be used with SuperCalc3
TAPE MAC - Macros to be used with SideKick's calculator
that allow you to use the notepad as a tape
TAPEOFF MAC - File that allows you to turn TAPE on and off
TURBO MAC - Macros to be used with Turbo Pascal
VISICALC MAC - Macros to be used with Visicalc
VOLKSWTR MAC - Macros to be used with Volkswriter
WORDIX MAC - Macros to be used with Wordix
WORDPER MAC - Macros to be used with Word Perfect 4.0
WS MAC - Macros to be used with WordStar
DVORAK LAY - Sample layout file simulating a Dvorak keyboard
LETTER TXT - Sample document you can experiment with encryption
on
README - This file
END
---
MICROSOFT MOUSE RELEASE NOTES (Software version 9.00)
Copyright (C) Microsoft Corp. 1993
This document contains information that supplements the
"Microsoft Mouse User's Guide" and accompanying software.
The Microsoft Mouse software is designed and tested for
the Microsoft Mouse.
To view best on-screen in Windows Notepad, maximize the
Notepad window and turn on Word Wrap (if it's not already
on). To activate Word Wrap, select the Edit menu and
choose Word Wrap. For best printed results, open this
document in Windows Write, Microsoft Word, or another
word processing application, select the entire document
and format the text in 10 point Courier before printing.
Tip: To quickly find any section of this README, use
your word processing application's Search command.
CONTENTS
I. Important Ergonomic Safety Information
II. The Microsoft Mouse Setup Program
1. Modifications Made by Setup
2. Returning Your System to Pre-Setup Condition
3. Setting up to a Floppy Disk System
4. Loading MOUSE.EXE into Upper Memory
III. The MOUSEPWR Feature
IV. Microsoft Windows NT Support for Your Mouse
V. Meet the Mouse
VI. Notes on Mouse Manager Features
1. Windows and MS-DOS Features
2. Magnify
3. Screen Wrap
4. Snap-to
5. Mouse Trails
VII. Other Issues
1. MS-DOS Support for the IBM XGA Video Card
2. Hot Keys on LCD Screens
3. Large and Medium Pointers
4. Windows 3.0 Support
VIII. More Ergonomic Information
_________________________________________________________________
I. IMPORTANT ERGONOMIC SAFETY INFORMATION
*******************************************************************
* Some studies suggest that long periods of repetitive motion, *
* coupled with an improper work environment and incorrect work *
* habits, may be linked to certain types of physical discomfort *
* or injury. These include carpal tunnel syndrome (CTS), *
* tendinitis, and tenosynovitis. It is important to follow all *
* instructions carefully. Failure to do so may result in CTS, *
* tendinitis, or tenosynovitis. These instructions may not only *
* help minimize your chances of experiencing one of these *
* conditions, but will also help you to work more comfortably *
* and effectively. Ensuring that your chair, work surface, and *
* the placement of the mouse are in the correct positions is *
* important. In addition, you should take frequent breaks to *
* avoid sitting in the same position for extended periods of *
* time. See the end of this README for more important ergonomic *
* information. *
*******************************************************************
_________________________________________________________________
II. THE MOUSE SETUP PROGRAM
1. Modifications to Your System
The following changes are made to your system if you set up the
software using all the default conditions during the mouse Setup
program (default directory is c:\mouse).
For the mouse driver in MS-DOS, Setup makes the following changes:
a. Installs or modifies lines similar to the following in AUTOEXEC.BAT:
set mouse=c:\mouse
c:\mouse\mouse.exe
b. Adds mouse to the PATH statement.
NOTE: Setup adds mouse to the beginning of your PATH statement.
However, the end of your PATH statement may be truncated if it
contains too many elements.
c. Deletes the following line (if it exists) from CONFIG.SYS:
device=c:\mouse.sys
For the mouse driver in Windows, Setup makes the following changes:
a. Adds the following line to the load line in WIN.INI:
[windows] section c:\mouse\pointer.exe
b. Modifies the following lines in SYSTEM.INI:
[boot] section mouse.drv=c:\mouse\mouse.drv
[boot.description] section mouse.drv=Microsoft Mouse version 9.00
[386enh] section keyboard=mousevkd.386
c. Adds a group to PROGMAN.INI:
groupn=c:\mouse\mouse.grp
(where n = group number and \mouse=mouse directory)
d. Setup updates to the latest CTL3D.DLL file to the Windows System
directory (if it's not already there).
e. If you have Microsoft Windows version 3.0, Setup installs WINHELP.EXE.
2. Returning Your System to Pre-Setup Condition
To return your system to its previous condition before you
ran the mouse Setup program, make the following modifications:
a. Remove the following line from WIN.INI:
c:\mouse\pointer.exe
b. Change the following lines in SYSTEM.INI to read:
[boot] section mouse.drv=mouse.drv
[boot.description] section mouse.drv=Microsoft, or IBM PS/2
[386enh] section keyboard=*vkd
3. Setting up with a Floppy Disk System
Setup supports only hard disk systems and floppy disk systems
with two drives. If you are installing files onto a floppy disk
system that has only one drive, you must decompress and copy the
files manually. EXPAND.EXE, a file-decompression program, is
provided on the Setup disk for this purpose.
To install using a single-drive floppy disk system:
a. Insert the Setup disk into drive A and type:
expand mouse.ex$ b:mouse.exe
b. When prompted by MS-DOS, remove the Setup disk and insert
your destination disk.
c. Reinsert the Setup disk in the drive and type:
expand mousemgr.ex$ b:mousemgr.exe
d. When prompted by MS-DOS, remove the Setup disk and
insert your destination disk.
To load your mouse driver, type:
mouse
Run Mouse Manager to set pointer options, if desired.
To run Mouse Manager, type:
mousemgr
If you install the software using a dual floppy disk system,
set up the mouse software from drive b to drive a.
4. Loading MOUSE.EXE into Upper Memory
The MS-DOS mouse driver automatically loads itself into
upper memory, if available. Using the MS-DOS loadhigh command
may cause your mouse software to load into low memory.
_________________________________________________________________
III. THE MOUSEPWR FEATURE
Some laptop computers have the capability to go into a sleep mode
to conserve power when not being used. Load the MOUSEPWR feature if
your mouse becomes erratic after you resume from sleep mode. MOUSEPWR
restores pre-sleep mode settings of the mouse when you resume
work on the laptop.
It's not necessary to use MOUSEPWR if your system has Advanced
Power Management (APM). However, this feature requires very
little memory (928 bytes) and won't conflict with APM if both
are loaded on your system.
The MOUSEPWR feature is not automatically copied during the
mouse Setup program. Use the MS-DOS copy command to load
MOUSEPWR.COM to your system. The MOUSEPWR feature must
be loaded at the MS-DOS prompt only (not in Windows). If
you need to load MOUSEPWR to your system, add it to your
AUTOEXEC.BAT file so that it loads each time you turn your
system on. For example, if MOUSEPWR is in the root directory,
add the following line to your AUTOEXEC.BAT file:
c:\mousepwr.com
Otherwise, you'll need to load MOUSEPWR manually each time you
want to use it. Type the following line at the MS-DOS prompt
to load the MOUSEPWR feature manually:
\mouse\mousepwr.com
where 'mouse' is the directory containing the MOUSEPWR.COM file.
____________________________________________________________________
IV. MICROSOFT WINDOWS NT SUPPORT FOR YOUR MOUSE
Microsoft Windows NT will have Microsoft mouse drivers included.
For additional mouse support for Microsoft Windows NT, contact
Microsoft Customer Service upon release of Microsoft Windows NT.
Inside the U.S.A., call 1-800-426-9400. Outside the U.S.A.,
please contact your subsidiary.
____________________________________________________________________
V. MEET THE MOUSE
Meet the Mouse is a short, animated demonstration that is
available for viewing when you run the mouse Setup program.
You can also watch Meet the Mouse from Mouse Manager. Meet
the Mouse takes approximately two minutes to run if you have
the minimum required configuration set up for Microsoft Windows.
Meet the Mouse may run slower if you have less than the required
configuration, or if you have a 24-bit graphics card.
To save disk space, you can remove this demonstration by deleting
the ERGODEMO.DLL file from the directory that contains your
mouse software.
____________________________________________________________________
VI. NOTES ON MOUSE MANAGER FEATURES
1. MS-DOS and Windows Features
When you choose Set Buttons, Overall Pointer Speed, Acceleration,
and Orientation from Mouse Manager in Windows, the changes
do not affect the MS-DOS driver until you reboot your computer.
However, if you set these features from the Mouse Manager in
MS-DOS, the changes affect both MS-DOS and Windows.
2. Magnify
Once you activate Magnify with the keyboard key and mouse,
release the key and mouse button. Click any mouse button
to return your pointer to normal.
If you move the magnified pointer quickly in highly graphical
applications, it may take a few seconds for the screen to fully
redraw.
You cannot use the Magnify feature on pull-down menus because
the activating keystroke causes the pull-down menu to close. This
also applies to other items that are deactivated by a single
keystroke.
3. Screen Wrap
Screen Wrap cannot move off the edge of the screen while
Microsoft Windows is busy (for example, while the pointer
is an hour glass).
4. Snap-to
If Snap-to does not work in some dialog boxes, it is because
the default buttons in these dialog boxes do not adhere to the
standard Microsoft Windows user interface specifications.
5. Mouse Trails
You can not adjust the length of Mouse Trails for Paletized
video drivers through Mouse Manager.
_____________________________________________________________________
VIII. OTHER ISSUES
1. MS-DOS Support for the IBM XGA Video Card
A file called XGA.VDM is on your Mouse Setup disk, but is not
automatically copied during Setup. You need to copy this file
to your mouse directory only if you have an IBM XGA card in your
system. This file will give you MS-DOS support for your XGA card.
2. Hot Keys on LCD Screens
On some LCD screens some of the hot keys do not show up or are
not highlighted.
3. Large and Medium Pointers
When using a large or medium sized pointer, some MS-DOS
applications may not redraw the pointer correctly, resulting
in "mouse droppings."
When using a large or medium sized pointer, some applications
for Windows may not enlarge the pointer correctly.
4. Windows 3.0 Support
Setup does not update Mouse Manager in the Windows Control
Panel, version 3.0. But Setup still creates a mouse
program group which contains Mouse Manager.
There is no support for the mouse driver in an MS-DOS windowed
application within Windows 3.0. To get mouse support, run your
MS-DOS application full screen within Windows (ALT + ENTER switches
between a window and full screen).
___________________________________________________________________
VIII. MORE ERGONOMIC INFORMATION
Personalizing your environment so that it is comfortable for your work
situation promotes a healthy physical and mental lifestyle. Studies
show that a carefully planned work environment can actually increase
productivity. Of course, only you can judge whatÆs best for you, so
we encourage you to adapt these tips to your own needs.
Exercises
Exercise and frequent breaks play an important part in staying alert
and comfortable on the job. Take periodic breaks to rest your eyes,
move your body, and get your circulation flowing. Try some of the
following exercises several times during the day.
Gently press your hands against a table, stretch, and hold for five
seconds. Stretch and massage your fingers, hands, wrists, and forearms
throughout the day. Gently shake your hands and fingers to relieve
tension and help blood flow. Rotate your shoulders in a full forward
circle four times. Then roll them backward four times. Then rotate
each shoulder separately four times. Do this at least twice daily.
Organize your work so that you alternate using your computer with
other activities. Try to use different muscle groups throughout the
day. Get up and walk around several times a day.
Note: If you experience pain while using your computer, consult a
qualified health professional.
Chair and Desk
A chair that is adjustable in height is a good place to start. It
should be comfortable and provide firm support to the lower back
(lumbar region). Adjust the chair so that your forearms form
approximate right angles with your upper arms and so that your
feet rest flat on the floor. If your feet donÆt rest flat on the
floor, use a footrest that is high enough so that your thighs
are about parallel to the floor while youÆre seated.
If at all possible, place your system on a desk designed for a
computer. Traditional writing desks are sometimes too high for
computer use. A proper height between your chair and your desk
is essential. And donÆt forget good posture -- slouching puts
unnecessary strain on your back and weakens muscles.
Display and Lighting
Place the display screen directly in front of you at a comfortable
viewing distance. Sit in your chair and make sure that the top of
the display is no higher than eye level. Make sure you canÆt see
glare and bright reflections on the screen (anti-glare filters help)
or on your mouse, and keep your screen clean and dust free.
ItÆs important to look away from your display frequently. Several
times every hour, focus on an object about 20 feet away and slowly
inhale through your nose and exhale through your mouth.
Keyboard and Mouse
Position the keyboard directly in front of you on the desk. While
youÆre typing and using the mouse, keep your shoulders relaxed and
let your upper arms hang freely at your sides. Let your elbows hang
loosely near your body and allow enough room on your desk for
unhindered movement of the mouse. Your forearms should be nearly
parallel and at approximate right angles to the floor as you type
and use the mouse.
Position the mouse at the same height as your keyboard. If you can,
try to avoid light sources that can reflect on the surfaces of your
mouse and keyboard. Use your entire arm to move the mouse around
on your desktop whenever possible. The Microsoft Mouse is designed
so that you can rest your hand on it whenever possible, and so that
you donÆt have to grip it unusually hard when using it. Avoid
excessive tension in your hand by relaxing -- donÆt pinch the
mouse too hard.
The high-performance level of the Microsoft Mouse makes it
unnecessary to use a mouse pad. However, if you do use a mouse
pad, make sure it is not so thick that it raises your arm and
the mouse. Your arm should maintain an approximate right angle
to the horizontal table top. The mouse pad should provide smooth
friction for ease of use -- it should not be too slippery. It
should also be lint free so the mouse ball doesnÆt get dirty.
The design of the Microsoft Mouse accommodates a wide variety
of grips and lets you use the mouse in either hand. The mouse
allows for several possible work positions, which can help you
avoid unnecessary strain on your arms and hands. By periodically
varying the way you hold the mouse, you donÆt repeat the same
motion over a long period of time. The software that comes with
the Microsoft Mouse (Mouse Manager) supports the mouse design
by letting you customize the software for variable work positions.
ItÆs a good idea to periodically readjust your software as you get
better acquainted with your mouse.
_________________________________________________________________
MICROSOFT MOUSE RELEASE NOTES (Software version 9.01)
Copyright (C) Microsoft Corp. 1993
This document contains information that supplements the
"Microsoft Mouse User's Guide" and accompanying software.
The Microsoft Mouse software is designed and tested for
the Microsoft Mouse.
To view best on-screen in Windows Notepad, maximize the
Notepad window and turn on Word Wrap (if it's not already
on). To activate Word Wrap, select the Edit menu and
choose Word Wrap. For best printed results, open this
document in Windows Write, Microsoft Word, or another
word processing application, select the entire document
and format the text in 10 point Courier before printing.
Tip: To quickly find any section of this README, use
your word processing application's Search command.
CONTENTS
I. Important Ergonomic Safety Information
II. The Microsoft Mouse Setup Program
1. Modifications Made by Setup
2. Returning Your System to Pre-Setup Condition
3. Setting up to a Floppy Disk System
4. Loading MOUSE.EXE into Upper Memory
5. The SHARE.EXE File and Multidisk Setup
6. Reinstalling Your Virtual Keyboard Driver
III. The MOUSEPWR Feature
IV. Microsoft Windows NT Support for Your Mouse
V. Meet the Mouse
VI. Notes on Mouse Manager Features
1. Windows and MS-DOS Features
2. Magnify
3. Screen Wrap
4. Snap-to
5. Mouse Trails
VII. Other Issues
1. MS-DOS Support for the IBM XGA Video Card
2. Hot Keys on LCD Screens
3. Large and Medium Pointers
4. Windows 3.0 Support
5. Exiting from Microsoft Windows with a Serial Mouse
VIII. More Ergonomic Information
_________________________________________________________________
I. IMPORTANT ERGONOMIC SAFETY INFORMATION
*******************************************************************
* Some studies suggest that long periods of repetitive motion, *
* coupled with an improper work environment and incorrect work *
* habits, may be linked to certain types of physical discomfort *
* or injury. These include carpal tunnel syndrome (CTS), *
* tendinitis, and tenosynovitis. It is important to follow all *
* instructions carefully. Failure to do so may result in CTS, *
* tendinitis, or tenosynovitis. These instructions may not only *
* help minimize your chances of experiencing one of these *
* conditions, but will also help you to work more comfortably *
* and effectively. Ensuring that your chair, work surface, and *
* the placement of the mouse are in the correct positions is *
* important. In addition, you should take frequent breaks to *
* avoid sitting in the same position for extended periods of *
* time. See the end of this README for more important ergonomic *
* information. *
*******************************************************************
_________________________________________________________________
II. THE MOUSE SETUP PROGRAM
1. Modifications to Your System
The following changes are made to your system if you set up the
software using all the default conditions during the mouse Setup
program (default directory is c:\mouse).
For the mouse driver in MS-DOS, Setup makes the following changes:
a. Installs or modifies lines similar to the following in AUTOEXEC.BAT:
set mouse=c:\mouse
c:\mouse\mouse.exe /q
b. Adds mouse to the PATH statement.
NOTE: Setup adds mouse to the beginning of your PATH statement.
However, the end of your PATH statement may be truncated if it
contains too many elements.
c. Deletes the following line (if it exists) from CONFIG.SYS:
device=c:\mouse.sys
For the mouse driver in Windows, Setup makes the following changes:
a. Adds the following line to the load line in WIN.INI:
[windows] section c:\mouse\pointer.exe
b. Modifies the following lines in SYSTEM.INI:
[boot] section mouse.drv=c:\mouse\mouse.drv
[boot.description] section mouse.drv=Microsoft Mouse version 9.01
[386enh] section keyboard=c:\mouse\mousevkd.386
c. Adds a group to PROGMAN.INI:
groupn=c:\mouse\mouse.grp
(where n = group number and \mouse=mouse directory)
d. Setup updates to the latest CTL3D.DLL file to the Windows System
directory (if it's not already there).
e. If you have Microsoft Windows version 3.0, Setup installs WINHELP.EXE.
2. Returning Your System to Pre-Setup Condition
To return your system to its previous condition before you
ran the mouse Setup program, make the following modifications:
a. Remove the following line from WIN.INI:
c:\mouse\pointer.exe
b. Change the following lines in SYSTEM.INI to read:
[boot] section mouse.drv=mouse.drv
[boot.description] section mouse.drv=Microsoft, or IBM PS/2
[386enh] section keyboard=*vkd
3. Setting up with a Floppy Disk System
Setup supports only hard disk systems and floppy disk systems
with two drives. If you are installing files onto a floppy disk
system that has only one drive, you must decompress and copy the
files manually. EXPAND.EXE, a file-decompression program, is
provided on the Setup disk for this purpose.
To install using a single-drive floppy disk system:
a. Insert the Setup disk into drive A and type:
expand mouse.ex$ b:mouse.exe
b. When prompted by MS-DOS, remove the Setup disk and insert
your destination disk.
c. Reinsert the Setup disk in the drive and type:
expand mousemgr.ex$ b:mousemgr.exe
d. When prompted by MS-DOS, remove the Setup disk and
insert your destination disk.
To load your mouse driver, type:
mouse
Run Mouse Manager to set pointer options, if desired.
To run Mouse Manager, type:
mousemgr
If you install the software using a dual floppy disk system,
set up the mouse software from drive b to drive a.
4. Loading MOUSE.EXE into Upper Memory
The MS-DOS mouse driver automatically loads itself into
upper memory, if available. Using the MS-DOS loadhigh command
may cause your mouse software to load into low memory.
5. The SHARE.EXE File and Multidisk Setup
For multidisk Setup (360 KB or 720 KB disks) only:
Do not load the SHARE.EXE file (included with MS-DOS) before
you run the mouse Setup program. If SHARE.EXE exists in
your AUTOEXEC.BAT, it must be removed before running
the mouse Setup program. After mouse Setup is complete,
you can reinstall SHARE.EXE.
6. Reinstalling Your Virtual Keyboard Driver
If you received a message at the end of Setup similar to the one below:
Setup replaced your Virtual Keyboard Driver
you may wish to reinstall your Virtual Keyboard Driver if you are
experiencing problems with your mouse. To do this, change the following
line in the SYSTEM.INI file to read:
[386enh] section keyboard = c:\N.VKD
Where N is the path and name of your VKD. The location and name of your
former VKD is displayed in the message box at the end of Setup.
_________________________________________________________________
III. THE MOUSEPWR FEATURE
Some laptop computers have the capability to go into a sleep mode
to conserve power when not being used. Load the MOUSEPWR feature if
your mouse becomes erratic after you resume from sleep mode. MOUSEPWR
restores pre-sleep mode settings of the mouse when you resume
work on the laptop.
It's not necessary to use MOUSEPWR if your system has Advanced
Power Management (APM). However, this feature requires very
little memory (592 bytes) and won't conflict with APM if both
are loaded on your system.
The MOUSEPWR feature is not automatically copied during the
mouse Setup program. Use the MS-DOS copy command to load
MOUSEPWR.COM to your system. The MOUSEPWR feature must
be loaded at the MS-DOS prompt only (not in Windows). If
you need to load MOUSEPWR to your system, add it to your
AUTOEXEC.BAT file so that it loads each time you turn your
system on. For example, if MOUSEPWR is in the root directory,
add the following line to your AUTOEXEC.BAT file:
c:\mousepwr.com
Otherwise, you'll need to load MOUSEPWR manually each time you
want to use it. Type the following line at the MS-DOS prompt
to load the MOUSEPWR feature manually:
\mouse\mousepwr.com
where 'mouse' is the directory containing the MOUSEPWR.COM file.
____________________________________________________________________
IV. MICROSOFT WINDOWS NT SUPPORT FOR YOUR MOUSE
Microsoft Windows NT will have Microsoft mouse drivers included.
For additional mouse support for Microsoft Windows NT, contact
Microsoft Customer Service upon release of Microsoft Windows NT.
Inside the U.S.A., call 1-800-426-9400. Outside the U.S.A.,
please contact your subsidiary.
____________________________________________________________________
V. MEET THE MOUSE
Meet the Mouse is a short, animated demonstration that is
available for viewing when you run the mouse Setup program.
You can also watch Meet the Mouse from Mouse Manager. Meet
the Mouse takes approximately two minutes to run if you have
the minimum required configuration set up for Microsoft Windows.
Meet the Mouse may run slower if you have less than the required
configuration, or if you have a 24-bit graphics card.
To save disk space, you can remove this demonstration by deleting
the ERGODEMO.DLL file from the directory that contains your
mouse software.
____________________________________________________________________
VI. NOTES ON MOUSE MANAGER FEATURES
1. MS-DOS and Windows Features
When you choose Set Buttons, Overall Pointer Speed, Acceleration,
and Orientation from Mouse Manager in Windows, the changes
do not affect the MS-DOS driver until you reboot your computer.
However, if you set these features from the Mouse Manager in
MS-DOS, the changes affect both MS-DOS and Windows.
2. Magnify
Once you activate Magnify with the keyboard key and mouse,
release the key and mouse button. Click any mouse button
to return your pointer to normal.
If you move the magnified pointer quickly in highly graphical
applications, it may take a few seconds for the screen to fully
redraw.
You cannot use the Magnify feature on pull-down menus because
the activating keystroke causes the pull-down menu to close. This
also applies to other items that are deactivated by a single
keystroke.
3. Screen Wrap
Screen Wrap cannot move off the edge of the screen while
Microsoft Windows is busy (for example, while the pointer
is an hour glass).
4. Snap-to
If Snap-to does not work in some dialog boxes, it is because
the default buttons in these dialog boxes do not adhere to the
standard Microsoft Windows user interface specifications.
5. Mouse Trails
You can not adjust the length of Mouse Trails for Paletized
video drivers through Mouse Manager.
_____________________________________________________________________
VIII. OTHER ISSUES
1. MS-DOS Support for the IBM XGA Video Card
A file called XGA.VDM is on your Mouse Setup disk, but is not
automatically copied during Setup. You need to copy this file
to your mouse directory only if you have an IBM XGA card in your
system. This file will give you MS-DOS support for your XGA card.
2. Hot Keys on LCD Screens
On some LCD screens some of the hot keys do not show up or are
not highlighted.
3. Large and Medium Pointers
When using a large or medium sized pointer, some MS-DOS
applications may not redraw the pointer correctly, resulting
in "mouse droppings."
When using a large or medium sized pointer, some applications
for Windows may not enlarge the pointer correctly.
4. Windows 3.0 Support
Setup does not update Mouse Manager in the Windows Control
Panel, version 3.0. But Setup still creates a mouse
program group which contains Mouse Manager.
There is no support for the mouse driver in an MS-DOS windowed
application within Windows 3.0. To get mouse support, run your
MS-DOS application full screen within Windows (ALT + ENTER switches
between a window and full screen).
5. Exiting from Microsoft Windows with a Serial Mouse
If you find that exiting from Microsoft Windows is slow with your
serial mouse, try modifying the following line in the SYSTEM.INI file
to read:
[386enh] section keyboard = *VKD
___________________________________________________________________
VIII. MORE ERGONOMIC INFORMATION
Personalizing your environment so that it is comfortable for your work
situation promotes a healthy physical and mental lifestyle. Studies
show that a carefully planned work environment can actually increase
productivity. Of course, only you can judge whatÆs best for you, so
we encourage you to adapt these tips to your own needs.
Exercises
Exercise and frequent breaks play an important part in staying alert
and comfortable on the job. Take periodic breaks to rest your eyes,
move your body, and get your circulation flowing. Try some of the
following exercises several times during the day.
Gently press your hands against a table, stretch, and hold for five
seconds. Stretch and massage your fingers, hands, wrists, and forearms
throughout the day. Gently shake your hands and fingers to relieve
tension and help blood flow. Rotate your shoulders in a full forward
circle four times. Then roll them backward four times. Then rotate
each shoulder separately four times. Do this at least twice daily.
Organize your work so that you alternate using your computer with
other activities. Try to use different muscle groups throughout the
day. Get up and walk around several times a day.
Note: If you experience pain while using your computer, consult a
qualified health professional.
Chair and Desk
A chair that is adjustable in height is a good place to start. It
should be comfortable and provide firm support to the lower back
(lumbar region). Adjust the chair so that your forearms form
approximate right angles with your upper arms and so that your
feet rest flat on the floor. If your feet donÆt rest flat on the
floor, use a footrest that is high enough so that your thighs
are about parallel to the floor while youÆre seated.
If at all possible, place your system on a desk designed for a
computer. Traditional writing desks are sometimes too high for
computer use. A proper height between your chair and your desk
is essential. And donÆt forget good posture -- slouching puts
unnecessary strain on your back and weakens muscles.
Display and Lighting
Place the display screen directly in front of you at a comfortable
viewing distance. Sit in your chair and make sure that the top of
the display is no higher than eye level. Make sure you canÆt see
glare and bright reflections on the screen (anti-glare filters help)
or on your mouse, and keep your screen clean and dust free.
ItÆs important to look away from your display frequently. Several
times every hour, focus on an object about 20 feet away and slowly
inhale through your nose and exhale through your mouth.
Keyboard and Mouse
Position the keyboard directly in front of you on the desk. While
youÆre typing and using the mouse, keep your shoulders relaxed and
let your upper arms hang freely at your sides. Let your elbows hang
loosely near your body and allow enough room on your desk for
unhindered movement of the mouse. Your forearms should be nearly
parallel and at approximate right angles to the floor as you type
and use the mouse.
Position the mouse at the same height as your keyboard. If you can,
try to avoid light sources that can reflect on the surfaces of your
mouse and keyboard. Use your entire arm to move the mouse around
on your desktop whenever possible. The Microsoft Mouse is designed
so that you can rest your hand on it whenever possible, and so that
you donÆt have to grip it unusually hard when using it. Avoid
excessive tension in your hand by relaxing -- donÆt pinch the
mouse too hard.
The high-performance level of the Microsoft Mouse makes it
unnecessary to use a mouse pad. However, if you do use a mouse
pad, make sure it is not so thick that it raises your arm and
the mouse. Your arm should maintain an approximate right angle
to the horizontal table top. The mouse pad should provide smooth
friction for ease of use -- it should not be too slippery. It
should also be lint free so the mouse ball doesnÆt get dirty.
The design of the Microsoft Mouse accommodates a wide variety
of grips and lets you use the mouse in either hand. The mouse
allows for several possible work positions, which can help you
avoid unnecessary strain on your arms and hands. By periodically
varying the way you hold the mouse, you donÆt repeat the same
motion over a long period of time. The software that comes with
the Microsoft Mouse (Mouse Manager) supports the mouse design
by letting you customize the software for variable work positions.
ItÆs a good idea to periodically readjust your software as you get
better acquainted with your mouse.
_________________________________________________________________
Carbon Copy for Windows Version 2.0
README.TXT
USING NOTEPAD TO VIEW ON-LINE DOCUMENTS
=======================================
* If you are currently setting up Carbon Copy for Windows,
choose Exit from the Notepad File menu to continue with
Setup.
* You can enlarge Notepad to its maximum size to make this
document easier to read. To do so, click the Maximize button
in the upper-right corner of the Notepad window, or open the
Control menu in the upper-left corner of the Notepad window
and choose Maximize.
* To move through the document, press PAGE UP and PAGE DOWN or
click the arrows at the top and bottom of the scroll bar
along the right side of the Notepad window.
* To print the document, choose Print from the Notepad File
menu.
* For Help using Notepad, press F1.
NOTES ON CARBON COPY FOR WINDOWS
================================
This document contains important information about Carbon
Copy for Windows including the following topics:
* Copying files from the Carbon Copy for Windows disks
* Information not found in the User Guide
* Using the SETCOM Utility (using COM3 or COM4)
* Files included on the diskettes
COPYING FILES FROM THE CARBON COPY FOR WINDOWS DISKS
====================================================
The files on the Carbon Copy for Windows installation disks are
compressed. The files are not usable until they are expanded.
Setup expands the compressed files as they are copied onto your
hard disk.
If you need to copy files directly from a Carbon Copy for Windows
disk without using Setup, follow these steps:
1. Copy EXPAND.EXE (located in the \INSTALL directory) from the
Carbon Copy Setup Disk onto your hard drive. (This utility
expands compressed files to a useable format.)
2. Insert the disk with the file you want to expand into drive
A: (or any floppy-disk drive).
3. Type the following and press ENTER:
EXPAND /R x:<filename> y:<filename>
where x: is the disk drive you are copying from (source)
y: is the disk drive you are copying to (destination)
The compressed file is expanded as it is copied onto your
hard-disk drive.
INFORMATION NOT FOUND IN THE USER GUIDE
=======================================
Using Carbon Copy with Novell NetWare
-------------------------------------
The following versions of Novell NetWare components
are recommended for proper operation when using the
Carbon Copy LAN (IPX) driver:
Windows Components
------------------
NETWARE.DRV: v2.02 (021026)
NWIPXSPX.DLL: v1.32
NWPOPUP.EXE: v2.02 (021027)
VIPX.386: v1.13 (920903)
VNETWARE.386: v1.06 (921015)
DOS Components
--------------
EMSNETX.EXE: v3.31 (921112)
IPXODI.COM: v2.00 (920904)
LSL.COM: v2.00 (920904)
NETX.EXE: v3.31 (921112)
TBMI2.COM: v2.10 (911204)
XMSNETX.EXE: v3.31 (921112)
It is especially important to update to Novell's
VIPX.386 version 1.13 or later. The version that
ships with Windows 3.1 will not work properly.
These files are available on CompuServe in the Novell
forum as WINUP7.ZIP and DOSUP6.ZIP.
Using Carbon Copy with 3COM 3C505 LAN Adapter Cards
---------------------------------------------------
The 3COM 3C505 LAN Adapter card does not work properly
with Microsoft Windows in enhanced mode. 3COM is working
on new drivers that will correct this problem. Contact
3COM technical support at (800) 876-3266 for more
information.
Disabling the Host Video on 256-color Cards
-------------------------------------------
Carbon Copy may not be able to disable the video on
some 256-color cards. Changing to a 16-color driver
will usually correct this.
Display Drivers
---------------
The Windows display drivers not directly supported by Carbon
Copy for Windows include the following:
Olivetti/AT&T monochrome or PVC display
Quad VGA
82c441 VGA
Diamond Steath VRAM 1280 16-color Mode
--------------------------------------
The Diamond Stealth card will not work with Carbon Copy
in this mode, but it will work with other modes such as
1024x768 16 or 256-color modes.
XGA 16-color, HP 16-color SVGA
------------------------------
These cards do not work with Carbon Copy in 16-color
mode using their native drivers. However, they will
work fine using the Windows standard VGA driver. The
XGA and HP cards also work correctly with native
drivers using any of their 256-color modes.
ATI Ultra "Crystal Font" Driver
-------------------------------
The ATI Ultra "Crystal Font" driver does not work properly
with Carbon Copy, however, all other ATI Ultra drivers work
fine, including 1024x768 and 256-color drivers. If you are
using this driver, you should use the Windows Setup program
to select another Ultra driver, and then reinstall Carbon
Copy.
Using Alt+Tab to Switch Windows during Remote Control
-----------------------------------------------------
Using Alt+Tab to select a active window from a full-
screen DOS session in remote control will not display
the selected banner on the Guest machine. However,
the switch still occurs properly, and the new
application will be displayed as soon as the keys are
released.
Using Windows 386 Enhanced Mode "Exclusive in Foreground" Option
----------------------------------------------------------------
Setting this option in a PIF file will interfere with
Carbon Copy's ability to remote control the application.
Do not set this option for applications you wish to remote
control.
Network Warning Messages During Windows Startup
-----------------------------------------------
Carbon Copy is not able to display Network Warning messages
during Windows startup. In order to prevent problems with
remote control, we recommend disabling these messages using
the Network option in Windows Control Panel. If these
messages are not disabled, you will not be able to view
the Host screen until the dialog box is removed. However,
the keyboard is still active and pressing <Enter> will
remove the warning message.
"Host is in an unsupported video mode" Message
----------------------------------------------
Depending on the Host and Guest video hardware, if you
switch from full screen DOS from the Guest while in Remote
Control, you may get the message "Host is in an unsupported
video mode". This occurs only when Windows is running in
a Super-VGA mode. The message will disappear as soon as
the switch to Windows is complete, and does not indicate a
problem.
Using Window's Standard Mode with the LAN (IPX) Driver
------------------------------------------------------
The TBMI2.COM (TBMI.COM for Windows 3.0a) utility must
be loaded before Windows can be run in standard mode
using the network. If you get a "Communication driver
is not installed." message, make sure that this utility
is loaded before you start Windows.
DOS version 5.0 is recommended on 80286-based machines if
the LAN (IPX) driver is used for Host operation and DOSHOST
is loaded. The CONFIG.SYS file should contain the line:
DOS=HIGH
Other versions of DOS may work if you have a utility such
as QRAM, allowing at least 500K of free memory at the DOS
prompt after loading DOSHOST.
Increasing Performance on 80286-based PCs
-----------------------------------------
Most 80286-based machines running at 12-MHz or slower will
give better performance if the port speed is set at 9600 baud
or lower. Using port speeds greater than 9600 baud may
actually decrease throughput on these machines due to more
frequent retransmissions.
If you are running Windows version 3.1, you may use the
FasterModeSwitch=1 option in the [standard] section of
your Windows SYSTEM.INI file. Enabling this setting causes
Windows running in standard mode to use a faster method of
switching from protected to real mode on many 80286-based
computers. When this setting is enabled, Windows responds
quicker to hardware interrupts, screen updates, and improves
file transfer speeds. NOTE: This setting has no effect on
80386-based computers. Some early IBM AT and compatible
computers do not support this setting. Enabling this setting
on these 80286-based machines may cause them to lock up when
starting Windows.
Increasing Performance on 80386sx-based PCs
-------------------------------------------
For best performance on 80386sx-based machines, we recommend
running Carbon Copy for Windows in standard mode.
As with all Windows applications, running Carbon Copy on any
PC in standard mode will improve performance over enhanced
mode on the same machine.
Enhancing Mouse Performance
---------------------------
When using Carbon Copy for Windows with modems that connect
at 2400 baud, mouse performance can be enhanced by changing
the QuickMouse parameter in CCW.INI as follows:
QuickMouse=5
This change must be made directly using a text editor.
(CCW.INI is located in your WINDOWS directory.) The default
setting of QuickMouse=2 is best for modems that connect at
baud rates of 9600 or higher.
When using modems that have asymmetrical modulation schemes,
the transmit and receive channels may operate at vastly
different speeds. An example of such a modem is the US
Robotics Courier HST. For these modems, you may want to set
QuickMouse as high as 10 for best performance.
You may also notice better performance by setting QuickMouse
to a higher value on noisy phone lines.
Disconnecting with the "Exit Windows" Dialog Displayed
------------------------------------------------------
Because of a limitation within Microsoft Windows, you should
not disconnect from a Host machine while the "Exit Windows"
dialog is displayed. If you do, you may not be able to
reconnect to the Host system until someone at the host
machine responds to the dialog box.
Changing the Communications Options
-----------------------------------
If you change any of the options on the Communications menu
(i.e. change drivers, WorkStation Name, Port, etc.) while
DOSHOST is loaded, you should unload and reload the DOSHOST
program. Some of the options do not take effect in DOSHOST
until this is done.
Using the Virtual Desktop Feature
---------------------------------
The Virtual Desktop feature mentioned in the User Guide
is not available if the Host PC is running Windows 3.0a.
The Host PC must be running Windows 3.1 to use this
feature.
Running Setup with Limited Disk Space
-------------------------------------
Setup requires a minimum of 4Mb of disk space plus 2Mb of
temporary workspace to install the complete Carbon Copy
for Windows product. If your disk space is limited to
less than this amount, and you have a previously installed
version of Carbon Copy for Windows on your hard disk, you
may want to delete it so you have enough space to reinstall
the product.
Using Carbon Copy along with CPU Intensive Applications
-------------------------------------------------------
When using Carbon Copy's File Transfer utility along with
CPU intensive applications (mostly benchmark programs),
File Transfer may sometimes display the message "General
Failure". This means that File Transfer is not receiving
enough CPU time to do its work. If this happens, simply
close the application that is causing the problem and try
the transfer again.
If you have trouble connecting to a machine that is running
this type of program, you may want to try terminating the
application before attempting a connection.
Changing the Mouse Settings during Remote Control
-------------------------------------------------
If you change the mouse settings in the Windows Control Panel
during a remote control session, the Guest's mouse may
temporarily be out of synchronization with the Host mouse.
If this happens, simply use the keyboard to choose the OK
button in the Mouse Settings dialog, and the mouse will
return to normal.
Note that there is very little reason to change the mouse
settings on the Host in this way. Mouse performance is
mostly affected by the Guest's mouse settings.
HP Intellifont Drivers
----------------------
The HP Intellifont display driver (IFW.DRV) is incompatible
with Carbon Copy for Windows. You should remove this driver
from your SYSTEM.INI in order to use Carbon Copy.
Communications Port Not Found Message
-------------------------------------
If you get a "Communications port not found." message from
Carbon Copy, you may want to check the "Custom" settings in
the Port Settings dialog box to make sure they are correct.
The settings installed by using the "Default" pushbutton are
usually correct for most systems.
Using Carbon Copy with Asynchronous Communications Servers (ACS)
================================================================
See ACS.TXT for application notes regarding the use of
Carbon Copy with NCSI/NASI and EBIOS/INT14-based ACS
products.
USING THE SETCOM UTILITY (USING COM3 OR COM4)
=============================================
In many systems, Windows will not recognize serial ports
COM3 and COM4. See SETCOM.TXT for information about the
SETCOM utility and solutions to this problem.
FILES INCLUDED ON THE DISKETTES
===============================
See FILELIST.TXT for a list of files included on the
diskettes.
End of File
NFormat v1.1. A Dynamic Floppy Disk Formatter. Allows you to Format 1.7M on a 1.44M disk and 1.5M on a 1.2M disk. Also Has superior error detection, and a user friendly menu system. (Also has mouse support!)
IF YOU HAVEN'T UNPACKED THIS ARCHIVE WITH PKUNZIP /D, DELETE ALL FILES EXCEPT FDFORM18.ZIP AND TRY AGAIN WITH PKUNZIP /D. The following files should be included in the archive: AUXDOS.PAS - Supplemental DOS Routines in TP 6.0 AUXDOS.TPU - Compiled Unit of AUXDOS.PAS BASECONV.PAS - Number Base Conversion in TP 6.0 BASECONV.TPU - Compiled Unit of BASECONV.PAS CPUTEST.ASM - Test for the CPU-Type in Assembler DESQVIEW.PAS - Desqview aware routines DESQVIEW.TPU - Compiled Unit of DESQVIEW.PAS DISKIO.PAS - low-level disk I/O routines in TP 6.0 DISKIO.TPU - Compiled Unit of DISKIO.PAS FDBOOT.001 - TP 6.0 readable File of FDBOOT.SYS in English FDBOOT.049 - TP 6.0 readable File of FDBOOT.SYS in German FDBOOT.ASM - Source of FDBOOT FDBOOT.SYS - Binary File of FDBOOT FDFORMAT.DOC - Documentation of FDFORMAT FDFORMAT.EXE - Executable FDFORMAT in English FDFORMAT.NEW - What's new FDFORMAT.PAS - TP 6.0 source of FDFORMAT FDR88.EXE - XT version of TSR-disk-driver FDREAD.ASM - Source of FDREAD/FDR88 FDREAD.EXE - AT version of TSR-disk-driver GERMAN/FDFORMAT.EXE - Executable FDFORMAT in German GETBOOT.EXE - Make FDBOOT.001/049 from FDBOOT.SYS GETBOOT.PAS - Source in TP 6.0 of GETBOOT MAKEFILE - Makefile for FDFORMAT READBOOT.EXE - Read/Write Boot-Sector from/to file READBOOT.PAS - Source in TP 6.0 of READBOOT README.1ST - This file WIMAGE.EXE - Diskcopies to/from file WIMAGE.PAS - Source of WIMAGE in TP 6.0
FORMATMASTER ......please register your shareware!
----------------------------------------------------------------------------
Requirements: Any PC
Directory installed to: C:\FORMAT
To run, at the Dos prompt, type: C:
CD \FORMAT
FMTMAS
----------------------------------------------------------------------------
FormatMaster is a full-featured floppy diskette format utility. It achieves
its utility through a menu driven interface and provides the means to easily
and quickly format 5.25in (360k/1.2Mb) or 3.5in (720k/1.4Mb) diskettes. In
addition, it will transfer system files to a freshly formatted disk and add
a user provided volume label. Formatting speed is twice that of the normal
Dos format utility.
In addition to all this, on many PCs (but not all), it will format low
density 5.25in disks that normally have a capacity of 360k to 800k in a high
density drive! Recycle all your old low density floppies!
NOTE: If the 800k option does not work properly on your system, place the
statement SET FMSEC=9 in your AUTOEXEC.BAT file and reboot your system. If
FormatMaster finds FMSEC=9 the Main Menu will show "700k Format" instead.
This should now work on your PC.
Virus SCAN v117 for DOS Official Release from McAfee dated on 15/7/94. (YO!Net)
Central Point Anti-Virus for DOS Version 2.0
This file contains information that is not in the manual or has changed
since the manual was printed. Please take a moment to read it.
SIGNATURE UPDATES AND OTHER CENTRAL POINT PROGRAMS
Signature updates improve the virus-detection capability of other
Central Point Software programs that have virus-detection features
(Central Point Backup, DiskFix, and Commute). However, the virus
signatures used by Central Point Anti-Virus Version 2.0 are not
compatible with these Central Point programs. Signatures using the
previous format will still be available on CompuServe and Central Point
Software's BBS.
INSTALL OPTIONS
After you perform the initial installation, you can complete the
following procedures from the directory where Install is located (by
default, C:\CPAV) on your hard disk drive:
* Creating an emergency disk
* Changing Anti-Virus options
* Creating a custom installation or installation set
USING STACKER AND MAKING AN EMERGENCY DISK
When you make an emergency disk, you might get a message that the
process cannot be completed. If so, Install detected that you have
Stacker loaded and are swapping drive designators. When you make an
emergency disk under these circumstances, the boot area of the hard
disk drive is swapped. However, when you boot your computer from your
emergency disk, you need one that boots without loading Stacker and
swapping drives. To create one, follow these steps:
1. Create a formatted, bootable floppy disk in drive A.
Type
FORMAT A: /S and press Enter
2. Copy BOOTSAFE.EXE to the floppy disk.
Change to the C:\CPAV directory and type
COPY BOOTSAFE.EXE A:
3. Restart your computer and boot from the floppy disk in
drive A.
4. From drive A, type
BOOTSAFE C: /M
5. Choose Yes to save an image of the partition table to the floppy
disk in drive A.
6. Write-protect the floppy disk, place a label on it, and store it
in a safe place.
SCHEDULING ANTI-VIRUS SCANS
If you manually install the scheduler TSR (CPSCHED.EXE), make sure you
add the full path to the program (C:\CPAV\CPSCHED) and that you run it
from the same directory as the SCHEDULE.EXE program. If you have
Install add CPSCHED to your AUTOEXEC.BAT file for you, this has been
done.
PC Tools for DOS Users
To schedule Central Point Anti-Virus 2.0 scans along with your other PC
Tools events, delete the CPSCHED.EXE and SCHEDULE.EXE files from the
CPAV directory. Then start Scheduler from the PC Tools directory and
add the full path to Central Point Anti-Virus 2.0 in the Event text box
(C:\CPAV\CPAV.EXE). Edit your AUTOEXEC.BAT file and change the CPSCHED
line to include the full path to the PCTOOLS directory
(C:\PCTOOLS\CPSCHED).
PC Tools for Windows Users
To schedule Central Point Anti-Virus 2.0 events using Scheduler in PC
Tools for Windows, follow the instructions for importing a file found
in the Scheduler chapter of the PC Tools for Windows manual.
SCANNING NETWORK SERVERS
When scanning a network server from the command line (using /N or /P),
you get no visual indicator when the program is mapping the directory
structure and it may appear locked. Since network drives tend to be
large, they take longer to process.
COMPATIBILITY NOTES
Packard Bell Mouse Users
The Packard Bell mouse driver version 4.0 is not fully compatible with
the Microsoft mouse driver (version 6.14 or later). Use the Microsoft
mouse driver (often provided with Windows) with this mouse.
Speedstar 24X Video Board Users
The 24XMODE.COM file changes each time it is executed. To prevent
verification alerts each time the driver is run, add this file to your
Verification Exceptions list.
Disk-Compression Software
When scanning drives that have been compressed with the
disk-compression utility SuperStor from AddStor, turn off the
Anti-Stealth option. On such compressed volumes, files are compressed
and decompressed dynamically, which results in their checksums not
matching. You may get unreliable verification errors.
DOS 6 DoubleSpace Users
To make a Central Point Anti-Virus emergency disk, you must first
create a bootable, formatted floppy disk, and then create a CONFIG.SYS
file on the emergency disk that contains the following statement:
SHELL=A:\COMMAND.COM
QEMM or 386MAX
Some problems have been detected when loading VSafe and using the
SQUEEZE option in QEMM or the FLEXFRAME option in 386MAX. For best
results, do not use either of these options if you are loading VSafe.
If Install detects that you are using QEMM, it adds the /L option to
VSAfe or VWatch, which forces them to use conventional memory instead
of automatically loading into upper memory blocks (UMBs). If you want
to use UMBs after installing VSafe or VWatch, remove the /L option
before optimizing memory with QEMM.
If you get the message "386MAX VxD error V1014: Disk Cache or other
file IO software using EMS memory" when using VSafe with 386MAX, load
VSafe using the /NE option.
VSafe and Other TSRs
If you have VSafe loaded with the Resident Warning option (2) on, you
might receive an error when another memory-resident program loads. If
you choose Stop, the system might lock. Choose Continue to complete the
startup process, then edit your AUTOEXEC.BAT file and turn off the
Resident Warning option (2-).
Generally, the only reason for not using the VSafe default options is
if you think your system might be infected with a virus. If this is the
case, boot your system from your write-protected emergency disk. Follow
the instructions in the manual for using the emergency disk.
VSafe and DESQview
VSafe does not display a warning when you are running a DOS program in
graphics mode (such as DESQview); instead, an alarm sounds and the
action stops. Exit from the program and run Central Point Anti-Virus to
verify the integrity of files.
DOS Shell Users
If you are using the DOS Shell program in graphics mode when a
scheduled Anti-Virus scan begins, the screen fonts will not be drawn
correctly. When you return to the DOS Shell, choose Repaint Screen from
the View menu to redraw the display. To run Central Point Anti-Virus
from the DOS Shell without this problem, run the DOS Shell in text
mode.
Banyan Vines Network Users
If you want to use VSafe on Banyan Vines network workstations, load
VSafe after the network drivers.
计算机病毒清除工具
ＫＩＬＬ V64
使用说明书
概 述
计算机病毒清除工具KILL系根椐已知的各种微机病毒
结构和工作机理而设计的专用程序，主要用于清除病毒，
对已感染病毒的系统和程序文件进行检测和可靠的恢复。
KILL的开发是建立在对病毒详细剖析的基础上。KILL
的知识库存有每一种病毒的具体结构和突出特征，因此可
以准确地指出所感染病毒的名称及其位置，对被感染系统
和文件进行可靠的恢复。当用户系统或文件被病毒感染后，
由于没有备份而不能放弃时，使用KILL是用户的最佳选择。
KILL可以处理目前在国内已经出现的各类病毒，特别
是各类国产病毒及其变种。
考虑到广大普通微机操作人员的技术水平，KILL在设
计上尽可能减少对用户的使用要求，对各种复杂情况的判
定和处理均由KILL自动完成，并在屏幕上给出清淅明了的
说明，不需用户对病毒有任何了解。任何人均可于几分钟
内学会使用。
KILL具有良好的软硬件兼容性，可在各种兼容机上运
行。
KILL目前只限在DOS环境下使用。
使用说明
KILL必须在干净无毒的系统环境下才能可靠运行。因
此，用户在使用本软件前，必须用本盘或其它版本的干净
无毒 DOS盘启动系统。
系统启动后，将本盘插入Ａ或Ｂ软盘驱动器，输入命
令：KILL [驱动器号][路径名][文件名]
方括号中各项内容可根据用户要处理的盘号、路径及
文件名填入，可以只输入盘号，KILL则对指定盘进行处理。
可以填入盘号和路径，此时只处理指定的路径。也可输入
文件名，KILL只对这个文件进行处理。
例如：
KILL C: 或 A: 或 B:
KILL C:\DOS
KILL C:\TC\LIB
KILL C:\XSDOS\WPS.EXE
若用户只输入文件名，则默认当前驱动器和当前目录。
例如：
KILL FILENAME.EXE
若只输入:
KILL
则对整个当前盘进行处理。
KILL开始运行时若显示提示:FIND VIRUS IN MEMORY，
REBOOT SYSTEM 则说明系统已被病毒感染，可用本盘或其
它干净DOS盘重新启动一次。
软件运行后，主屏幕上会有 6个可选项，可使用功能
键←和→进行选择。
SCAN项：KILL只检查病毒是否存在，若发现病毒，屏
幕会显示被感染的文件名及病毒种类，不做任何处理。
CLEAN项：KILL将对病毒进行清除,屏幕会显示被清除
的病毒种类和被感染的文件名。
DRIVE 项：用户可用此项功能随时改变原来指定的驱
动器号或目录或文件名，而不必退出KILL 重新加载。 用
RETURN键选中此项后，屏幕上会出现一个小窗口，此时可
输入新的驱动器号或目录或文件名，与KILL加载时命令行
参数的格式要求相同。如：
C:
C:\DOS
C:\XSDOS\WPS.EXE
内容输入后，显示小窗口消失，即可进行其它操作。
QUIT项：选中此项时，程序将结束运行，正常退出。
另外二项功能为软件常驻与辅助分析工具，此二项功
能暂不向用户提供。
KILL运行过程中可随时用功能键ESC 中止运行或强行
退出。
屏幕在运行过程中会不断显示发现的病毒种类数和已
检查处理过的文件个数。
关于KILL本身加密情况的说明
1)KILL.EXE是加密后的程序，该程序所在软盘为" 密
钥盘"
2)该程序可拷贝至其它盘中(如: C、D)执行，但必
须将该“密钥盘”插入 A 或B 驱动器。
3)若不插入“密钥盘”，运行KILL时会引起系统死机，
须重新启动方可再次运行。
4)各“密钥盘”可以通用。
注：清病毒时，若用户用自己的DOS启动系统并且CONFIG
.SYS中要求扩展内存管理，则可能与软件有冲突, 此时可
去掉CONFIG.SYS文件，重新启动即可。
本磁盘使用前应贴封写保护。
如用户发现新病毒不能解决，可向我公司联系获取新
版清除工具。
联系地址： 北京市东长安街14号
邮 编: 100741
电 话: 5122831-3588
中国金辰安全技术公司
QUICK START INSTRUCTIONS FOR McAFEE ASSOCIATES PROGRAMS
Last revised February 15, 1994.
Copyright 1990-1992 by McAfee Associates.
All rights reserved.
McAfee Associates (408) 988-3832 Telephone
2710 Walsh Avenue, Suite 200 (408) 970-9727 FAX
Santa Clara, CA 95051-0963 (408) 988-4004 BBS
USA CompuServe GO MCAFEE
Internet support@mcafee.com
QUICK START Page 1
These instructions explain how to identify a virus with the
VIRUSCAN program and remove the virus with the CLEAN-UP program.
They are intended to provide an emergency means to identify and
remove an infection. They are not meant to replace the program
documentation. Please read through the documentation for
detailed instructions.
Files ending in a .DOC extension have been formatted for
printing on a printer with a minimum of 55 lines per page.
Files ending in a .TXT extension have not been formatted.
VIRUSCAN (SCAN)
1. Copy all the VIRUSCAN files to a floppy disk in drive A:.
2. WRITE PROTECT THE DISK!!!
3. Turn computer off to remove the virus from memory, insert a
clean (virus-free) DOS system boot disk into the A: drive,
and turn the power back on.
4. Insert the VIRUSCAN disk into the infected PC and type:
SCAN C: D: E:
This will allow VIRUSCAN to scan the C:, D:, and E: drives.
If you do not have D: and E: drives, leave them out.
NOTE: If infected files are found, they may be ERASED by
running SCAN with the /D (overwrite and delete)
option:
SCAN C: D: E: /D
Running SCAN with the /D option will delete files so they
can not be recovered. Use this option only if you do NOT
want to recover any infected files. Otherwise use CLEAN-UP,
the universal virus disinfection program.
4. Copy SCAN.EXE to the hard disk and run it from there against
any floppies you suspect have the virus on them.
QUICK START Page 2
CLEAN-UP (CLEAN)
1. Copy all the CLEAN-UP files to a floppy disk in drive A:.
2. WRITE PROTECT THE DISK!!!
3. Power down the infected system and then boot from a clean,
write protected system master diskette. This must be done
to remove any viruses from memory that may interfere with the
virus removal process.
NOTE: If you are unable to access the hard disk after booting
from a floppy, check to make sure that any special
device drivers needed to use the hard disk are on the
floppy and loaded from the CONFIG.SYS or AUTOEXEC.BAT
file. Check to make sure the version of DOS is the
same version as on the hard disk (or a later version).
4. AT THIS POINT IF YOU HAVE NOT DONE A BACKUP OF ANY CRITICAL
FILES ON YOUR SYSTEM, THEN DO SO IMMEDIATELY.
5. Insert the CLEAN-UP disk into the floppy drive of the
infected PC and type:
CLEAN C: D: E: [virus I.D. code]
This will allow CLEAN-UP to disinfect viruses on the C:, D:,
and E: drives. If you do not have D: and E: drives, leave them
out.
For the Jerusalem virus, the ID code is [JERU]. For the
Stoned virus, the ID code is [STONED]. For other viruses,
use the ID code reported by SCAN, or refer to the
VIRLIST.TXT file. Be sure to include the square brackets,
"[" and "]."
If you are disinfecting a file-infecting virus, such as the
Jerusalem, it is recommended that you add the /A switch to the
command line to check all files. This will ensure that the virus
is removed from any overlay files that may not use the default
overlay extensions recognized by CLEAN-UP.
If more than one virus type was detected, then CLEAN-UP will
have to be run for each type of virus.
5. Turn the computer off and then re-boot from the hard disk,
run SCAN to confirm that the virus has been removed, copy
CLEAN.EXE to the hard disk, and check any floppies that may
have been infected by the virus.
QUICK START Page 3
AN IMPORTANT NOTE
You have now completed a virus disinfection of your computer
system, however, you may have other computers and floppy disks
that are infected. You now have a clean PC from which to
scan and clean them. Please now take the time to read through
the VIRUSCAN and CLEAN-UP documentation to show you the fastest
and safest way of completely removing your computer virus infection.
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
CARMEL Software Engineering
is proud to present:
Turbo Anti-Virus v6.80A
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
New Features in Version 6.80A
1. At last, we have an INSTALL utility. It is VERY user friendly and does
everything automatically for you. Just type INSTALL.
2. All executable files of Turbo Anti-Virus will check and validate themselves
before running.
But this is not all. In case of any virus infection - the files will cure
and clean themselves.
3. New command line parameters were added to TSAFE:
A. The '/Ax' parameter allows specification of the hot-key used to activate
the control window. If TSAFE is activated, the hot key will be <Alt-x>
instead of the default <Alt-T>. For example, To set the hot key to
<Alt-S> type: TSAFE /AS
B. The /X parameter will Disable / Enable the write protection of executable
files (COM & EXE).
This feature will warn the user of any attempt to change an executable
file, (e.g. When a virus is trying to infect it).
The default for this warning is ON.
4. A new option in the WARNING window of TSAFE allows the user to simulate
an error and cause the operation to FAIL.
For Example: If a virus tries to write to the boot sector - TSAFE will
open the warning window. Pressing the 'F' key (FAIL) will cause the
termination of the writing routine causing the virus to "think" that
the disk is write protected (Smart ah...).
5. TSAFE will open a window after every program termination and prompt the
user of the virus scan which has been carried out in the memory.
6. In TNTVIRUS, new options have been added to the Options menu and command
line.
A. The Check All Files option (/A from the command line) was added due to
the fact that there are some new viruses (100 Years - 4096), which also
infect data files. The virus can not be executed in data files but the
file is corrupted after infection and Turbo Anti-Virus will rebuild it's
original state.
B. The Automatic Loop option (/L from the command line) will cause the
automatic pilot to check more than one disk instead of checking once and
then exiting to DOS - This is intended for use in checking several floppy
disks.
7. Many more viruses are now identified and cleaned by Turbo Anti-Virus(tm).
Just keep on reading to understand why it is so important to use Turbo Anti-
Virus(tm).
8. The BOOTSAFE utility:
CARMEL Software Engineering
Turbo Anti-Virus software package
The * BOOTSAFE * module
The complete boot sector and partition table security system
GENERAL DESCRIPTION
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
BOOTSAFE is a security utility for the boot sector and partition table of
hard and floppy disks.
This utility will create clean images of the boot sector and partition
table of the drives requested.
Before creating the images - BOOTSAFE will make sure that these areas
are currently clean and free of any known viruses, and then it will create
images of these boot areas. It will also enable the saving of the images
to a floppy disk which can later be used in order to recover from a total
loss of the disk boot areas.
As soon as these images are created and saved, BOOTSAFE will be able
to compare them to all boot areas currently being used.
In case any difference is found between the images and the current boot
areas - BOOTSAFE will report this, and will provide the opportunity to
restore the original boot areas from the file images.
This solution will actually solve two common problems:
1) ANY virus which attempts to place itself instead of, or together with
the boot areas, will be found and eliminated.
2) ANY damage or changes will be fixed and the boot areas will be restored
to their original form.
It is most recommended to run BOOTSAFE from the AUTOEXEC.BAT file, since
this method does not occupy space in the memory, and its execution-time is
only a matter of seconds.
BOOTSAFE will also check the memory for all known viruses, and eliminate
any virus which is found - allowing for the continuation of work as if
nothing had happened.
HOW TO INSTALL BOOTSAFE IN THE AUTOEXEC.BAT FILE?
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
BOOTSAFE can be installed by the INSTALL utility contained in the original
Turbo Anti-Virus package.
While booting up the system, the INSTALL utility asks which drives to
check. It then creates the images for these drives.
BOOTSAFE can always be uninstalled by the same INSTALL utility.
HOW TO RUN BOOTSAFE FROM THE DOS COMMAND LINE (INSTEAD OF THE AUTOEXEC)?
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
Very Simple!
BOOTSAFE offers several options - the following is a description of each,
and a few examples:
In order to verify that the boot areas are OK:
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
Just type:
BOOTSAFE and it will check the default drive boot areas.
or
BOOTSAFE D: and it will check the D drive boot areas.
or
BOOTSAFE C: D: and it will check both C & D drives boot areas.
etc.....
If BOOTSAFE finds any changes in the boot areas - it will enable
restoration of the original boot areas from the images.
In order to create new images for the boot areas...
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
The /M option is used:
E.G.
BOOTSAFE D:/M and it will generate a new image file for drive D boot areas.
It will then provide the option to save the images on a seperate floppy
disk. (This will be usefull in case of a total loss of the boot areas, for
whatever reason.)
In order to restore the boot areas from a floppy disk, the floppy disk
containing the saved images is inserted to drive A and...
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
The /R option is used:
E.G.
BOOTSAFE D:/R and it will read the original boot areas of drive D which
were previously saved as image files on drive A, and will copy them to
drive D.
By using BOOTSAFE, worry about boot sector viruses will be a thing of the
past.
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Description of Known Viruses
Files Infecting Viruses
The Friday 13th viruses (7 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Jerusalem B ,Israeli virus and PLO virus.
*There are many variations of this virus: Jerusalem A,B,B (new),B-2,C,D, and E.
*This type of virus was released in Israel and was first discovered by CARMEL
Software Engineering in Kiryat Hamachshev LTD in July 1987, and 2 weeks later
at the Hebrew University of Jerusalem (causing much panic).
*The size of the virus is 1808 bytes, or 1813 bytes including the last 5 bytes,
which are the signature of this infection, and it infects EXE, COM and
some overlay files.
*Due to a bug in the virus, when it infects EXE files it does not add it's
signature at the end of the file, therefor the virus does not stop after the
first infection but continues infecting further EXE files.
*The Friday 13th is a resident virus and uses INT 21H function 31H in order to
remain in the memory. Then it infects every COM or EXE file which is executed.
The virus slows down the computer, black "boxes" appear on the screen and
on any Friday which is the 13th of the month it will erase the files being
executed.
The Saturday 14th viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Durban virus.
*The size of the virus is 681 (+0-15 Bytes for Paragraph alignement).
*Remains resident in Memory (not using Int 21H or 27H).
*Infects EXE & COM files (excluding COMMAND.COM).
*On every Saturday which falls on the 14th day of the month the virus will
destroy the disk by writing to the first 100 sectors of the disk - eliminating
the Boot sectors, FAT & Directory areas.
The Tuesday 1st viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* This virus is almost identical to the Friday 13th virus but with two
major differences.
* The activation date is every Tuesday which is the 1st day of the month.
* The identification signature of the virus was changed from MsDos to MsDns.
* This virus was sent to us by the virus hunter Mr. Szegedi Imre from Budapest,
Hungary.
The Friday 13th Destructive viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* This virus is almost identical to the Friday 13th virus but with one
major difference.
* Infected files are not working after the infection took place and this
makes reconstruction - impossible.
* This virus was sent to us by the virus hunter Mr. Szegedi Imre from Budapest,
Hungary.
The Jerusalem 3 virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Almost the same as the Friday 13th varieties with a few slight changes.
The Suriv 3.00 viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as a variety of the Jerusalem B/E or Israeli virus.
*The size of the virus is 1813 bytes, including the last 5 bytes which are the
signature of this infection, and it infects both EXE and COM files (SURIV).
*The Suriv 3.00 is a resident virus and uses INT 21H function 31H in order to
remain in the memory. Then it infects every COM or EXE file which is executed.
*The virus slows down the computer, black "boxes" appear on the screen and on
any Friday which is the 13th of the month it will erase the files being
executed.
The Sunday viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the 1636 virus.
*The size of the virus is 1636 bytes including the last 5 bytes which are the
signature of this infection and it infects both EXE and COM files.
*The Sunday virus is a resident virus and uses INT 21H function 31H in order to
remain in the memory. Then it infects every COM or EXE file which is executed.
*Every Sunday the virus will print on the screen:
Today is SunDay !
Why do you work so hard ?
All work and no play make you a dull boy !
Come on ! Let's go out and have some fun !
*This virus also steals Int 8 and may corrupt the FAT.
The April 1st viruses (Type A and B) (4 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The April 1st virus is also known as the TSR virus and the SURIV 1 - it only
infects COM files.
*The size of the virus is 897 bytes.
*Discovered in Israel in July 1987.
*It will remain resident in the memory, like the Friday 13th virus, but will not
infect EXE files.
*The virus is very easy to identify and therefore it is not very widespread -
evry time the virus infects a new file it writes on the screen:
YOU HAVE A VIRUS.
on April 1st it writes:
HA HA HA IT'S APRIL 1ST - YOU HAVE A VIRUS.
*There are two types of April 1st virus, with slight differences in their codes.
The April 1st D viruses (SURIV 2 & 3) (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The April 1st D virus is also known as the SURIV 2, SURIV 3 or Jerusalem D
virus, and it infects only EXE files.
*The size of the virus is 1488 bytes.
*It does not remain resident in the memory, like the other April 1st viruses,
but operates using MCB's (Memory Control Blocks).
*There are two types of virus with only slight differences in the first 16 bytes
of the virus: SURIV 2.01 or SURIV 3.00. The rest of the code is exactly the
same.
The Typo COM files virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The Typo virus infects only COM files.
*The size of the virus is 867 bytes.
*It will remain resident in the memory using INT 21 function 31.
*When an infected file is executed, the virus will search through all COM files
in the current directory and infect every clean file.
*This virus will mix some keystrokes at random, replacing the original keystroke
with that which is immediately adjacent to it on the right. E.g. ';' instead
of 'l', 's' instead of 'a' etc...
*Very annoying!....
The Amstrad COM files virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
The Amstrad virus infects only COM files.
Size: 850 Bytes (including 3 null bytes at the end).
It will not stay resident and will not infect COMMAND.COM.
When an infected file is being executed, the virus will search through all
COM files in the current directory and infect a clean file.
Inside the virus code there is an advertisement for AMSTRAD computers but
a few varieties which were sent to us contaid various messages.
The Oropax virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also called the Music virus.
*The Oropax virus infects only COM files.
*The sizeof the virus is 2756-2806 bytes.
*Infected files will always be divisible by 51.
*The virus will infect COM files which are not divisible by 51 - except COMMAND.
COM.
*It will remain resident in the memory, and will infect files in the default
directory when Int 21 functions: 13H, 16H, 17H, 39H, 3AH, 3CH, 3DH, 41H, 43H,
46H are called up.
*These functions are called up by standard DOS commands (COPY, RD, MD, DEL,
REN).
*After a few minutes, randomly, ("decided" by the virus) the virus will play 3
different melodies with a 7 minute delay between them.
The 640K COM files virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The 640K virus infects only COM files.
*Also called the Stupid virus and the Do-nothing virus.
*The size of the virus is 583 bytes.
*It will stay in the memory by copying itself at the location 9800:0000.
*For this reason the virus works on 640K systems only.
*When an infected file is executed, the virus will search through all COM files
in the current directory and infect one clean file.
*This virus causes no harm to the computer itself.
The MIXER 1 viruses (A & B) (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The size of the virus is 1615 bytes, version A, or 1635 bytes, version B,
(plus 0-15 bytes for paragraph alignment).
*The MIXER 1 virus was discovered in Israel in August 1989. The name probably
indicates that there are more MIXER viruses to come.
*CARMEL Software Engineering was the first to find a complete solution to this
virus. The virus was written in Israel and was found on Bulletin Boards.
*This virus infects only EXE files.
*Unlike the April 1st and the Friday 13th viruses it does not uses the INT 21H
function 31H to remain in the computer's memory.
*When executing a program it will mix the information being transferred through
the parallel and serial ports (e.g. � instead of �,[ instead of ]).
*At the end of the infected file the string MIX1 can be found.
*When the CHKDSK program is executed, if the virus is in the memory the amount
of memory reported is 2K less than the actual amount.
The Alabama virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the 1560 virus.
*One of the smartest and most destructive file viruses.
*Discovered in Israel by CARMEL Software Engineering in September 1989.
*Infects EXE files only.
*The size of the virus is 1560 bytes exactly.
*Like the MIXER 1 it does not use INT 21H function 31H to load itself in the
memory.
*Unlike the MIXER 1 it loads itself 30K below the highest memory location
reported by DOS, BUT IT DOES NOT LOWER THE AMOUNT OF MEMORY reported by
BIOS or DOS (this may cause big problems).
*This virus steals INT 9 and checks the keyboard for the RESET combination keys
(CTRL + ALT + DEL). It uses IN and OUT commands so that only experienced
programmers know how to deal with this virus.
*When it identifies this combination it will boot the computer using the
Bootstrap routine and will keep lurking in the computer's memory.
*After an hour of operation (the virus checks the hour in every INT 9 or 21
call) the following flashing boxed message will appear:
SOFTWARE COPIES PROHIBITED BY INTERNATIONAL LAW
Box 1055 Tuscambia ALABAMA USA.
*Now for the worst part. The infection system is one of the smartest of all.
*This virus does not infect the file which is currently being executed. First it
checks the current directory for other uninfected files. If it finds a clean
file it will infect it. Then when no further clean files remain, it will infect
the file that is being executed.
*Sometimes, when the virus finds a clean file, instead of infecting it, it will
exchange it for the file that is currently being executed, but will not rename
it. For example, the user may think that he is executing a DISKCOPY program but
instead he is executing a FORMAT program.
The 100 Years virus (COM & EXE) (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also known as the 4K, 4096, Frodo, hiding, and Century virus.
* The smartest file viruses.
* Discovered in Israel by CARMEL Software Engineering in October 1989.
* Infects COM, EXE, Overlay and DATA files as well as COMMAND.COM.
* The size of the virus is exactly 4096 bytes.
* It does not use INT 21H function 31H to load itself in the memory.
* It loads itself into the highest memory location reported by DOS, BUT IT DOES
NOT LOWER THE AMOUNT OF MEMORY reported by BIOS. DOS reports about 6K less
than BIOS (try CHKDSK).
* When the virus is loading itself into the memory it looks for COMMAND.COM in
the COMSPEC PATH and infects it.
* The virus reports the infected files as their original size (4K less than they
are).
* The header of the infected files is changed - but when the virus is in memory
it will show you the original data which is actualy at the end of the file
where the virus begins.
* It adds 100 years to the year stored in the directory. This does not appear in
the DOS dir which shows only the 2 last digits of the year.
* In this way the virus "knows" which file is infected and will reduce its size
by 4K when executing a DIR command and will show the original file header
instead of the current header.
* This "hiding" trick is very very smart and it makes all the Anti-Virus
utilities which look for changes in the files worthless.
* Interrupt stealing is very smart and cannot be detected by any mapping utility
(SMAP, SNOOP, PCTOOLS etc.). This will also bypass any warning utility which
checks the interrupts for illegal viral actions.
* The virus makes a single step in order to find the lowest memory location
and to put itself before any other programs which are hooked to the
interrputs which are used by it..
* The virus is encrypted and smart anti-debugging tricks are used.
* In order to avoid detection by resident warning utilities, it takes a single
step through INT 21 and checks for the lowest memory location that the system
calls. It then hooks itself to the original 21 Interrupt.
(It didn't have much success trying to "fool" TSAFE).
* This virus may cause serious damage to infected files.
The problem is that due to a bug - sometimes the virus infects files but does
not update the directory information - year, size etc.
This causes DOS to report a message :
ERROR in EXE File.
* This problem can be solved only by running CHKDSK/F and then performing the
Turbo Anti-Virus cleaning procedure.
* This virus also infects Data files (Lotus 123 SET file, DBASE DBF files etc.)
which can be restored by the regular cleaning procedure of Turbo Anti-Virus.
Just use the /A option in order to check all files in your disks - also data
files.
* From September 22nd 1990 - all infected program will hang the computer
immediatlly after loading into memory.
The Vienna viruses (versions A, B, C & D) (4 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the DOS 62 seconds virus and the 648 virus.
*Discovered in Israel by CARMEL Software Engineering in November 1989.
*Infects COM files only, including COMMAND.COM.
*The size of the virus is 648 bytes.
*Unlike other file viruses, this one will not load itself into the memory.
*When an infected file is executed - the virus searches in the current PATH for
a clean file and infects it. An infected file can be identified as the seconds
are switched to 62.
*This virus will destroy files randomly by removing the first 5 bytes, and
replacing them with a jump which will reboot the computer.
*This will happen whenever the 7 AND (assembler command) System time in seconds
equals zero.
The Lisbon virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the DOS 62 (Lisbon).
*Infects COM files only, including COMMAND.COM.
*The size of this virus is 648 bytes.
*This virus is almost the same as the Vienna virus.
The Pretoria virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also known as the South Africa and the June 16th virus.
* Infects COM files only, including COMMAND.COM and even IBMBIO.COM.
* If the virus infect SYSTEM files such as the IBMBIO.COM the disk will no
longer be bootble and it is necessery to run the SYS utility in order to
fix the system files again.
* The size of this virus is 879 bytes.
* It will not load itself into the memory.
* On June 16th all files in the ROOR directory will be renamed to ZAPPED.
The Christmas virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also known as the XA1 virus.
* Infects COM files only.
* The size of this virus is 1539 bytes.
* It will not load itself into the memory.
* On April 1st it will destroy the FAT.
* From December 24th to January 1st it will draw a picture of a Christmas
Tree.
The Sylvia virus. (1 variety)
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Netherlands Girl virus.
*Infects COM files only (excluding COMMAND.COM).
*The size of the virus is 1332/1301 bytes.
*It loads itself into the memory with MCB's.
*The virus changes the current drive to drive 'C:'.It infects all the files
in the C root directory, current directory and files being executed.
*Some of the files may be destroyed and only the virus program (1332 bytes)
will remain in place of the lost file.
*The virus will disable write-protect messages.
*A girl's name (Sylvia) and her address are in the virus asking you to send
a funny postcard and in return you will be sent an anti-virus (for this virus).
*We didn't try - we didn't have to!
The DataCrime A virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the 1168 virus and Columbus day virus.
*Infects COM files only.
*The size of the virus is 1168 bytes.
*It loads itself into the memory with MCB's.
*On October the 12th it will write on the screen:
1 MARCH 1989, DATACRIME VIRUS
and then will format your hard disk (first track - that is enough!).
*A very nasty virus which has caused much trouble and panic all over the world.
The DataCrime B virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the 1280 virus and Columbus day virus.
*Almost the same as DATACRIME A.
*Beware of other anti-viruses which identify only the DATACRIME A, they might
crash your files 'thinking' DATACRIME B is DATACRIME A.
The DataCrime C virus (COM & EXE) (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Columbus day virus and DataCrime II-A.
*Infects COM & EXE files.
*The size of the virus is 1514 bytes.
*This virus is encrypted, it will stick to any executable file (including
COMMAND.COM) which is smaller than 60K (approx.).
*It will infect files on drives A, B and C only; other drives are safe.
*Every time an infected file is executed, the virus will look through all the
directories for clean files in drives A, B and C and will infect the first
clean file it finds.
*When the virus infects a file it will perform a sector alignment - leaving
garbage at the end of the file.
*On October the 12th it will write on the screen:
谀哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
� 1 MARCH 1989, DATACRIME VIRUS �
滥哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪�
and then will format your hard disk (first track -that is enough!).
*A very nasty virus which has caused much trouble and panic all over the world.
The Syslock (COM) (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the 3551 virus.
*Infects COM files.
*The size of the virus is 3551 (+0-15 paragraph alignment) bytes.
*This virus is encrypted, it will stick to any executable COM file (including
COMMAND.COM).
*It will not load into the memory.
*It will infect files on the default drive only, other drives are safe.
*Every time an infected file is executed, the virus will look through all the
directories for clean files in the default drive and will infect a clean COM
file, at random.
*When the virus infects a file it will perform a paragraph alignment - leaving
garbage at the end of the file.
*At random it will cause a DOS error alarm:
Error writing to device AUX
The MachoSoft virus (COM) (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects COM files.
*The size of the virus is 3551 (+0-15 paragraph alignment) bytes.
*This virus is encrypted, it will stick to any executable COM file (including
COMMAND.COM).
*The structure and encryption method are the same as in the Syslock virus.
*It will not load into the memory.
*It will infect files on the default drive only, other drives are safe.
*Executing the command VIRUS=OFF will stop the virus action and infection
unless the COMMAND.COM file is infected. In this case every time the system
boots and loads COMMAND.COM another file will be infected.
*Every time an infected file is executed, the virus will look through all the
directories for clean files in the default drive, and will infect a clean COM
file at random.
*When the virus infects a file it performs a paragraph alignment - leaving
garbage at the end of the file.
*The virus will create a "hidden/read only" file which is called IBMIONET.SYS.
*When an infection takes place, the virus reads 20 sectors (using int 25) and
stores the number of the last sector in the file.
*Then it looks for the string "Microsoft" inside the sectors and changes the
"Microsoft" into "Machosoft". After that it writes the 20 sectors back with the
changes.
*This virus has big problems with DOS 4.
The Ghost File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the 2351 virus.
*Infects COM files only.
*The size of the virus is 2351 bytes.
*This virus will stick to any executable COM file (excluding COMMAND.COM).
*The seconds in the time field of the file are changed to 62 as in the Vienna
viruses.
*Every 8th file will be permanently damaged.
*Every time an infected file is executed, the virus will look for clean files in
the default directory and will infect a clean COM file.
*When an infected file is executed the virus will look for a 360K floppy in
drive A and will infect the boot sector of this disk with a Boot virus which
is very similar to the Ping-Pong virus but does not have an infection routine.
The 1260 File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects COM files only.
*The size of this virus is 1260 bytes.
*This virus is a variety of the Vienna (62 Seconds) virus.
*It changes the seconds in the directory to 31 (instead of 62), in order to
identify an infected file. Every file with 31 seconds in the directory time
field will not become infected.
*The virus looks for clean files to infect through the DOS PATH.
*This virus does not remain in the memory.
*This virus will stick to any executable COM file (excluding COMMAND.COM).
*It is encrypted and the description routine is changed at random in order to
confuse the search routines. (It didn't have any success with us,but it
certainly gave us a good fight. We consider it the hardest virus to search
for, since there is nothing constant in the virus code).
*Simple Anti-Debugging tricks can be found but not as clever as we found in
the 100 Years virus.
The 2930 File virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also called the Spanish virus.
*Infects COM & EXE files including COMMAND.COM.
*The size of the virus is 2930 bytes.
*Steals INT 24H in order to avoid READ\WRITE error reports.
*Looks for one executable file, infects it and then remains in the memory using
INT21H function 31H.
*While in the memory it will infect any file being executed.
*Uses simple Anti-Debugging tricks.
The Traceback File virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also called the 3066.
*Infects COM & EXE files including COMMAND.COM.
*The size of the virus is 3066 bytes.
*This virus is almost identical to the 2930 virus and one of them was probably
based on the other.
*It steals INT 24H in order to avoid Read \ Write error reports.
*It looks for one executable file, infects it and then remains resident using
INT 21H function 31H.
*While in the memory, it will infect any file which is executed.
*Uses simple Anti-Debugging tricks.
The 1720 File virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also called the Spanish II virus.
*Infects COM & EXE files excluding COMMAND.COM.
*The size of the virus is 1720 bytes including a 5 byte signature.
*Signature at the end of the file is: "=PSQR"
*When the signature is present - file will not be infected.
*It looks for one executable file, infects it and then remains resident using
INT 21H function 31H.
*While in the memory, it will infect any file which is executed.
*EXE files may be damaged immediately after infection - last 30 bytes are
totaly destroyed.
The ZeroBug File virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also called the Pallete and the 1536 virus.
*Infects COM & EXE files excluding COMMAND.COM.
*The size of the virus is 1536 bytes.
*While in the memory, it will infect any file which is executed.
*While in memory - infected files size is shown to be 1536 bytes less - as
it was before the infection.
*After a while - a bug will apear on the screen and will start eating all the
zero characters.
Very funny...
The JOJO File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Infects COM files only including COMMAND.COM.
* The size of the virus is 1701 bytes.
* This virus will stick to any executable COM file (including COMMAND.COM) which
is smaller than 63800 bytes.
* This virus randomly destroys the first tracks of every drive which it infects.
* The virus remains in the memory by using memory control blocks.
* Inside the virus the following strings can be found:
Welcome to the JOJO virus.
and
Fuck the system (c) - 1990
* This virus was sent to us by Eran Livne from Israel who won a Regsitered
version of Turbo Anti-Virus.
Thank you Eran...
The 1701 File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Cascade, Falling tears, Herbist, Autumn leaves virus.
*Infects COM files only.
*The size of the virus is 1701 bytes.
*This virus will stick to any executable COM file (including COMMAND.COM) which
is smaller than 63800 bytes.
*This virus was designed to operste on IBM PC clones only and on IBM PC original
systems.
*However there is a bug in the program which causes the virus to be activated
on any system.
*The virus remains in the memory by using memory control blocks.
*It is activated randomly and only in the years 1980 and 1988 in September,
October, November and December (Autumn).
*When the virus is activated - the letters start falling to the bottom of the
screen (CGA, EGA, VGA cards & monitors only).
*The virus is encrypted.
*This virus was sent to us by Yuval Tal from Israel who won a Regsitered
version of Turbo Anti-Virus.
Thank you Yuval...
The 1704-A File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Cascade, Blackjack ,Falling tears, Autumn leaves virus.
*Infects COM files only.
*The size of the virus is 1704 bytes.
*This virus will stick to any executable COM file (including COMMAND.COM) which
is smaller than 63800 bytes.
*The bug in the virus program (which causes it to be activated on any system)
has been fixed.
*The virus remains in the memory by using memory control blocks.
*It is activated randomly and only in the years 1980 and 1988 in September,
October, November and December (Autumn).
*When the virus is activated - the letters start falling to the bottom of the
screen (CGA, EGA, VGA cards & monitors only).
*The virus is encrypted.
The 1704-B File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Cascade, Falling tears, Autumn leaves virus.
*Infects COM files only.
*The size of the virus is 1704 bytes.
*This virus will stick to any executable COM file (including COMMAND.COM) which
is smaller than 63800 bytes.
*The bug in the virus program (which causes it to be activated on any system)
has been fixed.
*The virus remains in the memory by using memory control blocks.
*It is activated randomly and only in the years 1980 and 1988 in September,
October, November and December (Autumn).
*When it is activated - the letters start falling to the bottom of the screen
(CGA, EGA, VGA cards & monitors only).
*The virus is encrypted.
The 1704-C File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Cascade, Falling tears, Autumn leaves virus.
*Infects COM files only.
*The size of the virus is 1704 bytes.
*Almost the same as the 1704-A.
The 1704-Format File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Cascade, Falling tears, Autumn leaves virus.
*Infects COM files only.
*The size of the virus is 1704 bytes.
*Almost the same as the 1704-A.
*This virus will also format hard disks - be careful.
*The virus is encrypted.
The 17Y4 File virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Cascade, Falling tears, Autumn leaves virus.
*Infects COM files only.
*The size of the virus is 1704 bytes.
*Almost the same as the 1704-A.
The Dark Avenger virus (COM & EXE) (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects COM & EXE files.
*The size of the virus is 1805 bytes (+0-15 bytes for paragraph alignment).
*It loads itself into the memory with MCB's.
*The virus writes to the boot sector and does other bad things with the FAT.
*Uses simple Anti-Debbuging tricks.
*The virus contains the message:
Eddie lives somewhere in time.
The FU-Manchu A virus (COM & EXE) (2 varieties)
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also called the 2086 virus.
*Infects COM & EXE files.
*The size of the virus is 2086 bytes.
*It loads itself into the memory with MCB's.
*The funniest virus we have ever received.
*It steals interrupts 21 (DOS), 9 (Keyboard), and 16 (Keybard).
*Int 16 will be installed only after August 1989.
*This virus will do the following things:
-When CTRL+ALT+DEL are pressed it will write the message:
The World will hear from me again !!!
-When you type : 'fuck' it will be erased.
-When you type : 'waldheim' it will continue - 'is a nazi.'
-When you type : 'thacher' it will continue - 'is a cunt.'
-When you type : 'reagen' it will continue - 'is an arshole.'
-When you type : 'FuManchu' it will continue - 'virus date:' etc...
*As you can see, the author of the virus didn't know English very well.
The Icelandic viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects EXE files only.
*The size of the virus is 652 bytes (+0-15 bytes for paragraph alignment).
*It loads itself into the memory with MCB's.
*The virus infection system is very much like the MIXER's viruses and probably
the MIXER's author copied it from this virus since it is older.
*It will copy itself at the end of the memory and lower the amount of memory
reported by DOS by 2K (CHKDSK).
*The first version of this virus will infect every 10th file executed which is
the reason why it is not very popular; the second version will infect any file,
but this is the only difference between them.
*The virus will mark one bad cluster in the FAT of the infected disk.
The Icelandic II viruses (1 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects EXE files only.
*The size of the virus is 632 bytes (+0-15 bytes for paragraph alignment).
*It loads itself into the memory with MCB's.
*The virus infection system is very much like the MIXER's viruses and probably
the MIXER's author copied it from this virus since it is older.
*It will copy itself at the end of the memory and lower the amount of memory
reported by DOS by 2K (CHKDSK).
*The first version of this virus will infect every 10th file executed which is
the reason why it is not very popular; the second version will infect any file,
but this is the only difference between them.
*The virus will mark one bad cluster in the FAT of the infected disk.
The Saratoga virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects EXE files only.
*The size of the virus is 640 bytes (+0-15 bytes for paragraph alignment).
*It loads itself into the memory with MCB's.
*This virus is almost identical to the Icelandic virus.
*It will copy itself at the end of the memory and lower the amount of memory
reported by DOS by 2K (CHKDSK).
*This version of the virus will infect every 2nd file executed.
*The virus will mark one bad cluster in the FAT of the infected disk.
The 405 virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects / Overwrites COM files only.
*This virus will destroy the infected file and will replace it by 405 bytes of
code.
*More of a Trojan horse than a virus...
The 512 virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Infects / Destroys COM files only.
*The size of the virus is 512 bytes (the file size will not grow).
*Remains in the memory.
*This virus will overwrite itself (512 bytes) at the beginning of the file,
destroying the previous code which was there.
*More of a Trojan horse than a virus...
The Aids virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Hahaha and Taunt virus.
*Infects / Overwrites COM and EXE files.
*When activated the virus displays the message:
Your computer now has AIDS,
and hangs the computer. (That's it, stuck dead.)
*The virus overwrites the first 13K of the infected file - destroying the
original data with no way to rebuild the file.
The Perfume virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Size: 768 bytes.
It infects only COM files (excluding COMMAND.COM).
Stays resident by replicating itself to the end of memory (1024 bytes).
While in memory - infects every file which is being executed.
This virus was sent to us by Mr. Arieh Goretsky from MacAffe Co USA.
The Yankee Doodle 1 virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 2890 (+0-15 bytes for paragraph alignement) bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident in memory using MCB's .
* While in memory - infects every file which is being executed.
* At 17:00, if the virus is in memory - It will start playing the Yankee Doodle
melody.
* Staels interrupts 1,3,1CH,21H and 24H (during infection only).
* Virus uses Sinlge step in order to locate the original INT 21H address.
* Virus can repair it self if it finds that an Anti-Virus tried to disable
it in memory (Didn't help it self much when we aliminated it).
* This virus is a part of the family of other Doodles and Vacisnas viruses
which are capable of identifing each other and remove an older version
of the virus before infecting it with a new version.
the number of version cam be seen at the end of the file.
* This virus was delivered to us at the CeBIT 90' fair by Pavel Baudis from
CZECHOSLOVAKIA who won a Registered version of Turbo Anti-Virus.
Thank you Pavel...
The Yankee Doodle 2 virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 2940 (+0-15 bytes for paragraph alignement) bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident in memory using MCB's .
* While in memory - infects every file which is being executed.
* At 17:00, if the virus is in memory - It will start playing the Yankee Doodle
melody.
* Almost the same as the other Yankee Doodle viruses.
The Yankee Doodle 3 virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 2772 (+0-15 bytes for paragraph alignement) bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident in memory using MCB's .
* While in memory - infects every file which is being executed.
* At 16:59:57, if the virus is in memory - It will start playing the
Yankee Doodle melody.
* Almost the same as the other Yankee Doodle viruses.
* This virus was delivered to us at the CeBIT 90' fair by users from East
Europe.
The Haloechen virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 2011 (+0-15 bytes for paragraph alignement) bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident in memory using MCB's (not with Int 21H or 27H).
* While in memory - infects every file which is being executed.
The Vacsina v5 virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 1217 bytes ,EXE file - 132 additional bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident in memory using MCB's .
* While in memory - infects every file which is being executed.
* Infects EXE files with Entry point of 0000:0000.
* It infects EXE files in 2 stages: 132 bytes and than 1217 bytes.
* EXE file are infected by placing a jump at the head of the file instead of
the 'MZ' EXE file identifier.
* At the end of the virus there is a number which indicates the version
of the virus.
* New versions wii identify old versions and will replace them instead of
infecting the file again.
* This virus is a part of the family of other Doodles and Vacisnas viruses
which are capable of identifing each other and remove an older version
of the virus before infecting it with a new version.
the number of version cam be seen at the end of the file.
* This virus was delivered to us at the CeBIT 90' fair by users from East
Europe.
The Vacsina v16 virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 1350 bytes, EXE file - 132 additional bytes.
* Almost the same as Vacsina v5.
The Vacsina v24 virus (2 varieties EXE & COM).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Size: 1760 bytes bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident in memory using MCB's .
* While in memory - infects every file which is being executed.
* EXE files larger than 62K will not be infected.
* EXE file are infected by placing a jump at the head of the file instead of
the 'MZ' EXE file identifier.
* At the end of the virus there is a number which indicates the version
of the virus.
* New versions will identify old versions and will replace them instead of
infecting the file again.
* This virus is a part of the family of other Doodles and Vacisnas viruses
which are capable of identifing each other and remove an older version
of the virus before infecting it with a new version.
the number of version cam be seen at the end of the file.
* This version of vacsina steals INT 9 (keyboard) and when the ALT-CTRL-DEL
combination is pressed - it plays the Yankee Doodle melody.
* This virus was sent to us by the virus hunter Mr. Szegedi Imre from Budapest,
Hungary.
The Aids Information Trojan (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* This hard disk "eater" is not a virus but a Trojan.
* It was released on December 1989 and was spread by an unknown company named
Cyborg from Panama.
This company invested 150,000 U.S.$. in order to send thousands copies of the
disk which contained the Trojan.
* The disk contains two files. The first one is the file AIDS.EXE which is a
big database of information about the Aids virus (not the computer virus).
The other file is an INSTALL utility which must be executed to install the
AIDS file on a computer system which includes a Hard-Disk, otherwise the
AIDS file will not run.
* During the installation, the AUTOEXEC.BAT file is changed to AUTO.BAT file
and a new AUTOEXEC.BAT file is written by the INSTALL utility.
* After 90 reboots of the system - the disk is reformated by the program.
The Taiwan virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also known as the sunny virus.
* Infects COM files only, including COMMAND.COM.
* Size: 743 bytes.
* This virus will not load itself into memory.
When an infected file is being executed - the virus searches in C drive
a clean file and then infects it.
* It will place itself instead of the 743 first bytes of the file and the
code which was there before will be transfered to the end of the file.
The DBASE virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Size: 768 bytes.
It infects only COM files (excluding COMMAND.COM).
Stays resident by replicating itself to the end of memory (1024 bytes).
While in memory - infects every file which is being executed.
This virus was sent to us by Mr. Arieh Goretsky from MacAffe Co USA.
The V2000 virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Size: 2000 bytes.
It infects COM & EXE files (excluding COMMAND.COM).
Stays resident by replicating itself to memory without using INT 21H.
While in memory - infects every file which is being executed.
This virus was sent to us by the virus hunter Mr. Szegedi Imre from Budapest,
Hungary.
The Victor virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also called the Ivan virus.
* Size: 2442 bytes.
* It infects COM & EXE files (excluding COMMAND.COM).
* Stays resident by replicating itself to memory without using INT 21H.
* While in memory - infects every file which is being executed.
* This virus was sent to us by the virus hunter Mr. Szegedi Imre from Budapest,
Hungary.
The Friday 13th 1 COM virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also known as the South Africa 2 and virus-B.
* Infects COM files only, including COMMAND.COM and even IBMBIO.COM.
* The size of this virus is 425 bytes.
* It will not load itself into the memory.
* Infects all clean files in the current directory.
The Friday 13th 2 COM virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also known as the South Africa 2 and virus-B.
* Infects COM files only, including COMMAND.COM and even IBMBIO.COM.
* The size of this virus is 549 bytes.
* It will not load itself into the memory.
* Infects all clean files in the current directory.
The VP virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Infects COM files only, including COMMAND.COM and even IBMBIO.COM.
* The size of this virus is 904 bytes.
* It will not load itself into the memory.
* In the first 16 bytes of the infected file - the 2 letters VP can be found.
* The virus writes to the boot sector of every drive in the system thses
2 bytes (VP).
The Barcelona virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Infects EXE files only.
* The size of this virus is 1157 (+0-15 bytes for paragraph alignement).
* It will not load itself into the memory.
* Infects one clean file in the current directory.
* If infection fails - the virus will delete the file.
* The virus is encrypted.
* The word Barcelona can be found after the decription.
The Lehigh viruses (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* One of the first viruses for PC computers working under DOS.
* Detected for the first time at the Lehigh University.
* Infects only, COMMAND.COM.
* COMMAND.COM file will not grow.
* Virus locate the stack area inside the COMMAND.COM and put itself
inside avoiding by this the growing of the file.
* Load itself into the memory and steals INT 21 (using INT 44 instead).
* Will look for the COMMAND.COM file at the current drive ROOR directory.
* Version #2 of this virus is known as a DISK formatter.
The 5120 virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Also called the BASIC virus.
* Infects COM & EXE files - excluding COMMAND.COM.
* The size of this virus is 5120 (+0-15 bytes for paragraph alignement).
* It will not load itself into the memory.
* Infects all clean file in the current directory and looks for clean
files on drive C through all directories.
This action takes a lot of time.
* From April 1st 1992 - All infected files will stop running and the
message : "Access Denied" will be displayed.
* Inside the virus code - the word BASRUN can be found.
* This virus was sent to us by Alfred Manthy Rojan from West Germany, who
got a registered Turbo Anti-Virus package free of any charge.
Thank you Alfred...
The 8 Tunes virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
* Infects COM & EXE files - excluding COMMAND.COM.
* The size of this virus is 1971 (+0-15 bytes for paragraph alignement).
* It willload itself into the memory.
* Infects every clean file which is being executed.
* When the day comes it will play one of the 8 Tunes which it "knows"
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
These are the 108 types of file viruses (identification and safe elimination).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Boot Infecting Viruses
哪哪哪哪哪哪哪哪哪哪哪哪
The Ping-Pong virus (A, B, C, D) (4 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The first Boot Sector virus to be discovered in Israel.
*It is also called the Bouncing Ball, and the Italian virus.
*This is a "nice" virus (in comparison with the others), which infects the DOS
boot sector of floppy and hard disks.
*Every time the computer is booted from an infected diskette the memory will
retain the virus.
*While booting, the virus loads itself at the end of the memory (as reported
by BIOS) and lowers the amount of reported memory by 2K.
*After a while, a bouncing ball will appear on the screen and will not stop
until the computer is rebooted.
*The infection is very quick and by simply executing a DIR command on a clean
diskette it will become infected.
*When mapping an infected disk (e.g. with PCTOOLS) one cluster is marked as bad
whereas actually the original boot sector was placed there by the virus
program.
*A new variety of the Ping-Pong virus was identified in March 1990.
*This variety will not lower the memory size (BIOS) by 2K but will set the size
to a constant value.
The MisSpeller virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Typo virus.
*The MisSpeller virus is an Israeli mutation of the Ping-Pong virus.
*90% of the boot system is exactly the same as the Ping-Pong, which caused some
Anti-Virus programs to destroy disks because they identified the virus as the
Ping- Pong.
*However, Turbo Anti-Virus(tm) recognized that it was a new virus and did not
destroy the disk, due to smart and careful virus elimination and data
recovery techniques.
*The MisSpeller also infects the DOS Boot sector and loads itself at the end of
the memory during booting.
*The amount of memory is lowered by 2K exactly as with the Ping-Pong virus.
*This virus, however, will not simply bounce a "nice" ball on your screen.
*The minute it loads itself, it will start mixing the data which is being
transferred through the parallel port.
*English, Hebrew and digits are mixed up in order to cause great confusion (V is
mixed with W, C with K, J with G, � with �, � with �, etc..).
The Disk Killer virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Also known as the Ogre virus.
The Disk Killer infects the DOS Boot sector and loads itself to the end of
memory during boot.
The amount of memory is lowered by 8K.
The virus size is 3 clusters which are marked as BAD in the FAT.
Due to a BUG in the virus code other clusters are incorrectly marked as BAD
instead of the right ones.
The virus may also put himself on top of a file - destroying it while it does
so.
A counter inside the virus checks for the number of disks which it has
infected and than formats the Hard-Disk.
A very destructive virus.
The Stoned virus (version A and B) (3 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The stoned virus was discovered in Israel by CARMEL Software Engineering in
September 1989.
*Also known as the Marijuana virus and the New-Zealand virus.
*It is a very destructive virus which infects the Boot Sector.
*No bad clusters are marked when this virus infects a disk.
*When booting from an infected disk - it will sometimes display the message:
Your PC is Stoned - LEGALIZE MARIJUANA.
*This little virus loads itself, while booting, at the end of the memory and
lowers the amount of memory reported by BIOS by 2K (like the PING-PONG and
MisSpeller viruses).
*It will save the original boot sector in TRACK 0, SIDE 1, SECTOR 3 on floppies,
and in TRACK 0, SIDE 0, SECTOR 7 on hard disks.
*This virus will not save the data which was in that sector before the
infection, causing great damage to the directory and FAT.
*There are at least 5 versions of the Marijuana\Stoned virus.
The Yale virus (2 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*Also known as the Alameda and Merritt virus.
*This virus will infect 360K floppy disks only (not hard disks).
*When a clean diskette is inserted in the drive and the computer is booted using
CTRL+ALT+DEL the virus will infect it.
*The virus stores the original boot sector at track 39 sector 8 head 0,
destroying the data which was there before the infection occurred.
*The virus will not cause any other damage.
The Ghost Boot virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*This virus is not a regular one. Actually it is not a virus at all.
*The Ghost Boot virus is planted by the Ghost file virus on a 360K floppy disk
which is situated in drive A at the time of execution.
*It is very much like the ping-pong virus but it does not have an infection
routine and therefore it will only load into the memory and will not infect
other disks.
*This virus can be found in 360K floppies only (not in hard disks).
*The virus stores the original boot sector at track 39 sector 9 head 1,
destroying the data which was there before infection occurred.
*The virus will not cause any other damage.
The Den-Zuk virus (1 variety).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*The Den-Zuk virus infects 360K floppy disks only.
*It loads itself at the end of the memory and lowers the amount of memory
reported by BIOS by 7K.
*The virus stores the original boot sector at track 40 head 0, which it formats
in a non-standard format (sectors 33-42 instead of 1-9).
*This virus looks for the Brain virus in the boot sector before infection takes
place. If it finds the Brain virus - it will save the Boot sector which was
saved by the Brain virus and not the current boot sector.
*When the virus is in the memory - any clean floppy disk which is inserted in
disk drive A or B will become infected.
*The virus steals interrupts 13 (DISK I/O) and 9 (Keyboard).
*When the ALT-CTRL-DEL keys are used to boot the system,the virus will show the
Den-Zuk logo, on a graphic screen only (a nice picture!).
*The virus will not cause any other damage.
The Pakistani Brain viruses (regular, version 9.00 and Ashar) (3 varieties).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
*This virus was the second boot-sector virus discovered in Israel (after
the Ping-Pong virus). It is a little bigger, and uses some smart tricks.
*Like all boot-sector viruses, the Brain virus infects a disk by changing
the boot-sector, so that when the system is booted from an infected diskette,
the virus is loaded into the memory, even before the system is operated. The
virus itself is located in sectors marked as "bad sectors" on the disk,
which take 3K bytes from the free sectors of the disk.
*The Brain virus can be easily recognized because the boot-sector of an
infected disk contains a message dedicating it to "all the viruses which are
no longer with us". Some versions of the Brain virus even contain the
address and phone number of the authors who wrote the virus!
*One of the easiest ways to recognize this virus is that on an infected
system disk, the volume label is changed to "Brain". (You can see it with a
simple 'dir' command on the infected disk).
*To make it harder to destroy the Brain virus uses a very smart trick - If the
virus is in the computer's memory (after being booted from an infected disk),
each time the computer tries to read or write to the boot sector - the virus
uses the original boot sector! This means that you cannot just write a
normal boot-sector on the infected disk in order to destroy the virus, because
the virus will not allow this! (This method will work on the Ping- Pong virus,
but then the bad sectors on the disk will be lost, so it is not recommended).
*In order for the computer's memory to become infected, it has to be booted
from an infected disk. However once the virus is in the memory -any diskette
that is inserted in the disk drive will become infected! It is enough to
type "A:" or "DIR A:" to infect the diskette in drive A.
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
These are the 16 types of Boot Sector / Partition table viruses.
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Turbo Anti-Virus will also detect the following file viruses:
* Doodle B
* Kennedy
* AIDS II
* Amoeba 1392
* Agiplan
* Eddie 2 (Dark Avenger 2)
* Pixel 1
* Pixel 2
* Polish virus
* 1210 virus
* 1559 virus
* VComm virus
* ItaVir
* Solano
* 12 Tricks Trojan A
* 12 Tricks Trojan B
* Joker
* Icelandic 3
* Virus-90
* Jerusalem 1 (Friday 13th variety).
* Jerusalem 2 (Friday 13th variety).
* Vacsina X.
* Devil's Dance
* DataCrime D COM (DataCrime II-B)
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
These are the 24 FILE-Infecting viruses (identification - no elimination).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
Turbo Anti-Virus will also detect the following boot viruses:
* Korea
* EDV
* Pentagon.
* Ohio.
* Falling letters / Israeli BOOT.
* Chaos
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
These are the 6 BOOT viruses (identification - no elimination).
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
谀哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪目
� Send us new viruses (including those viruses which �
� are only identified) and win a FREE registered version �
� of Turbo Anti- Virus with 12 months guarantee. �
滥哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪馁
Total Viruses
108 File viruses Identification & Elimination.
16 Boot viruses Identification & Elimination.
24 File viruses Identification.
6 Boot viruses Identification.
Total of 154 viruses
哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪哪
For more details, or to place an order, please ask your
local software dealer about Turbo Anti-Virus(tm).
or
Contact us directly.
USA Main Office:
CARMEL Software Engineering
177 Palisade Av.
Cliffside Park.
New-Jersey 07010
USA.
TEL: 201-945-5751
FAX: 201-945-9029
Eli Shapira & Yuval Sherman
CARMEL Software Engineering
- END -
CENTRAL POINT ANTI-VIRUS FOR WINDOWS VERSION 1
This file contains information that is not in the manual or has changed
since the manual was printed. Please take a moment to read it.
Getting Help
============
For additional information about features in the program, press F1 for
online help.
Command-Line Options
====================
For a list of command-line options available in VSafe, VWatch, or
Bootsafe, type the program name at the DOS prompt followed by /? like
this:
VSAFE /?
Supported Modes
===============
Central Point Anti-Virus for Windows supports standard or enhanced
modes. It does not support Windows real mode.
Updating the Virus List from CompuServe or CPS BBS
==================================================
When new viruses are discovered, signature update files are placed on
CompuServe and Central Point Software's BBS. The manual incorrectly
tells you to download CPAVSCAN.DLL, WNVIRLIST.CPS, and VIRSIGS.CPS.
Instead, to update the virus detection capability in Central Point
Anti-Virus, look for a self-extracting archive file named WSIGxx.EXE
(where xx is a two-digit number representing incremental updates,
starting with 01). This file contains CPAVSCAN.DLL, WNVIRLIST.CPS and
VIRSIGS.CPS.
Troubleshooting
===============
Alerts When Upgrading Software
------------------------------
Anti-virus software is designed to alert you when files change.
However, when you are upgrading new versions of software, you may not
want to be alerted. See the "Preventing Unwanted Alerts" section in the
Troubleshooting chapter of the manual for a way to cut down on these
alerts.
No Central Point Anti-Virus Icon
--------------------------------
If there is a generic icon in the Central Point Anti-Virus group when
you start Windows, you need to specify the full path name for Central
Point Anti-Virus to use the correct icon. To do so,
1. With the Central Point Anti-Virus group open in the Program Manager,
highlight the generic icon for Central Point Anti-Virus.
2. Choose Properties from the File menu.
3. Type the full path name in the Command Line text box, then choose
OK.
For example, if you installed Central Point Anti-Virus into the default
directory, type this in the Command Line text box:
C:\CPAV\WNCPAV.EXE
Scheduler Can't Find WNCPAV.EXE File
------------------------------------
If you receive a message that Scheduler can't find the WNCPAV.EXE file,
choose Search for Applications from the Options menu in the scheduler.
This reconfigures Scheduler so that it locates the necessary files it
needs.
Configuration File Too Big
--------------------------
If you receive a message that your configuration file is too big when
you install, you need to manually edit your WIN.INI or PROGMAN.INI
files.
To update these files:
1. Open each file using a text editor. (These files are found in your
WINDOWS directory.)
2. In your WIN.INI file, add the full path of the Central Point TSR
Manager to your Windows load line. For example,
[windows]
load=C:\CPAV\WNTSRMAN.EXE
3. In your PROGMAN.INI file, add a new Group line for WNCPAV and then
append that group number to the order line. For example,
Order= 1 2 3 4
[Groups]
Group1=C:\Windows\MAIN.GRP
Group2=C:\Windows\APPLICAT.GRP
Group3=C:\Windows\ACCESSOR.GRP
Group4=C:\CPAV\WNCPAV.GRP
4. Save each file and close the text editor.
Central Point Backup Users
--------------------------
Virus detection capabilities have been built into Central Point Backup
so that you will not inadvertently back up infected files. Do not scan
for viruses with Central Point Anti-Virus while backing up your system.
;-------------------------------------------------------------------------
; This is the README.TXT file for SMARTCD CD-ROM cache device driver
;
; (C) Copyright FarStone corp. 1993, All rights reserved.
;-------------------------------------------------------------------------
Preface :
=========
Have you an experience running MS-Windows(TM) without disk caching drivers
(without SMARTDRV command in AUTOEXEC.BAT) ? What a terrible hard work for
hard disk in this situation ?
How about your CD-ROM drives ?
It seems to be over loaded when running MS-Windows (TM) multimedia
applications or titles (such as Microsoft(R) BookShelf(TM)).
SMARTCD (TM) CD-ROM cache device driver is target to resolve this problem.
SMARTCD can easily increase CD-ROM performance by 2 to more than 30 times
faster, and free as much available conventional memory as without it.
System requirement :
====================
To get the benefit from SMARTCD, you need:
1. A CD-ROM drive compliant to MPC (Multimedia PC)
2. At least 256 KB of extended memory.
SMARTCD Overview
================
SMARTCD is a professional and experienced cache device driver for CD-ROM
devices. It will improve CD-ROM performance from 2 to more than 30 times
faster than without it dependent on applications. (please refer to "test
report section" in this file).
In addition to good performance improvement, SMARTCD also has many
other smart features. SMARTCD has an integrated installation program,
well test with existing hardware, software and related systems,
has on-line help, device driver status and statistics report program,
intelligent memory allocation strategy, easy to unload from system,
and plus all above, SMARTCD may incredibly use none extra conventional
memory of system !
SMARTCD features :
==================
1. Dramatically improve CD-ROM device performance from 2 to 30
times faster.
2. SMARTCD is a professional, experienced product and support the
largest cache size up to 64 MB.
3. Command line startup, with unload capability.
4. Integrated with install, status check, unload, on-line help,
and others.
5. Automatically detect and allocate memory.
6. Very small and efficient resident code (TSR), at least 7 KB.
7. Can configured to eat nothing of extra conventional memory.
Installation
============
It is quite easy to install the SMARTCD CD-ROM device driver, run next
at DOS command prompt :
> SMARTCD /SETUP
Follow the setup program to install SMARTCD onto your system. If you want
to change the configuration of SMARTCD, you can run setup program again,
SMARTCD setup program will keep track of your current setting and setup the
new configuration.
Note : You have to reboot to make the new setup active.
SMARTCD command syntax :
========================
SMARTCD has the following command line syntax :
1. > SMARTCD /SETUP : setup onto your machine.
2. > SMARTCD [dddddd]: Start SMARTCD (TSR) and use [dddddd] KB of memory
as cache, ddddd from 256 to 65535 KB. [dddddd] is
option, see note for detail description.
3. > SMARTCD /UN : unload from memory, free all memory used by SMARTCD
to system.
4. > SMARTCD [/? | /ST | /ON | /OFF | MAX | MIN]
/? or /ST : Help or show SMARTCD driver status
/ON or /OFF : Enable or Disable SMARTCD cache driver
/MAX or /MIN : Cache all or directory only, Default is MAX if
cache buffer size > 512 KB
Note : SMARTCD is started by command line "SMARTCD [dddddd]", where ddddd
size is optional, it tells SMARTCD allocate how much of system
XMS memory for the CD-ROM buffer. The larger the buffer the better
CD-ROM performance gained. The size can from 256 to 65535 (256 KB to
64 MB). If you do not specify dddddd, SMARTCD will use the following
table to allocate system RAM (XMS RAM) as cache buffer.
Free XMS memory SMARTCD allocates
----------------------------------------------------------------
less than 256 KB none (fail to load)
less than 1024 KB allocate all
> = 1024 KB allocate half of available
with maximum buffer size = 2048.
Note : If you want to allocate cache buffer size larger than 2048 KB, you
have to specify the [dddddd]. SMARTCD will allocate maximum of 2048
KB without this parameter.
Note : /UN unload command will free all of the memory occupied by SMARTCD,
include cache buffer and program code.
Note : /MAX will cache all of the data read from CD-ROM, and /MIN cache
the directory information of CD-ROM only. You can change
it at any time. By default, SMARTCD will use /MAX methodology
except cache buffer size less than 512 KB.
Free more conventional memory
=============================
After you have installed the SMARTCD CD-ROM device driver, you can release
the buffer allocate for MSCDEX.EXE (TM). There is an "/M:number" parameter
with MSCDEX.EXE command line. The "number" means to allocate how many 2 KB
buffers for MSCDEX, which allocates memory from conventional memory
(under 640KB) and that decreases your free conventional memory. In general
the buffers allocated are 12 ("/M:12"). If we install SMARTCD onto system,
then these buffers have no benefit to CD-ROM performance according to the
speed test, so actually we can decrease it to 4 without inferring performance
of CD-ROM drives if SMARTCD is loaded.
If we reduce the number to 4 then we can free 8 buffer space (16 KB)
of conventional memory from MSCDEX. We recommend to update the MSCDEX buffer
number to 4 if you need more conventional memory. Next is an example MSCDEX
and SMARTCD commands in AUTOEXEC.BAT after you installed SMARTCD and
changed MSCDEX buffer number to 4:
in AUTOEXEC.BAT
C:\DOS\MSCDEX.EXE /M:4 /D:SONY_000
C:\SMARTCD.EXE 1024
Performance test report :
=========================
Please find detailed performance test report in file "report.txt"
SMARTCD developer :
===================
SMARTCD project leader had been given an excellent comment for his disk
cache driver developed for a famous world wide PC company in 1988. In the
LanTime NSTL test reported in 1990, his cache driver was outstanding the
other competitors, such as Microsoft SMARTDRV, and Multisoft PCKwirk cache.
Technical highlights :
======================
Intelligent cache method used, which include the read-ahead, data hashing
technology, priority data handling, and many others.
Notes:
======
SMARTCD is a trademark of Far Stone Technology Corp. Microsoft is registered
trademark of Microsoft corp. Acer is registered trademark of Acer inc.
Stacker 3.1 for Windows and DOS - Late Breaking News
This document contains important information that is not
included in the Stacker for Windows & DOS User's Guide or in
the Stacker 3.1 Supplement. If you're using any special or
unique software with your system, such as and Super PC-Kwik
Cache, see the help provided in Setup. To get help in these
situations:
When Setting Up Stacker for Windows:
1 From any Setup screen, press F1.
2 Click Contents.
3 Press TAB to select Software Considerations and press
ENTER.
When Setting Up Stacker for DOS:
1 From any Setup screen, press F1.
2 Press ENTER to choose the Index.
3 Press TAB to select Software Considerations and press
ENTER.
To print the contents of this file
1 Retrieve this document into any word processor
2 Use the print feature
Contents
This document contains late-breaking information on the
following topics:
1.0 How Stacker Works
1.1 How Stacker Compression Happens
1.2 Compressing Data
1.3 Establishing Access
1.4 Compressing the Space on an Empty Disk
1.5 How Your System Works with Stacker
2.0 The STACKER.INI File
2.1 STACKER.INI Structure
2.2 STACKER.INI General Syntax rules
2.3 Editing your STACKER.INI File
2.4 STACKER.INI General Switches
2.5 Mounting Parameters
3.0 STACKER.INI Examples
3.1 Single Hard Drive Example
3.2 Multiple Hard Drive Example
4.0 Loading Stacker High
5.0 MS-DOS Command Equivalents
1.0 How Stacker Works
After you set up Stacker on your computer, it works by
decompressing files when you open them and compressing
the files when you save them again. Stacker does its
work in the background; you never notice it. Because
Stacker compresses all your data, you have access to
approximately twice as much disk space.
How does Stacker do all this? When you set up Stacker,
Setup modifies your system. This modification allows
the operating system to "recognize" your Stacker drive.
Prior to DOS 6, all of these changes to your system
were contained in the CONFIG.SYS file. Now with DOS 6,
these changes take place by "preloading" the
information from two files, DBLSPACE.BIN and
STACKER.INI.
Stacker adds an extra drive to your system during
Setup, and then compresses all your files into one
large file on this new drive. DOS assigns this new
drive the next available drive letter, so your data is
really on the new drive (D, for example). Stacker then
exchanges drive letters between your original disk (C,
for example) and the new drive. So all your data is
where you expect, on drive C.
1.1 How Stacker Compression Happens
Setup does two things when it compresses the data on a
disk. It:
1 Compresses the data and stores it more efficiently
to save space.
2 Establishes access to the compressed data so your
computer can use it.
The compression process is the same whether you use the
Express or Custom method.
1.2 Compressing Data
1 Setup compresses data by creating a hidden file,
STACVOL.DSK, in the root directory of the disk.
2 Setup reads every file on the disk, one at a time.
It then compresses each file and stores it
efficiently in the new STACVOL.DSK file. As each
file is stored and verified, Setup deletes the
original uncompressed file, making more space on
the disk. In the process, the STACVOL.DSK file
gets larger and larger as more and more data is
added to it.
3 As it stores files in STACVOL.DSK, Setup keeps
track of each file's size and location.
4 Setup leaves any files the system needs for
startup, as well as any files with the system
attribute, outside of STACVOL. Consequently, your
hard disk contains
- The large STACVOL file
- Some uncompressed files, including DBLSPACE.BIN
and STACKER.INI
- Some free space
Once the files are stored,
1 Setup runs a version of Norton Speed Disk to
defragment STACVOL.DSK so it is in as few pieces
as possible.
2 Setup enlarges the STACVOL file to fill most of
the rest of the disk, leaving a small amount of
space uncompressed. All your new free space is
within the STACVOL file, so it will be available
on the stacked disk.
3 Setup leaves about 1 MB on the uncompressed drive
your system starts from. If it is not a "boot"
drive, Setup it leaves about 100 KB. If you use
custom Setup, you can leave more space
uncompressed.
Example
Suppose you want to compress the data on a 120 MB drive
containing about 80 MB of data. Express Setup creates a
STACVOL.DSK file and compresses all the data it can
into the file. Then it enlarges the STACVOL file to
about 119 MB leaving about 1 MB uncompressed.
If the disk isn't used for starting up, STACVOL.DSK
could be larger than 119 MB.
1.3 Establishing Access
Setup has to tell your system how to access the Stacker
drive, so it first copies a file, DBLSPACE.BIN, to your
system. At start up, MS-DOS 6 looks for this file
before it looks for any other file. When it finds this
file, it loads the Stacker driver into memory.
Because every system is different, the Stacker driver
is configured specifically for your system. Setup
creates a hidden file, STACKER.INI, to handle that
configuration. Any information found in DBLSPACE.BIN
and configured by STACKER.INI is loaded before any
other device drivers (which are normally found in
CONFIG.SYS). This is called "preloading." Before DOS 6,
data compression had to compete with every other device
driver to load into memory. Because DOS 6 has endorsed
data compression, there is no competition. . . Stacker
is loaded first!
In STACKER.INI, Setup creates lines to set the
compression speed, specify the Stacker directory, and
define the STACVOL file as another drive so it gets a
new drive letter. If these lines already exist, Setup
edits them.
At startup time, the operating system gives the new
drive (the STACVOL file) the next available drive
letter. So if you compressed the data on your only hard
disk, the drive that represents the STACVOL file gets
named D.
Setup adds SW to the STACVOL line. This swaps the drive
letters so you can refer to files on drive C, just as
you always have. The new drive letter (D) now refers to
the uncompressed drive.
Setup arranges to keep startup files found in both
Stacker drives and their uncompressed drives the same.
Example
Using that same, single 120 MB hard disk, the following
lines are placed in the STACKER.INI file:
/P=1
/DIR=C:\STACKER
C:\STACVOL.DSK, SW
The /P switch controls how fast Stacker compresses data
when it puts it on the disk. You can tune Stacker later
to change the speed to get even more compression. The
second line tells DOS where to find the Stacker files.
The last line loads the Stacker drive and assigns a
drive letter. The SW exchanges the drive letters, so
the data is still referenced by the same drive letter.
1.4 Compressing the Data on an Empty Disk
Setup compresses the space on an empty disk very
quickly, because it doesn't have to compress any
existing data. It doesn't have to exchange drive
letters either, because no current data is affected by
the new drive letter. Setup lets you choose to compress
only the free space if you wish. This is an excellent
way to prepare an empty hard disk for use.
You can compress the data on floppy disks and
removables also. Either run Setup from the Stackometer
in Windows or use the Stacker Toolbox to compress
floppies as described in your documentation. All of the
necessary statements are added to your STACKER.INI file
to recognize removable drives as Stacker drives at
start-up.
1.5 How Your System Works With Stacker
When an application reads data from a Stacker drive,
Stacker intercepts the read request and decompresses
the data, then passes it on to the application. Because
the data is compressed, the system doesn't have to read
as much data, so in most cases you won't even notice
the time it takes to decompress data. When an
application writes data to the Stacker drive, Stacker
again intercepts the data, compresses it, and writes it
to the Stacker drive. The data is always compressed
when on the disk, and is always uncompressed when in
memory or in use by another application.
Once Stacker has been set up on your disk, you use it
as before. When you read data from the disk, Stacker
decompresses the data. When you write it back to the
disk, Stacker compresses it again. Normally, you don't
even notice the process.
2.0 The STACKER.INI File
The STACKER.INI file contains the configuration
information for your Stacker device driver. It also
specifies the drive letter assignments for your Stacker
drive(s). This file is a hidden file located in the
root directory of your boot drive. Setup creates the
STACKER.INI file for you. It is updated each time you
compress additional drives (except floppies).
NOTE: Normally, you won't need to edit this file. Setup
automatically takes care of the configuration for you.
The following information details the structure of the
file and the elements you may find in it.
For an example of a sample STACKER.INI file, see
STACKER.INI Example. For more detailed information,
continue reading.
2.1 STACKER.INI Structure
The structure of the STACKER.INI file is very simple.
Each statement or switch is contained on an individual
line. All switches are found at the beginning of the
file, while all of the drive specifications are found
at the end. Unlike CONFIG.SYS, this file is not
processed on a line-by-line basis, so the order of the
switches is not important. However, the order in which
the drive specifications are found will be the order in
which they are set up.
2.2 STACKER.INI General Syntax Rules
A line can have a maximum of one item, except for
STACVOL line mounting parameters RP, SW, and NS. These
items are always the second item on a line. Spaces and
tabs are allowed before or after an "=", but not after
a "/". All text is not case-sensitive.
You may want to modify the STACKER.INI file to change
switches are cause other effects. All of the switches
do not need to be included in the file. Again, Setup
determines the appropriate ones.
2.3 Editing Your STACKER.INI File
The STACKER.INI file is a hidden file contained in the
root directory of your uncompressed boot drive. You may
either change the hidden attribute and then edit it
with any text editor, or use the STACKER.INI editor
provided by Stac. Procedures for using this editor are
outlined below.
1 Insert Stacker Disk 1 into drive A or B
2 Change to the floppy disk drive by typing its
letter followed by a colon, for example, A: and
press ENTER.
3 From the DOS prompt, type STACKER and press ENTER.
4 Note the drive letter of the uncompressed drive.
5 From the DOS prompt, type \TOOLS\STACINI drive:
where drive: is the letter of the uncompressed
drive.
6 When the lines of the file appear, edit as
required (see the switches in the following
section).
7 Press Ctrl-Z to save the file.
8 Restart your computer to put these changes into
effect.
2.4 STACKER.INI General Switches
The following section details each of the switches
which may be found in the STACKER.INI file.
* Reserves a drive letter.
/-AUTO Turns off automounting for all replaceable
drives. This saves about 2.7 KB in the driver.
/BD=x Specifies the base drive letter (x) from
which to start Stacker drives. For example, if the
first Stacker drive should be assigned to drive
letter F, this statement would read /BD=F
/C or /C=n Specifies the cluster size, if necessary.
These count as the same switch, so only one should
be found.
/DIR=<stacker path> Specifies the path where the
Stacker software is located. This switch generally
occurs at the top of the STACKER.INI file.
/EMS Indicates that Stacker's disk cache (up to 64
KB) should be stored in expanded memory, if there
is any available.
/M=nnn Sets the cache memory size to nn KB. Use any
value between 1 and 64. The amount of driver
memory required increases by whatever you specify
up to a maximum of 64 KB for the cache (The /M
switch has no effect if you use it with /EMS.)
/P=n Sets the compression tuning. Use any value
between 0 and 9. 0 turns compression tuning off;
it decreases memory requirements by 4.4 KB. You'll
have to restart your system to take advantage of
any change in tuning if you change between 0 and
any other value. If no /P switch is included,
Stacker uses /P=1 for everyday usage.
Values 0 and 1 are the fastest, with standard
compression. 9 gets the best compression but takes
a bit longer. Setup uses level 9 to get the best
possible compression while setting up your Stacker
drive.
/RP=n Sets the number of replaceable drives to reserve.
/W- Disables Windows permanent swap file pointer
updating. By default, if Stacker detects a Windows
permanent swap file on a disk that was swapped,
Stacker searches through its preset pattern for
the Windows directory and places the full path of
the Windows permanent swap file in SPART.PAR in
the Windows directory. Once this is done (the
first time you restart your system after
compressing the disks that contain the permanent
swap file), it really doesn't have to be done
again unless you make drastic changes to your
system. If you add this switch to the STACKER.INI
file, the search won't take place and you'll save
a bit of time at startup.
NOTE: Stacker checks for a Windows permanent swap
file every time you restart your system. You can
include the /W- switch to shorten startup time
even if you don't have Windows.
/W=<directory> Names the directory that contains your
permanent swap file pointer (SPART.PAR). Use this
switch if your directory has an unusual name or
isn't on the default path that Stacker searches.
If Windows can't find its permanent swap file
after you compress a disk, add this switch and
restart your system. This switch tells Stacker
exactly where to find the SPART.PAR file, saving a
bit of time on startup. Replace it with /W- after
Windows finds its swap file.
/W+<directory> Names the directory that contains your
permanent swap file. Use it if your directory has
an unusual name or isn't on the default path that
Stacker searches. It causes Stacker to search its
regular default path and find this one too, just
in case you have multiple swap files. This switch
actually lengthens the search, but ensures that it
finds all the files.
2.5 Mounting Parameters
The following parameters appear after a STACVOL
statement. These parameters specify the mounting method
for the Stacker drive. They are preceded by a comma
",".
RP Mount replaced.
NS Mount un-swapped, using the next available drive
letter.
SW Mount swapped, using the next available drive
letter.
Multiple Swapping. /SW = jk mn xy
After mounting all drives, swap drive pairs J: with K:,
M: with N:, X: with Y:, and so on. You may have no more
than 26 swaps. This option is rarely used since the
mounting parameter "sw" on the STACVOL line handles
standard swapping. The /SW = switch appears at the TOP
of the file along with the other switches, however,
swapping will not happen until all the drives have been
mounted.
For examples of a sample STACKER.INI files, see
STACKER.INI Examples.
3.0 STACKER.INI Examples
3.1 Single Hard Drive Example
In this example, the original system configuration has
just one hard drive. EMS is available. The STACKER.INI
file created by Express Setup would look like the
following:
/DIR=C:\STACKER
/P=1
/EMS
C:\STACVOL.DSK,sw
The first line specifies the directory where the
Stacker files are located. The second line sets up the
default compression tuning for the fastest speed with
standard compression. /EMS tells Stacker to use
expanded memory. The last line specifies the location
of the Stacker drive. It then swaps the drive letter
references so that all of the compressed data is found
on drive C, and the uncompressed drive is referenced by
D.
3.2 Multiple Hard Drive Example
In this second example, the system is a bit more
complex. This system also has expanded memory. It also
has a combination of five hard drives (including
removable drives). The STACKER.INI file for this
configuration might look like:
/DIR=C:\STACKER
/P=5
/EMS
/RP=2
/BD=I
/SW FM
C:\STACVOL.DSK,sw
D:\STACVOL.000,ns
*
E:\STACVOL.DSK,sw
F:\STACVOL.000,ns
G:\STACVOL.DSK,rp
Again, the first line gives the location of the Stacker
files while the second provides the compression tuning
information. In this case, the user modified the tuning
(from the Stacker Tuner) to the setting "More
compression and a bit less speed." This returns a value
of /P=5. /EMS tells Stacker to use expanded memory.
/RP=2 reserves two replaceable drive letters, while
/BD=I specifies that the first Stacker drive letter
assignment is 'I". The next line, /SW=FM swaps drive F
with drive M after all of the drives are mounted.
The next section sets up the Stacker drives and the
drive letter assignments. Note that Stacker always
takes the next available drive letter. Remember that
there were five drives originally (C-G). This means
that H is the next logical drive letter assignment.
However, since the switch /BD=I is present, the first
drive letter assignment has to be I. The following
explains the drives and their assignments.
C:\STACVOL.DSK, sw
The Stacker drive becomes drive C, and the uncompressed
drive (originally C) becomes the next available drive
letter, I.
D:\STACVOL.000,ns
Because of the "ns" mounting parameter, the Stacker
drive is not swapped and is assigned drive letter J,
while the uncompressed drive remains D.
*
Reserves the next drive letter, K.
E:\STACVOL.DSK,sw
Again swaps the drive assignments. The Stacker drive
remains E, while the uncompressed drive becomes L.
F:\STACVOL.000, ns
Because of the "ns" mounting parameter, the Stacker
drive is not swapped and is assigned drive letter M,
while the uncompressed drive remains D. Note: after all
of the drives are mounted, F and M will be switched due
to the line /SW FM.
G:\STACVOL.DSK, rp
RP specifies that the drive letter of the uncompressed
drive is assigned to the Stacker drive (G). There is no
drive letter assigned to the uncompressed drive. Any
data on it becomes unavailable after mounting.
After completing all of the assignments in STACKER.INI,
here are all of the drives and their types:
C Stacker drive
D Uncompressed drive containing the STACVOL file for
Stacker drive J
E Stacker drive
F Stacker drive (note that it is only switched once
the line /SW FM is executed)
G Stacker drive
H DOES NOT EXIST
I Uncompressed drive containing the STACVOL file for
Stacker drive C
J Stacker drive
K Reserved by the * (no data can be found here)
L Uncompressed drive containing the STACVOL file for
Stacker drive E
M Uncompressed drive containing the STACVOL file for
Stacker drive F (note that it is only switched
once the line /SW FM is executed)
4.0 Loading Stacker High
Stacker provides a device driver, STACHIGH.SYS, which
loads the Stacker device driver into either the high
end of DOS memory, or to the Upper Memory Blocks (UMB).
To load Stacker high with MS-DOS 6
1 Edit your CONFIG.SYS file
2 Place the following line in the file
DEVICEHIGH=STACHIGH.SYS
3 Save your CONFIG.SYS file
4 Restart your system for the changes to take
effect.
STACHIGH.SYS obtains its configuration information (for
the Stacker device driver) from STACKER.INI, so there
are no switches.
To load Stacker high with other memory managers,
consult your memory manager's documentation. Use
STACHIGH.SYS as the specified device driver.
5.0 MS-DOS Command Equivalents
If you type in a compression-related DOS command on a
Stacker drive, the command is automatically run. There
is no need to know both the DOS and Stacker commands.
However, some users want to know the equivalents, so
this section is provided.
DOS Command Stacker Equivalent
CHKDSK (and all parameters) CHECK (and same
parameters)
DBLSPACE/CHK CHECK
DBLSPACE/DEF SDEFRAG
DBLSPACE/LIST STACKER
DBLSPACE/MO drive: STACKER drive:
DBLSPACE/U drive: STACKER -drive:
DIR/C SDIR
DIR/C/P SDIR/P
DIR/C/H SDIR/H
DIR/C/W SDIR/W
DEFRAG SDEFRAG
DEFRAG/F SDEFRAG
DEFRAG/U SDEFRAG/Q
DEFRAG/B SDEFRAG
DEFRAG/SN SDEFRAG/SN
DEFRAG/SE SDEFRAG/SE
DEFRAG/SD SDEFRAG/SD
DEFRAG/SS SDEFRAG/SS
DEFRAG/LCD SDEFRAG/M
DEFRAG/BW SDEFRAG/M
DEFRAG/CO SDEFRAG
DEFRAG/SKIPHIGH SDEFRAG
FORMAT/S Stacker-Aware copy of
DBLSPACE.BIN is placed on
formatted disk.
SYS Stacker-Aware copy of
DBLSPACE.BIN is placed on
formatted disk.
Stacker 4.0 for Windows and DOS
Late-Breaking News
NOTE: It is a good idea to print this file so you have it for future
reference.
Contents
========
==Getting More Information about Stacker
==Getting the Best Compression
==Additions/Changes to the User's Guide
==Compatibility and Other Issues
==Upgrading from Stacker 1.x to Stacker 4.0
==Getting More Information about Stacker
========================================
Always Check Stacker Help!
--------------------------
Please note that Stacker Setup Help and the Stacker Help system in Windows
contain up-to-date information about using Stacker.
The easiest way to get detailed information about Stacker is to double-click
the Stacker Help icon in the Program Manager and then click the Search
button. Select or type in the name of the Stacker tool or procedure you need
help on and select the topic. Stacker Help contains information on such
topics as:
- DPMS and Stacker in Memory
- Stacker AutoSave
- Compressing and automounting floppy disks
- Repairing a damaged STACVOL file
Stacker Help works with Windows 3.1. If you are using Windows 3.0, you can
order a special version of Help through one of our online services. The
product support brochure explains how to reach Stac's BBS or Stac on
CompuServe.
Use STAC FAX or STAC TALK for Special Topics
--------------------------------------------
If you have an unusual configuration or are interested in specific advanced
Stacker topics, you can order information from our STAC FAX STAC TALK
system. Both services are available in the U.S. and Canada 24 hours, 7 days
a week. See your technical support brochure for information on how to reach
STAC FAX or STAC TALK. For a listing of STAC FAX topics, request STAC FAX
#1000.
==Getting the Best Compression
==============================
If you are upgrading from a previous version of Stacker, be sure to choose
Full Update when you run Stacker Setup. The Full Update option updates your
compression to Stacker 4.0's new storage format. Depending upon the size of
your disk, Full Update may take a few hours. If you upgraded Stacker but
didn't perform the Full Update, search for the topic "Updating Stacker
drives Outside of Setup" for more information on updating your drives.
==Additions/Changes to the User's Guide
=======================================
Please note the following changes and/or additions to your User's Guide:
Page 8--If you are using MS-DOS 6.2, Stacker runs SCANDISK instead of CHKDSK
while converting DoubleSpace drives to Stacker drives.
Pages 28-30--Stacker Anywhere is designed for use on computers that do not
have Stacker installed. If you are using compressed floppy disks on a
computer with Stacker, you do not need to use Stacker Anywhere. But you do
need to change your configuration so that Stacker will automatically mount
floppy disks you compress using the Stacker Toolbox. To have Stacker
automount your B drive, for example, completely exit to DOS. Then, type
C:\STACKER\ED and choose STACKER.INI from the File menu. Add the line B: on
a line by itself. Restart your computer. From now on, Stacker automatically
mounts a Stacker-compressed floppy disk you insert in the B drive.
Page 29--The Note at the bottom of the page describes a procedure for
viewing compressed data on a removable disk under both DOS and Windows. To
do this, you need to type STACKER d: where d: is the drive letter. If you
type STACKER without the drive letter, a listing of all your drives
displays.
Page 48--The last paragraph asserts that Stacker sets up your configuration
to automount when you compress a floppy disk in that drive. This is true
only if you compress the disk through Stacker Setup. If you compress the
floppy disk through the Windows Toolbox (using the Compress tool), add
either an A: or a B: (or both) to your STACKER.INI file and restart your
computer. Changing your configuration in this way sets up automounting for
the floppy disk drive.
==Compatibility and Other Issues
================================
Third-party disk optimizers
---------------------------
Disk optimizers other than the Stacker Optimizer are not effective on
Stacker drives. Please do not use optimizers such as Norton Speed Disk 7 or
PC TOOLS PRO 9.0 for DOS after you've set up Stacker on your system.
Norton Disk Doctor 7.0
----------------------
Unfortunately, Norton Disk Doctor 7.0 is not yet compatible with Stacker 4.0
drives. If you are using NDD 7, please check the option to "Skip Compression
Tests."
QEMM 7.x
--------
If you are running a version earlier than QEMM 7.03, please consider
upgrading to the latest version. For QEMM 7.01, please add the option
/B=2001 to the DEVICE=DOSDATA.SYS line in your CONFIG.SYS file. In all
versions of QEMM, at startup, the DOS-UP feature (DOSDATA.SYS) temporarily
disables your monitor and Stacker's password prompt. In your CONFIG.SYS
file, add the option: DEVICE=DOSDATA.SYS /ALTVIDEO- so the password prompt
is visible again.
QEMM Stealth mode and DOS 5
---------------------------
In Stacker's Custom Setup, please choose the "Don't Use EMS" option if you
are using QEMM's Stealth mode. Stealth mode cannot access memory using EMS.
In Stacker's Express Setup, the default is to "Use EMS" if your computer
uses 32K clusters (large drives) or if you cannot use DPMS. In these cases,
insert the option /DBF=2 on the QEMM386 line of your CONFIG.SYS file.
DPMS and 386 Max
----------------
To take advantage of DPMS and reduce your memory requirement, please add the
switch EMS=0 to your 386MAX.PRO file.
PKZIP 2.04
----------
If your computer takes advantage of Stacker's DPMS (386 or higher with 1MB
of RAM), please use the -) on the command line when using PKZIP 2.04. These
options disable PKZIP's use of a DPMI driver that interferes with DPMS. If
you want to permanently disable DPMI, add one of these options to your
PKZIP.CFG file.
DOS Screen Savers and Stacker Optimizer
---------------------------------------
Before running the Stacker Optimizer, disable the DOS mode of screen savers
such as AfterDark. They interfere with Stacker Optimizer completing its work.
Speeding Up AutoSave
--------------------
To speed up the time it takes Stacker to save header information at startup,
edit your AUTOEXEC.BAT file. Move the line C:\STACKER\CHECK /WP so it comes
after the SMARTDRV.EXE line.
Stacker for OS/2 & DOS
----------------------
Please do not install Stacker 4.0 on a system that is using Stacker for OS/2
& DOS. If you do, you won't be able to see your compressed DOS drives under
OS/2. Stacker for OS/2 & DOS does not yet take advantage of Stacker
SmartPack. If you want to install Stacker 4.0, you'll have to first remove
Stacker for OS/2. First use the UNSTACK command to decompress your data.
Then, remove the OS/2 Stacker driver STACKER.SYS and its associated files
from their directory (usually C:\STACKER\OS2). Then you can set up Stacker
4.0.
Backing Up a Stacker Drive
--------------------------
You can perform your standard backup procedure to back up files on the
Stacker drive. If you also want to back up the files on the uncompressed
drive, backup all files EXCEPT the hidden STACVOL file. (The STACVOL file
actually contains your compressed data.) Type STACKER at the DOS prompt to
determine the location of your STACVOL file. The location of the STACVOL
file will be in [brackets]. For example, on a computer with C as the Stacker
drive, the uncompressed drive is typically D [D:\STACVOL.DSK = size]. You
would back up all the files on drives C and D except the file STACVOL.DSK.
Adding a Hard Disk
------------------
When you add another hard disk to your system, DOS assigns it the next
available drive letter, usually D. The Stacker drive that previously swapped
with drive D now swaps with drive E. Stacker takes care of the drive letter
assignments so you still find your data on drive C. If your new hard disk
requires a device driver, place the hard disk device driver BEFORE the
STACKER.COM and/or STACHIGH.SYS statements in your CONFIG.SYS file.
Stacker Optimizer and 32K Cluster Drives
----------------------------------------
If you are using drives with 32K clusters, Stacker Optimizer may need
additional memory (more than the 600K needed in previous Stacker versions).
If you don't have that much conventional memory available, you can run
Stacker Optimizer with a special option. Using this option affects speed,
but allows you to run in less memory.
To run Stacker Optimizer in less memory:
1. From the DOS prompt, type SDEFRAG /buffer=#
where # is a value between 256 and 4096, inclusive
The following examples show how much memory is saved with various values:
SDEFRAG /buffer=3072 21K memory saved
SDEFRAG /buffer=2048 42K memory saved
SDEFRAG /buffer=256 78.75K memory saved
By default, SDEFRAG normally runs at /buffer=4096.
==Upgrading from Stacker 1.x to Stacker 4.0
===========================================
Before you upgrade from Stacker 1.x:
1. At the DOS prompt, type SWAPMAP and press ENTER to determine which drive
letter is being swapped with C. Write that letter here.________________
2. Insert Stacker 4.0 floppy disk #2 into its drive.
3. Type
drive:SATTRIB -R C:\AUTOEXEC.BAT
where drive: is the letter of the floppy drive where you inserted floppy
disk #2. This removes the read-only attribute from the AUTOEXEC.BAT file.
4. Type
COPY drive:\AUTOEXEC.BAT C:\
where drive: is the drive letter in which C is being swapped
(determined in step #1).
5. Type
COPY drive:\CONFIG.SYS C:\
where drive: is the drive letter in which C is being swapped
(determined in step #1).
6. Install Stacker 4.0 starting with Disk 1.
If you are using DOS 5 or an operating system that does not preload
compression, you need to add the /SYNC+ option to your STACKER.INI file to
synchronize configuration files on compressed and uncompressed drives. (From
the Stacker directory, type ED to start the editor. Then, choose STACKER.INI
from the File menu. Add the /SYNC+ on its own line anywhere in the file.)
Stacker for OS/2 & DOS - Late Breaking News
This document contains important information that is not included in the
Stacker for OS/2 & DOS User's Guide or in the Help.
If you're going to use MS-DOS 6.0 and Stacker 3.1 in conjunction with
Stacker for OS/2 & DOS, please be sure to read section 3, particularly
section 3.4.
If you're going to install OS/2 on a Stacker drive, please be sure to read
section 11.
If you're using any special or unique hardware or software with your system,
see the Help provided in SETUP. To get help in these situations:
1. From any SETUP screen, press F1.
2. Press ENTER to choose the Index.
3. Press TAB to select Hardware Considerations or Software Considerations
and press ENTER.
Contents
This document contains late-breaking information on the following topics:
1.0 Changes to Stacker for OS/2 & DOS User's Guide
1.1 Which CONFIG.SYS files are updated by UNSTACK
1.2 Order of diskette insertion when installing OS/2 2.1
1.3 Rebooting directly from POSTINST and POSTUP
1.4 Instructions for keeping SWAPPER.DAT uncompressed
2.0 Non-compression of SWAPPER.DAT
3.0 Using Stacker for OS/2 & DOS with other Stacker software
3.1 Installing Stacker 3.x after Stacker for OS/2 & DOS
3.2 Protecting EAs by using the Stacker for OS/2 & DOS utilities
3.3 CHECK /WP path
3.4 Operation with Stacker 3.1 under MS-DOS 6.0
3.4.1 Installing Stacker for OS/2 & DOS after Stacker 3.1
3.4.2 Installing Stacker 3.1 after Stacker for OS/2 & DOS
3.4.3 Accessing converted DoubleSpace drives under OS/2
3.4.4 Accessing new Stacker drives under MS-DOS 6.0
3.4.5 Error messages when booting MS-DOS 6.0
3.4.6 CONFIG.SYS on Disk 1 not updated by SETUP
3.4.7 Error messages after UNSTACK on Dual Boot systems
3.4.8 Running PREPINST and PREPUP
4.0 Rebuilding your OS/2 desktop
5.0 Creating more Stacker drives after installation
6.0 Installing without creating any Stacker drives
7.0 For users of Dual Boot systems
7.1 Safe rebooting from OS/2 to DOS
7.2 Safe rebooting from DOS to OS/2
7.3 Location of Stacker and IBM versions of BOOT.COM
7.4 If you're using a Dual Boot system with Stacker 2.0 or 3.0
8.0 Making space for UNSTACK
9.0 Damaged drives: AutoProtect and AutoRecovery
9.1 If a Stacker drive is write-protected under OS/2
10.0 Formatting a Stacker drive as HPFS: don't try this!
11.0 Installing OS/2 on an existing Stacker drive
11.1 Simplified procedure for OS/2 2.1 may be available
11.2 Slight change to procedure in Appendix B for OS/2 2.1
11.3 Installing OS/2 from a CD-ROM
11.4 Files won't migrate from other Stacker drives
11.5 OS/2 error message in POSTINST
11.6 Temporary video corruption after running MIDINST
12.0 CONFIG notes
12.1 CONFIG with optical disks
12.2 Handling of special switches in DOS CONFIG.SYS
13.0 Lost extended attribute message on CONFIG.SYS
14.0 Files not found at OS/2 startup
15.0 HPFS boot drives
16.0 Changing where Stacker for OS/2 & DOS is installed
17.0 Avoiding the SUBST command
18.0 SDEFRAG notes
18.1 Lowers fragmentation even if you don't tell it to defragment
18.2 Error 136
19.0 The DONT_DEL.ME file
19.1 CHECK and CHKDSK error messages related to DONT_DEL.ME
20.0 Creating large Stacker drives
20.1 Two Stacker drives created when one is requested
20.2 SETUP running out of memory
21.0 For users of systems with OS/2 pre-installed
21.1 Unscrambling the OS/2 logo screen
22.0 Running DOS from a disk or disk image within OS/2
23.0 GammaTech utilities
24.0 Customizing Stacker for international use
25.0 Determining free space requirements
----------------------------------------------------------------------------
1.0 Changes to Stacker for OS/2 & DOS User's Guide
1.1 Which CONFIG.SYS files are updated by UNSTACK
The User's Guide states (on page 93) that UNSTACK updates only one OS/2
CONFIG.SYS file. Actually, when UNSTACK removes a Stacker drive it updates
all the OS/2 and DOS CONFIG.SYS files it can find. It can't, however, update
a CONFIG.SYS file that's on an HPFS partition or on a hidden partition.
1.2 Order of diskette insertion when installing OS/2 2.1
Due to a late-breaking change in the installation process for OS/2 2.1,
step 10 at the bottom of page 154 in the Stacker for OS/2 & DOS User's
Guide should be changed to:
10 After you have inserted several diskettes, insert the Installation
Diskette again when OS/2 asks for it. If you're installing OS/2 2.1,
also reinsert Diskette 1 when OS/2 asks for it.
1.3 Rebooting directly from POSTINST and POSTUP
The POSTINST and POSTUP utilities both have been modified to prompt you to
press Ctrl-Alt-Del to reboot when they have completed their processing.
Accordingly, step 18 on page 156 and step 9 on page 160 of the User's Guide
can be omitted.
1.4 Instructions for keeping SWAPPER.DAT uncompressed
The directions in Appendix E of the User's Guide for telling OS/2 to use an
uncompressed drive for SWAPPER.DAT no longer apply, since this is now done
automatically, as described in the next section.
2.0 Non-compression of SWAPPER.DAT
The OS/2 swap file SWAPPER.DAT cannot be kept on a Stacker drive in this
version of Stacker for OS/2 & DOS. If SWAPPER.DAT is on a Stacker drive,
SYNC2.EXE will detect this when it runs at startup and will alter the
SWAPPATH directive in the OS/2 CONFIG.SYS to make sure that on subsequent
reboots SWAPPER.DAT will be on an uncompressed drive.
When SYNC2 has to move SWAPPER.DAT, it always tries to move it to the
uncompressed drive corresponding to the OS/2 boot drive. If there is not
enough uncompressed space on that drive, SYNC2 suggests making more free
space available by running SDEFRAG /GP. If you have more free space on a
different uncompressed drive, you may wish to edit CONFIG.SYS so that the
SWAPPATH directive instead points to the uncompressed drive with more free
space.
As mentioned above in section 1.4 of this file, the directions in Appendix E
of the User's Guide for telling OS/2 to use an uncompressed drive for
SWAPPER.DAT no longer apply, since this is done automatically.
After SYNC2 changes the SWAPPATH away from a Stacker drive, be sure to delete
the unused SWAPPER.DAT file from the Stacker drive so that it won't be taking
up space. It's normally in the directory \OS2\SYSTEM, although the SWAPPATH
directive in CONFIG.SYS can cause it to be placed in a different directory.
3.0 Using Stacker for OS/2 & DOS with other Stacker software
This section provides some additional information you need to be aware of
if you'll be using Stacker for OS/2 & DOS along with other Stacker software.
It supplements Appendix C of the Stacker for OS/2 & DOS User's Guide. Please
be sure to read that appendix as well if this section applies to you.
If you're using MS-DOS 6.0 and will be using Stacker 3.1 in conjunction with
Stacker for OS/2 & DOS, please pay particular attention to section 3.4 below.
If you're already using a DOS version of Stacker and have created a Dual Boot
system by installing OS/2 in the C drive's uncompressed free space, please
see section 7.4 of this file.
Stacker 3.x is used in this section whenever information applies to both
Stacker 3.0 and Stacker 3.1.
3.1 Installing Stacker 3.x after Stacker for OS/2 & DOS
If you install Stacker 3.x after Stacker for OS/2 & DOS, when you run the
Stacker 3.x SETUP program, choose Custom Setup, not Express Setup, and do not
let it compress any drives that you'll want to access under OS/2. Otherwise,
you risk losing the extended attributes (such as OS/2 desktop icons) of files
on those drives. It's best to just let the Stacker 3.x SETUP install the
Stacker 3.x files. To do this, run the Stacker 3.x SETUP, choose Custom
Setup, let it copy the Stacker files to the hard drive, and then choose Exit
when it asks you to select a drive to compress.
Use the Stacker for OS/2 & DOS SETUP, as described in the next section of
this file, to create new Stacker drives.
3.2 Protecting EAs by using the Stacker for OS/2 & DOS utilities
If you have Stacker 3.x on your system in addition to Stacker for OS/2 & DOS,
please be sure that after you've installed Stacker 3.x you use the Stacker
for OS/2 & DOS versions of the following utilities:
SETUP
UNSTACK
REMOVDRV
It's particularly important to observe this rule with SETUP and UNSTACK so
that the extended attributes (for example, OS/2 desktop icons) of the files
are preserved. In addition, the Stacker for OS/2 & DOS versions of the
utilities listed above update OS/2 CONFIG.SYS files, not just the DOS one,
to reflect the addition or removal of Stacker drives.
If you let the Stacker for OS/2 & DOS SETUP modify your AUTOEXEC.BAT, this
normally will cause the Stacker for OS/2 & DOS versions of the utilities to
be executed instead of the Stacker 3.x versions when you're using DOS. For
example, typing UNSTACK C: runs the Stacker for OS/2 & DOS version of
UNSTACK, not the Stacker 3.x version.
If you don't let SETUP modify your AUTOEXEC.BAT, or if you've installed
Stacker 3.x in a directory with a name other than \STACKER, you should edit
your DOS AUTOEXEC.BAT file and make sure the Stacker for OS/2 & DOS directory
precedes the Stacker 3.x directory in the PATH command.
3.3 CHECK /WP path
If you're already running a DOS version of Stacker, you should change the
path on the CHECK /WP command in your DOS AUTOEXEC.BAT to the one where
Stacker for OS/2 & DOS is installed. For example, if it now says
C:\STACKER\CHECK /WP and you installed Stacker for OS/2 & DOS in
D:\STACKER\OS2, change the command to D:\STACKER\OS2\CHECK /WP. (An OS/2
AUTOEXEC.BAT file does not need a CHECK /WP command. If you have a Dual Boot
system, then while you're running OS/2 your DOS AUTOEXEC.BAT is stored as
\OS2\SYSTEM\AUTOEXEC.DOS, not \AUTOEXEC.BAT.)
3.4 Operation with Stacker 3.1 under MS-DOS 6.0
Stacker for OS/2 & DOS is basically compatible with Stacker 3.1 when running
under MS-DOS 6.0. This section provides some information you should be aware
of if you're using that combination.
3.4.1 Installing Stacker for OS/2 & DOS after Stacker 3.1
If Stacker 3.1 is already installed, the Stacker for OS/2 & DOS SETUP will
overwrite the Stacker 3.1 files if you let it install to the same path with
"\OS2" appended. For example, if Stacker 3.1 is installed in C:\STACKER and
you install Stacker for OS/2 & DOS to C:\STACKER\OS2, then you'll lose the
Stacker 3.1 files in C:\STACKER. You can work around this problem in either
of the following two ways:
(i) Before running the Stacker for OS/2 & DOS SETUP, copy the file
\DOSUTILS\SSWAP.COM from Stacker for OS/2 & DOS Disk 1 to the directory
in which Stacker 3.1 is installed. (This will inhibit SETUP from
overwriting the Stacker 3.1 files.)
(ii) Reinstall Stacker 3.1 after Stacker for OS/2 & DOS, making sure not to
compress any drives with the Stacker 3.1 SETUP.
(iii) Install Stacker for OS/2 & DOS to a different path or drive. For
example, if Stacker 3.1 is installed in C:\STACKER, you might install
Stacker for OS/2 & DOS in D:\STACKER\OS2 or C:\STAC\OS2 instead of
C:\STACKER\OS2.
Also, the Stacker for OS/2 & DOS SETUP may insert STACKER.COM and SSWAP.COM
lines in your DOS CONFIG.SYS that will cause error messages to display when
you boot DOS. You can use a text editor to remove those lines from the
CONFIG.SYS file if you wish. This subject is also covered in section 3.4.5
below.
Finally, you should make sure that the path specified in the CHECK /WP line
near the top of your DOS AUTOEXEC.BAT file is the path where Stacker for OS/2
& DOS is installed, as described above in section 3.3 of this file.
3.4.2 Installing Stacker 3.1 after Stacker for OS/2 & DOS
If you install Stacker 3.1 in the parent of the directory where Stacker for
OS/2 & DOS is installed, the DOS-specific Stacker for OS/2 & DOS files, in
particular STACKER.COM and SSWAP.COM, will be overwritten. This doesn't do
any harm, however.
After installing Stacker 3.1, you should make sure that the path specified in
the CHECK /WP line near the top of your DOS AUTOEXEC.BAT file is the path
where Stacker for OS/2 & DOS is installed, as described above in section 3.3
of this file.
3.4.3 Accessing converted DoubleSpace drives under OS/2
When you convert a DoubleSpace drive using Stacker 3.1, one more step is
required before you can access it under OS/2. You must run SDEFRAG d: /R
(where d: is the drive letter of the converted drive), using the Stacker 3.1
SDEFRAG, to recompress the data. Until then, the drive can't be accessed
under OS/2 or when you boot from Stacker for OS/2 & DOS Disk 1.
When you run SDEFRAG for this purpose, you need to specify the directory in
which Stacker 3.1 is installed to make sure the correct version of SDEFRAG is
run. That's because, as described above, the Stacker for OS/2 & DOS directory
probably precedes the Stacker 3.1 directory in your PATH command, and only
the Stacker 3.1 SDEFRAG program can recompress the converted drive. The
Stacker for OS/2 & DOS version of SDEFRAG will display an error message if
you try to use it on such a drive.
Most commonly, Stacker 3.1 will be installed in C:\STACKER, in which case
you would type C:\STACKER\SDEFRAG d: /R (where d: is the drive letter of the
converted drive) and press Enter.
3.4.4 Accessing new Stacker drives under MS-DOS 6.0
After you use the Stacker for OS/2 & DOS SETUP to create a Stacker drive,
which is the way to ensure the files' extended attributes are preserved,
you need to run the Stacker 3.1 CONFIG program to make sure that drive
can be accessed under MS-DOS 6.0.
When you run CONFIG for this purpose, you need to specify the directory in
which Stacker 3.1 is installed to make sure the correct version of CONFIG is
run. Most commonly, Stacker 3.1 will be installed in C:\STACKER, in which
case you would type C:\STACKER\CONFIG and press Enter.
3.4.5 Error messages when booting MS-DOS 6.0
The Stacker for OS/2 & DOS SETUP and CONFIG commands may insert STACKER.COM
and SSWAP.COM lines in your DOS CONFIG.SYS file. This will cause error
messages to display when you boot MS-DOS 6.0, but will otherwise do no harm.
You can use a text editor to remove those lines from the CONFIG.SYS file if
you wish.
3.4.6 CONFIG.SYS on Disk 1 not updated by SETUP
When you boot from Stacker for OS/2 & DOS Disk 1 and run SETUP, the
CONFIG.SYS file on that disk may not be updated if Stacker 3.1 is on your
system. If you find that when you boot Disk 1 you can't access some or all
of your Stacker drives, run CONFIG, accept the CONFIG.SYS changes it offers
to make, and reboot with Disk 1.
3.4.7 Error messages after UNSTACK on Dual Boot systems
On a Dual Boot system, UNSTACK may not update the OS/2 CONFIG.SYS file; when
you reboot OS/2 you will get a message that the drive you removed cannot be
mounted. Running CONFIG under OS/2 will make the necessary update to the
CONFIG.SYS file.
3.4.8 Running PREPINST and PREPUP
PREPINST and PREPUP should be run by booting from Stacker for OS/2 & DOS Disk
1 if Stacker 3.1 is on your system. Otherwise, they may complain that the
drive on which you want to install or update OS/2 isn't swapped, even though
it is.
4.0 Rebuilding your OS/2 desktop
If you use Alt+F1 while rebooting to rebuild the desktop on a compressed OS/2
boot drive, you won't be able to boot OS/2 from that drive subsequently. To
avoid this problem, enter these commands before using Alt+F1:
COPY d:\OS2\INSTALL\CONFIG.SYS d:\OS2\INSTALL\CONFIG.SAV
COPY d:\CONFIG.SYS d:\OS2\INSTALL\CONFIG.SYS
where d: is the compressed OS/2 boot drive.
As a result of the first COPY command above, the original CONFIG.SYS that
OS/2 saved in the OS2\INSTALL directory will still be there, but under the
name CONFIG.SAV.
5.0 Creating more Stacker drives after installation
If you run SETUP from Stacker for OS/2 & DOS Disk 1, it will assume that you
want to reinstall the Stacker files to the hard drive. To avoid this when
you've already done the installation and only want to create additional
Stacker drives, run SETUP from the directory where you installed it on the
hard drive. If you've booted from Disk 1, the easiest way to do this if you
don't remember the installation path is to enter the command
TYPE INSTPATH.TXT
which will show you the path where Stacker for OS/2 & DOS was installed (for
example, C:\STACKER\OS2\) and run SETUP from there (for example, type
C:\STACKER\OS2\SETUP and press Enter).
This is potentially more complicated if you have HPFS drives on your system,
as the drive letter given in INSTPATH.TXT is the OS/2 drive letter, and the
DOS drive letter may be lower. For example, let's say you installed Stacker
for OS/2 & DOS in E:\STACKER\OS2 and INSTPATH.TXT will say E:\STACKER\OS2\.
However, if your D drive is an HPFS drive, then the drive that's called E:
when you're in OS/2 or in SETUP is called D: under DOS because DOS skips over
the HPFS drive, so you would run SETUP by typing D:\STACKER\OS2\SETUP instead
of E:\STACKER\OS2\SETUP. (Within SETUP, all drives are referred to by their
OS/2 drive letters.)
6.0 Installing without creating any Stacker drives
Here's the cleanest way to install Stacker for OS/2 & DOS without creating
any new Stacker drives. Run SETUP and select Custom installation (as opposed
to Express). If a version of Stacker isn't already present on your system,
you'll be prompted for the directory in which to copy the Stacker files.
After SETUP has copied the files, you'll be asked whether you want the PATH
command in your AUTOEXEC.BAT updated (recommended answer: yes) and then
you'll see a screen with buttons labeled Restart, Don't Restart, and Exit.
Select Exit at this point. (It would work to exit from SETUP at any time
after the files have been copied, but this way you don't spend any more time
in SETUP than you have to.)
7.0 For users of Dual Boot systems
This section contains important information for users of Dual Boot systems;
that is, systems where both DOS and OS/2 boot from the C drive. Stacker for
OS/2 & DOS installs its own version of BOOT.COM, as the one that comes with
OS/2 doesn't work if the C drive is a Stacker drive.
7.1 Safe rebooting from OS/2 to DOS
On Dual Boot systems, before entering BOOT /DOS to reboot into DOS you must
make sure to shut down all applications. This is true of the IBM BOOT.COM as
well as the Stacker for OS/2 & DOS BOOT.COM.
7.2 Safe rebooting from DOS to OS/2
If you use a disk cache utility under DOS that performs "lazy writes" (that
is, it doesn't write data to the disk right away), be sure to flush or
disable the cache before running the BOOT /OS2 command. One symptom of
needing to do this is that the computer reboots back into DOS instead of
booting OS/2.
7.3 Location of Stacker and IBM versions of BOOT.COM
On your OS/2 boot drive, SETUP renames \OS2\BOOT.COM to OS2BOOT.COM and
copies the Stacker for OS/2 & DOS version of BOOT.COM into the \OS2
directory. If you have more than one OS/2 boot drive, SETUP asks you which
one you want to have CONFIG.SYS updated on, and this is the one on which
\OS2\BOOT.COM is updated.
If you compress that OS/2 boot drive, neither \OS2\BOOT.COM nor
\OS2\OS2BOOT.COM is kept on the uncompressed drive. However, the Stacker
for OS/2 & DOS version of BOOT.COM is kept on the uncompressed drive, in the
directory where Stacker for OS/2 & DOS is installed (typically \STACKER\OS2).
7.4 If you're using a Dual Boot system with Stacker 2.0 or 3.0
A number of users of Stacker 2.0 or Stacker 3.0 for Windows and DOS who
couldn't wait for Stacker for OS/2 & DOS have set up Dual Boot systems on
which the C drive is a Stacker drive. They've done this by installing OS/2 in
the C drive's uncompressed space. On such a system, rebooting from DOS to
OS/2 would normally be a problem because the physical C drive is swapped with
a different drive, which throws off IBM's BOOT.COM. However, these ingenious
folks have solved this problem by rerunning SSWAP.COM before BOOT /OS2 (for
example, if C: is swapped with E:, they would enter SSWAP C: E:). That way,
C: is what the IBM BOOT.COM expects it to be, namely the physical C drive.
If you're not one of these users, you can ignore the rest of this section.
If you are one of these users, your preferred course of action is to run
UNSTACK on your existing C drive, then install Stacker for OS/2 & DOS and
turn the whole drive, including OS/2, into a new Stacker drive. That way,
you'll be able to see all your data under both OS/2 and DOS. If you're
currently using Stacker 2.0, in which case you don't have UNSTACK, you can
use the Stacker for OS/2 & DOS UNSTACK as follows:
1. Boot with the Stacker for OS/2 & DOS Disk 1 in the A drive
2. Update A:\CONFIG.SYS by running CONFIG.
3. Reboot with Disk 1 still in the A drive.
4. Run UNSTACK to remove Stacker drive C.
After you've run UNSTACK, you can run the Stacker for OS/2 & DOS SETUP.
If for some reason you don't run UNSTACK before the Stacker for OS/2 & DOS
SETUP, you need to be aware of two issues:
1. If you run SETUP with the Stacker drive C mounted and swapped (the way
you normally run your system), SETUP will not modify the OS/2 CONFIG.SYS and
AUTOEXEC.BAT files, which are stashed away as C:\OS2\SYSTEM\CONFIG.OS2 and
C:\OS2\SYSTEM\AUTOEXEC.OS2 when you're running DOS. The next time you reboot
to OS/2, you'll need to do two things:
(i) Run CONFIG to update your OS/2 CONFIG.SYS
(ii) Edit the OS/2 AUTOEXEC.BAT to put the Stacker for OS/2 & DOS path (which
is C:\STACKER\OS2 if you accepted the default) in the PATH command.
2. If you run SETUP without the Stacker drive C mounted, it will not install
Stacker for OS/2 & DOS on the C drive. However, if you have another drive
that isn't compressed, you can install Stacker for OS/2 & DOS there. In that
case, SETUP will update your OS/2 CONFIG.SYS and AUTOEXEC.BAT files, unlike
the preceding case.
8.0 Making space for UNSTACK
UNSTACK may tell you that you must make more space on the uncompressed drive.
If you're unstacking an OS/2 boot drive, the easiest way to make lots of
space may be to delete the SWAPPER.DAT file, which normally will be in the
\OS2\SYSTEM directory on the uncompressed drive. (If you're not sure which
drive is the uncompressed one, run SWAPMAP. For example, if you're about to
unstack drive D, look for the drive that SWAPMAP says was drive D at boot
time.)
If you decide to make more space by deleting other files, it's best to boot
OS/2 and delete the files, so that the extended attributes of files you
delete aren't left dangling. Then run CHECK (in a DOS session) and the OS/2
CHKDSK to make sure the Stacker drive is clean, and reboot into DOS. If CHECK
reported any errors, run CHECK /F, and finally run UNSTACK again.
9.0 Damaged drives: AutoProtect and AutoRecovery
The AutoProtect(TM) feature mentioned on the Stacker for OS/2 & DOS box is
the feature that if a Stacker drive is seriously damaged it is automatically
write protected at startup, under both OS/2 and DOS, to prevent any further
loss of data. The AutoRecovery(TM) feature mentioned on the box is the
automatic repair of such damaged drives under DOS.
Damaged Stacker drives that have been write protected are automatically
repaired when you boot DOS, assuming the CHECK /WP command that SETUP puts
in your DOS AUTOEXEC.BAT is still present.
9.1 If a Stacker drive is write-protected under OS/2
When OS/2 is starting up, if the Stacker driver (STACKER.SYS) write-protects
a damaged Stacker drive it displays a message to that effect and asks you to
press a key to continue. At this point, you should let OS/2 finish booting
(if it will), then shut down OS/2 and boot DOS. Assuming your DOS
AUTOEXEC.BAT has the CHECK /WP command in it, your drive will automatically
be repaired at that point; this is the AutoRecovery feature. Otherwise, run
CHECK d: /F (where d: is the drive letter of the damaged drive) to repair it.
10.0 Formatting a Stacker drive as HPFS: don't try this!
If you try to reformat a Stacker drive as an HPFS drive, the format operation
may "succeed" but the Stacker drive will be rendered useless. Of course, all
the data on the drive will be lost, as in any formatting operation.
11.0 Installing OS/2 on an existing Stacker drive
Please read this section before installing OS/2 on an existing Stacker drive.
11.1 Simplified procedure for OS/2 2.1 may be available
If you're installing OS/2 2.1 and you have a modem, check Stac's BBS or
the Stacker CompuServe forum. We expect to be posting software soon in
both places that allow OS/2 2.1 to be installed on a Stacker drive with
considerably fewer steps than the method given in Appendix B of the User's
Guide. Consult the HOW TO REACH US brochure in your Stacker for OS/2 & DOS
package for information on Stac's BBS and the CompuServe forum.
11.2 Slight change to procedure in Appendix B for OS/2 2.1
If you're installing OS/2 2.1 on a Stacker drive using the method in Appendix
B of the User's Guide, pretend that step 10 at the bottom of page 154 says:
10 After you have inserted several diskettes, insert the Installation
Diskette again when OS/2 asks for it. If you're installing OS/2 2.1,
also reinsert Diskette 1 when OS/2 asks for it.
11.3 Installing OS/2 from a CD-ROM
If you're installing OS/2 from a CD-ROM, the instructions in Appendix B of
the User's Guide for installing on a Stacker drive still apply. Where the
instructions refer to the OS/2 Installation Diskette and OS/2 Diskette 1,
use the two diskettes that came with the CD-ROM.
11.4 Files won't migrate from other Stacker drives
During OS/2 installation, "Migrate Applications" and "Configure WIN-OS/2
Desktop" will not find files on any Stacker drive other than the drive on
which you're installing OS/2.
11.5 OS/2 error message in POSTINST
If you get an error message from OS/2 while running POSTINST to reinstall
OS/2 on a Stacker drive, select "Return error code to application."
This error occurs when POSTINST tries to replace the OS/2 BOOT.COM with the
Stacker for OS/2 & DOS version, if that replacement has already been done.
No harm is done by this error.
11.6 Temporary video corruption after running MIDINST
While installing OS/2 on a Stacker drive using PREPINST, MIDINST, and
POSTINST, you may see some video corruption. Specifically, when OS/2 is
rebooting from the target drive after you run MIDINST, the OS/2 rings may
appear out of sync and there may be a series of vertical lines near the top
of the screen. This goes away in a few seconds and is harmless.
12.0 CONFIG notes
This section provides some further information on the CONFIG command.
12.1 CONFIG with optical disks
If you run CONFIG in a DOS session under OS/2 with an optical drive mounted
that has no disk in it, OS/2 will display a SYS0039 error, saying the drive
is not ready. If this happens, select "Return error code to application" and
CONFIG will continue normally.
12.2 Handling of special switches in DOS CONFIG.SYS
When you run CONFIG under DOS, the Stacker lines that it offers to insert in
in your DOS CONFIG.SYS are strictly "vanilla." STACKER.COM switches that
don't start with a slash (such as @ and *) are not preserved, nor are
special driver loading directives such as DEVICEHIGH. Also, SSWAP.COM lines
inserted by CONFIG use the /SYNC switch, not /SYNC+.
If you press Y to accept the changes CONFIG suggests, the old lines are left
in the CONFIG.SYS (with a REM in front so they're ignored), so they're right
there to refer to if you decide to edit the file to restore any of the
previous switches or directives.
13.0 Lost extended attribute message on CONFIG.SYS
The OS/2 CHKDSK may give you a "lost extended attribute" message after you
run SETUP, UNSTACK, or REMOVDRV if your OS/2 CONFIG.SYS had an extended
attribute. Those programs do not preserve the extended attribute of
CONFIG.SYS. By default, CONFIG.SYS has no extended attribute; when it
does have one, it's generally just a file type whose loss does no harm.
14.0 Files not found at OS/2 startup
Installation of some OS/2 software packages may insert DEVICE= lines at the
top of the OS/2 CONFIG.SYS file, before the STACKER.SYS and SSWAP2.SYS lines.
The next time you reboot OS/2, these new drivers may display error messages
saying they can't find certain files; the reason is that those files are on a
Stacker drive which, because the Stacker driver hasn't been loaded yet, can't
be accessed yet.
The solution is to edit the OS/2 CONFIG.SYS and move the Stacker-related
lines (the ones that mention STACKER.SYS, SSWAP2.SYS, FATMGR.EXE, and
SYNC2.EXE) to the top of CONFIG.SYS, making sure to keep them in their
original order.
15.0 HPFS boot drives
If you have an OS/2 boot drive formatted as an HPFS drive, the CONFIG.SYS and
AUTOEXEC.BAT files on that drive will not be updated by SETUP, UNSTACK, and
REMOVDRV, since these programs run under DOS and therefore cannot access HPFS
drives. To bring this drive up to date, boot from it and run CONFIG to update
the CONFIG.SYS file. You may also wish to use a text editor to insert the
path where you've installed Stacker for OS/2 & DOS in the AUTOEXEC.BAT file's
PATH statement, so that the Stacker utilities will be directly available. For
example, if you've installed Stacker for OS/2 & DOS in C:\STACKER\OS2, you
would change the PATH statement from
PATH D:\OS2;D:\OS2\MDOS
to
PATH D:\OS2;D:\OS2\MDOS;c:\stacker\os2
16.0 Changing where Stacker for OS/2 & DOS is installed
After you've installed Stacker for OS/2 & DOS, it's inadvisable to try to
move it to a different directory or to give the directory that it's in a new
name (for example, to install in \STACKER\OS2 and then by renaming
directories change it to \ST\O2). If you absolutely must change the path
of the Stacker files, you need to replace the old Stacker path with the new
one every time it occurs in the following files:
(i) All OS/2 and DOS CONFIG.SYS files containing Stacker commands. This
includes the CONFIG.SYS on the second diskette in the set of Stacker-
aware OS/2 boot diskettes you made with STACBOOT. It also includes
C:\OS2\SYSTEM\CONFIG.DOS on a Dual Boot system where you're currently
running OS/2.
(ii) All OS/2 and DOS AUTOEXEC.BAT files. This includes
C:\OS2\SYSTEM\AUTOEXEC.DOS on a Dual Boot system where you're currently
running OS/2.
(iii) \OS2\SYSTEM\CONFIG.OS2 and \OS2\SYSTEM\AUTOEXEC.OS2 on a Dual Boot
system where you're currently running DOS.
(iv) INSTPATH.TXT on Stacker for OS/2 & DOS Disk 1 and Disk 2 and in the
directory to which you've moved Stacker.
If you have HPFS drives on your system, the path may be different under DOS
than it is under OS/2 because DOS skips over HPFS drives. The DOS CONFIG.SYS
and AUTOEXEC.BAT files (including CONFIG.DOS and AUTOEXEC.DOS) should use
the DOS drive letter. The OS/2 CONFIG.SYS and AUTOEXEC.BAT files (including
CONFIG.OS2 and AUTOEXEC.OS2), plus all the INSTPATH.TXT files, should use the
OS/2 drive letter.
17.0 Avoiding the SUBST command
Avoid using SUBST to assign a new drive letter to a directory on a Stacker
drive. If you must do this, it is advisable to remove the mounted drive
before running any Stacker utilities, such as CHECK. If x: is the drive
letter of the mounted drive, SUBST x: /D will remove it.
18.0 SDEFRAG notes
This section provides some further information on the SDEFRAG command.
18.1 Lowers fragmentation even if you don't tell it to defragment
SDEFRAG performs certain kinds of cleanup even if you decline to actually
defragment the drive, so it and the other utilities that report on the
fragmentation level (CHECK and REPORT) may display a lower number than
before.
18.2 Error 136
If you run SDEFRAG /GP to change the physical size of a Stacker drive and
get a message that says SIZE CHANGE ERROR 136, create a new subdirectory in
the root directory of the Stacker drive that alphabetically precedes all
the others (e.g., \aaaaa), copy some files into it, and rerun SDEFRAG /GP.
19.0 The DONT_DEL.ME file
Under OS/2, the root directory of every Stacker drive contains a hidden file
called DONT_DEL.ME. Its size is continuously monitored and adjusted as
necessary by FATMGR.EXE to ensure that the drive never runs out of physical
space while OS/2 thinks it still has logical free space (free clusters) left.
Even if DONT_DEL.ME is huge, it's not using up any physical space on your
Stacker drive -- it's just making sure OS/2 won't try to write data to the
drive when there isn't enough room. Deleting it won't let you fit more data
on the drive, and FATMGR will just create it again in a few seconds anyway.
Hence the name DONT_DEL.ME!
When a Stacker drive is almost full, FATMGR increases the size of DONT_DEL.ME
more aggressively due to the greater risk of running out of space. This
effectively limits the capacity of small (less than 5 megabyte) Stacker
drives, since they're treated as almost full from the outset.
DONT_DEL.ME is automatically deleted when OS/2 shuts down, and also when
DOS boots up (the latter is courtesy of the CHECK /WP line in the DOS
AUTOEXEC.BAT). A different method is used under DOS for managing the free
space, so it's not appropriate to have DONT_DEL.ME present under DOS.
19.1 CHECK and CHKDSK error messages related to DONT_DEL.ME
You may see CHECK and CHKDSK report errors such as "File length error" on the
DONT_DEL.ME file. These are generally harmless and are due to the file not
having been closed since the last time its length changed. There would be a
substantial performance impact if FATMGR closed DONT_DEL.ME each time the
file length changed.
If you run CHKDSK /F on a Stacker drive under OS/2, CHKDSK may report that it
cannot access the drive because it is locked or in use by another process.
This may be because DONT_DEL.ME is open. Wait 10 to 20 seconds and try
running CHKDSK again; if no other programs are writing or deleting files on
that drive, FATMGR will close DONT_DEL.ME in the meanwhile and CHKDSK /F
should proceed.
20.0 Creating large Stacker drives
This section covers some situations you may run into when creating large
Stacker drives, i.e., larger than 512 megabytes.
20.1 Two Stacker drives created when one is requested
When you compress a large drive, you may find that you end up with two
Stacker drives instead of just one. The reason is that we avoid using 16K
clusters (the units in which space is allocated to files) if we can use 8K
ones, and avoid using 32K ones if we can use 16K. Smaller clusters can allow
more data to be stored on a drive, but they limit the size of the drive; 8K
clusters allow up to a 512 megabyte drive, and 16K clusters allow up to a 1
gigabyte drive. When you compress an entire drive, the existing data on the
drive always goes onto a single drive, regardless of the cluster size that
requires.
You can enforce a given cluster size when creating a new Stacker drive by
going into SETUP's Advanced Options (during a Custom Setup) and selecting
that cluster size.
20.2 SETUP running out of memory
If you attempt to create a Stacker drive with 16K or 32K clusters by
compressing a drive that has 32K clusters and has extended attributes on
it, you will probably get an "insufficient memory" error message and the
Stacker drive will not be created. The workaround is to remove enough data
from the drive you wish to compress so that it has less than 1,024,000,000
bytes of data on it, and rerun SETUP to compress the drive. SETUP will now
create two Stacker drives with 16K clusters, as described above in section
20.1.
21.0 For users of systems with OS/2 pre-installed
If your system was preloaded with OS/2, then it probably didn't come with
OS/2 installation diskettes. In that case, you need to make your own OS/2
utility diskettes and use copies of those diskettes whenever the Stacker for
OS/2 & DOS User's Guide asks you to use copies of the OS/2 installation
diskettes. With at least some systems, the procedure for making the utility
diskettes is documented in a manual called "Using the Welcome Folder," in a
section called "Creating Utility Diskettes."
The procedure for creating utility diskettes results in three diskettes,
which are supposed to be labeled Utility Diskette 1, 2, and 3. Use Utility
Diskette 1 whenever the Stacker for OS/2 & DOS User's Guide tells you to use
the OS/2 Installation Diskette, and use Utility Diskette 2 whenever the
User's Guide tells you to use OS/2 Diskette 1.
You'll need copies of the first two Utility Diskettes in order to run
STACBOOT, which will turn them into "Stacker-aware" OS/2 boot diskettes that
can be used to repair errors on drives that might otherwise be locked if you
booted in the usual way.
21.1 Unscrambling the OS/2 logo screen
If your system was preloaded with OS/2, then you may get garbage on your
screen early in the process of booting of OS/2 if you've compressed the OS/2
boot drive. This doesn't affect the operation of OS/2 or Stacker, but you can
use this command to clean up the screen:
XCOPY od:\OS2\INSTALL\PRELOAD\WELCOME.RGB ud:\OS2\INSTALL\PRELOAD\
where od: is the compressed OS/2 boot drive and ud: is the corresponding
uncompressed drive. You can determine the latter by running SWAPMAP in a DOS
session under OS/2. For example, if C: is the compressed OS/2 boot drive,
SWAPMAP might display the following (among other information):
Drive C: was drive E: at boot time
Drive E: was drive C: at boot time
This tells you that the uncompressed drive is E:. You would then enter
XCOPY C:\OS2\INSTALL\PRELOAD\WELCOME.RGB E:\OS2\INSTALL\PRELOAD\
22.0 Running DOS from a disk or disk image within OS/2
The information in this section applies to running a specific version of DOS
from within OS/2. For example, you can start up an MS-DOS 4.0 session by
inserting an MS-DOS 4.0 boot diskette in the A drive and double-clicking on
the "DOS from Drive A:" icon in the Command Prompts folder. In general, you
can start up such a DOS session from a diskette, from a hard drive (normally
C:), or from a disk image created by VMDISK.
This section does not apply to regular DOS Window or DOS Full-screen sessions
within OS/2, nor does it apply to rebooting from OS/2 to DOS on a Dual Boot
system via the BOOT /DOS command or the Dual Boot icon.
When running a specific version of DOS within OS/2, you can access all the
Stacker drives in that session that you can normally access in OS/2, provided
the CONFIG.SYS used by that session contains a DEVICE=FSFILTER.SYS line.
OS/2's on-line help contains further information on FSFILTER.SYS.
The results are unpredictable if you run DOS in this manner from a disk or
disk image that itself mounts Stacker drives or runs Stacker utilities. You
should make sure the disk's CONFIG.SYS doesn't load STACKER.COM or SSWAP.COM
and that its AUTOEXEC.BAT doesn't run CHECK, before booting DOS from it
within OS/2.
23.0 GammaTech utilities
A trap 000E with possible data corruption may occur if you try to run the
GammaTech Analyze, Sector-Edit, or Sentry utilities on a Stacker drive. The
utilities themselves may be stored a Stacker drive, but you should not tell
them to operate on a Stacker drive.
24.0 Customizing Stacker for international use
By default, Stacker uses a standard United States keyboard and conventions
for date, time, and characters. You can tell Stacker that you use a different
keyboard layout and request country-specific conventions for date, time, and
characters if necessary. The \INTL directory on Stacker for OS/2 & DOS Disk 1
includes new files for use in these countries:
Code Country
FR France
GR Germany
IT Italy
JA Japan
NL Netherlands
PO Portugal
SP Spain
UK United Kingdom
ENG To revert to the standard English version after changing it
BEFORE RUNNING SETUP FOR THE FIRST TIME:
Modify Stacker for OS/2 & DOS to suit your computer following these steps:
1. Start your computer as usual.
2. Get to a DOS command line; a DOS session within OS/2 is fine.
3. Insert Stacker for OS/2 & DOS Disk 1 into drive A.
4. Type A:\INTL\LANGUAGE code where code is one of the choices in the table
above (for example, A:\INTL\LANGUAGE GR for Germany) and press ENTER.
5. Restart your computer using this disk to run SETUP.
Whenever your computer restarts into DOS from this disk, it will use the
appropriate keyboard and country settings.
The LANGUAGE batch file runs the KEYB and COUNTRY commands to make your
computer respond appropriately. KEYB specifies the keyboard layout in use,
while COUNTRY determines the appropriate date, time, currency, character
sort, and filename validity for the computer.
Using any keyboard other than the standard United States English layout uses
a bit more memory. If you find that you run out of memory after customizing
it for your language, use A:\INTL\LANGUAGE ENG to restore it to the default
settings. You'll be able to use it, but the keyboard and displayed values
will be in their default state.
25.0 Determining free space requirements
Currently Setup allows you to compress an entire drive as long as you have at
least 1% plus 45K free, or compress free space if you have at least 100K
free. However, if you are trying to compress a drive that has particularly
large clusters, you may receive an error message indicating that Setup cannot
continue because the disk is full. If this happens to you, you can use the
following procedure to determine the free space requirements.
1. Determine the Number of Sub-Directories using the CHKDSK command.
This is the "Number of Directories" (not the bytes).
Write that number here._________________________________
2. Determine Stacker's Working Drive Size using the CHKDSK command.
This is the "Bytes Total Disk Space."
Write the number of bytes here._________________________
3. Determine the amount of data you have on your disk using the CHKDSK
command. This is:
Bytes determined in #2 _____________________________
- "Bytes Available on Disk"_____________________________
= _____________________________
4. Determine the STACVOL cluster size on your drive in bytes using the
following table. Locate your drive size (the number of bytes determined
in #2) in the first column. Locate your data size (the number of bytes
determined in #3) underneath the Data Size heading. The cluster size for
your drive is displayed in the column beneath the range in which your
data size falls.
Write the number of bytes here.________________________
Drive Size | Data Size
|0 - 1,023,999,999 |1,024,000,000 - 2,147,483,648
| STACVOL Cluster Size
----------------------------------------------------------------------------
0 - 460,799,999| 8,192 | N/A
460,800,000 - 921,599,999| 16,384 | N/A
921,600,000 - 2,147,483,648| 16,384 | 32,768
----------------------------------------------------------------------------
5. Multiply the number from #1 by the number of bytes from #4.
Write that value here.________________________
6. Multiply .006 by the number of bytes from #2.
Write that value here.________________________
7. Add the two values calculated in #5 and #6. This is the free space
requirement for compressing the drive.
Write that value here.________________________
8. Remove data from your drive until the amount of free space you have on
your disk (see #3) is at least this size.
********************************************************************
* SuperStor version 2.04 Release Notes *
********************************************************************
1. If a. you are running under any version of Microsoft WINDOWS
(up to and including Version 3.1),
AND
b. you have not loaded the SuperStor driver (SSTORDRV.SYS)
through your "config.sys" file,
AND
c. you wish to use a Transportable Compressed floppy (or TCF)
THEN
please note that you MUST first quit WINDOWS and then run
either "2XON.COM" or "2XOFF.COM" as you may need.
2. SuperStor 2.04 is compatible with WINDOWS 3.1.
Notes regarding SuperStor in the WINDOWS 3.1 README.TXT file
are not applicable to SuperStor versions 2.0 and above.
There are, however, some issues related to the SMARTDRV.SYS
and SMARTDRV.EXE programs that you must be fully aware of.
Please study the document titled "ADDITIONAL NOTES ON SUPER-
-STOR 2.0 FOR USERS OF SMARTDRV OR WINDOWS 3.x" carefully
before you start using SuperStor. The document is included in
your product package.
3. If you find your SuperStor disk mounting as a read-only disk:
a. run SSUTIL from the read-only disk or the distribution floppy
b. choose the "Repair" option under the "Analysis" menu item
c. run "Repair" over the read-only disk
d. exit SSUTIL and the drive should be fixed
4. If you get a "Disk Structure Error" while running "Defragment":
a. terminate SSUTIL
b. run DOS CHKDSK (run CHKDSK /f if CHKDSK reports problems)
c. run SSUTIL and select the "Repair" option under the "Analysis" menu
d. follow the instructions "Repair" issues or reboot the machine
if "Repair" completes successfully and reports that the drive is OK.
5. DO NOT run disk cache utilities while preparing a SuperStor disk.
Before running the "Prepare" option of SSTOR, remove (REM) the
references to any disk cache utilities from your "config.sys" and
"autoexec.bat" files and reboot your machine to remove the disk
cache from memory. We also recommend that you disable your disk cache
while running any option under the SSUTIL menu items "Analysis" and
"Disk Tuneup". For normal operation, your disk cache is ok.
6. DO NOT use a commercial defragmenter on a "compressed" drive.
SSUTIL has a defragmenting utility that is specifically
designed for SuperStor compressed data. Commercial defragmenters
will NOT produce a well organized compressed disk, and in some
cases actually DECREASE the read/write speed of compressed data.
There is nothing wrong however, with running your commercial
defragmenter over a disk that is not controlled by "sstordrv.sys".
If, for example, your drive "C:" is compressed, you could boot from
a floppy and then run your defragmenter over drive "C:".
7. You should NOT compress your bootable partition if you use DMDRIVER.
DMDRIVER should come before the SuperStor driver in the
"config.sys" file. When creating mountable disks on DMDRIVER
partitions, you must determine the sector size of the DMDRIVER
partition and set the '/MAXSS=' on the SuperStor driver line
to that number.
8. SuperStor software is compatible with Multisoft PC-KWIK 2.0.
It is also compatible with many other speed enhancing software
packages. For a complete list, please call the AddStor
Technical Support line.
This diskette contains the file PKZ204e.EXE. Type PKZ204e followed by pressing the Enter key to create the program and documentation files for PKUNZIP, PKZIP, and PKSFX version 2.04e To print the documentation files after running PKZ204e, type COPY *.DOC PRN followed by the return key. If you distribute PKUNZIP, PKZIP, and PKSFX to friends, associates, or to a computer bulletin board system (BBS), please distribute the file PKZ204e.EXE rather than the individual files for PKUNZIP, PKZIP and PKSFX.
This diskette contains the file PKZ204g.EXE. Type PKZ204g followed by pressing the Enter key to create the program and documentation files for PKUNZIP, PKZIP, and PKSFX version 2.04g To print the documentation files after running PKZ204g, type COPY *.DOC PRN COPY *.NEW PRN COPY *.204 PRN COPY *.TXT PRN following each line by the return key. See the files V204G.NEW, WHATSNEW.204 and ADDENDUM.DOC for more information about features and changes made in this version of the software. If you distribute PKUNZIP, PKZIP, and PKSFX to friends, associates, or to a computer bulletin board system (BBS), please distribute the file PKZ204g.EXE rather than the individual files for PKUNZIP, PKZIP and PKSFX.
This diskette contains the file PKZ102.EXE. Type PKZ102 followed by pressing the Enter key to create the program and documentation files for PKUNZIP, PKZIP, and PKSFX version 1.02. To print the documentation files after running PKZ102, type COPY *.DOC PRN followed by the return key. If you distribute PKUNZIP, PKZIP, and PKSFX to friends, associates, or to a computer bulletin board system (BBS), please distribute the file PKZ102.EXE rather than the individual files for PKUNZIP, PKZIP and PKSFX. REZIP ----- Thomas Atkinson has graciously allowed us to include his REZIP program with this release of PKZIP. The REZIP program can be used to convert existing .ZIP files to the new improved compression in PKZIP version 1.0. For more information on REZIP, extract the file REZIP.ZIP and follow the enclosed instructions.
This diskette contains the file PKLTE115.EXE. Type PKLTE115 followed by pressing the Enter key to create the program and documentation files for PKLITE version 1.15. To print the documentation files after running PKLTE115, type COPY *.DOC PRN followed by the return key. If you distribute PKLITE to friends, associates, or to a computer bulletin board system (BBS), please distribute the file PKLTE115.EXE rather than the individual files for PKLITE.
This program was written in French. The help screen (displayed when LZEXE is executed without any arguments) is in French and cannot be hacked into English because it's encrypted, compressed, etc. The info displayed is just a summary of the doc file. The latter has been translated very quickly into English. It seems like a very useful and good program. I tried it a few times, and it worked flawlessly. The translator. Luigi M. Bianchi 414 Atkinson, York University 4700 Keele Street] North York, Ontario M3J 1P3 Canada Errata and addenda for version 0.91 by earle robinson 70004,1762
WATCHDOG 7.0.1 README.DOC
Latest revision: March 4, 1993
By Fischer International Systems Corporation
Included in this document file: Page
DOS Versions Supported 1
Upgrading to MS-DOS 5.0 2 1
Upgrading Previous Versions of Watchdog 2
New Version of Watchdog Armor Included 2
Security Checks on Boot Process 2
Backing Up Security Files 2
Control Diskette Booting Backups 3
Installing Watchdog on Hard Disks other than C: 3
Transparent Interface 3
Network Single Sign-on 3
Network Encryption 3
Watchdog Keylock and Screensavers 4
Super User Mode 4
WDRIGHTS 4
DOS VERSIONS SUPPORTED
THIS COPY OF WATCHDOG 7.0.1 SUPPORTS DOS VERSIONS FROM 3.0 THROUGH
5.0x.
This copy of Watchdog 7.0.1 will not run on versions of DOS higher
than 5.0x. This restriction has been set to prevent security
exposures from being introduced by new DOS facilities not yet
available at the time that this copy was distributed. As new
releases of DOS become available, Watchdog will be enhanced to
support them.
IF YOU HAVE A LATER VERSION OF DOS, CONTACT FISCHER INTERNATIONAL
SYSTEMS CORP. ABOUT SUPPORT FOR THAT VERSION OF DOS.
* You should remove Diskette Booting prior to changing DOS
versions on a PC that already has Watchdog installed.
Page 2
UPGRADING TO DOS 5.0
If you plan to upgrade your machine to MS-DOS 5.0:
- upgrade the machine to Watchdog 7.0.1,
- remove diskette booting,
- boot to A:
- and run the DOS SETUP from there.
When you reboot on C: after SETUP, run the SA program and
restrict diskette booting again.
UPGRADING PREVIOUS VERSIONS OF WATCHDOG
Watchdog 7.0.1 will not upgrade or replace Watchdog versions
prior to 5.x. If you have a Watchdog version prior to 5.x,
first deinstall that version, then install Watchdog 7.0.1.
NEW VERSION OF WATCHDOG ARMOR INCLUDED
Due to changes in handling configuration environments such as
colors and menu titles, Watchdog Armor has been upgraded. The code
loaded on the Armor Card is still current, but if you have a old
copy of WDARMOR.EXE and WDARMOR.HLP you should replace it with the
version on the Supplemental Disk. The easiest way is to copy the
contents of the Armor diskette into the System Administration
directory and then copy the two files from the Supplemental Disk
into SYSADM on top of the old versions. You can then run WDARMOR
from the System Administration Area on the hard disk instead of
from the diskette.
SECURITY CHECKS ON BOOT PROCESS
Watchdog version 7.0.1 provides additional checks on the
boot process. If you subsequently upgrade your version
of DOS, you could get a warning message about the boot
process. To correct this situation, run replace to update
the Watchdog files and security checks on the boot process.
If you should get this warning message, and you have NOT
upgraded your DOS version, call Watchdog Technical Support.
BACKING UP SECURITY FILES
The Watchdog System Administration (SA) files contain all the
information pertaining to your PC's security environment. Once you
have installed the product, you should log onto Watchdog, run WDSA
(either from the System Administration Area that was created, or
from the SA diskette), and backup your SA files. This is very
important and will provide you with an additional layer of
protection against hard disk failures. ANY CHANGES TO WATCHDOG
SECURITY INFORMATION, INCLUDING RANDOM ENCRYPTION KEYS, COULD BE
LOST IF BACKUPS ARE NOT MADE.
Page 3
CONTROL DISKETTE BOOTING BACKUPS
Control Diskette Booting processing now requires a backup step. You
will use this backup if the hard disk ever has a hard failure that
prevents Watchdog's normal error recovery process from accessing
information on the hard disk while Diskette Booting is restricted.
When restricting Diskette Booting, it is important that you make
and keep this backup in a safe place.
INSTALLING WATCHDOG ON HARD DISKS OTHER THAN C:
Watchdog program and data files may be installed to any hard disk
on the PC. Hard disks containing Watchdog must, however, be
accessible when CONFIG.SYS is referenced during the boot process.
If a disk is defined to the PC later in the AUTOEXEC.BAT (by
ASGNPART for example) or when a network program is first run, then
Watchdog files referenced in CONFIG.SYS will not be available when
CONFIG.SYS is processed.
If you install Watchdog on a disk other than drive C:, make sure
that drive is available to CONFIG.SYS during the boot process.
TRANSPARENT INTERFACE
If you are upgrading or replacing a previous Watchdog version,
Watchdog will not automatically activate the transparent interface.
You must manually activate the transparent interface by enabling
the System Permission "Automatically Add All Areas at Login".
NETWORK SINGLE SIGN-ON
On a new install, Watchdog automatically copies WDNET.* files to
\SYSLIB. If you are upgrading or replacing a previous Watchdog
version, you must manually copy the appropriate WDNET file to \SYSLIB.
If you are using Novell, copy WDNET.NOV to \SYSLIB\WDNET.BAT. If
you are using OS\2 Lan Manager, copy WDNET.MAN to \SYSLIB\WDNET.BAT.
You will need to customize the WDNET.BAT file to automatically log
users onto your server, pass Watchdog user IDs and passwords, and
synchronize the network to Watchdog whenever a password changes.
Refer to your Watchdog Setup Guide for complete instructions on
network setup.
NETWORK ENCRYPTION
When you setup a network directory as a new Watchdog area, make sure
that directory does not already contain data.
Before you copy data into the network area, make sure you are logged
into the network area. If you are using Novell, make sure you also
load WDEMUL /NET.
If you want to unprotect a network area, be sure to log into the area
and copy any data it contains to an external directory, before you
unprotect the network area.
Page 4
WATCHDOG KEYLOCK AND SCREENSAVERS
If Watchdog Keylock conflicts with an existing screensaver, turn off
the screensaver and use the Watchdog Keylock to blank your screen and
lock the keyboard.
SUPER USER MODE
A Super User has unrestricted access to the entire hard disk and can
delete any file or directory, reformat the hard disk, or run any DOS
command. We recommend the SA assign only himself or herself as a
Super User, under a separate user ID.
If you login as a Super User and get a warning that Watchdog cannot
add all areas, do the following:
- run the SA program and at the Change System Configuration menu,
- select F5 (Change Encryption Key Memory Usage).
- Select F3 (Auto), or Select F2 (Set) and enter a higher number.
For most situations, AUTO is the correct choice.
* Don't write to any encrypted areas that Watchdog was unable to add.
WDRIGHTS
WDRIGHTS is a utility command that displays permission rights for the
current user. You can specify any legal path after the WDRIGHTS
command and Watchdog will show you the access permissions for the
specified directories (Execute, Read, Write, Create/Delete).
１９９３年, 微宏新奉献, 软件钢铁卫士, 保护著作权
Lock93 ---- 超级软件加密工具 V1.0
m&M Software Research Institute
使用说明书
一、特点
★ 最新突破：Lock93制作的加密软件可以在 486/33M 计算机及最新发表的
MSDOS 5.0、DRDOS 6.0等上面正常使用。
★ 高可靠性：加密子盘的制作和判读采用更可靠的思想和程序设计方法，采用了
更加认真细致改造的反拷贝和动态反跟踪机制，使各种硬拷贝都无
法生成复制品。反跟踪解密因异常艰难困苦而不可能
★ 高适应性：高密、低密、５寸、３寸盘均可自动识别并完成加密子盘的制作，
对硬件及介质的要求降到目前所有加密软件的最低要求，适用于
ＰＣ到４８６的各档次的微机，操作系统: DOS 3.0或以上版本，
★ 多功能性：生成的加密子盘具有向硬盘安装加密软件的功能，这是本软件的一
个重要突破。
★ 面向用户：菜单驱动，界面友好，操作简单无需各种设置。
★ 成批制作：可以一次读入被加密软件成批地制作出可直接交给用户的加密成品
盘，提高了用户使用效率。
二、软件构成
本软件的构成是：
１，３６０Ｋ或７２０Ｋ，低密软盘１张
２， 用户使用说明书 １份
本软件４个文件，它们是：
Ｌｏｃｋ９３Ｓ．ＥＸＥ -- Lock93 加密子盘生成工具
Ｌｏｃｋ９３Ｓ．ＯＶ１ -- Lock93 生成工具辅助文件
Ｌｏｃｋ９３Ｓ．ＯＶ２ -- Lock93 生成工具辅助文件
ｒｅａｄｍｅ -- 本说明书
ｃｒｅａｄ．ｃｏｍ -- 本说明书阅读工具
Ｃｏｍｐｒｅｓｓ．ｅｘｅ-- .EXE文件压缩工具,当某些被加密软件直接
加密不能用时, 请用压缩工具压缩后再加密
说明： ①，程序可以在本软盘上执行，也可以拷贝到硬盘中执行，只要
执行时将本软盘插在Ａ或Ｂ盘即可。
②，请注意在任何情况下都不要试图打开写保护进行各种操作，
否则可能感染计算机病毒，任何人为的原因造成的程序被破坏，
一切后果损失自负。
三、适用范围:
①适用机型：ＰＣ ＩＢＭ２８６ ３８６ ４８６及其兼容机
②操作系统：IBM PCDOS 3.0或以上版本。
③适用磁盘：360K、1.2M、720K、1.44M。
④本软件在西文状态下运行的，所有提示均为英文。
四、使用说明:
1，制作子盘
A，先用 Format 或 PCtools格式化软盘
B，在C:盘建一子目录LOCK93, 将Lock93加密母盘插入Ａ(或Ｂ)驱动器，
然后把加密母盘上的所有文件拷贝到该子目录下，
C:\>md lock93
C:\>cd lock93
C:\LOCK93>copy a:*.*
C:\LOCK93>lock93S
接着执行 LOCK93S 即可出现本软件的主屏幕，上面包括菜单、出版公司、
作者等，屏幕顶行有两项 Lock Help
本系统提供完整的联机帮助。（可键入Alt+H 或 F1 即可弹出帮助的屏幕）
C，Make child-disk（制作子盘）
①Make制作子盘（可自动识别各种软盘，高密低密，5寸,3.5寸盘)
②Select Drive选择驱动器（Ａ或Ｂ）
③Option是否生成带硬盘安装功能的加密子盘（√表示此项已选）
先选择好驱动器，再把光棒移动到 Make 回车，这时进行制作，制作子
盘是带校样的，如果都是PASS则表示子盘制作成功.
可键入ESC退出此菜单。（以下相同）
D, Encrypt file可成批制作加密成品盘
①Filename输入要加密的文件名(.EXE或.COM)
②Encrypt 制作加密成品盘
③Select Drive选择驱动器（Ａ或Ｂ）
④Option选择是否生成带硬盘安装功能的加密成品盘（√表示此项已选）
加密过程都是带校验的，只要出现三个 PASS 加密就成功。
E, Get information 可显示时间及已制作子盘个数
2, 用加密子盘加密文件
制作好了的子盘上有一个Lock93.exe文件，这是一个加密工具文件,其
用法同 DOS 的 COPY 命令完全一样，可以用此文件加密其它EXE文件或COM文件，
加密后的指纹在此盘上，而文件可以放在各个盘上（包括A:盘B:盘或C:盘等）
但运行时必须在A:盘或B:盘读到加密子盘上的指纹.
Lock93的用法：
Lock93 [d:][path] sourefile [d:][path] targetfile
其中：d:表示盘号，缺省值为当前盘．
path为路径，缺省值为当前目录．
sourcefile 为需要被加密的文件名(扩展名为.EXE或.COM)
targetfile 为加密后的文件名．
该目标文件(targetfile)就是加密后的文件,可在各种机器上使用。
例:在A:加密子盘上加密C:盘当前目录下的UNFOX.exe文件
A>Lock93 C:UNFOX.exe A:UNFOX.exe
3,用加密子盘向硬盘安装被加密软件
这是本软件的一大新突破，在制作过程中有一个选项Option，如果选择
了Install to hard disk (即其后显示一个√)则生成的子盘上有一个 HDinst.exe 文件。
向硬盘安装的用法如下:
HDinst sourefile [d:]
例:在A:加密子盘上安装UNFOX.exe文件到C:盘当前目录下
A>HDinst UNFOX.exe C:
本软件可在硬盘上产生２５５个加密点，不用担心用此工具加密的多个软件
安装到硬盘后造成的冲突，而且安装次数不加以限制，安装时不必打开加密子盘
的写保护标签，所以使用Lock93加密子盘不必担心被病毒感染。
如果在Option中没有进行选择(无√)，则就没有此功能。
＿＿Lock93 可以生成带硬盘安装的加密子盘提高了使用效率防止了病毒感染。
五、开发背景
近几年来，本公司和其他各公司陆续出现了一些比较优秀的加密软件，这些
加密软件的使用，对于防止某些拷贝软件及至拷贝机，卡的非法复制，对于保护
软件合法著作者和持有者的合法权益，起到了良好的作用。
但是，道高一尺魔高一丈，即使是公认为的比较成功的优秀的加密软件,从
其流行到被解密，其寿命也是短暂的，究其原因，一方面是由于前几年没有软件
法规的建立，健全和实施，软件著作人的利益没有法律保障,少数人钻了这个空
子，在或短或长的时间解密成为可能，另一方面，加密软件本身也不够严密，缺
少灵活的变化，结果造成了“有通用的加密程序，就有了通用的解密程序”，使
加密程序设计者, 使用者以及加密程序者三者的利益都受到严重损害。 还有
现在大部分加密软件的实用范围都受到了一定的限制，如ＤＯＳ５．０不能使用，
３８６／３３以上的和４８６机器不能运行等许多的问题使得使用者购买了加密
软件，在许多环境下不能运行，使用者的利益受到严重损害，而且许多加密工具
功能有一定的局限性如加密后的软件必须读钥匙盘,这样增加了使用加密软件的麻
烦，而且软盘又容易损坏，一旦损坏就不能使用。鉴于以上问题，我公司在深入
细致地调查研究的基础上，借鉴了许多加密软件的长处，历经了长时间的研制，
终于推出了实用广泛的, 最新的，高可靠性的，方便的，新一代加密软件包
总之，Lock93是目前各种加密软件优点的结合体，是用户所需要的、目前最好的
加密工具，我们坚信，使用Lock93可以使您开发的软件得到有效保护。
要说明的是：
当某些被加密软件直接加密不能用时, 请用.EXE文件压缩工具Compress.exe压缩
后再加密，其使用格式如下：
Compress inputfile outputfile
例如欲压缩 AS.exe 文件，压缩后文件名为 AS1.exe
Compress AS.exe AS1.exe
虽然我们作了大量工作，以提高此工具的通用性、最大限制满足广大
用户的要求，但本工具目前尚不支持 EXE文件内部有动态覆盖调用的软件。
例如：Clipper 5.01编译后的 exe文件就不能加密。在这方面我们正在继续加以
改进，希望在不久的将来与大家见面。
微宏电脑软件研究所
1993.01.06
联系电话:2559756,2560694
联系人 : 于滨, 徐新, 蔡文雨
联系地址:北京市海淀区颐宾饭店北段441室
邮政编码:100080
开户行 :工商行北京市海淀区海淀镇分理处
帐号 :661730-03
户名 :北京市海淀区微宏电脑软件研究所
Lock93 ---- Super software protection tool
m&M Software Research Institute
How to make Lock93 key disk(child disk):
A. first format disk using Format.exe or PCtools.exe
B. create directory LOCK93 in C:drive, insert Lock93 mother disk in A:(or B:)
then,copy all files in mother disk to LOCK93 directory
C:\>md lock93
C:\>cd lock93
C:\LOCK93>copy a:*.*
C:\LOCK93>lock93S
then, execute LOCK93S.exe, the screen will show like following:
Lock Help
you can get help any time (Just type Alt+H or F1 )
How to use Lock93 :
In DOS environment, type in:
[d:][path]Lock93 [d:][path]sourcefile [d:][path]targetfile
d: designates drive, default is current drive.
path: designates directory path.
sourcefile designates the name of the file to be protected.
targetfile designates the name of the protected file.
EXAMPFLE:
Current drive is A:, type in:
A>Lock93 C:UNFOX.exe A:UNFOX.exe
How to install protected file to hard disk:
A. when you make key disk (child disk), Please select Install to hard disk
option (Just press return )
B. insert key disk in A:, type in
HDinst sourefile [d:]
EXAMPFLE:
A>HDinst UNFOX.exe C:
Remark: Bin Yu write this readme file for Lock93 software protection tool
the first version is writed by Wen Yucai
欢迎使用 BITLOK V1.0
====================
■ 版权声明
BITLOK 软件保护系统，由
北京微远公司 Beijing Miniway Software Development Corp.
黄玫瑰软件制作室 Yellow Rose Software Corp.
香港金山公司 HongKong KingSun Co.
联合研制开发，具有完全的自主版权。并经中国计算机软件登记办公室登记
注册，注册号为: 920000143。
为保障 BITLOK 所有合法用户的权利，维护各地代理销售公司利益，在此
郑重声明：任何单位或个人对 BITLOK 及使用 BITLOK 加密过的软件进行解密、
修改内容及标题等均属违法行为，我们保留对以上行为追究法律责任的权利。
■ BITLOK 快速入门
请仔细阅读手册，手册中有 BITLOK 系统的详细用法和使用技巧。
BITLOK 系统中有两个实用程序，BITLOK.EXE 和 BLINST.EXE。BITLOK.EXE 是
加密程序，BLINST.EXE 是硬盘和网络安装工具。
密钥盘默认驱动器是 A, 如果密钥盘插在 B 驱动器, 请设置 SET KEY = B。
输入以下命令, 会在 B 盘生成 TEST.EXE, TEST.0VL 两个程序，TEST.EXE会
自动调用TEST.0VL覆盖模块。覆盖模块可以直接拷贝到文件尾。
BITLOK TEST.EXE B:TEST.EXE
COPY /B B:TEST.EXE+B:TEST.0VL
DEL B:TEST.0VL
安装到硬盘上
COPY B:TEST.* C:
BLINST C:TEST.EXE
安装完毕后, 可把 C:TEST.EXE 加上只读属性。
安装到网络上 (网络驱动器是 F 盘)
首先用 SUPERVISOR 入网, 其次所有用户必须在安装前入网, 再开始安装。
COPY B:TEST.EXE F:
BLINST F:TEST.EXE
■ 如何与 BITLOK 销售部门取得联系，获得必要的技术支持
■ 手册印刷后 BITLOK 最新改进
----------------------------------------------------( Revision 1.69 )-----
[1] 增加了安装计数功能.
使用 BITLOK 的安装计数功能，应事先设置环境变量，如
SET KEY=B,INST123
这样加密过的软件最多可以安装123次。如果不设置这个参数,
则对安装次数无限。INST后面可以接一位、两位或三位数字。
[2] BLINST 增加了一个参数 /t
该功能用来测试加密盘上还有多少次安装计数
注意 /t 和 /q 两个参数一起使用, 屏幕上仍然会显示加密盘上剩余的安
装次数。
[3] BLINST 增加了一个错误码 50
错误信息是没有剩余的安装计数。
[4] 显示用户序列号
直接输入 'BITLOK' 或 'BLINST', 屏幕上就会显示该套软件的用户序列号。
----------------------------------------------------( Revision 1.70 )-----
[1] BITLOK 在加密所有的软件都不再生成覆盖。
[2] 在加密驻留软件时，建议在 KEY 的环境变量中加入 NOSTAY 参数。
如: SET KEY=B,OLD,NOSTAY
----------------------------------------------------( Version 1.2 )------
[1] 提供集成环境的BITLOK, 使用户使用更加方便
[2] BITLOK 的命令行参数 /A /B 表示制作 KEY 的软盘在 A 驱或 B 驱
[3] BL.EXE 是 BITLOK 命令行版本
■ 手册中存在的印刷问题
■ BITLOK 使用说明
如果使用过 MS-DOS 中的共享程序 SHARE.EXE, BITLOK 加密过的程序安装到
硬盘上, 工作不正常. 请移去 SHARE.EXE 后使用。
-·-
───────────────────▄─ Quarterdeck Office Systems
────────────────▄▄▄── 150 Pico Boulevard
─────────────▄▄▄▄▄─── Santa Monica CA 90405
──────────▄▄▄▄▄▄▄────
───────▄▄▄▄▄▄▄▄▄─────
────▄▄▄▄▄▄▄▄▄▄▄──────
September 24th, 1993
QEMM Patch for version 7.01 dated 6/21/93
This patchfile implements fixes to QEMM version 7.01. This patch
will work ONLY on QEMM version 7.01. The dates on the QEMM386.SYS (in
your QEMM directory) should be 6/21/93. If the date on these files is later
than 6/21/93, you do not need this patch.
This patch should be applied by copying the files which should
accompany this README (PATCH.EXE, 701to702.RTP, STEALTH.RTP,
TECHNOTE.RTP, YESNO.COM and 701to702.BAT) into your QEMM
directory, and then typing
701to702
After the patch has been successfully applied, you may delete the
following files (if any still exist) from your QEMM directory:
701to702.ZIP
PATCH.EXE
701to702.RTP
STEALTH.RTP
TECHNOTE.RTP
YESNO.COM
701to702.BAT
README.702 (this file)
**************************************************************************
*These files may be copied and distributed freely as long as they are *
*distributed together, in their entirety, and not distributed for profit.*
* Copyright (C) 1993 by Quarterdeck Office Systems *
************************ E N D O F F I L E ***************************
QEMM v7.04 FULL RELEASE!!! No Update! Serial Number 001-32H-72414 Extract With -$
READ ME FIRST
VM/386
The Professional MultiTasker
Version 1.2
Note: The following instructions assume that VM/386 is
installed to the C: drive and the \VM386 directory. If not,
please substitute the actual drive letter and directory name
which VM/386 is installed to where appropriate.
The following topics are covered in this README disk file:
* 1. Installing Version 1.2
* 2. Enhancements for Version 1.2
* 3. Compatibility List
* 4. Other Notes
Additional topics, as listed at the end of this file, are
covered in the printed READ ME FIRST document which comes
with VM/386.
INSTALLING VERSION 1.2
REMOVE DISK CACHE, EXPANDED MEMORY MANAGER (EMM) BEFORE
INSTALLING VM/386
You must edit your CONFIG.SYS file before installing VM/386.
The procedure is described in the manual's Chapter 2,
Installation. The following device drivers must be removed:
* Expanded memory managers such as CEMM.SYS and QEMM.SYS.
* Other device drivers which use Protected Mode.
* Device drivers such as SMARTDRV.SYS which install a disk
cache. The disk cache may interfere with VM/386 hard disk
driver selection if it is not removed (see below).
* RAM disks such as VDISK.SYS.
VM/386 has its own expanded memory manager, disk cache, and
shared RAM disk which offer enhanced versions of these
functions.
REMOVE OTHER DEVICE DRIVERS, MEMORY-RESIDENT PROGRAMS (TSRs)
BEFORE USING VM/386
Device drivers installed by CONFIG.SYS and memory-resident
programs started by AUTOEXEC.BAT are not accessible to
Virtual Machines once VM/386 is started, yet they still
occupy memory. Remove device drivers from CONFIG.SYS and
memory-resident programs from AUTOEXEC.BAT to conserve system
memory. Then add the device drivers to custom CONFIG files
used by Virtual Machines, and memory-resident programs to
custom AUTOEXEC files used by Virtual Machines, as needed to
make best use of each Virtual Machine.
INSTALLING VM/386 FOR THE FIRST TIME
Carefully follow the installation instructions in Chapter 2
of the manual:
* Make a working copy of your VM/386 disk - from a DOS
prompt, type:
DISKCOPY A: A: <Enter>
* Insert the working disk in drive A: and reboot (Ctrl-
Alt-Del).
* Remove the working disk and reboot (Ctrl-Alt-Del).
* Confirm that you are at a DOS prompt (i.e., C:>).
* Insert the working disk in drive A: and type: A: <Enter>
* Type: SETUP <Enter> and follow the instructions on the
screen.
UPGRADING AN EXISTING COPY OF VM/386
When you upgrade an existing copy of VM/386, the old
CONFIG.VM and AUTOEXEC.VM files are saved in the root
directory as CONFIG.VM2 and AUTOEXEC.VM2. New CONFIG.VM and
AUTOEXEC.VM files are created by adding entries to the
CONFIG.SYS and AUTOEXEC.BAT files found in the root
directory.
VM/386 can be installed in either of two ways:
1. Install the new version of VM/386 to the same drive and
directory as the old one.
The following steps will occur:
* Existing Profiles will be preserved.
* A new Profile called COMM, and a group of Profiles with
the letters "PC" in the Profile name (e.g., "640K_PC"),
will be added to the Profiles list. (To delete the
existing "STD" Profiles, go to a DOS prompt in the
VM/386 directory and enter the command: DEL ???K_STD.PRO.)
* The default Startup File, VMSTART.SUF, will be replaced by
a new file. Other Startup Files will be preserved.
2. Install the new version of VM/386 to a different drive
and/or directory than the old one.
This allows both versions to be available on the hard disk
simultaneously. Before creating a Virtual Machine with the
old version of VM/386, change the Boot Files menu on the
Create Virtual Machine screen (1.1) to use CONFIG.VM2 and
AUTOEXEC.VM2. These Boot Files use the copy of VMFSS.COM and
other VM/386 utilities stored in the same drive and directory
as the old version of the program.
Before using other custom AUTOEXEC files with the old version
of VM/386, change the line:
C:\<directory>\VMFSS.COM
so the <directory> name matches the directory in which the
older VM/386 version is stored. The AUTOEXEC file will now
run the older version of VMFSS. If the wrong version of
VMFSS is used, an error message will appear and you will not
be able to access your hard disk from the Virtual Machine.
PRINTER SHARING
During VM/386 installation, you will be asked if you want to
share your printer across all Virtual Machines. If you
answer yes, you will be asked which port your printer uses.
If you answer LPT1, for example, the following command will
be added to the AUTOEXEC.VM file:
\VM386\VMLINK LPT1
This command will automatically link the printer as a
floating device to all Virtual Machines which boot up using
AUTOEXEC.VM (the default AUTOEXEC file).
COMPAQ AND MICRONICS MOTHERBOARD USERS - /X OPTION
Some Compaq and Compaq-compatible machines reserve 384K of
RAM for use by Compaq DOS and the ROM BIOS. This causes
VM/386 to only find 1664K available out of the 2M of RAM in
your machine. For all Compaq 386 machines except the Deskpro
386/20, and most Micronics motherboard machines, start VM/386
as follows:
CD \VM386 <Enter>
VM386 [startup file name] /x <Enter>
The [startup file name] is optional. The /x option makes
256K of the reserved memory available for use by VM/386. The
/x option is not compatible with the Compaq Deskpro 386/20
memory cache.
AUTOMATIC HARD DISK DRIVER SELECTION
During installation, VM/386 automatically installs one of the
following hard disk drivers:
* The VM/386 driver for the Western Digital ST-506
controller (used in the IBM PC/AT and many other
computers).
* The INT 13 BIOS driver for ESDI, SCSI, and other
controllers.
In the following cases, the wrong hard disk driver may be
selected:
* A disk cache was active during installation. This may
cause the INT 13 BIOS driver to be installed when the
driver for the WD ST-506 should have been used. This
results in poor performance.
* The Adaptec RLL controller is in use; VM/386 will install
the WD ST-506 driver. This may result in errors in
writing to the hard disk.
Either of these problems can be resolved by installing the
correct driver. Exit VM/386 if it is running; then go to a
DOS prompt and enter:
CD\VM386
VMSETHD
You will be asked whether you want automatic hard disk driver
selection. Type:
N <Enter>
to respond "No".
A list with the two available controllers will appear. Type:
1 <Enter>
to select the VM/386 driver for the Western Digital ST-506
controller. Or type:
2 <Enter>
to select the INT 13 BIOS driver.
Once the correct driver is installed, start VM/386 and retry
the operation which failed previously.
ENHANCEMENTS FOR VERSION 1.2
1) VM/386 now supports hard disk partitions larger than 32M
under the following products:
* PC DOS 4.0
* Compaq DOS 3.31
* Speedstor (by Storage Dimensions) versions through
5.11
* Disk Manager (by Ontrak Systems) versions through 3.10
2) VM/386 now supports access to 3COM networks. Read
Appendix D in the manual for complete directions on how
to access a 3COM network from within a Virtual Machine.
3) The printer can now be shared among Virtual Machines.
The printer (LPT) port can be linked as a floating device
to any or all Virtual Machines. During installation, you
will be asked if you want to automatically link the
printer to all Virtual Machines as a floating device.
4) New Profiles are included with VM/386. The new Profile
names use the letters "PC", as in "640K_PC", in place of
the letters "STD" which were used in previous VM/386
versions. Also included is the COMM Profile, which should
be used to create a Virtual Machine for modem
communications, accessing a network, or other
communications tasks. The COMM Profile ensures that the
Virtual Machine will have first access to interrupts (the
Queue is set to 1 and the Priority is set to 1) and that
the Virtual Machine will not be suspended by the System
Resource Monitor (SRM Check set to No).
5) The Alt-SysRq SysRq key combination allows direct access
to the next Virtual Machine in the VM List without
accessing the Switcher. If two Virtual Machines are
active, for example, and VM1 is in the foreground, do the
following to bring VM2 onscreen:
* Hold down the Alt key.
* Press SysRq.
* Press SysRq again.
* Release the Alt key.
VM2 will come to the foreground. Repeat the same
keystrokes to go to the next Virtual Machine, which in
this case is VM1.
Note that the Virtual Machine Manager is not "in the loop"
and can't be accessed via Alt-SysRq SysRq. Use (Alt)
SysRq to bring up the Switcher and access the Virtual
Machine Manager.
6) CPU performance has been further improved. CPU overhead
for memory-intensive calculations is now only about 2%
(had been 4-5%).
COMPATIBILITY LIST
COMPATIBLE SYSTEMS
VM/386 has been tested on the following computers or boards:
* Compaq Deskpro 386 * Intel Inboard 386/AT
* Compaq Deskpro 386/20 * Orchid Jet 386 board
* Compaq Portable 386 * AOX Master 386 motherboard
* Everex System 386 * Intel motherboard
* IBM PS/2 Model 70 * Everex System 386
* IBM PS/2 Model 80 * Intel motherboard
* Kaypro 386 * Micronics motherboard
* Multitech (Acer) 1100 * Wedge Tech. motherboard
* PC's Limited 386-16
* Siemens PCD-3T
* Tandy Model 4000
VM/386 also supports close compatibles of the computers and
boards listed above.
VM/386 does not support the Toshiba T5100.
Some implementations of the 80387 math coprocessor can't be
reset dynamically, as required to successfully multitask
programs which use it. If problems occur, only run one
coprocessor-dependent program at a time under VM/386.
VIDEO ADAPTERS
VM/386 supports MDA (monochrome text), Hercules, CGA, EGA,
and VGA video adapters. The 8514/A and PGC video controllers
can be used to support a second monitor running a single
Virtual Machine, as described in the manual.
VM/386 does not support the ATI Wondercard and ATI
Professional VGA graphics cards.
VM/386 does not support some high-resolution monitors such as
the Wyse 700 and the Zenith Flat Tension Mask (FTM) monitor.
VM/386 has compatibility problems with the Zenith 449 video
card on the Zenith 386:
* The Zenith 449 video card supports certain VGA functions
but not others, leading to problems with some graphics
software and with VM/386. It is possible to lock the card
into EGA mode by resetting its jumpers, which allows
VM/386 to run successfully. Check the 449 card's
documentation for instructions.
* Normally, when VM/386 is terminated it reboots the
computer it's running on. On the Zenith 386 with the 449
card locked into EGA mode, exiting from VM/386 causes a
"slushware error" in reloading the card's low-level video
software ("slushware"). Turn the computer off, then back
on, to continue.
HARD DISKS
VM/386 supports the following formatting programs which allow
partitions greater than 32 Mb in size:
* PC DOS 4.0
* Compaq DOS 3.31
* Speedstor (by Storage Dimensions) versions through 5.11
* Disk Manager (by Ontrak Systems) versions through 3.10
VM/386 does not support Golden Bow or Priam disk formatting
software. If your hard disk is formatted with one of these
programs, you will need to reformat it using supported
formatting software before running VM/386. (For information
on hard disk setup, see the Installation Notes.)
There are two problems which may occur with Wyse DOS Version
3.21:
* The version of DOS is unable to read the VM/386
distribution disk, or other disks formatted under PC-DOS
Version 3.3.
* Though VM/386 is installed successfully, it is impossible
to create a Virtual Machine.
If either of these problems occurs, your copy of Wyse DOS
3.21 is incompatible with VM/386.
OTHER NOTES
EGA, EGA+, AUTOSWITCHING VIDEO CARDS
If your video card has autoswitching capabilities, you may
get a blank screen when you switch Virtual Machines. This is
because some cards switch modes when VM/386 switches screens.
To solve this problem, disable autoswitching; this should
make switching work correctly, while not otherwise affecting
your software programs. See the video card's manual for
directions on how to disable autoswitching.
DISK CACHE SIZE
On the Create VM/386 Startup File screen (1.6), VM/386 allows
you to specify and save to disk a Startup File with a disk
cache up to 4 Mb in size. The largest disk cache which this
version of VM/386 will actually support is 1.4 Mb. If a disk
cache larger than 1.4 Mb is specified, a memory allocation
conflict may occur during initialization of VM/386. Testing
with several programs indicates that the optimum disk cache
size is 32K (the default value).
READ ME FIRST DOCUMENT
Please see the printed READ ME FIRST document which comes
with VM/386 for additional notes on:
* Using a mouse within a Virtual Machine.
* Support for DOS commands.
* Using the IBM Token Ring Network.
* Running AutoCAD 9 with VGA graphics.
* The VMFG program, a command entered from the DOS prompt
which brings a Virtual Machine to the foreground.
* The Universal Device Driver found in Virtual Machine 1.
* The Template Device Driver for supporting new devices in
other Virtual Machines.
THANK YOU FOR PURCHASING VM/386,
THE PROFESSIONAL MULTITASKER
IGC TEL (408) 986-8373
4800 Great America Parkway FAX (408) 986-1431
Santa Clara, CA 95054
Important updates to the manual
----------
As of August 10th 1989, the following new facilities could be of importance
to you:
TC! POWER is now EMS 4.0 compatible
-----------------------------------
The manual states that TC! POWER emulates EMS 3.2 and not 4.0.
This is no longer true. We now give full EMS 4.0 support.
The device driver name has changed
----------------------------------
The manual states that the TC! POWER EMS driver is called TCPOWER.SYS.
This has been changed to TCPOWER.EXE.
If this is an upgrade
---------------------
If you are installing this version of TC! POWER as an upgrade to an earlier
version of the program, simply copy the files on the new distribution diskette
into your TCPOWER directory. Then make sure you are in your TCPOWER directory
and run INSTALL selecting the install option.
Accept the default parameters (they will be the same as the ones you used
before) by pressing END. Then reboot your machine to load the new version into
memory.
TC! POWER can now use existing expanded memory
----------------------------------------------
If you already have an expanded memory board in your machine, TC! POWER will
append more memory to that board. As long as the expanded memory board is
fully operative when you install TC! POWER using the INSTALL program, your
total expanded memory will be the sum of the memory on the board plus the
memory emulated by TC! POWER minus 64K. The 64K lost is used for moving the
64K pageframe out of conventional memory so TC! POWER occupies only 15K
conventional memory instead of about 80K. An example:
You have a 512K ABOVEboard and accept TC! POWERs defaults so it will give
you 512K. The total will be: 512K + 512K - 64K = 960K
TC! POWER will use the existing board first, then do spillover to extended
memory and then do spillover to hard disk. TC! POWER only uses EMS 3.2 calls
when communicating with the existing board, so your board can be EMS 3.2 or
4.0 compatible. It doesn't matter as 4.0 is a superset of 3.2.
Building on an expanded memory board like this, TC! POWER will support so
called "page frame aliasing" necessary to make some applications run.
TC! POWER can take advantage of the 80386 processor
---------------------------------------------------
We here assume that your 386 machine does not already have an EMS board.
If it has, you will use the existing board as described above.
If you have an 80386 processor, you can use a special driver to turn your
extended memory into expanded memory which looks EXACTLY like a board.
Then TC! POWER will look at that expanded memory as if you had a board
in your machine, and TC! POWER will not occupy 64K conventional memory
for its pageframe. The situation will be exactly the same as if you had a
board installed. TC! POWER will now occupy around 15K and not 80K.
There are several drivers that will help you accomplish this. EMM386.SYS
comes with MSDOS 4.0 from MicroSoft. QEMM.SYS from Quarterdeck will do the
same thing for you.
Simply install EMM386.SYS or QEMM.SYS according to their manuals converting
all your extended memory into expanded, reboot your machine, and THEN install
TC! POWER using the INSTALL program. The defaults set forth by TC! POWER should
always be correct. You can of course increase the HARDDISK USAGE field to
cover your expanded memory needs, but the EXTENDED MEMORY USAGE field will
already contain its maximum value. The total EMS memory available will be the
amount of expanded memory given to you by the 386 driver plus the expanded
memory emulated by TC! POWER minus 64K.
Using EMM386.SYS or QEMM.SYS, TC! POWER will support so called "page frame
aliasing" necessary to make some programs run. The resulting expanded memory
will also be much faster than if you told TC! POWER to use your extended
memory directly. Therefore all your extended memory should be used by
the 386 driver which will convert it to expanded memory which will eventually
be used by TC! POWER and passed on to application programs. The whole idea
is of course that TC! POWER will append more expanded memory by using hard
disk.
HIDE and SHOW commands free and grab the 64K pageframe
------------------------------------------------------
When TC! POWER installs through its DEVICE= directive in CONFIG.SYS, it
is not yet ready to serve your programs. You have to say SHOW to make it
operative. The INSTALL program has been changed to insert the SHOW command
into the first line of your AUTOEXEC.BAT file. So you should normally not
have to think about this. Running INSTALL will leave you with an operative
EMS driver.
What IS nice to know is that TC! POWER does not grab 64K conventional memory
for its pageframe until the SHOW command is given. When you say HIDE
later on, the 64K pageframe will be freed and TC! POWER will be hidden.
So if a program does not use EMS memory at all and you would rather have as
much conventional memory as possible, say HIDE before you execute that
program and you will have another 64K conventional memory.
This allocation / deallocation of 64K conventional take place only if
you have to use conventional memory for the pageframe. If TC! POWER
is utilizing an existing EMS board or a 386 driver, the 64K pageframe will
not reside in conventional memory and no allocation / deallocation will
be performed by SHOW / HIDE. This also applies if you have put the
pageframe into a special memory expansion card giving you memory in the
reserved area between 640K and 1MB (by using the /A= parameter).
HIDE now has an optional switch. Giving the command HIDE /D hides the
TC! POWER EMS driver, frees the pageframe and deletes the swapfile if present.
If you give the command without any parameters you will avoid deleting the
swapfile, which can have certain advantages. Your disk will probably become
less fragmented resulting in faster disk accesses.
Installing or removing drivers in CONFIG.SYS
--------------------------------------------
If you install or remove drivers in your CONFIG.SYS file which will use
extended memory, you should first deinstall TC! POWER by running the INSTALL
program selecting DEINSTALL. Then install the new driver, boot your machine
and re-install TC! POWER by selecting INSTALL in the INSTALL program.
TC! POWER's installation program acts like a tailor, tailoring TC! POWER's
behaviour and performance. Doing things as described above ensures that
TC! POWER adjusts to the new environment.
In many cases, this operation is not necessary as TC! POWER ignores the
parameters given on the DEVICE= and adjusts if the environment has changed.
This will work only as long as all drivers are loaded BEFORE TC! POWER,
and is not the preferred way to do it - the clean thing to do is to
deinstall and then reinstall TC! POWER after the new drivers have been
installed. Then you should have a correct system configuration. This procedure
is necessary if you for instance want to install EMM386 or QEMM when
TC! POWER is already in your machine.
Thank you for taking the time to read this information. We hope that it was
time well spent and that you gained a better understanding of what TC! POWER
is capable of doing.
Happy computing with TC! POWER
CompuFix/NTI Development
* * * * * * * * * * * * * * * * * * * * * * * * * * *
* 最 新 九 针 打 印 软 件 ９Ｐ２４ 使 用 说 明 *
* * * * * * * * * * * * * * * * * * * * * * * * * * *
简 介
９Ｐ２４是最新９针打印机汉字打印驱动程序，用来模拟２４针打印机打印２４Ｘ
２４点阵的驱动程序，该软件有以下特色：
１．以软方式实现２４针打印机的输出功能，使９针打印机打出的汉字具有并超过
２４针打印机的效果．
２．保留原来Ｄ３２０的８种输出字体，并且９Ｐ２４新增加俩种字体，使得输出
美观实用．
３．增加了制表的功能，可在汉字软件如Ｃ－ｄＢＡＳＥＩＩＩ中打印全密封的表
格，制表格方法十分简便．
４．增加了自动走纸换页的功能，使您在打印程序或输出结果时不致于打在纸的折
叠处，打印好的程序易于装订．
本程序适用于与ＩＢＭ－ＰＣ或其兼相连的各种打印机，如ＩＢＭ ８０ＣＰＳ原
装打印机、ＭＸ／ＦＸ系列、ＣＰ－１３２、Ｓｔａｒ（即Ｇｅｍｉｎｉ－１０Ｘｉ／
１５Ｘｉ）打印机．
使 用 方 法
一．９Ｐ２４驱动程序装入步骤
（１）．开机，装入ＣＣＤＯＳ．
（２）．在Ａ驱动器中插入有９Ｐ２４程序的软盘．
（３）．使当前盘为Ａ盘，即屏幕显示 Ａ＞
（４）．键入９Ｐ２４，按回车，屏幕上出现两行说明，则程序已装好．
二．打印字体选择方法
字体选择方法与Ｄ３２０相同，９Ｐ２４程序装入后默认字体为Ａ字体．
（１）．键盘输入选择字体
在键盘上按Ｃｔｒｌ＋Ｆ１０，提示行出现打印字号选择，键入Ａ－Ｉ对应
十种字体．
（２）．程序中选择字体
在应用程序中可向打印机送 ＥＳＣ码，＂Ｉ＂及＂Ａ－Ｉ＂之一的序列来
选择十种字体．
如在ＢＡＳＩＣ中，ＬＰＲＩ ＮＴ ＣＨＲ＄（２７）＋＂ＩＣ＂为选择
Ｃ字体；在Ｃ－ｄＢＡＳＥＩＩＩ中，向打印机送ＣＨＲ（２７）+＂ＩＣ＂
为选择字体为Ｃ字体．
使用９Ｐ２４打印的１０种字型运行ＢＡＳＩＣ ＤＥＭＯ２ （ＣＲ）．
三．表格打印方法
表格打印是利用原汉字库中区位码０６０４－０６７９中提供的制表符号，在
配合本软件的制表命令来实现的．进入表格打印方式要往打印机送 ＣＨＲ＄（７）
（在Ｃ－ｄＢＡＳＥＩＩＩ中是ＣＨＲ（７） ）．这时打印机发出一声铃响，表示
打印机进入表格打印方式，如再送ＣＨＲ＄（７），这时打印机发出两声铃响，表
示打印机退出表格打印方式，恢复到正常打印方式．制表格字符运行 ＢＡＳＩＣ
ＤＥＭＯ２（ＣＲ）
程序中输入制表符时，为避免使用区位码输入，加快输入速度，请您使用９Ｐ
２４盘上提供的表格词组文件ＢＧＣＺ，ＣＺＬＯＡＤ ＢＧＣＺ，则今后您在输入
制表符号时无论在拼音或首尾码输入状态，只要按Ｏ、Ｐ、Ｋ、Ｌ中的任一键，再
按一下分号（；），就可出现您所需要的制表符号，用这种方法不仅不必记住制表
符号的区为码， 而且可大大加快制表符号的输入速度．
犓 一般打印机常用的纸有宽纸和窄纸两种，宽纸称为１３４列的纸，窄纸称为80
列的纸， ＢＴＤ９装入后默认的纸宽为８０，若您用大于８０列的纸，可在键盘上
按Ｃｔｒｌ＋Ｆ１０来选择纸宽，输入８０－１３４，最大值可为２５５．在BASIC
中，还要用 ＷＩＤＴＨ ＂ＬＰＴ１：＂，ｓｉｚｅ 语句再定义一次行宽度， 用
９Ｐ２４驱动程序，对于８０列的窄纸，Ａ字体一行可打印８０个汉字，Ｉ字体可
打印１６０个汉字；常用的折叠式打印纸，每页长度一般为１１英寸和１２英寸两
种，程序或输出结果打在纸缝上是件令人烦恼的事情，为此在９Ｐ２４中增加了自
动走纸换页的功能，默认的页长为１１英寸. 请执行自动换页程序ＡＵＴＯＦＦ，
先定好纸的起始位置，使得打印完一页后，跳过纸缝，这样打出来的程序和结果便
于装订整理．
由于９Ｐ２４驱动程序可模仿２４针打印机来打印汉字，您会发现，用９Ｐ24
打印汉字程序和输出结果，字体美观大方实用．９Ｐ２４可使您的９针打印机为您
发挥更大的作用．
* * * * * * * * * * * * * * * * * * * * * * * * * * *
* 最 新 九 针 打 印 软 件 ９Ｐ１６ 使 用 说 明 *
* * * * * * * * * * * * * * * * * * * * * * * * * * *
简 介
９Ｐ１６是最新９针打印机汉字打印驱动程序，用来取代原来ＣＣＤＯＳ使用的ALL
９Ｐ驱动程序，该软件有以下特色：
１．以软方式实现１６针打印机的输出功能，使９针打印机打出的汉字具有超过１６
针打印机的效果，
２．保留原来ＡＬＬ９Ｐ的１６种输出字体，但９Ｐ１６输出的字体更加美观实用,其
它同９Ｐ２４．
使 用 方 法
一．９Ｐ１６驱动程序装入步骤
（１）．开机，装入ＣＣＤＯＳ．
（２）．在Ａ驱动器中插入有９Ｐ１６程序的软盘．
（３）．使当前盘为Ａ盘，即屏幕显示 Ａ＞
（４）．键入９Ｐ１６，按回车，屏幕上出现三行使用简介，则程序已装好．
二．打印字体选择方法
字体选择方法与ＡＬＬ９Ｐ相同，９Ｐ１６程序装入后默认字体为Ａ字体．
（１）．键盘输入选择字体
在键盘上按Ｃｔｒｌ＋Ｆ１０，提示行出现打印字号选择，键入Ａ－Ｐ对
应十六种字体．
（２）．程序中选择字体
在应用程序中可向打印机送 ＥＳＣ码，＂Ｉ＂及＂Ａ－Ｐ＂之一的序列
来选择十六种字体．
用９Ｐ１６驱动程序，对于８０列的窄纸，Ａ字体一行可打印６０个汉字，Ｉ字体
可打印１２０个汉字；对于１３４列的宽纸，Ａ字体一行可打印１０２个汉字，Ｉ字体
可打印２０４个汉字．
在ＢＡＳＩＣ，ＤＢＡＳＥＩＩＩ等中如何选择字体表格打印方法及宽纸换页均同
９Ｐ２４. 可运行 ＢＡＳＩＣ ＤＥＭＯ２ ，ＢＡＳＩＣ ＤＥＭＯ１．
由于９Ｐ１６驱动程序可模仿１６针打印机来打印汉字，您会发现，用９Ｐ１６打
印汉字程序和输出结果，可比原来的ＡＬＬ９Ｐ在一页纸上打印多一倍的内容，并且字
体美观大方实用．ＢＴ９Ｐ可使您的９针打印机为您发挥出更大的作用．
在ＢＡＳＩＣ，ＤＢＡＳＥＩＩＩ等中如何选择字体表格打印方法及宽纸换页均同９Ｐ２４ 注：可运行 ＢＡＳＩＣ ＤＥＭＯ２ ，ＢＡＳＩＣ ＤＥＭＯ１．
由于９Ｐ１６驱动程序可模仿１６针打印机来打印汉字，您会发现，用９Ｐ１６打印汉字程序和输出结果，
可比原来的ＡＬＬ９Ｐ在一页纸上打印多一倍的内容，并且字体美观大方实用．ＢＴ９Ｐ可使您的９针打印机
为您发挥出更大的作用．
深圳宏建电脑有限公司科技商场展销部
深圳科技商场B111柜
电话 3364793
扩机 182-32601
张鸣钟