I have just installed PartitionMagic 8.0 and am trying to resize two
partitions.  After doing everying I need to do to accomplish this, at
the last click, I get "Error #11019" and a great "thung" from the
computer.  I know this is an operting system error according to the
PartitionMagic documentaion, but I cannot find out what it is or how
to fix it.  I am using Windows XP Home Edition.  How can I "fix" this?

Hi deewuhwa-ga,

Unfortunately, the error you describe is more complex to fix than
you're probably bargaining for. I found the following information
about the error:

(Please note, all text between the !==*==! marks are copied from the
site the link leads to.)

Windows XP Service Pack 1 Known Issues
http://www.ostweaks.com/temp/windowsxp_service_pack1_known_issues.html#_Toc17884035
!==*==!
Partition Magic makes changes to the registry. These changes take
place during the process of resizing a partition.  It is possible
other changes made by Partition Magic also make registry changes, but
this is only known instance where an issue has come up. This change to
the registry has been present when using Partition Magic, however has
not caused any known issues that we are aware of in prior releases of
our operating systems.

Build 1079 and later versions of the service pack will expose this
registry change with an error. When you install Service Pack 1 for
Windows XP you will get the following error message. "System could not
allocate the required space in registry log."

Build 1079 presents this error. Build 1050 did not.  
Build 1089 and later builds have a workaround in place for people did
not run into this problem with 1079.
Steps to reproduce: Run Partition Magic and resize the partition. When
Partition Magic runs it modifies the system hive of the registry.

Partition Magic makes changes to the registry at boot time before the
OS is loaded. They rename the registry mounteddevices key.

            HKEY_Local_Machine\System\MountedDevices

The MountedDevices key is later renamed back.  A new key is left in
place MountedDevice1 for trouble-shooting purposes. The way the
registry is modified affects the changes in build 1079 when we look at
the LastKnownGood entry.  The entry is not at the expected location,
thus the error is generated. We can work around the issue in the next
release of Service Pack 1 by making changes to mounteddevice1 registry
key.

Resolution: The built in workaround only applies to systems that did
not previously install 1079 and ran across the registry error message.
If the user previously had the error. "System could not allocate the
required space in registry log." you may not be able to install the
service pack unless you restore from an image without any previous
1079 installation failures.

This is due to uninstall failing to complete properly and leaving the
system in a partially installed / uninstalled state. If the uninstall
actually succeeded, it may very well be possible to install build 1089
or a later version of the service pack. However, all internal attempts
to install the service pack after this type of failure were
unsuccessful. Booting with last known good also failed to resolve this
problem.

This key is not used by the OS and is left on the system only for
trouble-shooting. This registry entries will be fully fixed with
Service Pack Two for Windows XP and will be fully fixed in Windows
.NET. Powerquest is working on resolution that will prevent this from
happening and will update their software."
!==*==!

So, the quick answer to the problem is to attempt to uninstall Service
Pack 1, and reinstall the latest Service Pack 1a in your install of
XP. HOWEVER, this is NOT an especially safe thing to do: you may cause
more problems than you solve.

Second solution MIGHT be the floppy boot disks. However, there's no
guarantee that they will work either--as you can see from the above
quote, in the 'resolution' section, there is no mention that a
boot-disk approach will work any better.

You also MIGHT be able to save a step and lots of hair-pulling by
trying to install SP1a over top of your SP1 install. The download page
for SP1 can be found at:
http://www.microsoft.com/windowsxp/pro/downloads/servicepacks/sp1/default.asp

I'd recommend doing the "Network Install" and forcing a full/complete
reinstall of SP1a. That might help with the issue.

Failing the above, complain to PowerQuest and ask for a refund and/or
a bug-fix that will work around the known SP1 issue from Microsoft.

If any part of this answer is unclear, please let me know by asking
for clarification prior to rating and closing this question.

Legolas-ga

Hi deewuhwa, 

At the Windows NT command prompt, type:
net helpmsg 1019
SOURCE: http://www.powerquest.com/support/primus/id720.cfm

Also have you tried rebooting and using the floppy disks that came
with your PartitionMagic software? In my experience, I have found that
it is quite safe to partition using the PowerQuest software, but you
should have backups made beforehand.

tisme-ga

Thank you for the comments.  I am using XP and not NT.  I tried it
anyway at the "Run" command and got a quick flash of black . . . .but
no answer.  The floppies I got I made.  But I'll try rebooting with
them.

Thanks for your comments.

deewuhwa

Just to complete the info here. Have the same problem under Windows
XP. Used the floppies and that worked fine in getting my NTFS
partition resized.

Cheers!

The following sequence of actions seemed to solve the problem
(permanently?) for me..
I'm using windows xp build 

1. I removed every key inside folder
HKEY_Local_Machine\System\MountedDevices1 except "Default"
2. I renamed the folder to a temporary name, say "temp"
3. I rebooted
4. I completely deleted the temporary folder ("temp")

At last, I ran Partition Magic again and everything worked fine..

cyfex

I'm using windows xp (unknown build) and i had the same problem
The following sequence of actions seemed to solve the problem
(permanently?) for me..

1. I removed every key inside folder
HKEY_Local_Machine\System\MountedDevices1 except "Default"
2. I renamed the folder to a temporary name, say "temp"
3. I rebooted
4. I completely deleted the temporary folder ("temp")

At last, I ran Partition Magic again and everything worked fine..

cyfex