                                                  April 23, 2002

Diskeeper[R] 7.0 (Build 410) for Windows[R] 95/98/Me, 
Windows NT[R] 4.0, Windows 2000 and Windows XP Professional. 

Note: This version of Diskeeper will also run stand-alone on a 
Windows XP Home Edition system.  However, Diskeeper cannot be
networked with a Windows XP Home Edition machine.  For more
information about using Diskeeper with Windows XP Home Edition, 
see section G, item 32.


TABLE OF CONTENTS
=================

A.  PRODUCT CERTIFICATION
B.  PLATFORMS AND OPERATING SYSTEM VERSIONS SUPPORTED
C.  OVERVIEW OF DISKEEPER 7.0
D.  MAJOR FEATURES IN VERSION 7.0
E.  OTHER KEY DISKEEPER FEATURES
	Frag Guard
	Set It and Forget It[R] Scheduling
	Exclusion List
	Selectable Run Priorities
	Event Logging
F.  CHANGES/CORRECTIONS IN THIS RELEASE
G.  KNOWN RESTRICTIONS IN THIS RELEASE
H.  KNOWN INCOMPATIBILITIES
I.  INSTALLING DISKEEPER 
J.  SETTING ACCESS CONTROL ON WINDOWS 95/98 SYSTEMS
K.  UNINSTALLING DISKEEPER 

-----------------------------------------------------------------


A.  PRODUCT CERTIFICATION
=========================

The Diskeeper 6.0 and Undelete 2.0 Server and Workstation
full versions for Windows are compliant with the Microsoft
Windows 2000 logo certification.   

At this time, Diskeeper 7.0 has received "Designed for Windows 
XP-Optimized" logo certification.


B.  PLATFORMS AND OPERATING SYSTEM VERSIONS SUPPORTED
=====================================================

This version of Diskeeper is supported on Intel x86 (or 
compatible) platforms running Windows 95, Windows 98, 
Windows Me, Windows NT 4.0, Windows 2000 and Windows XP.

Note that Diskeeper requires OSR 2 or higher on Windows 95 
systems.  


C.  OVERVIEW OF DISKEEPER 7.0
=============================

Diskeeper is the leading defragmenter in the Windows enterprise, 
and it continues to improve with each new version.  This version
is no exception -- we have made additional enhancements and 
changes as the result of feedback from customers worldwide.  
Support for Windows XP has been added, further demonstrating 
Diskeeper as "The Standard in Entire Network Defragmentation"[TM].  

Diskeeper 7.0 introduces a Remote Installation feature, which
makes installing Diskeeper on multiple networked computers fast
and simple.

This version of Diskeeper is compatible with Windows XP and will
defragment Windows XP cluster sizes of up to 64 kilobytes on NTFS
volumes.

Further enhancements have been made to Disk Volume Scheduling, 
Network Scheduling and Boot-Time Defragmentation Scheduling.

In addition to these enhancements, a Command Line Interface (CLI)
has been provided, which makes it easy to defragment disk volumes
from the command line.

Diskeeper relies on both the Distributed Component Object Model 
(DCOM) and the Microsoft Management Console (MMC).

In most cases, Windows 95 systems are not running either DCOM or 
the MMC by default.  On Windows 98 and Windows NT systems, DCOM 
is installed by default when the operating system is installed, 
but the MMC is an additional installation.  The Diskeeper setup 
process automatically installs DCOM and the MMC on your computer 
if it determines either are not already installed.  Windows 2000
has both DCOM and MMC included.  MSI files will also be installed
on pre-Windows 2000 systems that don't already have it. 


D.  MAJOR FEATURES IN VERSION 7.0
=================================

In addition to the core features present in the previous version
of Diskeeper, this version expands on the concept of "Set It and
Forget It" defragmentation.  

Remote Installation
-------------------

The Remote Installation feature provides a convenient way for
installing Diskeeper on multiple remote computers.  Here is how
it works:

Diskeeper can be installed simultaneously from a single machine to
multiple computers on a network, using the Remote Installation 
feature. The machines receiving the Diskeeper files must be 
running either Windows NT, Windows 2000, or Windows XP. Diskeeper
Remote Installation can save system administrators a tremendous 
amount of time and effort, especially on large networks, where the
same software may need to be installed on hundreds, or even 
thousands of computers.

