You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the first time I ran DROID 6.6, the HASH column did successfully export. Subsequent runs did not, and I have not changed any preferences between runs.
I've also tested on DROID 6.5 and behaviour is as-expected. Let me know if you need anything further.
I've managed to reproduce this bug. Interestingly, it works okay the first time I launched and ran it. The minimum sequence for me to reproduce this bug is:
Started Droid GUI
Added few files and clicked on "start"
Clicked export... and exported to CSV
The export has "MD5_HASH" column with valid values
Went back to the GUI,
The results are still open in GUI from before
Clicked export and exported to CSV overwriting the file that was generated before
The MD5_HASH column does not exist in the export ----- BUG!!
Hi @Dclipsham out of interest, do you find Checksum generation totally reliable in 6.5.2? We can see this issue that has arisen in 6.6.0 but as we've discussed this people have mentioned intermittent unreliability with checksums in 6.5.2, and maybe worse when analysing subfolders too.
DROID 6.6, embedded JRE 11 GUI version, Windows 10 22H2:
Preferences:
GUI behaviour (Hash present):
Export options:
CSV Output (also attached):
DROID Log (also attached):
Note that the first time I ran DROID 6.6, the HASH column did successfully export. Subsequent runs did not, and I have not changed any preferences between runs.
I've also tested on DROID 6.5 and behaviour is as-expected. Let me know if you need anything further.
droid.log
v109_EDRM_6.6_test2.csv
The text was updated successfully, but these errors were encountered: