RE: msdart.dll and WMP

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
>
.

Relevant Pages

  • Re: .Net packaging/wrapper application?
    ... it just didn't work well in reality due to DLL ... Windows works is to look in the executable's directory for a needed DLL ... the way apps used to work when they developed Windows. ... Looks to me like Jim is looking for the .NET equivalent of compiling ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Unnown process... 5eplorer.exe
    ... do not remove the cause (a "super"-hidden .dll program) but only remove ... symptom files and registry settings. ... It has all permissions but 'copy' denied to everyone, ... then by using the Windows XP Recovery Console. ...
    (microsoft.public.win2000.general)
  • Re: WinSxS, functional under 2k ?
    ... The newSide-by-Side Assembly technology was introduced with Windows XP to help reduce or eliminate DLL Hell. ... If you recall earlier Windows versions, like Windows 95, when you installed an application you were warned if the installer tried to replace a DLL from the system folder with an older version and you were asked if you wanted to accept the change. ... Until Windows XP it wasn't so easy to use different versions of shared system DLLs, that is what the new Side-by-Side assemblies attempts to resolve. ...
    (microsoft.public.win2000.general)
  • Re: Determine name and path of dropped object?
    ... MDE I would really suggest the use of external DLL to hold the subclassing ... windows after loading the Microsoft Office Visual Basic Editor, ... Public Declare Sub DragAcceptFiles Lib "shell32.dll" _ ...
    (microsoft.public.access.modulesdaovba)
  • Re: .Net packaging/wrapper application?
    ... the simple answer to DLL Hell for Visual Basic apps was simply to place a copy of the needed DLLs in the same directory as your executable. ... The way Windows works is to look in the executable's directory for a needed DLL BEFORE using the registry to find one EVEN IF THE REFERENCED DLL IS REGISTERED ON THE PC RUNNING THE APPLICATION THAT NEED IT. ... Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming. ... Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. ...
    (microsoft.public.dotnet.framework.aspnet)