What is Digg?Sponsored by Travelzoo
Take Advantage of Ridiculously Low Holiday Airfares view!
travelzoo.com - Flights $52 and up for Thanksgiving, Christmas & New Year. But move on it now.
461 Comments
- RVSTY, on 10/30/2007, -23/+153It's a feature
- inactive, on 10/29/2007, -42/+171Pics or it didn't happen!
- agimat, on 10/30/2007, -20/+133Who's copying who again?
- La9os, on 10/29/2007, -29/+132KARMA
- IVIrMP3, on 10/30/2007, -35/+116But I those tv ads said Macs were flawless?!
- duncandog, on 10/29/2007, -5/+75Happened to me. Right after Leopard finished installing - system restarted and then after the apple logo - just a blue screen. I took my G5 imac into the apple store and they had to use their connection to access my machine and reformat a clean install. Now works well (after a 3 hour journey to the Apple store). There was another guy who came in with the same problem with his imac.
- chugger1992, on 10/29/2007, -37/+104Typical Mac users.
______
"That worked just fine. Despite this small hiccup, it's far better than any Windows upgrade I've suffered through."
______
>>>oh really? how bout these steps listed farther below?
______
Reboot into single-user mode (hold Command-S while booting)
Remove the following files by typing each line below:
rm -rf /Library/Preference Panes/Application Enhancer.prefpane
rm -rf /Library/Frameworks/Application Enhancer.framework
rm -rf /System/Library/SystemConfiguration/Application Enhancer.bundle
rm -rf /Library/Preferences/com.unsanity.ape.plist
Exit, to continue booting normally, type:
exit
_____
IIRC (and I most definitely do), "Windoze" upgrades are much less painful. - inactive, on 10/30/2007, -7/+65It happens. It happened to me, except instead of bitching about it and doing nothing, I did a little investigation and it turns out to be due, in my case, to one of two things:
1. the account in question had Filevault turned on, and Leopard couldn't read it.
2. the account in question ran a craptacular third party software which was in no way tolerant of Leopard, despite the fact that its developers had far more than enough time to fix it before Leopard was released.
I blew away the filevault stuff, and followed the instructions below:
1. Reboot into single-user mode (hold Cmd-S while booting machine)
2. Follow the directions OSX gives you when you get to the prompt (I
think these were them - just type the two commands it tells you to):
fsck -fy /
/sbin/mount -uw /
3. Remove the following files:
rm -rf /Library/PreferencePanes/ApplicationEnhancer.prefpane
rm -rf /Library/Frameworks/ApplicationEnhancer.framework
rm -rf /System/Library/SystemConfiguration/ApplicationEnhancer.bundle
rm -f /Library/Preferences/com.unsanity.ape.plist
4. Exit, to continue booting normally
exit
And now it works fine. - Vicujozobenaxod, on 10/29/2007, -42/+94Guess they should edit that little quip from the smug Mac guy in the commercials.
- dalesmatrix, on 10/30/2007, -4/+45I don't think it's FUD about APE...booting in single user mode and deleting those files certainly let me get past the blue screen. So it would seem in some cases it is the cause. After the upgrade install though my user account was no longer an admin which was a pain, had to do a password reset via booting from the DVD.
- monkeyrun, on 10/29/2007, -4/+36unsanity writes some pretty hardcore OS X apps, APE digs deep into OS X, so it's no surprise that it would crash a new OS release.
They should be responsible for writing an upgrade for APE, or at least warn users about possible conflicts. - louiedog, on 10/28/2007, -2/+32And in Windows the BSOD is caused by buggy drivers and screwed up hardware.
- tico24, on 10/29/2007, -6/+36Its clearly not all 8char passwords though. I use a 10 char alphanumeric password and the leopard upgrade went through fine.
- klaupacius, on 10/29/2007, -3/+32301 new features.
- Sornos, on 10/29/2007, -7/+34The Irony.
It is delicious. You must try it. - sickanimations, on 10/29/2007, -1/+26How delicious after that Windows Server easter egg.... *licks lips* Tastes like.... irony.
- gravedigg, on 10/29/2007, -7/+31Everything I know is WRONG!
- Pic0, on 10/29/2007, -22/+46no blue screens in XP for years, maybe Apple stole them?
now they will claim innovation so that apple users know what happened when their computer crashes, instead of just rebooting. - wilf_brim, on 10/29/2007, -27/+50First, I am really, really enjoying this. OMG, a problem with an Apple OS? How can this be? Hey, hot flash. There are problems with every new OS. Microsoft has the largest install base, so their problems appear worse. No new OS is going to work perfectly out of the box for every user. Second, gotta agree that ANY OS shouldn't be "upgraded". Clean re-install. Yes, it's a pain to reinstall the apps and data, but in the end it's less of a headache than all the wonkiness that comes with an OS that isn't quite firing on all cylinders.
- bullsfan03, on 10/29/2007, -11/+33glad I'm waiting for ***** like this to clear up before upgrading ;)
- inactive, on 10/30/2007, -23/+44Apple - It Just Works!
- ilgaz, on 10/29/2007, -7/+28There are more details coming up. It has something to do with the accounts created back in 10.2.x days. The password hash method was different. So in fact, if you only change your password one time on 10.3.x+ or even put the same password, it won't happen.
- TheFinaleofSeem, on 10/30/2007, -7/+25APE has always been a buggy piece of crap that ***** with the system in ways that it shouldn't.
- Kazrog, on 10/30/2007, -13/+31Buried as inaccurate. This is the result of people leaving an old version of APE installed. By the way, the Unsanity folks are fully aware of this and emailed everyone letting them know to upgrade APE or remove it before installing Leopard.
http://unsanity.com/products/compatibility/ - TheFinaleofSeem, on 10/29/2007, -12/+29And have him warn people to not install ***** software like APE, which was buggy and screwed up systems prior to Leopard.
- inactive, on 10/29/2007, -6/+23First you diss apple, then you promote a windows site...
Are you trying to set a new record for most digg downs in a one hour span, or something? - otomo, on 10/29/2007, -12/+28This is only if you installed a third party application. For example, if you replaced explorer.exe in your windows install and expected an upgrade to work flawlessly.
I am anything but typical I suppose though, not installing third party tools that use private interfaces to the os and expecting upgrades to go by without a hitch. Erase and install is always my preferred method. - radmarshallb, on 10/28/2007, -2/+17APE is not just an application. It messes with system files pretty significantly.
- f4nt0m4s, on 10/29/2007, -7/+22"hi, i'm a PC"
"and i'm a Ma... *crash*" - mozzep, on 10/29/2007, -5/+19amen for clean installs and restoring all information on your computer.
- NSResponder, on 10/29/2007, -2/+16I don't buy it. My password is rather longer than that, and APE has a known track record of causing instability.
-jcr - autoy, on 10/30/2007, -14/+28This seems to be caused by the - unfortunately - well known crapware (yes, there is a little of these in OS X too) Application Enhancer. Whoever installed that ***** deserves BSOD and a slap on their face. You can stop the FUD now.
- RoamShell, on 10/29/2007, -1/+15I'm really surprised it didn't this time around. It's the same hardware in every machine. How hard can it be compared to having to support hundreds if not THOUSANDS of different hardware on Windows and Linux/Unix distros?
- edlowe0, on 10/29/2007, -22/+36BHAHAHA
- RoamShell, on 10/28/2007, -3/+17***** up hardware isn't windows' fault, it's the manufacturer's (or the consumers if not buying a prebuilt), but I agree on the drivers part. I thankfully have never had a BSOD on XP. Ever.
I've had a kernel panic or two on Puma & Panther, not sure what caused them either, but after a restart everything was okay.
Haven't had any problems with Ubuntu so far, except general nomenclature issues. But I gotta give it to them, it is improving. - djjuice, on 10/29/2007, -1/+14I did have this problem, but as most article states, once removing application enhancer everything was well. I even was crashing at shutdown.
- inactive, on 10/29/2007, -0/+13It was Application Enhancer. Poetically, I installed it and never actually used it for anything as it didn't seem necessary in the first place.
- digitalarcanum, on 10/29/2007, -0/+13CAKE IS A LIE.
- gamersedge, on 10/28/2007, -4/+16Up 6 hours ftw, i didnt have this problem because i had nothing i wanted to keep on my new machine with an upgrade drop-in disc, so i just said ***** it, wipe everything because i had an external backup.
- inactive, on 10/29/2007, -0/+11Forgot one thing---I've talked to the nice people over at TekServe here in NYC (a giant mom-and-pop Apple store, predating actual Apple stores by quite a while), and they're reporting the App Enhancer problem right and left. Looks like that's probably the most likely candidate for most.
- Cl1mh4224rd, on 10/28/2007, -0/+11louiedog's comment was a counter-point to TheFinaleofSeem's comment that Leopard's BSoD is caused by third-party vendors. More often than not, it's the same thing in Windows.
Most people don't get it though, because the hate is so strong. - ZachPruckowski, on 10/29/2007, -5/+15So you can frack Windows up anyway you want and updates will be flawless? Basically, the instructions consist of "remove a very risky, unsupported application you shouldn't have installed in the first place".
- 2Deluxe, on 10/29/2007, -1/+11I logged in purely to Digg you up.
- RoamShell, on 10/29/2007, -2/+12"This isn't a hardware issue, it's an issue with Application Enhancer, a third-party product. Again, it's NOT a hardware issue."
It better not be, considering how little hardware they have to support. - seventoes, on 10/29/2007, -4/+14Stop with your ***** ads. We hate your life.
- xXMetalJesusXx, on 10/30/2007, -1/+11Deleting the app and preference files for Unsanity's ClearDock makes the Blue Screen go away....hmmmmmm
- EricVKX, on 10/29/2007, -2/+11I got one of these too after I tried a straight 10.5 upgrade from 10.4.10. I restarted, and did an archive and install instead. Now everything works just fine.
- inactive, on 10/28/2007, -5/+14Mac attack.
- Bob042, on 10/30/2007, -9/+18Upgrade worked perfectly for me. Seems like this is a problem with APE, which does mess around with the OS quite a bit and isn't properly ready for Leopard.
A blue screen from OS X is certainly ironic enough though. - HerrEisenheim, on 10/29/2007, -1/+9Didn't run into this per-se, but Leopard is kind of buggy. What they needed was a PUBLIC beta to sort this kind of stuff out ahead of time. I've run into a few issues.
1) Flip4Mac will not allow you to register with a clean install unless you use the Flip4Mac Beta. Problem with a missing eSellerate engine.
2) Pixen 3.0 does not workâat all. You must use 3.1b.
3) A lot of icons for 3rd party apps are low resolution in Coverflow view.
4) Repair Permissions (Disk Utility) takes FOREVER (5 to 20 minutes, depending on system), and returns an error about ARDagent.app.
5) Since AIImageViewWithImagePicker is disabled (or non-existent) on 10.5, applications which used it (ie. Adium), now have that functionality disabled.
6) You must make SURE that you tell Time Machine to omit the directory for a VM using VMWare Fusion and Windows Vista. If you have a Windows Vista VM running while Time Machine attempts to backup, it will freeze both the machine and the backup procedure, and may corrupt your entire VM.
7) Verify Disk (Disk Utility) also takes forever.
8) For some reason, holding down "C" at startup to boot do a CD does NOT work with an Intel Core Duo iMac (Gen. 1) and the new wired Apple Keyboard.
Those are the issues I've run into in the past 36hrs or so. -
Show 51 - 100 of 462 discussions
© Digg Inc. 2009
— Content created and posted by Digg users is