NetNews Usenet Archive 1992 #31/NN_1992_31.iso/spool/comp/sys/mac/apps/19012

Text File | 1992-12-26 | 3.9 KB | 75 lines

Newsgroups: comp.sys.mac.apps
Path: sparky!uunet!usc!wupost!csus.edu!netcom.com!netcom!triantos
From: [e-mail] (Nick B Triantos)
Subject: Conflicts with Claris products (was FileMaker Pro 2.0 init conflicts)
In-Reply-To: [e-mail]'s message of Wed, 23 Dec 1992 23:34:29 -0500
Message-ID: <[e-mail]>
Sender: [e-mail] (Nick B Triantos)
Organization: Netcom Online Communications Service
References: <[e-mail]>
Date: Sat, 26 Dec 1992 19:33:10 GMT
Lines: 62

In article <[e-mail]> [e-mail] writes:

   I just installed FileMaker Pro 2.0 (v1 9/92) on my 8MB IIci running
   6.0.7.  When I use my normal large complement of INITs, launching FM
   Pro 2.0 causes it to freeze during the initial splash screen.  When I
   cut back to a minimum set of INITs, FM Pro 2.0 launches and runs fine.
   Before I embark on a series of experiments where I turn off individual
   INITs and combination of INITs (I recommend a binary search), I thought
   I would check the Net.

   Has anyone experienced INIT conflicts with FM Pro 2.0?  If so, what
   INIT(s) were the culprit(s)?

Your problem, with about a 100:1 probability, is that you have a corrupt
font.  Whenever any Claris applications start up for the first time, or any
time after you have added or removed fonts from the System, they create a
file called Claris Fonts in the Claris folder in your System Folder.  What
you will need to do, unfortunately, is remove all but the most standard
fonts (Helvetica, Geneva, Times, New York, and Chicago), and try running
FileMaker Pro with all your inits on.  If it works, then I am correct.  How
can you fix a corrupt font?  Well, if you own Suitcase II or 2.0, it should
come with a program called Font Harmony.  That program is often good at
fixing corrupt fonts.  If you don't own it, then you need to re-install your
fonts from the original disks, which I hope you own.  Now, how can we tell
which font is the corrupt one?  Well, a way to test is to re-load some of
the fonts in, and try to run FileMaker Pro.  If it loads, then you know that
all the ones that are in are OK.  Now quit, add in some more, and try again.
When you get the hang, you have reached a bad font (or several of them).
Re-install, and you should be golden.

While you mention it, I would like to make my list of the INIT no-no's for
users of FileMaker Pro.  First, don't use Norton FileSaver, Central Point's
Mirror, or DiskExpress II.  FileMaker is a very disk-intensive program, and
databases often go corrupt because of these INITs butting heads with
FileMaker Pro.  If you notice that Cmd-L is now quit, check to see if you're
running NOW Menus 4.0.  It's a great program, but it does allow you to
spontaneously change and Cmd-key mapping to any menu item (actually, it
allows you to map any key to any menu item).  It's neat if you know how to
use it, but confusing if you don't.

Virus checkers.  Disinfectant is, IMHO, the best.  The init is effective and
non-obtrusive, and the program is free.  I'm not trying to take sales away
from companies like Symantec, but SAM, Virex, and GateKeeper have all caused
their share of calls to me in Claris Technical Support.

Lastly, although I know they are fun programs, Talking Moose, After Dark
using Lunatic Fringe, SoundMaster, etc. all take up a lot of memory.  When
you are using System 7 on a 3MB Mac IIsi and wonder why FileMaker Pro won't
load with all of these INITs loading, take them out of your System, then see
if it will work.

Anyway, sorry for writing so much, but it is a very common call at Claris,
and I hope that I may answer a few people's questions before they have to
wait, long distance, on hold for me to step them through this.

Anyway, have a great holiday!!

-Nick "At least I don't need a SoundBlaster to play nice music" Triantos

I may work in Claris Technical Support, but not when I'm logged in on
the Internet...