Feyd

A variety of things could be revealed. Some examples: Someone could use their real name as their user name. They could have directory or file names that include the names of providers of different services (such as banking, phone, etc). There could be geographic clues or information about where the person received their education. If a malicious person knows what software is installed on a target's PC, they could create specific exploits. I could go on, but hopefully that gives you an idea. Even if it isn't plausible that the information will be used improperly, I don't see the benefit of including it in the log.

Background: Currently, I am not comfortable running Defraggler in debug mode and uploading the complete log file straight to these public forums. Suggestion: Do not log personally identifiable and unnecessary information. Examples: Do not log Computer Name or User Name. Do not log file name and path unless there is a problem with the associated file operations such as an error or failure. Benefits: Users like me won't have to edit and censor the log files before uploading. Users not familiar with technology won't inadvertantly post personal information on your forums that could be misused by others. Piriform will have to worry less about protecting user information.

Defraggler v1.21.209 (64-Bit) OS: Vista 64-bit 2 mirrored (RAID 1) HDs Towards the end of a defrag, Defraggler attempts to defrag C:\$MFT. While I think this is a known issue in and of itself, I found the GUI updates interesting. The attached screenshot shows a still version. The large set of red blocks near the top is C:\$MFT and for many seconds (10-30?) Defraggler reads (the red flashes yellow) and tries to write it (a green section flashes) the bottom half cycles through blue, white and light blue. To clarify, the areas around the pagefile and MFT are actually almost completely empty. This is reproducible for me (if I defrag again it does the same thing). I wish I had an animation because it is neat (despite the panic the first time it happened because it looked like my HDs were getting eatten). After it moves on, the map is updated and looks normal again. I've also included a debug log. There are several errors/failures in it which may be useful to the dev team. defraggler64.exe.1_21_2092010-10-30_12-21.txt