To use the Remote Installation feature, you must have previously
installed the Diskeeper Server version and the Remote Installation 
program on a Windows NT/2000/XP computer that will act as the 
server on the network. You must also be logged into an
administrative account that has Administrator access to the 
intended remote installation machines. Note that on large networks 
the enumeration may take some time, as it gathers Diskeeper data
from the registry of each machine.


Faster Boot-Time Defragmentation
--------------------------------

Notable in Diskeeper version 7.0 is a the introduction of a 
much faster boot-time defragmenter, which also defragments
the MFT and other NTFS metadata.

Command Line Interface
----------------------

In addition to its Graphical User Interface (GUI), Diskeeper now 
supports commands from the command prompt. This provides an 
alternative method of defragmenting disk volumes. The single 
command supports several optional command qualifiers.

To use this command, follow these steps:

1. Open the command prompt window.

2. Type Diskeeper at the command prompt, followed by a drive 
   letter and any of the optional command parameters.

The Diskeeper command defragments the files of the selected 
volume.  Use the command in this form:

Diskeeper <volume> [/f] [/?]

Parameters:

<volume>  This is a required parameter that will accept any valid
          drive letter. A colon after the drive letter is not 
          required.

/f        Force. This option is accepted for compatibility with 
          Microsoft Disk Defragmenter (MDD), but is not used.

/?        Help. Displays the command prompt Help text.


E.  OTHER KEY DISKEEPER FEATURES
================================

The following features have been incorporated into previous
versions of Diskeeper.  All of these functions are available 
from the Action menu in the Diskeeper MMC Snap-In:


Smart Scheduling
----------------

The method used to determine how often Diskeeper should run is
elegant in its simplicity.  When Smart Scheduling is enabled,
Diskeeper keeps track of the number of files moved every
time it runs on each disk volume.  When the number of files
moved during a defragmentation run increases, Diskeeper
is automatically scheduled to run more often.  When the number 
of files moved decreases, the time between defragmentation runs 
is increased.

The Smart Scheduling option is available in both the Disk Volume
Scheduler and the Network Scheduler features.  It has been added 
to the "Run" drop-down option list.


Defragmentation Improvements
----------------------------

As Diskeeper has matured and grown, so has the engineering
knowledge and expertise that continually goes into improving
its efficiency.  Improvements have been made in the way
defragmentation is approached, and the result is better,
faster, and more efficient defragmentation of your disk 
volumes.

If you have used Diskeeper in the past, you will likely see
a marked improvement in how thoroughly your disk volumes are
defragmented and the speed at which the defragmentation is 
done.  These improvements are most noticeable on large 
volumes, but they affect all defragmentation jobs.


Frag Guard
----------

Frag Guard is available in the Windows NT and Windows 2000 
versions of Diskeeper only.  Frag Guard and the Diskeeper 
Boot-Time defragmentation function combine to address the 
defragmentation of two critical sections of an NTFS volume, 
the Master File Table (MFT) and the paging file, and keeps 
them that way.

Frag Guard has an online mechanism that minimizes MFT and paging 
file fragmentation, greatly reducing the need for boot-time 
defragmentation runs.  This mechanism also monitors the 
fragmentation levels of the MFT and paging file, and automatically 
sets a boot-time defragmentation operation to run when either of 
these levels exceeds a threshold that you set.  The boot-time 
defragmentation will only occur during a time period you specify.  

The dialog box that controls the Frag Guard settings is displayed 
during setup, but can also be accessed later from the Action menu.

Note that in order for Frag Guard to provide any benefit on most
volumes, it is necessary for you to run a full Boot-Time 
defragmentation of the volume.  This includes defragmenting the 
MFT and paging file, as well as defragmenting and consolidating 
the directories.  This manual Boot-Time defragmentation run 
"clears the way" to allow Frag Guard to function fully.


Set It and Forget It Scheduling
-------------------------------

The "Set It and Forget It" mode allows Diskeeper to run 
automatically in the background while users and other processes 
are active on the system.  To run Diskeeper in the "Set It and 
Forget It" mode, first create a schedule specifying the times 
Diskeeper either will or will not be allowed to run on a 
specific disk volume, then start the scheduled defragmentation 
job.  After a defragmentation schedule is created for a volume, 
Diskeeper will follow that schedule until you explicitly stop it.  
The defragmentation job will run as scheduled, whether you are 
logged onto the computer or not.  Also, multiple "Set It and 
Forget It" defragmentation jobs can be run at the same time on
separate volumes.  

