|
Table of Contents
Installation
with Setup Wizard and Uninstall
General Information
Bootable Norton Utilities CD
Disk Editor (DISKEDIT.EXE)
Image
Norton Diagnostics
Norton Disk Doctor
Norton File Compare
Norton Optimization Wizard
Norton Protected Recycle Bin and Norton Protection
Norton Registry Tracker
Norton SpeedStart
Norton System Doctor
Norton WinDoctor
Norton Wipe Info
Rescue Disk
Run
Utilities From CD
Speed Disk
System Information
UnErase Wizard
UnFormat (UNFORMAT.EXE)
áErratum
á
⌐ 1995-2000 Symantec Corporation.
All rights reserved.
|
|
Norton
Utilities 2001 for Windows 95/98/Millennium/NT/2000
|
Norton UtilitiesÖ gives you more effective
problem solving than any other product.
Thank you for purchasing Norton Utilities 2001 for Windows
95/98/Millennium/NT/2000. Please review this document before you install
Norton Utilities 2001 or call technical support, as it contains information
not contained in the UserÆs Guide and the online help.
|
|
|
IMPORTANT:
Do not use Norton Utilities versions 8.0 or earlier for DOS or Windows 3.xx
on your Windows 95/98/Millennium system. These versions were designed for
earlier versions of DOS and Windows and are not compatible with the Windows
9x/Millennium file system. Disk problems will occur if prior versions are
used.
Please
note that as of this version of Norton Utilities, we no longer support the
original version of Microsoft Windows 95. Shortly after the original
release, Microsoft released the second edition of Windows 95. This is known
as OSR2 or version 950 B.
Norton
Utilities 2001 supports OSR2 and higher versions.
To
check which version you are using, right click on My Computer, and go to
Properties. On the screen displayed you will see the version number. If it
shows "950 B" then you are using OSR2. If it shows
"950" then you are using the original version. In this case, you
should upgrade to a newer version of Microsoft Windows.
Norton
Utilities may not be installed in Safe Mode. Please boot into Normal mode prior
to installing Norton Utilities. If you are unable to boot into Normal mode,
run the utilities from the CD in Safe Mode to resolve any issues. If you
are unable to install in Normal mode, please review
the
following documents located in the TechBltn folder on
the
Norton Utilities CD-ROM: NU-CLE95.HLP and NU-CLE98.HLP.
We
recommend that you uninstall any earlier versions of Norton Utilities for
Windows 9x from your system prior to installing Norton Utilities 2001.
Norton
Utilities 2001 supports only the released version of Windows Millennium and
Windows 2000. At the time of writing there are still release candidates of
these operating systems in the field.
On
Windows NT and Windows 2000 we require that the volume you are installing
to support both 8.3 and long file names.
Do not
install Norton Utilities 2001 in a path longer than 128 characters.
Norton
Utilities 2001 cannot be installed into a directory with Double Byte
Characters.
Do not
install Norton Utilities 2001 into the \Windows directory, or into the
\Program Files\Symantec directory.
On a
dual-boot Windows NT/2000 with Windows 9x/Millennium system, Norton
Utilities 2001 must be installed to different drives if the application is
required under both operating systems. Installing to the same drive, even
to different directories, is not supported.
At
installation, backups are made of USER.DAT and SYSTEM.DAT named USER.NU5
and SYSTEM.NU5. 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 de-selectable if Norton System Check is
selected.
During
a Custom Install, some components cannot be de-selected if other components
are selected. For example, Norton System Doctor requires LiveUpdate. The
Base files are always required.
If you
install Norton System Doctor, we recommend you install all other Norton
Utilities 2001 programs to get the full benefits of Norton System Doctor.
If you
uninstall Norton Utilities 2001, or an earlier version of Norton Utilities,
please reboot your system after completing the uninstall and before
re-installing Norton Utilities 2001 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 2001
is installed, an error may appear on startup: "Unable to dynamically
load NPROTECT.VXD". Re-install Norton Utilities 2001 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. Use the Windows Add/Remove Programs function found in the
Control Panel.
Norton
Utilities 2001 uses a Windows component called DCOM, which comes with
Microsoft Internet Explorer 4.0. Uninstalling Internet Explorer 4.0 will
remove DCOM, which causes certain components of Norton Utilities 2001 to no
longer function correctly. If DCOM is removed, you can run the DCOM setup
program from the Support\DCOM95 directory on your Norton Utilities 2001
CD-ROM.
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.
Norton
Utilities 2001 standard installation adds LiveUpdate to the Add/Remove
Programs list in the Windows Control Panel. This item can be uninstalled
separately. LiveUpdate should only be uninstalled when no other Symantec
programs exist on the computer.
We have
observed occasional problems when uninstalling TalkWorks 3.0 when Norton
Utilities 2001 is installed. We are currently investigating this irregularity.
During
the Norton Utilities 2001 Standard Installation, Rescue and Live Update are
installed. These are special components of Norton Utilities and require
their own installation process. If the installation of any of these
components fails for some reason, you can run these installations manually
after the installation of Norton Utilities 2001 is complete. To manually
install any of these components, insert the Norton Utilities 2001 CD into
your CD Rom Drive. The CD Start Panel should load automatically. Select
"Browse the CD" from the menu.á
To reinstall Rescue Disk, type:
á \NU\RESCUE\SETUP.EXE
To reinstall Live Update, type:
á \SUPPORT\LUPDATE\LUSETUP.EXE
Return to top of pageá á
|
|
If you intend to
have this new Norton product installed along with any 2000 version Norton
product on your computer, the LiveAdvisor button on the menu bar of your
2000 version Norton product will be removed. As LiveAdvisor is no longer being used for information
delivery, this is no loss in functionality to you. As was outlined in the
final LiveAdvisor messages, Symantec has replaced the LiveAdvisor delivery
mechanism with information on the Symantec web site
(http://www.symantec.com) and product-specific newsletters
(http://www.symantec.com/techsupp/bulletin/index.html). In this way we can
offer information of specific interest to you in the fastest possible
fashion.
The
Norton Utilities 2001 DOS-based programs do not support NTFS volumes.
Please be aware of this when you create either the Emergency Disks or the
Rescue Disks.
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.
Norton
Utilities 2001 does not support running in operating system host
environments, binary conversion environments or emulators (such as VMware,
Odin and Wine respectively).
LiveUpdate
and Internet Firewalls: LiveUpdate downloads updates automatically
Symantec's internet 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 2001 programs momentarily lock the
hard drive on which they are running. If the drive is written to while it
is locked, the Norton Utilities 2001 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.
With
FMV Biblio Notebooks, when selecting the Multimedia tab, a dialog may show
up saying "Open File Error. There was no CD-I or Video CD detected on
your System". You may get this error message when there are duplicate
entries for multimedia device drivers. To resolve it, open the Control
panel/Multimedia and make sure there are no duplicate device drivers
registered. If there is a duplicate driver please delete one of the
duplicates.
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 2001 User's Guide 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 2001 may have difficulties with other utility software products
that use the hard drive in a non-standard way. 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 UnErase Wizard.
To
install Quick View:
á 1 From the Start Menu, Click Settings,
then Control Panel.
á 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.
DOS-Based
Programs that are included with Norton Utilities 2001 for Windows 9x have
the following minimum memory requirements:
|
DOS-based
Program
|
Conventional
|
Extended
|
|
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.
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
Norton Utilities 2001 programs for DOS 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 2001 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 mis-configured, 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 2000 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, running Speed Disk, running Optimization
Wizard, or running Norton System Doctor. If you are experiencing lockups,
try disabling VirusScan to see if that solves the problem.
Third-party
IFS drivers (such as the FAT32 driver from sysinternals.com for Windows NT)
are not supported by any of the Norton Utilities components.
If you
utilize an enhanced hard drive controller (such as a RAID controller, or an
ATA/66 or ATA/100 controller) be sure to install the drivers that are supplied
with it. Without the drivers the controller and/or attached drives may
return incorrect information to the various modules of Norton Utilities.
Under Windows 9x, Norton Utilities 2001 does not support
NTFS partitions or FAT16 drives with 64Kb clusters.á These are available under Windows NT and
Windows 2000 only.
Not all Norton Utilities modules may be run when booted
from a Norton Zip Rescue disk.
Return to top of pageá
á
|
|
Bootable Norton Utilities CD
The Norton Utilities 2001 CD is bootable. This means on
systems with 2.88 MB bootable CD support built into the BIOS, the CD will
boot to DOS for emergency recovery. This standard is not supported by some
systems and 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 ensure they support the
2.88 MB standard.á
When booted, the CD may be displayed as
the A: Drive (floppy) This is normal when booting from the CD. In this
situation, the 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, use the Emergency floppies provided
with Norton Utilities.
The bootable CD does not support running Norton Disk
Doctor on NTFS partitions or FAT16 drives with 64Kb clusters (available in
Windows NT and Windows 2000 only). For this functionality the complete
Norton Disk Doctor package must be installed on the computer.
Return to top of page á
|
|
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.
Return to top of page á
|
|
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.
Return to top of page á
|
|
If you have ProComm Plus installed, when you run the
Printer test, ProCommÆs fax program will start. This causes the Printer
test to wait until you close this fax program. Close it, and the test will
complete.
If you have WinFax installed, you may encounter problems
running the
Modem test. If WinFax is open, close it and do the test
again.
Memory test fails on systems with more than 256MB of
RAM. Norton Diagnostics cannot run a memory test on systems having more
than 256 MB of memory. This appears to be due to the fact that Windows 95/98
often has a problem allocating the correct amount of memory to the disk
cache on systems with more than 32 MB of RAM. To resolve this problem,
you'll need to limit the size of the disk cache file through the SYSTEM.INI
file.
To limit the size of the disk cache file:
1. Click Start and choose Run. The Run dialog box
appears.
2. Type:
SYSEDIT
and click OK.
3. Click the SYSTEM.INI title bar to display the file.
4. Choose the Search menu and click Find.
5. Type:
VCACHE
and click Next.
6. When you find the [vcache] section, add the
MinFileCache= and MaxFileCache= lines to it, as shown below, (if there is
no [vcache] section, create it). These settings limit the size of the disk
cache file to between 5 and 8 MB. This should be acceptable for nearly all
systems, regardless of the size of the hard drive and the amount of RAM.
[vcache]
MinFileCache=5120
MaxFileCache=8192
7. Choose the File menu, and click Save.
8. Close the System Configuration Editor.
9. Restart the computer.
You should now be able to run the Norton Diagnostics
memory test without any problems.
On some Compaq systems you may not hear any sound from
the PC Speaker test. On these systems, Compaq redirects the PC Speaker
sound to the sound card.
The CD-ROM test is designed to work with CD-ROM disks.
The test may not function correctly with an Audio CD in the drive.
The CD-ROM test is designed to verify the functionality
of the CD drive and not the integrity of the CD. The test does read data
off the disk, but it may not encounter any damaged areas on the physical
disk during the test.
If you are using MouseKeys from Control Panel's
Accessibility Options, the keyboard and keypad tests will not work
properly.
Norton Diagnostics does not support Windows Safe Mode.
When Windows is booted into Safe Mode, many of the drivers Norton
Diagnostics needs are not loaded.
If two sound cards are installed in a system, one
on-board, the other a plug-in card, Norton Diagnostics will test the
on-board sound card unless drivers for it are removed and drivers for the
additional card installed.
Return to top of page á
|
|
Note: Do not run Norton Disk Doctor 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.
Running Speed Disk frequently will improve the performance
of the scans that Norton Disk Doctor DOS conducts.
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 will report that a hard drive is
mis-configured if 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 create the drive partitions.
Check with the BIOS manufacturer to be 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://www.symantec.com/techsupp/.
You can force 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/.
Do not run Norton Utilities 2001 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 will produce an error message.
When restarting Windows after an improper shutdown, 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 Windows 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 Norton Disk Doctor 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 Norton Disk Doctor continues loading. Then
select the drive to diagnose the problem.
Norton Disk Doctor 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
compressed volume file, you may get a blue screen error message. Norton
Disk Doctor does not generate this message. Please contact Microsoft for
assistance.
Norton Disk Doctor 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 cartridges from the drive
when not in use to minimize disk damage.
Norton Disk Doctor should only be used to fix an invalid
partition if it is completely inaccessible from Windows or DOS. Prior to
any kind of partition repair operation, you should update your Rescue Disk
set.
Norton Disk Doctor will not create an Undo disk in
Windows NT/2000 when the "Automatically fix errors" checkbox is
checked.
Norton Disk Doctor can only revive FAT or FAT32
partitions under Windows NT/2000. It cannot revive NTFS partitions.
á
The language version of Windows NT or Windows 2000 and
the language version of Norton Utilities 2001 must be the same for Norton
Disk Doctor to post a summary clipboard screen after a drive has been
analyzed. If the languages do not match a dialog box will pop up reporting
that the disk check has completed and will not display a summary.
Norton Disk Doctor does not support reparse points on
Windows 2000. The drive containing the junction will be checked as normal,
but the reparse point will not be resolved and the destination checked.
To repair corrupted boot records use the DOS version of
Norton
Disk Doctor, not the Windows version. The Windows
version will
diagnose this problem, but will not repair the boot
record to
the degree that the DOS version can.
Norton Disk Doctor does not support floppy disks
compressed using DriveSpace 3 when they are used with Windows Millennium.
If you are experiencing problems running Norton Disk
Doctor in Safe Mode, please use the DOS components (available on the
bootable CD).
Return to top of page
|
|
Binary files can occasionally be viewed in the text
viewer. These files appear illegible.
The maximum size of a file is 32,767 lines.
Return to top of page á
|
Norton
Optimization Wizard
We recommend that you close all other programs before
running Norton 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.
WinIce users 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 is to rename NRW16.EXE (in the Norton Utilities directory)
to NRW16.NUL.
Norton Optimization Wizard 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"
If there is corruption or non-standard 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 (sub-keys of HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\
{B3943EF5-CEC5-11CF-AF20-00A0C9034837\). This key is split into two keys,
"Component" and "CLSID", but 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. (Windows Millennium users may wish to consider creating a
restore point with System Restore prior to running Optimization Wizard to
enable any operations to be undone if they are not satisfactory.)
Return to top of page á
|
|
IMPORTANT: Do not attempt to purge protected files while
utilities such as Speed Disk or Norton Disk Doctor are running.
To configure Norton Protection features, right-click the
Recycle Bin icon, then click Properties on the context menu.
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. Norton Protection will begin
removing files if the total of all files sizes it is protecting is greater
than the amount of actual free space on your drive. Norton Protected
Recycle Bin protects a maximum of 1500 files.
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 cause the Norton Protection shield status to be displayed
incorrectly. To correctly display the status, disable Norton Protection and
then re-enable it.
Internet Explorer's temporary files are excluded from
Norton
Protection by default. However, other browsers may use
different
folder names, or locate temporary files in user folders.
You may
wish to consider excluding these folders from protection
to
avoid protecting too many files that do not warrant
saving.
There may be times when you may need to disable Norton
Protection.
To do this on Windows 95/98/Millennium, run
NPROTECT.EXE /REMOVE.
On Windows NT/2000, run
NET STOP "NORTON UNERASE PROTECTION"
[include the quotes].
If you add a drive/partition under Windows NT 4 or
Windows 2000
the drive will not be protected until after a system
reboot. If
a reboot is not possible, issue the following command in
its
entirety from a Command Prompt window (CMD.EXE, not
COMMAND.COM):
NET STOP "NORTON UNERASE PROTECTION" & NET START "NORTON
UNERASE PROTECTION"
Include the quotation marks in this command.
If the service is changed to a Manual startup,
protection will not
be available at the next system start. To protect
drives, start the
service (NET START "NORTON UNERASE
PROTECTION") then go to Recycle Bin / Properties / Norton Protection,
and enable protection for each drive you wish to protect. It is recommended
that you do not change the service from its default startup type,
Automatic.
If you run SetiAtHome you may wish to add the .SAH
(SetiAtHome) extension to Norton ProtectionÆs Exclusion list to avoid
excessive numbers of Seti files from being protected needlessly.
Return to top of page á
|
|
To track files with long names (greater than 12
characters), track the files individually
instead of tracking the folder that contains them.
Changes to hidden or system files in a tracked folder will not cause 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.
Return to top of page á
|
|
Because functionality similar to Norton SpeedStart is built in to Windows
98, Norton SpeedStart is disabled in
Windows 98.
The very first time an application is loaded after
Norton SpeedStart is installed, it may load more slowly than usual because
Norton SpeedStart is profiling the loading process.
Immediately after
installing Norton Utilities 2001 and rebooting, Norton SpeedStart profiles many applications for the first time, so the
first boot may be noticeably slower than normal.
Norton SpeedStart uses this information
to speed up application startup.
Return to top of page
|
|
Norton System Doctor sensors (eg. drive space) do not
support reparse points on Windows 2000.
The Disk Health sensor is set to Monitor All Local Hard
Drives by default. The Disk Doctor, Disk Doctor (Surface Test), and Image
sensors can be set to Monitor All Local Hard Drives from the Drive tab of
the sensor Properties. 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 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 2001 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, if Norton System Doctor is docked
vertically, its width may be larger than necessary to accommodate the
current set of selected sensors. To fix this problem, close and re-launch
the program.
Norton System Doctor configuration files saved with
versions prior to 3.0 of Norton Utilities for Windows 9x are not compatible
with the 2001 version. Please set up a new System Doctor configuration with
Norton Utilities 2001.
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 provided in the SMARTDRV folder on the Norton Utilities 2001 CD. For
more information, see the SMARTDRV.TXT located there.
Upgrading to Windows 98 will remove the SMARTVSD.VXD
file from the WINDOWS/SYSTEM/IOSUBSYS directory if there is such a file
there. If you had operating SMART sensors prior to upgrading you will have
to re-install using SMARTDRV.EXE on the NU CD after the upgrade.
If you connect to an Internet Service Provider (ISP)
such as CompuServe 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 Disk
Space alarm is displayed, 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 display the alarm anyway because it
perceives it as new error condition.
After running a Norton Utilities 2001 program to correct
a problem indicated by a Norton System Doctor sensor, some stoplight sensor
faces might 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.
Return to top of page á
|
|
Program dependency errors cannot always
be repaired because programs can lose required files and require re-
installation. Norton WinDoctor's "Repair" button is grayed 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.
WinDoctor can create a log file of all the changes made
to the system. Pressing CTRL-ALT-S will open a Save dialog and allow you to
save the log to a text file.
Norton WinDoctor will not diagnose broken links to a
hard drive that have been removed from your computer. Turning off the
"removable drive" analysis agent enables Norton WinDoctor to show
these errors.
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.
If Norton WinDoctor starts up, but does not have any
tests in its list, you may have an installation error. To repair the
installation error, reinstall Norton Utilities, or select Run from the
Start Menu and browse to the Norton Utilities 2001 folder and type:
á SIREGIST.EXE
"C:\Program Files\Norton Utilities\siregist.txt"á
If you do not have a temp directory, you will get the
message, "An error (4) occurred while examining your registry."
You can fix this error by opening a MS-DOS prompt from Start Menu /
Programs and typing MD TEMP.
Upon trying to retrieve a file from Norton Protected
Recycle bin or the Windows Recycle bin using the Repair button of
WinDoctor, you may at times get a message that the repair failed. This may
be in part due to disk activity. We recommend you shut all running
applications and then hit Repair button again.
Return to top of page á
|
|
Norton WipeInfo will not wipe the slack space for the
Windows Swap file (win386.swp).
Norton WipeInfo will not wipe the slack space or remove
the directory entry for files located on Network and Shared drives.
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, use
the Wipe Free Space option in WipeInfo.
If Wipe Free Space repeatedly restarts, open My Computer
and right click on the drive you want to wipe and select Wipe Free Space.
This will run WipeInfo without the user interface. Network and Internet
connections can cause writes to the disk. Disconnect from your network and
run Wipe Free Space again.
Windows Me System Restore can restore files that have
been wiped if they are one of the protected file types. By default, many
document types, such as .DOC and .XLS files in My Documents are protected.
Windows Me System Restore maintains a copy of protected files. Wiping the
original file does not wipe the copy that Windows Me System Restore
maintains.
Return to top of page á
|
|
Please refer to the file README.TXT in the Rescue
directory.
Return to top of page á
|
|
WinDoctor in Norton Utilities 2001 is significantly different
from WinDoctor in Norton Utilities 4.0/4.5. If you use WinDoctor from the
Norton Utilities 2001 CD you will disable WinDoctor from running from the
Norton Utilities 4.0/4.5 CD. WinDoctor will still work fine if it is
already installed on the computer.
If the Registry Integrity Scanner shows
"ERROR" when WinDoctor is run from CD, look for a file called
WINDOC.DAT on your system and delete it. This will resolve the error.
Return to top of page á
|
|
Speed Disk (Windows 95/98/Millennium only)
NOTE:
Please refer to the file READMESD.TXT
regarding Speed Disk for NT/2000.
We strongly recommend that you shut down any CPU
intensive applications prior to running Speed Disk. For example, the SETI@Home
Screen Saver and Background versions can assume up to 97% of CPU activity.
This can have adverse effects on Speed Disk. To check for programs
currently running, press Ctrl-Alt-Del ONCE. End task on all items except
for Explorer before running Speed Disk.
On Drives with more than 6000 folders or folders with
more that 2000 large (>5mb) files, the initial scan will run very slowly
and may even appear to stop. You should always allow the scan to complete.
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.
If Speed Disk reports that a hard drive is configured
incorrectly and the drive fails the configuration check, the 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://www.symantec.com/techsupp/.
You can force 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: Set this value ONLY if
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/.
With the huge increase in the size of hard drives, there
is no longer a need to compress drives. Please note that Speed Disk no
longer supports compressed drives.
If Speed Disk is launched 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 launch Speed
Disk.
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 in the registry to prevent Speed Disk from
moving BestCrypt system files. Launch Norton Registry Editor and create a
new key under "HKEY_LOCAL_MACHINE\Software\Symantec\Speed Disk
Unmovable Files" called "*.jbc" with the value to
"*.jbc".
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 the value for Minimum Virtual Memory is set to zero,
the Swap File will not be moved to the front of drive even if the Speed
Disk options is set to move it. You can also run Optimization Wizard and it
will optimize your Swap File settings.
Some users may have partitions overlapping (which is an
error that should be rectified using Norton Disk Doctor). When Speed Disk
optimizes such partitions it may overwrite data belonging to the other
partition. Currently Speed Disk does not check for this Partition error,
however Norton Disk Doctor does. We recommend running Norton Disk Doctor on
your drives before using Speed Disk.
Speed Disk does not support being run from a rescue set.
Please use the
rescue set to restore your system before running Speed
Disk.
Speed Disk may keep restarting during an optimization if it is
running out of memory. This is because it is having to resize the swap file
in order to be able to store information about the data it is processing.
If this is occurring, define a fixed swap file size. To do this select
Start / Settings / Control Panel / System / Performance / Virtual Memory.
Select "Let me specify my own virtual memory settings". In the
Minimum field enter the amount of RAM your system has, eg 128 for 128MB of
RAM. In the Maximum field enter at least double this amount, eg 256. Press
OK / Yes / Close and decide if you wish to reboot the system at that time.
In the unlikely event that Speed Disk continues to restart when optimizing,
despite having no other applications running, or no items in the System
Tray, it may be necessary to increase the swap file Maximum amount further.
Return to top of page á
|
|
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 not be able 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 swap file
- 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.
On CD-ROM drives, the Physical Benchmark option for
drive benchmarking is disabled. To obtain similar results, manually set the
supplemental cache size to small in Windows System Properties, and the
access pattern to no read ahead for that drive, then run the logical
benchmark.
If you are using the Promise DC4030-VL2 EIDE disk controller,
and run the drive benchmark, the computer 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
active applications, disk swapping, most hardware interrupts, 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.
Volumes mounted as reparse points are not treated as
part of the file system on which they have a junction. They are treated as
separate volumes.
The Details button on the Network tab is
unavailable on Windows NT/2000 due to it's security features. This is
inconsistent with System Information running on Windows 9x/Millennium,
which does not have these security features.
LS-120 drives are not currently
supported.
Return to top of page á
|
|
On Windows NT/2000, UnErase Wizard does not have the raw
UnErase functionality of its 9x/Millennium counterpart. This means if files
are deleted which are not intercepted by the Recycle Bin or Norton
Protection (either because the file is in the Exclusion List or Norton
Protection is disabled) they will not be recoverable when running on
Windows NT/2000. If the volume is not NTFS, then you can boot into Windows
9x/Millennium (if you are using Dual Boot) or DOS and use that version of
Unerase, which will recover the file.
The Recently Deleted Files list shows the 25 most-
recently deleted files that are recoverable. If some of the files have been
overwritten, you will see fewer than 25 files in the list.
If you delete a file on a floppy disk from an MS-DOS
prompt, by specifying filename letters after a wildcard (e.g. DEL
*ILENAME.TXT as opposed to DEL FILENAME.TXT or DEL *.TXT), then the file
will be listed as Unrecoverable on the 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, refer to the note
under "General Points of Interest" earlier in this document.
When using Windows Millennium, system files will not be
recoverable with UnErase Wizard. Such files are restored by the System
Restore feature which is part of Windows Millennium.
The UnErase Wizard will track every application that is
launched under Windows 2000 and list it as an unerasable entry. Under NT
5.0, the program applications shortcuts are stored under the folder
"x:\Documents and Settings", where X: is the system drive
(usually C:). Within the user sub-folder is a Start Menu sub-folder. To
avoid having launched applications listed in the UnErase Wizard, set the
exclusion list to exclude the appropriate subfolders under "x:\Documents
and Settings". Reboot the machine for the settings to take effect.
Manually exclude any files you do not want included. Under NT 4.0 the Start
menu items are excluded by default.
Return to top of page á
|
|
Long file names are not recoverable on floppy disks.
UnFormat does not work on compressed hard drives. 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.
Due to the dynamics of FAT32 file systems, UnFormat
may not always detect when the cluster size has
been changed.
Return to top of page á
|
The online documentation for System Doctor incorrectly states
that
there is a sensor to monitor Norton Protected Files on Windows
NT
and Windows 2000. This monitor is available only on Windows
95, 98
and Millennium.
|
|
