I still use the old DOS command SUBST to make deeply imbedded folders become a drive letter – old habits die hard. Anyway When I open a macro on a SUBSTituted drive and attempt to compile nothing happens. When I navigate to the folder the long way all works as advertised.
As an example, I made my downloads directory on Vista drive A:. When I compile a macro by loading the file A:\SomeMacro.s and attempt to compile nothing happens; however, when I load c:\Users\Joe\Downloads\SomeMacro.s all works fine.
I cannot find anything else that is adversely affected in TSE by using SUBST. Just wondered if anyone knew why?
Joe Berry
Really makes it more of a puzzle. I can load a file from a drive that I have set using Net Use and all works well.
I SUBST my drives as a startup batch file. I run Total Commander as admin and can see and use the drive. Is that what you were referring to?
Joe
I also have Vista x64, but don’t share that behavior. Whether I run a program as administrator or normal mode I have my SUBST drives after once setting them either at startup or later.
I set mine from a command file at startup or run it later. I have several different setups to mimic my work at client sites.