By default, "Set It and Forget It" defragmentation jobs are run at 
"Lowest" Windows priority.  As an option, you can change the 
priority at which Diskeeper runs for "Set It and Forget It" jobs.  
To do this, select the Priority option from the Action menu.  Note
that raising the priority of Diskeeper jobs can impact the 
performance of other tasks on your system running at the same 
time, but will reduce the amount of time needed to defragment your
disk volumes.


Exclusion List
--------------

Choose the Exclusion List option from the Action menu to create an
Exclusion List.

In some cases, you may have files or directories of files you do
not want to defragment.  For example, you might not want to 
defragment temporary files that will soon be deleted.  Any files 
or directories can be excluded from Diskeeper processing by 
creating an exclusion list. 
 

Selectable Run Priorities
-------------------------

Use the Priority option on the Action menu to select the Windows 
priority at which Diskeeper defragmentation jobs run.  You can set 
the priority independently for both "Set It and Forget It" and 
"Manual Defragmentation" defragmentation jobs.  

By default, scheduled, "Set It and Forget It" defragmentation jobs 
run at the lowest Windows priority.  Also by default, "Manual 
Defragmentation" jobs run at the normal Windows priority.  The 
priority for either type of defragmentation job can be changed 
with the Priority option.

Running at the lowest priority minimizes the system performance 
impact when Diskeeper is defragmenting a disk volume.  However, 
defragmentation jobs running at the lowest priority can take 
substantially longer to complete than those running at higher 
priorities, since Diskeeper "backs off" for any process running 
at a higher priority (even screen savers).

For this reason, you may have occasions where you want to run 
Diskeeper at a higher priority.  In these instances, use the 
higher priority options.  Keep in mind, though, that your 
system performance may be impacted when Diskeeper is run at 
higher priorities.


Event Logging
-------------

Use the Event Logging option on the Action menu to enable and 
disable the recording of various Diskeeper events to a log file.

On Windows 95/98/Me, the Diskeeper log file is named 
DkEventLog.txt, and it is stored in the directory where 
Diskeeper is installed.  This text file can be viewed with 
Notepad, or your choice of text editor programs.

On Windows NT 4.0 and Windows 2000/XP, the Diskeeper information 
is logged in the Windows Application Event Log.  See the "After 
the Installation" section of the Diskeeper Help for information 
about setting up the Windows Application Event Log for optimum
logging operation.



F.  CHANGES/CORRECTIONS IN THIS RELEASE
=======================================

The following list summarizes the changes and corrections that
have been made to Diskeeper since version 6.0:


1.  Under Windows 2000 and Windows XP, NTFS directories are now 
    being moved online as intended.  As before, directories under 
    Windows 95/98 are moved online.  Note that under Windows NT, 
    directories cannot be moved online.  Also note that where
    directories can be moved online, they may also move from the 
    location they were moved during a directory consolidation.

2.  Use has been made of improvements in the Windows 2000 and 
    Windows XP NTFS interface, to make free space consolidation 
    more effective.

3.  The Diskeeper defragmentation algorithms have been further
    improved, especially those addressing partial defragmentation.
    You may find this improvement noticeable even if the volume
    has less than 20% free space.

4.  There are certain files that should not be moved under any 
    circumstances. These files may be system files or files 
    related to specific applications. Moving these specific files 
    can cause system or application failure. As a result, 
    Diskeeper uses an “internal” exclusion list to ensure these 
    files are always excluded from Diskeeper processing. This list 
    is fixed in memory and cannot be modified. These are the files 
    that are currently in the Diskeeper internal exclusion list:

      o bootsect.dos
      o hiberfil.sys
      o memory.dmp
      o boot.ini
      o NTDETECT.COM
      o NTLDR
      o NTOSKRNL.EXE
      o safeboot.fs
      o safeboot.csv
      o safeboot.rsv
      o pad.esi

    Note that these files are not displayed in the Diskeeper 
    user-defined exclusion list.
    
5.  Under Windows 2000 and Windows XP, the MFT reserved space
    can "wander".  Diskeeper's NTFS boot-time defragmenter 
    now enforces a clear space bracketing the MFT zone, so 
    the MFT defragmenter has a chance to work more efficiently.
 
    Note that under Windows 2000 and Windows XP, the MFT zone 
    position is dynamic and cannot be changed by Diskeeper.  It 
    can only be changed by the NTFS driver within the file system 
    itself.  

6.  In some cases where an NTFS volume is low on contiguous free 
    space, it appears that the boot-time defragmenter does not 
    fully consolidate the directories.  This is often remedied by 
    simply re-running the NTFS boot-time defragmenter.

