Community Manager

 • 

56.9K Posts

November 11th, 2004 16:00

Jof,

Where did you find the Officejet 500 and 600 series fix?

11 Posts

November 12th, 2004 10:00

hi,
 
HP support emailed me the following link
 
I am still having the same error message, even though I have updated my .Net Framework, ran the HP reg fix (scrubber), uninstalled and re-installed the USB ports, re-installed the updated softeware, installed in safe mode...
 
Basically - unless there is a clear , concise 'fix' - I am gonna drop kick the psc into touch...
 
thanks for looking.
 
Jof

11 Posts

April 6th, 2005 09:00

for info - the fix i finally found was to use the IP address of the printer (as it resides on a network via another pc) instead of the name of the printer. This worked !

9 Legend

 • 

47K Posts

April 16th, 2005 23:00

HP Officejet 500 and 600 Series - Error: Attempt To Release Mutex When Printing


ISSUE: Either during the installation process or some time after the HP OfficeJet 500/600 Series software is loaded, when you try to print, the following error message or messages appear: "Attempt to release mutex not owned by caller" and/or "cannot create a file when a file already exists." The HP OfficeJet Printer/Fax/Copier/Scanner will no longer print.

WORKAROUND:Check the C:Windows\system.ini file. Make a backup copy of the System.ini file. Go to the line in the boot section that reads: "drivers=mmsystem.dll." Also check for "system.drv=system.drv." If either of these lines is missing, insert blank lines and type the lines in, save the file, and reboot.

NOTE: Look for any odd-looking entries in this section that could potentially cause a problem. Delete the lines in question and remove any blank lines. If you have a problem, bring back the original system.ini file you saved.

Example of a typical [boot] section

[boot]

system.drv=atmsys.drv (may read system.drv=system.drv)

drivers=mmsystem.dll power.drv (the power.drv entry does not cause an issue)

user.exe=user.exe

gdi.exe=gdi.exe

sound.drv=mmsound.drv

dibeng.drv=dibeng.dll

comm.drv=comm.drv

shell=Explorer.exe

The system.ini file should look very much the same as this example. In some instances, various drivers will include entries in the drivers' line that interferes with our bidirectional communication.

CAUSE:


In general, this error may occur when the printer driver "thinks" that bidirectional communication has been lost but the rest of the software (the document assistant and the manager) is running normally.

11 Posts

April 20th, 2005 12:00

Thanks speedstep - but I now have exactly the same problem with my new printer.
 
I am trying to install the hp deskjet 9300, but I am getting the dreaded 'mutex' message.
 
I have a DELL OPTIPLEX 240 running WIN2K.
 
The system.ini text you have displayed above does not look anything like the text in my system.ini file.
 
ARe you aware of a fix for me ??
 
many thanks
 
Jonathan
 
 

9 Legend

 • 

47K Posts

April 20th, 2005 19:00

The problem is definitely a Driver issue and or USB port issue.
Call HP and get them to help.

11 Posts

April 25th, 2005 07:00

Thanks Speedstep - will give 'em a go.

 

Jonathan

No Events found!

Top