Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!agate!sandstorm.Berkeley.EDU!dburr From: dburr@sandstorm.Berkeley.EDU (Captain_Picard) Newsgroups: comp.sys.mac.system Subject: Re: SuperMac "Manager"- huh? Message-ID: <1991Jun9.221625.19165@agate.berkeley.edu> Date: 9 Jun 91 22:16:25 GMT Article-I.D.: agate.1991Jun9.221625.19165 References: <1991Jun9.200338.26144@midway.uchicago.edu> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: Starfleet Command, USS Enterprise, NCC-1701-D Lines: 35 In article <1991Jun9.200338.26144@midway.uchicago.edu> nwc1@quads.uchicago.edu (Einstuerzende Neubauten) writes: > > Just before (and after, as well) installing System 7.0, I ran the >Compatibility Checker Stack. Interesting thing is that it turned up something >called "Manager" which I didn't think that I had. As far as I know, I've >never gotten anything by SuperMac. Don't they make large screens and things? >Anyhow, there's no INIT or anything which even resembles "Manager". Is it in >the "System"? > Oh, the reason that I know that Manager is from SuperMac is that it >says so in the stack's "For further I=info, contact the manufacturer" section. >Can anyone tell me what it is that I or someone installed to make this show up? > System 7.0 on a 5M RAM, 40M HD SE/30. No external screen yet. >Extensions: Gatekeeper & Aid, BeepFlashToo, Extensions Manager, ATM 2.0, InUse, >DragWindow, JustClick, Public Folder, Programmer's Key, Remember, Understudy, >DeskPict, Suitcase 1.2.10. In case it matters. Post or e-mail welcome. > > >-- >*** The University of Chicago *** >*** Claimer: Beavers Are Gods. Disclaimer: Believe What You Want. *** >*** Come closer and see/ see into the trees/ find the girl if you can -Cure *** >*** Tintin et Milou. "Goofy Come to a Party" - Mickey Mouse Talking Phone *** You're not the only one! I had this happen to me, except in my case, it interpreted one of my applications as some weird high-powered graphics arts program that I never even heard of, let alone had on my disk! I think this is a bug in the compatibility checker... I think it checks by filetype/creator, certain resources (Owner resources, etc.) and "vers" resources, and some- times it screws up because certain manufacturers use the same resources/ filetypes as others =============================================================================== Donald Burr, Univ. of California,Berkeley | America Online: DonaldBurr INTERNET: dburr@ocf.Berkeley.EDU |_Compu$erve:_72540,3071_____________ or: 72540.3071@compuserve.COM | "Send flames to /dev/null."