The procedure entry point GetIUMS could not be located

**RedHouse18** · June 24th, 2004, 05:01 PM

I appreciate your advice, unfortunately it doesn't seem to be cutting it for me. I got a little further in the installation but I seem to have gotten stuck "registering components" with 13 minutes left. I still have the error message that you mention below up on the screen. Any additional help you can give is greatly appreciated.

Thanks,
Mike

Originally Posted by TripleRLtd

"The procedure entry point GetIUMS could not be located in the dynamic link library msdart.dll" Just a heads up on this issue with XP repair installs. Some people report having to click OK dozens of times. I had the same issue just now but went to check with a Google. When I went back to the pc it was finishing the install after I had only clicked like three times. Seems XP needs to think about it for a couple minutes first and approve the OK.

The issue has to do with repairing a SP1 install with the original and has to do withMedia Player being "downgraded". Thought this might help other who have to do a search for this issue.

In other words: click OK once, and then give it some time: walk away and have a cuppa or whatever. Then, all should be well. One of these days MS will have answered or fixed this problem.

**TripleRLtd** · June 24th, 2004, 05:03 PM

Welcome to WD Redhouse. Unfortunately, that is another issue entirely. Try rebooting and doing the repair again if it doesn't go away.
When you say it "seems" stuck, what is it doing? How long have you waited?

**RedHouse18** · June 25th, 2004, 01:32 PM

A cuppa tea wasn'tlong enough but a shower was! everything is golden, thanks for the advice.

mike

Originally Posted by TripleRLtd

Welcome to WD Redhouse. Unfortunately, that is another issue entirely. Try rebooting and doing the repair again if it doesn't go away.
When you say it "seems" stuck, what is it doing? How long have you waited?

**TripleRLtd** · June 25th, 2004, 02:15 PM

Cool. So more proof that you need to be patient.
And Welcome to WD dozevo.
Clicking it a zillion times only wears out your finger. In essense, it is the same as just waiting.
That being said, this is only a known workaround for this particular error message, and a few similar ones like confus-ed mentions. If there are other issues, then they would need to be explained in a new thread.
Good luck all.

**Me--Me--Me** · July 9th, 2005, 03:43 PM

Hi there,

Not sure if this is the right place for this but here goes.

I keep getting an error message which reads

The procedure entry point@WriteJPEGToMemoryRGB@24 could not be located in the dynamic link library jpegdll.dll

I have no idea what this means at all. It happens when I click on an icon after I have installed a game on the pc.

What do I do??

**NooNoo** · July 11th, 2005, 07:49 AM

Originally Posted by Me--Me--Me

Hi there,

Not sure if this is the right place for this but here goes.

I keep getting an error message which reads

The procedure entry point@WriteJPEGToMemoryRGB@24 could not be located in the dynamic link library jpegdll.dll

I have no idea what this means at all. It happens when I click on an icon after I have installed a game on the pc.

What do I do??

Err no, this error is not the same... but Welcome to Windrivers anyway! When do you get this message? it's part of a jpeg picture showing routine which is used in all kinds of programs.

**gotflash** · June 29th, 2006, 12:23 PM

Originally Posted by NooNoo

Err no, this error is not the same... but Welcome to Windrivers anyway! When do you get this message? it's part of a jpeg picture showing routine which is used in all kinds of programs.

I downloaded it and it still doesn't work. Is there anything else I can do??

**Natt** · April 3rd, 2006, 08:44 AM

Originally Posted by Me--Me--Me

Hi there,

Not sure if this is the right place for this but here goes.

I keep getting an error message which reads

The procedure entry point@WriteJPEGToMemoryRGB@24 could not be located in the dynamic link library jpegdll.dll

I have no idea what this means at all. It happens when I click on an icon after I have installed a game on the pc.

What do I do??

Hi guys, im new to trying to download games and install/run them and i am also getting this error msg and have no idea what to do, it comes up when i try to install a crack to play Hitman: Contracts if this makes sense to anyone please help, ive been at this for days and cant work it out

**Platypus** · April 4th, 2006, 04:47 AM

Originally Posted by Natt

trying to download games
...install a crack to play Hitman: Contracts

Sorry Natt, we will not provide assistance for any activities that breach the site's Acceptable Use Policy , which you agreed to abide by when you use this site.

**nihir** · June 30th, 2004, 05:09 PM

FOUND A SOLUTION!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

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.

**NooNoo** · July 1st, 2004, 05:02 AM

Welcome to windrivers nihir

Thanks, that will save a lot of coffee being drunk while waiting for the darn thing to time out.

**TripleRLtd** · July 9th, 2004, 09:15 AM

Originally Posted by nihir

FOUND A SOLUTION!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

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.

Indeed. Since this thread started two months ago, the problem has been noticed a great deal more and "other" solutions...or workarounds have been found such as this here (see post number two):
reference: http://www.mcse.ms/message778017.html
Although it seems that MS has still not gotten around to recognizing the "issue".
My thoughts on this other workaround are this: I think doing the above referenced only removes that problem window, but I think that even with the window still open after clicking ok once, the "repair" install was still installing. Otherwise, all the many people who took a break would not have come back to a successfully repaired and working pc. Right?
PS
I will update the initial post though.

**Redon73** · July 5th, 2004, 02:26 PM

Brutal, I wish I had seen this yesterday. I almost pulled my hair out trying to get the repair install to work. Wasted hours trying different things, almost paid an on site tech to come out and fix it, but no one would do it on a Sunday night. So, instead I had a couple glasses of wine with the GF, watched a movie, and left it. And wouldn't you know it, it fixed itself.... but that was the longest 13 minutes _ever_

**tarrans** · July 29th, 2004, 08:39 PM

Originally Posted by RedHouse18

A cuppa tea wasn'tlong enough but a shower was! everything is golden, thanks for the advice.

mike

Thanks for the excellent advice. I drank tea, coffee, milk and a couple shots of whiskey, but still no progress.
I decided to hit the OK button on the error message and after a lot of button pushing, the install started back up.
If waiting doesn't work, push the button.