Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I tried this command in Terminal but got this message:

update_dyld_shared_cache[250] current cache invalid because /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit has changed

update_dyld_shared_cache[250] current cache invalid because /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit has changed

You have to restart for the updated boot cache to take effect.

Basically the QTKit isn't up-to-date, which can slow things down involving quicktime.

Edit: now look to see what you can do to remove that old fan/temp monitoring program, might be in the login items.
 
You have to restart for the updated boot cache to take effect.

Basically the QTKit isn't up-to-date, which can slow things down involving quicktime.

Edit: now look to see what you can do to remove that old fan/temp monitoring program, might be in the login items.

So coreduotemp was installed but the speedit was missing. So i unistalled the speedit (there was an option for it) and then uninstalled the program. I restarted and its still the same error message.

If anyone is curious or has a moment, I can share my screen on ichat. My sn is mach1andy ... I really appreciate all of the help! Thanks guys-- we're getting close.
 
Leopard came on my machine and yes, I installed istat nano and menus a while back but then uninstalled them earlier today.

I did do the install and archive and still seem to be getting this message (see photo)

Istat NANO was your problem. It installed a kernal extention that messed up your install of OSX. I'd remove all traces of it (try a spotlight search) and if that doesn't work... backup your homefolder to another machine/external disk and reinstall.

Sorry! :cool:
 
At worst try a new user, see if that gets you around the speedit issue.

I gave up on istat long ago, every time I installed it it would mess with my Universal Access prefs giving me a wiggly screen, alway ended up having to trash all my apple prefs.
 
It's just the problems that the security update has caused Safari, and 1.1 didn't fix it for everybody.
 
Ok. So I rid my machine of istat nano, pro, menus, coreduotemp & speedit and it feels better but I still get this in the console>>

12/23/07 3:12:35 PM mdworker[83] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
 
Any chance there is Now Up To Date and Contact 5 on the machine and a little folder called "NUDC" in the startup items folder?
 
Any chance there is Now Up To Date and Contact 5 on the machine and a little folder called "NUDC" in the startup items folder?

no "NUDC" in the startup folder-- just these 3. Are they safe to remove? I uninstalled the HP printer mish-mash crap and I'm guessing this is just ruminant.
 

Attachments

  • Picture 1.png
    Picture 1.png
    78.6 KB · Views: 68
Here seems like Scott Lahteine's answer may help if it isn't NUDC.

http://discussions.apple.com/thread.jspa?messageID=6113346

So his advice is to uninstall 3rd party apps and monitoring software and then reinstall them if they're for Leopard. If I keep getting these messages, do you think there is there any harm to the machine or will it slow it down? I got rid of a lot of stuff so I'm hoping that even though there are still the messages, its impact is minimal.
 
Ok. So I rid my machine of istat nano, pro, menus, coreduotemp & speedit and it feels better but I still get this in the console>>

12/23/07 3:12:35 PM mdworker[83] _CFGetHostUUIDString: unable to determine UUID for host. Error: 35
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.
12/23/07 3:12:44 PM com.apple.SystemStarter[17] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec().
12/23/07 3:12:44 PM com.apple.SystemStarter[17] Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__() to debug.

I wouldn't worry about the messages if your machine is working fine. :)

Those messages just mean that there are some unniceties in Apple's coding - nothing serious.
 
It seems like they should fix this-- anyways, maybe in 10.5.2 ? Thanks for all of the help everyone! Leopard Cache Cleaner is pretty darn awesome, by the way!

So here's a last tangent question: in OSX, when you remove a program and it doesnt have its own uninstaller, what is the best way to remove the program and all of its spattered files?
 
It isn't an Apple problem, it is a coding error from developers with 3rd party apps and drivers using Core Foundation calls.

Something the developers have got away with in the past, but has caught up to them in Leopard.

Also something to keep an eye on since any OS update could make the issue worse and totally break those apps/drivers/etc. in the future.

Of course developers aren't the only ones nailed, you'll see slips like this from Apple apps also.
 
It seems like they should fix this-- anyways, maybe in 10.5.2 ? Thanks for all of the help everyone! Leopard Cache Cleaner is pretty darn awesome, by the way!

So here's a last tangent question: in OSX, when you remove a program and it doesnt have its own uninstaller, what is the best way to remove the program and all of its spattered files?

For OSX, well writtten apps (unlike MS Word, or **cough**SMC Fan Contollers**) that don't modify system files store most of their files in /Users/~you~/Library/**App-Name**/ or /Users/~you~/Library/Application Support/**App-Name**/. If you remove the app in Applications folder and its file in ~/Library/, you should be fine.



Sun Baked: I appologize for having made a too general statement :) But this might be fixed in 10.2 - it seems to have more libraries for older software.
 
For OSX, well writtten apps (unlike MS Word, or **cough**SMC Fan Contollers**) that don't modify system files store most of their files in /Users/~you~/Library/**App-Name**/ or /Users/~you~/Library/Application Support/**App-Name**/. If you remove the app in Applications folder and its file in ~/Library/, you should be fine.



Sun Baked: I appologize for having made a too general statement :) But this might be fixed in 10.2 - it seems to have more libraries for older software.

Well, I've learned a good lesson from getting in there a bit. I'm going to be a lot more careful with what I install and let have access to important directories. Its still throwing those same error messages but in general, its fixed. Thank you for your help!!
 
well, i think you dont have to install that much

like istat nano and coreduo temp and speedit

they have the same function anyway, to monitor the temp and stuffs

and i dont think you will be needing those and still your MB will be perfectly fine as long as you don't do anything crazy with it :D
 
well, i think you dont have to install that much

like istat nano and coreduo temp and speedit

they have the same function anyway, to monitor the temp and stuffs

and i dont think you will be needing those and still your MB will be perfectly fine as long as you don't do anything crazy with it :D

I also have a 2,2 and 4G of ram, no pinwheels here......

Did either of you read this thread past its first post? :D

Glad I could be of help mach1andy!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.