User Forum
Xequte User Forums
Profile    Active Topics    Forum FAQ    Search this forumSearch
Forum membership is Free!  Click Join to sign-up
Username:
Password:
Save Password
Forgot your Password?

     
Forum Tips
» This forum is for users to discuss their software problems and suggestions for improvement.  Remember that only a tiny percentage of our users experience such problems (To be precise less than 0.7% have ever posted on this forum)
» Include your software version number (as displayed in the About Box)
» Check the FAQ before posting as most common questions have already been answered
» You don't need to also e-mail us separately as our support team will respond to all questions on this forum
 
 All Forums
 Xequte User Forums
 DVD PixPlay
 Device Drivers
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

mama.dj@sbcglobal.net

USA
1 Posts

Posted - Jun 20 2009 :  05:11:13  Show Profile  Reply
My computer errors out because it cannot locate mplapx.dll and cpuinf32.dll. I downloaded these drivers to my desktop; however, it does not seem able to find them. Can someone please tell me where to save these files so that they are recognized? Is there something else I need to do to have the computer recognize these files?

Thanks for your help.

JIMD

USA
499 Posts

Posted - Jun 20 2009 :  09:17:41  Show Profile  Reply
MAMA.DJ

I think I can help you out.

cpuinf.dll is a system shared library file that contains functions used to obtain information about the CPU such as CPU Speed and CPU ID

mplapx.dll is a system shared library file that contains functions used by Microsoft Media Player for audio playback

if you like, you can download both of these right here:

http://www.dll-files.com/dllindex/index.shtml

Depending on what version of Windows you are using, you should place these files in either the Windows\system or Windows\system32 (use the latter for WinXP and 2000)

As to how this happened, have you installed any Ulead software, such as DVD Movie Factory, recently? I have heard that sometimes these software packages can cause the exact problem you are describing, and Ulead software is fairly common
.
Apparently the Ulead installer tries to append the path to the .DLL in the system's PATH: statement, Restoring the proper PATH: to the .DLL should do the trick if dropping the DLLs manually into the Windows system folder doesn't.,
Also, I know that there are other applications out there that repackage these DLLs, I just don't know what they are :)

Anyway, I hope this helps, let me know how it goes,



JIM DALTON
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To: