Memory slot utility keeps popping up: Mac Pro 2009 quad

If you need Root:

1) enable Root

2) Log in as Root, see the meassge and dismiss it.

3) go back to your regular userid

4( If message does not recur, disable Root

orionexp, how do u do that?

Morton,

This is for Lion: Go to Macintosh/System/Library/CoreServices

in CoreServices take the Memory Slot Utility application and drag it somewhere else, maybe another hard drive.. this way you can replace it later if you want to withouth reinstalling the system.

Once you re-log in, that warning will be gone forever. Yeah, it's really annoying.

avsome, thanks a lot 🙂

and btw, 32bg ram rocks in FCPX 😉

Grant Bennet-Alder wrote:

If you need Root:

1) enable Root

2) Log in as Root, see the meassge and dismiss it.

3) go back to your regular userid

4( If message does not recur, disable Root

This works in Lion...I added 4 Gig to my Mac Pro and kept getting the message, PRAM Zap did nothing, SMC Reset did nothing.

Had the same problem with MacPro Eight Core 2,26 GHz early 2009.

Since upgrading to 16 GB (8x2GB) a few weeks ago the Memory Slot Utility kept popping up after every startup.

Any of the solutions brought up here did help me fixing the problem.

So i searched for a different way to get rid of the Slot Utility Window and reminded myself of NEARLY ALWAYS being CORRUPT PREFERENCES the reason for most of the problems with my Mac.

But were does the System store the Memory-Slot Utility-Preferences?

Logged in as Administrator I went to MACINTOSH HD / SYSTEM / LIBRARY / CORE SERVICES / MEMORY SLOT UTILITY.

Then I right-clicked the utility and chose the option SHOW PACKAGE CONTENT.

Within the contents folder there are several subfolders.

I searched for files with a ".plist" at the end, which in my case were "Info.plist", "Memory Slot Utility-Info.plist" and "version.plist".

The ending ".plist" means that the file is a only a preference-file and can be deleted without having destructive impact on any programm.

After restarting the Mac, the Memory-Slot-Utility-window was gone.

Best regards,

Pat Garret

Your research shows that you can suppress the Memory Slot Utility. But have you permanently disabled it with this method?

If you add or remove memory, it would be nice if it came back to report if the modules were in the right place [once] and then could be made quiet again until the memory size changed again.

Morten Schmidt wrote:

got the same here

upgraded Macpro 8core, from 16 to 32GB, and I keep having this masage

nice to know, but not everytime I boot..

I am the only user on this mac, so I am admin, but I did the root trick with no luck, still same tning.

anyone?

On my MacPro 5,1 I HAD to log in as root to dismiss the message - Admin User had no effect. I have spent hours looking for a method for my customers that did not require root password, so far to no avail. At least on my own computer, root log in was required, and works every time. Since I move memory around a lot I get the message problem a lot.

Rick

Great find Pat.

thanks! one reason I don't care for use of package style app-folder

Thank you Pat, your approach is the sane way to eliminate the pesky message. It works! FYI, each time I booted my MacPro 2009 quad after adding 3 GB my msg read, "The memory modules are installed in the recommended slots." Enabling the root user via the Users & Groups/Login Options/Network Account Server/Open Directory Utility/Edit/Enable Root User was easy but it is not clear to me how to also login as a root user. Just enabling root user then rebooting didn't ask for a login/password and the message kept returning. If I new how to login perhaps the other method in this thread would have worked as well. Anyway I'm happy now.

Pat Garret wrote:

Logged in as Administrator I went to MACINTOSH HD / SYSTEM / LIBRARY / CORE SERVICES / MEMORY SLOT UTILITY.

Then I right-clicked the utility and chose the option SHOW PACKAGE CONTENT.

Within the contents folder there are several subfolders.

I searched for files with a ".plist" at the end, which in my case were "Info.plist", "Memory Slot Utility-Info.plist" and "version.plist".

The ending ".plist" means that the file is a only a preference-file and can be deleted without having destructive impact on any programm.

After restarting the Mac, the Memory-Slot-Utility-window was gone.

I would like to point out to future readers of this thread, do not follow this procedure!

The reason it "works" is because removing those plists was basically almost the moral equivalent of removing the slot utility application which I have often recommended against doing since the app will may be replaced by future Apple updates. All this does is break the application so that it is no long an executable application. There may even be a error message in the logs when the system attempts to execute the slot utility although I didn't verify that. You might as well just remove the app instead of bothering with this and leaving a damaged application in your system.

The poster is incorrect that all files ending with .plist are "only" just preferences. They are not. There are lots of places in the system where plist's are not preferences and have special meaning. A bundle's Info.plist in particular is the file in all executable bundles that defines the attributes of the bundle. Take any executable bundle like an application, remove it's Info.plist, and it is no longer considered an execuable application bundle. Consider it damaged because the system certainly does.

See the following:

Information Property List Files

X423442X your reply is troubling. It is OK to provide constructive criticism but not to offer something in exchange does not convince me of its accuracy. Like Pat, I learned to remove .plist files in lieu of .app programs. (The Apple tech on Case # 293335442 sent me to my local Apple store to resolve.) Also note that this thread has a root user solution on which you made no comment. Perhaps you could offer a bullet proof solution to this problem that meets the goal to eliminate the message and doesn't involve .plist removal.

X423442X your reply is troubling. It is OK to provide constructive criticism but not to offer something in exchange does not convince me of its accuracy. Like Pat, I learned to remove .plist files in lieu of .app programs. (The Apple tech on Case # 293335442 sent me to my local Apple store to resolve.)

Whether you take my word for it or not is up to you. I don't really care. I gave a link to the Developer doc of what a Info.plist is used for and it is not preferences.

If you don't believe what I say then try it for yourself. Copy any application you choose at random and drag the Info.plist out of it. Then try to execute the damaged app.

Also note that this thread has a root user solution on which you made no comment. Perhaps you could offer a bullet proof solution to this problem that meets the goal to eliminate the message and doesn't involve .plist removal.

I don't need to make a comment about using root for this problem since I was the one who posted in the first place to do that. If you read this entire thread then you would have seen my post here with two links to threads where I first said to login as root to disable the message.

Since you apparently didn't read that I'll save your the trouble getting those links. See this discussion and this discussion.

As you said, had I read your posts you would have convinced me as you did EasyRider 1976 that your solution was bullet proof. Background: I first check the file and the .plists files had not been recreated as I thought they would be, and as you said the app was busted. So I restored the Memory Slot Utility app from Time Capsule and verified the pesky msg did return as a user login. Finally logging in as root user correctly and clearing the msg, then re-logging in as user did indeed clear the msg. To verify I tested the app and it was not busted.

You were assualted from many sides on this one and you prevailed. I do believe you and, yes, your method is bullet-proof. Also I learned in the process, but don't worry, as they say, I will not attempt to be a repair tech with other peoples machines. I will leave that to the professionals, such as yourself.