PCMania 1/PCM1.ISO/Norton_utilities/setup.exe/README.TXT

Text File | 1999-05-27 | 55.2 KB | 1,194 lines

SYMANTEC CORPORATION - PETER NORTON GROUP                03/01/99
Release Notes for Norton Utilities 4.0 for Windows 95 / 98
------------------------------------------------------------------
Thank you for purchasing Norton Utilities 4.0 for Windows 95/98.
This version of Norton Utilities is designed for Windows 95 and
Windows 98. In this document we will refer to them collectively
as Windows 9x. This version is not compatible with Windows NT,
Windows 3.x, OS/2, or Windows emulators such as SoftWindows.

Please review this document before you install Norton Utilities
or call technical support, as it contains information not
contained in the User's Guide and the online help.

- Attention Windows 98 Users
If you are upgrading, or have upgraded, to Windows 98 from Windows
95, we would encourage you to make a Rescue Disk set in Windows 98.
Due to the changes in the registry between the two operating
systems, any previous Rescue Disks are not usable.

Before and after upgrading to Windows 98, we strongly recommend
running Norton Optimization Wizard and doing a registry
optimization.  This will not only increase the efficiency of
registry size and operations, but will also ensure that you are
safe from potentially hazardous registry corruption.

Windows 98 removes support for SMART drive monitoring by default.
Please see the section on SMART drivers under the Norton System
Doctor section for details on how to set these up on your system.

S3 Vision 964 video adapters exhibit intermittent font corruption
in Windows 98 when Energy Saver features are turned on.  This is
correctable by starting a full screen MS-DOS session and then
exiting the session.

Contents
1.  Installation with Setup Wizard and Uninstall
2.  General Information
3.  Bootable Norton Utilities CD
4.  Connection Doctor
5.  Disk Editor DOS-based program (DISKEDIT.EXE)
6.  Image
7.  Norton Diagnostics DOS-based program (NDIAGS.EXE)
8.  Norton Disk Doctor Windows (NDD32.EXE) and DOS (NDD.EXE)
9.  Norton File Compare
10. Norton Optimization Wizard
11. Norton Protected Recycle Bin and Norton Protection
12. Norton Registry Tracker
13. Norton Space Wizard
14. Norton SpeedStart
15. Norton System Doctor
16. Norton Web Services
17. Norton WinDoctor
18. Norton WipeInfo
19. Rescue Disk
20. Speed Disk
21. System Information
22. UnErase Wizard
23. UnErase DOS-based program (UNERASE.EXE)
24. UnFormat DOS-based program (UNFORMAT.EXE)


1. Installation with Setup Wizard and Uninstall
----------------------------------------------------------------
IMPORTANT: Do not use Norton Utilities versions 8.0 or earlier
for DOS or Windows) on your Windows 9x system.  They are not
compatible with the Windows 9x file system and can cause disk
problems.  Uninstall these programs from your system.
===================
We recommend that you uninstall any earlier versions of Norton
Utilities for Windows 9x from your system prior to installing
Norton Utilities 4.0.
===================
Do not install Norton Utilities 4.0 in a path longer than 128
characters. Do not install Norton Utilities into the \Windows
directory, or into the \Program Files\Symantec directory.
===================
At installation, backups are made of USER.DAT and SYSTEM.DAT
named USER.NU4 and SYSTEM.NU4.  After you make and test a full
rescue disk set, you can safely delete these backup files.
===================
In a custom install, choosing to install Norton System Check will
require that Norton Disk Doctor, Norton WinDoctor, and Norton
Optimization Wizard also be installed.  These will not be
unselectable if Norton System Check is selected.
===================
With a dual boot Windows 9x / Windows NT machine, do not install
Norton Utilities for Windows 9x into the same directory with Norton
Utilities for Windows NT.
===================
If you uninstall Norton Utilities 4.0, or an earlier version of
Norton Utilities, please reboot your system after completing the
uninstall and before re-installing Norton Utilities 4.0 or any
other Symantec product.
===================
When uninstalling Norton Utilities, you are asked whether or not
you want to remove shared files.  In most cases, it is safe to
select "Yes to All".
====================
If you install and then uninstall Norton Antivirus 2.0 while Norton
Utilities 4.0 is installed, an error may appear on startup:
"Unable to dynamically load NPROTECT.VXD".  Re-install Norton
Utilities 4.0 to solve this problem, or call technical support for
assistance. This problem does not occur with Norton Antivirus 4.0.
===================
Users are strongly discouraged from using Uninstall programs to
remove Norton Utilities v4.0.  Use the Windows Add/Remove Programs
function found in the Control Panel.
===================
Norton Utilities requires DCOM for Windows 9x, which is installed
by default.  If this is removed, some components of Norton
Utilities will no longer function, and you will need to reinstall
Norton Utilities.
===================
Norton Utilities standard installation adds LiveUpdate, Norton
CrashGuard, and Norton Web Services to the Add/Remove Programs list
in the Windows Control Panel.  These items can be uninstalled
separately.  LiveUpdate should only be uninstalled when no other
Symantec programs exist on the computer.
===================
On some western European versions of Windows 95 OSR2, you may get
a message about COMPOBJ.DLL being replaced by an older version
than the one that is currently on the machine.  The dialog box
will inform you that the file error will be corrected after
restarting Windows.  This error results from installing
Microsoft's DCOM for Windows 9x.
===================
During the Norton Utilities Standard Installation, both Norton
CrashGuard 4.0 and Norton Web Services are installed.  If the
installation of either of these two components fails for some
reason, you will be prompted to run these installations manually
after the installation of Norton Utilities is complete.  The
installation files for these programs will reside under the Norton
Utilities folder.  If you installed Norton Utilities to the default
location, the command line to run these setup programs would be:

For Norton Web Services:
  C:\Program Files\Norton Utilities\Nwssetup\SETUP.EXE

For Norton CrashGuard:
  C:\Program Files\Norton Utilities\Cgsetup\SETUP.EXE

