Slashdot Mirror
Leopard Upgraders Getting "Blue Screen of Death"
Z80xxc! writes "Some Mac users upgrading to Apple's new Leopard operating system are encountering long delays on reboot — an experience they liken to the Windows 'Blue Screen of Death.' While some of those upgrading were able to access their computer after waiting for as long as several hours, others were forced to do a complete reinstall. Some suspect that a framework called 'Application Enhancer' by Unsanity LLC may be causing the problem, but there has been no official word from Apple at this point."
people are so fucking stupid
"oh no this 3rd party application which adds dubious and useless enhancements to my system is causing my computer to not work upon upgrading to a completely new version!"
bust out the slashdot article I guess
I had used Application Enhancer for a while, but Photoshop became very crash-prone; a friend reported Safari crashes after installing it. I wouldn't suggest it to anyone.
Also, rule of thumb: 100% clean installs are always the safe way to go. Back up your stuff, wipe the HD, then restore as needed.
Circumcision is child abuse.
Yep, and it would be tagged as "defectivebydesign" and "haha". You know, MS is a near-monopoly so their products do deserve a good deal of good old unfair bashing...
Just remember, if windows got taken down by a third party app, not only would you be screaming and shouting...
Not under circumstances like this, we wouldn't. Some of Unsanity's programs are pretty invasive little things that fuck around with the OS in ways that Apple doesn't support. From their site:
So yeah, if you have even a vague understanding of what this product does, it shouldn't be any surprise that it could cause problems if you threw it on a new/unknown version of the operating system. This isn't just a "3rd party application". It's not like if Windows crashed when you installed Firefox (which Microsoft would get criticized for), but more like if Windows crashed when you tried to use an obscure and invasive 3rd party WindowsXP hack on Windows Vista (which Microsoft would not get criticized for).
And it's not even clear that OSX itself crashed (as in a kernel panic). For as few details are available, it could just be that Finder or the installer crashed, which wouldn't be surprising if APE is screwing around with those applications' memory space.
I was worried when I first saw it until I found that it was a 3rd party app causing the issue. The summary would lead me to believe it was a defect in Leopard. It would be nice to mention it's a 3rd party issue and not Apple's fault in the summary.
But if it is APE then well then that's kinda understandable its the singlemost invasive kernel mod of all.
APE is not a kernel mod. It runs entirely in user mode.
Too bad Apple doesn't talk up safe booting more so people will know it is there.
Too bad Apple doesn't do the user-friendly thing, which is to offer users "safe mode" when the previous boot failed. That's what both Linux and Windows do, and it's the right thing to do (well, even better would be detecting and disabling broken extensions, but I guess that's too hard for any of them).
Like most problems of society, drug use is not likely the cause of the above errant moderation.
I get mod points quite often and I've fucked up applying them a few times. Each time it was related to the fact that the current UI for moderating is drop down menu (which is just fine) that applies whatever moderation is selected immediately upon being clicked (no fine). This would be halfway fine if there were some means to un-mod a post, or at least re-mod it, but there is not.If my mouse pointer is off slightly when I click an item in the list I'll have applied the wrong moderation and can do nothing about it.
This is obviously dumb. I don't want to be bothered like I'm using Windows, but some things involving user selections on a computer need either a confirmation step that is distinct from the selection or have a Back button.
"Sacrifice for the good of The State" - The State
I've noticed that is the latest groupthink to make the rounds. it's a statement about as useful as "i know I'll get modded down for this..." which inevitably gets modded up.
There are a lot of people on slashdot (and I guess in the world in general) who seem to enjoy being the victim of some massive conspiracy, rather than perhaps recognizing that when lots of people disagree with them it really is just a lot of people thinking they're wrong.
Recursive: Adj. See Recursive.
no, it's reflective of the fact that Apple doesn't provide any APIs for accomplishing those tasks. It's no different than patching explorer.exe while it's running so that the File menu suddenly does something completely different -- basically guaranteed to cause problems with something, because you're not supposed to do it and no programmer expects it to happen. But I'm sure the code that MS programmers work on is reasonably modular and accepting of changes to the File menu without breaking anything else.
Recursive: Adj. See Recursive.
And it is still a terrible idea. You can make very few safe assumptions about the target process. You don't know the state of the heap, so you have to use your own heap for that thread. You don't know the base address for DLLs, so you have to use only kernel32.dll functions (and that is luck that it always loads at the same base address for every process).
But the absolute worst part about CreateRemoteThread() isn't the fact that it does what it says. It is the simple fact that you need to actually inject your thread function into the target process. That is, you need to copy the assembly necessary to run your thread into the target process. WriteProcessMemory() is an API call that will get you flagged as malware by a lot of AV utilities, but is necessary to use CreateRemoteThread().
No, verbose boot just causes the graphics to be delayed until loginwindow is run. It does not affect "safe boot" in any way.
One of the first things I do on setting up a new Mac is to change the boot-args nvram variable to be verbose. Not only is it informative if there's a problem, but I find the scrolling text messages to be comforting in their obscurity.
Unsanity warns you that they are making deep modifications to the user interface and patching applications dynamically when they are loaded. They are not "just apps", they are not even like Parallels which does come with a kernel extension... because it runs as a regular application otherwise. Not to mention that Apple considers Parallels a key player, but has a definite problem with Unsanity.
I'm not saying that people who are having this problem are morons, but I don't think they should be so quick to blame Apple for this... unless you're suggesting that Apple actively broke APE or something?
My car 'just works'
Even with regular maintenance, I still get unexpected interruptions of service now and then.
Nothing technically 'just works' all the time if you want to bitch and moan about all the corner cases where it can break, but there are things designed to work with very little fuss, for a reasonably long time.
Point is, 'just works' doesn't have anything to do with occasional bugs, but describes how something was designed/is intended to happen, and the reliability to work as intended. That's where Mac OS X, and my car wins the title. For the most part, they work very simply, as intended.
Apple's not a monopoly. If you have all Apple products, that's your choice. You can use an Apple computer with Linux or Windows (though I don't see why), a Logitech mouse and keyboard, a Dell monitor, a Linksys router, GMail, an RCA mp3 player, and purchase music elsewhere. You use Apple by choice, and they don't have a very large market share in much other than the iPod/iTunes area. Though I can't see why anyone would use an Apple monitor; you can get the same monitor for 1/3 of the price from a different company...
OTOH, you'd be hard pressed to find a computer in a business (other than Apple's stores) or the home of an Aunt Tillie that doesn't have Microsoft Windows.
<sig> </sig>
If things go wrong sometimes, then I would say that "it just works" isn't all that true. I don't use Apple stuff, but I still have a pretty good impression of their integration/user experience work.
I just started getting into Apple stuff with the release of the G4 Mac Mini. I then subsequently got a Mac Pro to replace my main machine which was running Linux. I decided to give OS X a fair chance to see if really was better than Linux.
In my experience "it just works" is far from accurate. It's definitely a slick environment and worth using, but comes with enough issues that it doesn't live up to the hype. But I guess its a mistake to listen to the hype (Apple's products fell far short of my expectations due to hype).
The problem, as with any commercial vendor, is that you are often stuck waiting for the company to fix things. For example, iLife apps crash. They crash a *LOT*. What can you possibly do other than wait for them to fix the bugs? OS X itself is usually pretty solid. Occasional something just won't work right. Sometimes I actually have to REBOOT to fix things. This is just not what I expect from an OS based on UNIX. I suspect (partially from experience) that they just haven't gotten it together after the Intel switch.
Apple's products have just as many problems as any other OS vendor. They may be different problems, but don't believe anyone who says they don't exist. And Apple is a company that is constantly changing things (OS9 -> OSX, PowerPC -> Intel, frequent OS updates), so you can't possibly expect stability from them. Having control over the hardware apparently still isn't enough to achieve this.
#!/
Maybe the only reason people would install a "hacky" piece of software is because Apple makes it so dang hard to customize your personal workspace. People are different, not homogenous.
Note to the apple modders -- I have a bunch of apple hardware, and not a bit windows stuff -- I'm speaking from experience, not as a troll.
What changed under Obama? Nothing Good
On Windows it can get somewhat more complicated, because
1) the registry entries may be spread over various sections of the registry. Offhand, I can recall
-HKEY_LOCAL_MACHINE\SOFTWARE
-HKEY_CURRENT_USER\Software
-HKEY_CLASSES_ROOT (have fun searching through that)
2) fishing out the DLLS may require an extra tool like Dependency Walker (URL:http://www.dependencywalker.com/). Easy enough if you know such a tool, but it may be somewhat beyond a newbie.
C - the footgun of programming languages