Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!mips!apple!keith From: keith@Apple.COM (Keith Rollin) Newsgroups: comp.sys.mac.system Subject: Re: Another thing lost in 7 Message-ID: <53553@apple.Apple.COM> Date: 1 Jun 91 02:24:27 GMT References: <13789@goofy.Apple.COM> <1991May31.183151.20329@m.cs.uiuc.edu> Organization: Apple Computer Inc., Cupertino, CA Lines: 74 In article <1991May31.183151.20329@m.cs.uiuc.edu> gillies@m.cs.uiuc.edu (Don Gillies) writes: > > (2) Command-option-E is used to eject a disk. It's just plain > slow and stupid to ask the user to select the disk. > If I have to select the disk with the mouse, it only > takes half a second to drop it on the trash. > > my conclusion -- The quick-eject features has been REMOVED. I hardly ever used Cmd-Opt-E under System 6.0.x (or, now, Cmd-Y under System 7.0) because I always just drag the volume to the trash. But, in either case, don't you have to select the volume you want to eject? In your statement, you imply that you don't have to select a volume in order to eject it with Cmd-Opt-E. If that's so, then how do you specify which volume to unmount? Does Cmd-Opt-E eject _all_ unmountable volumes? > (3) The ability to zap the PRAM is now restricted to people > with 4 fingers and two hands. *I* have two hands and at least 4 fingers. How many do you have? I realize that there are handicapped individuals out there who may not have two hands, but ... see below. > Zapping the PRAM > and rebooting with all your inits MAY BE a 2-boot > (I don't know, haven't tried it yet). This is a > great loss in convenience. If your PRAM is smashed, > preventing you from booting your hard disk, you must > do a 7.0 FLOPPY BOOT, then a Hard Disk boot. This statement intrigues me. You can consider me to be a person likely to get into the situation you describe. For over three years, I worked in Mac DTS where I was required to try to get my Macintosh to do incredible things. Either I'd be exploring some interesting trick on my own, or I'd have to figure out something obscure for a developer. Writing INITs, DAs, drivers, CDEVs, applications ... all of these were part of my job. All of this was done on a base of dubious nature. I was one of the internal testers for the Mac IIfx. I'm always using the latest internal versions of System Software. I'm always shaking out bugs in the latest versions of MPW. On a good day, I'd have to reboot my Mac only a 1/2 dozen times or so. Seems to me that if _anyone_ is going to smash their parameter RAM, then I would. BUT I NEVER HAVE!!! The only time I've even ever seen parameter RAM corrupted was when the Mac II was introduced, and there was a system bug that would corrupt it. So ... are people really still corrupting parameter RAM. HOW??? What are you running that gets you into this situation? > This is > outrageously moronic! I can't believe Apple let this > slide into system 7.0. They shouldn't even document > it, it's that stupid. Perhaps they're trying to make > a new market for $25 "PRAM zero" DA's. My guess is that the experiences of most people within Apple is much like my own. Even with the volitile situation of my Mac when I worked in DTS, the situation of the System Software engineers would be even worse. My guess is that they never had to zap PRAM, and so didn't see the need to make the feature simple to access. The above comment should be taken with a grain of salt. I don't know what the procedure is for zapping PRAM, so I don't know if it is indeed difficult or easy. -- ------------------------------------------------------------------------------ Keith Rollin --- Apple Computer, Inc. INTERNET: keith@apple.com UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith "But where the senses fail us, reason must step in." - Galileo