After installing these programs successfully, the Nwssetup and
Cgsetup folders may be deleted.
===================
During a Custom Install, some components cannot be deselected if
other components are selected.
- LiveUpdate is required by Norton System Doctor, Norton Web
  Services, and Norton CrashGuard.
- Norton Antivirus SE is required by Norton System Doctor and
  Rescue Disk.
- The Basefiles are always required.

If you install Norton System Doctor, we recommend you install all
other Norton Utilities programs to get the full benefits of Norton
System Doctor.
===================
Norton Utilities uses a Windows component called DCOM which comes
with Microsoft Internet Explorer v4.0.  Uninstalling Internet
Explorer v4.0 will remove DCOM, and cause certain components of
Norton Utilities to no longer function correctly. You can run the
DCOM setup program from the \DCOM95 directory on your Norton
Utilities 4.0 CD-ROM to reinstall DCOM should it get removed.
===================
You may select NOT to install NSW (Norton Web Services) on your
system.  However, the file NWS.URL will be installed.  However,
no other peices of NWS will be installed on your system.


2. General Information
---------------------------------------------------------------
If you have a Promise FastTRAK Ultra 33 controller, Norton Disk
Doctor and Norton SpeedDisk may detect problems that do not exist
and should not be fixed.  This is due to problems in the Promise
driver or hardware.  We recommend that you do not use these
applications on drives attached to this controller at this time.
===================
-LiveUpdate and Internet Firewalls
----------------------------------
LiveUpdate downloads updates automatically from an FTP site.  If
your Internet connection is protected by a firewall, you may need
to modify its configuration to permit access to the Symantec
LiveUpdate FTP site.

Use the following data:

  Host:  update.symantec.com
  Outbound data port:  21
  Inbound data port:   20
  Protocol:  FTP

Consult your firewall's documentation or your network administrator
for implementation details.
===================
For safety reasons, several Norton Utilities programs momentarily
lock the hard drive on which they are running.  If the drive is
written to while it is locked, the Norton Utilities program running
will restart. Restarts are most commonly noticed on the drive that
contains the Windows swap file.  For example, if the swap file
changes while Norton Disk Doctor is diagnosing the disk, Norton
Disk Doctor restarts in order to verify the newly written data on
the disk.
===================
Norton Disk Doctor can be used under Windows 9x safe mode to
diagnose and recover drives.  However, many other Norton Utility
programs do not run in safe mode, because the operating system
functions they require are not available.  If you have an emergency
situation and you cannot start Windows 9x normally, use your Norton
Zip Rescue disk set to boot into Windows safe mode, or refer to the
Norton Utilities User's Guide, Chapter 3, for more information.
===================
Hard disk drives with more than 1024 cylinders may, if improperly
partitioned, cause problems with Norton Utilities.  To avoid this
problem, use an Enhanced IDE (EIDE) or SCSI controller, upgrade
your system BIOS, or use a third-party disk partitioning software.
===================
Norton Utilities may have difficulties with other utility software
that use the hard drive in non standard way(s).  If you use a
program like Partition Magic to resize clusters, make sure that you
recreate your rescue disk set and re-run Image.  If you use
Partition Magic to expand the size of the root directory, Norton
Disk Doctor may have difficulties with boot sector repairs.
===================
If you have either the Buslogic BT-757s SCSI adapter for EISA
systems or the Buslogic BT-445s SCSI adapter, add the following
two lines to the SYSTEM.INI file in the Windows directory:
[SYMEVENT]
DOSINT13HOOK=FALSE
===================
The Windows 9x Setup Wizard does not automatically install Quick
View. Quick View must be installed to view a file's contents before
deleting or recovering it in either Unerase Wizard or Space Wizard.

To install Quick View:

  1 Click Settings, then Control Panel from the Start menu.
  2 Double-click Add/Remove Programs.
  3 Click the Windows Setup tab.
  4 Select Accessories from the list box, then click Details.
  5 Select Quick View.
  6 Click OK.
  7 Click Apply.

You will be prompted to insert your Windows 9x disk.
===================
The DOS-based programs that are included with Norton Utilities for
Windows 9x have the following minimum memory requirements:

DOS-based Program          Conventional       Extended
Norton Diagnostics (NDIAGS.EXE)    512K           NONE
Norton Disk Doctor (NDD.EXE)       360K           2 MB
Disk Editor (DISKEDIT.EXE)         360K           2 MB
UnErase (UNERASE.EXE)              360K           2 MB
UnFormat (UNFORMAT.EXE)            360K           2 MB
Rescue Restore (RESCUE.EXE)        512K           NONE

Most of these programs run in protected mode.  Therefore, a memory
manager such as HIMEM.SYS must be loaded.

Note that on machines with large FAT32 partitions, a significant
amount of RAM will be needed for some of the applications.  An 8
gigabyte FAT32 partition will require 64mb of RAM in order to run
NDD.

On some machines, HIMEM.SYS may not detect your hardware correctly,
and may need a /M:1 command line switch to function properly.
Details on the operation of HIMEM.SYS can be found in the
MSDOSDRV.TXT file in your Windows 9x directory.  The proper syntax
in your CONFIG.SYS would be:

device=c:\windows\himem.sys /m:1
===================
The protected-mode DOS Norton Utilities programs may display
"Run-time error R6009 - not enough space for environment" if your
PATH environment variable contains more than 128 characters.
===================
If you run Norton Utilities in DOS, you may wish to add the path
(usually c:\Program Files\Norton Utilities\) to the AUTOEXEC.BAT
file.  The path used in AUTOEXEC.BAT must use the short file name
version of the path.
For example, open AUTOEXEC.BAT and add the line:

PATH=%path%;c:\progra~1\norton~1

