[EMAIL PROTECTED] said: >Give us a break - NOT TRUE. I had a customer with a stubborn -127 disk >error the other day and I simply wiped the drive and restored her from >backed up prefs and all is well again. I do tons of these and have NEVER >had one of those, whaddayoucallem? Extension conflicts? NEVER.
Then you're quite alone. I agree that extension conflicts went way down with OS 9, 9.2.2 especially, but I've seen Base install intermitting conflicts with only Apple extensions in several configurations, usually involving the traditionally buggy Apple Menu Options and and Apple CD/DVD extension. Solutions have involved replacing Apple Menu Options with Behierarchic as well as updating or downgrading the version of Apple CD/DVD extension, depending on which version you had. iTunes 1 and 2 extensions conflicted with Toast Firewire extensions such as the drive was invisible to Toast, rendering CD Firewire Toasting impossible, unless you turned off all iTunes stuff except CD/DVD. This as late as in 9.1. There are plenty more of extension conflicts I could mention, mostly involving third party extensions of course, but too often also Apples own even with each other. If we go back to OS 8, I probably rebooted 1000+ times in order to identify what extension caused problems, something that for some reason have been too intermittent usually in OS 9 to be effective. >And I do >little tinkering except to customize the machine for the person's way of >getting email etc. A fresh base install of the iBook Mac OS 9.04 will default to unpack browserdownloaded stuffit files with dropstuff instead of expander, which 9 out of 10 times will make an archive of a archive. Hardly what you expect if you download a file. I've seen this in no less than 10 blue FW iBooks on several occasions. This could be related to the swedish version. I haven't seen it with other Mac OS versions. The location manager of 9.1 can intermittantly refuse to accept a configuration in one control panel as not being default, even if a second configuration have been added (You need 2 in order for LM to work). The solution was to add a third configuration in Contro Panels that wouldn't "take". I reported this bug to Apple myself, but as far as I know they have been ignoring it. maybe it was too intermittant. Personally at least, on all Mac OS 9 apps I've used, I've had recurring problems of files, usually foreign, not being able to open when doubleclicked in the correct application even as it had been set in File Exchange and in Internet Preferences. Also, I can't choose an app. Actually, generally this behaviour is even worse in OS X. Apple is doing too little for problems like this. As I recall it used to work fine in 8.6. On the other hand Mac OS 8.6 on Powerbook G3 had sudden type 10 error within 10 minutes of booting unless you *added* some third party extensions. I'm glad something stopped those errors, as they were quite embarrasing. I don't know if this was widespread problem, but it was on brand new machine and hardware problems seemed unlikely as adding extensions stopped the behavior. You want me to get into sudden Finder quits? Not all froze the computer but many did. They used to be very common pre 9.1. Type error 1 or 2? Bus errors? Type 11 error in earlier OS versions, that now are routed to other error numbers? Macfixit even used to have a special type 11 article for a while. There are plenty of recurring errors like these in different versions of Mac OS. Lately in 9.2.2 I have had a type 10 error once in a while, seemingly for no good reason. But as it happens after several days of use, I think it's a memory related issue. Can't be bothered though. You want me to get into OMS? No, I don't have the time to list all problems there. Though, to it's defence, it worked very well when it worked. As in many other cases it took a lot of tinkering though. Basically, I haven't seen a Mac with 10+ commercial apps, that didn't need to be went through for a week or so until it was stable enough to be used in a production environment. This did change in a noticeable way with 9.1 and 9.2.2, but don't forget the history (like 9.2.1). I've taken great pride in delivering stable systems for my customers over the years. One week uptime have been my minimum criteria. But that doesn't mean that Mac OS have been the epithome of stability. I've had graphical designers switch to NT, commenting on how much more stable that was, running for months without crashing (this in 98-99). There were reasons for those comments. Adobe Premiere wouldn't work properly with Mac OS 9.0 on the first iMac DV back in 89. Adobe blamed Apple. Apple blamed Adobe. Gee, thanks guys. Thing is, it DID WORK with Mac OS 8.6, but Apple refused to deliver such a thing as their wonderful OS 9 now as available with iMac DV. We told them it didn't work for us and they said it was not their fault. Gee, that really helped. In the end, an insider connection got me a UK 8.6 version for iMac DV (it had to be for that as usual 8.6 versions didn't work). I could write you 10 000 lines of stories of Mac OS problems, but I'll stop here as I have work to do. All of this said, I'm not claiming the problems I mention above all are universal, but they were very real. Mostly, they could be solved, but not always. There are thousands of other stories on places like Macfixit, that I'm sure a few of you at last have followed parts of. The history of OS X is somewhat similar to OS 9, with early versions full of strange bugs. I still maintain that 10.2.x solve most of these problems as well as speeding up, while a few bugs still hang around and need to be solved. Some of these are vital for some people to be able to use their fav apps, but that is not something new. As far as I'm concerned 10.2 is the first really usable version of OS X for common people. No whining in the world will change that. Thank you for reading this far Micke Bystrom Project Manager Web & Idea Developer ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
