UNREGMPZ.EXE

From: Bob (anonymous_at_discussions.microsoft.com)
Date: 05/01/04


Date: Sat, 1 May 2004 11:51:36 -0700

Hi, I have a corrupt version of WindowsXp Home that I am
trying to repair and would appreciate HELP. I was asked
if I want to Upgrade and clicked OK and the Upgrade
install began but with about 13 minutes left
in the install, I received an error message titled
UNREGMPZ.EXE-Entry Point Not Found with The Proceedure
entry point GETIUMS could not be located in the link
library MSDART.DLL. From what little I know, this does
NOT look like a good sign and would appreciate your help.
Agin, my objective is to Repair WindowsXp Home.
Thank you,
Bob
P.S.-I Posted a more complete note at 4:44PM



Relevant Pages

  • Re: Motherboard/CPU Upgrade
    ... Changing a Motherboard or Moving a Hard Drive with XP Installed ... How to Perform a Windows XP Repair Install ... So I did a Slipstream upgrade of my original XP SP1 disk, ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: new mobo requires XP upgrade?
    ... | install, repair and the typical safe modes, etc. ... Contrary to what Uncle Grumpy says, the article *does* call for an upgrade ... or select "repair" if you follow example 2 in the article. ... settings to reflect the new motherboard only. ...
    (microsoft.public.windowsxp.general)
  • Re: Repair install issues..Upgrade ?
    ... In Windows XP this option is called in-place upgrade (if you run the ... I just began what I wanted to be a repair install from an XP pro disk ...
    (microsoft.public.windowsxp.general)
  • Re: Repair install issues..Upgrade ?
    ... In Windows XP this option is called in-place upgrade (if you run the ... I just began what I wanted to be a repair install from an XP pro disk ...
    (microsoft.public.windowsxp.general)
  • Re: Repair install issues..Upgrade ?
    ... In Windows XP this option is called in-place upgrade (if you run the ... installation from within the operating system) or repair (if you boot the ... Install windows XP (which I chose, thinking I would find a "repair" ...
    (microsoft.public.windowsxp.general)