Replies

Gentlemen,

Thanks for the info. I skipped from Windows 98SE to XP, so I missed the new environment variables in Windows 2000. But I remember the CHDIR (aka CD) command from way back in MS-DOS 2.11, imported along with the concepts of directories and redirection from unix. I think the DATE and TIME commands were in MS-DOS one point something-or-other, but in those days, I was using CP/M3.0 on a Z80.

Gentlemen,

Thanks for the info. I skipped from Windows 98SE to XP, so I missed the new environment variables in Windows 2000. But I remember the CHDIR (aka CD) command from way back in MS-DOS 2.11, imported along with the concepts of directories and redirection from unix. I think the DATE and TIME commands were in MS-DOS one point something-or-other, but in those days, I was using CP/M3.0 on a Z80.

Hey, that’s neat! The CD variable saves the gyrations with PROMPT that I’ve been using to accomplish the same thing. But I hadn’t seen it when looking with the SET command. How did you come across this variable? And is it new with XP?

Hey, that’s neat! The CD variable saves the gyrations with PROMPT that I’ve been using to accomplish the same thing. But I hadn’t seen it when looking with the SET command. How did you come across this variable? And is it new with XP?

John, those are interesting ideas. I think I’ll play with them when I get a little time. Thanks.

John, those are interesting ideas. I think I’ll play with them when I get a little time. Thanks.

I should have thought of SUBST. I presume that CD is an environment variable that you populated by manipulating the PROMPT command.

I should have thought of SUBST. I presume that CD is an environment variable that you populated by manipulating the PROMPT command.

Bruce and BigAl,

Thanks for the suggestion. However, (unless I am missing your point) while switching to the root directory would simplify the prompt, that would be at the cost of being able to work in different directories. Just setting the prompt to $g would be more practical.

I’ve been working a fair amount in FreeBSD lately, and was just getting spoiled by the flexibility of the unix csh and sh shells. It may be that Windows can’t easily satisfy my wish list. My work in the command box under Windows is pretty limited, so this is a relatively minor issue.

Bruce and BigAl,

Thanks for the suggestion. However, (unless I am missing your point) while switching to the root directory would simplify the prompt, that would be at the cost of being able to work in different directories. Just setting the prompt to $g would be more practical.

I’ve been working a fair amount in FreeBSD lately, and was just getting spoiled by the flexibility of the unix csh and sh shells. It may be that Windows can’t easily satisfy my wish list. My work in the command box under Windows is pretty limited, so this is a relatively minor issue.

Yes, thanks. There is a lot of information there, but I hadn’t found anything that suggested an answer to my wish list. I’ll keep looking. I’m also perusing the references from the April Windows Command Processor – I want to learn it (SP1) thread, such as the Allenware tutorial (for Win9x) and Labmice

Yes, thanks. There is a lot of information there, but I hadn’t found anything that suggested an answer to my wish list. I’ll keep looking. I’m also perusing the references from the April Windows Command Processor – I want to learn it (SP1) thread, such as the Allenware tutorial (for Win9x) and Labmice

Hans, thank you very much! SendKeys was the right approach.
VBA Help said that it would accept control key inputs, so I wasted time trying to get into the Print dialog using ^P. When I finally switched to %FP (alt-FP), it worked fine.

Hans, thank you very much! SendKeys was the right approach.
VBA Help said that it would accept control key inputs, so I wasted time trying to get into the Print dialog using ^P. When I finally switched to %FP (alt-FP), it worked fine.

Thanks, that worked fine. I should have thought of the Properties window.