7.  In Diskeeper version 6, the NTFS defragmentation engines were 
    reworked so they run much faster than they did in Diskeeper 
    5.0 and earlier versions on volumes having more than 
    25,000 files.  The speed difference may not be as noticeable 
    on volumes having fewer than 25,000 files.

    In Diseeper version 7, additional speedups were made.

8.  A tool tray icon now is displayed every time the Diskeeper
    defragmentation engine is running.

9.  A remote installation feature has been added, which makes 
    installing Diskeeper on multiple network computer faster
    and easier.

10. Disk volumes can now be defragmented from the command line.
    Enter diskeeper /? on the command line to view the available
    options.

11. On Windows XP systems, Diskeeper supports Microsoft's Volume 
    Shadow Copies.

12. On Windows XP systems, Diskeeper supports Boot Optimization.

13. In Diskeeper Build 403.2, the NTFS engine was fixed to prevent
    unnecessary occurrences of a popup declaring the MFT was 
    corrupt.

14. Diskeeper Build 407 added information in the Windows Event Log 
    and the post-anaylsis and post-defragmentation reports.  

    The following "tags" are now displayed in the Most Fragmented 
    Files listing, as well as the "Defragmentation Stop" and 
    "Moved Files" event log entries to show files that could not 
    be moved by Diskeeper:

        Tag: [Cannot Open]
        File System: NTFS and FAT
        Displayed After: Defragmentation Only
        Description: This file cannot be opened (and thus moved) 
                     by Diskeeper. This is often the result of 
                     the access controls (permissions) on the file 
                     being set to prevent Diskeeper from accessing 
                     it.  File permissions must allow SYSTEM to 
                     have full control of a file in order for 
                     Diskeeper to defragment it.

        Tag: [Excluded]
        File System: NTFS and FAT
        Displayed After: Defragmentation Only
        Description: This file is listed on one of the Diskeeper 
                     exclusion lists.  This can be either the 
                     user-specified exclusion list or the internal
                     exclusion list.

        Tag: [Partially Defragmented]
        File System: NTFS and FAT
        Displayed After: Defragmentation Only
        Description: This file has been partially defragmented. 
                     Its fragments have been reduced in number, 
                     but the file is not yet contiguous.

        Tag: [Excess Allocation]
        File System: NTFS Only
        Displayed After: Analysis and Defragmentation
        Description: The space allocated for this file exceeds 
                     the actual space used by the file. In some 
                     cases, the file data itself may be 
                     contiguous, but the unused free space 
                     allocated to the file is not.

15. In order for Diskeeper to have access to move files, both 
    SYSTEM and ADMINISTRATOR must have full control over a file 
    (or the directory folder it is in).  This version of Diskeeper 
    includes a batch file that sets the access permissions on a 
    disk volume to allow Diskeeper to run properly.  

    This batch file is called "setdkacls.bat", and it is located 
    in the directory folder where Diskeeper is installed.

    If you find you have made files inaccessible to Diskeeper, or 
    that you have some files inaccessible to Diskeeper, open a 
    command prompt window, change directory to the Diskeeper 
    installation directory, and type:
 
	setdkacls x: 

    where x: is the letter name of the disk volume on which you 
    want to change access permissions.

    This batch procedure will only work if the account you are 
    logged onto has been granted access to the file(s) you want
    to defragment.

16. Changes were made to enhance the information shown in the 
    Diskeeper GUI when Set It and Forget It scheduled 
    defragmentation jobs are running.

17. In build 410, the Diskeeper Analysis Report has been modified 
    to display more usable information.  The fields for "Total 
    Fragmentation %" and "Free Space Fragmentation %" have been
    replaced with "Volume Fragmentation %" and "Data 
    Fragmentation %".  These values are calculated as follows:

                                Fragmented bytes
       Volume Fragmentation % = ----------------
                                Total volume bytes


                                Fragmented bytes
         Data Fragmentation % = ----------------
                                Total file bytes

18. The number of excess fragments discussed in the post-analysis 
    and post-defragmentation summary screens now includes both 
    file and directory fragments.  In Diskeeper builds prior to 
    410, only file fragments were included in the figures shown.


G.  KNOWN RESTRICTIONS IN THIS RELEASE
======================================

