info-mac@uw-beaver (09/12/85)
From: Moderator Richard M. Alderson <INFO-MAC-REQUEST@SUMEX-AIM.arpa>
INFO-MAC Digest Thursday, 12 Sep 1985 Volume 3 : Issue 39
Today's Topics:
Macintosh Pinouts (VERY LONG! c. 8000 chars)
Smalltalk on the Macintosh (LONG! c. 6000 chars)
Flicker-free animation on the mac. (LONG! >5000 chars)
PageMaker review (VERY LONG! c. 9000 chars)
----------------------------------------------------------------------
Date: Mon, 26 Aug 85 10:53:34 pdt
From: Larry Rosenstein <lsr%apple.csnet@csnet-relay.arpa>
Subject: Macintosh Pinouts (VERY LONG! c. 8000 chars)
It did not occur to me that people would not be able to get the file onto a Mac
easily. I have enclosed a text version of the same document.
Larry
----------------------------------------------------
Macintosh Technical Notes
#10: Pinouts
See also: Macintosh Hardware Manual
Written by: Mark Baumwell April 26, 1985
Modified: July 23, 1985
_____________________________________________________________________________
This note gives pinout descriptions for the Macintosh ports, Macintosh cables,
and various other products.
_____________________________________________________________________________
Below are pinout descriptions for the Macintosh ports, cables, and various
other products. Please refer to the Macintosh Hardware chapter for more
information, especially about power limits (the Macintosh Hardware chapter is
included in the May Software Supplement). Note that any unconnected pins are
omitted.
Macintosh Port Pinouts
Macintosh Serial Connectors (DB-9)
Pin Name Description/Notes
1 Ground
2 +5V See Macintosh Hardware chapter for power limits
3 Ground
4 TxD+ Transmit Data line
5 TxD- Transmit Data line
6 +12V See Macintosh Hardware chapter for power limits
7 HSK HandShaKe: CTS or TRxC, depends on Zilog 8530 mode
8 RxD+ Receive Data line; ground this line to emulate RS232
9 RxD- Receive Data line
Macintosh Mouse Connector (DB-9)
Pin Name Description/Notes
1 Ground
2 +5V See Macintosh Hardware chapter for power limits
3 GND Ground
4 X2 Horizontal movement line (connected to VIA PB4 line)
5 X1 Horizontal movement line (connected to SCC DCDA- line)
7 SW- Mouse button line (connected to VIA PB3)
8 Y2 Vertical movement line (connected to VIA PB5 line)
9 Y1 Vertical movement line (connected to SCC DCDB- line)
Macintosh Keyboard Connector (RJ-11 Telephone-style jack)
Pin Name Description/Notes
1 Ground
2 KBD1 Keyboard clock
3 KBD2 Keyboard data
4 +5V See Macintosh Hardware chapter for power limits
Macintosh External Drive Connector (DB-19)
Pin Name Description/Notes
1 Ground
2 Ground
3 Ground
4 Ground
5 -12V See Macintosh Hardware chapter for power limits
6 +5V See Macintosh Hardware chapter for power limits
7 +12V See Macintosh Hardware chapter for power limits
8 +12V See Macintosh Hardware chapter for power limits
10 PWM Regulates speed of the drive
11 PH0 Control line to send commands to the drive
12 PH1 Control line to send commands to the drive
13 PH2 Control line to send commands to the drive
14 PH3 Control line to send commands to the drive
15 WrReq- Turns on the ability to write data to the drive
16 HdSel Control line to send commands to the drive
17 Enbl2- Enables the Rd line (else Rd is tri-stated)
18 Rd Data actually read from the drive
19 Wr Data actually written to the drive
Other Pinouts
Macintosh XL Serial Connector A (DB-25)
Pin Name Description/Notes
1 Ground
2 TxD Transmit Data line
3 RxD Receive Data line
4 RTS Request to Send
5 CTS Clear To Send
6 DSR Data Set Ready
7 Ground
8 DCD Data Carrier Detect
15 TxC Connected to TRxCA
17 RxC Connected to RTxCA
24 TEXT Connected to TRxCA
Macintosh XL Serial Connector B (DB-25)
Pin Name Description/Notes
1 Ground
2 TxD- Transmit Data line
3 RxD- Receive Data line
6 HSK/DSR TRxCB or CTSB
7 Ground
19 RxD+ Receive Data line
20 TXD+/DTR connected to DTRB
Apple 300/1200 Modem Serial Connector (DB-9)
Modem Name Description/Notes
2 DSR Output from modem
3 Ground
5 RxD Output from modem
6 DTR Input to modem
7 DCD Output from modem
8 Ground
9 TxD Input to modem
Apple Imagewriter Serial Connector (DB-25)
ImageWriter Name Description/Notes
1 Ground
2 SD Send Data; Output from Imagewriter
3 RD Receive Data; Input to Imagewriter
4 RTS Output from Imagewriter
7 Ground
14 FAULT- False when deselected; Output from Imagewriter
20 DTR Output from Imagewriter
Apple LaserWriter AppleTalk Connector (DB-9)
LaserWriter Name Description/Notes
1 Ground
3 Ground
4 TxD+ Transmit Data line
5 TxD- Transmit Data line
7 RXCLK TRxC of Zilog 8530
8 RxD+ Receive Data line
9 RxD- Receive Data line
Apple LaserWriter Serial Connector (DB-25)
LaserWriter Name Description/Notes
1 Ground
2 TXD- Transmit Data; Output from LaserWriter
3 RXD- Receive Data; Input to LaserWriter
4 RTS- Output from LaserWriter
5 CTS Input to LaserWriter
6 DSR Input to LaserWriter (connected to DCBB- of 8530)
7 Ground
8 DCD Input to LaserWriter (connected to DCBA- of 8530)
20 DTR- Output from LaserWriter
22 RING Input to LaserWriter
Macintosh Cable Pinouts
Note for the cable descriptions below:
1. The arrows ("--->") show which side is an input and which is an output.
For example, the notation "a ---> b" means that signal "a" is an output and "b"
is an input.
2. When pins are said to be connected on a side in the Notes column, it means
the pins are connected on that side of the connector.
Macintosh Imagewriter Cable (part number 590-0169)
Macintosh Name Imagewriter Notes
(DB9) (DB25)
1 Ground 1
3 Ground 7 pins 3, 8 connected on Macintosh side
5 TxD- ---> RD 3 RD = Receive Data
7 HSK <--- DTR 20
8 RxD+ = GND Not connected on Imagewriter side
9 RxD- <--- SD 2 SD = Send Data
Macintosh Modem Cable (Warning! Don't use this cable to connect 2 Macintoshes!)
(part number 590-0197-A)
Macintosh Name Modem Notes
(DB9) (DB9)
3 Ground 3 pins 3, 8 connected on EACH side
5 TxD- ---> TxD 9
6 +12V ---> DTR 6
7 HSK <--- DCD 7
8 No wire 8
9 RxD- <--- RxD 5
Macintosh to Macintosh Cable (Macintosh Modem Cable with pin 6 clipped on both
ends.)
Macintosh Name Macintosh Notes
(DB9) (DB9)
3 Ground 3 pins 3, 8 connected on EACH side
5 TxD- ---> RxD- 9
7 HSK <--- DCD 7
8 No wire 8
9 RxD- <--- TxD- 5
Macintosh External Drive Cable (part number 590-0183-B)
Macintosh Name Sony Drive
(DB9) (20 Pin Ribbon)
1 Ground 1
2 Ground 3
3 Ground 5
4 Ground 7
6 +5V 11
7 +12V 13
8 +12V 15
10 PWM 20
11 PH0 2
12 PH1 4
13 PH2 6
14 PH3 8
15 WrReq- 10
16 HdSel 12
17 Enbl2- 14
18 Rd 16
19 Wr 18
Macintosh XL Null Modem Cable (part number 590-0166-A)
Macintosh XL Name DTE Notes
(DB25) (DB25)
1 Ground 1
2 TxD- ---> RxD 3
3 RxD- <--- TxD 2
4,5 RTS,CTS ---> DCD 8 pins 4,5 connected together
6 DSR <--- DTR 20
7 Ground 7
8 DCD <--- RTS,CTS 4,5 pins 4,5 connected together
20 DTR ---> DSR 6
Macintosh to Non-Apple product Cable Pinouts
Macintosh to IBM PC Serial Cable #1 (not tested)
Macintosh Name IBM PC Notes
(DB9) (DB25)
3 Ground 7 pins 3, 8 connected on Macintosh side
5 TxD- ---> RxD 3
7 HSK <--- DTR 20
8 RxD+ = Ground Not connected on IBM side
9 RxD- <--- TxD 2
CTS <--- RTS 4-5 pins 4,5 connected on IBM side
DSR <--- DCD,DTR 6-8-20 pins 6,8,20 connected on IBM side
Macintosh to IBM PC Serial Cable #2 (not tested)
Macintosh Name IBM PC Notes
(DB9) (DB25)
1 Ground 1
3 Ground 7 pins 3, 8 connected on Macintosh side
5 TxD- ---> RxD 3
9 RxD- <--- TxD 2
CTS <--- RTS 4-5 pins 4, 5 connected on IBM side
DSR <--- DTR 6-8 pins 6, 8 connected on IBM side
[I am posting this for those who cannot FTP it from SUMEX. --RMA]
------------------------------
Date: Tue, 3 Sep 85 15:03:50 pdt
From: Mark Lentczner <mark%apple.csnet@csnet-relay.arpa>
Subject: Smalltalk on the Macintosh (LONG! c. 6000 chars)
[]
There has been so many requests for my info file on Smalltalk that I think it
warrents being posted to info-mac, so here it is... Please don't send me any
more requests for this file, and do send your address physically, not
electronically to the address below for an order form. I will still gladly
answer specific questions regarding Smalltalk on the Mac.
--Mark Lentczner
Smalltalk Group
Apple Computer, Inc.
20525 Marianni Avenue, MS:22Y
Cupertino, CA 95014
UUCP: {nsc, dual, voder, ios}!apple!mark
CSNET: mark@Apple.CSNET
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Yes, It is true, we have released the pre-product release 0.2 of Smalltalk for
the Macintosh and Macintosh-XL systems. It comes with two images: level 0 and
level 1. Being a pre-product version and because of the low price ($50,
institution licence is $150 more, or $50 for educational institutions) we do
not offer any support, you're on your own (but then again, haven't Smalltalkers
allways been...)
MEMORY
Both images expand to use as available memory upto 2Meg (should work upto 4Meg,
but we're not really sure about that...) Level 0 needs at least 512k and level
1 needs at least 1Meg. The number of objects is limited: level 0 at 14k
objects, level 1 at 32k objects. We have tested Smalltalk with some third
party 1Meg upgrades to the Macintosh as well as the 2Meg upgrade to the
Macintosh-XL from AST and it works. The major factor for a Mac. 1Meg upgrade
is if the 1Meg is continous and seen by the ROMs that way. The amount of free
space in level 0 is 3k objects and 24k words (on a 512 Mac), and in level 1 is
16k objects and 104k words (on a 1Meg Mac-XL).
FILES
The level 0 image file will fit on one 400k floppy! On the other hand, some
other files are a lot bigger. Level 1 is 600k so you will need a hard disk to
run it. The sources file (on-line sources to all the code in the system) is
1.3Meg, hence you need a hard disk if you want that too, however the system
will still keep all the source code you write in the changes file and will
decompile all the system sources it can't find. Good news is that we don't do
anything really weird with the files so that almost any hard disk that works
with existing Mac applications should work with Smalltalk. Even better is that
any disk server that appears as volume in the Finder will also be found and
used by Smalltalk (several people sharing the sources over Apple talk from one
disk server has been proven to work!) Finally, we the system comes with a file
in that makes lets you issue a command from the browser that will read the
sources off the distribution disks if you really need the source code and can't
have the sources on line (that means that sources are still available even on
diskette systems!!!)
VERSIONS
Our images are built out of Xerox version 1. (Sorry about there being release
numbers, level numbers, and version numbers...) Version 2 is what is described
in the books from Addison/Wesley. The differences are not major and we have
added equivelent things in many cases (spelling correction for instance). At
this time there are no plans for us to do a version 2 port. (If version 2 is
important to you, and you have the resources to do a port of the image, please
contact us further...) Level 0 is actually a pared down version of level 1
which is missing many of the 'extras' that are in the system (Spline curves for
example). The whole programming enviornment is there except for projects.
CONFIGURATION, SPEED, TOOLBOX, & MISC.
Just to pull together some of the above info: Yes, it is possible to run
Smalltalk on a 512k Mac with one (or two) floppy disk drives and have enough
space to do 'student' type projects (1 or 2 weeks). On the other hand, level 1
with 1Meg and a harddisk makes quite a useful system that can support a great
deal of work. The speed of our system has been clocked at 13% Dorado, or just
slightly faster than the Berkley BS2 implementation on SUNs. The images do
provide access to the Mac toolbox, although they do not make use of it
themselves. As can been seen from some of the examples in the image, one could
speed up the Smalltalk interface substantially by making use of the toolbox
(which is one of the projects we are doing here).
NEWS LETTER
At this time we are not 100% certian what to do about a Macintosh Smalltalk
newletter. For the time being, if you happen to have anything that you'd like
to be in such a newsletter (goodies, work-arounds, fixes, applications, lab
reports, novel uses, etc.) you can mail them to us and we will do somthing
useful with them. If you are seriously interested in coordinating such a
newsletter, please let us know.
Well, there's more info than you probably bargained for, hope you enjoyed it.
Ordering info: if you already sent me your address, then the order form is on
the way. Otherwise, if you send a letter to:
Smalltalk Request
c/o Eileen Crombie
Apple Computer, Inc.
20525 Mariani Avenue
Cupertino, CA 95014
She'll send you some more info and an order form.
-- Mark Lentczner
DoIt:
Rectangle allInstancesDo: [:r | Display reverse: r]
(p.s., if you get this twice, please mail me so that I may fix my addresses)
[This entire message has been archived, in Tops-20 MAIL.TXT format, in the file
[SUMEX]<INFO-MAC>SMALLTALK.TXT, as a public service. --RMA]
------------------------------
Date: Tue, 3 Sep 85 17:06:00 pdt
From: oster%ucblapis.CC@Berkeley
Subject: Flicker-free animation on the mac. (LONG! >5000 chars)
When you do animation, you show the viewer successive frames at a rate high
enough that the viewer percieves the successive frames as continuous motion.
At the movies, you just show successive frames. On the computer the frame to
frame transition is a little more complex: You draw a frame, erase it, and
draw the next. This is ususally optimized to: You draw a frame, undraw the
parts that change, and draw the parts that change in the next.
If the viewer can percieve the undrawn state, the viewer will call your
animation "flickery". The flicker problem of animation is to hide the frame to
frame transition from the viewer. A movie projector hides the frame to frame
transition by concealing the film with a shutter while it is moving the film.
On a TV set, the picture is drawn by sweeping an electron beam across the
surface of a cathode ray tube in many horizontal scan lines. If you look
closely at the Mac screen, you can see the scan line structure. The Mac
picture tube, in order to take advantage of the mass production of the TV
industry, follows the TV convention of only drawing while the beam moves from
left to right, and drawing each scan line below the previous one. (I don't
know why TV was not designed to scan in alternate directions on alternate scan
lines and draw scan lines top down in one frame and bottom up in the next. I
just know it doesn't.) The beam is deflected by magnetic fields (or electric
fields on some older sets). These fields behave as if they had inertia - they
can not be changed instantaneously. It takes time to bring the beam back to
the position of the start of the next scan line. During that time the Mac can
make multiple changes to screen memory, and only the cumulative results of
those changes will be seen by the viewer.
The Mac circuitry generates an interrupt at the end of each horizontal scan
line and at the end of each frame.
During the horizontal sync interrupt, while the electron beam is moving back
from the right edge of the screen to the left, the Mac may send a byte to the
speaker and the floppy motor. The horizontal retrace is completed very
quickly, so there isn't time to do much.
During the vertical sync interrupt, while the electron beam is moving from the
lower right corner to the upper left corner, the Mac executes procedures in its
vertical retrace queue. There are system calls for adding and removing
procedures from the queue.
The standard vertical interrupt procedure increments a global variable called
Ticks, a longInt at location $16A. If you pause in you screen modification
loop until this changes, your screen modification loop will be synched to the
video.
(Don't depend on $16A for the time. As I discovered when I wrote my menu bar
clock desk accessory, the value drifts slightly so that after ten hours, it
will be a minute or two slow.)
Synching to the video may not be good enough. If your graphics commands take
more than about 1/128th second to execute, they will still be in progress while
the beam is scanning out the picture, and syncing to the video will just have
traded you intermitant flicker for continuous flicker. The other way of hiding
the changes from the viewer is to hide the changes from the viewer - draw where
the viewer can't see them and them quickly put them on the screen. There are
two ways to do this:
1.) Use the Mac's alternate screen. There is a bit on the Mac's VIA chip that
changes which memory locations are shown on the screen. You draw on the hidden
one, and when you are done, you make it visible and draw the next frame on the
other one. The viewer never sees drawing in progress. This method has
problems:
a.) The stack is right in the middle of the alternate video page. To begin to
use it, you must move the stack out of the way, and when you are done, move the
stack back. (There is a parameter to the Launch system call so that when the
program exits, the cleaning up will be done for you, but the only way to use
that parameter is to write one program that launches a second one, so its
pretty useless.)
b.) It takes 22k of memory. Any program that uses the alternate video probably
won't run on a thin Mac, because there probably isn't room.
c.) The Mac XL doesn't have an alternate video page and future Macs probably
won't.
The second method is the one I prefer:
2.) Do your drawing off screen and use CopyBits when you are done. Allocate a
new GrafPort, and change the .bitMap field to point to a new bitMap that you
have allocated elsewhere than in screen memory. Copy the portion of the screen
that is going to change into it, make the changes, and copy it back. If the
new bitMap is aligned to a byte boundary on the screen, the transfers are very
fast.
-- David Oster, THE unknown hacker.
[This entire message has been archived as [SUMEX]<INFO-MAC>ANIMATION-NOTES.TXT.
--RMA]
------------------------------
Date: Tue, 3 Sep 85 21:33:51 edt
From: mtu!russell@Glacier (Russell Reid)
Subject: PageMaker review (VERY LONG! c. 9000 chars)
I recently bought a copy of PageMaker, from Aldus Corporation, 610 First Ave.
Suite 400, Seattle, WA 98104. PageMaker is a publications layout program,
designed to do page layout for a publication after you have written the
articles with MacWrite or Word and drawn the graphics with MacDraw, MacPaint,
or the like. (it apparently accepts any graphics in PICT format, though I did
not test it with anything except MacDraw.)
I read the whole manual before attempting anything of substance, then used it
to lay out first a very simple newsletter, and then a somewhat more complicated
four-page newsletter with three columns, some MacDrawings, headers, page
numbers, and a big title bar.
PageMaker comes with two disks, one with system files and one with PageMaker,
called respectively system and master. Its copy-protection scheme demands that
you insert the original master disk once per bootup. It will not accept a bit
copy made with Copy II Mac 4.0 as a master disk. If you do as they ask and
tear a card from the manual and mail it in, Aldus sends you a backup copy of
the master disk. I frequently carry my PageMaker disk to a remote site which
has a LaserWriter printer, so I'm nervous about not being able to make backups.
Overzealous copy protection.
To use PageMaker you first set basics like paper orientation and margins, then
set up one (or two if left and right pages differ) master page. The master
page presets printing and nonprinting items you want on every page, like
running heads, page numbers (printing) and column guides (nonprinting.) On any
given page, you can override the master page's dictum by "hiding" master page
items. You then paste things into the publication using the "place" command:
when you choose place from a menu, a list of possible text and graphics items
appears. You select one, and an icon appears showing where the top left corner
of the item is. You put it where you want it and click, and Pagemaker flows it
onto the page, between the column guides if you selected text. Text keeps
flowing until it runs into something else, either another article or picture or
the bottom of the page. The end of an article has a tab with a "+" if the
entire article didn't fit, and a "#" if it did. If there's a "+", you point at
it and click, and then go somewhere else and click to flow the rest of the text
into place.
After things are in place you can drag them around to your liking. You can
edit text and add new text on the page, though the editing sometimes works
awkwardly (as when you are editing the first part of an article on page 1 and
the editing affects the part on page 3). If you have an article in many
pieces, a given piece will have a + sign at both top and bottom if it is
continued in both directions. Supposedly if you pull on a plus sign you can
cover or uncover lines from the article, and they simultaneously appear/
disappear in other parts. It doesn't always work like that, though, and I am
unable so far to tell when it does and when it does not.
PageMaker has several useful MacDraw-like tools: you can draw lines, boxes,
and circles with various pen and fill patterns, it has rulers, something like a
grid system, and the ability to move one object behind another. You can choose
size from larger-than-actual size down to fit-in-window.
PageMaker is basically very flexible, and quite easy to learn. It is fun to
use.
PageMaker also has a number of drawbacks, some of them serious. I'll list them
in the order they occur to me.
First, and very serious in my judgement, is that PageMaker and MacDraw do not
get along well at all. If you are going to publish something on the
LaserWriter, you want to use MacDraw instead of MacPaint, so the LaserWriter
can work its magic. All the graphics I used with PageMaker were MacDrawings.
The problems are several: first, a MacDrawing of any complexity slows Mac- and
PageMaker down to uselessness. You mustn't paste it in until you're largely
finished mucking with a given page. Of course, complicated MacDrawings also
tend to slow MacDraw into uselessness. Sigh. PageMaker is worse, however,
largely because it often re-draws the picture completely unnecessarily. When
you tell it to print, it puts up a dialog box, you click OK. Then it carefully
re-draws the entire page before starting to print. If that takes 15 seconds or
so, it starts to irritate you.
Second, PageMaker simply blows up and will not print a moderately complicated
MacDrawing. In a four-page newsletter, I had several MacDrawings. One was an
outline map of the Great Lakes States, with about 10 cities drawn. (No roads or
anything fancy.) It was all made of smoothed polygons. PageMaker could not
print it (stack overflow somewhere in the PostScript code sent to the
LaserWriter) but MacDraw could print it fine. So I cut and pasted in the
old-fashioned way. (So who needs PageMaker then?...) Another MacDrawing it
wouldn't print was actually entirely text: about 35 separate captions arranged
in a box in a way that suited me. Again, MacDraw printed it OK, and the
PageMaker page printed OK when I deleted the offending MacDrawing. Get out the
scissors and glue.
Third, and more surprising and insidious, is that PageMaker does a very much
worse job of printing the same MacDrawing (on the LaserWriter; I didn't test
any other printer.) I drew an outline of a skier with polygons, filled it with
black, and pasted it into my PageMaker banner header. The skiers came out much
thicker and cruder than the MacDrawings. To double-check I cut them back out
of PageMaker, pasted them into MacDraw, then printed with no modification. The
MacDrawings looked just fine. Ski poles were thin and elegant in MacDraw,
thick and clumsy in PageMaker. Yukk, more scissors and glue. (The whole
image, not just the poles, was thick and clumsy.) As best I can figure,
PageMaker drew the polygon boundaries with too thick a line.
So much for PageMaker/MacDraw compatibility. When ThunderScan comes out with
their LaserWriter compatible software, I sincerely hope to be able to paste
ThunderScan images into PageMaker. If not, I surely will use old-fashioned
scissors and glue, and complain a lot. Right now, ThunderScans are too crude
to be used directly.
PageMaker seems to work pretty well with both Word and MacWrite. I had wome
weird translation problems with a lot of special symbols, though: I used
"...", apostrophe, and printers em-dash in Times Roman font. They looked OK on
the screen in PageMaker, but came out in some (!!??!) printings as U's, Q's,
and the like. I gave up on figuring it out and took them out of the text,
replacing with old-fashioned 's and double-hyphens and such.
My best guess, by the way as to the cause of all of these troubles, MacDraw and
others, is the weird custom Aldus version of the Laser Prep that you must use
with PageMaker. If you are printing at a remote site as I was, you learn more
than you want to know about Aldus Prep, which is the set of PostScript
procedure definitions that Aldus sends to the LaserWriter before shippint its
PostScript code. Aldus's prep file, which they call Aldus Prep, is completely
different from Apple's Laser Prep, and looks very ill-conceived both to my eye
and to some others who know a lot more PostScript.
To print at a remote site, as with other applications, you tell PageMaker to
print on the LaserWriter you wish you had, then hold command-f down to put
PostScript into a file for shipping to a PostScript printer. When you do that
Aldus first puts its prep file into "PostScript1" and then puts in the
PostScript for your document, unlike other applications which do not put in the
prep file. The prep file is very large indeed, and takes a long time (20
minutes or so) to upload every time you ship a version to the LaserWriter. It
turns out there's a way to avoid this, but it isn't in the Aldus manual:
command-option-f will print the file without the laser prep. Command-f rapidly
followed by command-d will print the file with prep file AND code to install
the Aldus header in your LaserWriter, where it will remain until you reboot the
LaserWriter. (Thanx and a tip of the hat to my PostScript guru....)
That's about all I know about PageMaker, save a few oddball quirks in using the
built-in text editor. When I copied PageMaker to my hard disk, the icon came
out with DEMO stamped over it. Huh???
On balance, I think PageMaker is way too expensive ($495 !!!!), is too
zealously copy-protected, and damn well ought to work with MacDraw. Any
program that charges $500 should work a lot better than this one does. (My
publication ended up looking good, but kudos go to the LaserWriter.) The
copy-protection irritates me, but I figure I can count on Copy II Mac to beat
it next version out. If they had used Apple's LaserPrep they would have had a
lot fewer problems....
I have nothing whatsoever to gain or lose from my opinions about PageMaker,
unless they remember my name and won't send me updates....
Russell Reid
Michigan Technological University
[This entire message is archived as [SUMEX]<INFO-MAC>NEWS-PAGEMAKER.REVIEW.
--RMA]
------------------------------
End of INFO-MAC Digest
**********************