Attempting to create a hard link fails when the source files are on a network drive

[milleniumbug]

If possible, fall back to regular copying.

[DrWhoCares]

I thought I had something in place to handle this, but I believe I'm conflating it with a separate network drive issue from before the refactor.
I'll fix this sometime after work today.
To be clear, what is the intended behavior you are looking for?

Copy to destination drive, process, and then move to the output destination?

[milleniumbug]

Copy to destination drive, process, and then move to the output destination?

I think this one is the most likely one. Not sure what are you using hard links for, so it's hard for me to tell, as I'm not yet familiar with this program, using it for a joint project with Danke furs Lesen.

[DrWhoCares]

Hardlinks because Windows doesn't allow softlinks in an unelevated process unless you activate developer mode (which is relatively new). Hardlinks avoid excess copying of files on the harddisk.

Specifically, hardlinks result in no copies being made until necessary. Imagemagick automatically converts a hardlinks into a new copy when using mogrify. So a copy is only ever made when it's being processed.

If you want to process 500 files, instead of making 500 copies, and then processing after all copies are made, only to find out that it fails after the first one, instead you make 500 hardlinks, and fail on the first one.

Of course, this is all provided that hardlinks can be made. Certain configurations of settings will make copies instead.

[DrWhoCares]

It looks like I'm going to need more information, as I did actually fix this, in that I have a check that will cause the file to be copied if the image's root drive path is not the same as the output's.