(The actual short file name version of the path may be different
for your system than the one above.)
===================
If you receive an error stating your hard drive is misconfigured,
and you are certain that the drive is configured and functioning
correctly, the hard disk partitioning scheme may be incompatible
with Norton Disk Doctor and Speed Disk.  See the appropriate
section below for more information.
===================
Prior to compressing a drive, disable Norton Protection for that
drive.
===================
If you install CleanSweep v3.0, it may install an older version of
MFC42.DLL (dated 10-1-96), which will cause some problems with
some of the Norton Utilities.  This problem does not exist with
CleanSweep 3.01.  If you have this problem, you can copy MFC42.DLL
from the Norton Utilities CD (in the \NU\SYSTEM directory) to your
Windows system directory(C:\WINDOWS\SYSTEM\ if Windows is installed
in the \WINDOWS directory).
===================
Quarterdeck's MagnaRAM and QEMM97 products may cause
"out of memory" errors when attempting to run some of the Norton
Utilities. Please refer to the QEMM97/MagnaRAM user guide to solve
this problem by adjusting the cache size.
===================
Users of Network Associates' VirusScan version 3.1 may experience
system lockups when creating Zip Rescue disks, when running Speed
Disk, when running Optimization Wizard, or when running Norton
System Doctor.  If you are experiencing lockups, try disabling
VirusScan to see if that solves the problem.


3. Bootable Norton Utilities CD
--------------------------------------------------------------
The Norton Utilities CD is bootable.  This means on systems with
2.88MB bootable CD support built into the BIOS, the CD will boot
to DOS for emergency recovery.  This standard is not supported by
some systems may not successfully boot from the Norton
Utilities CD.  Should problems be encountered, please contact the
hardware manufacturer of your System, CD-ROM drive or CD-ROM
Drive Controller to insure they support the 2.88 standard.
===================
When booted, the CD may be displayed as the A: Drive (floppy)
This is normal when booting from the CD.  (Note: Your original
A: Drive may also now be identified as your B:.  Your original
B: drive will be inaccessible.)
===================
Because the bootable image on the CD is formatted as a 2.88MB
floppy, the CD will appear as a 2.88MB floppy diskette.
===================
If you encounter problems booting from the CD, then use the
Emergency floppies provided with Norton Utilities.
===================


4. Connection Doctor
---------------------------------------------------------------
If you phone system requires a dial out Prefix number. (i.e. 9
or 1).  Make sure you have setup the modem correctly.  This is
a problem that Connection Doctor cannot scan or correct.
===================
Connection Doctor does not support ISDN Modems.


5. Disk Editor DOS-based program (DISKEDIT.EXE)
--------------------------------------------------------------
When switching to 32-bit boot record view, the current position of
the cursor will change.  To solve this problem, select the range
of the suspected boot record and then view the selection as a boot
record.
===================
Long file names that use high ASCII characters display as dots in
the directory view.
===================
If Windows reports that it cannot find HIMEM.SYS after running
Disk Editor, rem out all reference to HIMEM.SYS from the CONFIG.SYS
and CONFIG.WIN files.  These references are redundant since
Windows always loads HIMEM.SYS.  Note: Do not rem out references
to HIMEM.SYS from any CONFIG.DOS file you may have.


6. Image
----------------------------------------------------------------
Image may report "Volume Lock Failed." This indicates that another
disk program is currently accessing the disk and Image could not
lock the volume for its own process.  Click OK and try again when
the other program stops accessing the disk.
===================
Programs that rearrange data on the disk, such as Defrag, can
invalidate the saved Image information.  Rerun Image after running
these types of programs.
===================
On a large, extremely fragmented FAT32 drive, Image may report an
"Out Of Memory" error.  Run Speed Disk to correct this.


7. Norton Diagnostics DOS-based program (NDIAGS.EXE)
----------------------------------------------------------------
Norton Diagnostics reboots your computer before performing a
Comprehensive Memory Test.  The drivers for compressed drives are
temporarily disabled during this process.  Start your computer
normally after using Norton Diagnostics so those drivers are loaded
and the drives are properly mounted.
===================
Do not run the Comprehensive Memory Test option from Norton
Diagnostics on a "swapped" compressed drive (where C: is compressed
and another drive is the host drive).  If you accidentally run
Norton Diagnostics in this configuration, rename your
compressed-drive drivers with their original names before
restarting your computer.  To do this, look for the files
DBLSPACE.NDS or DRVSPACE.NDS in your root directory, rename them
DBLSPACE.BIN or DRVSPACE.BIN, respectively, and then reboot.
===================
Norton Diagnostics is known to have a problem with some high speed
processors, such as the Intel Pentium II and the Cyrix/IBM 6x86MX.
NDiags may not identify the speed or type of these CPUs correctly,
and may report spurious and erroneous system board or interrupt
problems.  Please contact technical support for more information.
===================
Do not run the Floppy test on LS-120 drives.  The Disk Change,
Disk Rotation and Disk Speed tests will all fail.


8. Norton Disk Doctor Windows (NDD32.EXE) and DOS (NDD.EXE)
----------------------------------------------------------------
Norton Disk Doctor for Windows restarts its diagnosis if it detects
a write to the disk being diagnosed.  Restarting ensures the
integrity of data on the disk if repairs are required.  A restart
may occur several times during a single Norton Disk Doctor session.
===================
Norton Disk Doctor reports that a hard drive is mis-configured when
the drive fails the drive configuration check.
Possible reasons for this failure include:

a. The drive may have been partitioned on one PC and moved to
another PC that uses a different type of BIOS, or has a different
BIOS setup.

b. The BIOS may have been set up incorrectly for the drive in
question when the drive was partitioned.

c. The BIOS may require an update to correctly support the hard
drive.

d. A program other than FDISK was used to format the drive.

Check with the BIOS manufacturer to make sure that the BIOS
supports the drive and that the BIOS is set up correctly for that
drive, and make sure you have the latest BIOS version.

If you are certain the drive is configured and functioning
correctly, you can start Norton Disk Doctor with the /NOLBA
command-line switch to prevent the drive configuration check
during one run of the program.
NOTE:  Use this command-line switch ONLY if you are certain the
drive is configured correctly. For more information on hard drive
configuration, contact your drive's manufacturer, or visit our
website at http://service.symantec.com

