U
usenetdg
I have a Dell computer; 550 MHz processor, 512 meg of memory, 20 gig
hard drive with 5 gig free, running Windows 98.
The printer is connected to the computer using a USB cable (whatever
the "old" USB is). This is the only computer supported by the
printer, an HP 920. Okay, let me be more accurate - the USB cable
goes into a USB hub, which it shares with my digital camera and
scanner, neither of which are generally connected tot the computer.
That is, the hub has three things feeding into it: the cable going the
printer (always connected), a cable for the scanner (usually not
connected), and a cable for the camera (usually not connected). The
cable for the printer feeds into the first port on the hub.
When the computer has been in use for any length of time - nothing
heavy, just some web browsing, email checking, stuff like that -
printing a simple document, even a one-pager, from MS-Word, is an
experience in torture. The printer icon will appear at the bottom of
the screen, opening the icon up shows that that document is
"printing," but nothing will happen from the printer. The document
won't print, and the printer won't even make the noise indicating it's
gotten a signal from the computer.
Yes, I've checked, and the print queue is not paused.
I've seen this behavior a bit from other programs, but it's Word from
which we do most of our printing.
If I do a Windows restart, when the computer reboots, the first thing
that happens is it asks if I want to print the queued documents, and
they zip right off the printer with no problems.
What is going on here?
It's not the cable. I had the same problems when I was using a
parallel cable with the printer. And as I said, it prints fine all
the time once I turn the computer off and back on.
It's not the printer driver. The driver on the HP web site, dated
12-11-01, was on the printer's install disk, and I've even tried
redownloading and installing it off the web site.
It's not my computer's memory. I had 128 meg up until a couple months
ago before going to 512 meg. If anything, the delay is worse now.
But I can run way more things concurrently, and never hear the disk
spinning for virtual memory access like I used to. Yes, Windows
recognizes all 512 meg.
It's not what I'm printing. It displays this awful behavior if I'm
printing a 5k text-only document, or if I'm printing a 300k thing
crammed with graphics and tables. And the 300k document will print
quickly after a restart, just as the 5k one will.
Because it is a sometimes minor, but often huge, pain to restart my
computer just because I want a printed document now, I'd like to get
this matter fixed.
Suggestions, please?
Again, my documents show up immediately in the print queue. They just
don't print right away unless I've essentially just started Windows.
hard drive with 5 gig free, running Windows 98.
The printer is connected to the computer using a USB cable (whatever
the "old" USB is). This is the only computer supported by the
printer, an HP 920. Okay, let me be more accurate - the USB cable
goes into a USB hub, which it shares with my digital camera and
scanner, neither of which are generally connected tot the computer.
That is, the hub has three things feeding into it: the cable going the
printer (always connected), a cable for the scanner (usually not
connected), and a cable for the camera (usually not connected). The
cable for the printer feeds into the first port on the hub.
When the computer has been in use for any length of time - nothing
heavy, just some web browsing, email checking, stuff like that -
printing a simple document, even a one-pager, from MS-Word, is an
experience in torture. The printer icon will appear at the bottom of
the screen, opening the icon up shows that that document is
"printing," but nothing will happen from the printer. The document
won't print, and the printer won't even make the noise indicating it's
gotten a signal from the computer.
Yes, I've checked, and the print queue is not paused.
I've seen this behavior a bit from other programs, but it's Word from
which we do most of our printing.
If I do a Windows restart, when the computer reboots, the first thing
that happens is it asks if I want to print the queued documents, and
they zip right off the printer with no problems.
What is going on here?
It's not the cable. I had the same problems when I was using a
parallel cable with the printer. And as I said, it prints fine all
the time once I turn the computer off and back on.
It's not the printer driver. The driver on the HP web site, dated
12-11-01, was on the printer's install disk, and I've even tried
redownloading and installing it off the web site.
It's not my computer's memory. I had 128 meg up until a couple months
ago before going to 512 meg. If anything, the delay is worse now.
But I can run way more things concurrently, and never hear the disk
spinning for virtual memory access like I used to. Yes, Windows
recognizes all 512 meg.
It's not what I'm printing. It displays this awful behavior if I'm
printing a 5k text-only document, or if I'm printing a 300k thing
crammed with graphics and tables. And the 300k document will print
quickly after a restart, just as the 5k one will.
Because it is a sometimes minor, but often huge, pain to restart my
computer just because I want a printed document now, I'd like to get
this matter fixed.
Suggestions, please?
Again, my documents show up immediately in the print queue. They just
don't print right away unless I've essentially just started Windows.