After using Partition Magic I was trapped by the "xmnt program not found - skipped autocheck" problem. I went to the registry key involved HKLM \ System \ CurrentControlSet \ Control \ SessionManager and removed all references to Partition Magic from the 'boot.exe' key.
Now I don't get the xmnt message any more, but after the XP splash screen I get a two minute, or so, black screen with intermittent HD activity.
Would anyone be kind enough to look at their 'boot.exe' entry in this registry key and tell me how it should look?
Presumably there is also an autochk in Windows\system32, but the one in the registry is the one activated by Partion Magic Pete.
I went back to the key I had changed and deleted the 'autochk* which just left 'autocheck' there. I still get a long hang with a black screen, but no warning from autocheck, so I presume that there should be a mention of C:\Windows in there somehow.
I wonder why Arie doesn't get the same warning that I did?
Yes I did mean Boot Execute Pete. When the problem first occurred I did a Google search for 'xmnt 2002 not found', and got about 8 results. One unreachable, and six in Japanese. The one I did locate was in French, my translation follows:
_ _ _ _ _ _ _ _ _ _ _ _ ___ ___ _ _ _ _ _ _
This error message at start-up is because of using Partition Magic. Repartitioning using the graphic interface works badly and is not advised, whilst from the floppies it is much better.
PM ads a key in the registry in order to make the changes at next boot, and this key must be cleared to resolve the problem, (or gather the file and put it in x:\Windows\System32)
In HKLM\System\CurrentControlSet\Control\SessionManager, double click on BootExecute and rremove xmnt2001 or 2002.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
This is directly translated from the French, and I don't understand the "or gather the file etc." bit.
My Boot Execute now reads Autocheck Autochk* and I am still getting the b......y warning screen with the associated hanging. I have now asked Powerquest for help.
I had an answer from Powerquest about this problem, but it was of no help because it just told me what we already knew, i.e. autocheck autochk* in the registry key Boot Execute. It did however add - quote "Cause of the problem.
after PM makes a change to the partition tables, it adds the following bootexecute instruction to the registry:
%systemroot%/windows/system32/autochk.exe " This instruction contains an incorrect path. The %systemroot% string should actually be %systemdrive%
I must admit that I don't know what this means or how to find it, or even if it is possible to correct it.
I have never had a problem with the Windows interface before either. The problem now is, if I decide to try a repair of XP, will this problem be kept in the registry, or will it be corrected. At the moment I am not shutting down at all unless it is absolutely necessary. I use hibernation instead.
It turns out that PowerQuest is aware of this problem with Terminal Servers and Citrix Servers. The patch for Volume Manager is at their FTP site ftp.powerquest.com/pub/utilities/VolumeManager
Read the readme.txt file that is unzipped with the other files for where to place files.
They may have patches for other PowerQuest products under the folder for the product. Good Luck
I am using PM8 Pete, and I never had a problem with PM7 of any sort. I de-installed and re-installed to no effect, and then I tried a partition resize after booting from the floppies. All that did was double up the entries in the boot.exe key.
I have again contacted Powerquest with the problem.