PDA

View Full Version : unregmp2.exe error - stuck, need help


jankin
February 25th 04, 03:41 AM
I keep getting "unregmp2.exe The procedure entry point GETIUMS could not
be located in the dynamic link library MSDART.dll" failure during an XP
repair isntllation (booted from CD). The isntallation simply stops at
this point - the blurb screen keeps scrollong more advertisement, and
the animation blobs at the right bottom keep ticking, but there's no
disk activity, and it just stays stuck on "registering compoenents".
How do I get past this point and get my system back to running? My
guess is that it's media player related...

Patti MacLeod
February 25th 04, 06:41 AM
Hi jankin,

Here are a couple of workarounds that seem to be successful in getting by
the error and completing the install/reinstall:

1) Press Shift +F10 to bring up the Command prompt. Then key in taskmgr.exe
in the DOS window and hit ENTER. The Task Manager should be started. If
not, then try pressing C+Shift+ESC. In the Task Manager window, 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.

2) Try holding down the CTRL key and clicking the OK button repeatedly.

Regards,

Patti MacLeod
Microsoft MVP - Windows Shell/User

"jankin" > wrote in message
...
> I keep getting "unregmp2.exe The procedure entry point GETIUMS could not
> be located in the dynamic link library MSDART.dll" failure during an XP
> repair isntllation (booted from CD). The isntallation simply stops at
> this point - the blurb screen keeps scrollong more advertisement, and
> the animation blobs at the right bottom keep ticking, but there's no
> disk activity, and it just stays stuck on "registering compoenents".
> How do I get past this point and get my system back to running? My
> guess is that it's media player related...
>

jankin
February 25th 04, 10:43 PM
In article >,
says...
> Hi jankin,
>
> Here are a couple of workarounds that seem to be successful in getting by
> the error and completing the install/reinstall:
>
> 1) Press Shift +F10 to bring up the Command prompt. Then key in taskmgr.exe
> in the DOS window and hit ENTER. The Task Manager should be started. If
> not, then try pressing C+Shift+ESC. In the Task Manager window, 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.
>
> 2) Try holding down the CTRL key and clicking the OK button repeatedly.
>
> Regards,
>
> Patti MacLeod
> Microsoft MVP - Windows Shell/User

Thanks - the install completed; but now there no sound (asus mobo with
integrated sound). Ah well - at least the system booted now. Thanks

Patti MacLeod
February 26th 04, 06:21 AM
You're welcome.

Have you visited Asus' website in order to d/load and install the audio
drivers for your motherboard? That might help with the sound problem, as the
reinstall may have "knocked out" the drivers that were installed previously.


Regards,


Patti MacLeod
Microsoft MVP - Windows Shell/User


"jankin" > wrote in message
...
> In article >,
> says...
> > Hi jankin,
> >
> > Here are a couple of workarounds that seem to be successful in getting
by
> > the error and completing the install/reinstall:
> >
> > 1) Press Shift +F10 to bring up the Command prompt. Then key in
taskmgr.exe
> > in the DOS window and hit ENTER. The Task Manager should be started. If
> > not, then try pressing C+Shift+ESC. In the Task Manager window, 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.
> >
> > 2) Try holding down the CTRL key and clicking the OK button repeatedly.
> >
> > Regards,
> >
> > Patti MacLeod
> > Microsoft MVP - Windows Shell/User
>
> Thanks - the install completed; but now there no sound (asus mobo with
> integrated sound). Ah well - at least the system booted now. Thanks

Google