From: Klaus Meinhard
Subject: win95 dos prompt properties
Date: 1998/04/16
Message-ID: #1/1
Distribution: fido
References:
Organization: But honey, we can afford it, I sold your car!
Newsgroups: fido.4dos
Hallo Vic
VB> In win95 I have a shortcut desktop icon setup to run 4dos, because for
VB> some reason even though it's the primary shell it doesn't automatically
VB> run when I open a dos prompt.
VB>
VB> Doing it this way I'm also able to open a normal MSdos box from win95
VB> using the normal dos prompt menu option. But the only problem I had
VB> with this was MSDOS didn't like my 4dos prompt too much.
Exactly what I found on my system...
VB> In the prog
VB> properties for the dos prompt where the command line etc is specified
VB> there's a section to setup a batch file which is automatically run. I
VB> thought I'd use this to change the prompt to something command.com can
VB> handle. Problem is that whenever I specify anything here 4dos always
VB> starts instead of command.com, no matter what!
VB>
VB> It doesn't matter that command.com is specified as the program command
VB> line, as soon as I specify a batch file/command to be run 4dos starts
VB> instead of command.com! The only way I've found to get around this is
VB> to use the /K switch after the command line. Is this a win95 problem or
VB> something wrong with how I've setup 4dos?
Both BTM and BAT files are set up as BATFILE in your registry and bound to
4DOS.COM, so 4DOS is called as soon as you try to execute them as a command
instead of a parameter for CC... There's no way I found to eat that cake _and_
have it...
VB>
VB> Rgds, Vic
VB>
VB>
VB>
VB> --- GoldED/386 2.50+43UK1
Gr�sse aus Ostrhauderfehn,
*Klaus Meinhard*
VB> * Origin: The Bates Motel! Bolton, UK. (2:250/167)
|