Your Powerbook is at fault. 10.2.2 for me and many was a complete success. A crashing and corrupted Finder should tell you it's time to run Norton. I know it it ONLY started doing this after the 10.2.2 update, but you can't yet blame 10.2.2 fore complications.
"As for jfpoole, you're lucky.. my update was fine for a few weeks, and then things went into the crapper. Give me news in about two to four weeks to tell me how things are going."
STOP JINXING ME!
I mean, ahem. I updated to 10.2.2 on 11 November 2002 (which was a day or two after it was released), so I'd hope that if I was going to have problems then they should have already started. I'll keep you posted, though.
<BLOCKQUOTE>quote:</font><HR> I don't recomment installing Norton on any machines Mac or PC <HR></BLOCKQUOTE>
I've used Norton (and Disk Warrier) for years and have NEVER had a problem with it scewing things up. In fact Norton 5 & 6 have saved a number of hard drives that had gone wacky and that other utilities couldn't fix (I act as "tech support" for a number of Mac users) What kinds of problems did you experience? I've heard of problems after running Speed Disk, but that was because the user didn't run a full Disk Doctor check of the files and directories first before defragging the corrupt data
There is nothing wrong with the Powerbook - there are lots of problems with 10.2.2 in various areas - we are warning people off it. Just because some situations work okay doesn't mean it will work in others.
Making blanket statements like " your hardware is at fault" contributes nothing to help people.
X is a work in progress and some releases will be better than others for some machines and setups.
Partition your drive, clone your system and install suspect upgrades where they won't do harm and you can easily dump a problem setup.
You are being Beta testers for Apple..not good if you need to get work done without problems.
Automatic software update can be very dangerous to a complex system... firmware updates in particular. We've had clients lose all their sound on one firmware update - Apple eventually replaced the motherboard admitting the probkem but it took 3 months and lots of grief.
The saw "if ain't broke"...applies here big time. Reinstalling X is not like 9.
Sorry to hear your grief with 10.2.2, and Macdoc, thank you for being so forthcoming regarding the problems with that particular update. I downloaded it yesterday and was going to run the update over the weekend. After having read this thread, I think I'll pass for the moment. If it's any consolation, you may be saving others much frustration through sharing your difficulties and advice.
I am sorry, but the OS iteslf is just fine. I have over 15 Xserves installed in the industry with no problems.
They all have the .2 update installed and I have not had a problem outside of having to build a DNS server for those that want to use the password server.
The only major flaw that i have heard of is the Microsoft Intellimoue and some HP Printer drivers.
I had a bad stick of ram installed in my powerbook that went bad over time. Once I got it exchanged have not had a problem on my powerbook.
I also run a bunch of websites off of my 10.2.2 server at my business and have not had a problem with it. I think you have either a bad piece of software installed on your box, or you have a problem with the hardware itself.
Before you blame the 10.2.2 update on your powerpoint, look at what third party software you have installed.
Look in your log files for problems with the system. Watchdog knows all!
Just a few thoughts here on your problems with OSX 2.2.....especially after my own very serious grief with Jaguar.
Try taking out one of your Ram sticks and then see how it runs. Same problems? Then stick it back in and take out the other one. Bad RAM is seriously debilitating for any UNIX-based system. It may work just fine on OS9 or even an earlier version of X, but it will show up eventually. Trust me on this.
This may not be the problem....but at the very least, you will be able to eliminate this variable in your search for a soloution.
UNIX likes RAM. UNIX needs RAM. GOOD RAM. LOT'S of RAM. Bad RAM equals BAD (or buggy) UNIX.
macdoc: What problems are you referring to? Every machine I have installed it on runs flawlessly.
The only things I have heard about are the INtellimouse Driver (which doesn't seem to effect all the different mice, which is wierd) and there was a specific HP driver, I can;t remeber which one.
"The only major flaw that i have heard of is the Microsoft Intellimoue"
I own a Microsoft IntelliMoue hooked up to both my G3 and G4 tower, both running Mac OS X 10.2.2 and have not noticed a single complication yet. What kind of flaw is apparently with this mouse and the 10.2.2 update?
"Try taking out one of your Ram sticks and then see how it runs. Same problems? Then stick it back in and take out the other one. Bad RAM is seriously debilitating for any UNIX-based system. It may work just fine on OS9 or even an earlier version of X, but it will show up eventually. Trust me on this."
I totally agree here. However, what I don't understand, is why would your RAM be all nice with 10.2 and then suddenly fail under the 10.2.2 update?
Hey RTC... computer problems are really frustrating for sure... but I don't think its OS X's "Fault". The majority of times when people have had a major problem with their Mac in OS X has been "defective" ram. Usually the culprits are cheaper ram like generic ram, or even Kingston "Value" ram... the type you find at future shop or Mac dealers who sell on price instead of value and dependability.
I also take a bit of issue with Macdoc's statement that we are being beta-testers for Apple. This may have had some truth to it with 10.0 and even 10.1 to a certain extent. Of course X is a work in progress, every OS is, but I wouldn't go so far as to categorize 10.2 as beta software. Its stability on the 6 different Macs I use running power applications is an absolute joy.