Hi Bob



 BL> It was the idea I liked, not the execution. He should have

 BL> added "c:" and "cd\" lines as well, to return
to the root

 BL> directory (or wherever)



 RM> In some cases that's an irritation, I sometimes want to stay

 RM> put when I leave an app, or return to the dir where I started

 RM> (this tends to be app dependent). Besides, what I wrote was but

 RM> a crude translation from the original 4dos...



 BL>   At the risk of setting you off,



If I wasn't an even tempered tolerant person I'd tell you to do

something that only you could find anatomically possible. I refuse

to rise to your bait. Absolutely. Positively. Oh well, if you

really insist,



 BL> I'd just like to say that 4DOS

 BL> sucks, for the record. I bought Norton 7.0 which included NDOS and it's

 BL> a total wank. The idea of improving DOS is insane.



 BL>   It's like improving a turd... no matter what you do it still stinks.



1. NDOS was always a version or two behind 4dos.



2. If you no longer live in turdland (dos), read no further. If,

however, you like your turds tastier, read on.



The individual 4dos extras are mostly trivial, but there are just

so many of them that they become addictive. A few of my faves:



Aliases: similar to Doskey aliases, but: Can be defined in a text

file, instead of a batch file. Can be called from a batch file -

try that with vanilla dos. Can use the ^ linebreak char, so a small

multiline batch file can be an alias. Eg, to save the current

working directory, jump to a directory on (maybe) another drive,

run a program (passing to it all parameters passed to the alias),

then return to the current working dir, try this alias:



  fred=set aa=%_cwd^cdd c:\apps\fred^fred %&^cdd %aa^unset aa



Keystack: potent little tsr that can stack up keystrokes before

launching a dos program. Very nice for killing boring intro

screens, entering opening passwords, or entering repetitive keys at

the beginning of a program. I've used it at work to add a weekly

correction to our fileserver's slow clock by injecting the required

commands into the rconsole program.



Filename completion: If the file STUFFXYZ.EXE is in the current

dir, then if I type S, 4dos would look for an executable

file starting with S and fill in the command line if it found one.

If I type ST it would look for executables starting with ST.

If I type COPY ST it would look for all files, not just

executables, starting with ST. This applies to subdir changing,

too: cd is optional, typing dos\ is the same as typing cd dos, and

typing d can call up dos\ as well as dog.exe .



Command Recall: In dos, if Doskey is loaded, hitting UpArrow will

step up through recent keyboard entries. In 4dos, filename

completion rules apply: if I type DI, it will step through

recent keyboard commands that started with DI.



I use the above two so often that I feel partly strangled at a

vanilla dos prompt.



Dir: filenames shown by the dir command can be coloured according

to their extension. My setup does exe and com in yellow, bat&btm in

blue, dat&txt&doc in red, directories in ltblue on grey, and so on.

Sounds like a wank, but speeds up dir browsing heaps.



 BL>   But I do like your batch file idea.



Remove C:\ from your path while you're at it. Command.com should

know where to find itself, nothing else there should need to be on

the path.



Cheers



--- PPoint 1.88