Unsolved

This post is more than 5 years old

Closed

3 Posts

12859

April 25th, 2005 09:00

Commit Error

I am trying to install HP's OfficeJet G Series Printer All-in-one software on my new Inspiron 8600. The Insipron 8600 has a wireless connection to a Dell True Mobile 2300 Router and the HP OfficeJet g85xi is connected to the router through a DirectJet 175x. The software has load fine but when I restart the computer I get a SEVERE - Error "Commit Failed - hResult = 80004005". When I click "ok" the message reappears. If I click "ok" again then I get an error information message explaining that the device IO has not been initalized. When I click through this message the computer comes up and everything works except the HP All-in-one software. The print drivers do work so I can print from Word or other applications but I cannot use any other functions such as scanning and faxing.

What makes this problem strange is that I have loaded the HP G Series software on a year old Dell Inspiron 5100 and an 8 year old Gateway desktop and it runs fine. Both of those computers are also on a wireless interface to the True Mobile 2300. All three computers are running Windows XP Home Edition Service Pack 2 with the latest updates from Microsoft. I have reloaded the operating system from scratch and then reloaded the application and it still fails.

HP has no idea what is going on. By process of elimination it appears to be either a hardware or operating system problem in the Inspiron 8600.


Does anyone have any suggestions?

2.8K Posts

April 25th, 2005 09:00

Check the HP website to see if there are updated drivers and or patches.

3 Posts

April 25th, 2005 14:00



@jankerson wrote:
Check the HP website to see if there are updated drivers and or patches.



I have spent the last 4 days working with HP and download everything they suggested including the lastest drivers. It does not appear to be a driver problem since I can print using Word or other applications. The problem is when the All-in-One software first loads after being installed it fails to connect to the drivers and dies. After the Commit Failed message another screen appears saying that the commit error was because the Device IO has not been initialized.

I am currently working with Dell Support but getting passed around from software to hardware to printer to wireless. It's one of those "not my job" problems.

2.8K Posts

April 25th, 2005 20:00



@Yltrit wrote:


@jankerson wrote:
Check the HP website to see if there are updated drivers and or patches.



I have spent the last 4 days working with HP and download everything they suggested including the lastest drivers. It does not appear to be a driver problem since I can print using Word or other applications. The problem is when the All-in-One software first loads after being installed it fails to connect to the drivers and dies. After the Commit Failed message another screen appears saying that the commit error was because the Device IO has not been initialized.

I am currently working with Dell Support but getting passed around from software to hardware to printer to wireless. It's one of those "not my job" problems.


That is a software problem with the all in one software, not a hardware problem.

3 Posts

April 27th, 2005 14:00

You are right. Dell software support eventually solved the problem. I ound someone there who had worked for HP and realized it was a software problem. It relates to a failed install that initially may have resulted when I tried to install the all-in-one software. The software requires Java Vitual Machine if you are going theough a JetDirect print controller. Microsoft had to remove VM from XP in SP1a because of a legal problem. Thus my initial install failed due to no VM support. I eventually got VM from http://www.hi-teach.com/infohub/help.htm and was able to eliminate this error message. This evidently left an install application pending controled by devmgr.ini. Standard Deinstalls as well as a HP Cleanup utility did not delete this file. It wasn't until we identified this application by using "Process Explorer" and then deleted this application and the complete HP directory that I was able to get a sucessful install. You are right, it was a HP software problem that HP couldn't resolve.

2.8K Posts

April 27th, 2005 16:00

Glad you got it fixed. :)
No Events found!

Top