View Single Post
Old December 14th 05, 01:03 AM posted to microsoft.public.windowsxp.perform_maintain
external usenet poster
Posts: n/a
Default XP Device manager items w/ yellow exclamation marks

Further update for the Parallel Device conflict:
I uninstalled the printer and reinstalled it, also updated the driver. No
change. (the driver was the most recent before the uninstall too) Same as
before. I started in Safe Mode to see if the conflicts went away but they did

I tried uninstalling the PartMgr (the other device conflict) in Device
Manager but all that did was cause my system to crash during reboot- so I
chose the "last configuration that worked before error" option and the system
started up fine and works fine. Later I read that removing non-plug & play
devices can cause system problems- I shouldn't have been messing around with
something I wasn't sure of. (: So back to square one investigating these
curious conflicts...

"RobertK" wrote:

Gerry, no the yellow marks are still next to the Parallel Device
(branched-out below the printer) and the PartMgr. Same error codes as before.

"Gerry Cornell" wrote:


Have the yellow question marks gone?

If not what are the error codes now?

If there are no Device Error codes against the printer I would leave the
printer as it is.


Hope this helps.

Stourport, England

Enquire, plan and execute

"RobertK" wrote in message
Gerry, thanks for the reply. I followed your first link (HP) and
seems to be installed correctly- the HP722C printer icon appears in
& Faxes and it's checked as the default printer. I don't understand what
Parallel Device showing up below the HP 722C icon in Device Manager is
about, other than I know the printer uses the parallel port. I wonder if
should try uninstalling & reinstalling the printer to see what happens? As
I've mentioned I've had no issues with the printer & just came across
exclamation marks on a whim.

When you said I should sort the printer driver to see if the Code 24 goes
away- did you mean working on the above HP722C issue first, or use the
troubleshooter in PartMgr? If so can I try uninstalling the PartMgr
and installing it again? Thanks, Robert

"Gerry Cornell" wrote: