PartitionMagic by PowerQuest
Version 1.04 for OS/2
Copyright (c) 1994-1995, PowerQuest Corporation
All Rights Reserved. Patent Pending.

This file explains changes made since the printing of the manual.

TABLE OF CONTENTS
-----------------
I.    License Types
II.   Changing Your Boot Partition
III.  OS/2 Bugs
IV.   Warnings
V.    Drives >1024 Cylinders
VI.   Text Mode PQMAGICT.EXE
VII.  Code Pages
VIII. Error Messages
IX.   New Address

I. License Types
----------------

The Personal License allows you to install PartitionMagic on up to two
specific PCs to organize your hard drive(s) precisely the way you want.  In
addition to the Personal License, PowerQuest offers a Professional License for
use on an unlimited number of PCs, one at a time. A Corporate Site License is
also available for remotely configuring multiple machines simultaneously
throughout your enterprise. (Call PowerQuest corporate sales for more
information.)

II. Changing Your Boot Partition
--------------------------------

If you want to modify your OS/2 boot partition, you must boot from an
alternate source.  If you have multiple boot partitions, boot from a partition
other than the partition you want to modify.  If your hard drive contains less
than 1024 cylinders, you can start and operate PartitionMagic from DOS.  See
p. 19 in the *User Guide*.

You can also use PartitionMagic from OS/2 Maintenance Mode.  See p. 19 in the
*User Guide*.

If you have Version 1.0 of the manual, make this change to step 3:  When
booting Warp, press F3 instead of ESC to enter Maintenance Mode.

Also, see the material later in this file for information about drives
containing more than 1024 cylinders, and Text Mode (PQMAGICT.EXE).

III. OS/2 Bugs
--------------

We have found two serious OS/2 hardware bugs that can cause corruption of your
hard drive if you use PartitionMagic without first upgrading your OS/2
software.  One effects PS/2 Model 77 computers and possibly other computers
using a Future Domain SCSI controller.  The other effects Pentium PCI
computers.

Model 77
--------

The first bug occurs on PS/2 Model 77 computers and possibly other computers
using a Future Domain SCSI controller.  Make certain that you have the latest
flash BIOS and the latest SCSI driver or you may experience loss of data or
corruption of your hard drive.  IBM has released a new Future Domain SCSI
driver that fixes bugs in the drivers shipped with Warp FullPack and Warp
FixPak WFP_05.  The new driver can be found in FDWPGA.ZIP, available in the
standard places (CIS:OS2SUPPORT, FTP:software.watson.ibm.com/pub/os2/os2fixes,
OS/2 BBS).

