We are testing SEE V8 and its new features in removable storage. In particular the ability for a file to be decrypted automatically when written to USB and then allowing the user to decrypt the file.
The reason we want this is so we can ensure that all files are encrypted but them allow the users to use decrpyted files where needed. eg. image files.
The image file we are using is around 1.8GB in size and we were finding that when decryption was reporting as finished (yellow dot dissapears and the decrypt option changes to encrpyt) the file was corrupt. The image process would get so far but then fail.
We then started the decrpyt process and left it overnight and this morning the file works.
So it seems like the file hadn't been totaly decrypted, even though it was reporting that it was.
Does this make sense? Anyone else seen the problem?