1.  The Windows NT 4.0 version of Diskeeper will not defragment
    NTFS volumes formatted under Windows 2000, or that were 
    upgraded to NTFS 5 volumes.  The Windows 2000 version of 
    Diskeeper will defragment these volumes.  If you have a 
    dual-boot system with Windows NT and Windows 2000, you must
    defragment all your disk volumes from the Windows 2000 boot.

2.  Diskeeper needs access to the root directory on a volume to
    display the volume in the GUI.  Diskeeper runs under the 
    SYSTEM logon, so if an NTFS volume is not appearing in the 
    volume list, make sure that SYSTEM has FULL CONTROL on the 
    root directory of the volume.
 
3.  Diskeeper needs to be able to access a file to defragment it.
	
    a) If a file on an NTFS volume does not grant FULL CONTROL to
       the SYSTEM logon, Diskeeper will not be able to defragment 
       it.
 
    b) If a file on an NTFS volume is open for update with an 
       exclusive lock, Diskeeper will not be able to defragment
       it.  You will need to shut down the application that has
       a file open in this mode in order to defragment it.

4.  Under Windows NT 4, Diskeeper will not defragment FAT-32 
    volumes, as FAT-32 was not a file system supported by
    Microsoft under Windows NT 4.  Diskeeper will, however 
    defragment FAT-32 volumes when running on Windows 98, 
    Windows 2000 and Windows XP systems.

5.  Boot-Time operations on very large or very fragmented volumes
    may take longer to complete than expected.  We therefore 
    recommend you do a thorough online defragmentation of a volume
    before you perform a Boot-Time Defragmentation on it.  We also
    recommend doing the Boot-Time Defragmentation on only one 
    volume at a time.

6.  Changes have been made to the boot-time engine, which enable 
    the use of the ESC key to terminate the operation.  Note that
    this option is only available if your hardware supports it. If
    pressing the ESC key does not stop your boot-time engine, you
    can safely restart your computer by pressing its reset button.
    In that case, you should run CHKDSK after restarting the 
    system, to free up any unused clusters that may not yet have
    been released due to the abrupt shutdown.

7.  Connecting to remote computers with the server version of
    Diskeeper can take up to 1 minute, depending on your network
    connection and traffic.

8.  If User Profiles are enabled on Windows 95/98/Me systems,
    Diskeeper will only be available under the logon of the user
    who installed it.  If you are using multiple user profiles,
    you can install Diskeeper from within each profile to make it
    available to that profile.

9.  Although Diskeeper attempts to lock removable drives, some 
    may not be lockable, or may eject anyway if the eject button 
    is used.  Data corruption may occur if you eject a removable
    disk while defragmentation is occurring on that disk.

10. When multiple disk volumes are scheduled to be defragmented
    with the same starting time, defragmentation is started on
    the volumes one at a time, with one-minute intervals between
    each starting time.  This is by design.

11. The Boot-Time Defragmentation feature is only available in 
    the Windows NT/2000/XP versions of Diskeeper.  Under Windows 
    95/98/Me, directory consolidation is not necessary, since 
    directories are automatically defragmented by Diskeeper in its
    online mode.  Swap file defragmentation under Windows 95/98/Me
    is not supported in this version of Diskeeper.

12. If you are running Internet Explorer 4.0 and using Dial Up 
    Networking (DUN) with a modem, starting Diskeeper can cause 
    the DUN dialog box to be displayed.  To work around this, 
    disable connecting through a modem or install Internet 
    Explorer 5.0.  Internet Explorer 5.0 may show similar results
    if the "Always dial my default connection" option is set via 
    the Tools | Internet options | Connection tab set.

13. If you install other software that also loads the MMC, be 
    aware that the other product may install an older version of 
    the MMC.  If this occurs, Diskeeper may not operate correctly,
    and should be reinstalled.

14. FAT volumes larger than 2GB formatted on Windows NT cannot be
    defragmented under Windows 95/98/Me.  This is due to a 2GB FAT 
    volume limit on Windows 95/98/Me systems.

15. The free space figures displayed in the Diskeeper MMC snap-in 
    may not match those shown in the Diskeeper report view if
    you are running Norton Protect.

16. If you are defragmenting a remote computer with the Server 
    version of Diskeeper, shutting down the remote system can
    cause the MMC on the local machine to generate an application
    error.

17. When you use the server version of Diskeeper 7 to connect 
    to computers running versions of Diskeeper prior to 5.x, the 
    information normally shown in the Diskeeper snap-in (such as 
    capacity and free space figures) is displayed as zeros (0). 
    This is because the earlier versions do not collect this 
    information at the GUI level.

