msdart.dll and WMP

G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

My problem is an error message on opening WMP after installing a program
called iVol -
The procedure entry point GetIUMS could not be located in the dynamic
link library MSDART.DLL.

I have found a solution at Kelley's Korner (is there anything that can't
be found there?) but I don't understand what is meant by "This should
allow you to run the InfoBase CD" in the following extract from the site

"Msdart.dll Problems, Error Messages and Workarounds and Suggestions

"The procedure entry point GetIUMS could not be found in the dynamic
link library MSDART.DLL."

1. This is caused by Windows XP improperly naming the msdart dll file.
Download (save) DARTFIX.BAT to your desktop and click on it. This will
make a copy of MSDART.DLL and name it MSDART32.DLL. It will be placed in
the Windows/System32 directory. This should allow you to run the
InfoBase CD.

2. Start/Search for file msdart*.* on your computer.

Should be found in:

C:\I386
C:\Winnt or Windows\System32
C:\Winnt or Windows\ServicePackFiles\i386"

I also don't know what you are meant to do once you run the search for
msdart*.* - do you copy it somewhere?

Thankyou for your time
Cheers
miskairal
 

Shawn

Distinguished
Mar 30, 2004
214
0
18,680
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

Hi miskairal,

It simply means to use the Windows 'Find File' feature (or 'Search' in
Windows XP) to look for MSDART.DLL, then make a copy of it wherever it is,
naming the copy MSDART32.DLL.

For example, if the dll is in C:\Windows\System32\MSDART.dll, it is asking
you to copy that file and rename the copy to MSDART32.dll. I recomend keeping
the origional aswell in case other issues arise.
--
"If it's not broken, fix it anyway"


"miskairal" wrote:

> My problem is an error message on opening WMP after installing a program
> called iVol -
> The procedure entry point GetIUMS could not be located in the dynamic
> link library MSDART.DLL.
>
> I have found a solution at Kelley's Korner (is there anything that can't
> be found there?) but I don't understand what is meant by "This should
> allow you to run the InfoBase CD" in the following extract from the site
>
> "Msdart.dll Problems, Error Messages and Workarounds and Suggestions
>
> "The procedure entry point GetIUMS could not be found in the dynamic
> link library MSDART.DLL."
>
> 1. This is caused by Windows XP improperly naming the msdart dll file.
> Download (save) DARTFIX.BAT to your desktop and click on it. This will
> make a copy of MSDART.DLL and name it MSDART32.DLL. It will be placed in
> the Windows/System32 directory. This should allow you to run the
> InfoBase CD.
>
> 2. Start/Search for file msdart*.* on your computer.
>
> Should be found in:
>
> C:\I386
> C:\Winnt or Windows\System32
> C:\Winnt or Windows\ServicePackFiles\i386"
>
> I also don't know what you are meant to do once you run the search for
> msdart*.* - do you copy it somewhere?
>
> Thankyou for your time
> Cheers
> miskairal
>
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

Shawn wrote:
> Hi miskairal,
>
> It simply means to use the Windows 'Find File' feature (or 'Search' in
> Windows XP) to look for MSDART.DLL, then make a copy of it wherever it is,
> naming the copy MSDART32.DLL.
>
> For example, if the dll is in C:\Windows\System32\MSDART.dll, it is asking
> you to copy that file and rename the copy to MSDART32.dll. I recomend keeping
> the origional aswell in case other issues arise.

Thankyou for replying Shawn. I thought that is what it meant but can't
understand what it does. If the procedure entry point can't find
something in the msdart.dll and if I copy that file and call it
msdart32.dll how will it find a newly named file? And if it can't find
what it's looking for in the old file, why will it suddenly appear in
the copy? (I am clueless as to what this procedure entry point is or the
getIUMS thingy).

Anyway, I have copied and pasted the msdart.dll and renamed it
msdart32.dll but I'm still getting the same problem. I have not rebooted
yet as I'm on dialup but will try that later and see if it makes a
difference.

Do you know why installing that volume program would have caused this to
happen and why a system restore would not undo it?

Thanking you again
miskairal
 
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.newusers (More info?)

Why can't things be explained properly?
No where am I told I have to download a newer version of the msdart.dll.
After more hours spent searching I found this out here
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21111045.html

There is a link from here to a download of the dll. Once I copied that
download over the old one (ie replaced it) all is well. One day, maybe
microsoft will make error messages that actually tell you what to do
when you get them?



miskairal wrote:
> Shawn wrote:
>
>> Hi miskairal,
>>
>> It simply means to use the Windows 'Find File' feature (or 'Search'
>> in Windows XP) to look for MSDART.DLL, then make a copy of it wherever
>> it is, naming the copy MSDART32.DLL.
>>
>> For example, if the dll is in C:\Windows\System32\MSDART.dll, it is
>> asking you to copy that file and rename the copy to MSDART32.dll. I
>> recomend keeping the origional aswell in case other issues arise.
>
>
> Thankyou for replying Shawn. I thought that is what it meant but can't
> understand what it does. If the procedure entry point can't find
> something in the msdart.dll and if I copy that file and call it
> msdart32.dll how will it find a newly named file? And if it can't find
> what it's looking for in the old file, why will it suddenly appear in
> the copy? (I am clueless as to what this procedure entry point is or the
> getIUMS thingy).
>
> Anyway, I have copied and pasted the msdart.dll and renamed it
> msdart32.dll but I'm still getting the same problem. I have not rebooted
> yet as I'm on dialup but will try that later and see if it makes a
> difference.
>
> Do you know why installing that volume program would have caused this to
> happen and why a system restore would not undo it?
>
> Thanking you again
> miskairal