required cpqmixer.DLL not found

cpqmixer DLL is constantley poping up on start up boot only then computer runs fine, can I get rid of dialoge box cpqmixer DLL

 

Option one
Do a search / find files for cqpmixer.dll on your computer.
If found go to start / run and type
sfc
hit enter
when it says that it found a problem with cpqmixer.dll tell it to restore from where you found it. (Preferably if you have a D: restore partition on your Compaq choose this copy)

If you have it and it is in C:\Windows or Windows\System
try going to start/ run and type
regsvr32 cpqmixer.dll
and hit enter
It should say file started or entered or something like that.

It is also possible that you uninstalled the compaq sound manager and it left the call for this dll behind. That may be a bit more difficult to clean up, but we can work on that if you did indeed do this.

 

I have a few more additional comments to add to Ohswyn's thoughts that this may be sound related, left over dredge or the file its self is missing...

It is a Compaq file. Via a Google search, there are a few references to this file problem and win98. "Missing" and "sound related" are two of these possibilities, but it may not be directly related but rather indirectly related to sound device. Some have pinned it down to the "Total Access Keyboard" (my guess is the Compaq keyboard probably has a sound volume controls built into it). They have reported that after making sure that any HP or Compaq keyboard is installed correctly the problem was resolved. This may or may not apply to you depending on what type of keyboard your computer has detected and is using in device manager or if you have an indication that hp keyboard software is being loaded via "msconfig ">startup" tab.

Others have reported that a Compaq specific service pack was needed as this is also a known common problem and error, bug or glitch with specific models of Compaq computers. You need to visit Compaq support site and do a search for your specific make/model to see if the problem is know for your comp and update it with the sp that is applicable.

 

Are you saying if I just type regsvr32 cpqmixer.dll , it may fix the problem

 

required dll

I tried it and it came up with-Libray cpqmixer dll failed get last error returnes 0x0000485

 

Now maybe we are getting someplace, I just installed a new logitech key board, and I didnt install the disk that came with it because eveything works, but should I run the logitech disk any way to get rid of my problem?

 

Right click My Computer on your desktop then click Properties. Under the Device Manager tab click the + next to Keyboard to expand the list. If two different keyboards are shown highlight your old keyboard then click the Remove button. If both keyboards have the same naming scheme remove both. Reboot and your new keyboard should be recognized as the only one. If this doesn't stop the error then the old keyboard is probably listed in Startup and will have to be disabled there. Post back for directions on how to remove the keyboard from Startup if the error continues.

 

Hello again Rhondas,

I've been watching your post here:
http://www.cybertechhelp.com/forums/showthread.php?t=89772&page=2 and have felt that you were in in very capable hands but this problem seems to be going on for some time. I have searched high and low for a more concrete lead as to what component this dll would come from or be required by but have come up empty handed. Your going to have to play detective on your own computer and try to discover 1] if you need this dll and restore it or 2] if it is not needed, get rid of the program or load line that is still calling for it. I can give you quite a few ideas on how to go about playing detective if you like. Here's a few ideas:

