README.TXT for PartitionMagic

PartitionMagic by PowerQuest
Version 1.0 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.   Legal Notices
II.  Changing Your Boot Partition
III. Boot Manager
IV.  Warnings
V.   Drives >1024 Cylinders
VI.  Text Mode PQMAGICT.EXE
VII. Code Pages

I. Legal Notices
----------------
The entire risk of the use or the result of the use of this sofware and
documentation remains with the user. No part of this document may be
reproduced or transmitted in any form or by any means, electronic or
mechanical, for any purpose, except as expressed in the Software License
Agreement.

Copyright (c) 1994-1995, PowerQuest Corporation. All rights reserved. This
software and documentation are copyrighted. All other rights, including
ownership of the software, are reserved to PowerQuest Corporation. This
software is protected by one or more pending patents.

PartitionMagic, PowerQuest, the PowerQuest Mark, Partition Map, and Partition
List are trademarks of PowerQuest Corporation.

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*. When booting Warp, a change is made to
step 3: 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. Boot Manager
-----------------
Because of bugs and limitations in OS/2's Boot Manager, moving or resizing a
partition usually causes Boot Manager to malfunction.  Boot Manager may delete
partitions from its menu, display partitions with the wrong drive letter, fail
to boot a bootable partition, fail to display a partition, or boot partly from
one partition and partly from another.

We have reported the problems to IBM and hope for their cooperation in finding
permanent solutions to these problems. In the mean time, the work-around is
simple. If you experience any of the above problems with Boot Manager:

  1) Boot OS/2. If Boot Manager will not boot, you can boot from your
installation disks.

  2) Run FDISK. FDISK does not suffer from the Boot Manager bugs and will
display all your partitions, with the correct drive letters.

  3) For any partition that disappeared from the Boot Manager menu, select Add
to Boot Manager Menu. If that option is grayed out, first select Delete from
Boot Manager Menu. This works around Boot Manager's limitation; it can not
track moving partitions.

  4) Otherwise, select Change Partition Name on any of the bootable
partitions. This works around the Boot Manager bug that causes Boot Manager to
display wrong drive letters, fail to boot a bootable partition, fail to
display a partition, or boot partly from one partition and partly from
another.

  5) Exit FDISK and save the changes.

There is another Boot Manager/FDISK bug that PartitionMagic detects and
handles correctly. Changing the Boot Manager label of a logical partition
using FDISK partially damages the partition tables. The damaged portions are
non-critical for DOS and OS/2. PartitionMagic used to give error 108,
"Partition doesn't end at end of cylinder" and refused to run. PartitionMagic
now diagnoses the damage and extracts the proper information from other
sources in the partition tables. If PartitionMagic makes any changes to the
damaged partition table, PartitionMagic will write repaired tables to the
disk.

IV. Warnings
------------
- Don't forget to backup your hard drive before using PartitionMagic.

- Don't powerdown or prematurely reboot when PartitionMagic is in the middle
of an operation.

- Do not format drives while PartitionMagic is running. PartitionMagic does
not know about the change and does not Move/Resize the partition correctly.

- 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.

- 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.

- Computers with DMA hardware bugs can corrupt partitions. A Gateway2000 P5-75
is the only computer we've seen this problem on. If you have problems with
applications while other applications access a floppy drive or a network
drive, you have DMA hardware problems and should not use PartitionMagic on
that computer. Beware that if you do have DMA hardware problems, NONE of your
data is safe for long when you run any program--including the operating
system!

- 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.

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.  Depending on the drivers loaded when
starting Maintenance Mode, OS/2 can access the entire drive. If not, you must
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
--------------------------
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

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

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.
