This may well be a problem with my lack of experience with either TCMD (the latest version I've used until now was 18 briefly but mainly 14) or Windows 10 (I avoided it as long as possible) but I'm seeing this odd behaviour with drives created by NET USE.
1) If I do something like
NET USE P: C:\DRIVEP
in a TCMD shell, exit the shell and open a new one the drive Q is still there but it isn't seen by CMD shells or other programs like the DOPUS Explorer replacement and it doesn't survive a reboot.
2) If I do the NET USE in a CMD shell then it's seen by other processes but NOT TCMD and it does survive a reboot.
Nothing I've seen before explains why this is happening nor gives me any idea how to deal with it.
Can someone educate me? :)
1) If I do something like
NET USE P: C:\DRIVEP
in a TCMD shell, exit the shell and open a new one the drive Q is still there but it isn't seen by CMD shells or other programs like the DOPUS Explorer replacement and it doesn't survive a reboot.
2) If I do the NET USE in a CMD shell then it's seen by other processes but NOT TCMD and it does survive a reboot.
Nothing I've seen before explains why this is happening nor gives me any idea how to deal with it.
Can someone educate me? :)