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?
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.
On Fri, Oct 2, 2009 at 8:29 AM, Joe Berry <joe-be...@comcast.net> wrote: > 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?
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
_____
From: semware@googlegroups.com [mailto:semware@googlegroups.com] On Behalf Of Marshall Fryman Sent: Friday, October 02, 2009 10:46 AM To: semware@googlegroups.com Subject: [TSE] Re: Unable to compile - info
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
On Fri, Oct 2, 2009 at 8:29 AM, Joe Berry <joe-be...@comcast.net> wrote:
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?
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.
On Fri, Oct 2, 2009 at 9:03 AM, Joe Berry <berry....@comcast.net> wrote: > 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
> ------------------------------
> *From:* semware@googlegroups.com [mailto:semware@googlegroups.com] *On > Behalf Of *Marshall Fryman > *Sent:* Friday, October 02, 2009 10:46 AM > *To:* semware@googlegroups.com > *Subject:* [TSE] Re: Unable to compile - info
> 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
> On Fri, Oct 2, 2009 at 8:29 AM, Joe Berry <joe-be...@comcast.net> wrote:
> 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?
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.
From: semware@googlegroups.com [mailto:semware@googlegroups.com] On Behalf Of Marshall Fryman Sent: Friday, October 02, 2009 11:15 AM To: semware@googlegroups.com Subject: [TSE] Re: Unable to compile - info
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
On Fri, Oct 2, 2009 at 9:03 AM, Joe Berry <berry....@comcast.net> wrote:
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
_____
From: semware@googlegroups.com [mailto:semware@googlegroups.com] On Behalf Of Marshall Fryman Sent: Friday, October 02, 2009 10:46 AM To: semware@googlegroups.com Subject: [TSE] Re: Unable to compile - info
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
On Fri, Oct 2, 2009 at 8:29 AM, Joe Berry <joe-be...@comcast.net> wrote:
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?
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?
On Fri, Oct 2, 2009 at 9:23 AM, Joe Berry <berry....@comcast.net> wrote: > 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.
> *From:* semware@googlegroups.com [mailto:semware@googlegroups.com] *On > Behalf Of *Marshall Fryman > *Sent:* Friday, October 02, 2009 11:15 AM > *To:* semware@googlegroups.com > *Subject:* [TSE] Re: Unable to compile - info
> 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
> On Fri, Oct 2, 2009 at 9:03 AM, Joe Berry <berry....@comcast.net> wrote:
> 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
> ------------------------------
> *From:* semware@googlegroups.com [mailto:semware@googlegroups.com] *On > Behalf Of *Marshall Fryman > *Sent:* Friday, October 02, 2009 10:46 AM > *To:* semware@googlegroups.com > *Subject:* [TSE] Re: Unable to compile - info
> 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
> On Fri, Oct 2, 2009 at 8:29 AM, Joe Berry <joe-be...@comcast.net> wrote:
> 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?
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.
_____
From: semware@googlegroups.com [mailto:semware@googlegroups.com] On Behalf Of Marshall Fryman Sent: Friday, October 02, 2009 11:29 AM To: semware@googlegroups.com Subject: [TSE] Re: Unable to compile - info
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?
On Fri, Oct 2, 2009 at 9:23 AM, Joe Berry <berry....@comcast.net> wrote:
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.
From: semware@googlegroups.com [mailto:semware@googlegroups.com] On Behalf Of Marshall Fryman Sent: Friday, October 02, 2009 11:15 AM
To: semware@googlegroups.com Subject: [TSE] Re: Unable to compile - info
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
On Fri, Oct 2, 2009 at 9:03 AM, Joe Berry <berry....@comcast.net> wrote:
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
_____
From: semware@googlegroups.com [mailto:semware@googlegroups.com] On Behalf Of Marshall Fryman Sent: Friday, October 02, 2009 10:46 AM To: semware@googlegroups.com Subject: [TSE] Re: Unable to compile - info
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
On Fri, Oct 2, 2009 at 8:29 AM, Joe Berry <joe-be...@comcast.net> wrote:
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?
|
