Photo above shows Take Command running on @Macarlo's Warp 4 IDE
Take Command for OS/2 Revisited

In Affiliation CNET News.com with CNET, Inc.

=@MACARLO MICROSOFT=  =@MACARLO YAHOO=  =@MACARLO WEBALIAS=  =@MACARLO ALTAVISTA=

 


In Affiliation with Beyond.com

 Hi All.
Some OS/2 users requested an illustrated report about Take Command for OS/2 from JPS, developers of famous 4DOS and 4NT.I'm registered user of Take Command for OS/2 (purchased from Digital River Secure Server) and I used it everyday on my Warp 4 FP6 (note I'm using FixPak 6 because I need not another level of Fix; my Warp 4 is running really fine and I not reinstalled it since 1997!).
I mounted three IDEs on this environement: Java, C++ and Web Development. For this three IDEs I need Take Command! This soft really improves the command line on PM window and I take control on everithing I've here (actually I have installed and running just fine on this Warp above 200 applications (I'm  registered user of 212). Well, sincerelly I can said: If you are a developer on OS/2 Warp one of the most important tools for you is exactly Take Command!

@Macarlo
Team OS/2 Registered

READ ALSO

Take Command Update

 

What is Take Command
 
 Take Command for OS/2 is a new environment that lets you perform tasks easily under OS/2. You can use it to execute commands, start applications, and perform other work at the command line.

 In the past you may have accomplished some of these tasks by starting an OS/2  character-mode session or running 4OS2, JP Software's replacement character- mode command processor.

 In either case -- and especially if you are an experienced user of 4OS2 -- you'll find plenty of familiar features in Take Command.  You'll also find a lot that's new and different.

 While Take Command includes most of the command-line, batch file, and other capabilities provided by 4OS2, and goes well beyond those provided by CMD.EXE, the OS/2 environment places a few limitations on how Take Command operates.

 These limitations are minor -- for example, some keystrokes are interpreted differently to conform more closely to OS/2 conventions, and there are some considerations when running batch files or OS/2 aliases designed to work in character mode under a graphical program like Take Command.  All of these differences are covered in more detail under Take Command for 4DOS and 4OS2 Users.

 Take Command also offers a wide range of new OS/2 PM-related features which are not available in 4OS2 or CMD.EXE, including:

         *   A built-in scrollback buffer that lets you look back through the output from past commands.

         *   A standard OS/2 menu bar for access to many commonly-used Take Command
             features.

         *   A status bar showing memory and resource usage.

         *   A customizable tool bar that gives you quick access to commands and applications.

         *   Dialogs (accessible from the Options and Utilities menus) for editing environment variables, aliases, file descriptions, and startup parameters.

         *   High-speed, dialog-based file and text search (see "Search Files/Text" on the Utilities menu). The new FFIND command gives you the same capabilities at the Take Command prompt.

         *   Commands like ACTIVATE, MSGBOX, and QUERYBOX that allow you to use OS/2 features and control OS/2 applications from your batch files.
           
Starting applications
 
 Take Command offers several ways to start applications.  (For special considerations related to starting character-mode applications, see the next topic).

 First, you can simply type the name of any OS/2, DOS, or Windows application at the Take Command prompt.  As long as the application's executable file is in one of the standard
 search directories (see below), Take Command will find it and start it.  If you type the full path name of the executable file at the prompt the application will be started even if it is
 not in one of the standard search directories.

 Take Command offers two methods to simplify and speed up access to yourapplications.  
 One is to create an alias, for example:

         [c:\] alias myapp d:\apps\myapp.exe
 
 You can also use the Tool Bar To start frequently-used applications.  For example, a tool bar button named MyApp which invokes the command d:\apps\myapp.exe would accomplish the same thing as the alias shown above.

 You can use these methods together.  For example, if you define the alias shown above you can set up a tool bar button called MyApp and simply use the command myapp, which would then invoke the previously-defined alias.

 You can also start an application by typing the name of a data file associated with the application.  Take Command will examine the file's extension and run the appropriate application, based on Take Command's executable extensions.

 For additional flexibility, you can also start applications with the START command.  START provides a number of switches to customize the way an application is started.

 Searching for Applications

 When you start an application without specifying a path, Take Command searches for the application in the current directory and then all directories on the PATH.  (If you do enter an explicit path, Take Command will only look in the directory you specified.)

 If you enter a file name with no extension, Take Command will search each directory for a matching .COM, .EXE, .BTM, or .CMD file, then for a file matching a Take Command executable extension.  If no such file is found Take Command will move on to the next directory in the search sequence.

 Waiting for Applications to Finish

 When you start an application from the prompt, normally Take Command does not wait for the application to finish before returning to the prompt.  This allows you to continue your
 work in Take Command while the application is running.  You can change this default behavior for applications started from the prompt, using the ExecWait directive in TCMDOS2.INI, or the Wait for Completion option on the Options 2 page of the configuration
 notebook.  These options do not affect batch files; Take Command always waits for applications started from batch files.

 Character-mode applications which run inside the Take Command window are an exception to this rule.  Take Command always waits for such applications to finish before displaying a new prompt, regardless of the ExecWait setting. For more information see the next section, on starting character-mode applications.

 You can also force Take Command to wait for an application to finish with the START command with the /WAIT switch.  START can also control many other aspects of how your applications are started.

You can purchase Take Command for OS/2 from Atlantic-Coast, at:

http://www.atlantic-coast.com/   

 


Compare prices on more than 100,000 products!

Search our product directory.

 

CNET Shopper. Click here.

@Macarlo, Inc.
@Macarlo's Shareware & Web
OS/2
Java Lobby Member
Java Site Accredited

[TOP] [HOME] [INDEX]