Model 77 owners should also make certain they have v3.03 (Rev 5) or later of
the flash BIOS.  Rev 5 was released in April 95 and is available on the IBM PC
Co. BBS (919-517-0001) in the Reference Disk Section.  From the main menu,
select "REF DISK" to read and accept the license terms.  Search for "flash" in
the Reference Disk file area (currently #27).  The filename is currently
7677flsh.dsk.

Pentium PCI
-----------

We think the second serious hardware bug, a sporadic data loss bug, is
restricted to certain Pentium, PCI computers.  But we don't know for sure.  If
you have experienced unexplained problems with OS/2, try checking for this
bug.  If you have a Pentium computer with a PCI bus, please do NOT use
PartitionMagic until you have tested for this bug.  (This bug is not fixed in
Warp FixPak 5.  Tests with Warp Connect show that it has the problem as well.)

Use DMATEST to test a computer for the Pentium PCI DMA bug.  READ THE
INSTRUCTIONS FOR DMATEST BEFORE USING IT!  If the instructions are not
followed carefully, the test itself could trigger the bug which could destroy
data in any or all of your files on any of your drives!  The instructions for
proper use of DMATEST are found in the file, DMATEST.TXT.

On computers with an AMI BIOS, a work-around is possible.  In the BIOS setup,
Advanced, Advanced Chipset, PCI IDE Prefetch Buffers should be set to
Disabled.  The computer is then safe for use with PartitionMagic and your
other programs.

IV. Warnings
------------

- Don't forget to backup your hard drive before using PartitionMagic.  While
PartitionMagic has been thoroughly tested and is quite safe, power failure,
operating system bugs, and hardware design bugs can put your data at risk.  No
software program, including PartitionMagic, is perfect.  Before using any
utility that makes such extensive changes to your hard drive, you should
backup your data.

- Do not use the DOS executable of PartitionMagic under Multitasking software
such as Windows or DesqVIEW.  It is best to turn off disk caching software
when using the DOS executable.  When running PartitionMagic (DOS executable)
under Windows 95, please use MS-DOS Mode to prevent multitasking.

- Before using PartitionMagic, you should deactivate or unload from memory any
TSR (terminate and stay resident) programs that access or modify the
partitions being changed.  For example, a TSR that downloads files in the
background, accesses and modifies one or more disk partitions.

- It is normal to get an error starting Windows 3.1 stating the swap file is
corrupt.  Windows 3.1 is designed knowing that disk utilities may move the
clusters of the swap file.  When a move is detected, the error message is
given.  To fix the swap file, delete the swap file and create it again.  Click
on the 386 Enhanced icon in Control Panel, then on the Virtual Memory button.

- The PartitionMagic DOS executable (PQMAGICD.EXE) uses the same DOS extender
as DOOM.  If DOOM will not run on your computer, chances are that PQMAGICD.EXE
will not run either.

- Sometimes using PartitionMagic confuses Windows NT in that Windows NT
changes drive letter assignments.  Use Disk Administrator to change the drive
letters back to the values you prefer.

V. Drives >1024 Cylinders
-------------------------

If any partitions go past cylinder 1023, you will get error 109, "Partition
ends after end of disk" when running PartitionMagic from DOS or sometimes from
Maintenance Mode.  If at all possible, use the Presentation Manager executable
(PQMAGIC.EXE) to modify the drive.

Usually in OS/2 Maintenance Mode OS/2 can access the entire drive.  However,
if the default driver set loaded for maintenance mode does not include the
drivers necessary for your drive, you will not be able to access the entire
drive until you modify the CONFIG.SYS used to boot maintenance mode.  Change
the CONFIG.SYS used to start Maintenance Mode to include the same hard disk
drivers used by the full OS/2 boot.

VI. Text Mode PQMAGICT.EXE
--------------------------

To access physical drives beyond the first four, use the Text Mode executable,
PQMAGICT.EXE.

We have found that after booting from the OS/2 installation diskettes, there
is very little memory left in a 4 MByte computer.  After PartitionMagic is
loaded into memory, about 300 KBytes remain.  In many instances, this is not
enough for PartitionMagic to operate.  This simplest solution is to run the
DOS executable, PQMAGICD.EXE.  Another alternative is to free up some memory.
This can be done by copying the first two installation diskettes, identifying
unused device drivers, then deleting the lines that load those drivers in the
CONFIG.SYS file on the 2nd diskette.

When you run PartitionMagic in Maintenance Mode, depending on how you started
OS/2, you may get the error, "SYS1804:  The system can not find the file
VIOCALLS." To solve this problem, copy VIOCALLS.DLL and PQMAGICT.EXE to a
scratch floppy.  Then start PQMAGICT.EXE from the scratch floppy.

You should copy VIOCALLS.DLL from the disk or diskettes you used to boot OS/2.
It can be found in the following locations:

  Boot Source               VIOCALLS.DLL Location
  ----------------------    ---------------------
  Installation Diskettes    Install Disk 1
  Utility Diskettes         Utility Disk 2
  Hard Disk                 \OS2\DLL

VII. Code Pages
---------------

This release of PartitionMagic handles 7-bit ASCII filenames.  PartitionMagic
does not yet handle full 8-bit character sets such as Code Page 850 or double
byte character sets.  Converting a partition can produce incorrectly
translated filenames.

VIII. Error Messages
--------------------

This section explains error messages you may encounter while using
PartitionMagic.  Some of these messages have been added since the manual
printing.  Only the most common messages are explained here.  If you encounter
an error message that is not referenced in this section, contact PowerQuest.
See Appendix D:  Product Support.

Resolving Check Errors (Error Codes 1000-2999)
----------------------------------------------

Many errors can occur after selecting the Check option or when starting a
Move, Resize, or Convert operation before any changes are made to the
partition.  If PartitionMagic detects a problem with a partition, it refuses
to modify it since doing so may decrease the amount of the partition's
recoverable data.  If you receive an error message, exit PartitionMagic and
run the CHKDSK program (without /F) on the same partition to further diagnose
the problem.  (OS/2's CHKDSK should be used instead of DOS's in order to
detect problems in extended attributes.) If PartitionMagic's Check operation
shows a problem and CHKDSK does not, either PartitionMagic has detected an
error that CHKDSK ignores, or PartitionMagic has made a mistake.  Either way,
contact PowerQuest.  See Appendix D:  Product Support.

The DOS CHKDSK program usually detects the same errors as the PartitionMagic
Check option.  (If you don't have a backup of your disk, now would be a good
time to make one.) If both check programs detect an error, run CHKDSK /F on
the partition to fix the problem.  After running CHKDSK /F, try running CHKDSK
(without /F) to make sure the partition is fixed.  CHKDSK should pass twice
consecutively before proceeding.  Once CHKDSK is satisfied that the partition
is clean, run PartitionMagic's Check option.  If PartitionMagic still shows a
problem, CHKDSK /F may have introduced new errors.  At this point, reformat
the partition and restore your files from the backup copy.

PartitionMagic also performs a Check at the end of a Move or Resize.  If the
final Check fails, report the problem to PowerQuest.  See Appendix D:  Product
Support.  In this case, data loss is possible, but not typical.  The problem
is usually a minor file system error that can easily be corrected by CHKDSK
/F.  For more extensive errors, you may need to restore from a backup copy.

Resolving Partition Table Errors (Error Codes 100-199)
------------------------------------------------------

You can use the PARTINFO utility to print the contents of the partition
tables.  Remember that the actual geometry of the drive may differ from the
logical geometry assigned to the drive by the operating system.

Many times, partition table errors occur when DOS and OS/2 disagree about the
geometry of a drive.  Run the PARTINFO utility after booting from DOS and
again after booting OS/2 and compare the reported geometries.  The geometry
switch (/GEO) can sometimes be added to the BASEDEV statement in CONFIG.SYS
that loads the driver for the drive to force OS/2 to recognize the same
geometry used by DOS.  Other switches may be available for the device driver
that can resolve geometry or sector-mapping disagreements.

One user reports that running a virus check program detected and repaired a
partition table virus.  After the virus was removed, PartitionMagic no longer
reported a partition table error.

Sometimes drastic action must be taken to resolve a partition table error.
To create new error-free partition tables:  (1) backup the offending
partitions, (2) delete them, (3) recreate them, and (4) restore their
contents.  You may need to use the FDISK program from a recent DOS version.
(Older versions may refuse to delete HPFS or hidden partitions.) The OS/2
FDISK program may recognize the partition's corruption and refuse to modify
it.

Error Table
-----------

Error #3 - Not enough memory

The PartitionMagic box and User Guide explain the program's memory
requirements.  Quitting other applications can often free enough memory for
PartitionMagic to run.  See System Requirements in Chapter 1:  Introduction.

Error #8 - Could not allocate/deallocate DOS real mode memory

PartitionMagic DOS executables use a DOS extender to allow PartitionMagic (a
32-bit application) to run from DOS.  To read from and write to the disk,
PartitionMagic requires some memory in the first 1 MB of the computer's
address space.  If not enough memory is available, PartitionMagic cannot
access the disk.  Use the DOS MEM command to determine how much memory you
have available and what programs are using it.  If you press F6 while booting
DOS, you will be prompted as to whether or not you want to execute each
CONFIG.SYS and AUTOEXEC.BAT command.  By not running drivers or TSR programs
that use memory, you can force DOS to boot with more memory available.

Error #9 - Not enough memory to complete the operation.  No changes made.

PartitionMagic is extremely careful with your data.  At certain points in the
operation, checks are made to determine if it is safe to continue.  At one of
those checks, PartitionMagic detected that there was not enough memory to
complete the next set of changes.  Rather than risk losing data,
PartitionMagic has aborted the operation.  No data was lost and no apparent
changes were made.

This error usually occurs when you are running PartitionMagic for OS/2 after
booting from floppy on a 4 MB computer.  After PartitionMagic is loaded into
memory, about 300 KB remain.  The simplest solution is to run the DOS
executable.  Another alternative is to free up some memory which can be done
by copying the first two OS/2 installation diskettes, identifying unused
device drivers, then deleting the lines that load those drivers in the
CONFIG.SYS file on the second diskette.

Error #23 - Unsupported version of operating system

The PartitionMagic box and manual explain what version of the operating system
is required to run PartitionMagic.  For most operating systems, the VER
command can be used in a command window to ask the operating system what
version is running.

Error #26 - xxxxx.DAT not found

The DOS executables require a data file containing the user interface objects
to be located in the same directory as the executable.  PQMAGICD.EXE requires
PQDPM.DAT, and PQMAGIC.EXE (the DOS version) requires PQDWIN.DAT.  Other
executables require a data file for the Help information.  If you received
this message when pressing a Help button, the PQHELP.DAT file was not found.

Error #27 - Cannot lock drive

Under multitasking operating systems (such as OS/2 and Windows 95),
PartitionMagic must lock a partition before it can safely modify it.  If the
drive contains files that are in use by another process, PartitionMagic cannot
lock the drive.  Most running programs, including the operating system, have
open files.  The boot partition typically has many open files.  Files and
directories listed in CONFIG.SYS (and sometimes AUTOEXEC.BAT) are often open.
The virtual memory swap file is open.  For information about how to avoid this
error, see Changing Your Boot Partition in Chapter 2:  Concepts.

Error #36 - DPMI Server error

PartitionMagic DOS executables use a DOS extender to allow PartitionMagic (a
32-bit application) to run from DOS.  This error indicates that the DOS error
has failed during a call from PartitionMagic through the DOS extender to DOS
(or to the BIOS).  DOS extenders often conflict with extended memory users
loaded in CONFIG.SYS or AUTOEXEC.BAT.  If you press F6 while booting DOS, you
will be prompted as to whether or not you want to execute each CONFIG.SYS and
AUTOEXEC.BAT command.  By not running several of these commands, you can often
find a configuration that allows the DOS extender to run without error.

Error #37 - File or app is open on partition

See error #27.

Error #38 - Program is running from that partition

You have selected an operation that modifies the partition on which
PartitionMagic resides.  Copy PartitionMagic and any necessary .DAT files (see
error #26) to a different partition or to a floppy disk, then run
PartitionMagic from that partition or floppy disk.

Error #40 - A hard disk is present but can't be accessed
Error #41 - Can not write, disk is write protected
Error #42 - Disk changed since last operation
Error #43 - Unknown unit
Error #44 - Drive not ready
Error #45 - CRC error in data
Error #46 - Seek error
Error #47 - Unknown media type
Error #48 - Sector not found
Error #49 - Write fault
Error #50 - Read fault
Error #51 - General hard disk failure
Error #52 - DMA error
Error #53 - Lock violation
Error #54 - Network device fault
Error #55 - Specified drive is busy
Error #56 - Unexpected internal error

These errors indicate that I/O with your disk is not possible.  This often
indicates hardware problems with the disk.  When possible, PartitionMagic
detects such errors before any changes have been made so you can back up your
data before upgrading to a new disk.

Error #70 - Windows was detected

Because PartitionMagic makes low-level changes to the disk, it must have
exclusive access to the disk in order to keep your data safe.  Because Windows
is a multitasking operating system that does not provide PartitionMagic a way
to guarantee exclusive access to the disk, it is not safe to run
PartitionMagic under Windows.  In Program Manager, select File, choose Exit
Windows, then start PartitionMagic.

Error #71 - DesqVIEW was detected

Because PartitionMagic makes low-level changes to the disk, it must have
exclusive access to the disk in order to keep your data safe.  Exit DesqVIEW
before running PartitionMagic.

Error #72 - DOS Shell was detected

Because PartitionMagic makes low-level changes to the disk, it must have
exclusive access to the disk in order to keep your data safe.  Exit DOS Shell
before running PartitionMagic.

(Errors #100-199)

These are primarily Partition Table errors.  See Resolving Partition Table
Errors earlier in this appendix.

Error #100 - Partition table is bad

The hard drive partition table contains erroneous values.  The partition
tables in the Master Boot Record (MBR) and Extended Partition Boot Records
(EPBR) can each contain one partition of type 5.  This error occurs if a
single partition table contains two type 5 entries.  Since any modifications
PartitionMagic makes may decrease the amount of data that is recoverable from
the drive, PartitionMagic will not recognize any of the drive's partitions.

Error #104 - No sectors in partition

No partition should contain zero sectors.  Delete the partition before using
PartitionMagic.

Error #105 - Partition starts on wrong boundary

The hard drive partition table contains erroneous values.  PartitionMagic
expects FAT, HPFS, and NTFS partitions to begin and end on the boundaries used
by FDISK.  If they do not, the disk may be partially corrupt and any
modifications PartitionMagic makes may decrease the amount of data recoverable
from the drive.  Therefore, PartitionMagic refuses to recognize any of the
drive's partitions.

Error #106 - Partition doesn't start with sector one

See error #105.

Error #107 - Partition begins after end of disk

Sometimes this error occurs when running one executable (such as PQMAGICD) but
does not occur when others (such as PQMAGIC or PQMAGICT).

This is often the case for a drive using more than 1024 cylinders.  Under DOS,
PartitionMagic is restricted by the BIOS 1024 cylinder limit.  If any
partitions extend beyond the limit, PartitionMagic cannot safely operate on
the drive.  You must use the OS/2 executables (PQMAGIC.EXE or PQMAGICT.EXE) to
operate on the drive.  This error can also occur when you are booting OS/2
from a floppy diskette if the correct drivers for the drive are not present on
the diskette.

This error can also occur if a partition erroneously extends beyond the actual
end of the drive.  This may happen if the drive has been used on a different
computer or with a different hard drive controller.

This error can occur if DOS uses one or more cylinders beyond that expected by
OS/2. The geometry switch (/GEO) can sometimes be added to the BASEDEV
statement in CONFIG.SYS that loads the driver for the drive to force OS/2 to
recognize the entire drive.

Error #108 - Partition doesn't end at end of cylinder

See error #105.

Error #109 - Partition ends after end of disk

See error #107.

Error #110 - Partition table number of sectors is inconsistent

The hard drive partition table contains erroneous values.  The partition table
contains two size descriptions which do not agree.

This error can occur if DOS and OS/2 disagree as to the apparent geometry of
the drive.

This error is serious if the drive is used by both DOS and OS/2.  DOS uses one
of the size descriptions and OS/2 uses the other.  Data loss is likely once
the partition is almost full.

Error #111 - Logical partition starts outside Extended

The hard drive partition table contains erroneous values.  All logical
partitions must be totally contained within the extended partition.

Error #112 - Logical partition ends outside Extended

See error #111.

Error #113 - Partitions overlap

The hard drive partition table contains erroneous values.  If data partitions
overlap, writing to one may destroy data in another.

This error is often the result of an OS/2 FDISK bug.  If free space exists
within the extended partition (often as a result of using the DOS FDISK
program), OS/2's FDISK program allows a primary partition to be created that
overlaps the extended partition.  A logical drive is subsequently created in
the space occupied by the overlapping primary partition.

If a primary partition overlaps the end of the extended partition but does not
overlap any logical partitions within the extended partition the problem can
be remedied by patching the partition table.  Only qualified individuals
should attempt this repair!  An incorrect patch could destroy all data on the
drive!

Error #116 - Partition table Begin and Start inconsistent

The hard drive partition table contains erroneous values.  The partition table
contains two disagreeing descriptions of the starting sector of the partition.
This error can occur if the operating system reports a drive geometry that is
different than the geometry in use when the partition table was written.
Possible causes are:  (1) if different operating systems (e.g. DOS vs. OS/2)
report different geometries, (2) if booting from a floppy uses a different
driver than booting from a hard disk, (3) if upgrading the operating system
(e.g.  OS/2 2.x to OS/2 Warp) causes a different driver to be used, (4) if the
hard disk or controller is changed, (5) if the BIOS is upgraded, or (6) if the
BIOS LBA setting is changed.

Data loss is possible if the drive is written to using geometries that vary by
number of heads or sectors per track.  One user reported that scanning for and
removing a partition table virus eliminated this error from his drive.

Error #117 - Partition's drive letter can not be identified

Under OS/2, PartitionMagic must know the drive letter for each partition
before modifications can be made.  A driver on your system may change the
drive letters from their defaults; or your partitions may not have unique
serial numbers.

Error #118 - Two partitions have the same serial number

PartitionMagic may require all partitions on your system to have unique serial
numbers.  This is typically the case when a drive letter change has occurred
as a result of loading a driver for disk compression or driver letter
remapping.

If this error occurs under OS/2 and you have Stacker (which assigns duplicate
serial numbers), use the LABEL command to assign each stacked volume the
volume label STACVOL XXX where XXX is unique for each volume.  Do not assign
the host partition (the partition that contains the STACVOL*.* hidden file) a
volume label that starts with STACVOL.  Once each stacked volume is labeled,
PartitionMagic ignores duplicate serial numbers on the stacked volumes.  After
using PartitionMagic, you can change the volume labels to your preferences.

You may use the included SNUTIL utility to change the serial numbers of
physical FAT partitions.  SNUTIL cannot be used for HPFS partitions, network
volumes, compressed volumes, or other volumes that are not physical
partitions.

Error #119 - A drive has been formatted since starting PartitionMagic

When it is started, PartitionMagic reads information about each partition into
memory.  If you switch to another window and format a partition, you must exit
PartitionMagic and restart it to allow PartitionMagic to recognize the change.

Error #120 - The logical drive chain is incompatible

DOS, OS/2, Windows 95, and Windows NT require that logical partitions be
chained together in ascending order.  One or more of the logical drives are
chained together in the wrong order.  Other operating systems may not have
this requirement.  Linux fdisk chains logical drives together in the order
created.  This situation is very dangerous and can cause loss of one or more
partitions when using DOS's FDISK.

Error #121 - The first sector of the drive can not be read

The first sector of the drive contains the master boot record and the master
partition table. The drive cannot be used because this sector is not readable.

Errors #500 to #505 - (Various Check Disk Errors)

These are primarily Check errors.  See Resolving Check Errors earlier in this
appendix.

Error #505 - Path was invalid

Error #506 - Not enough free space on partition to shrink

A certain amount of free space (dependent on the drive's current contents) is
required to shrink the partition.  Try deleting unused or duplicate files in
the partition before attempting the operation again.

Error #508 - As specified, the operation does not change the partition

You have entered a value that is the same or (when rounded to the required
cylinder boundary) rounds to the same as the partition's present value.  Enter
a larger change.

Error #950 - Unable to detect any disk drives

No partitionable drives were found on your computer.  Floppy drives and
certain removable media drives do not support multiple partitions on one disk.
Such drives cannot be manipulated by PartitionMagic.

Error #951 - User entered an invalid value

The value entered is outside the range or (when rounded to the required
cylinder boundary) rounds to a value that is outside the range for the
operation specified.  Check the displayed range and reenter the value.

Error #952 - Value entered is the same as the current value

See error #508.

Error #953 - Need larger change

See error #508.

Error #954 - Partition is already of the type specified for convert

The command script file contains a command to convert a partition into the
same type as the partition's current file system.  You may have specified the
current, rather than the intended file system.  Or you may have specified the
wrong partition.

Error #955 - Invalid parameter entered.

Command line parameters must start with a forward slash, "/", or with a dash,
"-".

Error #956 - Unknown parameter entered.

One of the command line parameters is unknown.  You may have misspelled it, or
tried to use a parameter that is not supported with the executable you used.

Error #957 - Could not open log file.

An error occurred while opening the log file.  Make certain that you have
specified a legal name on a legal drive.

Error #958 - Could not open command script file.

An error occurred while opening the command script file.  Make certain that
you have specified a legal name on a legal drive.

Error #959 - No-Run-File specified was found, program will not run

This error alerts you to the fact that you did not intend any changes to take
place if the "No-Run-File" exists.  It does exist.

Error #960 - Partition label was not unique

You can not use the partition label specified to identify a partition because
two partitions have the same label, or no label.  Make all your volume labels
unique to avoid this error.  Remember that PartitionMagic can see the volume
labels of all partitions, regardless of the operating system's ability to see
them.

Error #961 - Partition label specified was not found

You may have mistyped the name of the partition.  Run PartitionMagic
interactively to quickly see the names of all your partitions.

Error #962 - Invalid line in script

The indicated line in the command script is not correct.  Consult the
documentation for the proper syntax.

Error #963 - Selected operation is currently invalid

The command script specified an operation that can not be done.  There may not
be room to move or resize the partition.  Or the value specified may not be
legal for the current file system.

Error #965 - Unable to select drive or partition with drive letter

The drive letter specified did not refer to any partition.  Run PartitionMagic
interactively to quickly see all the valid drive letters.

Error #966 - Could not open error file.

An error occurred while opening the error file.  Make certain that you have
specified a legal name on a legal drive.

Error #967 - Could perform operation to the value specified

There may not be room to move or resize the partition.  Or the value specified
may not be legal for the current file system.

Errors #1000 to #2999 - (Various Check Disk Errors)

These are primarily Check errors.  See Resolving Check Errors earlier in this
appendix.

IX. New Address
---------------
PowerQuest has moved. All phone and e-mail addresses remain the same.
The street address has changed to

1083 North State Street
Orem, UT  84057

CompuServe: 74601,354
Internet: magic@powerquest.com
WWW: http://www.powerquest.com

