-
Thank you so much for investigating and finding the conflict.
This has always been an issue with Shell Extensions - they require that the Shell (Windows Explorer / Directory Opus etc) work as expected.
The problem is that Microsoft has not really documented this very well, so it's hard both for a shell implementer and for a shell extension to know.
However, by definition, if it works...
2009-11-09 19:24:40 UTC by svante
-
Hello Svante,
Thanks for your questions. I have now discovered that the problem arises through interaction with GP Software Directory Opus (http://www.gpsoft.com.au/), which is a File Manager & Explorer replacement.
If Directory Opus is set up to replace Explorer (see screenshot in AxCrypt.doc) then the error (see screenshot for error message) arises. If Directory Opus is set up with "Don't...
2009-11-09 18:25:43 UTC by polwhele
-
Thank you for this suggestion!
It will be considered for future releases.
2009-11-09 15:12:27 UTC by svante
-
Ok.
Is it possible for you to upload a screen shot, not only of the AxCrypt dialog, but of the Control Panel, so I can see what mode you're displaying it in.
It's obviously something that varies between installations, as it works perfectly on various Windows 7 installations that I have access to for testing purposes, both 32-bit and 64-bit.
Do you have other additions that affect the...
2009-11-09 15:07:49 UTC by svante
-
Currently, "Encrypt a copy to .EXE" retains a copy of the unencrypted file in the folder. If performing encryption on a folder structure, sorting through the folders to copy just the .exe's is time-consuming. Either a new selection "Encrypt to .EXE" or "Allow encryption of a copy (with or without the self-decryption) to a different destination" would be welcome.
2009-11-09 14:32:26 UTC by adobemac
-
Yes I am running 1.7.1836.0 Beta. Yes the problem goes away if it's uninstalled and reappears when AxCrypt is reinstalled.
Regards,
Peter.
2009-11-09 14:06:47 UTC by polwhele
-
I cannot reproduce this on any version of Windows.
Are you running 1.7.1836 ?
Does the problem go away if you uninstall, and reappear if you re-install?.
2009-11-09 12:20:35 UTC by svante
-
I can verify this issue on Windows 7 Home Premium 64 bit (Full Retail) . As soon as I open the control panel the error message always appears.
2009-11-08 21:56:41 UTC by https://www.google.com/accounts
-
Hello,
This is by design. The original file name is kept encrypted inside the encrypted data, and is always used when the file is decrypted. This is to allow you to rename the encrypted file without affecting the original file name.
Svante.
2009-11-08 10:45:31 UTC by svante
-
hello svante
i use beta version with windows 7 64 bits and if i encrypt
one file ex: test.axx and if i rename this file after encrypt in test1234.axx
when i decrypt test1234.axx the name change to the original name
(test) it's a bug or not ??
thanks.
2009-11-07 16:39:11 UTC by nobody
