Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!bc From: bc@Apple.COM (bill coderre) Newsgroups: comp.sys.mac.misc Subject: Re: mminit? Message-ID: <53526@apple.Apple.COM> Date: 31 May 91 14:32:05 GMT References: <0D010010.1ggqgc@brain.UUCP> Organization: Apple Computer Inc., Cupertino, CA Lines: 41 I wrote: |> Party Line is to trash it, and get the right fixes in System 7. Chuck Shotton replies: |Suppose, heaven forbid, someone doesn't want to run System 7? Is Apple going |to "fix" MMInit so poor, misguided System 6 users can have a fix to the fix |for buggy ROM code? First, try to understand the problem: The bugs in question do not cause crashes, but only slow pointer allocations down under certain obscure circumstances. I think Prograph was the only program known to cause this problem to manifest. The average user would never run into this bug, and therefore would not benefit from the fixes. (It's not like your Mac would run 20% faster.) MMInit also eats a lot of system heap (over 5k), and god forbid another init conflicted with it! When The-Corporate-Entity-Apple weighed the issue, they saw that the benefits to users were practically non-existant, so MMInit has never been officially released. Some hacker leaked it to the net a few months back, and it's probably floating around somewhere. Similar corrections are in System 7.0, if you should want to run that. They've been extensively tested there, with a wide variety of programs. You might also start a movement to get the functionality incorporated into the forthcoming system 6.0.8. I tried the patch, and it didn't make any difference, even with my most memory-flogging apps (Lisp and a multi-dimensional spreadsheet I support). I therefore removed the patch from 6.0.7, and left it at that. Obviously, you should decide for yourself if you want to run it, and test it out carefully before using it. (Also, make sure it isn't a virus in disguise!) But the party line is still NOT to use it, because it almost certainly won't make your mac faster or crash less often, and because who needs another init eating your memory? bill coderre just trying to help you understand