18. When you use the server version of Diskeeper 7 to connect 
    to computers running versions of Diskeeper prior to 5.x, the 
    progress bar at the bottom of the Diskeeper snap-in display 
    will proceed to 100% several times -- once each time an 
    individual "pass" completes on the pre-V5.0 computer.  

19. When the Notification option has been enabled in the Automatic
    Boot-Time section of the Frag Guard dialog box, the scheduled
    restart will not occur unless you are logged off the computer.

20. When a Diskeeper 7 server is connected to a workstation
    running Diskeeper 4.1, and the MMC is shut down and re-started
    on the server, the graphic display showing the remote machine
    is blank.

21. When the post-defragmentation summary report is displayed,
    scheduled "Set It and Forget It" defragmentation jobs are
    prevented from starting.  Close the summary report to allow
    the scheduled defragmentation to occur.

22. Diskeeper cannot defragment NTFS volumes with a cluster size 
    larger than 4KB in size on Windows NT 4 and Windows 2000.  
    This applies to both online and Boot-Time modes.  

    Under Windows XP, the online and boot-time NTFS 
    defragmentation engines support cluster sizes up to and 
    including 64 Kbytes.

23. On Windows NT and Windows 95, if you do not have Internet 
    Explorer 3.0 or higher installed, you will not be able to 
    access the Diskeeper Help system interactively from Diskeeper.
    However, you can still run the Diskeeper Help by clicking 
    Start | Programs | Executive Software | Diskeeper Help.

24. In rare cases, the Diskeeper installation will not be able 
    to uninstall a previous version of the Diskeeper service. 
    The error displayed is "Error stopping the Diskeeper 
    Service."  If you receive this error, use Control Panel, 
    Add/Remove Programs to uninstall the previous version of 
    Diskeeper.  This will enable you to resume the installation. 

25. The installation of this version will not automatically 
    uninstall foreign language installations of Diskeeper.  
    This must be done manually.  

26. On Windows 95/98/Me, pressing CTRL+ALT+DEL while the
    Diskeeper engine is running on the system drive, can cause 
    a "system busy" blue screen.  Pressing any key should return
    you to Windows. If CTRL+ALT+DEL is pressed twice, while any
    disk volume is being defragmented, this can prevent old file
    fragments that were moved from being freed up. To avoid this
    problem, press the space bar after the first CTRL+ALT+DEL to
    return to Windows, then stop any defragmentation before 
    shutting down your computer.

27. The Boot-Time defragmentation log file path name should not 
    contain any embedded spaces.  Instead, use the DOS 8.3 file 
    naming convention to specify the log file path name.

28. The Diskeeper Remote Installation feature only supports the 
    network type WNNC_NET_LANMAN, which is the standard Microsoft
    Windows Network type.

29. Windows XP Professional is by default set to "Use simple file
    sharing," which does not allow sharing of important system
    or program folders of the volume shared. To do a Diskeeper 
    Remote Installation to a Windows XP machine, from Windows 
    Explorer select Tools|Folder Options, then select the View 
    tab, scroll down in the Advanced settings window and clear 
    the "Use simple file sharing" checkbox.

30. Please note that if Diskeeper Server is installed on a machine
    that is the only computer within a domain and you run Remote
    Install, the domain will appear to be empty, because there is
    no computer to qualify for the Remote Installation.

31. When doing a remote install, the Diskeeper Remote Installation
    service checks if the Diskeeper GUI is currently displayed on 
    the remote machines.  If the GUI is displayed, Remote 
    Installation will not install to that machine.  We recommend 
    that you broadcast a message to users, prior to installation, 
    asking them to close Diskeeper.  This will help ensure that 
    the Diskeeper Remote Installation can proceed as planned.

32. Remote connections to Windows XP Home Edition systems are 
    limited in Diskeeper Server.  Windows XP Home Edition treats
    all remote users as a Guest account.  Since the Guest account
    does not include Administrative rights, remote users will not
    be able to run manual Diskeeper jobs, but remote network 
    scheduling to a  Windows XP Home Edition system is allowed 
    if configured properly.

    Configuration is as follows:

    a) The user must have the same username and password on the 
       Windows XP Home machine as on the system the user is 
       connecting from.

    b) Install Diskeeper in a directory on the Windows XP Home 
       machine to which the Guest account also has access. The 
       Guest account does not have access to the \Program Files 
       or the Windows system directory.

    c) Share the volume and directories on the path to the 
       Diskeeper install directory. 

