
Norton Utilities for Windows 95
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thank you for purchasing the Norton Utilities for Windows 95.
Norton Utilities is not compatible with Windows NT, Windows 3.x,
or WIN-OS2.  It will also fail to function under other Windows
emulators (SoftWindows etc).

Please review the contents of this readme.txt file prior to
installation of the Norton Utilities, particularly the
INSTALL, TUNEUP, and GENERAL sections.


TUNEUP
~~~~~~
If there is insufficient memory available to launch supplemental
applications (Norton Disk Doctor, NDiags, etc), it will not give any
indication that these utilities have been skipped.  Ensure that you
have at least two megabytes of free extended memory before running
Tuneup.  NDiags requires 512k of conventional memory.

During the Tuneup process, Norton Disk Doctor (NDD.EXE) may take a
long time to load.  Please be patient.


GENERAL
~~~~~~~
Windows 95 and 32-bit applications require large amounts of memory.
If your system has limited memory resources (such as a small amount of
hard drive space for the swap file), Norton Utilities and other
programs may exhibit abnormal behavior.  We recommend maintaining at
least 30 megabytes of free disk space that Windows may use for its
swap file.

Several of the Norton Utilities must lock the drive they are working
on.  If the drive is written to, the utility must restart processing.
This is normal operation under a multitasking operating environment,
and is particularly common when processing the drive containing the
Windows 95 swap file.

The DOS-based utilities (SPEEDISK.EXE, NDD.EXE, DISKEDIT.EXE,
RESCUE.EXE, SPACEWZD.EXE, UNERASE.EXE, UNFORMAT.EXE, TUNEUP.EXE) run
in protected mode, and require only a small amount of conventional
memory.  They should have a minimum of 2 megabytes of extended memory
free for proper operation. NDIAGS.EXE requires a minimum of 512k of
conventional memory for proper operation.

Utilities which are not Windows 95-aware may not function correctly if
they attempt to do low-level disk operations while the Norton
Utilities are working on your hard drive.

The DOS-based programs in the Norton Utilities may improperly report
an insufficient memory error on some computers with more than 32mb of
RAM.

If you are running the Norton Desktop for Windows, the following lines
should be removed from your system.ini:
device=c:\ndw\vfintd.386
device=c:\ndw\vnss.386

Norton Utilities cannot always function correctly when Windows 95 is
running in fail-safe mode.  Please restart Windows 95 in normal mode
before running the Norton Utilities.

Support for compressed drives (Doublespace/Drivespace, Stacker) has
been disabled in this version.

Running an older version of DOS (including use of the dual-boot
feature of Windows 95) may cause corruption of long file names.
Norton Disk Doctor will report and repair these errors.  To avoid such
problems, you can run such programs in "MS-DOS Mode" instead.

Hard disk drives with more than 1024 cylinders may cause some problems
with Norton Utilities if improperly partitioned.  These problems may
be overcome by using an Enhanced IDE (EIDE) or SCSI controller,
upgrading your system BIOS, or through the use of third-party disk
partitioning software.


INSTALL
~~~~~~~
During the creation of Rescue Disks during the install, Rescue will
indicate that it only needs one diskette, but may sometimes ask for a
second diskette part way through the process.

Norton Utilities should not be installed into a directory with a path
longer than 40 characters.  The DOS-based applications may not run in
a directory with such a long path.

We recommend that you disable your Windows 95 sound settings prior to
the installation of Norton Utilities, as sound drivers can sometimes
cause an Invalid Page Fault error in MMTASK at the conclusion of
installaton.  Sound settings may be re-enabled following installation.

During the installation of Norton Utilities, the install program will
search for older versions of some Norton Utility and Norton Desktop
programs in your path.  These utilities will be renamed with an .OLD
extension to avoid confusion with the new Windows 95 aware versions.
These utilities should not be run on a system where Windows 95 is
installed.


NORTON PROTECTED RECYCLE BIN
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Removable drives (including floppies) will not be protected if they
are not online when Windows 95 is started up.

If you installed Norton Utilities on a removable storage device,
network resource, or other device which is not present during the
Windows 95 startup, you will need to copy SMARTCAN.VXD to your Windows
95 directory.


NDIAGS
~~~~~~
The comprehensive memory test has been disabled for this version of
Norton Utilities.

NDiags requires a minimum of 512k of conventional memory to operate.


NORTON DISK DOCTOR
~~~~~~~~~~~~~~~~~~
Norton Disk Doctor (both Windows and DOS versions) may take an
extended amount of time to analyze removable drives (including optical
drives, Syquest and Bernoulli cartridges).

Norton Disk Doctor does not test boot records on Bernoulli or similar
removable drives.

Norton Disk Doctor may need to run twice on disks which have corrupted
long file names.

When you run the DOS version of Norton Disk Doctor (NDD.EXE) on a
machine with an invalid boot record, an "invalid media type" error
will be reported. Select [Ignore] when this error is displayed, and
Norton Disk Doctor will proceed to diagnose and repair the disk.

If Norton Disk Doctor is performing a surface scan and reports "Drive
Not Ready", restart the surface test and select "Thorough Test" to
correct the problem.

Norton Disk Doctor may take an extended length of time to load from
floppy, please be patient.


