We have a legacy application that can only read and write to physical drives. If we point it to a mapped network drive, it does not work. I've tried subst
, mklink
and net use
to no avail.
Is there a program that can create a virtual hard drive on Windows 10 (using drivers)? Then, allow me to specify where this virtual drive should get its data from? In this case, a networked drive.
Edit: iSCSI Target by Daemon came pretty close, but can't seem to provide an iSCSI target that is backed by a network drive.
Edit 2: This question proses the question in a different way. It contains useful information.
Edit 3: Haha, oh no. THE man himself suggests it's a bad idea:
The next time someone tries to sell you a programming product that lets you access network resources the same was as you access local resources, run full speed in the opposite direction.