Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Worked great for me (2008 MP with Intel G2 80GB). My only concern was the the permissions fix seemed to last forever, so I just rebooted.

Boots fast as ever.
 
HI guys. I was digging around about SSDs and TRIM for Snow Leopard and found this. Looks great but my question is, how do we know it's really working and not just changing what the hard drive diag says? Just curious. Thanks.
 
HI guys. I was digging around about SSDs and TRIM for Snow Leopard and found this. Looks great but my question is, how do we know it's really working and not just changing what the hard drive diag says? Just curious. Thanks.

Fair but lazy question, read the posts and you'll see your answer.
 
One other thing that hopefully hast been answered here.... Is there any ongoing cleanup that has to be done manually like the post patch cleanup?
 
Ive had enabler enabled since it was released and have had more beachballing and SUPER slow google chrome than ever before Enabler.

when it was first released, I just clicked "patch" Never did the free space nor did I run the command. If I do this, will it fix my issues?

if not, how do I remove trim enabler?

thank you in advance
 
so I did the free space.. Now my macbook pro is stuck at the start up spinning wheel of death

Real flipping nice.... POS TRIM enabler screwed up my system

used my install CD to get back into disk utilites and did the disk repair and such....still stuck

Now what. I'm about the flip a lid!

If you tell me I'm screwed, I'm going to be rather pissed at the developer...
 
so I did the free space.. Now my macbook pro is stuck at the start up spinning wheel of death

Real flipping nice.... POS TRIM enabler screwed up my system

used my install CD to get back into disk utilites and did the disk repair and such....still stuck

Now what. I'm about the flip a lid!

Over 600 posts here, and a ton more all over the net, tons of us have done this without issue, we all followed the directions, did you? Best way to get help is to call the tool and thus the creator foul names....I suggest you reread the posts to find your problem and solution.
 
Over 600 posts here, and a ton more all over the net, tons of us have done this without issue, we all followed the directions, did you? Best way to get help is to call the tool and thus the creator foul names....I suggest you reread the posts to find your problem and solution.

600 post doesnt mean squat. I've read through it. All I'm saying is that I followed the directions, and crashed my machine.

Anyway I can take out the HDD and chage the ktext file? Do you think thats it?
 
Yeah you're screwed. I actually built this tool and faked 600 posts just to **** your hard drive up. u mad?



Or not.



You say that you had a slow system after the patch. Fine, your SSD probably already has garbage collection, thus this patch is not for you.

How to remove the patch? Well, let's have a look at the GUI:

screen1.png


Gee, one could think that the Restore button might hold some function to restore your system. But I dunno. It's probably a better idea to rage at the developer instead. :rolleyes:


You say that after erasing free space, you can not boot. Well guess what, erasing free space is done in disk utility. Software created by Apple, not me. And yeah, people happen to get that problem. You would see that if you googled around on the problem. It's probably because Erase Free space failed to delete the tmp file.
 
lets say hypothetically the tmp file didn't get deleted.

since the machine wouldn't boot, I got into disk utility via the CD... did another free space, disk repair and such.

still nothing. I'm not bashing you, if it came across like that, I apologize.

Is there anything I can do to recover this or no?

thank you advance.
 
Well, you're not ****ed. If it's the tmp file, it can be deleted by booting Single User mode and finding it and delete it.

If it's the TRIM patch, attaching the hard drive to a working computer and switching back the kext will do it. The "normal" kext can be found in the Trim Enabler.app, if you right click and show contents.
It might not be the TRIM itself, but that the kext ran into some issue when installing.


But to find out your problem..

Do this:


Boot in verbose mode, hold Cmd + V during boot.

This will show all the "behind the curtain"-stuff when OSX boots. Check out what part it stalls/crashes on, and post here.
 
Well, you're not ****ed. If it's the tmp file, it can be deleted by booting Single User mode and finding it and delete it.