You can force Norton Disk Doctor (and Speed Disk) to skip drive
configuration checking always by adding a DWORD registry value
named NOLBACHECK under
HKEY_LOCAL_MACHINE\Software\Symantec\Norton Utilities
When this is set to 1, the drive configuration check is skipped.
NOTE: Do not set this value unless you are certain that your hard
drive is configured correctly.  For more information on hard drive
configuration, contact your drive's manufacturer, or visit our
website at http://service.symantec.com
===================
Do not run Norton Utilities programs during system startup with
other programs that require exclusive access to a drive.  For
example, do not run Norton Disk Doctor and ScanDisk on the same
drive at startup. Doing so produces an error message.
===================
When restarting Windows after it was not shut down properly, you
may receive the following message: "Error reading configuration
file SYMCFG.BIN."  Press OK to allow Norton Disk Doctor to check
for and repair any disk errors that may have occurred when the
system was shut down.  Once Windows loads, open the START MENU and
choose FIND to locate SYMCFG.BIN on your hard drive.  If you have
more than one hard drive, specify each drive in the FIND program's
LOCATE IN box by typing, for example,
  C:\
for a single drive or
  C:\;D:\
for multiple drives.
When the file is located, right-click the file and choose delete.
When prompted for confirmation, answer YES.
===================
Norton Disk Doctor cannot repair damaged program code in the boot
record.  Use Rescue Disk to restore this data.
===================
Make sure you are running under Windows 9x MS-DOS mode when
repairing the boot record with Norton Disk Doctor for DOS.
===================
If you use Norton Your Eyes Only with the BootLock feature, and
have boot record corruption, you should use the NYEO emergency
recovery disks to recover the boot record instead of Norton Disk
Doctor.
===================
When running NDD for DOS on a computer that contains one or more
drives with invalid boot records, you may receive the message
"Invalid media type reading drive x: (Abort, Retry, Fail?)."
Select Fail, and NDD continues loading.  Then, select the drive to
diagnose the problem.
===================
NDD may not be able to correctly repair drives partitioned with
Partition Magic as it may use non-standard partitioning scheme.
After using Partition Magic to re-partition a drive, update your
rescue disk set. Use Rescue Disk to restore any partition table
or boot record errors on these drives.
===================
If you are using DriveSpace and it accesses a damaged CVF, you may
get a blue screen error message.  This message is not generated
by NDD. Please contact Microsoft for assistance.
===================
On FAT32 drives, depending on the drive configuration and the
amount of memory in your system, DOS-based programs may produce
out of memory errors.
===================
NDD (for DOS) generates a divide by 0 error when attempting to run
on a Windows NT-formatted FAT partition with clusters larger than
32k. 32k clusters are the largest valid clusters for use with
Windows 9x.
===================
If Norton Disk Doctor reports an "invalid drive type" on a system
with an internal Zip drive, the Zip drive may be configured as a
fixed disk in your CMOS.  Remove the Zip drive from the CMOS, or
contact the hardware manufacturer's technical support.
===================
IoMega Zip and Jaz drives have internal automatic bad sector
correction, and will reallocate bad sectors on the fly.  Do not
use Norton Disk Doctor's surface scan function to check for bad
sectors, as this will thwart the internal bad sector detection
and cause problems with your Zip or Jaz cartridge.  IoMega
recommends that you remove Zip and Jaz cartriges from the drive
when not in use to minimize disk damage.
===================
Note: Do not run DiskDoctor DOS on partitions that were created
with Linux FDISK or Disk Druid. If you choose to fix errors on
partitions that were created with these utilities, it is critical
that you make an undo disk.


9. Norton File Compare
----------------------------------------------------------------
Binary files can occasionally be viewed in the text viewer.  These
files appear illegible.
===================
The maximum size of a file is 32,767 lines.


10. Norton Optimization Wizard
---------------------------------------------------------------
We recommend that you close all other programs before running
Optimization Wizard. If a program attempts to alter the system
registry while Norton Optimization Wizard is optimizing the
registry, the settings it is attempting to save will be lost.
Also, do not empty the recycle bin or change Windows settings
during the registry optimization.
===================
Users of WinIce may get an error "Invalid VXD dynamic link call to
device #3, service B" when optimizing the registry with Norton
Optimization Wizard. Do a full system reboot to solve this problem.
Another solution would be to rename NRW16.EXE (in the Norton
Utilities directory) to NRW16.NUL.
===================
Optwiz requires a file called REGOPT.DLL to be present and
registered on your system.   From the START Menu select the RUN
command. In the Dialog box enter the text:
    REGSVR32 "C:\Program files\Norton Utilities\REGOPT.DLL"
    Note: replace the path to REGOPT.DLL with what ever is
    appropriate for your installation
===================
If there is corruption or nonstandard entries in your system
registry, Norton Optimization Wizard will fail to optimize the
registry, and will create a file called BADKEY.OW in your Windows
directory.  This file can be used to locate such entries.

