Slalom, no, because in Windows 10 you have network places since mapping drives is from 1990.
however, I did map a network drive, pointing Ripbot temp folder to it, launching it and finding it could not access the shared drive because it insists on running in the elevated environment, mapping the drive in the elevated environment. adding a job, pressing the go button, and watching it error out...
Just as I expected, the EncodingClient can't share a mapped drive! it errors out immediately after copying the tools there
so what I am asking for is that the temp location can be \\server\share. and then the encoding client can use that as the shared location for all of the files and it can skip trying to share a folder on the machine in that instance...
doing it this way will take all I/O load off of the machine running ripbot, except managing the encodingservers and it's own encoding tasks, and put it on a device made to handle it--the NAS box...
|