NORTON SYSTEM DOCTOR
~~~~~~~~~~~~~~~~~~~~
System Doctor may report your CPU usage differently from Microsoft's
SYSMON utility.  System Doctor calculates CPU usage differently.  If
you attempt to run the System Doctor and Sysmon simultaneously, System
Doctor will report 100% CPU utilization because SYSMON uses all idle
processor time while displaying its processor usage monitor.


RESCUE
~~~~~~
Rescue cannot save information to the root directory of any hard
drive.  It can save rescue information to the root directory of a
floppy disk, or a subdirectory of a hard disk or network drive.


SPEEDISK
~~~~~~~~
Speedisk may sometimes report an "Error reading SD.INI" on ESDI or
SCSI hard drives.  Pressing [Enter] will allow you to run the utility
without problems.

Speedisk may sometimes run Norton Disk Doctor when it encounters a
memory error.  Norton Disk Doctor will not find any errors on your
disk, as it was not a disk error that Speedisk encountered.


SYSTEM INFORMATION
~~~~~~~~~~~~~~~~~~
System information will report your system's bus type as ISA,
regardless of whether you have PCI or VESA Local Bus slots in your
computer or not.

When selecting information on networked resources, System Information
may take an extended amount of time to gather all of its information
on large networks.

When System Information reports the amount of space used by files on a
network, CD-ROM, or compressed drive, it does not count "slack" space
(wasted space because of the device's cluster size), so the total
amount allocated will often be more than the size displayed by System
Information.

The Windows Memory Usage displayed on the memory tab may indicate more
memory used than is actually allocated.


UNERASE
~~~~~~~
The "Recently Deleted" file list in the Unerase Wizard lists all files
which are completely recoverable among the last 25 most recent
deletions.  If some of the files have been overwritten, you may not
see a full 25 files listed.


UNFORMAT
~~~~~~~~
Long file name information will not be recovered on floppy disks in
some cases.

Unformat will not function correctly if run on an unformatted 2.88mb
floppy.


THE SYSTEM INFORMATION 32-BIT BENCHMARK
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    The new SI-32 Benchmark is a true 32-bit benchmark designed to
    provide a single metric that lets you compare the performance of
    your system to the performance of other systems.

    The SI-32 Benchmark simulates the typical workload of common
    32-bit Windows applications running on your system.

    Describing how the SI-32 benchmark metric is determined is beyond
    the scope of this document, but the following information may be
    helpful in understanding some of the hardware considerations that
    come into play.


    What Does The SI-32 Benchmark Gauge?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    The SI-32 Benchmark is a gauge of your system's performance
    taking into account your CPU, RAM, System BUS, Memory Cache, and
    other system resources.


        Central Processing Unit (CPU)
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        The type and clock speed of your CPU is an important part of
        your system's overall performance.  In general, faster CPU
        speeds and more advanced CPU designs produce faster system
        performance.

        Random Access Memory (RAM)
        ~~~~~~~~~~~~~~~~~~~~~~~~~~
        The amount, speed, number of wait states, and configuration
        of your system's RAM will affect performance.  Windows 95 and
        32-bit applications utilize large amounts of RAM.
        Additionally, the more RAM you have, the less Windows 95 will
        need to swap to disk.

        System Bus
        ~~~~~~~~~~
        The type of system bus (ISA, EISA, PCI, VLB, or MCA) will
        affect your system's performance when transferring data
        between your CPU and RAM.

        Bus speed also will affect communication with peripherals
        (Video, Hard disks, etc.), however this communication does
        not affect the SI-32 Benchmark.

        Memory Cache
        ~~~~~~~~~~~~
        A memory cache consists of special high speed memory which is
        much faster than your system's RAM.

        Some processors have an internal cache (486, Pentium) known
        as the Level 1, (L1) cache.  In addition, most motherboards
        are configured with an external cache known as the Level 2
        (L2) cache.

        The size and architecture of the L1 and L2 cache will have a
        considerable impact on your system's performance.

        Sometimes, CMOS settings can be used to enable/disable the L1
        and/or L2 cache. If the CPU seems slower than it should be,
        verify the cache settings.


    What Doesn't The SI-32 Benchmark Gauge?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    The emphasis of the SI-32 benchmark is on measuring the speed
    that 32-bit applications run on your system (CPU, RAM, System
    Bus, Memory Cache).  Therefore, the benchmark does not take into
    account such factors as disk drives, video display, network, or
    other peripherals connected to your computer.

    For example, the benchmark does not take into account the time it
    takes to load an application because speed of loading an
    application is largely dependent on the speed of your hard disk.


    Why Do I Get Varied Results On The Same Machine?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Some variation of the SI-32 Benchmark result is normal.  The
    SI-32 benchmark is designed to exclude common outside factors
    such as most hardware interrupts, other running applications,
    disk swapping and etc., however some low-level system events can
    not be completely factored out.  These sometimes may cause minor
    discrepancies between consecutive runs.


    Why Does My Computer's SI-32 Benchmark Vary From Another
    Computer Of The Same Type?
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    Although your computer may be the same CPU and MHz speed as
    another computer it does not mean that it will get the same
    results from the SI-32 Benchmark.

    The various other factors, such as amount and speed of RAM,
    System Bus, amount and architecture of Memory Cache will affect
    the speed of your computer and the SI-32 Benchmark.

    See the section "What does the SI-32 Benchmark Gauge?" for a
    detailed list of these factors.


