I broke prebinding in Jag with Cocktail 2.0

michaelsanford

michaelsanford

Translator, Web Developer
It would appear that I've done something to my application prebinding with Cocktal.

I forced prebinding, which in retrospect was a really bad idea.

It seems to have done something to my apps. Imaging (or is it called Preview?) takes around 12 seconds to start up, when it used to take one or two.

It does that even if I start it, then immediately quit it and restart, which is strange because I would have assumed the cache would take over there...

I tried sudo update_prebinding -root / but it seems to have had no effect.

fix_prebinding does run whenever an app opens (I checked with top) but that doesn't seem to help.

Any suggestions, it's really annoying to have a 700MHz G4 with 786 ram and have to wait like 20 seconds for a little app like Imaging/Preview to open :rolleyes:
 
PS I should point out that this is a logical assumption I am making, since my system seems to have slowed down after I forced prebinding with Cocktail.

I can't, however, be completely certain that it is a prebinding issue.

System Preferences takes around 20 seconds to load, even when closed and re-opened right away. A nice little app called DropJpeg that usually loads in 1 second takes a full 16 seconds to open...

Mysteriously, though, Adobe Photoshop Elements loads the splash screen almost instantly...
 
I used Cocktail once, and i had to reinstall mystem, not sure what it was but something really killed it. But i was using a earlier version. Cocktail is a great app, but something did cause serious problems that nothing would fix.
 
yea, I was mad, because I had no reason to use it, i saw it on versiontracker, and for whatever reason tried each feature. Some were cool, but one really killed the system. I know I clicked restart, I got logged out, and from there it was hell .
 
Cocktail 2.0 has worked fine for me, causing NO problems. If you have any doubt regarding your prebinding, I would suggest booting off your OSX install disc and running Disc utility to check your drive, then run permissions repair from there to confirm that your physical drive is fine, and that your permissions are correct.
 
Yeah, I actually repair permissions rather regularly (after many installs, system mods, etc. just to make sure).

It seems to be working well now, so I'm not too concerned. Thanks for the input!
 
You must log in or register to reply here.
Back
Top