PC Online 1997 October

home *** CD-ROM | disk | FTP | other *** search

/ PC Online 1997 October / PCO1097.ISO / FilesBBS / OS2 / TCOS2200.ARJ / TCOS2200.ZIP / TCMDOS2.TXT < prev next >

Wrap

Text File | 1997-07-30 | 175.9 KB | 3,822 lines

Take Command/16 for Windows 3.x *** Take Command/32 for Windows NT and Windows 95 *** Take Command for OS/2 Introduction and Installation Guide Developed By Rex Conn and Tom Rawson Documentation By Hardin Brothers, Tom Rawson, and Rex Conn Published By JP Software Inc. P.O. Box 1470 East Arlington, MA 02174 U.S.A. (617*) 646-3975 fax (617*) 646-0904 (*Use area code 781 beginning Sep 1, 1997) ACKNOWLEDGMENTS We couldn't produce a product like Take Command without the dedication and quality work of many people. Our thanks to: JP Software Staff: Christine Alves, Mike Bessy, Janet Casey, Ed Lucas, Ellen Stone. On-line Support: The staff at CompuServe's PC-NET, Software Tool and Die (Brookline, MA) and TIAC (The Internet Access Co., Bedford, MA); Brian Miller and Tess Heder of Channel 1 BBS, Cambridge, MA. Beta Test Support: The sysops of CompuServe's CONSULT forum. Beta Testers: We can't list all of our beta testers here! A special thanks to all of you who helped make Take Command elegant, reliable, and friendly. The following tools are used in creating and maintaining Take Command: Compilers: Watcom C, Microsoft C, Microsoft Macro Assembler Editors: Visual Slick-Edit (MicroEdge Inc.), Boxer (Boxer Software) Debuggers: Watcom Debugger (Watcom), Win-ICE and Bounds Checker (Nu-Mega Technologies) Version Control: PVCS (Intersolv) Documentation: Microsoft Word for Windows Copyright 1997, JP Software Inc., All Rights Reserved. Take Command is a registered trademark of JP Software Inc. 4DOS, 4OS2, and 4NT are JP Software Inc.'s trademarks for its family of character-mode command processors. JP Software, jpsoft.com, and all JP Software designs and logos are also trademarks of JP Software Inc. Other product and company names are trademarks of their respective owners. 07-97 CONTENTS ------------------------------------------------------------------ CONTENTS Introduction...............................................1 How to Use This Manual.................................3 Contacting JP Software.................................4 Technical Support......................................5 Before You Contact Us..............................5 Electronic Support.................................7 Telephone Support..................................7 Registration and Upgrade Information...................8 Chapter 1 / Introducing Take Command......................10 The Take Command Window...............................10 Built-In Commands.....................................11 The Command Line......................................14 Working with Windows and OS/2.........................16 Configuration.........................................16 Aliases and Batch Files...............................17 Chapter 2 / Installation..................................20 Installing an Upgrade.................................20 Starting the Installation Software....................20 Installation of an Electronically Purchased Copy..21 Installation from a JP Software Diskette or CD-ROM21 Installation of a Downloaded Trial Copy...........23 Uninstalling the Program..............................25 Chapter 3 / The Help System...............................26 Using the Help System.................................26 Important Help Topics.................................27 Chapter 4 / Configuration (All Products)..................28 Starting Take Command.................................28 Command Line Options..................................28 Creating or Modifying Startup Files...................31 Chapter 5 / Take Command/16 Configuration and Notes.......33 Take Command/16 Installation Notes....................33 Manual Installation of Take Command/16................33 Extracting or Copying the Program Files...........34 Branding" Take Command/16.........................34 Updating Windows Files for Take Command/16........35 Take Command/16 Files and Directories.............36 Installing Take Command as the Windows Shell......37 Creating Desktop Objects for Take Command/16..........38 Take Command and DOS Applications.....................38 Caveman...........................................39 Uninstalling Take Command/16 Manually.................39 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / i CONTENTS ------------------------------------------------------------------ Chapter 6 / Take Command/32 Configuration and Notes.......41 Take Command/32 Installation Notes....................41 Manual Installation of Take Command/32................41 Extracting or Copying the Program Files...........42 Branding" Take Command/32.........................43 Installing CTL3D under Windows NT 3.5.............43 Updating the Registry.............................44 Take Command/32 Files and Directories.............45 Creating Desktop Objects for Take Command/32..........46 Creating Explorer Shortcuts.......................46 Creating Program Manager Items....................48 Character-Mode Applications...........................48 Caveman...........................................49 Uninstalling Take Command/32 Manually.................50 Chapter 7 / Take Command for OS/2 Configuration and Notes.51 Take Command for OS/2 Installation Notes..............51 Manual Installation of Take Command for OS/2..........51 Extracting or Copying the Program Files...........51 Branding" Take Command for OS/2...................52 Updating CONFIG.SYS...............................53 Take Command for OS/2 Files and Directories.......54 Creating Desktop Objects for Take Command for OS/2....55 The Take Command for OS/2 Help System.................56 Character-Mode Applications...........................57 Uninstalling Take Command for OS/2 Manually...........57 Index.....................................................59 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / ii INTRODUCTION ------------------------------------------------------------------ INTRODUCTION Welcome, and thanks for purchasing Take Command! We developed Take Command to bring the power and convenience of our popular 4DOS, 4NT, and 4OS2 programs to the Windows and OS/2 desktops. Whether you are a computer novice or an experienced user, Take Command will help you get the most out of your computer system. You're probably already familiar with graphical applications running under Windows or OS/2, and with the command line, but you may not be used to seeing them combined in one product. Most graphical applications offer limited command-line capability at best, and most command-line utilities aren't designed for a graphical environment like Windows or the OS/2 desktop. We designed Take Command to give you the best of both worlds. You'll probably find it most useful when you need to perform tasks like managing your hard disk, scripting a series of steps with an alias or batch file, or starting applications. There are graphical utilities that perform some of these tasks, but often you may find it more convenient or productive to perform them from the command line. Take Command can use fewer resources than starting a traditional character-mode command-line session, and, unlike a traditional command line session, it looks and feels like the other graphical programs you use. Take Command also offers a host of features that couldn't exist at all in a command-line utility. For example, you can pop up simple dialogs from a batch file, pass keystrokes to other graphical applications, and use a dialog to find files or text on any of your disks. Take Command comes in three different versions, and each works on different operating system platforms: * You can use Take Command/16 with Windows 3.x, Windows for Workgroups, and Windows sessions in OS/2. If you want full command-line control of Windows, you can also use Take Command/16 as your Windows shell, replacing Program Manager. This approach isn't for everyone, but if it's the way you like to work you'll find that Take Command is up to the task. * You can use Take Command/32 with Windows 95 and with Windows NT version 3.5 and above. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 1 INTRODUCTION ------------------------------------------------------------------ * You can use Take Command for OS/2 with OS/2 Warp 3.0, 4.0, and above. If you are familiar with the traditional command prompt, or with 4DOS, 4OS2, or 4NT, you won't have to change your computing habits or unlearn anything to use Take Command. If you know how to use commands to display a directory, copy a file, or start an application program, you already know how to use Take Command. And if you are a 4DOS, 4OS2, or 4NT user, you already know how to use most of the advanced features that we have built into Take Command. You can even use many of your 4DOS or 4OS2 batch files with Take Command (see the Reference Manual or the online help for tips about making batch files work properly in both environments). Once you have Take Command installed, you can learn its new features at your own pace. Each program has more than 90 commands and hundreds of enhanced features, but you don't have to learn them all, or learn them all at once. Relax, enjoy Take Command's power, and browse through the manuals occasionally. Press the F1 key whenever you need help. Take Command will soon become an essential part of your computer, and you'll wonder how you ever got along without it. We are constantly working to improve Take Command. If you have suggestions for features or commands that we should include in the next version, or any other way we could improve our product, please let us know. Many of the features in Take Command were suggested by our users. We can't promise to include every suggestion, but we really do appreciate and pay attention to your comments. Take Command/16, Take Command/32, and Take Command for OS/2 are related programs that work in graphical or desktop mode. If you also work in character (text) mode, we offer three command-line programs that include most of the power of Take Command. * 4DOS runs under all versions of MS-DOS and PC-DOS from 3.1 through 7.1 and above ("MS-DOS 7" is the DOS portion of Windows 95). You can also use it with all versions of Novell DOS and DR DOS (an older name for the same product) from 3.4 through 7.0 and above, and in DOS sessions started under Windows 3.0 or 3.1, Windows 95, OS/2 2.x, and OS/2 Warp 3 and 4. * 4OS2 runs under OS/2 2.1 and above, and OS/2 Warp 3 and 4. * 4NT runs under Windows NT 3.5, 3.51, 4.0 and above. You can use these products to maintain a common working environment and run the same commands, batch files, and aliases ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 2 INTRODUCTION ------------------------------------------------------------------ from Windows, the OS/2 desktop, and from the character-mode command line. Additional products for use on the same system are available at a discounted price for Take Command users. Our JP CD Suite includes all six products. Licenses for multiple systems are also available. Contact your software reseller or JP Software for more information. How to Use This Manual This manual is only one part of the documentation that you will need for Take Command. It introduces the product and will help you install it correctly on your computer. It also gives you specific information about using the program in your particular environment (for example, under Windows 95 or OS/2). The second part of our documentation is the Reference Manual and the online help. They contain complete information about the commands and features of Take Command. You should start with this introductory manual whether you are new to our programs or you are upgrading from a previous version. Once you have successfully installed Take Command you can move on to the Reference Manual or the online help for detailed information on commands, features, and configuration. The first three chapters of this manual introduce the products and help you install the program and its built-in help system. Chapters 4 _ 7 contain additional details about each product and operating environment. We encourage you to review the material in the later chapters to see what applies to you. Most of the first part this manual describes commands and features which are available in all three versions of Take Command. When we need to discuss the features or behavior of a single product, we mention it specifically in the text. When an entire paragraph or section applies to a specific product, we use marginal text to identify that product: TC16 marks sections that apply only to Take Command/16 for Windows 3.x, Windows for Workgroups, and Windows sessions in OS/2. TC32 marks sections that apply only to Take Command/32 for Windows 95 and Windows NT. TCOS2 marks sections that apply only to Take Command for OS/2. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 3 INTRODUCTION ------------------------------------------------------------------ Each of our products also includes complete online help for all commands. Our online help provides much of the same information that is available in this manual and the Reference Manual, but in an electronic form which you can access quickly. The online help also includes details about changes in the latest version of our products, compatibility with other products, and additional technical and reference information. See page 26 for more information about the online help. Finally, be sure to check README.TXT for last-minute notes on the current release, or if you are installing a downloaded update to Take Command. Contacting JP Software You can contact JP Software at the following addresses and numbers. Our normal business hours are 8:30 AM to 5:00 PM weekdays, eastern US time except on holidays. Please review the following section before contacting us for technical support. Address: JP Software Inc. P.O. Box 1470 East Arlington, MA 02174 USA Main number: (617*) 646-3975 Fax: (617*) 646-0904 Order Line: (800) 368-8777 (US / Canada, orders only) Support Line: (617*) 646-0798 (US / Canada, see below) * Our area code changes to 781 effective September 1, 1997 Internet: World Wide Web: http://www.jpsoft.com/ Sales / Customer Service: sales@jpsoft.com Technical Support**: support@jpsoft.com File downloads via FTP: For the simplest access to JP Software files use our web site. For direct FTP access connect to ftp.std.com and look in the /vendors/jpsoft directory, and its subdirectories. CompuServe: Sales / Customer Service: 75020,244 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 4 INTRODUCTION ------------------------------------------------------------------ Technical Support and File Downloads**: GO JPSOFT or GO PCVENB, section / library 10 (JP Software), User ID 75300,1215. BBS Downloads: Channel 1 BBS, Cambridge, MA, 617-349- 1300 for 28.8K, 617-354-3137 for 33.6 K. Join the "free files" conference (J FREE or J 5 at the main menu) for JP Software file downloads. ** Technical support messages should be sent as standard ASCII text. Please do not transmit attached files, binary files, screen images, or any file over 10K bytes in size to any of our electronic technical support addresses unless asked to do so by our support staff. For access to JP Software files use our web site, CompuServe library, or the Channel 1 BBS as listed above. Our files may also be available from other online locations, but we can't promise that files downloaded from other sites will be the same as files provided directly by us, or that they will be up to date. Technical Support Before You Contact Us Before contacting us for support, please check this manual, the Reference Manual, the online help, and other documentation for answers to your question. If you can't find what you need, try the Index. If you're having trouble getting Take Command to run properly, see the Troubleshooting, Service, and Support topic in the online help for any relevant information, and look through the README.TXT file for any last-minute information for your product. If you do need to contact us for support, it helps if you can give us some basic information. The first four items listed below are essential for us to be able to understand and assist you with your problem: * What environment are you working in? This includes the operating system version are you using, the version of the JP Software product involved, and related information such as network connections and the name and version number of any other software which appears to be involved in the problem. Use the ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 5 INTRODUCTION ------------------------------------------------------------------ VER /R command to determine the Take Command version and operating system version. * What exactly did you do? A concise description of what steps you must take to make the problem appear is much more useful than a long analysis of what might be happening. * What did you expect to happen? Tell us the result you expected from the command or operation in question, so that we understand what you are trying to do. * What actually happened? At what point did the failure occur? If you saw an error message or other important or unusual information on the screen, what exactly did it say? * Briefly, what techniques did you use to try to resolve the problem? What results did you get? * If the problem seems related to startup and configuration issues, what are the contents of any startup files you use (such as CONFIG.SYS, AUTOEXEC.BAT, TCSTART, TCEXIT, and the .INI file), any batch files they call, and any alias or environment variable files they load? * Can you repeat the problem or does it occur randomly? If it's random, does it seem related to the programs you're using when the problem occurs? If you have a problem with a batch file or complex alias, please contact us electronically if possible. Include an exact copy of the batch file or alias in question, preferably as part of the text of your message (not as an attachment). If you do not have electronic access, contact us by fax if possible. Problems of this type are usually very difficult to diagnose over the telephone because we cannot see the material you are working with. If your batch file is longer than about 20 lines, please try to reproduce the problem in a smaller test file; otherwise it will probably be impossible for us to understand and recreate the difficulty you found. If you need more in-depth assistance with the development of complex batch files or other procedures, please contact us for information on consulting services. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 6 INTRODUCTION ------------------------------------------------------------------ Electronic Support Usually the best way to contact us for support is via CompuServe or the Internet. The most efficient method is to use our CompuServe support conference; if you do not have CompuServe access, contact us via Internet email. (Our CompuServe and Internet addresses are listed on page 4.) Whenever possible, we also read messages posted on the Usenet comp.os.msdos.4dos newsgroup, and in the 4DOS conference on the FidoNet BBS network (these discussion areas are named for 4DOS, but carry messages related to all JP Software products). These areas offer valuable information and discussions with other users, but are not managed by JP Software, and are not official support channels. To be certain of a direct answers from our support staff use our CompuServe forum, web site, or Internet email, or contact us by telephone, fax, or mail. Additional support resources are available from our web site at htp://www.jpsoft.com/, including error message listings, documentation files, product histories, technical tips and discussions, other technical information, and links to other companies' sites. We update this information regularly, and we encourage you to check the Technical Support area of the web site to see if the information there will address any questions you have. Telephone Support Telephone technical support within the US and Canada is handled on a callback basis. To contact our support staff, call our US / Canada Support Line at any time and leave a short voice mail message describing your technical problem. The telephone number is 617-646-0798, and will change to 781- 646-0798 effective September 1, 1997. This line can not be used for sales and customer service issues such as pricing, ordering, upgrades, or shipping problems. We check messages regularly throughout the day, and will return your call as quickly as possible. We generally return all technical support calls within 24 hours (weekends and holidays excluded), and most are returned much more quickly, usually on the same business day. If your problem is urgent and requires a faster response, please let us know and we will try to accommodate you. If you contact us by telephone and don't receive a reply within 24 hours, please try again. We probably tried to return your call and were unable to reach you. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 7 INTRODUCTION ------------------------------------------------------------------ If you are calling from outside the US and Canada, are not sure if your question requires technical support, need other assistance in addition to your technical questions, or find yourself playing "telephone tag" with our support staff, please call our main number, 617-646-3975 (781-646-3975 effective September 1, 1997). Our office staff will assist you with all of your concerns, and have a technical support representative call you back if necessary. Registration and Upgrade Information If you purchased Take Command from a software dealer, your copy came with a registration card. Please fill out this card and return it promptly to JP Software. It ensures that we have a record of your registration so that we can give you ongoing technical support and notices of upgrades. If you purchased Take Command directly from JP Software, or ordered an electronic copy via our web site, you are already registered and no registration card is necessary. Once you are a registered user, with each notice of a major upgrade you will receive The Prompt Solution, JP Software's customer newsletter. The Prompt Solution also includes tips for using Take Command, and information about other products from JP Software. Registration also entitles you to full technical support via electronic mail, fax, mail, or telephone. Take Command is upgraded regularly through maintenance releases, designed to fix minor problems or improve compatibility, and major upgrades which contain enhancements and additional features. Maintenance releases are identified by a change in the hundredths digit of the version number, for example from 2.0 to 2.01 or 2.02, or in a letter suffix (e.g. 2.01B). Major upgrades are identified by a change in the tenths digit or "ones" digit, for example from 2.0 to 2.1 or 3.0. Major upgrades can be purchased from JP Software or your dealer. You can download maintenance releases from our web site (http://www.jpsoft.com/), or from the CompuServe or BBS locations listed under Contacting JP Software on page 4. You can also order them on disk at a nominal cost. As a registered user, you will automatically be notified when a major upgrade is released. We don't send out notices when maintenance releases become available, because you don't usually need them unless you're having a problem. If you call with a problem that's been addressed in a maintenance ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 8 INTRODUCTION ------------------------------------------------------------------ release, we'll mail you a copy on disk or assist you in downloading it. If you want to know when a product update is available, visit our web site at http://www.jpsoft.com/. Notices are posted there whenever one or more of our products is updated, and email or other automated methods for upgrade notification may become available on the web site in the future. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 9 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ Chapter 1 / Introducing Take Command Take Command is a command interpreter which runs in a window on your desktop. The window is similar to the ones you see with most desktop applications. Inside the window, Take Command displays a C:\> or [C:\] prompt, waits for you to type something, and then reacts to your commands. We've designed our products so that you don't have to change your computing habits or unlearn anything to use them. If you know how to display a directory, copy a file, or start an application program from a command prompt, you already know how to use Take Command _ and if you're not used to using the command line, you'll appreciate Take Command's comprehensive online help, the way it integrates the command prompt and a desktop window, and the way it makes the command prompt straightforward and easy to use. In this section, we introduce a few of the features we have built into Take Command. We don't have room to list them all or to explain all of the options available in each; that's what the Reference Manual and online help are for. This section will just give you a taste of what you can expect from your computer once you have Take Command installed. As you read through this section, remember that you don't have to use any of these features except the ones that appeal to you. Learn just the parts that will make your computer easier for you to use, and add more features to your repertoire as you find that you need them. The Take Command Window The Take Command window is similar to other applications that run on the Windows or OS/2 desktop. The title bar at the top is similar to the one used in most Windows and OS/2 applications, with a system menu button on the left and the maximize, minimize, and close buttons at the right (the close button may not be present in Windows 3.x, or in Windows NT 3.5). You can move the window and adjust its size with a mouse or the keyboard, and you can change the text on the title bar and change the window's size or position with the WINDOW command. The menu bar is also similar to many other applications: * The File menu allows you to save or print the screen buffer or exit from Take Command. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 10 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ * The Edit menu lets you copy text between the Take Command window and the clipboard. * The Apps menu lets you start applications from within Take Command. * The Options menu lets you configure Take Command and turn various display options on and off. * The Utilities menu lets you use several built-in utilities interactively. * The Help menu gives you access to Take Command's online help. Most of the menu bar features can also be invoked with typed commands if you prefer (for example, OPTION starts the option dialogs, and HELP starts the help system). The Tool bar lets you execute programs, utilities, and commands with the click of a mouse. You can configure the tool bar with any collection of commands and labels you wish. The Command window accepts your input and displays Take Command's output. You can scroll through the window, save or print text from the window, and transfer text between the Command Window and the clipboard. The Status bar displays information about Take Command and your system. The use of each portion of the Take Command window and of each menu option is explained in detail in the Reference Manual and in the online help. Built-In Commands The Command window is the heart of Take Command. It is here that you type commands for Take Command to execute, and here that the program displays the output of each command. Take Command supports every command you already know from your operating system's command prompt, adds to the features of each command, and also adds dozens of new commands. For example, the traditional DIR command, which displays a list of files, has about 8 options. The DIR command in our products has most of the same options plus almost 20 more. With the enhanced DIR command, you can: ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 11 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ * Display a list of files in 1, 2, 4, or 5 columns with the commands: c:\> dir c:\> dir /2 c:\> dir /4 c:\> dir /w * Use colors to indicate different kinds of files, display file descriptions (text to remind you of the contents of a file) along with file names, and sort files according to several different criteria. * Display hidden and system files, along with normal files. For example, this command displays all of the files in the current directory, whether they are "hidden" or not: c:\> dir /a * Display files of one type or of several types together. For example, this command lists all .TXT, .DOC, and .ASC files in the current directory: c:\> dir *.txt;*.doc;*.asc * Display files from a single directory, from one part of the directory tree, from a single drive, or from several drives. * Use wildcards to display all file names that start with the letter "A", end with the letter "A", or have an "A" anywhere in the name: c:\> dir a* c:\> dir *a c:\> dir *a* * If you use Windows 95 or Windows NT, you can view either long file names, traditional "short" file names, or both. That's just an example of some of the enhancements we have added to one command. Take Command adds enhancements to virtually every command you've used before and includes dozens of new commands as well. You don't have to learn to use them all, but you will find many commands and enhancements that will make your computer more powerful and easier to use. For example: ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 12 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ * COLOR lets you set the default colors to use in the Command window: c:\> color bright white on blue Additional features let you customize the colors you want to use for parts of the display, for input and output, and for specific kinds of files. * LIST displays the contents of files in text or hexadecimal mode, lets you search a file, and can print either an entire file or a single page from a file: c:\> list readme.txt * The Find Files / Text option in the Utilities menu and the FFIND command search for files based on their names and their contents. For example, to find all files on drive C: with the string "now" somewhere within their names, you can either fill in the Find Files dialog or type the command: c:\> ffind /s *now* To find all .TXT files in the current directory which contain the string "then" somewhere in the file: c:\> ffind /t"then" *.txt * SELECT lets you pick the files you want to work with from a full-window, "point and shoot" display. This command, for example, lets you select files from the current directory to copy to the floppy in drive A: c:\> select copy (*.*) a: * EXCEPT lets you work with all of the files in a directory except those that you want to exclude. It is something like wildcards in reverse. (A related feature, "exclude" ranges, also works like reverse wildcards, and can be used to exclude files from any internal command.) This command copies all files from the current directory to drive A: except backup (.BAK and .BK!) files: c:\> except (*.bak;*.bk!) copy *.* a: ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 13 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ The Command Line Take Command is much more than just a collection of commands in a window. It includes a number of features which make the command line easier to use: * Interactive help appears whenever you ask for it and also any time you use a command incorrectly. Type c:\> help when you need help. You can also select Contents from the Help menu, or press F1 to view the help Table of Contents. If you have typed part of a command, F1 displays help on the first word on the command line. * The command line works like a single-line word processor. You can edit any part of the line at any time before you press Enter to execute it or Esc to erase it. You can move the cursor left and right by a single character, a single word, or jump to the beginning or end of the line. You can delete, insert, or type over characters anywhere on the command line, and you can use standard Windows character editing and highlighting keys (Shift-arrow, etc.). * Take Command keeps track of each command you execute. You can display past commands, execute them again, or make changes before you execute them. The past commands can appear on the command line (if you press Ctrl--), or in a pop-up window (if you press Ctrl- PgUp). * If you don't want to type a complete file name as part of a command, you don't have to. Just type part of the name and then press the Tab key: a matching file or directory name will appear on the command line. Press the Tab key again to see the next matching file. To choose from all matching files in a pop-up window, press F7 or Ctrl-Tab. The ability to complete filenames easily can be invaluable on a drive with long filenames _ all you have to do is type part of a lengthy file or directory name and press Tab. Take Command fills in the rest. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 14 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ * Take Command keeps track of each directory you have visited. There are many ways to return to previous directories; perhaps the easiest is to press F6 to view past directories in a pop-up window. Select the directory you want, press Enter, and you will immediately change to that directory, even if it is on a different drive. * Take Command can also use a extended directory search "database" that will help you move, almost instantly, to any directory on any hard drive on your system when you type just part of the directory name. * Take Command includes features that let you select files by size, date, and time; exclude files from a command with wildcards; and use multiple sets of wildcards at once. For example, this command makes it simple to copy all files in the current directory that have been updated in the last week to a backup disk: c:\> copy /[d-7] *.* a:\ Or you can delete all .BAK and .BK! files that are greater than 1 MB in size: c:\> del /[s1M] *.bak;*.bk! With a simple change you can make the command delete the same files, but from the entire drive rather than just the current directory (use a command like this with caution!): c:\> del /[s1M] /s *.bak;*.bk! Finally, you could modify the command above to exclude files whose names begin with A, but still delete all other .BAK and .BK! files: c:\> del /[!A*.*] /[s1M] /s *.bak;*.bk! * Take Command lets you associate file extensions with particular applications. For example, it's easy to start your word processor and load a letter anytime you type the name of a .LTR file: c:\> set .LTR=c:\wp\wordproc.exe After you have defined the association, you can start your word processor and have it load your letter to ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 15 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ Mom, MOM.LTR, with this command (assuming the file is in the current directory): c:\letters> mom * You can also run multiple commands at one time. If you know the next 3 commands you need to run, you can type them all at once and then sit back while they are executed one at a time. For example, to copy all of your .TXT files to drive A: and then display the directory of drive A: TC16 c:\> copy *.txt a: ^ dir a: TC32, TCOS2 [c:\] copy *.txt a: & dir a: Working with Windows and OS/2 Take Command works with Windows and OS/2 in several ways to make your computing more productive: * You can use the Windows or OS/2 clipboard to copy text onto the command line, or to transfer text from Take Command to another application. * You can use the Windows or OS/2 Drag and Drop feature to insert file names from other applications onto the command line. * You can use Take Command/16 and Take Command/32 to send messages to other Windows applications using Dynamic Data Exchange (DDE). You can also use DDE to send commands to Take Command from other applications. * Take Command/16 and Take Command/32 automatically use Windows' File Associations to associate data files with applications. * Take Command/16 (and Take Command/32 under Windows NT 3.5) can communicate with Program Manager to determine what groups and applications to list on the Apps menu. Configuration We don't know how you use your computer, or how you would like it to work, so we have made Take Command as flexible as ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 16 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ possible. You can configure almost every part of Take Command to suit your needs or your whims. To start the configuration utility, use the Options menu or type: c:\> option For example, you can decide what colors to use for what purposes, how file names are displayed in command output, and command line editing details ranging from the size and location of pop-up windows to the shape of the cursor. Aliases and Batch Files We've left two of the most popular and powerful features, aliases and batch files, for last. Aliases Aliases are short sequences of commands which are stored in memory for very fast execution. Aliases can assign complex tasks to simple names or single keystrokes, define new commands, and set defaults for internal commands and for almost any application on your computer. They are the primary method we offer for customizing the command line to suit your needs. Here are a few examples of how you could define simple aliases to make the command line easier to use. The first two provide shorthand names for the DIR command _ D displays a directory, and D2 displays a 2-column directory, sorted vertically, with a pause at the end of each page: c:\> alias d dir c:\> alias d2 dir /2pv Once these definitions have been entered, all you have to do is type D or D2 at the prompt to execute the corresponding alias. You can also define aliases as shorthand ways to execute applications, usually without having to add the application's directory to your PATH. For example, this alias allows you to just type EDIT to run your Windows editor, even if its directory is not on the PATH: c:\> alias edit e:\edfiles\winedit.exe ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 17 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ You can put a whole group of commands into an alias so that you can invoke them without typing each one. This alias changes directories, runs the FINPROC program, and changes back to the original directory (the back-quotes [`] are used to enclose an alias when it contains more than one command): TC16 c:\> alias monthly `pushd c:\monthly ^ finproc ^ popd` TC32, [c:\] alias monthly `pushd c:\monthly & finproc & popd` TCOS2 This short description explains only the basics of what aliases can do. Like most Take Command features, aliases can be as simple or as complex as you like. You can save your aliases in a file and reload them each time Take Command starts (otherwise, you'd have to redefine them each time); assign aliases to keystrokes or Toolbar buttons so they can be invoked quickly; write aliases which use other aliases; and use aliases within batch files. For complete information on aliases see Chapter 5 of the Reference Manual, the ALIAS command in Chapter 7 of the Reference Manual, or the online help. Batch Files A batch file or batch program is a text file that contains a list of commands to execute. Take Command reads and interprets each line as if it had been typed at the keyboard. If you're an experienced batch file programmer, or if you want an easy introduction to batch file programming, you won't find anything better or more powerful than our built-in batch language. The batch language includes simple commands to display menus, dialogs, lines, and colored text to dress up your batch file displays; a full range of user input commands; over 70 built- in variables that let your batch files test system configuration, device status, and free memory and disk space; and almost 100 built-in functions that let your batch files read from files, find the date, perform calculations, and manipulate strings. Our batch files run 2 to 10 times faster than traditional ones. They can include subroutines, loops, IF/THEN/ELSE logic, and even exception handling. And you can run them in single-step mode to debug them easily, learn exactly what each line does, or view changes to environment variables and other information as the batch file executes. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 18 Chapter 1 / Introducing Take Command ------------------------------------------------------------------ Here are a couple of examples of simple batch files. The first example displays several pieces of information about your system status, using built-in variables provided with Take Command: cls echo System status as of %_date at %_time: echo CPU: %_cpu echo Coprocessor: %_ndp echo Window size (characters): %_rows x %_columns echo Boot drive: %_boot echo DOS version: %_dosver echo Windows version: %_winver echo Command processor version: %_4ver echo Country code: %_country echo Windows directories: %_windir %_winsysdir The next example clears the screen, displays a short menu, accepts some input from the user, and displays the result (a more useful version of this file would actually perform the requested action; for now we're just trying to give you the overall flavor of our batch enhancements). The TEXT command displays a block of text on the screen, the SCREEN command positions the cursor, and the INKEY command accepts a single keystroke from the user: cls screen 5 0 text Choose an option: 1 - Word processing 2 - Spreadsheet 3 - Load the network endtext screen +1 0 inkey Enter your selection: %%sel screen +2 0 echo You entered: %sel This example prompts for a user name (8 characters maximum) and a password (echoed as "*"s, 6 characters maximum), in a Windows dialog: cls querybox /L8 "User Name" Enter your user name %%name querybox /L6 /P "Password" Enter your password %%password ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 19 Chapter 2 / Installation ------------------------------------------------------------------ Chapter 2 / Installation All copies of Take Command come with automated software that makes installation simple and straightforward. The instructions for running this software vary depending on whether your copy came on a diskette or CD, or was downloaded from an on-line source. The installation software will set up Take Command automatically if you wish, and we recommend that you use this method. However, if you prefer to set up the program yourself you can allow the installation software to handle only certain required tasks (such as extracting files from a distribution disk), and perform the remaining steps manually. Manual installation is covered in detail for each product in Chapters 5 _ 7. We strongly recommend that you install your new version of Take Command in a new directory or folder, rather than using the same directory as a previous version, or a directory used by other software, including other products from JP Software. Installing an Upgrade Use the standard installation instructions below to install an upgrade. The installation procedure is essentially the same as when you are installing a new copy of the program. If you are upgrading from a previous version, you may have a TCMD.INI and / or TCSTART or TCEXIT file in the previous version's directory. To use these files with the new version, you must copy them to the new directory, and update the .INI file in some cases. You can allow the installation software to perform these steps automatically, or you can perform them yourself at a later time. Starting the Installation Software Our products are distributed using four standard methods: via electronic purchase, on a single-product diskette from JP Software, on the JP CD Suite, or in a downloaded .ZIP file. Instructions for each format are below; be sure to follow the instructions which correspond to the way you obtained the program. If your copy of the program came from a collection of trial software on CD or diskette, and is stored in a .ZIP or other similar file, use the instructions which refer to a ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 20 Chapter 2 / Installation ------------------------------------------------------------------ downloaded copy, even if you did not actually download the program. Installation of an Electronically Purchased Copy If your copy of Take Command was purchased and delivered electronically (e.g., from the on-line ordering section of our web site), you can simply extract the downloaded files to a temporary directory, then start the INSTALL.EXE program. It will offer the same Express and Custom installation options described in the next section, and you can follow the directions for those options below. Installation from a JP Software Diskette or CD-ROM To begin the installation process, you must run the Take Command Install program. If you have a JP Software diskette, put the disk into drive A (you can use drive B, if you prefer) and then start the Install program. Each operating system provides several ways to start the Install program. These are perhaps the easiest methods: * In Windows 3.x or Windows NT version 3.5, use the Program Manager's File / Run option. In the Command Line field, type: a:install and then press Enter. * In Windows 95 or Windows NT version 4.0 or later, use the Start button's Run option. In the Open field, type: a:install and then press Enter. * In OS/2, open Drive A (or Drive B) by selecting the Drives icon in the OS/2 System folder or on the WarpCenter task bar, then select the Install program. If you have the JP CD Suite, put the CD into your CD-ROM drive, then use the technique described above for your operating system to start the INSTALL program from the appropriate directory or folder: d:\tcmd16\install.exe ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 21 Chapter 2 / Installation ------------------------------------------------------------------ d:\tcmd32\install.exe d:\tcmdos2\install.exe where "d:" is the drive letter used for your CD-ROM. The installation software will offer two options: * Express Installation will install the program automatically on your system and, as necessary, make appropriate modifications to your system without further prompting (except for required directory information). A new folder or group for the program will be created in the Program Manager or on the desktop. * Custom Installation will extract or copy the Take Command files to your hard disk, then prompt you for confirmation before each installation step (including modifications to system files and the desktop). To install the program manually, use the Custom Installation option to extract or copy the necessary files, skip the steps you do not want performed automatically, and refer to the Manual Installation instructions in Chapters 5 _ 7. The diskette and electronic purchase installation programs also offer an Extract Individual Files option. This is used to restore damaged files, and is not needed during a normal installation. It is not offered on the JP CD Suite, because no "extraction" process is necessary _ individual files can be copied with a simple COPY command. "Branding" If you received your copy of Take Command on a JP Software diskette or CD-ROM, you will have a "brand card" or label with a serial number and validation code (in some cases you will have a separate card or label for each product). If your diskette or CD was purchased directly from JP Software the brand card will also include your registered name (company or individual). If your copy was purchased electronically the serial number and validation code are included in the materials you received as part of the purchase transaction. The serial number and validation code constitute your license, and are provided only with purchased copies, not with trial copies. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 22 Chapter 2 / Installation ------------------------------------------------------------------ A program which comes with each product checks your registered name, serial number, and validation code, and saves them for use by Take Command. This process, which we call "branding," personalizes your copy and removes the "unregistered copy" or other similar message which is displayed if you skip this step. Depending on the distribution mechanism used, some copies may not work at all until they are branded. The actual brand program name depends on the product (e.g. BRTC16.EXE for Take Command/16, etc.). The branding program is run automatically during the installation process. As you follow the instructions to enter your name, serial number, and validation code, be sure that all information is entered exactly as shown on the brand card, label, or electronic branding information you received. You cannot change spelling, capitalization, or punctuation. If you need to run the branding program manually, see the instructions in Chapters 5 _ 7. You may also need to run the branding program when you download a maintenance upgrade to any product. Branding a downloaded copy converts it from a timed trial copy to one fully registered to you. For this reason you should save your brand card, label, or electronically delivered branding information, in case it is needed when you download or purchase an upgrade. If you lose the branding information there is a charge to create a replacement card or label. Installation of a Downloaded Trial Copy To install a downloaded trial copy you must extract the product files and start Take Command, as described below: * Extract the files into a new directory using PKUNZIP, WINZIP, or a similar utility. * In Windows 3.x, or Windows NT version 3.5, use the Program Manager's File / Run option. In the Command Line field, type: d:\path\tcmd (for Take Command/16) d:\path\tcmd32 (for Take Command/32) and press Enter ("d:\path" is the name of the directory where you extracted the Take Command files). ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 23 Chapter 2 / Installation ------------------------------------------------------------------ * In Windows 95, or Windows NT version 4.0 or later, use the Start button's Run option. In the Command Line field, type: d:\path\tcmd32 and press Enter ("d:\path" is the name of the directory where you extracted the Take Command files). If you prefer, you can use Windows Explorer to execute the TCMD32.EXE file. * In OS/2, use the Drives object to select the directory where you extracted the Take Command files, and run the TCMDOS2.EXE program. If you prefer, you may use a 4OS2 or CMD.EXE command prompt; at the prompt, change to the Take Command directory and type: tcmdos2 and then press Enter. Once you have started Take Command, it will run its installation procedure and set itself up for your system automatically. You can allow the installation software to modify system files automatically, or modify them yourself at a later time. If you have an up-to-date copy of Take Command and have downloaded a maintenance upgrade, you may need to brand the new version with your registered name and serial number (see the previous section for details on branding). The automated installation procedure for the downloaded copy will start the branding program for you if possible. To brand a downloaded copy manually, see the instructions in Chapters 5 _ 7. If you try to brand a downloaded copy of a new major release, and you have not purchased a license for that release, the branding program will display a message indicating that you need to contact JP Software or your dealer for an upgrade. Once you have ordered an upgrade you can continue to use the downloaded trial version until your upgrade arrives. The automatic installation procedure for downloaded copies only runs the first time you start a new copy of Take Command in its own directory. If you need to re-install a downloaded copy, use the manual installation instructions in Chapters 5 _ 7. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 24 Chapter 2 / Installation ------------------------------------------------------------------ Uninstalling the Program We don't expect you to have trouble using our programs, but we know some people feel more comfortable knowing how to uninstall a product as well as install it. Or, you may need to remove the program from one system to move it to another system. To remove a purchased copy of Take Command, just insert the distribution diskette or CD, start the INSTALL program as described on page 20, and select the Uninstall option. Uninstall will offer you options which "undo" the corresponding steps in the installation procedure. Complete Uninstall will take all of the other steps automatically, and remove the program entirely from your system. The Uninstall option will attempt to reverse the changes made during installation, including modifications to your system. However, in rare circumstances, the program may not be able to complete all of the steps automatically and you will need to perform some of them manually. You will also need to uninstall the program manually if you installed it from a downloaded copy. See Chapters 5 _ 7 for instructions. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 25 Chapter 3 / The Help System ------------------------------------------------------------------ Chapter 3 / The Help System All of our products include complete online help. This chapter provides a basic description of how to use the help system, and lists important help topics you may want to refer to. Using the Help System If Take Command is running, you can start the help system from the Help menu, by typing HELP (or HELP plus a command name) at the prompt, or by pressing the F1 key at any time when the Take Command window is accepting keyboard input at the prompt. The information in each help system is fully cross-referenced, so you can move easily among related topics. If you type part or all of a command on the command line and then press F1, the help system will provide "context- sensitive" help by using the first word on the line as a help topic. If the first word is not a valid help topic you will see the Table of Contents. For example, if you press F1 after entering each of the command lines shown below you will get the display indicated: c:\> Table of Contents c:\> copy *.* a: Help on COPY c:\> c:\util\map Table of Contents If you are using Take Command for OS/2 and you type the name of any internal command at the prompt, followed by a slash and a question mark [/?] like this c:\> copy /? then you will see help for the command in a quick-reference style. In Take Command/16 and Take Command/32, /? starts the help system and displays help for the command. Once you've started the help system, you can use a standard set of keystrokes or mouse actions to navigate through the help text. The help system can also be started "manually" (i.e., without Take Command running), and contains information which may be helpful if you encounter difficulties setting up Take Command and configuring it for your system. See Chapters 5 _ 7 for details on starting the help system manually, and Chapter 7 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 26 Chapter 3 / The Help System ------------------------------------------------------------------ for information about customizing help in Take Command for OS/2. Important Help Topics The help system includes documentation for all Take Command commands and features. It also includes many other topics which may be of interest to you as you use the program or which you may need for advanced installations. This section lists some topics in the help system which you may find useful: * Configuring Take Command covers the .INI file and the related dialogs, including reference information on all .INI file directives. * Starting Take Command (under Setup and Troubleshooting) explains the startup command line, and contain links to related startup and configuration topics such as TCSTART and TCEXIT. * What's New explains changes in recent versions of Take Command. Be sure to review this information before working with any upgrade. This section covers the current release and any prior releases of the same major version. For older historical information see our web site at http://www.jpsoft.com/. * Troubleshooting, Service, and Support (under Setup and Troubleshooting) includes a list of error messages and a discussion of useful diagnostic and troubleshooting techniques. It also contains information on contacting JP Software for technical support, sales, customer service, and other similar matters. * Reference Tables (under Reference Information) includes comprehensive lists of ASCII characters and keyboard codes. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 27 Chapter 4 / Configuration (All Products) ------------------------------------------------------------------ Chapter 4 / Configuration (All Products) Once you have Take Command installed on your computer, the program is ready to run. However, you can configure Take Command in various ways to suit your needs and preferences. Most of the configuration or behavior of Take Command is controlled by aliases you create (explained in Chapter 5 of the Reference Manual, and in the online help) and by the .INI file (explained briefly below, and in detail in Chapter 6 of the Reference Manual, and in the online help). A few configuration options can also be set on the startup command-line, which is explained here. If Take Command works the way you want it to after installation, you can skip this chapter. You may, however, want to skim this material to see what options are available. Starting Take Command You will typically start Take Command from a desktop object or menu in Windows 95, Windows NT 4.x, or OS/2, or from an item in one of the Program Manager groups in Windows 3.x or Windows NT 3.5. The installation software will create a Take Command folder or group, and a desktop object within it which starts Take Command. Usually this item is sufficient, but if you prefer you can create multiple desktop objects or items to start Take Command with different startup commands or options, or to run different batch files or other commands. You can use these items to run commonly-used commands and batch files directly from the desktop. Each item or icon represents a different Take Command window. Using the .INI file, startup command line options, and aliases, you can configure each in various ways to suit your needs and preferences. Command Line Options Some of the options that Take Command recognizes are required in certain circumstances; others are available if you want finer control over the way the program starts. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 28 Chapter 4 / Configuration (All Products) ------------------------------------------------------------------ The line that starts Take Command will typically include the program name with drive and path then include any switches for the program, for example: c:\tcmd300\tcmd32.exe @c:\tcmd300\tcmd32.ini This command line may appear on one or two lines, depending on the operating system you are using. Specific details on where you should enter the command line for each product are included in Chapters 5 _ 7. Although the startup command line is usually very simple, you can add a number of options if you need to customize the way Take Command starts. The complete syntax for the startup command line is: d:\path\program [d:\path] [@d:\path\inifile] [//iniline] [/L /LA /LD /LH /T:bf] [[/C] command] Do not include the square brackets shown in the command line above. They are there to indicate that the items within the brackets are optional. Not all options are available in all products; see below for details. If you include any of the options below, you should use them in the order that they are described. If you do not, they may not operate properly. The following items can be included on the command line: * d:\path\program: The path and name of the executable program file (TCMD16.EXE, TCMD32.EXE, or TCMDOS2.EXE). It is required to start Take Command. * d:\path: This is the second d:\path in the command line above. It sets the drive and directory where the program is stored, called the COMSPEC path. This option is included for compatibility with character- mode command processors, but is not needed in normal use. Take Command can find its own directory without a COMSPEC path, and usually the COMSPEC variable should be left pointing to the default character mode command processor in use on your system, not changed to point to Take Command. * @d:\path\inifile: This option sets the path and name of the .INI file. You don't need this option if your .INI file has the default name (TCMD.INI, TCMD32.INI, or TCMDOS2.INI) and it is either in the same directory as the executable program, or in the ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 29 Chapter 4 / Configuration (All Products) ------------------------------------------------------------------ Windows or OS/2 directory. This option is most useful if you want to start the program with a specific and unique .INI file. * //iniline: This option tells Take Command to treat the text appearing between the // and the next space or tab as an .INI directive. The directive should be in the same format as a line in the .INI file, but may not contain spaces, tabs, or comments. Directives on the command line override any corresponding directive in the .INI file. This option may be repeated. It is a convenient way to place a few simple directives on the startup line without having to modify or create a new .INI file. TC32, * /L, /LA, /LD, and /LH: These options force Take TCOS2 Command to use a local alias, directory history, and / or command history list. They can be used to override any LocalAlias=No, LocalHistory=No, or LocalDirHistory=No settings in the .INI file. This allows you to use global lists as the default, but start a specific shell or session with local aliases or histories. See your Reference Manual or online help for details on local and global aliases and histories. /LA forces local aliases, /LD forces local directory history, /LH forces local command history, and /L forces all three _ local aliases, command history, and directory history. TC32 * /T:bf: This option sets the foreground and background colors in Take Command/32's command window. Both b and f are hexadecimal digits; b specifies the background color and f specifies the foreground color. This option is included only for compatibility with Windows NT's CMD.EXE; in most cases you should set default colors with the StdColors directive in TCMD32.INI, or the corresponding Output Colors option on the Display page of the option dialogs (see page 31). * [/C ] command: This option tells Take Command to run a specific command after starting. The command will be run after TCSTART (see page 31), and before the prompt is displayed. The command can be any valid alias, internal or external command, or batch file. All other startup options must be placed before the command, because Take Command will treat characters after the command as part of the command and not as additional startup options. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 30 Chapter 4 / Configuration (All Products) ------------------------------------------------------------------ When the command is preceded by a /C, Take Command will execute the command and then exit and return to the parent program or the desktop without displaying a prompt. For example, this command line will start Take Command/32, execute the TCSTART file (if any), execute START.BTM, and then display the prompt: c:\tcmd32\tcmd32.exe c:\tcmd32\start.btm This command line will start Take Command/32, select local aliases, execute any TCSTART file you have created, execute the file PROCESS.BTM, and then exit when PROCESS.BTM is done. The prompt will not be displayed by this session: c:\tcmd32\tcmd32.exe /la /c c:\tcmd32\process.btm Creating or Modifying Startup Files Each of our products uses two files to control the way it starts: a file of configuration information called the .INI file (TCMD.INI, TCMD32.INI, or TCMDOS2.INI), and a startup batch file called TCSTART (depending on your operating system, TCSTART may have the extension .BTM, .BAT, or .CMD). The .INI file is required, and is normally created during installation, or the first time you run Take Command. The .INI file for each command processor should be placed in the same directory as the other files for that product. You can add additional information to the .INI file manually with an ASCII editor. Many of the .INI options can also be set directly from within Take Command using the configuration dialogs (in Windows) or settings notebook (in OS/2), which is accessible from the Configure Take Command selection on the Options or Setup menu or with the OPTION command. There are several pages of options within the dialog or notebook. The .INI file is divided into sections. Each section begins with a section name in square brackets, for example [Fonts]. The options you can set are all in the [TakeCommand] section, which is normally the first one in the file. Take Command maintains all other sections of the file itself; you should not modify them unless you are instructed to do so by our support personnel. The TCSTART file is also optional. It is executed each time Take Command starts, and gives you a convenient way to load ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 31 Chapter 4 / Configuration (All Products) ------------------------------------------------------------------ aliases and environment variables, and otherwise initialize Take Command. TCSTART is normally placed in the same directory as the other product files, but this may vary if you use the same TCSTART file for more than one product. For complete details on startup files, on the option dialogs and OPTION command, and on the TCEXIT file (executed when the command processor exits), see your Reference Manual or the online help. If you are upgrading from a previous version of Take Command you may have a .INI file or a TCSTART (or TCEXIT) file in the previous version's directory. To use these files with your new version, copy them to the new directory, and then update any paths in either file which point to the old program directory. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 32 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ Chapter 5 / Take Command/16 Configuration and Notes Take Command/16 works well with Windows 3.x, Windows for Workgroups, and for Windows sessions in OS/2. Take Command/16 is not designed to be used under with Windows 95 or Windows NT; you should use Take Command/32 in those environments. This chapter provides basic information about Take Command/16. If you need more detailed technical information or troubleshooting assistance on any of these topics, consult the Troubleshooting, Service, and Support topic in the online help. Take Command/16 Installation Notes When you install Take Command/16, a few changes must be made to your Windows configuration. You can allow the installation software to make these changes automatically, or you can make them yourself at a later time (see Manual Installation of Take Command/16 below for details). Depending on options you select, the installation program can move the CTL3DV2.DLL file to the \WINDOWS\SYSTEM directory; create a Program Manager group for Take Command; modify SYSTEM.INI to load CAVEMAN.386 when Windows starts; and add a line to SYSTEM.INI to load Take Command as your Windows shell when Windows starts. Installing Take Command/16 does not modify, remove, or otherwise alter WIN.INI, CONFIG.SYS, AUTOEXEC.BAT, or any of your other system files. Manual Installation of Take Command/16 This section is for advanced users, and assumes you are generally familiar with Program Manager, your Windows directory, SYSTEM.INI, and using ASCII editors. In most cases you can select the installation options you need using the automated installation program, and manual installation is not necessary. In order to install Take Command manually, you must extract or copy the necessary files, "brand" Take Command if necessary, modify configuration files as required, and then create the necessary desktop items to start the program on your system. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 33 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ Extracting or Copying the Program Files When you extract or copy the Take Command files, be sure to place them in their own directory, rather than using the same directory as a previous version of the program, a directory used by other JP Software products, or a directory used by other software. We strongly recommend that you place all of the Take Command files in the same directory. See Take Command/16 Files and Directories below for some important considerations if you choose not to follow this recommendation. The method used to extract or copy the files depends on how you obtained your copy of the program: * If you have a JP Software diskette you must use the installation program to extract the files, which are compressed on the distribution disk. You cannot simply copy the files onto your hard disk. Select Custom Install and follow the prompts to specify the installation directory and copy the files. Then exit the installation program with Ctrl-X, or answer No when prompted for whether to proceed with each additional step. * If you have the JP CD Suite, all of the files are stored uncompressed on the CD, in the \TCMD16 directory, and you can copy them manually if you wish. However, we still recommend that you use the installation program to copy the files. Some files may be renamed after copying, and some files are used only during the installation process and do not need to be copied to your hard disk. If you copy the files manually, a few may not have the correct names, and you may copy more files than you need, resulting in wasted hard disk space. * If you have a downloaded copy of the program, or a copy distributed on a CD or diskette of trial software, extract the files into a new directory using the appropriate decompression program (e.g. PKUNZIP or WINZIP). "Branding" Take Command/16 (If you are not familiar with branding, refer to the general information on page 22 before continuing with this section.) ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 34 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ If you have purchased a copy of Take Command/16 the automated installation procedure will normally run the BRTC16 program to check your name, serial number, and validation code and "brand" Take Command as a registered product (in some cases Take Command/16 may not operate properly until this step is completed). If you need to brand Take Command/16 manually, start Take Command (or a 4DOS or "MS-DOS Prompt" session), change to the directory where Take Command/16 is stored, and enter the command: c:\tcmd200> brtc16 Follow the instructions displayed by BRTC16 to enter your name, serial number, and validation code. All information must be entered exactly as shown on your original brand card, label, or electronically delivered branding information; you cannot change spelling, capitalization, or punctuation. If you are upgrading from a previous version and using an old copy of the BRAND.EXE program distributed with that version, you must start BRAND from a 4DOS or COMMAND.COM prompt, not from Take Command. Older versions of BRAND cannot brand Take Command/16 while it is running. The newer BRTC16 program does not have this restriction. Updating Windows Files for Take Command/16 In order to run Take Command/16, you should make two changes in your Windows directory. Both changes are normally made by the installation program; this section describes how to make them manually. First, you may need to install CTL3D, a Microsoft library which gives a 3-dimensional appearance to some elements of the Windows display for programs (like Take Command) that use it. CTL3D for Take Command/16 is distributed in the file CTL3DV2.DLL. It only works properly if there is a single copy of this file on your system, stored in the \WINDOWS\SYSTEM directory; if you have more than one copy, Windows will display an error when Take Command starts. Check the CTL3DV2.DLL file in your new Take Command/16 directory. If it is newer (has a later date and time) than the version in your \WINDOWS\SYSTEM directory, or if the file does not exist at all in \WINDOWS\SYSTEM, copy it from the Take Command directory to the \WINDOWS\SYSTEM directory. Then delete the original file so that you don't have two copies. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 35 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ If the version of CTL3DV2.DLL in the \WINDOWS\SYSTEM directory is newer, simply delete the file from the Take Command directory. Second, you should add a line to your SYSTEM.INI file to load the Caveman device (see page 39 for more information on Caveman). Open SYSTEM.INI with an ASCII editor such as Notepad or SysEdit, and add this line to the [386Enh] section: device=d:\path\caveman.386 where "d:\path" refers to the drive and directory where Take Command is stored. The position of this line within SYSTEM.INI is not important as long as it is in the proper section. When you edit SYSTEM.INI, you must restart Windows for your changes to take effect. Take Command/16 doesn't require any other changes to any system files. Take Command/16 Files and Directories We strongly recommend that you place all Take Command/16 files (other than CTL3DV2.DLL) in the same directory. If you do not do so, you will probably have to explicitly set the locations of some files to avoid problems. If you do wish to move files to different directories, the following information will help you set up the programs correctly: TCMD.EXE is the Take Command/16 program file. It must be in the directory specified in the Command Line field of every desktop item that starts Take Command/16. TC16DLL.DLL is a library file used by Take Command/16. It is normally kept in the same directory as TCMD.EXE. You can move TC16DLL.DLL to the \WINDOWS\SYSTEM directory if you wish, but if you do you must move a new copy to that directory each time you update your copy of Take Command, so that the most up to date copy is always available. TCMD.HLP contains the text for the Take Command/16 help system. It must be in the same directory as TCMD.EXE. CAVEMAN.386 is the Windows device used for Caveman (see page 39). It can be in any directory as long as the ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 36 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ correct path is used in the corresponding device= line in SYSTEM.INI. CTL3DV2.DLL is a library which changes the appearance of some elements of the Windows display. It must be moved to the \WINDOWS\SYSTEM directory if necessary, and deleted from the Take Command/16 directory (see page 35 for details). If you are upgrading from a previous version of Take Command/16, you should copy any TCMD.INI file you have in the old directory to the new one. Be sure to update any paths in the file which point to the old program directory (e.g. TCStartPath). Installing Take Command/16 as the Windows Shell For complete command-line control of Windows, you can install Take Command as your Windows shell. When Windows starts it will load Take Command rather than Program Manager or any other shell. You can then start applications and perform any other work you desire from the command line. To install Take Command as the shell, first copy the TC16DLL.DLL file in your Take Command directory to your \WINDOWS\SYSTEM directory (otherwise Windows will not be able to find this file at startup). Next use SysEdit, Notepad, or another ASCII file editor to edit the SYSTEM.INI file (in your \WINDOWS directory). In the [Boot] section of SYSTEM.INI find the SHELL= line. Add a semicolon at the start of the old line to turn it into a comment (this preserves the old setting if you want to return to it in the future). Then add the following new SHELL= line: shell=d:\path\tcmd.exe Substitute the drive and path of TCMD.EXE on your system for "d:\path" in the line above. You can add any Take Command startup options (see page 28) to the shell line. Save SYSTEM.INI, close your editor, and then restart Windows for the line to take effect. More detailed information on using Take Command as your Windows shell is in the online help under Using the Take Command Interface, in the subtopic Using Take Command as the Windows Shell. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 37 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ Creating Desktop Objects for Take Command/16 This section assumes you are running Windows 3.1 or above or Windows for Workgroups, with Program Manager as the shell, and with a standard Windows desktop. If you are using an alternate shell, or you have altered your Windows desktop configuration substantially, you may need to take those changes into account as you read the instructions below. When Take Command/16 is installed it normally creates a program group which appears in the Program Manager, and includes items to run Take Command and its online help. If you want to create a new item for Take Command/16 in any group, use the Program Manager's File / New menu selection. Set the command line to d:\path\TCMD.EXE (use the appropriate drive and path for your system). Set the Description and Working Directory fields to your desired values, then click OK to create the item. No additional settings are required; the only required item is the drive and path for TCMD.EXE. However, you can put command-line switches, a command, or the name of a batch file at the end of the command line for any Take Command/16 item. This allows you to run specific commands or set configuration options when you start Take Command from that item. For details on the command line options available, see Chapter 4 and the Starting Take Command topic in the online help. For more information on creating and configuring Program Manager items see your Windows documentation. Take Command and DOS Applications This section gives a brief overview of how Take Command starts DOS applications. For complete details see Take Command and DOS Applications in the online help (under "Using the Take Command Interface"), and its subsidiary topics. You can use Take Command without going over the details in the online help; however, you should read through them before changing Take Command's default options for starting DOS programs (for example, those in the VM Setup dialog on the Options menu). When you start an external program under Windows it normally runs in its own window, which opens when the program starts and closes when it exits. You can also start a DOS program inside a 4DOS or "MS-DOS Prompt" session, and the program will run within that session. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 38 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ In its default configuration, Take Command conforms to these norms. When you start a DOS program, the program will be assigned its own window, Take Command will wait for the program to finish, and the DOS window will close when the program exits. However, this approach does not work well for command-line programs which display their output to the screen and then exit. As soon as the program exits, its window closes and the output is lost! Caveman To make it easier to use DOS programs from within Windows, Take Command includes a new technology, called "Caveman." Caveman allows DOS programs to run directly within the Take Command window. Caveman works best with simple DOS utilities which perform standard input and output. It is not recommended for use with major DOS applications like word processors, spreadsheets, and databases, and its performance and compatibility will be limited with other applications. Caveman is normally installed when you install Take Command, but it must be enabled (via the VM Setup dialog on the Options menu) before you can use it. For complete details on enabling and using Caveman, and some technical information on how Caveman works, read the online help section mentioned above (Take Command and DOS Applications, under "Using the Take Command Interface") before you begin using Caveman's features. Uninstalling Take Command/16 Manually For automated uninstall instructions, see page 25. To uninstall Take Command manually, follow these steps: * Use Notepad or another ASCII editor to edit SYSTEM.INI. In the [Boot] section, remove any SHELL= line for TCMD.EXE and replace it with a line to load Program Manager (PROGMAN.EXE) or another shell of your choice. Also look for a DEVICE= line for CAVEMAN.386 in the [386Enh] section, and remove it. These changes will take effect the next time you restart Windows. * You may want to delete CTL3DV2.DLL from the \WINDOWS\SYSTEM directory if you are certain it is ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 39 Chapter 5 / Take Command/16 Configuration and Notes ------------------------------------------------------------------ not in use by other applications (because CTL3DV2 is used fairly widely, in most cases you should not delete it). If you were using Take Command as your Windows shell there will be a copy of TC16DLL.DLL in the same directory; you can delete it as well. * Use Program Manager (or an alternate shell if you use one) to remove any Take Command groups and / or items. * Finally, check the Take Command directory for any files you placed there that you want to save. Use File Manager or a DOS session to delete the remaining files from the Take Command directory, and remove the directory. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 40 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ Chapter 6 / Take Command/32 Configuration and Notes Take Command/32 works well with Windows 95, and with Windows NT version 3.5 and later. It will not run under Windows 3.x or Windows for Workgroups, even if you have installed Microsoft's 32- bit extensions for Windows. This chapter provides basic information about Take Command/32. If you need more detailed technical information or troubleshooting assistance on any of these topics, consult the Troubleshooting, Service, and Support topic in the online help. Take Command/32 Installation Notes When you install Take Command/32, only a few changes are made to your Windows 95 or Windows NT configuration. You can allow the installation software to make these changes automatically, or you can make them yourself at a later time (see Manual Installation of Take Command/32 below for details). Depending on options you select, the installation program can move the CTL3D32.DLL file to the appropriate directory; create a folder or Start menu group for JP Software products, including Take Command; and add a small group of entries to the system registry (for more details on registry updates see page 44). Installing Take Command/32 does not normally modify the Windows 95 SYSTEM.INI, WIN.INI, CONFIG.SYS, or AUTOEXEC.BAT files, or any of your other Windows 95 or Windows NT system files. Manual Installation of Take Command/32 This section is for advanced users, and assumes you are generally familiar with the Windows desktop shell (e.g. Explorer or Program Manager), the Windows directory, and other similar topics. In most cases you can select the installation options you need using the automated installation program, and manual installation is not necessary. In order to install Take Command manually, you must extract or copy the necessary files, "brand" Take Command if necessary, modify configuration files as required, and then ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 41 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ create the necessary desktop items to start the program on your system. Extracting or Copying the Program Files When you extract or copy the Take Command files, be sure to place them in their own directory, rather than using the same directory as a previous version of the program, a directory used by other JP Software products, or a directory used by other software. We strongly recommend that you place all of the Take Command files in the same directory. See Take Command/32 Files and Directories below for some important considerations if you choose not to follow this recommendation. The method used to extract or copy the files depends on how you obtained your copy of the program: * If you have a JP Software diskette you must use the installation program to extract the files, which are compressed on the distribution disk. You cannot simply copy the files onto your hard disk. Select Custom Install and follow the prompts to specify the installation directory and copy the files. Then exit the installation program with Ctrl-X, or answer No when prompted for whether to proceed with each additional step. * If you have the JP CD Suite, all of the files are stored uncompressed on the CD, in the \TCMD32 directory, and you can copy them manually if you wish. However, we still recommend that you use the installation program to copy the files. Some files may be renamed after copying, and some files are used only during the installation process and do not need to be copied to your hard disk. If you copy the files manually, a few may not have the correct names, and you may copy more files than you need, resulting in wasted hard disk space. * If you have a downloaded copy of the program, or a copy distributed on a CD or diskette of trial software, extract the files into a new directory using the appropriate decompression program (e.g. PKUNZIP or WINZIP). ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 42 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ "Branding" Take Command/32 (If you are not familiar with branding, refer to the general information on page 22 before continuing with this section.) If you have purchased a copy of Take Command/32 the automated installation procedure will normally run the BRTC32 program to check your name, serial number, and validation code and "brand" Take Command as a registered product (in some cases Take Command/32 may not operate properly until this step is completed). If you need to brand Take Command/32 manually, start Take Command (or a 4DOS, 4NT, or "MS-DOS Prompt" session), change to the directory where Take Command/32 is stored, and enter the command: [c:\tc32200] brtc32 Follow the instructions displayed by BRTC32 to enter your name, serial number, and validation code. All information must be entered exactly as shown on your original brand card, label, or electronically delivered branding information; you cannot change spelling, capitalization, or punctuation. If you are upgrading from a previous version and using an old copy of the BRAND.EXE program distributed with that version, you must start BRAND from a command prompt session, not from Take Command, because older versions of BRAND cannot brand Take Command/32 while it is running. (The newer BRTC32 program does not have this restriction.) For a command prompt session under Windows 95 use 4DOS or COMMAND.COM; under Windows NT use 4NT or CMD.EXE. Installing CTL3D under Windows NT 3.5 (If you are using Windows 95, or Windows NT 4.0 or above, the CTL3D32.DLL file should not be installed. Delete it if it is present in your Take Command/32 directory, and skip the remainder of this section.) In order to run Take Command/32 under Windows NT 3.5 you may want to install CTL3D, a Microsoft library which gives a 3- dimensional appearance to some elements of the Windows display for programs (like Take Command) that can use it. This step is normally handled by the installation program; this section describes how to perform it manually. CTL3D for Take Command/32 is distributed in the file CTL3D32.DLL. It only works properly if there is a single copy of this file on your system, stored in the ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 43 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ \WINDOWS\SYSTEM directory; if you have more than one copy, Windows will display an error when Take Command starts. Check the CTL3D32.DLL file in your new Take Command/32 directory. If it is newer (has a later date and time) than the version in your \WINNT\SYSTEM32 directory, or if the file does not exist at all in \WINNT\SYSTEM32, move it from the Take Command directory to the \WINNT\SYSTEM32 directory. Then delete the original file so that you don't have two copies. If the version of CTL3D32.DLL in the \WINNT\SYSTEM32 directory is newer, simply delete the file from the Take Command directory. Take Command/32 doesn't require any other changes to any system files, although you may want to modify the registry as described in the next section. Updating the Registry JP Software distributes a file of registry extensions for Take Command/32, for use under Windows 95 and Windows NT 4.x (for information on registry changes for the Start menu and desktop shortcuts, see page 46). The registry extensions are stored in the file JPTCMD32.INF. Installing these extensions will: * Designate Take Command .BTM files (enhanced batch files) as batch files. They will then be recognized as such by the Windows Explorer; * Provide an additional "open" option in the context (mouse button 2) menu of all batch files, to explicitly run the file with Take Command/32; and * Create a new entry in the context menu of drives and directories to launch Take Command/32 in that drive / directory. You will have the option to install JPTCMD32.INF automatically during the Take Command/32 installation process. You can also install it manually by opening the Take Command/32 directory from within the Windows Explorer, clicking on JPTCMD32.INF with mouse button 2, and selecting INSTALL from the popup menu. If you have a downloaded trial copy of Take Command/32, JPTCMD32.INF will not be installed automatically; you must use manual installation. See the comments in the file for additional details. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 44 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ JPTCMD32.INF assumes that you have a relatively standard system configuration. If you have modified basic items in your registry (such as the characteristics of the system file type "batfile"), the registry extensions may not work correctly. To adjust the registry entries made when you install JPTCMD32.INF, open the Windows Explorer, and select Options on the View menu. Click on the File Types tab and find the listing for batch files (typically under "MS-DOS Batch File"). Use the Edit button to adjust this listing. JPTCMD32.INF also makes minor changes to the Drive and Directory types; you may want to modify these as well. Note that some of these file types may not be editable on your system, depending on the settings of various edit flags in the registry. To remove the registry entries created by JPTCMD32.INF, open the Windows Control Panel and select Add / Remove Programs. Select the item listed as "JP Software's Take Command/32 Registry Extensions (remove only)" and click the Add / Remove button. The registry extensions will be removed without further prompting. The removal operation may not work correctly if you modified the registry entries manually after they were created. JP Software's 4DOS and 4NT products also include .INF files which create registry extensions, some of which are the same as those used by Take Command/32. Therefore, if you remove the Take Command/32 extensions you will also remove some extensions used by 4DOS (under Windows 95) or 4NT (under Windows NT). If this causes a problem you can correct it by manually reinstalling the 4DOS or 4NT extensions after removing those for Take Command/32. Take Command/32 Files and Directories We strongly recommend that you place all Take Command/32 files (other than CTL3D32.DLL) in the same directory. If you do not do so, you will probably have to explicitly set the locations of some files to avoid problems. If you do wish to move files to different directories, the following information will help you set up the programs correctly: TCMD32.EXE is the Take Command/32 program file. It must be in the directory specified in the Command Line field of every desktop item that starts Take Command/32 . ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 45 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ TC32DLL.DLL is a library file used by Take Command/32. It is normally kept in the same directory as TCMD.EXE. If you wish, you can move TC32DLL.DLL to the \WINDOWS\SYSTEM directory in Windows 95, or the \WINNT\SYSTEM32 directory in Windows NT. However, if you move this file you must move a new copy to the appropriate directory each time you update your copy of Take Command, so that the most up-to-date copy is always available to Windows. TCMD32.HLP contains the text for the Take Command/32 help system. It must be in the same directory as TCMD32.EXE. CTL3D32.DLL is a library which changes the appearance of some elements of the Windows NT 3.5x display. It must be moved to the \WINNT\SYSTEM32 directory if necessary, and deleted from the Take Command/32 directory, as described on page 43. If you are running under Windows 95 or Windows NT 4.0 or above, this file should not be installed. SHRALIAS.EXE is a utility that saves the shared alias and history list between Take Command sessions. It is used by the internal command SHRALIAS. This file should be stored in the Take Command directory, or in a directory included in your PATH. If it is not, the SHRALIAS command will not work. If you are upgrading from a previous version of Take Command/32, you should copy any TCMD32.INI file you have in the old directory to the new one. Be sure to update any paths in the file which point to the old program directory (e.g. TCStartPath). Creating Desktop Objects for Take Command/32 The method you use to create a desktop object for Take Command/32 depends on whether you are using Explorer or Program Manager as your shell. Creating Explorer Shortcuts This section assumes you are running Windows 95 or Windows NT 4.x, with Explorer as your Windows shell, and with a standard Windows desktop. If you are using Program Manager, see the next section. If you have altered your Windows desktop ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 46 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ configuration substantially, you may need to take those changes into account as you read the instructions below. When Take Command/32 is installed it normally creates a JP Software program group which appears on the Start Menu under Programs, and includes items to start Take Command/32 and its online help. The installation program also creates a desktop shortcut for Take Command/32. These entries are created based on the file JPSOFT.INF, which is distributed with Take Command. If you have a downloaded trial copy of Take Command/32, JPSOFT.INF will not be installed automatically; if you want to install it you must do so manually. See the comments below and in the file for additional details. If you need to create a similar program group or shortcuts manually _ for example, if the JP Software group on the Start menu is inadvertently damaged or deleted _ you can use the Windows Explorer's facilities for creating shortcuts and modifying the desktop and / or the Start menu (see below). You can also install JPSOFT.INF manually if you wish; see the comments in the file for details. JPSOFT.INF is designed to install JP Software's 4DOS, 4NT, and Take Command/32 products under Windows 95 and Windows NT. It will install the product stored in the directory from which JPSOFT.INF is run; the entries for other products and operating systems will be ignored. To remove the desktop shortcuts and group created by JPSOFT.INF, open the Windows Control Panel and select Add / Remove Programs. Select the item listed as "JP Software program shortcuts (remove shortcuts and group)" and click the Add / Remove button. The JP Software group and all of its entries will be removed without further prompting. (To remove only the entries for a single product, use the Windows Explorer.) The removal operation may not work correctly if you modified the group or shortcuts manually after they were created. If you want to create additional shortcuts elsewhere on the Start menu, or modify the Programs entries, click mouse button 2 in an open area of the Task Bar, and select Properties on the popup menu. Select the Start Menu Programs tab and modify or adjust the menus as required. You can also manually create one or more shortcuts on the desktop to run Take Command/32. To do so click with mouse button 2 in any open area of the desktop. On the popup menu ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 47 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ click New, then Shortcut. Fill in the drive and path as d:\path\TCMD32.EXE (use the appropriate drive and path for your system). Add any other command line options you wish to set to the end of the line. You can also put command-line switches, a command, or the name of a batch file at the end of the command line for any shortcut. This allows you to run specific commands or set configuration options when you start Take Command/32 from that shortcut. For details on the command line options available, see Chapter 4 and the Starting Take Command section of the online help. For more information on creating and configuring shortcuts or modifying the Start Menu, see your Windows 95 or Windows NT documentation. Creating Program Manager Items This section applies to Windows NT 3.5 or 3.51 with Program Manager as the shell. When Take Command/32 is installed it normally creates a program group which appears in the Program Manager, and includes items to run Take Command/32 and its online help. If you want to create a new item for Take Command/32 in any group, use the Program Manager's File / New menu selection. Set the command line to d:\path\TCMD32.EXE (use the appropriate drive and path for your system). You can put command-line switches, a command, or the name of a batch file at the end of the command line for any item. This allows you to run specific commands or set configuration options when you start Take Command/32 from that item. Character-Mode Applications When you start a DOS program or a 32-bit Windows character- mode program under Take Command/32, it runs in a special "console session." The console session displays a separate window without a standard menu bar or other Windows features. This section gives a brief overview of how the console window works, and how you can run character-mode applications from Take Command/32. For complete details see Console Applications and the Console Window in the online help (under "Using the Take Command Interface"). ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 48 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ The console session window is connected to Take Command/32, and is created when Take Command starts. You can view it at any time with the Alt-V key or the View Console selection on the Apps menu. When you start a DOS or character-mode application from Take Command/32 it is run in the console session. The console window automatically becomes visible when the application starts, and is normally hidden when the application exits. If you run a DOS or character-mode program which does not exit immediately (for example, a DOS word processor or editor) you will be able to work in the console session, and return automatically to Take Command when you exit the application. If you run a DOS or character-mode application from Take Command and the application exits quickly, without waiting for any input (for example, a utility like PKUNZIP), you may have to use Alt-V to return to the console window and view the output. Caveman To make it easier to use character-mode applications from within Windows, Take Command/32 includes a technology called "Caveman." Caveman allows DOS and 32-bit Windows character- mode programs to run directly within the Take Command window, and eliminates the need to switch to a separate console window. When Caveman is running in Take Command/32, it continually scans the console window and updates the Take Command window with any changes it finds. It also sends keystrokes from the Take Command window to the console window. Caveman makes a character mode program appear to run in the Take Command window even though it is, in reality, running in the console session window. For complete details on Caveman see the Console Applications and the Console Window and Caveman topics in the online help (both accessible under "Using the Take Command Interface"). Due to limitations in the way character-mode programs can operate under Windows, the techniques used by Caveman do not work well with all programs. The online help explains how to enable Caveman, and how to set up your system to make the best use of Take Command/32 and Caveman. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 49 Chapter 6 / Take Command/32 Configuration and Notes ------------------------------------------------------------------ Uninstalling Take Command/32 Manually For automated uninstall instructions, see page 25. To uninstall Take Command manually, follow these steps: * If you installed the Take Command/32 registry extensions, start by removing them as described on page 45. * Use the Windows Explorer or Program Manager to remove any shortcuts or desktop objects for Take Command/32, or manually uninstall the JPSOFT.INF file as described on page 47. * If you are running under Windows NT 3.5 or 3.51 you may want to delete CTL3D32.DLL from the \WINNT\SYSTEM32 directory if you are certain it is not in use by other applications (because CTL3D32 is used fairly widely, in most cases you should not delete it). * Finally, check the Take Command directory for any files you placed there that you want to save. Then use File Manager, Explorer, or a DOS session to delete the remaining files and the Take Command directory. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 50 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ Chapter 7 / Take Command for OS/2 Configuration and Notes Take Command for OS/2 works well with OS/2 version 3.0 (Warp) or later. It will not run under earlier versions of OS/2. This chapter provides basic information about Take Command for OS/2. If you need more detailed technical information or troubleshooting assistance on any of these topics, consult the Troubleshooting, Service, and Support topic in the online help. Take Command for OS/2 Installation Notes When you install Take Command for OS/2 a few changes must be made to your OS/2 configuration. You can allow the installation software to make these changes automatically, or you can make them yourself at a later time (see Manual Installation of Take Command for OS/2 below for details). The installation program will normally modify the BOOKSHELF, DPATH, and LIBPATH settings in the OS/2 CONFIG.SYS file to include the Take Command for OS/2 directory, and will create a folder for Take Command on your OS/2 desktop. Installing Take Command for OS/2 does not modify, remove, or otherwise alter any of your other OS/2 system files. Manual Installation of Take Command for OS/2 This section is for advanced users, and assumes you are generally familiar with the OS/2 Presentation Manager shell, OS/2 directories and the CONFIG.SYS file, and other similar topics. In most cases you can select the installation options you need using the automated installation program, and manual installation is not necessary. In order to install Take Command manually, you must extract or copy the necessary files, "brand" Take Command if necessary, modify configuration files as required, and then create the necessary desktop items to start the program on your system. Extracting or Copying the Program Files When you extract or copy the Take Command files, be sure to place them in their own directory, rather than using the same directory as a previous version of the program, a directory ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 51 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ used by other JP Software products, or a directory used by other software. We strongly recommend that you place all of the Take Command files in the same directory. See Take Command for OS/2 Files and Directories below for some important considerations if you choose not to follow this recommendation. The method used to extract or copy the files depends on how you obtained your copy of the program: * If you have a JP Software diskette you must use the installation program to extract the files, which are compressed on the distribution disk. You cannot simply copy the files onto your hard disk. Select Custom Install and follow the prompts to specify the installation directory and copy the files. Then exit the installation program with Ctrl-X, or answer No when prompted for whether to proceed with each additional step. * If you have the JP CD Suite, all of the files are stored uncompressed on the CD, in the \TCMDOS2 directory, and you can copy them manually if you wish. However, we still recommend that you use the installation program to copy the files. Some files may be renamed after copying, and some files are used only during the installation process and do not need to be copied to your hard disk. If you copy the files manually, a few may not have the correct names, and you may copy more files than you need, resulting in wasted hard disk space. * If you have a downloaded copy of the program, or a copy distributed on a CD or diskette of trial software, extract the files into a new directory using the appropriate decompression program (e.g. PKUNZIP or OS/2 UNZIP). "Branding" Take Command for OS/2 (If you are not familiar with branding, refer to the general information on page 22 before continuing with this section.) If you have purchased a copy of Take Command for OS/2 the automated installation procedure will normally run the BRTCOS2 program to check your name, serial number, and validation code and "brand" Take Command as a registered product (in some cases Take Command for OS/2 may not operate ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 52 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ properly until this step is completed). If you need to brand Take Command for OS/2 manually, start Take Command (or an OS/2 Full-Screen or OS/2 Windowed command prompt session), change to the directory where Take Command for OS/2 is stored, and enter the command: [c:\tcos2200] brtcos2 Follow the instructions displayed by BRTCOS2 to enter your name, serial number, and validation code. All information must be entered exactly as shown on your original brand card, label, or electronically delivered branding information; you cannot change spelling, capitalization, or punctuation. If you are upgrading from a previous version and using an old copy of the BRAND.EXE program distributed with that version, you must start BRAND from a command prompt session, not from Take Command, because older versions of BRAND cannot brand Take Command for OS/2 while it is running. (The newer BRTCOS2 program does not have this restriction.) For a command prompt session use 4DOS, 4OS2, COMMAND.COM, or CMD.EXE. Updating CONFIG.SYS When you're ready to finish installing Take Command for OS/2, you need to make three changes to your CONFIG.SYS file. Use an ASCII editor to make these changes. The examples below assume that Take Command is installed in the C:\TCOS2200 directory; if you use a different directory, alter the instructions accordingly. First, find the three lines that begin with SET BOOKSHELF, SET DPATH, and LIBPATH (these lines may not all be together in CONFIG.SYS). Each is a list of directories separated by semicolons, for example: SET BOOKSHELF=C:\OS2\BOOK;... SET DPATH=C:\OS2;... LIBPATH=C:\OS2\DLL;... Add a semi-colon [;] and the name of the Take Command directory to the end of each line: SET BOOKSHELF=C:\OS2\BOOK;...;C:\TCOS2200 SET DPATH=C:\OS2;... ;C:\TCOS2200 LIBPATH=C:\OS2\DLL;... ;C:\TCOS2200 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 53 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ Check the changes you have made and save the CONFIG.SYS file. Then exit from your editor, shut down OS/2, and reboot your system. Take Command for OS/2 Files and Directories We strongly recommend that you place all Take Command for OS/2 files in the same directory. If you do not do so, you will probably have to explicitly set the locations of some files to avoid problems. If you do wish to move files to different directories, the following information will help you set up the programs correctly: TCMDOS2.EXE is the Take Command for OS/2 program file. It must be in the directory specified in the Command Line field of every OS/2 desktop object that starts Take Command . JPOS2DLL.DLL is a library used by TCMDOS2.EXE (and by 4OS2). This file must be in a directory listed in the LIBPATH setting in CONFIG.SYS. If you prefer, you can move this file into the standard OS/2 DLL directory, \OS2\DLL. TCMDOS2.INF contains the text for the Take Command help system. For the help system to work properly, the directory containing this file must be included in the SET BOOKSHELF command in CONFIG.SYS. If you prefer, you can move this file into the standard OS/2 bookshelf directory, \OS2\BOOK. TCMDOS2H.MSG contains the help text for the /? option that is available as part of each internal command. For this feature to work properly, the directory containing this file must be included in the SET DPATH command in CONFIG.SYS. If you prefer, you can move this file into the standard OS/2 directory for such files, \OS2\SYSTEM. KEYSTACK.EXE is a utility used by the KEYSTACK command to pass keystrokes to other applications. For the KEYSTACK command to work, this file must be in the same directory as TCMDOS2.EXE, or in a directory included in your PATH. SHRALIAS.EXE is a utility used by the SHRALIAS command to save the shared alias and history lists between Take Command sessions. For the SHRALIAS command to work, ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 54 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ this file must be in the same directory as TCMDOS2.EXE, or in a directory included in your PATH. TCNPDOS.COM is a utility used by Take Command for OS/2 to run DOS "TTY" Applications (see page 57 for details). This file must be in the same directory as TCMDOS2.EXE. If you are upgrading from a previous version of Take Command for OS/2 you should copy any TCMDOS2.INI file you have in the old directory to the new one. Be sure to update any paths in the file which point to the old program directory (e.g. TCStartPath). Creating Desktop Objects for Take Command for OS/2 This section assumes you are running OS/2 Warp 4, with the default desktop shell and a standard OS/2 desktop. If you are using an earlier version of OS/2 or a different shell, or have altered your OS/2 desktop configuration substantially, you will need to take those changes into account as you read the instructions below. The Take Command for OS/2 installation program normally creates a desktop folder which contains objects to start Take Command for OS/2 and its online help. If you want to create additional objects in other folders, or directly on the desktop, click mouse button 2 on the installed Take Command for OS/2 object, select Copy on the popup menu, and copy the object to another location as desired. You can then alter the properties of the new object if you wish. If you need to create a new object, switch to the folder where you want the object to appear and either copy an existing object (use the Copy or Create Another selection on the object's popup menu) or drag a Program Template in from the Templates folder. The new object's Properties notebook should open automatically. Use the Program page of the notebook to set the file name to d:\path\TCMDOS2.EXE (use the appropriate drive and path for your system). Then modify the parameters and startup directory as required. No additional settings are required; the only required item is the drive and path for TCMDOS2.EXE. However, you can put command-line switches, a command, or the name of a batch file in the Parameters field for any object. This allows you to run specific commands or set configuration options when you start Take Command for OS/2 from that object. For details on the command line options available, see Chapter 4 and the Starting Take Command topic in the online help. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 55 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ For more information on creating and configuring desktop objects see your OS/2 documentation. The Take Command for OS/2 Help System The Take Command for OS/2 help text, in the file TCMDOS2.INF, covers Take Command for OS/2 features and internal commands. OS/2 includes many other help files _ for example, a complete reference to all internal and external commands in the reference book named CMDREF.INF. You can specify a different set of help files or "books" to be opened when HELP or F1 is invoked with the HelpBook directive in TCMDOS2.INI, or the corresponding entry on the Options 2 page in the configuration notebook. For example, to set up Take Command for OS/2 so that both the CMDREF book and Take Command for OS/2 book are displayed when F1 is pressed, include the following directive in TCMDOS2.INI, or make the corresponding change in the configuration notebook: HelpBook=TCMDOS2+CMDREF When more than one book is listed in the HelpBook setting, the OS/2 help program will see the combined group as a single book. The displayed Table of Contents will include the tables of contents from all the listed books, joined together as one group of topics with no divisions to show where one book ends and the next begins. If any of the listed books are not available the help program will not start. The Take Command installation program sets up a separate object for Take Command help so that you can load the help file directly. To create a similar object manually, use entries like this on the Program page of the object's Settings notebook: Path and File Name: VIEW.EXE Parameters: TCMDOS2 Working Directory: d:\path where "d:\path" is the directory where you installed Take Command for OS/2. The help system can also be used to obtain help on OS/2 error codes. If you type either of these commands: [c:\] help nnnn [c:\] help sysnnnn ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 56 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ where "nnnn" is an OS/2 system error number, HELP will display an explanation of the OS/2 error. This feature works by running the OS/2 program HELPMSG.EXE which opens the file OSO001.H to get the explanation. For this feature to work, HELPMSG.EXE must be in a directory that is in your PATH, and the data file OSO001H.MSG must be in a directory in your DPATH (OS/2 sets up HELPMSG.EXE and OS0001H.MSG this way by default). Character-Mode Applications This section gives a brief overview of how the Take Command for OS/2 TTY Applications facility works. For complete details before using this feature, see Starting Character- Mode Applications in the online help (under "Using the Take Command Interface"). Take Command for OS/2 starts OS/2 "graphical" applications in their own windows, just as if you had started them from the desktop. By default, it also creates a separate character- mode window to run each DOS or OS/2 character mode application you start. If you prefer, you can run some DOS and OS/2 character-mode applications within the Take Command window, using an OS/2 facility called "named pipes." When you use this option, output from the application is displayed in the Take Command window, and no separate window is created. Because not all applications work properly with named pipes, you must specify which applications should be run as TTY applications within the Take Command window. To do so, use the TTY Applications dialog (accessible from the Setup menu). The online help explains in more detail how you can use this dialog to include and exclude programs from TTY application support by both file name and location. TTY application support for DOS programs depends on the TCNPDOS.COM file distributed with Take Command. This file must be in the same directory as TCMDOS2.EXE. If it is not, Take Command will display an error message if you try to run a DOS application within the Take Command window. Uninstalling Take Command for OS/2 Manually For automated uninstall instructions, see page 25. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 57 Chapter 7 / Take Command for OS/2 Configuration and Notes ------------------------------------------------------------------ To manually remove Take Command from your system, follow these steps: * Delete any desktop objects that refer to Take Command for OS/2. * Use an ASCII editor to edit your CONFIG.SYS file. Search the file for any other mention of the Take Command directory. In a typical installation, the directory name will be listed in the SET BOOKSHELF, SET DPATH, and LIBPATH lines. You may also have added it to the SET PATH line (although the installation program does not do so). Remove each reference to the Take Command directory, but leave the rest of each line unchanged. When you have made these changes, save the CONFIG.SYS file. Then shut down OS/2 and restart your system. * Use the Drives icon or a 4OS2, 4DOS, OS/2 Full Screen, or OS/2 Window prompt to check the Take Command directory for any files you placed there that you want to save. Then delete the remaining files and the Take Command directory. ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 58 Index ------------------------------------------------------------------ Index Character-mode applications, see Applications Clipboard, 16 4 Colors, setting, in Take Command/32, 30 4DOS product, 2 Command history, local and 4NT product, 2 global, 30 4OS2 product, 2 Command line enhancements, 14 Command line options, see Startup options A Command window, 11 Commands Aliases, 17 new and enhanced, 11 local and global, 30 startup, see Startup technical support for, 6 options Applications, character-mode COMSPEC path, 29 and DOS CONFIG.SYS, changes for Take under Take Command for Command for OS/2, 53 OS/2, 57 Configuration, 16, 28 under Take Command/16, 38 .INI file, 31 under Take Command/32, 48 dialogs, 31 Apps menu, 11 OPTION command, 31 starting Take Command, 28 startup options, 28 B Take Command for OS/2, 51 Take Command/16, 33 Batch files, 18 Take Command/32, 41 startup, see Startup TCSTART and TCEXIT, 31 options Console session, in Take technical support for, 6 Command/32, 48 under Windows 95 and Contacting JP Software, 4 Windows NT, 44 CTL3D BOOKSHELF setting, for Take for Take Command/16 Command for OS/2, 53, 58 installation, 35 Branding, 22 location of .DLL file, Take Command for OS/2, 52 35, 37 Take Command/16, 34 removing, 39 Take Command/32, 43 for Take Command/32 upgrades, 23, 24 installation, 43 .BTM files, see Batch files location of .DLL file, 44, 46 removing, 50 C Customer service, 4 Caveman for Take Command/16, 39 D CAVEMAN.386 device, 36 installation, 36 DDE, 16 removing, 39 Directory history list, local for Take Command/32, 49 and global, 30 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 59 Index ------------------------------------------------------------------ DOS applications, see Caveman (Take Command/16), Applications 36 DPATH setting, for Take CTL3D Command for OS/2, 53, 58 for Take Command/16, Drag and Drop, 16 35 for Take Command/32, 43 E custom, 22 directory Edit menu, 11 Take Command for OS/2, Enhancements 51, 54 aliases and batch files, Take Command/16, 34, 17 36 command line, 14 Take Command/32, 42, commands, 11 45 configuration, 16 downloaded trial copy, 23 electronically purchased copy, 21 F express, 22 from diskette, 21 File associations, 16 from JP CD Suite, 21 File locations, see manual Installation directory Take Command for OS/2, File menu, 10 51 Take Command/16, 33 Take Command/32, 41 H reversing, 25 Take Command for OS/2, Help menu, 11 57 Help system, 4, 26 Take Command/16, 39 /? option, 26 Take Command/32, 50 key topics in, 27 upgrades, 20 location of files Internet Take Command for OS/2, JP Software addresses on, 54 4 Take Command/16, 36 support via, 7 Take Command/32, 46 Take Command for OS/2 notes, 56 J JP Software, contacting, 4 I JPTCMD32.INF, see Microsoft Windows 95 and Windows NT, .INI directives, on startup registry extensions command line, 30 .INI file, 31 location of, 29 sections, 31 Installation, 20 automatic, 20 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 60 Index ------------------------------------------------------------------ L OS/2 (continued) system error codes, 56 LIBPATH setting, for Take versions of, 2 Command for OS/2, 53, 58 Local and global aliases and history, 30 P Popup menus, Windows 95 and M Windows NT, adding Take Command/32, 44 Menu bar, 10 Program Manager Microsoft Windows groups and applications, configuration, modifying 16 for Take Command/16, 33 replacing, 37 desktop objects, for Take Prompt Solution newsletter, 8 Command/16, 38 SYSTEM.INI Caveman, installing, Q 36 Caveman, removing, 39 Quick help, 26 changing Windows Take Command for OS/2, 54 shell, 37 Take Command as shell, 37 versions of, 1 R Microsoft Windows 95 and Windows NT README.TXT, 4 and Take Command/32 batch Reference manual, 3 files, 44 Registration, 8 popup menus, adding Take Registry, see Microsoft Command/32, 44 Windows 95 and Windows NT Program Manager items, for Take Command/32, 48 registry extensions for S Take Command/32, 44 removing, 45, 50 Service, 4 shortcuts, for Take Shortcuts, for Take Command/32, 46 Command/32, 46 versions of, 1 Start menu, adding Take Command/32, 46 Starting Take Command, 28 O Startup files, 31 OPTION command, 31 options, 27, 28 Options menu, 11 commands, 30 OS/2 for Take Command for creating desktop objects, OS/2, 55 for Take Command for for Take Command/16, OS/2, 55 38 named pipes, 57 for Take Command/32, 48 ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 61 Index ------------------------------------------------------------------ Status bar, 11 Take Command/32 (continued) Support, 5 directory, 42, 45 SYSTEM.INI, see Microsoft manual, 41 Windows notes, 41 uninstalling, 50 TCEXIT, 31 T TCMD.HLP, 36 TCMD.INI, TCMD32.INI, and Take Command TCMDOS2.INI, see .INI file and Windows and OS/2 TCMD32.HLP, 46 features, 16 TCMDOS2.INF, 54, 56 as Windows Shell, 37 TCSTART, 31 removing, 39 and startup command, 30 window, 10 Technical support, 5 Take Command for OS/2 consulting services, 6 and character-mode or DOS for aliases and batch applications, 57 files, 6 and operating system Title bar, 10 versions, 51 Tool bar, 11 branding, 52 TTY applications, 55, 57 configuration, 51 creating desktop objects for, 55 U folder, 55 installation Uninstalling, 25 directory, 51, 54 Take Command for OS/2, 57 manual, 51 Take Command/16, 39 notes, 51 Take Command/32, 50 uninstalling, 57 Upgrades, 8 Take Command/16 branding, 23, 24 and DOS applications, 38 installing, 20 and operating system Utilities menu, 11 versions, 33 branding, 34 configuration, 33 creating desktop objects for, 38 installation directory, 34, 36 manual, 33 notes, 33 uninstalling, 39 Take Command/32 and character-mode or DOS applications, 48 and operating system versions, 41 branding, 43 configuration, 41 installation ------------------------------------------------------------------ Copyright 1997 JP Software Inc. Take Command Install Guide / 62