Benches MacBooks

13

dead hard drive and "don't steal mac os" …

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

it's a 13" macbook pro, not some windows netbook.

did updating snow leopard kill my computer?

13 replies

Sign in or join Beachball Help to reply.

  1. 0

    sdschramm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I don't know about everyone else, but i've never seen a "don't steal OS X" error message?

    Please take a picture!

  2. 0

    sig

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I think you need to be more descriptive and specific of the issue. Your post is to vague.

  3. 0

    bound4cupertino

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    About a month ago I finally got around to installing Snow Leopard, but when it would restart to load the install, the backlight on the screen would turn off so you couldn't see to click anything, and it would just sit there doing nothing. Resetting the PRAM twice fixed that problem.

    Then a couple of days ago, I got a kernel panic. Just one. But since I've always had my dad to be my own, personal technical support, I didn't know what it was. Mac OS started acting glitchy the day after that-- Safari wouldn't respond with only one tab open, no video or anything, the trash wouldn't empty, and the Finder froze. So, I decided to try updating Mac OS, which of course was a bad idea. The update did not install, and when I restarted my computer, it did move past the gray Apple start-up screen.

    I tried resetting the PRAM a few times. Nothing.

    I reset the SMC or whatever. Nothing.

    In verbose mode, I got this error: proc 35: load code signature error 4 for file 'configd' and there was some "don't steal mac os" error

    We finally got it to boot from the Snow Leopard disk, and disk utility found some issue and said it couldn't be fixed and that we had to reformat, which didn't work either. But when booted from the install DVD that came with the machine, it couldn't detect a problem with the hard drive, but Mac OS still would not install.

    So, now I have a laptop with a completely blank hard drive. I'll take it to an Apple store this weekend. I just want to know if the software update had anything to do with it.

  4. 0

    red_menace

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Did you have any haxies installed when updating? Were some of the core components (Finder, Dock, etc) modified? Snow Leopard changed some of the underlying frameworks, so updating with third party modifications installed can cause issues.

    There is an older article about the message at
    http://osxbook.com/book/bonus/chapter7/binaryprotection/

  5. 0

    bound4cupertino

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    no hacks or third-party apps. but thanks, i'll take a look at that article.

  6. 0

    sig

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    "... I just want to know if the software update had anything to do with it."

    I doubt it. Your description is still sketchy. You may have directory problems that DU cannot fix and/or a hard drive problem. Let the genius at the Apple store check it out.

  7. 0

    Rod Hagen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi bound4cupertino,

    Never, ever, ever try to "fix" an existing serious problem of this kind by installing an OS update. It sounds to me as if your HD and operating system were suffering from serious corruption before you tried the SL install. Installing an update in such situations almost invariably leads to even greater problems.

    Instead work through the "regular" troubleshooting processes and make sure things are running fine BEFORE every or any OS update.

    Before any update boot up from your OS DVD and run Disk Utility from its "Utility" menu or options. get it to "Repair Disk" (most important) on your HD and then to "Repair Permissions" (less important usually, but sometimes matters).

    If Disk Utility can't undertake the repairs before an installation then you need to either get a more capable "third party" utility, like Alsoft's "Disk Warrior". If even that won;t fix the problem, then you may need to either an "archive and Install" or "clean install" of your operating system after backing up what you can (and, if you have to do a a clean install, wiping the disc by repartitioning and reformatting.)

    But never, ever, try to "fix" a serious problem like this by simply trying to "upgrade" or "update" the OS installation over the top of an already clearly defective one!

    Cheers

    Rod

  8. 0

    A Yilmaz

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Mate any chance your running snow leopard server? Incorrect activation will cause it to say this. The other thing you can try is deleting the .kext file that activates this. I don't know if this will be of any use however it is worth a try.

    If you cannot boot into OS X, start your Mac in Target Disk mode (Holding T at startup) and open your Mac's internal drive from another mac via FireWire. Then navigate to, /System/Library/Extentions

    There will be a .kext file in there called Dont Steal Mac OS X.kext. Try deleting that and restart your Mac normally.

    Just a suggestion. I stumbled upon it years ago and have been wondering what it is for considering that no server OS X doesn't need any form of activation whatsoever!

  9. 0

    TildeBee

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    bound --

    You're getting great advice here.

    Hang in there.

    I have seen that message, and it's on most console logs . . .

    I never seen an error with it, but I've seen notations of its existence often.

    It's put on there by Apple.

  10. 0

    A Yilmaz

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Actually, now that I have had time to read the question throughly, I am assuming this is the same issue I have. Only mine seems a little less serious because the machine will run perfectly following a restart.

    My MacBook Pro has been running SL since the original release (10.6) and has had the small hiccups that all operating systems have and the updates have fixed these issues. However the latest 10.6.2 update has added an issue rather than removing it! Since the update, and I am crystal clear that it is the moment after 10.6.2 because I use my Mac for school everyday, I have had to do an average of 15 restarts due to random freezes during the course of a 6 hour day. Get this. It's not because of graphics intensive programs being used because, I only use the OS X side for internet and word processing. In fact, I have two other partitions, a 10.4.11 partition and a Vista Ultimate partition on which AutoCad Inventor (graphics intensive) runs without any dramas. NONE of which freeze. I am positive that the issue here lies with 10.6.2 because a MacBook hard disk on 10.6.1 will run fine on the Pro when in target disk mode. So my suggestion here is mate, put in your install disk, do an archive-reinstall, and just copy your files back to the new system. AND DO NOT DO ANY COMBO UPDATES UNTIL AT LEAST 10.6.3. Sorry I just thought I had to put that caps to make myself clear. 🙂

  11. 0

    sdschramm

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    bound4cupertino wrote:

    it's a 13" macbook pro, not some windows netbook.

    did updating snow leopard kill my computer?

    I bet you ARE trying to install OS X on a windows netbook!

    http://www.cs.virginia.edu/~wh5a/blog/Don%27t%20Steal%20Mac%20OS%20X.html

  12. 0

    bound4cupertino

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks everyone. Yeah, my biggest mistake is that I didn't realize it was a serious problem until it was too late. My dad took over at that point and did all kinds of stuff. He ended up trying to reformat the hard drive, but it didn't work. And Mac OS would not load on the wiped drive. There isn't an Apple store close by, which is why he fooled around with it for so long. But I will be taking it to one or shipping it out in the next couple of days. I'm a college student. This is the first time anything like this has happened. Well, I've had a hard drive die, but it wasn't quite so weird. I know that Apple has great customer service. More than anything, I was just confused. Thanks again.

  13. 0

    Rod Hagen

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You might want to try "zeroing" the drive, rather than just "formatting" it, bound4cupertino, if you have not done so already. From your description, though, it is quite possible that a drive hardware issue is involved, in which case simply replacing it may be the easiest course.

    Cheers

    Rod