Our accouting uses an old Laserjet 4 printer with special ink for checks (otherwise we'd trash it).
Due to machine upgrades, I had to make use of its Jetdirect card and put it on the network.
Now, a few minutes after turning it on, its starts printing like crazy. I've done a cold reset, firmware upgrade, unplugged it for 10 minutes, to no avail. It prints fine using the new network config, as long as I get the job sent to it before this crap starts printing.
The document being printed is a few pages of weird information followed by tons of blank pages. Top of first page indicates that its a Microsoft Word document titled Lease Flyer.doc created on Windows NT 4.0, also it says "%!PS-Adobe-3.0"
Then theres a few pages of information which I assume is PS commands. If I interrupt its printing by taking it offline or resetting it, as soon as its back online it starts printing from the beginning again.
Like I mentioned, I've tried everything I know of to clear the memory, but it just won't stop. I'm trying to let the job run completely to see if that clears it, but its just feeding hundreds of blank pages now.
Any hints?
Due to machine upgrades, I had to make use of its Jetdirect card and put it on the network.
Now, a few minutes after turning it on, its starts printing like crazy. I've done a cold reset, firmware upgrade, unplugged it for 10 minutes, to no avail. It prints fine using the new network config, as long as I get the job sent to it before this crap starts printing.
The document being printed is a few pages of weird information followed by tons of blank pages. Top of first page indicates that its a Microsoft Word document titled Lease Flyer.doc created on Windows NT 4.0, also it says "%!PS-Adobe-3.0"
Then theres a few pages of information which I assume is PS commands. If I interrupt its printing by taking it offline or resetting it, as soon as its back online it starts printing from the beginning again.
Like I mentioned, I've tried everything I know of to clear the memory, but it just won't stop. I'm trying to let the job run completely to see if that clears it, but its just feeding hundreds of blank pages now.
Any hints?