Running portable apps from mounted EncFS4Win folders failed

[avoware]

Environment

• Windows version: 10
• Processor architecture: x64
• Encfs4win version: v1.10.1-RC13 (and previous)
• Dokan version (legacy, modern): 1.2.0.1000 (and previous)

Description

Not any portable app could be executed from the mounted Encfs4win drive, showing miscellaneous errors. At the same time the same apps are executed perfectly from any other (NOT encfs4win) folder or drive.

Expected behavior vs. actual behavior

App is started normally vs. it fails to start

Steps to reproduce problem

1. Download, for example, Thunderbird Portable
2. Install it on encfs4win drive
3. Try to start (either from %THUNDERBIRD_PORTABLE_FOLDER%\ThunderbirdPortable.exe or from %THUNDERBIRD_PORTABLE_FOLDER%\App\Thunderbird\thunderbird.exe)
4. You'll see error messages, they will differ depending on the executable you use, but the result will be the same - failed to start.
5. Move folder to any other (out of encfs4win) location, try to start - everything is ok.

[jetwhiz]

Hi @avoware

Thanks for reporting this! Is it possible to get some logs of the errors that you're seeing when trying this? You can also use the -v (verbose) flag to get more details.

Also, we have just released RC14 which features a newer version of Dokany. Could you test with this version and see if that fixes your issue?

[avoware]

Hi, @jetwhiz

Thank you for your reply!

Actually, I think that the real reason of behavior I described above is case sensivity of combination Dokan+EncFS4Win.

I used mirror.exe to understand if it is due to Dokan itself and found (not surprisingly) that I can not create 2 documents with similar names (for example, NewDocument.txt and newDocument.txt) in mirrored folder (the same with original folder).

But I can easily do it with EncFS4Win encrypted folder (because encoding of NewDocument.txt and newDocument.txt filenames lead to different results, which seems reasonalbe).

When I try to start some portable app from EncFS4Win mounted folder, I get errors that some files or DLLs coudn't be found. But these files and DLLs exist and located where they shoud be located! Probably, the problem is in case sensivity, but it is just my hypothesis.

Try to repeat my example with Thunderbird Portable. Does it work in your case???

[jetwhiz]

Hi @avoware

I'll have to look into this more ... I'm not completely certain why these executables can't find their dependencies, and I'm not noticing any errors being given in either encfs or dokany. Have you noticed this issue with other software as well?