Open thany opened 6 years ago
Let's actually call it the age-old problem of silent fails. At least my third point.
If I point it to a completely bogus file for my private key, it acts as if it still happily connects. It shouldn't work, and it should give a big fat error message. I can also happily """"connect"""" if I enter a nonexisting remote directory to connect with.
Why is this program unable to display an error message? How can I ever know what's wrong if acts as if all fields are correct, when they might not be??
Oh wow, even if the local mount folder doesn't exist, it still acts as if nothing is wrong. But in the mean time it connects to absolutely nothing, and mount nothing into nothing. Brilliant!
Just see this: https://github.com/Foreveryone-cz/win-sshfs/issues/163
But should it be so hideously unstable when I've got the latest version of its dependent library? Could you not just bundle whatever version of Dokan works with your program? I had been fiddling for several hours before giving up, with all kinds of combinations of versions. It shouldn't be so complicated.
Alternatively, why not use OpenSSH Beta, which is now a component in Windows 10?
I feel your pain bro, but I can't help, I'm a ordinary user. https://github.com/dokan-dev/dokany/wiki/Update-Dokan-1.0.0-application-to-Dokany-1.1.0
Technical data
WinSshFS
Dokan driver
Enviroment
Support
Probably 3 related issues: 1) After mounting a folder into a drive, the program crashes as soon as Explorer displays the drive, so that's before even opening it and viewing the contents. 2) After reopening the program, all my mounts are gone!! How many times do I have to keep reentering all those fields! Argh! 3) Mounting a remote folder into a directory doesn't seem to work either. It's totally empty, and I'm not getting errors, which leads me to assume the fields entered were correct.