Checksum plug-in no longer defaults to saving in same dir

[DavidAns]

In 2.51, the checksum plugin would default to saving the .md5 file in the same directory as whatever file you'd just computed the hash for. In 2.52b1, it seems to default to the last directory you saved something in - which is typically not what you want.

Would be nice to have the previous behavior back.

PS - LOVE the addition of SHA1!

[Jan Patera]

In 2.51, the checksum plugin would default to saving the .md5 file in the same directory as whatever file you'd just computed the hash for. In 2.52b1, it seems to default to the last directory you saved something in - which is typically not what you want.

This is weird. I am unable to reproduce it (WinXP64). And I don't see how this could be hapenning. Even if you save the .md5 file to some other folder and then do resave, again the original folder is offered. What version of Windows do you have? Are you saving to a local HDD or over some UNC path?

[DavidAns]

Sorry, Jan, I'll test again tomorrow to make sure I'm not crazy. Platform was Windows 7 Beta 1 x86. Maybe I'll use the new "bug recorder" in there to capture some screenshots and try to prove my claim.

[DavidAns]

I see the same behavior when I try this again. I used the Win7 problem report creation tool to generate attached file WrongDefaultDirectory.zip which contains a series of screenshots demonstrating the problem. Note that I first do a checksum in the AAA directory (where the path is correct), then I do one in the BBB directory and the path defaults to AAA incorrectly.

Thanks for the help!

[Jan Patera]

I see the same behavior when I try this again. I used the Win7 problem report creation tool to generate attached file WrongDefaultDirectory.zip which contains a series of screenshots demonstrating the problem. Note that I first do a checksum in the AAA directory (where the path is correct), then I do one in the BBB directory and the path defaults to AAA incorrectly.

Hmm, I tested Win 5.0, 5.1, 5.2 and 6.0 and it always worked. I do not have Windows 7.
I am suspecting a bug in Windows 7.
Can somebody please give it a try and confirm or deny David's observations?

[Jan Rysavy]

Please don't waste time with reporting Altap Salamander bugs in Windows 7. This system will not be supported until final version of Windows 7. Right now is Windows 7 (build 7000) just unfinished "technology preview", nothing more.