Unable to compile - info

2 views
Skip to first unread message

Joe Berry

unread,
Oct 2, 2009, 11:29:36 AM10/2/09
to sem...@googlegroups.com

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

Marshall Fryman

unread,
Oct 2, 2009, 11:45:41 AM10/2/09
to sem...@googlegroups.com
Joe -

Not sure if this is germane or not but I've discovered that SUBST does not hold between elevated and non-elevated processes. For instance, if I open a CMD prompt in normal mode and SUBST J: C:\somefolder, all normal mode CMD prompts and applications can see the J drive. If I open an elevated process (i.e., run as admin), J: doesn't appear. Normal mode and elevated mode work in completely separate spaces. The same also holds true for NET USE.

HTH,
Marshall

Joe Berry

unread,
Oct 2, 2009, 12:03:22 PM10/2/09
to sem...@googlegroups.com

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

 


Marshall Fryman

unread,
Oct 2, 2009, 12:14:39 PM10/2/09
to sem...@googlegroups.com
Joe -

Not sure about Total Commander, I don't use it.

On my Vista x64 box, if I open a normal mode command prompt and type in subst j: c:\apps, that command prompt then has a J drive. All subsequent normal mode command prompts (and applications) also have a J drive. If I then r-click on the command prompt and select Run As Administrator, there is no J drive. Likewise, any Admin mode program does not have a J drive. I have to re-subst the drive in Admin mode. There are literally two separate views of the file system. One from normal mode and one from administrator mode.

m

Joe Berry

unread,
Oct 2, 2009, 12:23:17 PM10/2/09
to sem...@googlegroups.com

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.

Marshall Fryman

unread,
Oct 2, 2009, 12:29:25 PM10/2/09
to sem...@googlegroups.com
Really? Both my Vista x64 desktop and my Vista x32 laptop have exactly the same behavior. In my case, I always subst the drives inside the command prompt. Where are you substing them?

Joe Berry

unread,
Oct 2, 2009, 8:25:17 PM10/2/09
to sem...@googlegroups.com

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.

Reply all
Reply to author
Forward
0 new messages