Home Forums Help needed Tabbles does not see the encrypted disk

Tagged: 

Viewing 4 reply threads
  • Author
    Posts
    • Avatar photouser52
      Member
      Post count: 2

      Hello. I use a program to encrypt files. When I decrypt files the program creates a new disk with the decrypted data.

      I plugged in this drive, specify a unique name in the Tabbles. I added files, add the tags with Tabbles and disconnected drive.

      Сonnect disk again – Tabbles does not detect drive.

      When i try to open a file from Tabbles tag – i got the message “please connect the disk labeled …”.

      If i connect this drive to another letter (F instead E, for example) – Tabbles detect it as new drive and ask for unique name.

      Questions:
      1) How to force Tabbles to see files on the disk, which was added before the first disconnection?
      2) How to move already tagged files with “Database update wizard”? I try to change disk letter in Tabbles (after connection my disk to another letter), but Tabbles requires that both drives are connected.

    • Avatar photouser52
      Member
      Post count: 2

      I opened the database and replace the old disk ID to the new ID in all tables.
      Accessed files, now I can move them.

      Why this identifier is present across multiple tables?
      It looks like a very bad database design.

    • Andrea
      Keymaster
      Post count: 963

      Hi there,

      we never made any test with encrypted disk. In our next release (Tabbles 4) we won’t use the DiskID anymoer, we’ll release a beta later today.

    • xKater
      Member
      Post count: 3

      What will replace the “DiskID” mechanism – just the full path? — which of course we can easily globally replace drive letters, here and there, where necessary?

      tia

    • Andrea
      Keymaster
      Post count: 963

      Yes, the full path.
      If you’re in sharing group, in V4, Tabbles saves the path for every machine where the file is tagged.

Viewing 4 reply threads
  • You must be logged in to reply to this topic.