I am not pleased with this developers idea of customer loyalty. I look forward to some help, as my work is halted until I finish defragging some drives, and I'm wondering if I need to budget 28 hours of computer downtime per 650GB of hard drive defragging :-|
#Idefrag requests license 5.3 portable#
Model: Expansion Portable HDD (STEA4000400)Ĭonnection: Seagate's USB 3 Elgato USB 3ĪLSO - Regarding upgrading from iDefrag 1.7.3 to 2.2.8 (per Corialis website suggestion for OS10.9.5):
#Idefrag requests license 5.3 pro#
Skip files that cannot be defragmented due to lack of free space: SELECTED/CHECKEDĬonnection: MacBook Pro ThunderBolt 1 Elgato ThunderBolt 2 I'm wondering: Does this mean I have another 14+ hours left to wait for this, and if so, is this normal/OK for iDefrag to take some 14-28 hours to optimize 650GB on a 4TB drive?!Įnable per-class sorting: SELECTED/CHECKED I recently upgraded my OS from 10.7 to 10.9.5, and I already had iDefrag 1.7.3 (229), which I'm using now.Īs we speak, I'm about 14+ hours into a iDefrag Optimize on a 4TB external drive that only has 650GB used, and the Location Indicator is only about halfway through the populated area of the Whole Disk Display. Hi MU community! I hope someone might be able to advise me here. The license information can be obtained from the Coriolis Systems' website Note: Coriolis Systems Limited is shut down and does not provide any support for its products. Fine-grained security, just like iPartition.Auto-update feature ensures you always have the latest version.Altivec accelerated display for improved performance.Quickly jump to specific files to examine them in more detail.Inspector allows you to view details of individual extents/files.Detailed statistics so you know whether you need to optimize.Per-block and accurate whole disk display.High-performance user-defined file classification engine.B-Tree metadata file compaction/optimization support.Defragment whilst your disk is mounted.Compact data, moving all free space to one place.Four powerful defragmentation algorithms:.
0 kommentar(er)
