FileBot

attempt 1 at keeplinking:
log: https://pastebin.com/9ZWzCvGr
screenshot: https://i.imgur.com/XwtBoUf.jpg

atempt 2 at keeplinking:
log:https://pastebin.com/yC2vt0zw
screenshot:https://i.imgur.com/y9J91Mc.jpg

1.
I've never seen this before, so unfortunately I've got no clue here either:
Since the keyword privilege appears in the error message, running FileBot as Administrator is worth a try. AFAIK, Windows allows certain filesystem operations only as Administrator.


I'd generally not expect Unix things like symlinks and hardlinks to work well on Windows, especially if we're working with a remote file system instead of a local NTFS drive.


A Google search might reveal a few work arounds you can try. But if you're using a Linux-based NAS, then I'd just run FileBot locally on that NAS if you need to symlink / hardlink / reflink / etc.


EDIT:

This error message might give us a hint: Presumably, as suggested by this warning message, the source file path and the destination file path are on different root drives, which means FileBot must create absolute path symlinks. If your destination drive is on a remote NAS, possibly even Linux based, then creating a symlink for an absolute Windows file path, on a Linux system, makes absolutely no sense, and is likely rejected by the file system with some obscure error message.

Yes, the source path and destination path are on different drive letters on the same (windows 10) system

I did notice the first error disappeared when i tried the keeplink function with the source and destination on the same drive, though it's not ideal since the destination will typically be on a different drive

as for the 'required priviledge' error, i ran filebot as admin, but the drag and drop function would not work: https://streamable.com/zuz4c

jonsnuh wrote: ↑24 Jun 2019, 07:00 Yes, the source path and destination path are on different drive letters on the same (windows 10) system

Sounds like copy is the way to go then. Links, conceptually, aren't ideal if you're dealing with different file systems, or maybe even different machines.

jonsnuh wrote: ↑24 Jun 2019, 07:00 as for the 'required priviledge' error, i ran filebot as admin, but the drag and drop function would not work: https://streamable.com/zuz4c

I see. Windows does not allow inter-process-communication between processes of different users, and thus drag and drop doesn't work if FileBot is running as Admin and you're dragging in files from Explorer running as your user. You can either use the Load button to select files via FileBot, or run Explorer as Admin too.

rednoah wrote: Sounds like copy is the way to go then. Links, conceptually, aren't ideal if you're dealing with different file systems, or maybe even different machines.

The reason I want to do a keeplink is because i want to keep the torrents seeding and doing a copy is not ideal since I'd be needlessly using up extra storage space. Symlinks do work between different drives. I've used window's mklink command before to create symlinks between drives. I could do everything manually, but that would defeat the purpose of me having filebot -- I installed filebot to make my media management more or less automatic.

rednoah wrote: I see. Windows does not allow inter-process-communication between processes of different users, and thus drag and drop doesn't work if FileBot is running as Admin and you're dragging in files from Explorer running as your user. You can either use the Load button to select files via FileBot, or run Explorer as Admin too.

running explorer as administrator did not fix the issue of me being unable to drag and drop onto the filebot window. the load function also always gives this error: https://i.imgur.com/tTkkARg.jpg

1.
If you're using the CLI, then you can pass in your own custom script to perform the rename operation, i.e. you can use mklink that way:
viewtopic.php?f=4&t=4915


2.
devenv.exe is not part of FileBot as far as I know. In fact, I've never heard of this executable. According to Google, it's apparently part of Visual Studio.


3.
You can also use the GUI to move files, and then run a custom script in a second pass to generate all the symlinks you want via the history feature: This is bash code. You might need to translate to PowerShell or CMD on Windows. The idea is the same. Generate commands. Execute them.