33. Diskeeper now can operate as a single instance application in
    all terminal server environments, in the XP Fast User 
    Switching environment, and as a cluster administrator 
    application.  In addition, Diskeeper can now be started with
    the "run as" command.

34. On Windows NT 4.0 systems, the Diskeeper graphic analysis will 
    display fragmented files on NTFS volumes in green (instead of
    red) if the analysis is started within 20 seconds of opening
    the Diskeeper user interface.  Subsequent analyses will 
    display the fragmented files in the correct color.
 

H.  KNOWN INCOMPATIBILITIES
===========================

1.  Diskeeper will not run on disk volumes that are locked by 
    utilities such as Scandisk.

2.  We have noted occasional problems in defragmenting volumes 
    that have been configured or resized with Partition Magic.  
    If you are having problems defragmenting a volume, and it 
    has previously been configured or resized with Partition 
    Magic, it may be necessary to backup, reformat, and restore 
    the volume prior to running Diskeeper.

3.  When using an IOMEGA JAZ drive with the IOMEGA Quick.exe 
    application installed, you may receive the following blue 
    screen error message when you log on to the computer using 
    an administrative account: 

       Stop 0x0000000A (parameter,parameter,parameter,parameter)
       IRQL_NOT_LESS_OR_EQUAL. 

    The IOMEGA Quick.exe application is installed in the Startup 
    group to start automatically.  It sends invalid system calls 
    that are only allowed when logged on as an administrator. 
    When the Diskeeper Boot-Time operation is run, the Quick.exe 
    application is delayed in starting, thus causing the above 
    problem.

4.  The Hercules Terminator AGP 128/3D "GLH" 8MB also does not 
    appear to display the full Boot-Time dialog, and thus appears 
    to hang when the "Pause at End" option in the Diskeeper 
    Boot-Time option has been selected.

5.  On Windows XP systems, manual defragmentation of large files 
    (4 GB or larger) at the default priority may result in the 
    system responding poorly.  This is a situation with the 
    operating system, not Diskeeper.  If you find Diskeeper 
    frequently defragmenting large files and your system bogs 
    down, we recommend either adding these files to the exclusion
    list, or defragmenting them during "off hours" when there is 
    less interaction with the system.  This situation has not been
    seen with Windows 2000 or Windows NT 4 systems.  We are 
    working with Microsoft to resolve this situation.

6.  The keyboard functions in the Boot-time defragmenter do not 
    work on all combinations of hardware, HAL (hardware 
    abstraction layer), and operating systems.  We are working to
    provide keyboard access from the greatest combination of these
    elements, but if your system does not respond to the keyboard
    functions during a boot-time, please report the hardware 
    configuration and full operating system version to Executive 
    Software Technical Support (tech_support@executive.com).  
    Providing this information may help us narrow down why certain
    combinations of hardware and software cannot access the 
    keyboard functions in the boot-time defragmenters.


I.  INSTALLING DISKEEPER 
========================

Windows NT Note: If you have previously installed Diskeeper Lite 
on your computer, Executive Software recommends that you uninstall 
it before proceeding with the installation of Diskeeper.  If, 
however, you decide to leave Diskeeper Lite on your system, be 
aware that uninstalling Diskeeper Lite after the installation will 
remove certain Windows NT registry entries used by Diskeeper, 
and you will need to re-install Diskeeper.  Use the Add/Remove 
Programs applet in Control Panel to uninstall Diskeeper Lite.

Note: On Windows NT machines, you must have Service Pack 3 or 
higher installed.  Also, you must be logged into an account 
that is a member of the Administrators group.

Diskeeper is available either as a downloaded self-extracting 
compressed file, or on CD-ROM.  The following instructions
apply to both formats.

Follow these steps to install Diskeeper:

1.  If your Diskeeper package is a self-extracting compressed 
    file, download the package into a temporary directory.  If 
    your Diskeeper package is contained on a CD-ROM, insert it 
    into the appropriate drive on your computer.

2a. (Download version only) From Windows Explorer, double-click 
    the file you downloaded in the temporary directory.  When 
    started, Setup will ask you where you want the installation 
    files to be unpacked.  Either select the default or specify 
    the desired folder. 

2b. (CD-ROM Version Only) The Windows AutoPlay feature 
    automatically determines the computer platform you are using 
    and begins installing the correct version of Diskeeper.  If 
    you have disabled the AutoPlay feature, double-click SETUP.EXE 
    in the Diskeeper folder.

