Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!n8emr!cmhgate!p3.f200.n226.z1.FIDONET.ORG!Michael.Burton
From: Michael.Burton@p3.f200.n226.z1.FIDONET.ORG (Michael Burton)
Newsgroups: comp.sys.mac.apps
Subject: VersaTerm / AddressBook conflict
Message-ID: <71881.26FAF84E@cmhgate.FIDONET.ORG>
Date: 20 Sep 90 03:21:09 GMT
Sender: ufgate@cmhgate.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 1:226/200.3 - Aurora Borealis, Gahanna OH
Lines: 29


   Carl K. Lim wrote:
> For some reason, AddressBook 2.1 (the application, not the DA) causes the
> system to crash when after VersaTerm has been used.  I think this happens
> with RedRyder also.  This doesn't seem to be a problem with the modem, since
> it crashes despite whether the modem was used.  Turning the modem off and
on
> doesn't help.  So it has to be the communication program that does something
> to the mac that irritates AddressBook.  Has this happen to anyone?  (I'm not
> sure if this topic has been discussed before)  Any help will greatly be
> appreciated.

   This sounds like an all-too-common problem that I discovered in other
software.  I don't have either VersaTerm or AddressBook 2.1, but I suspect
the problem is that AddressBook initializes the Mac's Window Manager before
initializing the Font Manager.  Inside Mac says this is a no-no, though it
apparently only causes problems under certain circumstances.
   The quick fix is to use a file editor like Fedit Plus or the Norton
Utilities disk editor.  Open AddressBook and search for the hex string
A912 A8FE.  If you don't find it, I'm wrong.  If you do find it, change
it to A8FE A912.  If your problems go away, you owe me a million dollars...
:-)
   (Of course, NEVER modify your only copy of a program.)
 

--  
Michael Burton via cmhGate - Net 226 fido<=>uucp gateway Col, OH
UUCP: ...!osu-cis!n8emr!cmhgate!200.3!Michael.Burton
INET: Michael.Burton@p3.f200.n226.z1.FIDONET.ORG