| Title: | -={ H A C K E R S }=- |
| Notice: | Write locked - see NOTED::HACKERS |
| Moderator: | DIEHRD::MORRIS |
| Created: | Thu Feb 20 1986 |
| Last Modified: | Mon Aug 03 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 680 |
| Total number of notes: | 5456 |
I have a problem with a printer and was wondering if anyone had
any idea's...
I have an lp14 on a 11/780. It's hooked up to a dmf32 device
is lca0. When you print to it the following happens:
Header page is printed then when the actual file should begin
all you get is one line. SYSTEM-F-ABORT%
At the same time if you did a /notify on the print it says the
same thing on the terminal? If you do a show queu/dev it comes
back with that error to.
We put the printer on another system and it works ...any help
would be appreciated.
Thanks
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 513.1 | Printer cable? | USFHSL::FULLER | F/S: When in doubt, swap it out | Tue Jul 21 1987 10:15 | 14 |
I've seen this before on a DMF32/LP27, but I'd imagine the principle
would be the same. There is a line in the DMF32 cable called
CONNECT.VERIFY. Its purpose is to ensure the DMF is truly connected
to a printer. I've seen where if this line isn't connected (bad
DMF, bad printer cable, cable not connected, etc), the header page
will print, but the data pages will just get the abort message you
see.
In the instance I saw, the customer was moving the printer around,
and the cable was pretty tight to begin with. They eventually pulled
the cable apart while moving the printer.
Stu
| |||||
| 513.2 | system-f-abort | COBRA::ROY | Mon Jul 27 1987 13:12 | 3 | |
Thanks for the info..i'll let you know how this ends up!
Regards,
Roy
| |||||