|
|
|
 |
 |
 |
|
|
|
|
 |
|
 |
Hardware support:
Diskeeper
runs on the Intel® x86 platforms
(including compatible CPUs from
other manufacturers).
OS
Support:
Diskeeper 2008 EnterpriseServer:
-
Windows XP Media Center
-
Windows XP Professional
-
Windows XP Professional x64
-
Windows Server 2003 Web
-
Windows Server 2003 Standard
-
Windows Server 2003 Standard
x64
-
Windows Server 2003
Enterprise
-
Windows Server 2003
Datacenter Server
-
Windows Server 2003 w/
Server Appliance Kit
-
Windows 2000 Professional
-
Windows 2000 Server
-
Windows 2000 Advanced Server
-
Windows 2000 Datacenter
Server
-
Windows 2000 w/ Server
Appliance Kit
Functional limits:
Maximum supported volume size:
Unlimited
Disk subsystems supported:
|
| |
Primary Partitions
Extended Partitions
Logical Drives
Volume Sets
RAID Arrays (hardware and
software)
Mirrored Disks
Mounted Volumes (letter-less
drives)
|
Resource requirements
The disk space requirements for
Diskeeper depend on several
factors. On Windows Server 2003,
Windows XP and Windows 2000
systems, Diskeeper will need
about 11 MB. Allow about 10 MB
of extra free space for
temporary files during the
installation. If Internet
Explorer® is not present on your
computer, some other needed
files (hhupd.exe, 50comupd.exe,
and wintdist.exe) may be added.
Further, your system may require
a new or updated version of the
Microsoft Management Console (MMC),
which is less than 6 MB.
|
Additional software requirements
Diskeeper relies on the
Microsoft Management Console (MMC).
The MMC provides a single point
of control for system utilities
such as Diskeeper. The MMC is
used as a central location for a
variety of Microsoft and third
party administrative tools. The
MMC is included in Microsoft
Windows 2000 and newer operating
systems.
|
A note
about firewalls
As a normal part of its
operation, the Diskeeper Service
(DkService.exe) acts as a server
on your system. If you are
running a hardware or software
firewall, you may see messages
indicating Diskeeper Service is
trying to act as a server. These
messages are expected; you can
safely allow these events. This
functionality is designed to
allow for support for network
operations (e.g. Remote Control)
via Diskeeper Administrator.
|
|
You may also be notified that
Diskeeper is trying to access
the Internet. It is important to
note that Diskeeper does not
access the Internet (except when
you specifically use the Check
for Updates feature), but it
does use Windows mechanisms that
may trigger these alerts from
your firewall. Again, these
messages are expected and you
can safely allow the events. If
networkability or automatic
update checking is not required,
you can safely disable this. |
|
|
 |
|
 |
|
|
 |
|
|
|
|
|
|
|
