eoshough@nmsu.edu (Mel Callender) (01/24/91)
(This is aimed at all you PageMaker guru's out there) I'm in charge of a Mac network, and just recently I was handed a big wad of Student PageMaker 4.0 disks, told to install it on our network and on various hard drives. ( We have 21 licenses, and in the zone it was installed there are only 15 machines, and the other 6 go on Mac II's with harddrives.) Fine. After a serious amount of fooling around, the student version of PageMaker 4.0 lives on the network and on the 6 Mac II's with harddisks. Great. Now, I try to print from these machines, notably the Mac II installations, and the job is flushed by the LaserWriter (who is connected to an AppleShare spooler). More fooling around results in replacing Aldus's Aldus Prep with a fake constructed with a Laser Prep whose type and creator has been changed to those of the Aldus Prep. ( Follow me so far? :) ) This seems to work alright, so no problem. >>BEEEEPPPP<< wrong. PageMaker 3.0x continues to live in another zone with shares the printers that PageMaker 4.0 uses. This causes a Prep crash in the printer because the 3.0x are using the 3.0 Aldus Prep. PageMaker 4.0 would try to print, and when it saw the old Prep in the LaserWriter, it would say 'No way, Jose' and cancel the job. Quick call to Aldus confirms that by substituting the Aldus Prep 4.0 for the old Aldus Prep 3.0 will solve the problem. So I spend better part of a day upgrading every installation of PageMaker 3.0 that could conceivable print to my printer to the new Prep file, and breath a sigh of relief. Too soon. Now it seems completely non-deterministic whether a job from PageMaker 3.0x or PageMaker 4.0 will print or be flushed. Needless to say, I'm am pretty frustrated. And so, I turn to the 'Million Dollar' net. If anyone has encountered this problem, or has a practical suggestion for a different approach ( i.e. one that doesn't involve major hardware/software upgrades ), or comments in general, please mail me at the address below. If the above needs clarification ( with my state of mind, I'm sure it does! ) please do not hesitate to ask for it. Flames for buying PageMaker and not something else will be completely ignored, I had no choice in the matter. Waiting anxiously.. -- _____________________________________________________________________________ ~ | Erik O'Shaughnessy |\/\/\/| ~ | Small Systems | | ~ | New Mexico State University | * | ~ o========== | Las Cruces, NM USA | (x)(x) |_|==== | eoshough@dante.nmsu.edu C _) === |------------------------------------ | ,___| === |"Do not follow the NULL pointer, | / | for that path leads to chaos, /____\ Die Bart! Die! | and madness." - me | \ | -----------------------------------------------------------------------------
steve@violet.berkeley.edu (Steve Goldfield) (01/24/91)
In article <EOSHOUGH.91Jan23124544@dante.nmsu.edu> eoshough@nmsu.edu (Mel Callender) writes:
Problem of PageMaker 4.0 and a spooler, not printing.
Here's what Aldus told me when I tried to print with
SuperLaserSpool; actually I don't think it was Aldus
but the company currently responsible for SuperLaserSpool.
If you try to print a complex PageMaker file, the spooler
tries to stick all the commands into a spool file--downloaded
fonts, etc. The file gets very big. At that point, it gives
up and nothing prints. I think a small file will print,
though I haven't bothered to try. As a result, I keep
printing from PageMaker in the foreground and cursing
as it ties up my machine.
I can understand the inability to handle very large spool
files. What I find incompetent is that no error message
is sent to the user. Nothing at all happens.
Steve Goldfieldgjb@cs.brown.edu (Gregory Brail) (01/25/91)
In article <EOSHOUGH.91Jan23124544@dante.nmsu.edu> eoshough@nmsu.edu (Mel Callender) writes: > >Now, I try to print from >these machines, notably the Mac II installations, and the job is >flushed by the LaserWriter (who is connected to an AppleShare >spooler). PageMaker isn't always happy printing through the AppleShare Print Server, especially if you're using downloaded fonts. Try printing straight to the printer, bypassing the print server entirely. (Be sure the "bypass" option is turned on in the print server.) If this doesn't work, try using the Apple print driver rather than the Aldus driver. You do this by pushing the "Change" button on the bottom of the PageMaker 4.0 "Print" dialog box and changing the "Driver" option from Aldus to Apple. (If I remember correctly.) This will also solve your problem with incompatible Aldus Prep files, since the Apple driver bypasses Aldus Prep. -greg +----------------------------------------------------+ Greg Brail Internet: gjb@cs.brown.edu BITNET: gjb@browncs.bitnet UUCP: ..uunet!brunix!gjb Home: (401)273-1172