error message during upgrade

[Hallimysore Keshavamurthy]

I am trying to upgrade from XP home to XP prof on my brand
new HP pavilion ZD7000 notebook. During instllation I am
seeing this error message.

window caption: Unregmp2.exe - Entry point not found
Message: The procedure entry point GetIUMS could not be
located in the dynamic link library MSDART.DLL

What is this? what should I do? This error message is not
going from screen even if I click ok button.

Could you please reply soon as I am half way installing.

Thanks
Keshavamurthy

 

[Carey Frisch [MVP]]

When the problem occurs, press: Shift + F10 to bring up the
Command Prompt. Then type: Taskmgr.exe in the DOS window
and press Enter. The Task Manager should be started. If
not, try to press: C + Shift + ESC. In the Task Manager
program, select the error messsage window in the
application list and click "End Task". In the Process
List, terminate the Unregmp2.exe program. Exit the DOS
prompt window and resume the installation process.

Ref: http://www.mcse.ms/message349955.html

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect your PC!
http://www.microsoft.com/security/protect/

--------------------------------------------------------------------------------------------------------------


|I am trying to upgrade from XP home to XP prof on my brand
| new HP pavilion ZD7000 notebook. During instllation I am
| seeing this error message.
|
| window caption: Unregmp2.exe - Entry point not found
| Message: The procedure entry point GetIUMS could not be
| located in the dynamic link library MSDART.DLL
|
| What is this? what should I do? This error message is not
| going from screen even if I click ok button.
|
| Could you please reply soon as I am half way installing.
|
| Thanks
| Keshavamurthy

 

[Matt Forner]

To: Carey Frisch

Thanks for this posting regarding the Shift-F10 and
taskmgr.exe workaround when the install hangs at the
Unregmp2.exe screen. I ran into the same problem when
reinstalling XP Home Edition. This cleared it up. I
wonder if this error is connected to recent XP security
updates?

Cheers,
Matt Forner
Washington, DC