#1
Go directly to the horses mouth, so to speak, and use your support service. This option looks like a winner:
http://h20179.www2.hp.com/psgna/caller/chat.asp
An online chat with a compaq tech...ask them
*Which application or device uses the cpqmixer.dll (it may be shared by more than one application)
*If you need it (be sure to mention that you have replaced your keyboard recently)
*How you can restore it or where you can get it (many of these files can be extracted individually from the recovery cd's but knowledge of "where it is" is needed, as well as the Compaq "how-to" step by step is needed). They may even have this file stored somewhere and can give you information on how you can download it. Either that or send it to you.

The following are more "manual" or "self help" suggestions....

#2
Open regedit and do a "search" (toolbar>edit>find) for references to "cpqmixer ". See if any application, device or load line clue can be found. Don't make any changes unless you ask for second opinions here, or are familiar with registry precautions such as backups, restoring, or exporting hkeys prior to to editing.

#3
Do a file search via the start startmenu button but instead of looking for the file "cpqmixer ", put *.* in the file type-in field and put cpqmixer in the text field. Perhaps this will lead to some clue. It may be an *inf file or a setup text or log...etc, that when opened in notepad, will offer or lead to the application that this dll relates to.

#4
Knowledge of sfc (system file checker) is needed:
Using SFC to check for files flagged as corrupted. Use the boards search feature to read up on the subject "SFC ". Learn how best to use this feature of win98 and become aware of it's flaws. Your only going to use this as a helper to point out issues that may be a problem and any flagged as such by SFC should be "ignored " by the tool itself.

See my comments about sfc included in this pastpost (ignore the topic of the post and comments about win.com. That was the original posters "problem and issue" at the time that I wrote this older archived post):
http://www.windowsbbs.com/showpost.php?p=135343&postcount=3

Use sfc.exe and read the log or run it with advanced option of checking for deleted files. It is most important to remember though, that it is only the cpqmixer we are interested in.

You may even want to give sfc's "extract" option a shot and point it towards your recovery cd or perhaps *:\windows\option folder (if you have such). Many users have the winxx install cabs in this folder.

#5
msconfig
Check the startup tab for references to files such as:
CPQEAUI, CPQEADM, EACLEAN, CPQEK.exe and BTTNSERV, which are all part of Compaq’s EasyAccess Button Support which enables you to program the extra "Easy Access keys" on the Compaq multimedia keyboards.
If found....
Recommendation :
If you decide to use a keyboard other than your Compaq multimedia keyboard, then disable CPQEAUI, CPQEADM (if present), and EACLEAN in The Ultimate Troubleshooter, as they will no longer be of any use to you. If, however, you are replacing the Compaq multimedia keyboard with another type of multimedia or specialist keyboard, such as the Microsoft Internet keyboard, the Microsoft Ergonomic keyboard, or some of the Logitech or Kinesis multimedia/internet keyboards, then it will become necessary that you disable the above two tasks as they will otherwise interfere with the proper working of your new keyboard.

"Total Access" keyboard files may differ but these file names are ones I have run across so I posted "em just in case. Look for references to such HP or Compaq programs in your startmenu/programs list. If found you may wish to uninstall the application.

#6
You could try booting up in safemode and see if the error is gone. If so an "msconfig" diagnostic or limited bootup may help to pin this down.

#7 (Last resort and experimental. The following suggestion should only be done when all else failed! Suggested mostly by curiosity on my part. This is risky if a device or program still needs this. On the other hand, if that proves to be the case, it can be re-registered, once found and put in c:windows\system folder. If a device or application reinstall is called for, it would do this anyway.) That said....
You could try to unregister this dll as opposed to the registering you tried to do earlier:
regsvr32 /u cpqmixer.dll or regsvr32 /u c:\windows\system\cpqmixer.dll

To sum up....
These are just some things to try and I could come up with others if need be. The suggestion of posting a startup list as advised here: http://www.cybertechhelp.com/forums/showthread.php?t=89772&page=2 was a good one. This may help others to spot the program that may be calling for this dll. Please, please remember to come back to us and share the final outcome. I am quite curious now...

You have never confirmed whether you tried reinstalling or updating your sound drivers. I noticed you mentioned you had lost your sound "volume icon" in the systray. Have you tried putting it back?

 

OK thanks so much for the compaq HP support ,they helped, heres the fix,
[[[[first I removed and let windows reconfigure my key board next.
As for the issue with the popup message, please follow the steps provided below: 1. Click Start, and then Run 2. In the command box, type msconfig; and click OK. 3. Click Startup. 4. Uncheck all the programs except RECGUARD, KBD, PCHBUTTON (if listed) 5. Click OK 6. Restart the system If you see a message "System Configuration Utility You are using the selective startup for troubleshooting your system ", check the option and click OK. This occurs if you are using the Selective startup option but not using the normal startup to reduce the number of startup programs.]]]]

 

Hi Rhondas,
So it maybe or is keyboard related. I take it disabling one or all "RECGUARD, KBD, PCHBUTTON" as a startup has fixed the problem.

I'm a little confused by your explanation. Did you uncheck these items and leave all others checked or did you uncheck all items and leave these checked? I am asking because there are certain things in msconfig startup that should not be disabled, at least not on any permanent basis. If you have unchecked all except these items that means they are not the problem but something else you have disabled from startup is the problem.

As much as I hate to keep poking this tiger, I want to make sure you have not caused yourself more future problems by disabling the wrong things from running at startup.

That startup list sure would help to figure out exactly what you've done and what should be done. It is never recommended to run on msconfig selective startup permanently. This is another helper item and once the problematic startup item or items have been pinned down additional steps should be taken to discover how to eliminate these (disable them from running) on a more permanent basis so that you can return to using an Msconfig "Normal Startup ".

 

dll

have unchecked all except those

 

Pooh! This is what I thought. Are you familiar with the theory behind using msconfig for trouble shooting startups or is all this new to you? I am going to try to explain or give you an overview on what "you are doing ", "what you did do" and "what you should do now ". Please keep in mind, for future use, that Msconfig (known additionally as "System Configuration Manager ") has many capabilities for experimentally or temporarily disabling various items and settings that may interfere with windows functioning in a normal manner. This is it's main function and use as a tool. Under normal circumstances one would have to use innumerable or various other methods to accomplish what msconfig allows you to do in one convenient spot. For the purpose of this post I will only be focusing on the task at hand, which is pinning down the application causing the cpqmixer.dll error using the startup tab "process of elimination ".

The list of "checked " items you see, when you are looking at msconfig's startup tab, is a list of the programs that are being started or ran during the windows boot process. It is not a complete list but for your purposes it seems to be complete enough that one of the items you now have unchecked is the startup that causes the cpqmixer.dll error. There are tasks in this list that should not be disabled as rule of thumb. These are:
*ScanRegistry
*TaskMonitor
*SystemTray
*LoadPowerProfile (may be two of these, if so both should be allowed to run)
*Also, your antivirus program (for obvious reasons).

There may be others but those would be user specific startups and further investigation would need to done to see if these need to be loaded or ran at startup. It was recommended by the Chatline Compaq Tech that you also include or enable:
*RECGUARD
*KBD
*PCHBUTTON

Since you have done so and this has not caused any return of the Cpqmixer.dll error leaving these checked should not cause a problem. What you also have done by disabling or unchecking all but these three items is disable certain startup items that should not have be disabled on a permanent basis.

What you should do now is enable or put a check in items I previously mentioned: *ScanRegistry, *TaskMonitor, *SystemTray, *LoadPowerProfile, *antivirus program. After doing so reboot to make sure that enabling these does not reproduce the cpqmixer.dll error. If it does we will have to scratch our heads and figure out why but we'll cross that bridge if and when we come to it...

Hopefully you have now rebooted, cpqmixer error free, with at least
*ScanRegistry, *TaskMonitor, *SystemTray, *LoadPowerProfile, *antivirus program, *RECGUARD, *KBD, and *PCHBUTTON items checked and enabled. Now you need to systematically enable any other items listed, one at a time, rebooting between each. The theory behind this elimination process is that when you find the one that reproduces or causes the cpqmixer.dll error to return, you have found the culprit. Further steps can then be taken to take care of the problem on a more permanent basis. All this is done in the effort to return windows to a "Normal Bootup" verses Msconfig's "Limited" or "Diagnostic" startup.
==========
Try the above technique, as explained, and let's see if one of the items in the list, indeed reproduces the cpqmixer.dll. If found, please update your post with the findings.
==========
On the flip side, it may be totally possible that, all along, the error was based on *RECGUARD, *KBD, and/or *PCHBUTTON being loaded and recognized as startups. This may not have been the case prior to the removal and reconfiguration of your keyboard via device manager. An msconfig "Normal Startup ", at this point, may be possible without additional steps, but the startup tab "process of elimination" is still a good learning experience...

 

Giving this a bump.....

Rhonda has not returned to the board. I will bump this to the top of the list, one time, in hopes that she will reappear once again. I do not want her or myself to lose track of this post. I think I'll zap her an email just to make sure she has not not gotten lost. Sure hope she returns....

 

required DLL

Thanks for your help but My computer is running fine now and a friend helped me ,and I dont know much about it, Im rather new so I must end this session Rhonda.

 

Thank you for your quick response and the update of your post. I only hope that friend has made sure you have the items I have suggested set or at least scanreg is being allowed to run. I can make suggestions but what you decide to do, based on experience level, comfort or curiosity, is up to you. Startups tend to be problematic and I'm sure at some point in time you will find yourself having to deal with a similar problem or issue. Can't fault you for being tired of dealing with this issue, for now, and wishing to put it to rest. Should you ever get curious again, this post will be here, found in the Archives....

Your very welcome.

 

required dll

Thanks so much for understanding