Dec 87 Mousehole
Volume Number: 3
Issue Number: 12
Column Tag: Mousehole Report
Mousehole Report 
By Rusty Hodge, Mousehole BBS
What: System 4.2
From: Jim Reekes (CMS)
Okay, I spent about a hour getting my Mac II set up with System 4.2/Finder 6.0
and the same exact problem is still there. In PageMaker 2.0a, all Menus, Dialogs, and
fonts within the document are totally garbaged. It is as if PageMaker cannot discover
the proper font to be using, including the System font. So far this is the only
application that I have had a problem with and I do blame it on PageMaker, not Apple’s
system. But, as I did mention before, this is a bug that I saw in the beta version of the
System 4.2.
The other major problem I had with upgrading to System 4.2 was that the boot
blocks have been changed. The first time I copied the new System/Finder to my system
folder, the boot blocks did not get updated. This presented me with the shaking
“Welcome to Macintosh” dialog at startup. So I check the original system disk’s boot
blocks with FEdit and modified my hard disk to match. Now it boots up properly.
[Looks like the best way to update is to use the Installer. We used it and had no
problems. Also, I have not seen your Pagemaker problem, except on certain
down-loaded fonts. As we reported last month, Pagemaker 2.0 cannot place formatted
MacWrite text correctly which uses certain down-loaded fonts, like the thin saratoga
we use for all our source code listings! -Ed]
What: MF Interactions
From: Randy Saunders (Honeywell Inc.)
I have two interesting MultiFinder interactions to report. I can work around
them, but I would like to hear hypotheses on what causes them.
1) Start up the new DA/Font Mover (3.6?) from the MultiFinder. The first
display (fonts in System) has all my fonts. Click the radio button for DAs, only 1 DA
appears. Click the radio button for fonts and NO fonts appear. Clearly the message
here is don’t run the mover when the MF is using this data, but why the lost fonts? On
second thought, why shouldn’t the mover work?
2) When running FreeTerm 2.0 under Finder 6.0 everything seems neat. When
you run FreeTerm under the MF, and the host clears the screen, the program freezes
up. Even the I-beam cursor flickers very dimly. Unless the host sends you a
character, you seem to be stuck. I honestly don’t have a guess what is going on here.
[Lots of things crash under MultiFinder. The Lightspeed compilers bomb miserably.
How about MPW? -Ed]
What: ProApp and Wabash Computer