Comment 100 for bug 35638

George,
Nope. Sorry for the confusion, but I quoted a previous post (who had said they had a R51..may have been you) and said I had the same problem, which I do. I id'ed the problem with my user assembled desktop with a INTELS865PERL motherboard. It has a Parallel port that I have reserved. The laptop is my daughter's and it does not have a para/port. Don't have the Make/model handy at the moment but when she comes over (frequently) she attaches the printer for output....hense the usb adapter cable. It's not uinreasonable to want this hardware to work and the HP4 is a horse of a printer with a great engine. Not getting rid of that beauty anytime soon.
Anyway, this combination ought to work in LINUX. Muffing around the problem by rearranging hardware doesn't really address the issue of the adapter cable support deficiency.
Thanks for the responses.

I'm trying to find a way to get to the hal folks to see if they can help with the issue. There are several threads out there with various descriptions of this issue and most have no clue where the genesis of the problem is. If it's not hal it below that level. I really do not think it is cups but that it is were the low level hardware detection is occurring....Since the cable itself is being correctly identified as a printer, it seems probable that a timing change in the logic would be all that is required to fix this.

Wish I knew more about linux internals (only in a brief weak moment, then I get a beer and think about the beach)
If I find an answer I'll post it back here..Hope you don't have to buy another printer to get this fixed. That is not exactly what I would call a "it just works" solution.
Later,
Bill