Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!claris!wombat From: wombat@claris.com (Scott Lindsey) Newsgroups: comp.sys.apple2 Subject: Re: 5.0.3 & AWGS problem Keywords: stealthy, please, Christian, rook Message-ID: Date: 17 Nov 90 07:31:28 GMT References: <2020@mountn.dec.com> <2741e03a.45ad@petunia.CalPoly.EDU> Sender: wombat@claris.com Organization: Claris Corporation, Santa Clara, CA Lines: 61 In-reply-to: araftis@polyslo.CalPoly.EDU's message of 15 Nov 90 00:24:26 GMT Subversive: Rule Psix In article <2741e03a.45ad@petunia.CalPoly.EDU> araftis@polyslo.CalPoly.EDU (Alex Raftis) writes: > In article <2020@mountn.dec.com> shatara@islnds.enet.dec.com (Chris Shatara) writes: > >One of the first things I did with 5.0.3 was to check out the new print > >driver. Well I ran AWGS and pulled in a PageLayout document which I had > >produced earlier in COMPRESSED (verticle) mode. > > > >When I went to print it, I had to use Print SETUP first as the driver had > >changed. Doing so and selecting the equivalent of "compressed" (forgot > >what its called), I ended up with a page with only half the orginal page > >on it. Quite a pain to deal with older documents when this occurs. > > > >Even though AWGS is not advertised as being compatible with 5.0.3, is this > >a bug or could I have averted the problem in some other way? > > Welcome to the world of changing printer drivers. No, it's not a bug, it's "correct" behavior. Stored with every document (except Comm) is a print record, so that the page setup "sticks" to the document and not to the session. When you changed printer drivers, the old print record stored with each document became invalid and reverted to the new driver's defaults. AWGS is not "advertised" as being 5.0.3 compatible, because it hasn't been extensively tested with that new version of the system, similar to when System 5.0 shipped while 1.0v2 was on the market. We won't claim compatibility unless we have the test results to back it up. Hopefully, since this is a minor rev of the system, there will be fewer incompatibilities than the 4.0 -> 5.0 change. > Actually, I think the probelm might be AWGS. They seem to like to push things > to their limits, which can be bad when it comes to working with future versions > of operating systems. Anyways, along your lines, I noticed that the new driver > also does not work correctly with the Spreadsheet under AWGS. It basically > attempts to print each row on a separate page, and considering by spreadsheet > had some 120+ rows, this wasn't very reasonable. I couldn't reproduce your results. Admittedly my test was simplistic: 4 rows with the digits 1-4, but it all printed on one page. Possibly you used some bizarre paper type, like one of the label settings? However, you're partially right about having problems. With the ImageWriter drivers before 4.0, printing in non-draft mode could be a memory hog. The way Apple recommends printing would cause the entire image of the printed document to be in memory at once (not just the data, but a bitmap of the entire thing). This could severely limit the number of pages in a printable document on the commonplace (1.25Mb) machine. Our work-around was to print a single page at a time. This had its own annoyances, but basically didn't hamper printing of larger documents. ImageWriter driver 4.0 now supports spooling to disk, meaning that if there's not enough memory to store the image, parts of it may be written out to the system disk (dreadful for people without hard drives, but it's added value without any major drawbacks). AWGS will not take advantage of this capability since it still prints a page at a time. If you're happy with the ImageWriter.CL that ships with AWGS, you should be able to continue to use it under 5.0.3 without problems. -- Scott Lindsey | And if you survive till 2005, I hope you're exceedingly Claris Corp. | thin. For if you are stout, you will have to breathe out ames!claris!wombat| so the man next to you can breathe in. -- Pink Floyd wombat@claris.com | DISCLAIMER: Extraterrestrials wrote this message, not me.