New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vault not compatible with CLI #204

Closed
sleezy23 opened this Issue Mar 24, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@sleezy23
Copy link

sleezy23 commented Mar 24, 2016

Can't navigate or perform operations such as DIR, ROBOCOPY etc from the Windows command prompt on an unlocked vault. Usually get an file Have tried with Windows 7 and 10, and several versions of Cryptomator, including latest version. Copying files works with Windows Explorer, however.

@markuskreusch

This comment has been minimized.

Copy link
Contributor

markuskreusch commented Apr 1, 2016

Created a vault placed a single file in foo/putty.exe and tried DIR and ROBOCOPY. Worked well.

Can you explain your problem a little more? What exactly do you place inside of the vault. How do you run the commands and what error messages / unexpected behaviour do you observe?

@sleezy23

This comment has been minimized.

Copy link

sleezy23 commented Apr 1, 2016

Thanks for getting back to me Markus.

The vault contains ordinary files like Word docs, pictures and PDFs.
Nothing special.

If one uses Robocopy to mirror a directory to another location, it is
supposed to sync only the changes between source and destination. However,
when the destination is an open cryptomator vault, Robocopy doesn't
recognise that files already exist in the destination and consequently it
deletes everything from the vault and recopies every file again. Here is an
example of the execution. In this test, a single file, i:\robocopy.txt,
which already exists in the vault, is deleted and recopied, but Robocopy
should simply have skipped it. You can also see that the sub-directories
were also not detected in the vault even though they too are present.

I have also previously seen DIR commands error or return blank when
attempting to list directory contents from the prompt.

-------------------------------------------------------------------------------
   ROBOCOPY     ::     Robust File Copy for
Windows
-------------------------------------------------------------------------------

  Started : 01 April 2016 20:54:03
   Source : i:\
     Dest = j:\

    Files : *.*

  Options : *.* /DCOPY:DA /COPY:DAT /R:1000000 /W:30

------------------------------------------------------------------------------

                       5    i:\
    *EXTRA Dir        -1    j:\Files
    *EXTRA Dir        -1    j:\Help
      *EXTRA File             7803    robocopy.txt
        New File              7803    robocopy.txt
  0%
100%

------------------------------------------------------------------------------

               Total    Copied   Skipped  Mismatch    FAILED    Extras
    Dirs :         1         0         1         0         0         3
   Files :         5         5         0         0         0         5
   Bytes :    17.9 k    17.9 k         0         0         0    17.9 k
   Times :   0:00:00   0:00:00                       0:00:00   0:00:00


   Speed :               26888 Bytes/sec.
   Speed :               1.538 MegaBytes/min.
   Ended : 01 April 2016 20:54:04

Thanks, Alain

@markuskreusch markuskreusch modified the milestone: 1.1 Apr 28, 2016

@overheadhunter overheadhunter modified the milestones: 1.1, 1.x May 10, 2016

@overheadhunter overheadhunter modified the milestones: 1.x, 1.4.0 Jun 20, 2018

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Jul 12, 2018

Good news, everyone! We've released version 1.4.0-beta2, which introduces Dokany support. You now have the choice between Dokany and WebDAV based virtual hard drives.

Please retest this issue with Dokany enabled.

@no-response

This comment has been minimized.

Copy link

no-response bot commented Jul 26, 2018

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment