brion@cbnewsh.att.com (brion.n.feinberg) (12/15/90)
For months now, I have been having trouble with Suitcase II and conflicts with other inits. Has anyone had similar problems and (hopefully) figured out workarounds? I use lots of inits, including init/cdev, Suitcase II (ver 1.2.6), On Cue etc. Sometimes, usually after changing one of the suitcase files containing fonts or DAs, the machine bombs when opening Suitcase II. It appears that the init itself gets corrupted, because when I install a new copy, it works fine (although I have to respecify the font and DA files to open at start up). Suspecting some type of conflict between inits, I tried using init/cdev to turn inits on and off to find the culprit. The first strange behavior was that everything worked fine when I used init/cdev - even if I didn't change which inits are active! Apparently (I'm guessing here), activating init/cdev during boot-up caused some initialization to occur allowing all the inits to load properly. However, I could still turn inits on and off and boot without activating init/cdev at startup (I'm talking about holding down the mouse button to get the list of inits available) to look for conflicts. Now I start seeing strange behavior #2. Namely, Suitcase is not conflicting with any single init. Only certain combinations seem to cause problems. If Suitcase wasn't such an essential init, I'd just toss it, since it seems pretty clear to me that the problem is with Suitcase. For the first time, recently, I was unable to fix the problem by simply replacing the copy of Suitcase. I am currently using a carefully selected set of inits which seem to work with Suitcase. Has anyone seen anything like this? Any ideas on how to proceed? Thanks for all your help. Brion brion@homxb.att.com