If it's the TRIM patch, attaching the hard drive to a working computer and switching back the kext will do it. The "normal" kext can be found in the Trim Enabler.app, if you right click and show contents.
It might not be the TRIM itself, but that the kext ran into some issue when installing.


But to find out your problem..

Do this:


Boot in verbose mode, hold Cmd + V during boot.

This will show all the "behind the curtain"-stuff when OSX boots. Check out what part it stalls/crashes on, and post here.

I will do that when I get home ( 5pm CST )
 
Well, you're not ****ed. If it's the tmp file, it can be deleted by booting Single User mode and finding it and delete it.

If it's the TRIM patch, attaching the hard drive to a working computer and switching back the kext will do it. The "normal" kext can be found in the Trim Enabler.app, if you right click and show contents.
It might not be the TRIM itself, but that the kext ran into some issue when installing.


But to find out your problem..

Do this:


Boot in verbose mode, hold Cmd + V during boot.

This will show all the "behind the curtain"-stuff when OSX boots. Check out what part it stalls/crashes on, and post here.

so I did the Verbose mode and its stalling on

"Executing fsck_hfs ( version diskdev_cmds-491.3.3~11 )

What shall I do from here?
 
My solution has the elegance of a butcher's knife, but if you have a backup and you can boot of the install CD, I'd just reinstall the OS and start again.

That probably takes an hour vs however long it will takes to troubleshoot the problem.
 
My solution has the elegance of a butcher's knife, but if you have a backup and you can boot of the install CD, I'd just reinstall the OS and start again.

That probably takes an hour vs however long it will takes to troubleshoot the problem.


I would do that, but I haven't backed up in about 3 weeks and I have 3 important things in it :-/
 
I would do that, but I haven't backed up in about 3 weeks and I have 3 important things in it :-/

Did you try running the terminal commands as posted on Cindori first post of the thread?

If you run Erase Free Space, you should run these commands in the terminal afterwards:
sudo chown root:admin /
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches

If you dont, your boot time can be much longer
 
Did you try running the terminal commands as posted on Cindori first post of the thread?

If you run Erase Free Space, you should run these commands in the terminal afterwards:
sudo chown root:admin /
sudo kextcache -system-prelinked-kernel
sudo kextcache -system-caches

If you dont, your boot time can be much longer

After erasing the free space, I had to force reboot ( machine froze and I let it try to unfreeze for 15 min )

After hardbooting, thats when I couldn't boot up anymore.

With that being said, I couldnt run the commands in terminal via Single user or terminal within the install CD since its not doing the command off the boot driver per say.
 
Hi guys. So I'm hearing a lot of bad things about this utility in another forum. Can someone tell me if using this tool is a bad idea, messes up the drive, or is irreversable? I'd like to start using an SSD in my mini and can wait for TRIM in Leopard as long as there is no problem doing so. Thanks.

EDIT: Drive is OCZ Vertex 2.
 
Last edited:
Hi guys. So I'm hearing a lot of bad things about this utility in another forum. Can someone tell me if using this tool is a bad idea, messes up the drive, or is irreversable? I'd like to start using an SSD in my mini and can wait for TRIM in Leopard as long as there is no problem doing so. Thanks.

EDIT: Drive is OCZ Vertex 2.

I have the same drive as u. I installed it when the patch came out in the early stages. It worked fine but then things like browser etc started chugging.
so i restored it back and things were fine.
so no trim support here but im not complaining as my system is on most of the time.
 
I have the same drive as u. I installed it when the patch came out in the early stages. It worked fine but then things like browser etc started chugging.
so i restored it back and things were fine.
so no trim support here but im not complaining as my system is on most of the time.

Okay super. Thanks for the heads up. Much appreciated. So it sounds like skip the trim for now until Lion. So why does it start "chugging"? Just curious. Thank you!
 
not sure
the trim did work at first and things were moving fast and after a while, beach balls galore esp on firefox or closing programs etc
ill just wait for lion i guess
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.