Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Separated C1 working directory

Comments

3 comments

  • FStgt
    thanks for your effort, i will try to implement it instead of creating the directory and link manually 😊
    0
  • PhaseZero
    Some DAM software is displaying junction folders even if no media files are located inside.
    If you dislike the visibility of junction folders you may like to hide them all with:

    attrib.exe +H CaptureOne /S /D /L
    The drawback is, that you may no longer be aware, if such a C1 junction is missing in specific directories. In this case C1 will create a new local subfolder structure. If this happens you still can move the C1 files manually to the "remote" C1 working directory and create the junction afterwards.

    I did not place this hiding command in the batch script, because this simple command can be inserted or started independently. You also need to know that before removing hidden directories, you have to unhide them.

    Regards from Joseph


    P.S.: Here is my trial to explain difference of symbolic and junction links (mklink with parameter /D or /J):
    • Create on PC-A a SYMBOLIC link c:\symbolic (which points to c:\target on PC-A).
      Remote access from PC-B to PC-A on c:\symbolic would resolve to the c:\target on PC-B (error if not existing).

    • Create on PC-A a JUNCTION link c:\junction (which points to c:\target on PC-A).
      Remote access from [color=#FF0000:344wty4g]PC-B to PC-A[/color:344wty4g] on c:\junction would resolve to the c:\target on [color=#0000FF:344wty4g]PC-A[/color:344wty4g].

    May be the network case is unlikely to be useful, so SymbolicLink is ok for this C1 purpose.
    0
  • Alain Decamps
    Thanks

    This is something that I would love to be in C1 native. (Even if the "SSD metadata copies" are read only aka a cache like copy that is disposable)
    0

Post is closed for comments.