Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!mentor.cc.purdue.edu!pur-ee!pur-phy!maxwell.physics.purdue.edu!sho From: sho@maxwell.physics.purdue.edu (Sho Kuwamoto) Newsgroups: comp.sys.mac.programmer Subject: Re: Communications Toolbox questions Message-ID: <2869@pur-phy> Date: 9 Dec 89 04:12:31 GMT References: <9125@hoptoad.uucp> <36869@apple.Apple.COM> <9194@hoptoad.uucp> <37030@apple.Apple.COM> <9222@hoptoad.uucp> Sender: news@pur-phy Reply-To: sho@maxwell.physics.purdue.edu.UUCP (Sho Kuwamoto) Organization: Purdue Univ. Physics Dept., W. Lafayette, IN Lines: 27 In article <9222@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes: >In any case, RAM is not the only problem with putting it in the System >file. System files are already too big; fetching resources from them >can take seconds under some common circumstances, like having a lot of >fonts installed. I think we've all seen DAs like Chooser (no >Appletalk) and Control Panel take forever to come up, and these are >only the most visible occurrences. What does the Control Panel have to load in from the System file? As a DA, it doesn't seem that much more complicated than other DA's, although I suppose it may be much bigger than I thought. I figured the bulk of its work was to look through the system folder to pick out the cdevs. Same thing with the Chooser. I assumed it spent most of its startup time figuring out which printers were connected, not pulling out resources from the system file. I do agree, though. The system file is way too big. What to do? I don't know. Starting with a ROM that needs less patching is a start, maybe putting some more resources in ROM would help. I'm sure everyone's had their fill of the "put the fonts in a folder, not the system file" whining. I shudder to think how big a 7.0 system file is going to be, even without a lot of fonts. The outline fonts will help reduce the space, but I'm begnning to wonder if it's going to fit on one disk... -Sho -- sho@physics.purdue.edu <<-- time to buy a bigger hard disk.