Standalone PS?
6 messages in this thread
I'm using Word 4.0 under System 7. I printed a document to disk as
PostScript. I moved it to a second machine and sent it over the serial
port to my PostScript laser, a QMS-410. 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. How do I
make a PostScript file that I can print on any laser printer?
Next I tried SendPS 2.0 from the library. After I selected a file, it
errored "Chooser error: Couldn't determine name of printer." However, I had
selected my printer in the Chooser beforehand. (The QMS came with SendPS
v1.21. After choosing a file, it says "Couldn't open the printer driver:
LaserWriter" and then the error above.)
Does this problem have something to do with Laser Prep, or the fact that I
got my printer before System 7, or that it might not have been installed
correctly? Laser Prep and LaserWriter are in my Extensions folder.
Did I mention that the file prints fine under Word's control, and through
the PrintMonitor on the Mac. When I copy the file to the same laser
printer, it always comes up with this same error. Next, I figured out how
to make SendPS work under S7, which was to move the LaserWriter file out of
Extensions and into System, and make an alias for Extensions. This would
make SendPS work, but Word broke – couldn't open printer. Then I sent the
file through SendPS and back to disk… again, this file wouldn't print
when simply copied to the laser printer. What's up?
Dear Syndesis
<<After a while, it returned an error stating that "ok" is an undefined
command.>>
It seems like Word is creating a corrupted PS file. To use SendPS under
System 7, you have to move the LW drive from Extensions folder and place it
loose in the System folder. Try using FontDownloader instead of SendPS
under System 7.
Michael Sh
But Word prints the document without trouble when I say "Print". Wouldn't
PrintMonitor complain about an error in the PostScript? Obviously, my
document prints… so I don't think it's sending bad PostScript. I
discovered my problem with the LW alias: I moved the real file to the
System folder and made an alias, but when I moved the alias to the
Extensions folder I renamed it "LaserWriter", when I should have left it
"LaserWriter alias". Oh well.
Dear Syndesis
<<But Word prints the document without trouble when I say "Print>>
Word is just printing the text file, it's not processing the PS file. There
seems to be a genral problem with System 7's creation of PS file. Try it
with the System 6 LW driver and see if that would help.
Michael Sh
I understand that the PostScript might actually get generated by some other
part of the operating system, and not Word itself, but that isn't at the
heart of the problem, is it? When you say there's "a general problem with
S7's creation of PS file," are you describing a bug that's known by Apple
and the general informed Mac public, or are you guessing that it's specific
to my system?