3.  If Internet Explorer 4.01 or higher is not installed on your 
    computer, the Diskeeper Setup program is stopped.  Another
    installation program is started and a package of necessary 
    components is installed on your computer.  Microsoft 
    Management Console (MMC), which is the interface for 
    Diskeeper, requires these components.  These components 
    are a small subset of Internet Explorer -- not the complete
    Internet Explorer product.  Installing these components will
    not affect your current web browser.  Note that you must
    restart your computer after installing the component pack
    before you can continue installing Diskeeper.

4.  If the MMC is not installed on your computer, the Diskeeper 
    Setup program is paused and the MMC Setup program is started 
    automatically.  After the MMC files are installed, the 
    Diskeeper Setup program resumes.

5.  On Windows 95/98/NT systems, the Setup program checks to 
    confirm DCOM is installed on your computer.  If it is not, the
    Diskeeper Setup program exits and the DCOM Setup program is 
    begun.  After a short period of copying files, the DCOM 
    installation is complete.

6.  Click Next when the welcome message appears.

7.  The installation procedure detects and removes any previously 
    installed Diskeeper software. 

    Note that if you are installing an update version of Diskeeper,
    this update installation will not save any previous settings.
    You will need to re-enter any exclusion lists, "Set It and 
    Forget It" schedules and Frag Guard settings. 

8.  As an option, you can change the destination location for the 
    Diskeeper files.  By default, Diskeeper is installed in one of 
    the following locations on your Windows system volume, 
    depending on the version installed:

  \Program Files\Executive Software\Diskeeper\DiskeeperServer
  \Program Files\Executive Software\Diskeeper\DiskeeperWorkstation

    To choose another disk volume or directory:

    a) Select the Custom option button and click Next.

    b) You can check if there is sufficient disk space for 
       Diskeeper on any of your local volumes by clicking on 
       Disk Usage.

    c) Click Change, make the desired changes to the destination 
       and click Next to accept the new destination.  If the 
       directory you specify does not exist, a new directory 
       will be created.
    
9.  After the Diskeeper files have been copied to your system, 
    you are presented with the opportunity to register Diskeeper 
    online.  You can also register Diskeeper at a later time via 
    the Executive Software Web site at www.diskeeper.com.

10. A reboot may be required on systems that do not have Internet
    Explorer 4 or above, DCOM or the MMC.  If this is the case, a
    dialog box will appear at the end of the installation, asking
    if you want to reboot now.

11. To run Diskeeper, click the Windows Start button and select 
    Programs, Executive Software Diskeeper.


J.  SETTING ACCESS CONTROL ON WINDOWS 95/98 SYSTEMS
===================================================

In some cases, the Diskeeper setup program will inform you
that it is necessary for you to change the access control 
settings on Windows 95/98 systems.  If such a message is 
displayed during the installation, follow these steps to
set the access control:

1.  From the Windows Control Panel, double-click "Network".

2.  Click the Access Control tab.

3.  Enable "User-level access control".

4.  Specify the correct domain, if necessary.


K.  UNINSTALLING DISKEEPER
==========================

Follow these steps to remove Diskeeper from your computer:

1.  From Control Panel, double click "Add/Remove Programs".

2.  Click the "Install/Uninstall" tab, or "Change or Remove 
    Programs" in Windows 2000 or higher.

3.  Highlight "DiskeeperServer" or “DiskeeperWorkstation,” 
    depending on the version installed.

4.  Click "Add/Remove", or "Remove" in Windows 2000 or higher.
    This removes the Diskeeper program files from your computer.

5.  When prompted, click "Yes" to remove the Roboex32.dll
    shared file, unless you know of other programs on your
    computer that also use this file.  If this is the case,
    click "No" instead.

6.  It may be necessary to manually delete the Diskeeper 
    installation directory after the uninstall process
    is complete.

Note: If the MMC and DCOM have been installed on your 
computer, they will not be removed when Diskeeper is 
uninstalled.



(c) Copyright 2001, 2002 Executive Software International, Inc.  
    All rights reserved.

Diskeeper, Executive Software, Frag Guard and "Set It and
Forget It" are registered trademarks owned by Executive 
Software International, Inc.

"The Standard in Entire Network Defragmentation"  and
"Smart scheduling" are trademarks owned by Executive Software 
International, Inc.

Microsoft, Windows, and Windows NT are registered 
trademarks owned by Microsoft Corporation.

All other trademarks are the property of their respective owners.
