How often does the letter . occur in:
from a previous 160GB hard disk.
check disk and all is OK.
partition causing a hang.
(until I try it again on this partition that is).
As I said, the other partitions are fine just this one which has unusually large files.
Im still having the same problem with my 300GB 320. The optimizer hangs at 12%, it shows running in blue text, but the run and schedule buttons go active again as if the utility had completed.
Is the partition giving you trouble the first partition on the SSD? Mine has a single partition on it.
I have exactly the same issue - the tool appears to not complete the operation properly (shows running 12%) whilst enabling the Run and Schedule buttons for further operations (I suspect the error is traped and silently ignored to enable the tool to keep in operation).
The partition then shows 100% full with the zeroed *.bin files remaining.
Ad-hoc solution is to run the Optimizer and manually delete the *.bin files on this partition only (all other partitions work OK).
If there was a log file option to capture the trap error message that would help a lot: this is one for the developers.
Ive tied it down to the Allocation Unit Size (as windows puts it).
Allocation Unit Size is 32K or 64K: default (which is 4K) works.
the software guys if they can reproduce it at intel.
not being a multiple of the partition (my hunch)).
Bingo! I was using 32K when I was having the issue...I erased the SSD and put it into a new build (Win 7 64) with the default allocation unit size, and the SSD tool worked OK there (though not necessary with Win 7).
I do wonder though...theres no evidence here that anyone at intel has either read this or has any interest in fixing this bug...
user
There are 28 "."s in the text you provided.
assistant