For example, Microsoft Visual C++ v5.0 contains one such corrupted
key (subkeys of hkey_local_machine\Software\Classes\CLSID\
{B3943EF5-CEC5-11CF-AF20-00A0C9034837\) which is split into two
keys: "Component and CLSID" which should actually be: Component
CLSID.  This split key causes Norton Optimization Wizard to fail
unless the key is renamed correctly (delete "Component and rename
CLSID" to Component CLSID).
===================
If you encounter any problems with your system registry, or your
system exhibits odd behavior after doing a registry optimization
with Norton Optimization Wizard, shutdown your system into MS-DOS
mode, switch to your Windows directory, and run RESTREG.BAT. This
restores your system registry to its pre-optimized state.


11.  Norton Protected Recycle Bin and Norton Protection
----------------------------------------------------------------
To configure Norton Protection features, right-click the Recycle
Bin icon, then click Properties on the context menu.
===================
IMPORTANT: Do not attempt to purge protected files while utilities
such as Speed Disk or Norton Disk Doctor are running.
===================
Norton Protected Recycle Bin protects a maximum of 1500 files.
===================
Norton Protection uses available free space to protect your files.
Once the free space available reaches a specified threshold,
Norton Protection starts purging the oldest protected files to
free up just enough space to protect the latest deletion.  By
default, this threshold is set to 10% or 10 MB of the current disk
partition, whichever is less.
===================
If the "Show Norton Protection" status is checked and you select
the "Use Large Icons" check box on the Plus! tab in Display
Properties, then the Recycle Bin icon may appear stretched or
shrunken.  To fix this, right-click on the Recycled Bin icon, and
select Properties.  Select the Desktop Item tab and uncheck Show
Norton Protection status.  Click Apply. Then click Show Norton
Protection Status and click Apply again.
===================
When using NDOS, some file deletions of read-only files may not
be protected.  Use 4DOS for Windows 9x instead.
===================
You cannot format drives currently protected by Norton Protection.
Disable Norton Protection before formatting a drive.
===================
Restoring a registry snapshot from Norton Registry Tracker may
mean the Norton Protection shield status is incorrect.  To
resynchronize the status, disable Norton Protection and then
re-enable it.

12.Norton Registry Tracker
----------------------------------------------------------------
To track files with long names (greater than 12 characters), track
the files individually instead of tracking the folder that contains
them.
===================
If you track folders, then a hidden or system file under a tracked
folder does not affect a snapshot.  To track a hidden or system
file, make it unhidden or non-system.
===================
If a snapshot is taken of a file tracked by Norton Registry Tracker
while the file is being edited inside another application, an error
message may appear when you try to save the file or when the
application's auto-save feature activates. The message says the
file is in use.
===================
Files created and Deleted from a tracked folder in DOS mode do not
cause an automatic snapshot.  Solution: Manually force a snap shot.
===================
Do not use Registry Tracker to track any text or data files
contained in a folder that is protected by Norton Your Eyes Only.
Doing so may cause Registry Tracker to take repeated unchanging
snapshots.  This is completely benign, but may cause extremely
high CPU usage.

13. Norton Space Wizard
----------------------------------------------------------------
Space Wizard, in its "commonly discardable files" section, lists
folders named CACHE as potential free space. Most programs use
cache directories to store temporary data so it can be accessed
more quickly by the system.  However, a few programs, such as Kai's
Power Soap, store more permanent data in the cache folder.  Use
caution when deleting files from a cache folder. If you are not
sure the files can be safely removed, compress them instead.

14. Norton SpeedStart
----------------------------------------------------------------
The very first time an application is loaded after Norton
SpeedStart (NSS) is installed, it may load more slowly than usual
because NSS is profiling the loading process. NSS uses this
information to speed up all future application loads.  Immediately
after installing Norton Utilities and rebooting, Norton SpeedStart
profiles many applications for the first time, so the first boot
may be noticeably slower than normal.
===================
Because functionality similar to SpeedStart is built in to Windows
98, SpeedStart is disabled in Windows 98.


15. Norton System Doctor
----------------------------------------------------------------
The Disk Doctor, Disk Doctor (Surface Test), Disk Health, Image,
and Norton AntiVirus SE Scan sensors can be set to Monitor All
Local Hard Drives from the Drive tab of the sensor Properties.
(The Disk Health sensor is set to Monitor All Local Hard Drives by
default.) If a sensor is set to Monitor All Local Hard Drives,
there should be no more than one of that sensor type in the Norton
System Doctor sensor panel.
===================
The CrashGuard+, Rescue Disk, and WinDoctor sensors are system
wide, and not drive specific.  Only one of each should be active
at any time.
===================
Norton System Doctor may report 100% CPU usage when Microsoft's
System Monitor (SYSMON) program is running, because System Monitor
uses all idle processor time while displaying its processor usage
gauge.
===================
Norton System Doctor may report 100% CPU usage during a pcANYWHERE
Session due to the high activity generated by constant video
updates and modem transmissions.
===================
Using High Contrast (White on Black) Accessibility Options may
cause Norton System Doctor's text to be invisible.  Adjust System
Doctor's sensor colors, or turn off the High Contrast features.
===================
Norton System Doctor's sensors have been configured for optimum
performance on most systems.  Do not increase the frequency of any
sensor that can automatically run a Norton Utilities program, such
as Rescue, Image, Disk Health, or Disk Optimization sensors. If you
notice a decrease in a drive's performance while Norton System
Doctor is monitoring it, decrease the frequency with which Norton
System Doctor monitors that drive.
===================
If you have Always on Top disabled in a docked Norton System
Doctor, you will not be able to move windows past the area it
occupies.
===================
In rare cases, in a vertically docked Norton System Doctor, its
width may be larger than necessary to accommodate the current set
of selected sensors.  To get around this problem, close and re-run
the program.
===================
Norton System Doctor configuration files saved with versions prior
to 3.0 of Norton Utilities for Windows 9x are not compatible with
version 4.0. Please set up a new System Doctor configuration with
version 4.0.
===================
Upgrading to Windows 98 will remove the SMARTVSD.VXD file from the
WINDOWS/SYSTEM/IOSUBSYS directory if there is such a file there.
This means that if you had operating SMART sensors prior to
upgrading you will have to re-install using SMARTDRV.EXE on the NU
CD to get them to work after the upgrade.
===================
If you believe your system has a SMART (Self-Monitoring And
Reporting Technology) hard drive, but the SMART sensor in Norton
System Doctor reports that no SMART drives can be found on your
system, please contact your hardware manufacturer or try
installing the Microsoft SMART driver we provide in the SMARTDRV
folder on the Norton Utilities CD. For more information, see the
SMARTDRV.TXT located there.
===================
If you connect to an Internet Service Provider (ISP) such as
CompuServe 3.01 or America Online using dial-up networking, do not
enable the Internet sensors in Norton System Doctor.  ISPs that use
dial-up networking do not disconnect properly if they detect
another application using the internet connection.  This could
cause your ISP charges or your telephone bill to be higher than
expected.
===================
If Norton System Doctor alarm is postponed for a set amount of
time, the alarm may show again before that time has elapsed. This
happens if the condition that caused the alarm is removed (which
clears the set postpone) and then the condition occurs again.
For example, if the default disk space alarm displays. You can
dismiss the alarm for a specified time period. If you then clean up
your drive and re-fill it before the time period has elapsed, System
Doctor will displays the alarm anyway (because it perceives it as
new error condition).
===================
After running a Norton Utilities program to correct a problem
indicated by a Norton System Doctor sensor, some stoplight sensor
faces may not update immediately to indicate the condition is
resolved. To update the sensor display after fixing the problem,
right-click the sensor, and choose Update from the context menu.


16. Norton Web Services
----------------------------------------------------------------
If you get an "Unable to load monitoring VXD error 2" when you
install an 'undoable' patch, you can fix this problem by going to
the \NWS directory on your Norton Utilities CD-ROM and running
SETUP.EXE.  This will reinstall the monitoring VXD (symmonit.vxd)
and solve the problem.


17. Norton WinDoctor
----------------------------------------------------------------
Program dependency errors cannot always be repaired because
programs can lose required files and require re-installation.
Norton WinDoctor's "Repair" button is greyed out if it cannot find
a program dependency, but it does not inform the user when "Repair
All" is used.
===================
When a program is moved from one disk drive to another, WinDoctor
may not always be able to repair all broken associations and get
the program working again.  Generally, if you want to move a
program to a different drive, you should uninstall the product and
re-install it.
===================
Norton WinDoctor cannot be used to diagnose system problems when
Windows is started up in Safe Mode.  WinDoctor can only be used
in Safe Mode to undo a previously executed repair.
===================
Norton WinDoctor will not diagnose broken links to a hard drive
which has been uninstalled.  Turning off the "removable drive"
analysis agent enables Norton WinDoctor to show these errors.
===================
If Norton WinDoctor starts up (with the system NOT in Safe Mode),
but does not have any tests in its list, you may have an
installation error. Switch to the Norton Utilities folder and type:
 SIREGIST.EXE "C:\Program Files\Norton Utilities\siregist.txt"
 or reinstall Norton Utilities. This enables all tests.
===================
An "An error (4) occured while examining your registry." can be
fixed by creating a temp folder called c:\windows\temp\.

18. Norton WipeInfo
---------------------------------------------------------------
Norton WipeInfo will not wipe the slack space on files located on
Network/Shared drives.  Nor will it remove the Directory entry.
====================
Norton WipeInfo will erase directory entries only if it can get
a drive lock.  If the drive is in use by another utility or by
the operating system the information in the files and folders
will be wiped, however, the directory entries may remain.  When
using Unerase, it may appear that the files or folders are
recoverable.  In fact, the data has been wiped.
====================
Files previously deleted from a folder before running wipeinfo
on a folder will not be wiped. To insure those files are wiped
as well, Run WipeFreeSpace.
====================
-To fix continual restarts of WipeFreeSpace:

From My Computer RIGHT-CLICKing on the drive and select
WipeFreeSpace.  This will run without the UI.
------
Network/internet connections can cause writes to the disk.
Disconnect from your network and run WipeFreeSpace again.cc


19. Rescue Disk
----------------------------------------------------------------
Creating a Norton Zip Rescue set now requires that you restart your
system using the rescue set, in order to complete the set creation.
Restarting your system after an update is optional, but highly
recommended.
===================
We recommend shutting down any applications running in the
background before creating a rescue set.
===================
Disk Manager partitions are not compatible with Rescue Disk.
===================
Rescue Disk 4.0 does not support rescue disks created by previous
versions of Norton Utilities.  Please make and test a new rescue
disk set.
===================
Rescue Disk requires 1.44MB 3.5" floppy diskettes for Zip, Jaz and
basic rescue sets.  720K disks and 5.25" diskettes are not
supported. 2.88MB and 120MB LS-120 floppy drives may be used to
create Rescue disks, but only using 1.44MB floppy diskettes.
===================
Norton Zip Rescue does not support creating Zip rescue sets with
USB Iomega drives.  Norton Zip Rescue doesn't detect if the user
has a USB drive.
===================
Rescue Disks cannot function properly or completely operations in
an emergency if you have not installed the following Norton
Utilities components:

For a basic rescue disk set:
- Norton Utilities DOS applications

For a Norton Zip Rescue disk set:
- Norton AntiVirus SE
- Norton Disk Doctor
- Norton UnErase Wizard

If, when you installed Norton Utilities, you chose to perform a
Compact Installation, or a Custom Installation that did not include
These components, your rescue disk set may not be complete.
===================
Norton Zip Rescue disks are closely tied to the operating system.
If you are not using a full release version of Windows 95
(build 950 or an OSR release) or Windows 98, Zip Rescue may not
have full functionality.
===================
If booting the Zip Rescue Disk causes an error stating
"VFAT & DOS Volume on drive C: layouts mismatched",  you may have
boot record corruption on the C: drive. In this case, boot from
the emergency recovery disk included with Norton Utilities.
NOTE: If you're using Norton Your Eyes Only with the BootLock
feature, use the NYEO emergency recovery disks to recover the
boot record instead of Rescue Disk.
===================
If your system loads virtual device drivers (VxDs) from SYSTEM.INI,
and the C: drive does not come up, Zip Rescue may show "Error
reading cluster on drive C" messages while booting up.
Choose [Abort] or [Fail], and Zip Rescue should continue booting.
===================
Do not save rescue items to a compressed floppy disk.  When rescue
items are stored on a compressed floppy, the floppy cannot be used
as a boot disk.
===================
You cannot save rescue items to the root of any hard disk.  The
Root typically contains important data that could be overwritten.
===================
The CMOS checkbox in the DOS Rescue Recovery application may
sometimes falsely indicate that the CMOS should be restored.  This
is because some motherboards change the CMOS values when hard drive
detection fails. If you see that the CMOS should be restored, and
you have already allowed rescue to recover it, try continuing with
the recovery anyway.
===================
SCSI drive problems: If Rescue Disk's default set of SCSI drive
adapters does not include the one necessary for your Zip drive,
Rescue Disk displays an error and creates a ZipAdapter*.reg file in
the Norton Utilities folder. This file can be used to modify the
registry as necessary to enable your Zip drive.

NOTE:  If you have more than one zip drive attached to a
non-supported SCSI adapter, there may be more than one of these
files on your system. To fix this problem:

1.  Get real-mode drivers from the manufacturer of each unsupported
    SCSI adapter.
2.  Copy your CONFIG.SYS file to CONFIG.BAK
3.  Install the new drivers.
4.  Open config.sys and config.bak for comparison in Notepad
    (or any other text editor.) Find the device line(s) that has
    been added to config.sys by the SCSI driver.
5.  Select ZipAdapter*.reg in Windows Explorer, where * is a number.
6.  Right-click and choose Edit to open the file in a text editor.
    It looks something like this:

    REGEDIT4

    [HKEY_LOCAL_MACHINE\Software\Symantec\NortonRescue\
    4.0\Setup\Zip Adapters\Your Adapter]
    "L0"=" "
    "F0"=" "

7. Add the line(s) from config.sys into the *.reg file LO key. If
   there are two drivers, you must add one to each line.
   For example: "L0"="device=xxx.sys"
                "L1"="device=yyy.sys"
8.  Add the SCSI driver file name(s) referred to in the LO key to
    the F0 key. There should be no path.
    For example: "FO"="xxx.sys"
                   "F1"="yyy.sys"
9.  Save and close the file. It would look like this:
    REGEDIT4

    [HKEY_LOCAL_MACHINE\Software\Symantec\
    Norton Rescue\4.0\Setup\Zip Adapters\Your Adapter]
    "L0"="DEVICEHIGH=SCSIDRV.SYS "
    "F0"="SCSIDRV.SYS "

10. Copy the driver files into the \Norton Utilities folder.
    In this example, you would copy xxx.sys and yyy.sys.
11. Double-click the file in Windows Explorer. The file's information
    is merged into the registry automatically.
12. Run Rescue Disk and the Zip/Jaz drives should appear.
===================
If you fail to boot a Norton Zip Rescue disk into full Windows and
boot into Safe Mode instead, you can try deleting the BOOTSAFE.TXT
file from the Windows directory on your Zip disk.  This will allow
Norton Zip Rescue to try booting into full mode again.  If the
recovery fails to boot into Normal Mode again, allow it to use Safe
Mode.
===================
Some customers have reported problems with Norton Zip Rescue not
functioning correctly when running in conjunction with MagnaRAM or
QEMM97.  If Rescue crashes on your system, try disabling the
MagnaRAM option to see if it clears up the problem.
===================
Zip drives attached to PCMCIA SCSI cards are not supported by
default.  Limited support is available.  To enable this, start
rescue32.exe with the /PCMCIA switch.  To do this, choose start
menu / Run, select the Browse button, browse to the Norton
Utilities directory and select RESCUE32.EXE,and add in "/PCMCIA"
at the end.  The run command would look something like:
"c:\program files\norton utilities\rescue32.exe" /PCMCIA
===================
If you make significant changes to your system, such as adding new
hardware or changing your hard drive layout, you should reset Zip
Rescue and create a new Zip Rescue set.  To do this, run Rescue32
with the " /RESET" switch.  Choose StartMenu / Run, select the
Browse button, browse to the Norton Utilities directory and select
RESCUE32.EXE, and add in " /RESET" at the end.  The run command
would look something like:
"c:\program files\norton utilities\rescue32.exe" /RESET
===================
If your Zip Rescue zip disk fills to capacity with files that
Windows requires to start, Norton System Doctor's Rescue sensor
will no longer turn red (since it is unable to copy any new files
to the disk).  If this occurs, we recommend that you reset Zip
Rescue, via the procedure outlined above.
===================
If you start up a Zip Rescue set and Windows displays error
messages or blue screens reporting that it cannot load a certain
VxD or driver, try to continue.  In many cases, these missing files
are not essential to the operation of Zip Rescue and Recovery
Wizard will still work to recover your system.


20. Speed Disk
----------------------------------------------------------------
We strongly recommend that you disable any programs, including
Screen savers and power saver features, before running Speed Disk
on compressed drives.  To check for programs currently running,
press Ctrl-Alt-Del ONCE. End task on all items except for Explorer
before running Speed Disk.
====================
Speed Disk is designed to restart upon detection of writes to the
Disk being optimized.  Restarting ensures the integrity of the data
on the disk during optimization.  A restart may occur several times
during a single session.
====================
Speed Disk reports that a hard drive is incorrectly configured when
the drive fails the drive configuration check.  Possible reasons
for this failure include:
- The drive may have been partitioned on one PC and moved to
  another PC that uses a different type of BIOS, or has a
  different BIOS setup.
- The BIOS may have been set up incorrectly for the drive in
  question when the drive was partitioned.
- The BIOS may require an update to correctly support the hard
  drive.
- A program other than FDISK was used to format the drive.

Check with the BIOS manufacturer to make sure that the BIOS
supports the drive and that the BIOS is set up correctly for that
drive, and make sure you have the latest BIOS version.

If you are certain the drive is configured and functioning
correctly, you can start Speed Disk with the /NOLBA command-line
switch to prevent the drive configuration check during one run of
the program. NOTE:  Use this command-line switch ONLY if you are
certain the drive is configured correctly. For more information on
hard drive configuration, contact your drive's manufacturer, or
visit our website at http://service.symantec.com

You can force Speed Disk (and Norton Disk Doctor) to skip drive
configuration checking always by adding a DWORD registry value
named NOLBACHECK under HKEY_LOCAL_MACHINE\Software\Symantec\Norton
Utilities When this is set to 1, the drive configuration check is
skipped. NOTE: Do not set this value unless you are certain that
your hard drive is configured correctly.  For more information on
hard drive configuration, contact your drive's manufacturer, or
visit our website at http://www.symantec.com/techsupp/
===================
If Speed Disk needs to "Pack" your DoubleSpace or DriveSpace 2
volume, it can take several hours or longer.  Using Space Wizard to
free up space can help speed the overall optimization process.
===================
Speed Disk locks the compressed volume file (CVF) while optimizing.
Whenever a CVF is locked, the operating system also locks the host
drive (and any other CVF's on the same host drive).  Other disk
programs may fail to run on the host drive while the lock is in
effect.
===================
If Speed Disk is run while another Norton Utilities program has a
drive locked, the Start button is grayed out.  We recommend that
you wait until the other program finishes before you run Speed
Disk.
===================
Speed Disk can be programmed to automatically treat certain files
as being unmovable.  A key can be added in the registry to:
HKEY_LOCAL_MACHINE\Software\Symantec\Speed Disk Unmovable
Files\Attributes DWORD value x=a, where x=drive letter and
a=binary attribute file. Developers of software programs that
rely on unmovable files for copy protection should set this key.
Contact your software manufacturer's technical support for more
assistance.
===================
If you have unmovable files on your drive, and have Speed Disk set
to not move unmovable files, Speed Disk may be unable to reach 100%
defragmentation of the drive.
===================
Users of BestCrypt data encryption software from Jetico Inc. should
add a string entry under HKEY_LOCAL_MACHINE\Software\Symantec\Speed
Disk Unmovable Files" called "*.jbc" and set the value to also be
"*.jbc"


21. System Information
----------------------------------------------------------------
For network, CD, and compressed drives, the Disk Usage Selection on
the Drive tab is the total size of all selected items as reported
by the file system.  This does not include "slack" space (space
wasted due to the device's cluster size), so the total amount
allocated is often slightly more than the size displayed by System
Information.
===================
If the Windows 9x Device Manager shows an improperly configured
device(represented by a yellow "!" symbol), System Information may
be unable to display the correct information for this device.
Also note that disconnected Plug & Play devices may be reported as
configured by the Windows 9x Device Manager.  System Information
will likely display a disconnected Plug & Play device as configured
and active.
===================
System Information identifies a NexGen 586 computer as having a
386-based processor.  The NexGen processor uses a 386 instruction
set.
===================
The Total Windows Memory value (located below the pie chart in
System Information's Memory tab) is calculated by adding together
the following numbers:
Total physical memory
- total current swap file size
- total current free space on disk if Windows is managing the
  swapfile
- total size of all currently loaded 32-bit applications

The last item is included in the total calculation because 32-bit
applications under Windows 9x are "swapped out" by flushing them
from memory, and then re-loaded from the original disk image when
they need to be "swapped in."
===================
System Information reports the bus type for "hybrid bus" systems as
follows:
    VL/ISA = ISA
    VL/EISA = EISA
    PCI/ISA = PCI
    PCI/EISA = PCI
===================
It may take System Information an extended amount of time to gather
information about network resources on large networks.
===================
Printing a report while using some versions of Adobe Type Manager
ATM) may cause the reversed text headings to print incorrectly.
===================
The physical details for large drives over 8.4 gigabytes may be
reported incorrectly as 1023 cylinders, 63 sectors per track, and
heads of 255.
===================
The option for drive benchmarking is disabled on CD-ROM drives.  To
obtain similar results, manually set the supplemental cache size to
small and the access pattern to no read ahead for that drive, and
then run the logical benchmark.
===================
If you run the drive benchmark while using the Promise DC4030-VL2
EIDE disk controller, the system may hang.  See the troubleshooting
section of the controller's user manual for possible solutions,
such as using only one VESA card in the system.
===================
To learn more about benchmarking your computer, click Help from
the System Benchmark dialog.  Please note the following:

-CMOS settings can be used to enable/disable the L1 and/or L2
 cache.  If the CPU seems slower than it should, verify the cache
 settings.
-Some variation in the benchmark results is normal.  System
 Information is designed to exclude common outside factors, such
 as most hardware interrupts, active applications, disk swapping,
 etc. However, some low level system events cannot be completely
 factored out.  These events may cause minor variations in
 benchmark results.
-Although your computer may be the same CPU and MHz speed as
 other computers, it does not mean that it will produce the same
 benchmark results.  Various other factors, such as the type and
 speed of the system bus and memory, and the amount and
 architecture of the memory cache, are accounted for and affect
 the speed of your computer and the results of the benchmark.


22. UnErase Wizard
---------------------------------------------------------------
The Recently Deleted Files list shows the last 25 deleted files
that are recoverable.  However, if some of the files have been
overwritten, you will not see 25 files in the list.
===================
If you delete a file on a floppy disk from an MS-DOS prompt, and
you specify filename letters after a wildcard (e.g  DEL
*ILENAME.TXT as opposed to DEL FILENAME.TXT or DEL *.TXT), then
UnErase Wizard shows the file as Unrecoverable in its Recently
Deleted Files page.  Right-click in the center of the file list
and select "Show Unrecoverable Files". To see if the file is
actually recoverable, click Next and use the subsequent Wizard
pages to search the floppy disk.
===================
If Quick View is not functioning, then refer to the note under
"General Points of Interest" earlier in this document.


23. UnErase DOS-based program (UNERASE.EXE)
----------------------------------------------------------------
The DOS version of UnErase may run out of memory if you use the
Change Directory or View All Directories commands on disks with
many subdirectories, such as network disks.  To avoid this problem,
use the file list to navigate to the directory you want.
===================
When files are deleted using the deltree command from an MS-DOS
window in Windows 9x, you cannot use the Unerase button in the main
UnErase/DX dialog box to recover any of these files.  When you
select View All Directories from the File menu and try to recover,
you will get the error message "Error reading directory.  It may be
erased." To work around this, use "Unerase To" from the File menu
instead.


24. UnFormat DOS-based program (UNFORMAT.EXE)
----------------------------------------------------------------
Long file names are not recoverable on floppy disks.
===================
UnFormat does not work on compressed disks.
===================
On FAT32 drives, depending on the configuration of the drive and
the amount of memory in your system, UnFormat may produce a General
Protection Fault due to lack of memory.
===================
Choosing to partially restore any information will disable the
automatic unerase feature.  Run NDD after restoring to reconstruct
lost files.
===================
Due to the dynamics of FAT32 file systems, UnFormat may not always
detect when the cluster size has been changed.