What I don't like, is that it's really slow as molasses when multitasking - and the RAM maxes out at 1GB. What I like about the PPC is that it is rock solid. However, I think that's something to keep in mind. Possibly there's nothing to it, and my personal experience may be coincidental and unrelated. Then, in various forums discussing Mac utilities, several times I've come across the claim that iDefrag can kill HDDs. I put in a new one, but skipped the iDefrag this time. Shortly thereafter, my HDD (Seagate) croaked. It did nothing whatsoever to speed up or otherwise improve the performance - if anything, it felt like it made it slightly worse (though that could be an illusion). Then, a few months later, I installed iDefrag. I put in a new (bigger) HDD and it worked well. I have the last model PPC mini made, a 1.5GHz one. Ignore anyone who says that macs don't need to be defragged. My MBP is a GREAT machine and this is just a little hiccup with the hard drive.įinally, if anyone has anything further to add about iDefrag or Apple MBP hard drives relating to this issue, the rest of us are all ears.Get something like iDefrag and actually defrag your HD from time to time. Apple will replace it and my problem will go away, or I will, at a later date, decide I need a larger system hard drive and replace it myself. What's going to happen with this? I suspect that this system drive will work fine until other, weird problems start cropping up or it will die suddenly (This sudden failure of the system drive did occur with my iMac right after I purchased it). I also have recent, valid backups of my system drive so if there is a sudden failure, my data loss will be minimal. I have partitioned my system hard drive with Boot Camp and am running XP Pro on it without any problems. I must also point out that my MBP works just fine. I will contact Apple on this as well and since I have Applecare, I'm not too concerned about this. Coriolis has forwarded a report to Apple making them aware of the problem and has suggested that I do the same. So, it appears that the problem is most likely a problem with the hard drive temperature sensor. Since I'm sure that more the two MBP owners use iDefrag, and if this was a problem with OSX, then there would be many more reports. At present, there are only one other report to Coriolis of this problem and disabling temperature monitoring has stopped iDefrag from crashing. iDefrag keeps track of the drive temperature since it's working it so hard during optimization. The problem is that for some reason, OSX isn't returning the temperature of the internal system drive properly. No problems we ever found and as it turned out, that wasn't the issue. None of these programs ever reported any problems with my system drive and I used them to verify the drive's disk structure as well as media surface since iDefrag's error logs showed corrupted disk sectors. The programs I purchased was Drive Genius, Disk Warrior and Check it. I did purchase several other hard disk performance programs to see if they would report any problems as well. The solution was to enter a new boolean parameter in iDefrag's plist file called disableThermalMonitorCompletely and the program ran fine. I emailed Coriolis' tech support and they had me go through some troubleshooting procedures and last night, I was able to get iDefrag to properly defrag my system drive again. When I tried it again, it hung part way through and went no further. When I did it again in March, the MBP crashed and I had to do a reboot. In December, iDefrag optimized my MBP's Macintosh HD without a problem. Now, I purchased a copy of iDefrag originally for my iMac G5 and when I got my MBP, I installed it there as well. The OS may delay that process with its own optimizations but all hard drives fragment over time when used as the system drive. I come from the school of thought that says the deleting and writing of new files to the system drive will, over time, fragment a hard drive. Second, I don't want to get into a debate about whether or not the OSX system drive should or should not be defragmented. If anyone else has any information on this problem, please post what you know so the rest of us can benefit. At this time, it appears that the problem is with my MBP and NOT iDefrag. This posting is to share my experiences with iDefrag and my MBP and what has been determined to be the problem. First, I would like to say the Coriolis' iDefrag is a fine program and it works well on both my MBP and iMac G5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |