gerhard@cs.arizona.edu (Gerhard Mehldau) (11/02/90)
I've been having trouble getting the latest versions of
Disinfectant (2.2 and 2.3) to run on my Macintosh. When
I double-click on the application, it starts up, shows
the Disinfectant menu bar, then displays an error message
("Out of memory"), and quits. This happens under Finder
and MultiFinder, both with and without any INITs.
The same copy of Disinfectant runs fine on other machines
in our lab, and getting different copies (NWU, sumex, ...)
doesn't help, either.
System configuration: Macintosh II, 5MB RAM, 140MB hard
disk. Previous versions of Disinfectant ran just fine
on the very same machine, with the same configuration.
Any ideas?
-- Gerhard
--
-> Gerhard Mehldau
Dept. of Computer Science internet: gerhard@cs.arizona.edu
University of Arizona uucp: {cmcl2,noao,uunet}!arizona!gerhard
Tucson, AZ 85721, U.S.A. voice: +1 (602) 621-4632gerhard@cs.arizona.edu (Gerhard Mehldau) (11/03/90)
In article <27085@megaron.cs.arizona.edu>, gerhard@cs.arizona.edu (Gerhard Mehldau) writes: > I've been having trouble getting the latest versions of > Disinfectant (2.2 and 2.3) to run on my Macintosh. When > I double-click on the application, it starts up, shows > the Disinfectant menu bar, then displays an error message > ("Out of memory"), and quits. This happens under Finder > and MultiFinder, both with and without any INITs. With the help of John Norstad, I've solved my problem. It turned out that my Disinfectant Prefs file was corrupted, and simply dumping the file fixed the problem. Thanks to all who replied. - Gerhard -- -> Gerhard Mehldau Dept. of Computer Science internet: gerhard@cs.arizona.edu University of Arizona uucp: {cmcl2,noao,uunet}!arizona!gerhard Tucson, AZ 85721, U.S.A. voice: +1 (602) 621-4632
jln@casbah.acns.nwu.edu (John Norstad) (11/03/90)
In article <27107@megaron.cs.arizona.edu> gerhard@cs.arizona.edu (Gerhard Mehldau) writes: > With the help of John Norstad, I've solved my problem. It > turned out that my Disinfectant Prefs file was corrupted, > and simply dumping the file fixed the problem. Thanks for figuring this out. In my next release (whenever that is), I'll add code to check for a corrupted Disinfectant Prefs resource fork before trying to open it with the Resource Manager, and this will fix the problem. I already do this check before opening files to be scanned, and it should be very simple to add a call to the same checking function before opening the Prefs file. If the file is corrupt, I'll just delete it and create a new one with the default prefs settings. John Norstad Academic Computing and Network Services Northwestern University jln@casbah.acns.nwu.edu