Solved

ACCESS  and WINMM.DLL problem (still a problem)

Posted on 1997-10-10
2
238 Views
Last Modified: 2012-05-04
I have MSOffice professional on 5 PCs, 4 work fine, on one PC, when I try to run ACCESS to fails with a message informing me of a page fault in respect of WINMM.DLL All 5 PCs are running Win95, all (in theory) set up the same, with software on network server (NT4.0). Any ideas as to cause (and preferably solution......I have reinstalled MS Office several times on offending PC)

I have previously asked this question and had a sensible suggestion for a cure (basically to disable the sound card........but the PC concerned does not have a sound card.) At that point I put the problem on the back-burner since I had more pressing problems. I now need a solution.
               Regards,
               Garry Homer
0
Comment
Question by:grh
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 4

Expert Comment

by:itamar
ID: 1604040
Please, find the WINMM.DLL in your Windows/System folder.
Right click it and use option "Quick view" ( i guess that's the English option), compare with the other PC's. If, it's not the same version or it's corrupted copy this file from one of the good PC's.
Check if the Multimidia option is complete unchecked in the Control Panel | Add/Remove software | Windows Installation.
Perhaps there was a multimidia kit installed some day...

IHTH
0
 

Accepted Solution

by:
FrankN earned 100 total points
ID: 1604041
You probably have either a corrupted file, or a bad Registry entry.  You didn't say whether you had an earlier version of Office on the offending PC, but often a re-install isn't sufficient to fix corrupted files or Registry entries.  You must completely *remove* the software in question (in this case, Office), and then reinstall it.  If you just re-install, the installation may see the files that are already there, and not update the new files.

If it's not a corrupted file problem, then your second choice is possibly a bad Registry entry, and you'll need to re-register the DLL in question.  You can use RegSrv32 to do this.  You'll find articles on the Microsoft Tech Support site pertaining to corrupted DLLs and how to re-register them.
0

Featured Post

To Patch or not to Patch? That is the question!

Don't get caught out like thousands of others around the world in the recent Ransomware Fiasco!
Discuss..
- Why it's not a good idea to wait before Patching
- Sensible approaches to Patching discussed
- Add your feedback, comments and suggestions

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to get Spreadsheet Compare 2016 working with the 64 bit version of Office 2016
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This video shows and describes the main difference between both orientations in Microsoft Word. Viewers will understand when to use each orientation and how to get the most out of them.
The view will learn how to download and install SIMTOOLS and FORMLIST into Excel, how to use SIMTOOLS to generate a Monte Carlo simulation of 30 sales calls, and how to calculate the conditional probability based on the results of the Monte Carlo …

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question