Windows 10 Virtual Machine cd issue with executable compiled with matlab R2016a

Hi,

I've compiled a set of matlab functions using Matlab 2016a into a executable file to run on a server Virtual Machine with Windows 10 installed. All the development and testing work before compiling the code was done in Windows 7 and all went ok. Now when I run the executable in Windows 10 I get a MATLAB:cd:NonExistentDirectory when trying to access a mapped drive on that machine. No sure what the problem is, but I can access the same folder in matlab using the full network path. It must be something related to the mapped drive. Is this an issue in matlab? Is there a fix?

Best

João

[Walter Roberson]

Does the mapped drive happen to be Microsoft OneDrive ?

[Joao]

Hi Walter! No. The VM has two drives one for the OS (C:) and one for data (E:). I'm using the one for data. I've mapped drive S: as E:\Myfolder\mytests\.

[Joao]

I've compiled a new version of the code replacing the mapped drive with the full directory path and it works ok! Neverthless if there is a fix which allows me to use a mapped drive it would save me a lot of time correcting all the functions.

[Walter Roberson]

Checking back historically, I see that the OneDrive issue I was thinking of started in R2017b and had to do with the Files On Demand feature of OneDrive -- so completely unrelated to whatever is triggering the problem for you.

[Greg]

Can you compile a simple test executable that displays the result of

isdir('S:')

I just tried the same in MATLAB for my router's attached thumb drive. It returned false until I used Windows Explorer to open the mapped drive letter. Before that, it was in the erroneous "disconnected" state.

[Joao]

Thanks Greg! I understood the issue here! I was using the same method to map a drive that I used in Windows 7: cmd command subst and this seems not to work properly on windows 10. I've now used the map network drive option on Windows Explorer using the \\localhost\MyFolder\Myfiledir location (its the way to map a disc drive as a network drive) and it is working fine!