Q: OS X Lion freezes at login screen + App Store is slow

Gabriela: Sounds good. (calling Apple Support). Hope you will let us know what happens.

Hi Terry,

I applied the fix to my mid 2010 MBP, but received a warning that I was using an invalid kext file. Is this normal when applying this fix?

Hi Bradford: "invalid kext file" is definitely not normal. I would try and verify that all steps completed OK. But did "the fix" work - in spite of the "warning"?

Bradford:

If you edited the plist file with textwrangler, go back and double check that the structure looks ok.

plist files are  text files with a given structure.

For examplle, the area you need to edit starts with <key>MacBookPro6,2</key>

Then under that, is <dict>, etc

1) Make sure that if you changed a value, you didn't accidentally drop a character:

  <integer>4/integer>    <- Wrong

   <integer>4</integer>   <-Right

2) there was one tricky value - Terry I believe reported that the P3HistoryLength needs to come out.

This is tricky because in my opinion, this is the one section of the file that isn't nested the way you'd expect;

The original section shows:

  <key>ID</key>

                                                            <integer>0</integer>

                                                            <key>IdleInterval</key>

                                                            <integer>100</integer>

<key>P3HistoryLength</key>

                                                            <integer>2</integer>

                                                            <key>SensorOption</key>

                                                            <integer>1</integer>

                                                            <key>SensorSampleRate</key>

                                                            <integer>10</integer>

note that the "key" and the following value (in this case "integer") go together, you;ll need to delete both lines

So your new section would look like this, with both P3HistoryLength and the integer below removed:

  <key>ID</key>

                                                            <integer>0</integer>

                                                            <key>IdleInterval</key>

                                                            <integer>100</integer>

                                                            <key>SensorOption</key>

                                                            <integer>1</integer>

                                                            <key>SensorSampleRate</key>

                                                            <integer>10</integer>

   ...

If edting the plist file manually seems a little daunting, there are programs like prefedit which make it easier.

- Jack

@BasementJack and Bradford: Jack - great suggestion to use PrefEdit. I had not known about it before but just tried downloading the trial version to trial-delete the P3HistoryLength parameter and edit one of the several Threshold parameters. I like it - it makes the editing-business much less error-prone which, as you sggested, is a likely source of Bradford's problem.

I noted, from the PrefEdit licence terms, that the Demo version is limited to no more than 5 nested levels of XML parameters (i.e. < < < < < ... /> /> /> /> />) so I'd probably need to make the purchase in order to save changes to the info.plist file. But I was able to actually make the changes and undo them; I didn't try to save them.I noticed that PrefEdit, like TextWrangler, prompts you to "Unlock" the file if you need to alter the original.

One thing I noticed about the Unlock prompt is that it warned me that the file was "in use" and might not be able to be saved. So you might need to edit a copy and then replace the original.

Kudos

Hi everyone, did you have this shutdown/restart issue with your Mac?

https://discussions.apple.com/message/17580682#17580682

Like login problem, it's very curious...

jas0nyan: No. I have seen the SBBoD but not in the circumstances you describe in your post to the thread that you started.

Question: Can you clarify which mid-2010 MBP model you have? You typed MBP "...371". Did you mean MacbookPro7,1?

My first guess is that it is the same "kext-related" bug that many of us have experienced at login (when prompted for the login account password). So the "kext-fix" is probably worth a try.

Mid-2010 MacBook Pro 15''

jas0nyan: Correction - I had this one ...

http://everymac.com/systems/apple/macbook_pro/stats/macbook-pro-core-i7-2.66-alu minum-15-mid-2010-unibody-specs.html

... for which the fix worked.  There were 4 of the mid-2010 15-inchers, all designated MacBookPro6,2.

Terry: I posted and hour ago re a possible solution to this issue. The solution was actually sent to me  from Apple Support Communities Updates <discussions-updates@apple.com>. The post has been deleted, I assume, because it relates to product which will be release this summer and that product, evidently cannot even be mentioned in a public forum.

I belong to the  iOS dev prog but not mac so I don't have access to the beta ver out right now which might solve this. I may go for it and see if it does solve the problem. If you want to see the email from apple I'll fwd it to you. The content of that email, as well as my post which was deleted, in no way violates any NDA. Im guessing the post was deleted because it contained the name of an operating system that has not been released.

I would love to see the email. I would be pleased to see it. Also, if you have any questions about the unreleased product, then do not hesitate to ask me any question (that you can send to my email) about it; don't pay for the Mac Dev Portal until you are sure you have other questions which I might not be able to answer. All I can really say is that it HAS been repaired by the product to be released in the summer.

<Edited by Host>

Courtland and Adam: Courtland - I think your guess is a good one. There must be a background-process that automatically flags and/or deletes posts that have forbidden keywords. My own replies were also deleted.

I have also had "the company's" terms-of-use pushed in front of me (again) and been obliged to check-off the agreement before being allowed to login. Makes me wonder what is going on at Tim Cook's level. After all, we are just trying to help each other. It feels weird! All I know about the new product is what I've read in public releases - and that is quite enough, thanks. Leave the speculation to the pro-journalists and bloggers.

Ok. Apple deleted my post (and edited another one) because it included my email. Anyways, for anyone still having the issue, they should try the kext fix.

Also: Terry - Apple also made me sign off the Apple Support Communities User Agreement, while I didn't even talk or release any unkown information about that product.

As a sequel to my previous post, I too have been advised by this discussion's moderators "... not to respond to question(s) ..." about unreleased products, which of course I could not possibly do since I have never had hands on said products. Looks like the "reality-distortion-field" is still alive and well.