-=> Quoting James Bradley to Jean Parrot <=-

Sounds like LONG AGO when I was running aprox 60 megs of programs 
and data on a 40 meg hard drive. 
All but the most used programs were kept in ZIP archives, and run 
from BAT files to unzip them, then update the archive before 
deleting the directory. 


 JB> Oh, you'd be surprized! Save or create a text file called
"e.bat" on
 JB> your desktop. In that file type the word "exit" and make
sure there's
 JB> a carridge return at the end. Save the file as a text file, and you're
 JB> a batch file programer!

 JB> (We used an environment variable called a PATH statement, where you
 JB> could congregate all your utilities, and batch files, but I suspect
 JB> the desctop would be just as convenient. )

 JB> Now, when you have "shelled to the OS", you can stop that
by involking
 JB> "e" and that will type "exit" for you.
Likewise, I have a batch file
 JB> that:

 JB> d:
 JB> cd\w
 JB> win.com

 JB> and I call it "C:\bat\w.bat". "C:\bat" is in my
PATH, and the first
 JB> place DOS looks for my executable files. When I'm tooling around in
 JB> the CLI, and I want to start Windows, I type "w", to change to the
 JB> drive, change to the directory, and then start "win.com" all by the
 JB> batch file.

 JB> Dead simple, and massivly handy. If I have DOS games I'd like to play,
 JB> I have one "games.bat" file that then calls other batch files to
 JB> change to different directories under my games directory, then execute
 JB> the game proper. Once I stop the game, it goes back to the
"games.bat"
 JB> file asking if I'd like to play a different game, or stop the file.


 
___ Blue Wave/386 v2.30
--- Platinum Xpress/Win/WINServer v3.0pr5a