#Standalone PS?
3 messages in this thread
I'm using Word 4.0 under System 7 on the Mac, and I can print without
trouble to my PostScript QMS 410 laser printer via AppleTalk. I want to
make a PostScript file that can be printed stand-alone to any PS laser. I
tried testing it myself on the second computer connected to the QMS's
serial port. (The serial connection is perfect, I've used it before.)
In Word, I printed a document to disk as PostScript, then moved that file
to the other computer and sent it from within a comm program. After a
while, it returned an error stating that "ok" is an undefined command.
Looking at the PS file, it does include the AppleDict proc set. I
installed an error handler, and it said that '%endexec' and 'currentfile
eexec' were on the stack. I tried this repeatedly, even slowing down the
serial speed, and it always dies in the same place.
Next I tried SendPS 2.0 from the library. (I moved the "LaserWriter"
driver from Extensions to System and left an alias there to get this to
work.) I selected my PostScript file and "sent" it out to disk. That file
had the same error when sent to the QMS.
What am I missing? I see some code in the AppleDict that tests the
existence of 'ok' and appears to check if the laser printer's product name
is truly a LaserWriter… obviously, it's not, it's a QMS. I used Apple
File Exchange to move the file to a PC disk, with no translation, so
nothing changes in the file. To double-check that, I tried running the
file through 'compress' and the result was the same.
There is 1 Reply.
Read action !
Try running a test configuration page and check the number of the Firmware
Revision. QMS will give you (free) an upgrade to Firmware Version 9.4
which solves the SYS7 printing problems using SendPS. It also solves the
problem with Firmware Version 7's problem with AppleTalk printing under
SYS7. Hope this helps.
Read action !reply
Enter reply. (/EXIT when done)
Wow, my config sheet says I have revision 8. I just bought this thing
a few months ago, like November 1991 – that'ey've had that many revisions?
And I just talked to QMS tech support twice, and they never mentioned
this… Thanks a lot – Compuserve pays off again!
On the other hand, I don't quite see how this could be the root of my
problem. The problem seems to be with the PostScript that's generated
when I print to disk, not when I print to printer. I haven't have any
problems printing that waye regular way through AppleTalk. It's only
when I print to disk, move the file to a second computer, then
send it in an on the serial port. It doesn't print at all that way,
it gives the ewrrror I describe in the first message. fof this thread.
So it makes me thingk I'm not getting enough otof magical essential
PS prolog code when I print to disk.
/post
Message # 111374 posted
Wow, my config sheet says I have revision 8. I just bought this thing a
few months ago, like November 1991 – they've had that many revisions? And I
just talked to QMS tech support twice, and they never mentioned this…
Thanks a lot – Compuserve pays off again!
On the other hand, I don't quite see how this could be the root of my
problem. The problem seems to be with the PostScript that's generated when
I print to disk, not when I print to printer. I haven't have any problems
printing the regular way through AppleTalk. It's only when I print to
disk, move the file to a second computer, then send it in on the serial
port. It doesn't print at all that way, it gives the error I describe in
the first message of this thread. So it makes me think I'm not getting
enough of magical essential PS prolog code when I print to disk.
Read action !