#2.1: nothing prints!
4 messages in this thread
Please help! I've just upgraded to 2.1, and now, NOTHING will print out on my
printer!!!
I *know* I've got the proper driver loaded (I'm using an HP DeskJet 500), and
I've tried alternating from HPDeskJet to HPDeskJetOLD to Generic – and NOTHING
works!!! I just get a "printer not found" type message (and I know I have the
printer hooked up properly.
The only way I can get something to print is to load it into PageStream and do
it that way, it takes about 3 minutes to create and print.
What's going on???!!!
<Dave>
What somethings have you tried to conclude that "NOTHING" will print? Does
"copy s:startup-sequence prt:" work? Is your printer connected to serial
or parallel? Did you get that button switched in prefs somehow?
If you have a backup you could revert to, try this: "delete
envarc:sys/printer#? env:sys/printer#?" That will clear everything about
the printer to the defaults. Then run printer prefs and select HPDeskJet.
Then try to print.
— Dale L. Larson, Intangible Assets Manufacturing
— INTERNET:dale@iam.com
Dale: I don't know what David's problem is, but I have noticed that under
2.1, some of my software just can't find the printer if I happen to turn
it on too late in the startup or after the software package in question is
itself loaded. View80 is one such problem child. It's easily gotten
around, but a bit annoying. Then again, I've got my parallel printer
assigned to a GVP I/O Extender board, so maybe this isn't the system's
fault, though I seem to recall it happening when I had the printer on the
normal PAR: too.
From hardware point:
I assume your printer and cable did work under the old system. If yes, the
following reasons come to mind:
If you have upgraded from WB 1.3 or lower, check your CIA chips.
If you upgraded from <WB 2.04, check your printer cable. Some things have
changed in the WB 2.04 (and higher) printer.device, making the
printer.device not working with some (mainly low cost) printer cables.
Don't get me wrong: the cable might work on other computer systems… but
with WB 2.04 and higher they don't as a new printer signal is checked on
the cable.
From software point:
don't know a reason for this…
— Wolf Faust, Am Dorfgarten 10, 60435 Frankfurt, Germany —