





















                                        4DOS


                                        4NT


                                    Take Command




                        Introduction and Installation Guide


                                    Published By
                                  JP Software Inc.
                                    P.O. Box 328
                             Chestertown, MD 21620 USA

                                   (410) 810-8818
                                 Fax (410) 810-0026 

















                                  ACKNOWLEDGMENTS

             We couldn't produce products like 4DOS, 4NT, and Take Command
             without the dedication and quality work of many people.  Our
             thanks to:

               JP Software Staff:  Mike Bessy, Celeste Conn.

               On-line Support:  Blueberry Hill Communications (Palm
               Desert, CA).

               Installation Scripting:  Mark Zembrzuski, Spudsian Software
               & Service.

               Beta Testers:  We can't list all of our beta testers here!
               A special thanks to all of you who helped make 4DOS, 4NT,
               and Take Command elegant, reliable, and friendly.


             Copyright 2003, JP Software Inc., All Rights Reserved.  4DOS
             and 4NT are JP Software Inc.'s trademarks for its family of
             character-mode command processors.  4DOS and Take Command are
             registered trademarks and JP Software, jpsoft.com, and all JP
             Software designs and logos are trademarks of JP Software Inc.
             Other product and company names are trademarks of their
             respective owners.

                                                                      2003-2


                                                                    CONTENTS



        CONTENTS

        Introduction..............................................3
            How to Use This Manual................................4
            Contacting JP Software................................5
            Technical Support.....................................6
                Support Plans.....................................6
                Before You Contact Us.............................6
                Online Support....................................8
            Upgrade Information...................................8
        Chapter 1 / Introducing 4DOS, 4NT, and Take Command......10
            Built-In Commands....................................12
            The Command Line.....................................14
            The Take Command Window..............................16
            Working with Windows.................................17
            Networks and Remote Systems..........................17
            Configuration........................................18
            Aliases and Batch Files..............................18
        Chapter 2 / Installation.................................22
            Preparing for Installation...........................22
            Performing the Installation..........................22
                Installing an Upgrade............................23
                Desktop, Registry, and System File Changes.......23
            Extracting or Repairing Product Files................24
            Uninstalling the Program.............................25

        Chapter 3 / The Help System..............................27
            Using the Help System................................27
            Important Help Topics................................28
        Chapter 4 / 4DOS and 4NT Startup.........................29
            Primary and Secondary Shells.........................29
            Command Line Options.................................30
            Creating or Modifying Startup Files..................36
            Exit Codes...........................................37
        Chapter 5 / 4DOS Configuration and Notes.................38
            4DOS Installation Notes..............................38
                Older Versions of DOS............................38
            Manual Installation of 4DOS..........................39
                Extracting or Copying the Program Files..........39
                Branding 4DOS....................................39
                Updating CONFIG.SYS and AUTOEXEC.BAT.............41
                Creating or Copying 4DOS.INI.....................42
                4DOS Files and Directories.......................43
                Creating 4DOS Shortcuts..........................44
            The 4DOS Help System.................................45


        4DOS, 4NT, Take Command Introduction and Installation Guide                i 


        CONTENTS


            4DOS and Your Computer...............................45
            4DOS and DOS.........................................47
            4DOS and Microsoft Windows 95, 98, and ME............47
                Installing 4DOS Under Windows 95/98/ME...........48
                Installing the KSTACK Program in Windows 95/98/ME 48
            Using 4DOS on a Network..............................49
                4DOS and Novell Netware..........................50
            Uninstalling 4DOS Manually...........................50
        Chapter 6 / 4NT Configuration and Notes..................53
            4NT Installation Notes...............................53
            Using 4NT Under Windows 98, and ME...................53
            Manual Installation of 4NT...........................55
                Extracting or Copying the Program Files..........55
                Registering 4NT..................................56
                4NT Files and Directories........................56
                Creating 4NT Shortcuts...........................57
            The 4NT Help System..................................57
            Uninstalling 4NT Manually............................58

        Chapter 7 / Take Command Startup and Configuration.......61
            Starting Take Command................................61
            Command Line Options.................................61
            Creating or Modifying Startup Files..................64
            Exit Codes...........................................65
            Manual Installation of Take Command..................66
                Extracting or Copying the Program Files..........66
                Registering Take Command.........................66
                Take Command Files and Directories...............67
                Creating Take Command Shortcuts..................67
            Character-Mode Applications..........................68
                Caveman..........................................69
            Uninstalling Take Command Manually...................69
        Index....................................................71


















        ii                                      (c) 2003 JP Software Inc. 


                                                                 INTRODUCTION



        INTRODUCTION

        Welcome, and thanks for using 4DOS, 4NT, or Take Command!

        We started developing these products when we realized that our
        computers could be a lot more powerful and a lot more helpful than
        they were.  Whether you are a computer novice or an experienced
        power user, we think that our products will help you get the most
        out of your computer.

        We offer three products for different operating systems:

           * You can use 4DOS with all versions of MS-DOS and PC DOS from
             3.1 through 7.1 and above, including Windows 95, 98, and ME
             ("MS-DOS 7" is the DOS portion of Microsoft Windows 95/98/ME).
             You can also use it with all versions of DR DOS / Novell DOS /
             OpenDOS from 3.4 through 7.0 and above, and in DOS sessions
             started under Windows 95/98/ME, and under Windows 3.x and OS/2
             Warp.

           * You can use 4NT with Windows NT 4.0, Windows 2000, Windows XP,
             Windows 98, and Windows ME.

           * Take Command brings the power of 4DOS and 4NT to the Windows
             desktop and adds many new features.  You can use it with
             Windows 95, Windows 98, Windows ME, Windows NT 4.0, Windows
             2000, and Windows XP.

        Once you have 4DOS, 4NT, or Take Command installed, you can learn
        to use it at your own pace.  Each program has more than 100
        commands and hundreds of enhanced features, but you don't have to
        learn them all, or learn them all at once.  Relax, enjoy the
        program's power, and browse the manual occasionally.  Press the F1
        key whenever you need help.  These programs will soon become an
        essential part of your computer, and you'll wonder how you ever got
        along without them.

        We are constantly working to improve our products.  If you have
        suggestions for features or commands that you think we should
        include in the next version, or any other way we could improve our
        product, please let us know.  Many of the improvements in this
        version were suggested by our users, and while we can't promise to
        include every suggested feature, we really do appreciate and
        consider your comments.

        4DOS, 4NT, and Take Command are related programs.  You can use them
        to maintain a common working environment and run the same commands,


        4DOS, 4NT, Take Command Introduction and Installation Guide                3 


        INTRODUCTION


        batch files, and aliases under DOS, Windows 95/98/ME, and Windows
        NT/2000/XP.  Additional products for use on the same system are
        available at a discounted price for current 4DOS, 4NT, and Take
        Command users.

        Our JP CD Suite includes all three 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 4DOS, 4NT, or Take Command.  It introduces the
             products and helps you install them correctly on your
             computer.  It also gives you specific information about using
             the program in your particular environment (for example, using
             4DOS under Windows 98).

             The second and third parts of our documentation are the online
             help and the reference manual.  They contain complete
             information about the commands and features of 4DOS, 4NT, and
             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 the program,
             move on to the online help or reference manual 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
             (particularly if you are using 4DOS under Windows 95/98/ME).
             However, in many cases you will not need the information in
             Chapters 4 - 7 unless you are working at a more technical
             level, or run into some unexpected difficulty.

             Most of the first part of this manual describes commands and
             features that are available in all three products.  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
             text in the margin to identify that product:

        4DOS



        4                                       (c) 2003 JP Software Inc. 


                                                                 INTRODUCTION


                  Sections that apply only to 4DOS.

        4NT

                  Sections that apply only to 4NT.

        TC

                  Sections that apply only to Take Command.

             Each of our products also includes complete online help for
             all commands.  The 4DOS help system can be configured to link
             to help on standard DOS commands as well, if the corresponding
             help files and programs are available on your system.  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 information.  See page 27 for more
             information about the online help.

             Check README.TXT for last-minute notes on the current release,
             or if you are installing a downloaded update to 4DOS, 4NT, or
             Take Command.

        Contacting JP Software

             You can contact JP Software at the following addresses and
             numbers.  Our normal business hours are 9:00 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 328
                                 Chestertown, MD 21620  USA

                Main number:     (410) 810-8818
                Fax:             (410) 810-0026
                Order Line:      (410) 810-8819

                Online:          Web:  http://jpsoft.com/
                                 FTP:  ftp://jpsoft.com
                                 Sales:  sales@jpsoft.com
                                 Customer Service:  support@jpsoft.com

                Technical Support:            Standard (free) support:
                                 Available via our online support forum,


        4DOS, 4NT, Take Command Introduction and Installation Guide                5 


        INTRODUCTION


                                 accessible from the support area of our
                                 web site.  See page 8 for additional
                                 details.  See Technical Support below for
                                 additional information on paid support
                                 options.

             To access JP Software files use our web site or FTP site
             listed above.  Our files are also available from other on-line
             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

             (If you need help with sales, ordering, shipments, brand
             codes, or other similar non-technical issues please contact
             our Sales and Customer Service department.  See the previous
             section for our addresses.)

             Support Plans

             Standard support is available through our support forum (see
             page 8).

             We also offer a paid support option that includes automatic
             upgrades and support by private email or telephone.

             For complete details on all support options, including plans
             currently offered and support terms and conditions, see our
             web site at http://jpsoft.com/.  Support plan availability and
             pricing can change, so be sure to check web site for the most
             up to date information.

             Before You Contact Us

             Before contacting us for support, please check this manual,
             the online help, the Reference Manual if available to you, 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 4DOS, 4NT, or Take Command to run properly,
             see the Troubleshooting, Service, and Support topic in the
             online help for any relevant information (in 4DOS, check the
             Compatibility section as well), 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

        6                                       (c) 2003 JP Software Inc. 


                                                                 INTRODUCTION


             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 you are 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 VER /R command to determine the
                  command interpreter 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, 4START, 4EXIT,
                  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?  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 alias, please
             include an exact copy of the batch file or alias in question,
             as part of the text of your message (not as an attachment).
             If your batch file is longer than about 25 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.





        4DOS, 4NT, Take Command Introduction and Installation Guide                7 


        INTRODUCTION


             Online Support

             The best way to contact us for technical support is via our
             online support forum, where our support personnel can read and
             respond to your messages, and other users can respond as well.
             The forum is accessible via several methods; for complete
             details see the support area of our web site at
             http://jpsoft.com/.

             A number of other support resources are available from our web
             site, 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.

             If you are unable to gain access to the forum, or if you need
             to include confidential information in your support request,
             contact us via email at support@jpsoft.com.  Please do not use
             this address for standard support questions that can be posted
             on the forum.

             If you are a paid support customer, you should use the
             electronic support forum for routine questions.  To create a
             private support incident refer to the materials sent to you
             with your subscription for contact information, or email
             priority_support@jpsoft.com and include your support ID (mail
             to this address may not be answered if it does not include a
             valid support ID).

             Technical support messages should be sent as standard ASCII
             text.  Please do not transmit attached files, binary files,
             screen images, or files over 10K bytes in size to any of our
             electronic technical support addresses unless asked to do so
             by our support staff.

        Upgrade Information

             Our products are upgraded regularly through maintenance
             releases, designed to fix minor problems or improve
             compatibility, and major upgrades that contain enhancements
             and additional features.  Maintenance releases are identified
             by a change in the hundredths digit of the version number, for
             example from 5.0 to 5.01 or 5.02, or in a letter suffix (e.g.
             5.01B).  Major upgrades are identified by a change in the
             tenths digit or "ones" digit, for example from 5.0 to 5.1 or
             6.0.


        8                                       (c) 2003 JP Software Inc. 


                                                                 INTRODUCTION


             Major upgrades can be purchased from JP Software or your
             dealer.  You can download maintenance releases from our web
             (http://jpsoft.com/) or FTP  (ftp://jpsoft.com) sites.  You
             can also order copies on CD-ROM at a nominal cost.

             If you want to know when a product update is available, visit
             our web site at http://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.













































        4DOS, 4NT, Take Command Introduction and Installation Guide                9 


        Chapter 1 / Introducing 4DOS, 4NT, and Take Command



        Chapter 1 / Introducing 4DOS, 4NT, and Take Command






















































        10                                      (c) 2003 JP Software Inc. 








        4DOS and 4NT are command interpreters or "shells."  That means that
        they display a prompt, wait for you to type something, and then
        react to your commands (we use the [C:\] prompt in this manual, but
        you can customize the prompt to use any format you prefer).  Our
        programs replace the default command interpreters that are supplied
        with your operating system.  4DOS replaces COMMAND.COM for DOS and
        Windows 95/98/ME.  4NT replaces CMD.EXE for command sessions under
        Windows NT 4.0, Windows 2000, and Windows XP.

        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 our
        command interpreters.  If you're not used to using the command
        line, you'll quickly come to value its power and flexibility, and
        appreciate our programs' comprehensive online help and the way they
        make the command prompt straightforward and easy to use.

        4DOS and 4NT understand all of the commands you already know and
        add to them.  Their purpose is to make the command line friendlier,
        easier to use, and much more powerful and versatile without
        requiring you to use or learn a new program, a new set of commands,
        or a new style of work.

        Take Command brings the power and convenience of 4DOS and 4NT to
        the Windows desktop.  You're probably already familiar with
        graphical applications running under Windows 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 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 it is more
        convenient or productive to perform them from the command line.
        Take Command can use fewer resources than starting a command-line
        session, and it looks and feels like the other graphical programs
        you use.

        In this section, we introduce a few of the features we have built
        into our products.  We don't have room to list them all or to
        explain all of the options available in each; that's for the online


        4DOS, 4NT, Take Command Introduction and Installation Guide               11 





        help and Reference Manual.  This section will just give you a taste
        of what you can expect from your computer once you have your new
        command interpreter installed.

        As you read this section, remember that you don't have to use any
        of these features except the ones that appeal to you.  Learn the
        parts that will make your computer easier for you to use, and add
        to your repertoire as you need them.

        Built-In Commands

             The 4DOS and 4NT command lines, and Take Command's command
             window (see page 16) are the heart of our products.  It is
             here that you type commands for the program to execute, and
             here that the program displays the output of each command.

             Our products support every command you already know, add to
             the features of each command, and add dozens of new commands.

             For example, the traditional DIR command has about a dozen
             options.  The DIR command in our products has the same options
             plus about 20 more.  With the enhanced DIR command, you can:

                * 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.

                * 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*

             That's just an example of some of the enhancements we have
             added to one command.  4DOS, 4NT, and Take Command have added
             enhancements to virtually every command you've used before and
             include dozens of new commands as well.  You don't have to
             learn to use them all, but you will find many commands and

        12                                      (c) 2003 JP Software Inc. 





             enhancements that will make your computer more powerful and
             easier to use.  For example:

                * COLOR lets you set the default colors to use on your
                  display or in the Take Command window:

                     [c:\] color bright white on blue

                  Additional features let you customize the colors you 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:

                     [c:\] list readme.txt

                * The FFIND command and the Find Files / Text dialog in
                  Take 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:

                     [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 "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 -
                         - and a related feature, "exclude" ranges -
                                                                   - let
                  you work with all of the files in a directory except
                  those that you want to exclude.  This command copies all
                  files from the current directory to drive A: except
                  backup (.BAK and .BK!) files:

                     [c:\] except (*.bak;*.bk!) copy *.* a:








        4DOS, 4NT, Take Command Introduction and Installation Guide               13 





        The Command Line

             4DOS, 4NT, and Take Command are much more than just a
             collection of commands.  They include a number of features
             that make the command line easier to use:

                * Interactive help appears whenever you ask for it, and any
                  time you use a command incorrectly.  Type:

                     [c:\] help

                  when you need help -
                                     - or just press F1, or in Take
                  Command), select Contents from the Help menu.  If you
                  have typed part of a command, F1 displays help on the
                  first word on the command line.  Ctrl-F1 displays help
                  for the word at the cursor.

                * 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 character or a word,
                  jump to the beginning or end of the line, or delete,
                  insert, or type over characters anywhere on the line.

                * 4DOS, 4NT, and Take Command keep 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 . or
                  in a pop-up window if you press PgUp.  In Take Command,
                  use Ctrl-. and Ctrl- PgUp.

                * If you don't know or 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 Tab:  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 file or directory name and press
                  Tab.  The command interpreter fills in the rest,
                  including any quotation marks required for long
                  filenames.

                * 4DOS, 4NT, and Take Command remember each directory you
                  have visited.  There are many ways to return to previous


        14                                      (c) 2003 JP Software Inc. 





                  directories; the easiest is to press Ctrl-PgUp in 4DOS
                  and 4NT (F6 in Take Command,) 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.

                * Our programs also use an 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.

                * Our programs include features that let you select files
                  by size, date, and time.  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 to delete all .BAK files that are greater than 1 MB in
                  size:

                     [c:\] del /[s1M] *.bak

                  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

                * 4DOS, 4NT, and Take Command let you associate file
                  extensions with applications.  For example, it's easy to
                  start your word processor and load a letter when 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 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.  For example, to copy all of your .TXT files to
                  drive A: and then display the directory of drive A:


        4DOS, 4NT, Take Command Introduction and Installation Guide               15 





      4DOS

                       c:\> copy *.txt a: ^ dir a:

      4NT, TC

                       [c:\] copy *.txt a: & dir a:

        The Take Command Window

             The Take Command window is similar to other applications that
             run on the Windows desktop.  The title bar at the top is
             similar to the one used in most Windows applications, with a
             system menu button on the left, and maximize, minimize, and
             close buttons at the right.  You can move the window and
             adjust its size with a mouse or the keyboard, and you can
             change the title and the window's size or position with the
             WINDOW command.









                           [  placeholder: graphic ]









             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.  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).


        16                                      (c) 2003 JP Software Inc. 





             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 online help and in
             the Reference Manual.

        Working with Windows

             Take Command works with Windows in several ways to make your
             computing more productive, including:

                * You can use the Windows clipboard to copy text onto the
                  command line, or to transfer text from Take Command to
                  another application.

                * You can use the Windows Drag and Drop feature to insert
                  file names from other applications onto the command line.

                * You can use Take Command to send messages to other
                  Windows applications using Dynamic Data Exchange (DDE),
                  or use DDE to send commands to Take Command from other
                  applications.

        Accessing Networks and Remote Systems

             All of our products can work with accessible files on your
             LAN, whether through mapped drive letters, or standard network
             names like \\SERVER\VOL\filename.

             In addition, built-in features of 4NT and Take Command let you
             access FTP servers.  You can use standard commands like DEL,
             DIR, COPY, MOVE, and REN to manage files on FTP servers.  Many
             other features also support FTP access, and the IFTP command
             lets you create a persistent FTP connection for use with
             subsequent commands.  Some commands (COPY and MOVE) can also
             manipulate files on HTTP servers.




        4DOS, 4NT, Take Command Introduction and Installation Guide               17 





        Configuration

             We don't know how you use your computer, or how you would like
             it to work, so we have made our programs as flexible as
             possible.  You can configure almost every part of our programs
             to suit your needs or your whims.  To start the configuration
             utility, 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 like the size and location of
             pop-up windows, or the shape of the cursor.

        4DOS

                  If conventional memory is tight on your DOS computer, you
             can configure 4DOS to squeeze out every possible byte, using
             extended (XMS) memory, expanded (EMS) memory, upper memory
             blocks (UMBs), or conventional memory.  4DOS can use just 256
             bytes of conventional memory, leaving as much room free as
             possible for memory-hungry DOS application programs, memory-
             resident utilities, and games.

        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 that are stored in
             memory for very fast execution.  They 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 your 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



        18                                      (c) 2003 JP Software Inc. 





             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 editor, even if its directory is
             not on the PATH:

                [c:\] alias edit e:\edfiles\editor.exe

             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).
             This alias should be entered on a single line:

        4DOS

                  c:\> alias monthly `pushd c:\monthly ^ finproc ^ popd`

        4NT, TC

                  [c:\] alias monthly `pushd c:\monthly & finproc & popd`

             This short description explains only the basics of what
             aliases can do.  Like most 4DOS, 4NT, and 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
             the command interpreter starts (otherwise, you'd have to
             redefine them each time); assign aliases to keystrokes so they
             can be invoked quickly; write aliases which use other aliases;
             and use aliases within batch files.  For complete information
             on aliases, see the online help, the reference manual, and the
             ALIAS command in Chapter 7 of the reference manual.

             Batch Files

             A batch file or batch program is a text file that contains a
             list of commands to execute.  4DOS, 4NT, and Take Command read
             and interpret 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 more powerful than our built-in batch
             language.




        4DOS, 4NT, Take Command Introduction and Installation Guide               19 





             The batch language includes simple commands to display menus,
             boxes, lines, and colored text to dress up your batch file
             displays; a full range of user input commands; over 80 built-
             in variables that let your batch files test system
             configuration, device status, and free memory and disk space;
             and more than 120 built-in functions that let your batch files
             read from files, find the date, perform calculations, and
             manipulate strings.

             Our batch files 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.

             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
             4DOS, 4NT, and Take Command:

                cls
                echo System status as of %_date at %_time:
                echo CPU:  %_cpu
                echo Screen size:  %_rows x %_columns
                echo Boot drive:  %_boot
                echo OS version:  %_dosver
                echo Command processor version:  %_4ver
                echo Country code:  %_country

             The next example clears the screen, displays a short menu,
             accepts some input from the user, and displays the result.
             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      3 - Load the network
                       2 - Spreadsheet
                endtext
                screen +1 0
                inkey Enter your selection: %%sel
                screen +2 0
                echo You entered: %sel

      4NT, TC


        20                                      (c) 2003 JP Software Inc. 





                  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 user name %%name
                querybox /L6 /P "Password" Enter password %%pword
















































        4DOS, 4NT, Take Command Introduction and Installation Guide               21 


        Chapter 2 / Installation



        Chapter 2 / Installation

        4DOS, 4NT, and Take Command normally come with Windows-based
        installation software that makes product installation simple and
        straightforward.  If you are installing our products under Windows
        95/98/ME or Windows NT/2000, we recommend that you follow the
        directions for automated installation below.

        If you are running in a non-Windows environment, or prefer to set
        up the program yourself, you can extract the installation files and
        perform all installation steps manually.  Manual file extraction
        and installation is covered in detail for each product in Chapters
        4 - 7.

        Preparing for Installation

             You can install and use each of our products under recent
             versions of DOS or Windows.  If you are using an older
             version, or you want to use a product under a different
             operating system than the one for which it is sold, consult
             Chapters 4 - 7 (depending on the product) for details on
             compatibility before proceeding with installation.

             We strongly recommend that you install your new version of
             4DOS, 4NT, or Take Command in a new directory or folder, not
             in the same directory as a previous version, or a directory
             used by other software.

        4DOS

                  When installing 4DOS under Windows 95/98, we also
             strongly recommend that you use a short name for the 4DOS
             directory (i.e. a name where each element of the path uses no
             more than eight characters for the name and three characters
             for the extension, with no white space or other special
             characters).  If you install 4DOS in a directory with a long
             name, you will have to determine the equivalent short name and
             use it throughout the installation process.

        Performing the Installation

             Our products are distributed using several methods.  This
             section explains how to start the automated installation
             software in each case.  In all cases, see Chapters 4 - 7 if
             you want a manual rather than automated install.




        22                                      (c) 2003 JP Software Inc. 


                                                       Chapter 2 / Installation


             To start the installation software you can use a command
             prompt, the Run option on the Windows Start menu, or from
             Windows Explorer.

                * If your copy of 4DOS, 4NT, or Take Command was downloaded
                  as an .EXE file from our web or FTP site, or as part of
                  an electronic purchase, store the file in a directory of
                  your choosing, and execute it to start the installation
                  process.  The file name will be based on the product and
                  version (e.g. 4NT500.EXE for 4NT 5.00).

                * If your copy came on a CD-ROM from JP Software, simply
                  run the installation software from the directory for the
                  desired product.  The program name will be SETUP.EXE.
                  For example, to install 4NT you would run
                  D:\4NT\SETUP.EXE, where "D:" is the drive letter used for
                  your CD-ROM.

                * If your copy came in a downloaded .ZIP file from our web
                  site or FTP site, then there is no SETUP.EXE.  In this
                  case, you must use the manual installation instructions
                  in chapters 4 -
                                - 7.

             Installing an Upgrade

             Use the 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
             4DOS.INI, 4NT.INI, TCMD.INI and / or 4START, 4EXIT, TCSTART,
             or TCEXIT files 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 later (see
             Chapters 4 - 7 for details).

             Desktop, Registry, and System File Changes

             During automated installation for any product some changes are
             made to the Windows desktop and registry.  These changes:

                * Create a JP Software program group on the Start Menu, and
                  include shortcuts in that group to start the command
                  processor and its online help.




        4DOS, 4NT, Take Command Introduction and Installation Guide               23 


        Chapter 2 / Installation


                * Optionally add a shortcut to the Windows desktop to start
                  the command processor.

                * Designate the .BTM files (enhanced batch files) used by
                  JP Software products as batch files.  They will then be
                  recognized as such by Windows Explorer.

                * Provide an additional "open" option in the context (right
                  mouse button) menu of all batch files, to run the file
                  with 4DOS, 4NT, or Take Command.

                * Create a new entry in the context menu of drives and
                  directories to launch 4DOS, 4NT or Take Command in that
                  drive / directory.

             If you need to make these changes manually, or reinstall them
             without reinstalling the software, see the support area of our
             web site for a set of registry extension (.INF) files you can
             download and install.  These files create shortcuts and
             registry changes similar to those made by the installation
             software.

             Automated installation for 4DOS may also modify CONFIG.SYS to
             make 4DOS the primary shell.  See chapter 5 for details on
             performing or reversing this step manually if necessary.

             All of these changes are reversed by the automated uninstall
             process.

        Extracting or Repairing Product Files

             If you need to recover or reinstall individual 4DOS, 4NT, or
             Take Command files you can do so manually, or using the
             automated installation software.  The methods described here
             can also be used to extract the files you need to perform a
             manual installation for any product.

             The method you use depends on what files you have:

                * If you have a downloaded .EXE file, execute the file with
                  a /X switch, for example:

                     c:\download\4nt500.exe /x

                  /X disables the normal automated installation and allows
                  you to select which files you want to extract.  You can
                  also extract files from the .EXE file with an unzip
                  program; see below for details.



        24                                      (c) 2003 JP Software Inc. 


                                                       Chapter 2 / Installation


                * If you have a CD-ROM from JP Software, in most cases you
                  can copy the desired files from the appropriate
                  directory, as the files are stored individually on the CD
                  and are accessible as normal files.  If you prefer to use
                  the installation software, or cannot find the files you
                  want, run SETUP.EXE from the directory for the desired
                  product, with the /X switch as explained above.

                * If you have a downloaded .ZIP file from our web site or
                  FTP site, then simply extract the files you want using an
                  unzip program.

             Because the .EXE files used for automated installation are
             created in .ZIP format, you can also use an unzip program like
             PKZIP or WinZip to view and/or unzip a downloaded .EXE file,
             or SETUP.EXE from a JP Software CD-ROM.  This allows you to
             extract the files even if you are not running under Windows
             and cannot use SETUP.EXE.  Note that when viewed in .ZIP
             format the installation .EXE file also contains a number of
             auxiliary files used during the automated installation
             process.  You should avoid extracting these files as they
             perform no useful purpose on their own, and will only clutter
             up the product directory.

        Uninstalling the Program

             We don't expect you to have trouble using our programs, but we
             know many users like to know how to uninstall a product.  Or
             you may need to remove the program from one system to move it
             to another system.

             If you installed your product using SETUP.EXE, go to the
             Windows Control Panel, select Add/Remove Programs, and select
             the product you want to uninstall from there.  You can also
             start the automated uninstall process by manually executing
             the UNWISE.EXE program in the product directory, but in most
             cases this should not be necessary.

             Once the uninstall starts you can select Automatic or Custom.
             The Automatic option is the simplest and fastest, but if you
             want to control each step of the uninstall process select
             Custom.

             Note that the automated uninstall software normally removes
             the registry changes which designate JP Software .BTM files as
             batch files.  These registry changes affect all JP Software
             products (see page 23 for details).  If you are using multiple
             products and only uninstalling one of them, you may not want


        4DOS, 4NT, Take Command Introduction and Installation Guide               25 


        Chapter 2 / Installation


             to remove these registry changes.  In this case, use the
             Custom Uninstall option, and when prompted for the registry
             changes to reverse, select all changes except those made to
             the Software\Classes registry keys.

             The automated uninstall software will attempt to reverse all
             of the changes made during installation, including
             modifications to your system files and registry.  However, in
             some instances (for example, if you manually moved the product
             files to a new directory after automated installation was
             complete), the program may not be able to complete all of the
             steps automatically.  In this case, you will need to perform
             some of them manually.

             You will also need to uninstall the program manually if you
             did not use SETUP.EXE install it, or if UNWISE.EXE has been
             deleted.

             See Chapters 5 - 7 for manual uninstall instructions for each
             product.


































        26                                      (c) 2003 JP Software Inc. 


                                                     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.

        Using the Help System

             If 4DOS, 4NT, or Take Command is running, you can start the
             help system by typing HELP (or HELP plus a command name) at
             the prompt, by pressing the F1 key at any time when the
             command processor is accepting keyboard input at the prompt,
             or from the Help menu in Take Command.  Each of our help
             systems 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 need help for a command or variable that is not at the
             beginning of the line, position the cursor under (or
             immediately to the right) of the word, and press Ctrl-F1.

             If you type the name of any internal command at the prompt,
             followed by a slash and a question mark [/?] like this

                [c:\] copy /?

             you will see help for the command in a quick-reference style.

             Once you've started the help system, you can use a standard
             set of keystrokes or mouse actions to navigate through the
             help text.

             Each help system can also be started "manually" (i.e., without
             4DOS, 4NT, or Take Command running), and contains information
             which may be helpful if you encounter difficulties setting up



        4DOS, 4NT, Take Command Introduction and Installation Guide               27 


        Chapter 3 / The Help System


             the program or configuring it for your system.  See Chapters
             4 - 7 for details on starting the help system manually.

        Important Help Topics

             The help system includes documentation for all 4DOS, 4NT, or
             Take Command commands and features.  It also includes many
             other topics that may be of interest to you as you use the
             program or which you may need for advanced installations:

                * 4DOS.INI, 4NT.INI, or Configuring Take Command cover the
                  .INI file and the related dialogs, including reference
                  information on all .INI file directives.

                * Starting Take Command, Starting 4DOS, or Starting 4NT
                  (under Setup and Troubleshooting) explains the startup
                  command line, and contain links to related startup and
                  configuration topics such as 4START and TCSTART.

                * 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 matters.

                * Reference Tables (under Reference Information) includes
                  comprehensive lists of ASCII characters and keyboard
                  codes.

                * Compatibility discusses using 4DOS with products from
                  other companies, including additional details on using
                  4DOS with Windows 95/98/ME.

                * External (DOS) Help provides access to the MS-DOS / PC
                  DOS help system.  This feature will only work if the 4DOS
                  help program can find the DOS help program on your disk
                  (see the External Help topic for details), and if the
                  4DOS help program has enough memory to execute DOS help.












        28                                      (c) 2003 JP Software Inc. 


                                                 Chapter 4 / 4DOS and 4NT Startup



        Chapter 4 / 4DOS and 4NT Startup

        This chapter explains startup options for 4DOS and 4NT under
        various operating systems.  For additional details on manual
        installation and configuration of 4DOS see chapter 5 on page 38;
        for 4NT see chapter 6 on page 53.  For information on Take Command,
        see chapter 7 on page 61.

        Once you have 4DOS or 4NT installed on your computer, the program
        is ready to run.  However, you can configure each program in
        various ways to suit your needs and preferences.  Most of the
        configuration or behavior of each program is controlled by aliases
        you create (explained in the online help and in Chapter 4 of the
        Reference Manual) and by the .INI file (explained briefly below,
        and in detail in the online help and in Chapter 5 of the Reference
        Manual).

        A few configuration options can also be set on the startup command
        line, which is explained here.  In order to understand the startup
        command line you will also need to understand primary and secondary
        shells, so that topic is covered first.

        If you do not need to alter the startup behavior of 4DOS or 4NT,
        you can skip the remainder of this chapter.  If you are using our
        products under any flavor of Windows, we recommend that you read
        this chapter, since each time you create a desktop object to run
        the command interpreter you will have to create a startup command
        line for that object.

        Primary and Secondary Shells

             4DOS and 4NT can be run as either primary or secondary shells.

             Under DOS and Windows 95/98, a primary shell is started from
             the CONFIG.SYS file with a SHELL= command.  Secondary shells
             are started when a program "shells" to the DOS prompt or runs
             a "transient" (temporary) shell to execute a specific command,
             or when you explicitly start a new shell from a desktop object
             under Windows 95/98.

             Under Windows NT/2000/XP, a primary shell is started each time
             you start a new command-line session or window from the
             desktop.  A secondary shell is started when a program "shells"
             to the command prompt, or runs a "transient" (temporary) shell
             to execute a specific command.




        4DOS, 4NT, Take Command Introduction and Installation Guide               29 


        Chapter 4 / 4DOS and 4NT Startup


             Whenever you start a primary or secondary shell, you can
             control the way that 4DOS or 4NT starts by adjusting the
             startup command line.

        Command Line Options

             A few of the command-line switches or options that 4DOS and
             4NT recognize are required in certain circumstances; most
             others are needed only if you want finer control over the way
             the program starts.

             The command line that starts 4DOS or 4NT will typically
             include the program name with drive and path, repeat the name
             of the directory where the program is stored, and finally
             include any switches for the program, for example:

                  e:\4dos\4dos.com e:\4dos /p

             This command line may appear on its own (for example, in a
             Windows desktop object), or in an operating system directive
             (e.g. the SHELL command in the DOS or Windows 95/98 CONFIG.SYS
             file).  Specific details on where you should enter the command
             line for each product are included in Chapters 5 and 6.

             Although the startup command line is usually very simple, you
             can add a number of options if you need to customize the way
             the command interpreter starts.  The complete syntax for the
             4DOS startup command line is:

                d:\path\program [d:\path] [@d:\path\inifile] [//iniline]
                [/D /E:nnnn /F /L /LA /LD /LF /LH /P[:filename] /Y] [[/C |
                /K] command]

             The complete syntax for the 4NT startup command line is:

                d:\path\program [d:\path] [@d:\path\inifile] [//iniline]
                [/L /LA /LD /LF /LH /Q /S /T:bf /U /X ] [[/C | /K] command]

             Do not include the square brackets shown in the command line.
             They are there to indicate that the items within the brackets
             are optional.

             If you include any of the options below, you should use them
             in the order that they are described.  If you do not do so,
             you may find that they do not operate properly.

             The following items can be included on the command line:




        30                                      (c) 2003 JP Software Inc. 


                                                 Chapter 4 / 4DOS and 4NT Startup


                  * d:\path\program:  The path and name of the executable
                     program file (4DOS.COM or 4NT.EXE).  It is required to
                     start 4DOS or 4NT.

                  * 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.  4DOS and
                     4NT use this path to find their files and to set the
                     COMSPEC environment variable (see your online help or
                     Reference Manual for more information on COMSPEC).

        4DOS

                    Under 4DOS, this option is generally required for the
                     primary shell, but not for secondary shells.  In some
                     cases, the primary 4DOS shell can find its directory
                     automatically and this option is not needed, but we
                     recommend that you use it on all primary shells to
                     ensure that the directory is found.

                    If you are running Windows 95/98 and you do not load
                     4DOS as the primary shell in CONFIG.SYS, or if you are
                     running Windows ME, you must use this option in each
                     desktop object or shortcut command line to allow 4DOS
                     to find its files.

        4NT

                    4NT knows its startup drive and directory, so this
                     option is not usually necessary, though it is allowed.

                  * @d:\path\inifile:  This option sets the path and name
                     of the .INI file.  You don't need this option if you
                     aren't using an .INI file at all, or if the file has
                     the default name (4DOS.INI or 4NT.INI), and it is
                     either in the same directory as the executable program
                     or in the root directory of the boot drive.  This
                     option is most useful if you want to start the program
                     with a specific and unique .INI file.

                  * //iniline:  This option tells 4DOS or 4NT 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



        4DOS, 4NT, Take Command Introduction and Installation Guide               31 


        Chapter 4 / 4DOS and 4NT Startup


                     the startup line without having to modify or create a
                     new .INI file.

        4DOS

                    * /D:  In 4DOS only, this option disables execution of
                     AUTOEXEC.BAT (or the file named in the AutoExecPath
                     directive in 4DOS.INI).  It is intended for internal
                     use by DOS and Windows 95/98.  When you press the F8
                     or Ctrl key during the boot process, MS-DOS prompts
                     whether to run AUTOEXEC.BAT.  If you answer "No", the
                     /D switch is used to relay your choice to 4DOS.  This
                     option is not available in 4NT.

        4DOS

                    * /E:nnnn:  In 4DOS only, this option sets the size of
                     the environment in bytes.  If you don't use this option,
                     4DOS will allocate 512 bytes for the environment.  You
                     can use any value from 160 to 32767 as the environment
                     size.  For example, to set an environment of 1,000
                     bytes, you would enter the option as /E:1000.

                     You can also set the environment size with the
                     Environment directive in the 4DOS.INI file (see your
                     online help or Reference Manual).  We recommend that
                     you use the directive instead of the /E switch, so
                     that all configuration information is kept in one
                     place in the 4DOS.INI file.

        4NT

                     4NT allocates space in the environment dynamically
                     instead of using a fixed amount of space.  Therefore,
                     this option is not available in 4NT.

        4DOS

                    * /F:  This option tells 4DOS to automatically provide
                     a Fail response to all critical errors, without
                     prompting or waiting for a user response.  It is
                     rarely used except on systems that must run
                     unattended.  We do not recommend use of this option on
                     a normal system, because you will not have a chance to
                     react to a critical error and correct the problem that


        32                                      (c) 2003 JP Software Inc. 


                                                 Chapter 4 / 4DOS and 4NT Startup


                     caused it.  For more information on critical errors,
                     see the online help or the Reference Manual.  /F only
                     affects critical errors detected by 4DOS, and will not
                     affect critical error handling for many application
                     programs which perform this function themselves.  It
                     is equivalent to the directive CritFail=Yes in
                     4DOS.INI.

                    The /F option is not available in 4NT.

                  * /L, /LA, /LD, /LF, and /LH:  These options force 4DOS
                     or 4NT to use a local alias, directory history,
                     function, and / or command history list.  They can be
                     used to override any LocalAlias=No, LocalFunctions=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, functions, or histories.  See your
                     online help or Reference Manual for details on local
                     and global aliases and histories.  /LA forces local
                     aliases, /LD forces local directory history, /LF
                     forces local functions, /LH forces local command
                     history, and /L forces all four.

        4DOS

                  * /P[:filename]:  This option tells 4DOS to load permanently
                     and to run AUTOEXEC.BAT.  If you specify a filename
                     after the /P, that file will be run instead of
                     AUTOEXEC.BAT.  You should specify the full name of the
                     file, including drive and directory.  A filename after
                     /P will override the AutoExecPath option in 4DOS.INI.

                    When 4DOS is loaded from the SHELL= command in
                     CONFIG.SYS it will normally detect that it is the
                     primary shell and set /P  automatically.  Under rare
                     circumstances, you may want to load 4DOS permanently
                     and have it run AUTOEXEC.BAT even though it is not
                     loading it from CONFIG.SYS; in such cases you must set
                     /P yourself.  4DOS will not run AUTOEXEC.BAT without
                     either an automatic or an explicit /P.  Do not use
                     this option in secondary shells, or you will be unable
                     to return to the primary shell.

                    The /P option is not available in 4NT.


        4DOS, 4NT, Take Command Introduction and Installation Guide               33 


        Chapter 4 / 4DOS and 4NT Startup


        4NT

                    * /Q:  This option, which is only available in 4NT,
                     has no effect.  It is included only for compatibility
                     with CMD.EXE.

        4NT

                    * /S:  This option tells 4NT that you do not want it
                     to set up a Ctrl-C / Ctrl-Break handler.  It is
                     included for compatibility with CMD.EXE, but it may
                     cause the system to operate incorrectly if you use
                     this option without other software to handle Ctrl-C
                     and Ctrl-Break.  This option should be avoided by most
                     users.  It is not available under 4DOS.

        4NT

                    * /T:bf:  This option sets the foreground and background
                     colors in the 4NT window.  Both b and f are
                     hexadecimal digits; b specifies the background color
                     and f specifies the foreground color.  This option is
                     included for compatibility with CMD.EXE; in most
                     cases, you will find it easier to set default colors
                     with the StdColors directive in 4NT.INI, or the
                     corresponding Output Colors option on the Display page
                     of the 4NT configuration dialogs.

        4NT

                    * /U:  This option causes the output of internal
                     commands to a pipe or redirected to a file to be in
                     Unicode.  (Unicode versions of 4NT only.)

        4NT

                    * /X:

                      This option forces 4NT to alter the operation of the
                     MD and MKDIR command to automatically create all
                     necessary intermediate directories when it creates a
                     new subdirectory.  Its effect is the same as adding a
                     /S option to all MD and MKDIR commands (see the online
                     help or Reference Manual for details about the MD /S
                     command).  This option is included for compatibility
                     with CMD.EXE.  In CMD.EXE it enables other options as



        34                                      (c) 2003 JP Software Inc. 


                                                 Chapter 4 / 4DOS and 4NT Startup


                     well, but in 4NT the only option not enabled by
                     default is the implicit MD /S.

        4NT

                    * /Y:  This option forces 4DOS to enable the batch
                     file debugger for 4START and AUTOEXEC.BAT (or the file
                     named in the AutoExecPath directive in 4DOS.INI).  It
                     is intended for internal use by DOS and Windows 95/98.
                     When you press the F8 key to enable single-stepping
                     during the boot process and then elect to single-step
                     through AUTOEXEC.BAT, the /Y switch is used to relay
                     your choice to 4DOS.  This option is not available in
                     4NT.

        4NT

                    * [/C | /K] command:  This option tells 4DOS or 4NT to
                     run a specific command after starting.  The command
                     will be run after 4START and AUTOEXEC.BAT in a 4DOS
                     primary shell.  The command will be run 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 the command interpreter will treat
                     characters after the command as part of the command
                     and not as additional startup options.

                    When the command is preceded by a /C, 4DOS or 4NT will
                     execute the command and then exit and return to the
                     parent program or the desktop without displaying a
                     prompt.  This is sometimes called a "transient"
                     command interpreter session.

                    In 4NT, and in 4DOS when it is started as a secondary
                     shell (for example from the Windows desktop), the /K
                     switch has no effect; using it is the same as placing
                     the command (without a /C or /K) at the end of the
                     startup command line.  It is included only for
                     compatibility with COMMAND.COM and CMD.EXE.

        4DOS

                    When you start 4DOS from the SHELL= line in MS-DOS /
                     PC-DOS 6.x and use /K, the command will be executed
                     instead of AUTOEXEC.BAT (for compatibility with MS-DOS
                     / PC-DOS 6.x COMMAND.COM).  This behavior occurs only
                     in MS-DOS / PC-DOS 6.x, not in other DOS versions or
                     in Windows 95/98.


        4DOS, 4NT, Take Command Introduction and Installation Guide               35 


        Chapter 4 / 4DOS and 4NT Startup


             For example, this command line will start 4DOS, execute any
             4START file you have created, execute the file START.BTM, and
             then display the prompt:

                c:\4dos\4dos.exe c:\4dos\start.btm

             This command line will start 4NT, select local aliases,
             execute any 4START 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:\4nt\4nt.exe /la /c c:\4nt\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 (named 4DOS.INI or 4NT.INI), and a startup batch file
             called 4START (depending on your operating system, 4START may
             have the extension .BTM, .BAT, or .CMD).

             The .INI file is optional in 4NT and required in 4DOS (see
             page 42 for details).  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, or you can use
             the OPTION command to aid you in selecting configuration
             options.

             The 4START file is also optional.  It is executed each time
             4DOS or 4NT starts, and gives you a convenient way to load
             aliases and environment variables, and otherwise initialize
             the command processor -- especially under 4NT, which does not
             use an AUTOEXEC.BAT file.  4START is normally placed in the
             same directory as the other product files, but this may vary
             if you use the same 4START file for more than one product.

             For complete details on startup files, on the OPTION command,
             and on the 4EXIT file (executed when the command processor
             exits), see the online help or the Reference Manual.

             If you are upgrading from a previous version of 4DOS or 4NT,
             you may have an .INI file and / or a 4START (or 4EXIT) file in
             the previous version's directory.  To use these files with
             your new version, you must copy them to the new directory, and
             then update any paths in either file that point to the old
             program directory.



        36                                      (c) 2003 JP Software Inc. 


                                                 Chapter 4 / 4DOS and 4NT Startup


        Exit Codes

             If you start 4DOS or 4NT from another program (e.g. to run a
             batch file or internal command), it will return a numeric code
             to the other program when it is finished.  This code is
             usually used to indicate whether the operation performed was
             successful or not, with 0 often indicating success and a non-
             zero value indicating a failure or other numeric result.

        4DOS

                  In 4DOS, the exit code is normally the numeric exit code
             from the last external command.  Internal commands do not set
             the exit code.

        4NT

                  In 4NT, the exit code is normally the numeric exit code
             from the last internal or external command.  However, for
             compatibility reasons and to avoid conflicts with external
             commands, only some internal commands set the exit code;
             others leave it unchanged from the most recent external
             command.

             If you enter an unknown command the exit code will be 2, which
             is the internal 4DOS and 4NT "unknown command" error number.

             In both 4DOS and 4NT, you can use the EXIT n command to
             explicitly set the exit code.  If you do, this will override
             the rules described above, and set the return code to the
             value in your EXIT command.

             The normal rules described above may not return a code that
             indicates the success or failure of the specific operation
             that concerns you.  Therefore, if you need to rely on the exit
             code from 4DOS or 4NT, we recommend that you use a batch file
             or alias to create the exit code you want, and then set the
             code explicitly with EXIT n.














        4DOS, 4NT, Take Command Introduction and Installation Guide               37 


        Chapter 5 / 4DOS Configuration and Notes



        Chapter 5 / 4DOS Configuration and Notes

        This chapter covers manual installation and configuration of 4DOS.
        For information on startup options for 4DOS and 4NT under various
        operating systems see chapter 4 on page 29.   For 4NT configuration
        see chapter 6 on page 53.  For information on Take Command, see
        chapter 7 on page 61.

        4DOS works well with virtually all PC hardware; with a wide range
        of operating systems and environments, including MS DOS, PC-DOS,
        Novell DOS / OpenDOS / DR-DOS, Windows 3.x, Windows 95 / 98 / ME,
        and OS/2; and with all DOS-based, Windows-based, and OS/2-based
        networks.  Each environment makes different demands on 4DOS and the
        user.

        4DOS is not recommended or supported for use under Windows NT,
        Windows 2000, or Windows XP.  If you are running Windows
        NT/2000/XP, use 4NT or Take Command.

        This chapter provides the basic information you need to run 4DOS in
        any of the standard PC environments.  If you need detailed
        technical information or troubleshooting assistance on any of these
        topics, consult the Troubleshooting, Service, and Support and
        Compatibility topics in the 4DOS online help.

        4DOS Installation Notes

             When installing 4DOS under Windows 95/98/ME, we strongly
             recommend that you use a short name for the 4DOS directory
             (i.e. a name where each element of the path uses no more than
             eight characters for the name and three characters for the
             extension, with no white space or other special characters).
             If you install 4DOS in a directory with a long name, you will
             have to determine the equivalent short name and use it
             throughout the installation process.

             Older Versions of DOS

             If you're running DOS 5 or earlier, we recommend you make a
             bootable system diskette before you install 4DOS (or any other
             software, for that matter).  This allows you to recover in
             case of a power failure, error, or other interruption during
             the installation process.  See your DOS documentation for
             details about creating a bootable floppy disk.

             In DOS 6 and above and in Windows 95/98/ME, a bootable disk
             usually is not necessary because the F5 and F8 keys can be

        38                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


             used to skip steps in the boot process and recover from errors
             in configuration files.

        Manual Installation of 4DOS

             This section is for advanced users, and assumes you are
             generally familiar with CONFIG.SYS, AUTOEXEC.BAT, and other
             concepts such as ASCII editors and batch files.  In most
             cases, manual installation is not necessary because you can
             use the automated installation program.

             In order to install 4DOS manually, you must extract or copy
             the necessary files, brand 4DOS if necessary, create or modify
             any configuration files you need, and then create the
             necessary commands to start the program on your system.

             Extracting or Copying the Program Files

             When you extract or copy the 4DOS 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 4DOS files in
             the same directory.  See 4DOS Files and Directories on page 43
             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.  The various methods
             are described on page 24.

             "Branding" 4DOS

             If you received your copy of 4DOS on a JP Software CD-ROM, it
             will have a label with your 4DOS serial number and validation
             code.  If your CD was purchased directly from JP Software, the
             label will also include your registered name (company or
             individual).

             If your copy was purchased electronically, the registered
             name, serial number, and validation code are included in the
             email you received as part of the purchase transaction.

             The serial number and validation code constitute your license,
             and are provided only with purchased copies.



        4DOS, 4NT, Take Command Introduction and Installation Guide               39 


        Chapter 5 / 4DOS Configuration and Notes


             A program called BR4DOS.EXE product checks your registered
             name, serial number, and validation code, and saves them for
             use by 4DOS.  This process, which we call "branding,"
             personalizes your copy and removes the "trial copy" or other
             similar message that is displayed otherwise.

             If you performed an automated installation, the installation
             software will normally run the BR4DOS program to install your
             name, serial number, and validation code in 4DOS.  If you need
             to brand 4DOS manually, go to a 4DOS or COMMAND.COM prompt,
             change to the directory where 4DOS is stored, and enter the
             command:

                c:\4dos> br4dos

             Follow the instructions displayed by BR4DOS 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.

             The way that you obtain and run BR4DOS depends on how you
             obtained your software:

                * If you purchased 4DOS electronically, either as a new
                  copy or as a major upgrade, and received the branding
                  information via email, the brand program(s) you need will
                  come to you attached to the email message.  Download a
                  trial version of the product from our web site and
                  install it, if you have not done so already.  Then copy
                  the brand program to the directory where the product was
                  installed, and run it from the prompt in that directory,
                  for example:

                     [c:\4dos] br4dos.exe

                * If you purchased 4DOS on a CD-ROM from JP Software, the
                  branding program will be installed and run automatically
                  during installation.

                * If you downloaded a trial copy of 4DOS as a minor upgrade
                  from our web site or FTP site, you will need to copy
                  BR4DOS.EXE from the directory where you installed the
                  previous version.  If the trial copy you downloaded is an
                  .EXE file with automated installation software it will
                  copy the brand program for you if it can find the
                  previous installation.  Otherwise, you will have to copy
                  the program to the new directory manually.



        40                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


             As you follow the instructions from BR4DOS.EXE to enter your
             name, serial number, and validation code, be sure that all
             information is entered exactly as shown in the branding
             information you received.  You cannot change spelling,
             capitalization, or punctuation.

             You may also need to run BR4DOS.EXE when you download a
             maintenance upgrade to 4DOS.  Branding a downloaded copy
             converts it from a timed trial copy to one fully registered to
             you.  You should save your brand document or electronically
             delivered branding information, in case it is needed for an
             upgrade.

              You can rerun BR4DOS.EXE manually at any time to reinstall
             your name and serial number.  To do so simply start the
             corresponding product, change to the product directory, and
             run the program, for example:

                [c:\4dos] br4dos.exe

             Updating CONFIG.SYS and AUTOEXEC.BAT

             (Please Note:  If you installed 4DOS to a directory with a
             long name under Windows 95/98, you must determine the
             equivalent short name for use when updating CONFIG.SYS and
             AUTOEXEC.BAT.  Paths in these files cannot be entered in long
             name format.)

             When you're ready to finish installing 4DOS, you need to add
             one line to your CONFIG.SYS file:

                SHELL=d:\path\4DOS.COM d:\path /P

             "d:\path" means the drive and directory where 4DOS.COM is
             stored.  The second "d:\path" on the SHELL= line should be the
             same as the first, and is used to set the COMSPEC environment
             variable properly.  Be sure to delete or REM out any old
             SHELL= line when you add the new line for 4DOS.

             You can add any command line options to the end of the line.
             See Chapter 4 on page 29 for information on command line
             options.

             If you are running 4DOS under DOS 4.01 or earlier, see the
             Compatibility section in the online help for notes on the
             length of the SHELL= line.

             Next, if you are running under DOS (without Windows 95/98/ME),
             add the following line to your AUTOEXEC.BAT file:

        4DOS, 4NT, Take Command Introduction and Installation Guide               41 


        Chapter 5 / 4DOS Configuration and Notes


                d:\path\KSTACK.COM

             where "d:\path" is the drive and directory where your 4DOS
             files are stored.  KSTACK.COM is a memory-resident program
             used to support the KEYSTACK command.  It requires about 1K of
             memory, and can be left out if you do not use KEYSTACK.

             Do not add the KSTACK line to AUTOEXEC.BAT if you are using
             Windows 95/98.  Under these operating systems, KSTACK should
             be loaded separately for each 4DOS session; see page 48 for
             details.

             If you have a line in AUTOEXEC.BAT which sets the COMSPEC
             environment variable to point to COMMAND.COM, remove it or REM
             it out.  If you set up the CONFIG.SYS file properly, 4DOS will
             set this variable automatically; setting it in AUTOEXEC.BAT is
             likely to cause trouble later on (for example, if you install
             an update to 4DOS in a different directory, but forget to
             change the COMSPEC setting).

             When you've finished modifying CONFIG.SYS and AUTOEXEC.BAT,
             you can reboot your system to start 4DOS.

             Creating or Copying 4DOS.INI

             (For general information on the .INI file see page 36.)

             4DOS requires a 4DOS.INI file with at least one line in it:

                InstallPath = d:\path

             where "d:\path" is the drive and directory where your 4DOS
             files are stored (under Windows 95/98, this must be the short
             name of the directory; long names cannot be used).  This will
             help 4DOS locate its auxiliary files, such as the help files
             and OPTION.EXE.  The automated installation process always
             places this line in 4DOS.INI.  If you need to create the file
             manually, you can do so with any ASCII file editor.  The
             InstallPath setting should be the first line in the file.

             If you are upgrading from a previous version of 4DOS, you
             should copy any 4DOS.INI file you have in the old directory to
             the new one.  Then add or modify the InstallPath directive at
             the beginning of 4DOS.INI, and update any paths in the file
             that point to the old program directory (e.g. 4StartPath).






        42                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


             4DOS Files and Directories

             We strongly recommend that you place all 4DOS files in the
             same directory.  If you do not do so, you will have to
             explicitly set the locations of 4DOS files to avoid problems.

             You may feel that you should place 4DOS.COM in the root
             directory because it is a system-related file.  We do not
             recommend this practice; 4DOS will run just fine from its own
             directory, and keeping it there makes configuration much
             simpler.

             If you do wish to move files to different directories, the
             following information will help you set up the programs
             correctly:

                4DOS.COM is the 4DOS program file.  It must be in the
                directory specified by the SHELL= line in your DOS or
                Windows 95/98 CONFIG.SYS file, or the directory specified
                on the command line in every desktop object used to start
                4DOS.

                4HELP.EXE is the 4DOS help program.  For online help to
                work, this file must be in the 4DOS installation directory
                shown in the InstallPath directive in 4DOS.INI, or in a
                directory included in your PATH.

                4DOS.HLP contains the text for the 4DOS help program.  It
                must be in the same directory as 4HELP.EXE, or in a
                directory included in your PATH.

                KSTACK.COM is the used by the KEYSTACK command.  If you
                wish to use the KEYSTACK command, this file should be
                loaded in your AUTOEXEC.BAT file (under DOS) or separately
                for each 4DOS session (under Windows 95/98/ME; see page 48
                for details).  This file does not have to be in the 4DOS
                directory.  If KSTACK.COM has not been loaded, you will see
                an error message when you attempt to use the KEYSTACK
                command.

                OPTION.EXE is a utility used by the OPTION command to
                configure 4DOS.  For the OPTION command to work, this file
                must be in the 4DOS installation directory shown in the
                InstallPath directive in 4DOS.INI, or in a directory
                included in your PATH.






        4DOS, 4NT, Take Command Introduction and Installation Guide               43 


        Chapter 5 / 4DOS Configuration and Notes


             Creating 4DOS Shortcuts and Registry Extensions

             When 4DOS is installed using automated installation software
             it normally creates Start menu entries and registry extensions
             as described on page 23.  The installation software can also
             create a desktop shortcut for 4DOS.

             If you need to create a Start menu entries or desktop
             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:

                * To create additional shortcuts elsewhere on the Start
                  menu, or modify the Programs entries, click the right
                  mouse button 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.

                * To create one or more shortcuts on the desktop to run
                  4DOS, click the right mouse button in any open area of
                  the desktop.  On the popup menu, click New, then
                  Shortcut.  Fill in the drive and path as d:\path\4DOS.COM
                  (use the appropriate drive and path for your system).

             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 4DOS from that shortcut.
             For details on the command line options available, see Chapter
             4 and the Starting 4DOS section of the online help.

             For more information on creating and configuring shortcuts or
             modifying the Start Menu, see your Windows documentation.

             If you want to make these changes as a group, or reinstall
             shortcuts and registry extensions without reinstalling 4DOS,
             see the support area of our web site for a set of registry
             extension (.INF) files you can download and install.  These
             files create shortcuts and registry changes similar to those
             made by the installation software.  The comments within each
             file explain how to install and uninstall it.

        The 4DOS Help System

             The 4DOS help program is called 4HELP.EXE; the help text is
             stored in the file 4DOS.HLP.  The 4DOS help system provides
             complete help for 4DOS commands and features; on most systems



        44                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


             it can also launch the DOS help program to display help on
             external DOS commands like FORMAT or SORT.

             The section entitled "The 4DOS Help System" within the help
             system itself explains navigation keystrokes and mouse usage
             in more detail, as well as instructions on linking the help
             system to DOS help or other help programs.

             If you do not have 4DOS running, you can start the help system
             by moving into the directory that contains your 4DOS files (we
             assume that you are using C:\4DOS in this example) and typing
             this command:

                C:\4dos> 4help

             You can use this command if you are unable to install 4DOS
             completely for some reason; information in the help system
             will likely help you solve the problem.

        4DOS and Your Computer

             4DOS will work on any IBM PC-compatible hardware, regardless
             of the CPU type, amount of memory (assuming the minimum 256K
             or so required to run 4DOS is available), disk configuration,
             or video hardware.  The notes below briefly cover memory,
             video, and disk issues.

             Memory

             4DOS knows how to use XMS memory, EMS memory, and Upper Memory
             Blocks (UMBs) in order to minimize the amount of space it
             takes in the 640K of DOS memory available to your application
             programs.  You can control 4DOS's memory usage with directives
             in the 4DOS.INI file.  For more details about configuring
             4DOS's memory usage see Initialization Directives under .INI
             File Directives in the 4DOS.INI section of the online help.
             You can also set most memory usage options easily from the
             Startup page of the OPTION command's dialogs.

             By default, 4DOS uses normal DOS memory ("low memory") for its
             small resident portion of about 3 - 4K.  4DOS can reduce its
             low memory usage by moving most of this information to Upper
             Memory Blocks (UMBs), when requested with UMBLoad and other
             UMB-related directives in the 4DOS.INI file.

             Low memory is also used to hold the larger (about 250K)
             transient portion of 4DOS while your system is at the prompt,
             or executing an internal 4DOS command or batch file.  When an


        4DOS, 4NT, Take Command Introduction and Installation Guide               45 


        Chapter 5 / 4DOS Configuration and Notes


             external application is running 4DOS moves its transient
             portion to EMS or XMS memory (or the hard disk), so the memory
             is available to the application.  For additional details see
             the online help or the Reference Manual, and in particular the
             documentation on the Swapping directive in 4DOS.INI.

             Video

             4DOS can normally adjust itself to your video hardware
             automatically, regardless of your video adapter and the number
             of rows and columns on your screen.

             Most video problems turn out to be unrelated to 4DOS, and are
             often due to the underlying operating environment (for
             example, attempting to display blinking text in a window when
             the underlying environment does not support this feature).

             If you experience scrolling or color problems, you should also
             check whether you have an ANSI driver installed, and if so
             verify that it is configured correctly and can support your
             video hardware.

             Disk Drives

             4DOS supports all types of disks including floppy disks, hard
             disks, high-capacity removable disks, compressed drives,
             network drives, and RAM disks.  4DOS never directly modifies
             the FAT, root directory, subdirectories, or other system areas
             of the disk, and it doesn't write any data directly to your
             disk.  It always calls on DOS to perform these actions, just
             like most application programs do.  As a result, 4DOS is
             compatible with all disk sizes, formats, and structures that
             your DOS or Windows version supports.

             If you receive unexpected results related to a disk drive or
             disk file (for example, an apparent error in the amount of
             free space on a drive, or an "access denied" message when
             attempting to use a file you thought was available), chances
             are that 4DOS is merely reporting information provided by the
             operating system, and is not the source of the problem.

        4DOS and DOS

             4DOS is compatible with MS-DOS or PC-DOS 3.1 and above, DR DOS
             / Novell DOS / OpenDOS 3.4 and above, Windows 95 / 98 / ME
             (and their built-in version of DOS, "MS-DOS 7"), and OS/2 DOS




        46                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


             sessions.  See page 47 for additional important information on
             Windows 95/98.

             Detailed information on 4DOS and DOS is covered in the
             Compatibility section of the online help.  If you use any of
             the DOS versions or features listed below, you may want to
             check that topic for additional information.  This is only a
             partial list of the DOS-related items discussed in the online
             help.  Inclusion of an item here does not mean it is
             incompatible with 4DOS, but only that more information on it
             is available in the help system.  The help system includes
             information you may need if you use:

                * Any version of DR DOS, Novell DOS, or OpenDOS.

                * Utilities which allow multiple configurations in your DOS
                  CONFIG.SYS file, including the MS-DOS or Windows 95/98
                  multiple configuration feature.

                * The MS-DOS APPEND utility.

                * The FORMAT /S and SYS commands (used to create a bootable
                  floppy disk) under MS-DOS or PC-DOS version 4.0 or above.

                * The DBLSPACE and DRVSPACE disk compression utilities.

                * The MS-DOS 6.x and Windows 95/98 HELP command.

                * The FASTOPEN utility.

                * The MS-DOS 6.x and Windows 95/98 MOVE command.

                * The MS-DOS / PC-DOS 6.x SMARTDRV disk cache.

        4DOS and Microsoft Windows 95/98/ME

             This section provides basic information on using 4DOS under
             Windows 95, Windows 98, and Windows ME.  For additional
             details see the Compatibility section in the online help.

             4DOS works well as both the primary shell, loaded before
             Windows 95/98, and when loaded from the Windows 95/98 desktop.
             Under Windows ME 4DOS can only be loaded from the desktop, not
             as a primary shell before Windows starts.

             If you are using 4DOS under Windows 95 or Windows 98, we
             strongly recommend that you install it as the primary shell in
             CONFIG.SYS (this is the way 4DOS is normally installed).  If
             you do not install 4DOS as the primary shell, individual 4DOS
             sessions will not be able to share global alias and history
             lists.  Each 4DOS session will have to process the .INI file


        4DOS, 4NT, Take Command Introduction and Installation Guide               47 


        Chapter 5 / 4DOS Configuration and Notes


             before it starts, and if you have two or more 4DOS sessions
             running simultaneously from the Windows desktop, they will use
             more system resources than they would if 4DOS were installed
             as the primary shell.

             If you have a typical Windows configuration, and install 4DOS
             as the primary shell, generally you must have an AUTOEXEC.BAT
             file, even if it only consists of a single REM statement.  In
             most cases, Windows 95/98 will not load the primary shell if
             it cannot find an AUTOEXEC.BAT file in the root directory of
             your boot drive.

             Installing 4DOS Under Windows 95/98/ME

             The 4DOS installation program will install and configure 4DOS
             correctly for Windows 95, 98, and ME.  If you are installing
             4DOS manually, follow the instructions under Manual
             Installation on page 39.

             If you reinstall Windows 95/98, your SHELL= line will be
             removed from CONFIG.SYS by the Windows installation process.
             To correct this, simply boot the new version and use Notepad
             or another ASCII editor to put the SHELL= line back in
             CONFIG.SYS as described in the manual installation
             instructions on page 39, then restart Windows.

             If you load Windows 95/98 in "safe mode" your startup files
             (CONFIG.SYS and AUTOEXEC.BAT) are ignored, and 4DOS will not
             be loaded as the primary shell.  If you start Windows in "safe
             mode" use caution if you load 4DOS after the GUI starts.  DOS
             applications sometimes do not work properly in "safe mode."

             For information on desktop shortcuts and registry extensions
             for 4DOS under Windows 95/98/ME, see page 44.

             Installing the KSTACK Program in Windows 95/98/ME

             If you want to load KSTACK.COM (required for the KEYSTACK
             command) it should be loaded separately for each 4DOS session
             in Windows 95/98/ME.  To do so, include the KSTACK command as
             the last item on the startup command line when you set up the
             corresponding shortcut(s).  For example, the command line for
             your shortcut might read:

                c:\4dos\4dos.com c:\4dos\kstack.com

             This will load KSTACK when 4DOS starts, then display a prompt.



        48                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


             If you install KSTACK in AUTOEXEC.BAT, it may not work
             properly when multiple 4DOS windows are open, as stacked
             keystrokes may "bleed through" from one window to another.

             You can also address this issue by loading KSTACK in 4START
             (see page 36), with an IF command to make sure it is not
             loaded from AUTOEXEC.BAT in the primary shell.  To do so, use
             a line like this in 4START:

                if %_shell ne 0 c:\4dos\kstack.com

        Using 4DOS on a Network

             This section will give you some tips on using 4DOS on a
             network, and on the proper locations for 4DOS files on a
             network.  For additional details, and any additional
             information about compatibility with your particular network,
             see the Compatibility section in the online help.

             In general, you'll find that you can load and run your network
             software normally under 4DOS.  Network drives will be
             accessible as normal drives once the network is loaded, and
             files on the network will be accessible just as if they were
             on a local hard disk.

             Some networks support file and directory names beginning with
             a double backslash [\\], also called "UNC" names, or with a
             server name followed by a colon, to identify files by their
             location on the network.  4DOS detects such names and passes
             them through to the network unaltered, allowing the network
             software to process them.

             Some networks support server disk partitions which exceed the
             standard DOS 2 GB partition size limit, but don't provide DOS
             applications with access to information about the drive size.
             On these drives, 4DOS may not be able to return proper free
             space or total space figures because the drive size
             information returned by DOS is not accurate.  If you have such
             a drive, you may need to use a network or server utility to
             obtain accurate partition size and free space information.

             If you need to boot a diskless workstation from a network
             drive, see the Novell Netware topic under Software in the
             Compatibility section of the online help.  The techniques
             described there will allow you to set your system up under
             Netware to avoid accesses to the boot drive once 4DOS is
             running, and can generally be used for other networks as well.



        4DOS, 4NT, Take Command Introduction and Installation Guide               49 


        Chapter 5 / 4DOS Configuration and Notes


             4DOS and Novell Netware

             4DOS includes a special 4DOS.INI directive for Netware called
             NetwareNames. You must set NetwareNames = Yes on systems which
             load Netware, in order to avoid problems with destroyed
             environment variables during LOGIN.  See Compatibility in the
             online help for more information.

             4DOS can also be set up to run on Novell Netware diskless
             workstations that boot from the server.  To do so, you must
             make several changes to 4DOS.INI and your other startup files;
             see the Compatibility section of the online help for complete
             details.

        Uninstalling 4DOS Manually

             For automated uninstall instructions, see page 25.

             The steps required to remove 4DOS from your system manually
             depend on the operating system you are using:

                * If you are running 4DOS under Windows 95/98/ME, and you
                  installed the 4DOS shortcuts or registry extensions from
                  a downloaded .INF file, remove them as described in the
                  file.

                * Next delete any remaining Windows desktop objects or
                  Start menu entries that refer directly to 4DOS.

                * If you are not running Windows ME (which doesn't have a
                  CONFIG.SYS file), find the location of COMMAND.COM on
                  your disk (for example, in the root directory, or the DOS
                  directory).  Then use your editor to edit the CONFIG.SYS
                  file in the root directory of the boot drive.  If you are
                  running DOS 5 or below, before modifying CONFIG.SYS be
                  sure you have a bootable floppy disk as described on page
                  38.

                  Look for the line which begins with SHELL=, and either
                  delete it, or insert the characters "REM " at the
                  beginning of the line.  Next, add a new line like this:

                     SHELL=d:\path\COMMAND.COM d:\path /P

                  where "d:\path" is the drive and directory for
                  COMMAND.COM (this same directory name is repeated after
                  the full name of COMMAND.COM and before the /P).  If you
                  were previously running COMMAND.COM with a /E:nnnn switch



        50                                      (c) 2003 JP Software Inc. 


                                          Chapter 5 / 4DOS Configuration and Notes


                  to set the size of your environment, add it to this line
                  as well.

                * After CONFIG.SYS has been modified, edit your
                  AUTOEXEC.BAT file to remove any changes made to
                  accommodate 4DOS.  Look for a command beginning SET
                  COMSPEC= and another which loads the 4DOS file
                  KSTACK.COM.  The SET COMSPEC command will not be present
                  on most systems.  If it's there, remove it, or change it
                  to:

                     SET COMSPEC=d:\path\COMMAND.COM

                  where "d:\path" is replaced by the correct drive and
                  directory for COMMAND.COM.  Then add "REM " in front of
                  the KSTACK.COM command to convert it to a comment, or
                  delete the line entirely.

             Now reboot your system, and you should be back up and running
             under COMMAND.COM.  You can check the 4DOS directory for any
             files you placed there that you want to save.  Then delete the
             4DOS files and remove the 4DOS directory if you wish to do so.
































        4DOS, 4NT, Take Command Introduction and Installation Guide               51 


                                           Chapter 6 / 4NT Configuration and Notes



        Chapter 6 / 4NT Configuration and Notes

        This chapter covers manual installation and configuration of 4NT.
        For information on startup options for 4DOS and 4NT under various
        operating systems see chapter 4 on page 29.   For 4DOS
        configuration see chapter 5 on page 38.  For information on Take
        Command, see chapter 7 on page 61.

        4NT works all Intel-based computers that run Windows NT 4.0,
        Windows 2000, or Windows XP.  This chapter provides the basic
        information you need to run 4NT.  If you need detailed technical
        information or troubleshooting assistance on any of these topics,
        consult the Troubleshooting, Service, and Support topic in the 4NT
        online help.

        If you used SETUP.EXE to install 4NT, you can skip this chapter,
        and return to it only if you have difficulty with the program or
        want to fine-tune it meet your needs.

        4NT Installation Notes

             If you run 16-bit character-mode applications which "shell to
             DOS" (i.e., start a secondary command prompt session), we
             recommend that you enable the NTCMDPROMPT directive in the
             \WINNT\SYSTEM32\CONFIG.NT file.  This Windows feature affects
             operation of shells started from 16-bit programs, and is not
             specifically related to 4NT.  However, in our experience using
             it improves operation, and prevents certain problems with
             secondary shells (e.g., requiring you to type an extra EXIT
             command to return to the parent application).  NTCMDPROMPT may
             or may not work well in your particular situation, and
             experimentation is usually required to determine the best
             configuration.  For further documentation on NTCMDPROMPT read
             the comments provided by Microsoft in CONFIG.NT.

        Using 4NT Under Windows 98, and ME

             4NT is designed principally to run under Windows NT, Windows
             2000, and Windows XP.  However, it is also supported under
             Windows 98 and ME.  This section explains the reasons for
             using 4NT in this environment, as compared to our standard
             Windows 95/98/ME product, 4DOS.  For additional details and
             discussion of any minor issues that may arise with 4NT under
             Windows 98/ME, see the Setup and Troubleshooting section of
             4NT's online help.



        4DOS, 4NT, Take Command Introduction and Installation Guide               53 


        Chapter 6 / 4NT Configuration and Notes


             The following list shows the major areas where 4DOS and 4NT
             differ in their behavior when used under Windows 98 and ME:

                System startup:  Under Windows 98, 4DOS is normally loaded
                as the DOS primary shell in CONFIG.SYS, which means that
                its capabilities are available when booting to a command
                prompt (without loading Windows).  4NT cannot be loaded in
                this way, as it requires Windows to be loaded before it can
                function.  (This difference is immaterial under Windows ME,
                where a command prompt boot option is not available.)

                Command line length:  4DOS accepts commands up to 511
                characters long.  4NT accepts commands up to 2047
                characters long, and can allow these lines to expand to up
                to 4095 characters during processing.  4NT's support for
                much longer command lines may be important for software
                developers who must use long commands to set compiler
                environment variables, and for other similar tasks.

                Performance:  4DOS can produce very fast text output under
                Windows 95, 98, and ME.  Text output from 4NT is often
                somewhat slower -
                                - for example, under Windows 98 and ME the
                4DOS DIR command will probably display a directory more
                quickly than 4NT's DIR.  This is due to the way Windows is
                designed; Windows 95, 98, and ME produce faster output from
                16-bit text mode programs like 4DOS, while Windows NT, 2000
                and XP generally produce faster output from 32-bit programs
                like 4NT.  This effect is less noticeable on faster
                systems, but you may want to check the speed on your system
                before deciding to use 4NT under Windows 98 or ME.

                Features:  While 4DOS and 4NT are highly compatible, they
                do not have the exact same feature set.  4NT offers certain
                features not available in 4DOS (e.g. FTP support, and
                MSGBOX and QUERYBOX commands).  4DOS also offers some
                features not available in 4NT (e.g. the LOCK command), and
                is somewhat better integrated with Windows 9x and ME.

                Windows Bugs:  The portion of Windows 98 which provides
                support to 32-bit console applications like 4NT has a
                number of minor but annoying long-standing bugs that do not
                affect 4DOS, which is a 16-bit application.  For example,
                the window close button does not work in 4NT; only a
                limited range of text window dimensions can be supported
                for 32-bit programs, etc.  These problems are somewhat less
                prevalent in Windows ME.





        54                                      (c) 2003 JP Software Inc. 


                                           Chapter 6 / 4NT Configuration and Notes


             In sum, if you need 4NT's features, such as long command
             lines, FTP support, and additional commands, it can be an
             excellent choice under Windows 98 and ME as long as you are
             willing to put up with slightly slower output and a few minor
             problems of integration with the Windows GUI.  If you don't
             need these features, it's important to you to be able to boot
             to a JP Software command prompt, or you want the fastest text
             output and the best Windows 98 and ME integration, use 4DOS.

             Many customers find that the best solution is the one we use
             at JP Software, which is to install both products, using one
             most of the time and the other where its benefits are
             particularly important.  (If you choose to install both, we
             offer a significant discount for adding the second product.)

        Manual Installation of 4NT

             This section is for advanced users and assumes you are
             generally familiar with ASCII editors, batch files, and other
             similar concepts.  In most cases, you can select the
             installation options you need using SETUP.EXE, and manual
             installation is not necessary.

             In order to install 4NT manually, you must extract or copy the
             necessary files, brand 4NT if necessary, create or modify any
             configuration files you need, and then create the necessary
             commands to start the program on your system.

             Extracting or Copying the Program Files

             When you extract or copy the 4NT 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 4NT files in
             the same directory.  See 4NT Files and Directories on page 56
             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.  The various methods
             are described on page 24.






        4DOS, 4NT, Take Command Introduction and Installation Guide               55 


        Chapter 6 / 4NT Configuration and Notes


             Registering 4NT

             When you purchase a new or upgrade copy of 4NT, you will
             receive an email with an attached file named 4NT.KEY.  Double
             click on the 4NT.KEY attachment (or save it to the disk and
             type the file name) to register 4NT  with your name and serial
             number.  (A popup may appear asking if you want to add the
             information in 4NT.KEY to the registry; click on Yes to
             continue.)

             If you are running 4NT at the time you load 4NT.KEY, your
             registration  information won't appear until you exit and
             restart 4NT.

             Remember to save your 4NT.KEY file in a safe place in case you
             need to   reinstall 4NT.  If you have lost your registration
             key, you can request a replacement key by contacting JP
             Software at sales@jpsoft.com.

             4NT Files and Directories

             We strongly recommend that you place all 4NT files in the same
             directory.  If you do not do so, you will probably have to
             explicitly set the locations of 4NT 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:

                4NT.EXE is the 4NT program file.  It must be in the
                directory specified in the Command Line field of every 4NT
                object.

                JPHELP.CHM contains the text for the 4NT help system.
                JPHELP.CHM must be in the same directory as 4NT.EXE.

                KEYSTACK.EXE is a small utility that is used by the
                KEYSTACK command to send keystrokes to application
                programs.  For the KEYSTACK command to work this file must
                be in the same directory as 4NT.EXE, or in a directory
                included in your PATH.

                SHRALIAS.EXE is a small utility that is used by the
                SHRALIAS command to save the shared alias and history lists
                between 4NT sessions.  For the SHRALIAS command to work
                this file must be in the same directory as 4NT.EXE, or in a
                directory included in your PATH.




        56                                      (c) 2003 JP Software Inc. 


                                           Chapter 6 / 4NT Configuration and Notes


             Creating 4NT Shortcuts and Registry Extensions

             When 4NT is installed using SETUP.EXE, it normally creates
             Start menu entries and registry extensions as described on
             page 23.  The installation software can also create a desktop
             shortcut for 4NT.

             If you need to create a Start menu entries or desktop
             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:

                * To create additional shortcuts elsewhere on the Start
                  menu, or modify the Programs entries, click the right
                  mouse button in an open area of the Task Bar, then select
                  Properties on the menu.  Select the Advanced tab and
                  modify or adjust the menus as required.

                * To create one or more shortcuts on the desktop to run
                  4NT, click the right mouse button in any open area of the
                  desktop.  On the popup menu, click New, then Shortcut.
                  Fill in the drive and path as d:\path\4NT.EXE (adjust the
                  drive and path for your system).

             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 4NT from that shortcut.
             For details on the command line options available, see Chapter
             4, and Starting 4NT under Setup and Troubleshooting in the
             online help.

             For more information on creating and configuring shortcuts or
             modifying the Start Menu, see your Windows documentation.

             If you want to make these changes as a group, or reinstall
             shortcuts and registry extensions without reinstalling 4NT,
             see the support area of our web site for a set of registry
             extension (.INF) files you can download and install.  These
             files create shortcuts and registry changes similar to those
             made by the installation software.  The comments within each
             file explain how to install and uninstall it.

        The 4NT Help System

             When you start the 4NT help system, 4NT opens a new window to
             run the standard Windows help program.  The help program



        4DOS, 4NT, Take Command Introduction and Installation Guide               57 


        Chapter 6 / 4NT Configuration and Notes


             displays the help text from the file JPHELP.CHM, and lets you
             browse through it.

             4NT's help text does not cover the Windows external commands
             because they are included in Windows's built-in Command
             Reference.

             If you start the help system from a 4NT window on the Windows
             desktop, you will be returned to that window when you close
             the help program.  However, if you have switched the window to
             full-screen mode before invoking the help system, you must
             return to 4NT manually (using standard Windows methods for
             switching between windows).  This is due to the design of
             Windows Help and is not a limitation of 4NT.

             You can also keep the help window on the screen and return to
             the 4NT window, switching between the two windows as needed.
             This may be useful when you are writing a batch file, working
             on a complex command, or experimenting with 4NT.

             In order for the 4NT help system to work properly, the help
             text file, JPHELP.CHM, must be in the same directory as
             4NT.EXE.

             The 4NT installation program sets up a separate object for the
             help system so that you can load the help file directly.  To
             create a similar object manually, create an object with a
             command line like this:

                WINHLP32 C:\4NT\JPHELP.CHM

             (Change the drive and path to reflect the location of
             JPHELP.CHM  on your system.)

             4NT also supports the /? switch to display "quick help" for
             any command.

        Uninstalling 4NT Manually

             For automated uninstall instructions, see page 25.

             To remove 4NT manually perform the following steps:

                * If you installed the 4NT shortcuts or registry extensions
                  from a downloaded .INF file, remove them as described in
                  the file.

                * Delete any remaining Windows desktop objects or Start
                  menu entries that refer directly to 4NT.


        58                                      (c) 2003 JP Software Inc. 


                                           Chapter 6 / 4NT Configuration and Notes



                * Check the 4NT directory for any files you placed there
                  that you want to save.  Then delete the 4NT files and
                  directory from your disk.




















































        4DOS, 4NT, Take Command Introduction and Installation Guide               59 


                                  Chapter 7 / Take Command Startup and Configuration



        Chapter 7 / Take Command Startup and Configuration

        This chapter covers startup options, manual installation, and
        configuration of Take Command.  For information on 4DOS and 4NT,
        see chapters 4 - 6.

        This chapter provides basic information about Take Command.  If you
        need detailed technical information or troubleshooting assistance
        on any of these topics, consult the Troubleshooting, Service, and
        Support topic in the online help.

        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 the online help and in Chapter 5 of the
        Reference Manual) and by the .INI file (explained briefly below,
        and in detail in the online help and Chapter 6 of the Reference
        Manual).

        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 section.  However,
        you may want to skim this material to see what options are
        available.

        Starting Take Command

             You will typically start Take Command from a Windows desktop
             shortcut or from the Programs section of the Start menu.
             SETUP.EXE will create a JP Software entry on the Start Menu,
             and objects within it to start Take Command and its online
             help.  A desktop shortcut for Take Command can be created
             during installation as well.

             Usually these are sufficient, but if you prefer you can create
             multiple shortcuts to start Take Command with different
             startup commands or options, or to run different batch files
             or commands.  You can use these items to run commonly used
             commands and batch files directly from the desktop.

        Command Line Options

             Some Take Command options are required in certain
             circumstances; others provide finer control over the way the
             program starts.



        4DOS, 4NT, Take Command Introduction and Installation Guide               61 


        Chapter 7 / Take Command Startup and Configuration


             The shortcut command that starts Take Command will typically
             include the program name with drive and path then include any
             switches for the program, for example:

                c:\tcmd\tcmd32.exe

             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 /LF /LH /T:bf /U] [[/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.

             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 (TCMD32.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.

                * @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 (TCMD32.INI) and it is either
                  in the same directory as the executable program, or in
                  the Windows 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


        62                                      (c) 2003 JP Software Inc. 


                                  Chapter 7 / Take Command Startup and Configuration


                  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.

                * /L, /LA, /LD, /LF and /LH:  These options tell Take
                  Command to use local alias, directory history, function,
                  and / or command history lists.  They will override any
                  LocalAlias=No, LocalFunctions=No, LocalHistory=No, or
                  LocalDirHistory=No settings in TCMD32.INI.  This allows
                  you to use global lists as the default, but start a
                  specific shell or session with local aliases, functions,
                  or histories.  See the online help or the Reference
                  Manual for details on local and global aliases,
                  functions, and histories.  /LA forces local aliases, /LD
                  forces local directory history, /LF forces local
                  functions, /LH forces local command history, and /L
                  forces all four.

                *

                  /T:bf:  This option sets the foreground and background
                  colors in Take Command'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 will find it easier to 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 64).

                *

                  /U:  This option causes the output of internal commands
                  to a pipe or redirected to a pipe to be in Unicode.
                  (Unicode versions of Take Command only.)

                * [/C] command:  This option tells Take Command to run a
                  specific command after starting.  The command will be run
                  after TCSTART (see page 64), 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.

                  When the command is preceded by a /C, Take Command will
                  execute the command and then exit and return to the

        4DOS, 4NT, Take Command Introduction and Installation Guide               63 


        Chapter 7 / Take Command Startup and Configuration


                  parent program or the desktop without displaying a
                  prompt.

             For example, this command line will start Take Command,
             execute the TCSTART file (if any), execute START.BTM, and then
             display the prompt:

                c:\tcmd\tcmd32.exe c:\tcmd\start.btm

             This command line will start Take Command, 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:\tcmd\tcmd32.exe /la /c c:\tcmd\process.btm

        Creating or Modifying Startup Files

             Take Command uses two files to control the way it starts:  a
             file of configuration information called the .INI file
             (TCMD32.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 created during installation, or the first
             time you run Take Command.  The .INI file should be placed in
             the same directory as the other files for Take Command.

             You can add additional information to the .INI file manually
             with an ASCII editor.  Most of the .INI options can also be
             set directly from within Take Command using the configuration
             dialog accessible from the Configure Take Command selection on
             the Options menu, or with the OPTION command.  There are
             several pages of options within the dialog.

             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 optional.  It is executed each time Take
             Command starts, and gives you a convenient way to load aliases
             and environment variables, and otherwise initialize Take
             Command.  TCSTART is normally placed in the same directory as




        64                                      (c) 2003 JP Software Inc. 


                                  Chapter 7 / Take Command Startup and Configuration


             the other product files, but this may vary if you use the same
             TCSTART file for more than one of our products.

             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 the online help or the reference
             manual.

             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 that point to the old program directory.

        Exit Codes

             If you start Take Command from another program (e.g. to run a
             batch file or internal command), it will return a numeric code
             to the other program when it is finished.  This code is
             usually used to indicate whether the operation performed was
             successful or not, with 0 often indicating success and a non-
             zero value indicating a failure or other numeric result.

             Take Command's exit code is normally the numeric exit code
             from the last internal or external command.  However, for
             compatibility reasons and to avoid conflicts with external
             commands, only some internal commands set the exit code;
             others leave it unchanged from the most recent external
             command.

             If you enter an unknown command the exit code will be 2, which
             is the internal Take Command unknown command error number.

             You can use the EXIT n command to explicitly set the exit
             code.  If you do, this will override the rules above, and set
             the return code to the value in your EXIT command.

             The normal rules described above may not return a code that
             indicates the success or failure of the specific operation
             that concerns you.  Therefore, if you need to rely on the exit
             code from Take Command, we recommend that you use a batch file
             or alias to create the exit code you want, and then set the
             code explicitly with EXIT n.

        Manual Installation of Take Command

             This section is for advanced users, and assumes you are
             generally familiar with the Windows desktop shell, the Windows


        4DOS, 4NT, Take Command Introduction and Installation Guide               65 


        Chapter 7 / Take Command Startup and Configuration


             directory, and other similar topics.  In most cases you can
             select the installation options you need using SETUP.EXE, 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
             shortcuts 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 Files and
             Directories on page 67 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.  The various methods
             are described on page 24.

             Registering Take Command

             When you purchase a new or upgrade copy of Take Command, you
             will receive an email with an attached file named TCMD.KEY.
             Double click on the TCMD.KEY attachment (or save it to the
             disk and type the file name) to register Take Command with
             your name and serial number.  (A popup may appear asking if
             you want to add the information in TCMD.KEY to the registry;
             click on Yes to continue.)

             If you are running Take Command at the time you load TCMD.KEY,
             your    registration information won't appear until you exit
             and restart Take Command.

             Remember to save your TCMD.KEY file in a safe place in case
             you need to   reinstall Take Command.  If you have lost your
             registration key, you can    request a replacement key by
             contacting JP Software at sales@jpsoft.com.






        66                                      (c) 2003 JP Software Inc. 


                                  Chapter 7 / Take Command Startup and Configuration


             Take Command Files and Directories

             We strongly recommend that you place all Take Command 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:

                TCMD32.EXE is the Take Command program file.  It must be in
                the directory specified in the Command Line field of every
                shortcut that starts Take Command.

                JPHELP.CHM contains the text for the Take Command help
                system.  It must be in the same directory as TCMD32.EXE.

                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.

             Creating Take Command Shortcuts and Registry Extensions

             When Take Command is installed using SETUP.EXE it normally
             creates Start menu entries and registry extensions as
             described on page 23.  The installation software can also
             create a desktop shortcut for Take Command.

             If you need to create a Start menu entries or desktop
             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:

                * To create additional shortcuts elsewhere on the Start
                  menu, or modify the Programs entries, click the right
                  mouse button in an open area of the Task Bar, then select
                  Properties on the menu.  Select the Advanced tab and
                  modify or adjust the menus as required.

                * To create one or more shortcuts on the desktop to run
                  Take Command, click the right mouse button in any open
                  area of the desktop.  On the popup menu click New, then
                  Shortcut.  Fill in the drive and path as




        4DOS, 4NT, Take Command Introduction and Installation Guide               67 


        Chapter 7 / Take Command Startup and Configuration


                  d:\path\TCMD32.EXE (adjust the drive and path for your
                  system).

             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 from that
             shortcut.  For details on the command line options available,
             see Chapter 4, and Starting Take Command under Setup and
             Troubleshooting in the online help.

             For more information on creating and configuring shortcuts or
             modifying the Start Menu, see your Windows documentation.

             If you want to make these changes as a group, or reinstall
             shortcuts and registry extensions without reinstalling Take
             Command, see the support area of our web site for a set of
             registry extension (.INF) files you can download and install.
             These files create shortcuts and registry changes similar to
             those made by the installation software.  The comments within
             each file explain how to install and uninstall it.

        Character-Mode Applications

             When you start a DOS program or a 32-bit Windows character-
             mode program under Take Command, 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.  For complete details, see Console Applications
             and the Console Window in the online help (under "Using the
             Take Command Interface").

             The console session window is connected to Take Command, 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 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


        68                                      (c) 2003 JP Software Inc. 


                                  Chapter 7 / Take Command Startup and Configuration


             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 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, it continually scans
             the hidden 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 a 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 and Caveman.

        Uninstalling Take Command Manually

             For automated uninstall instructions, see page 25.

             To uninstall Take Command manually, follow these steps:

                * If you installed the Take Command shortcuts or registry
                  extensions from a downloaded .INF file, remove them as
                  described in the file.

                * Delete any remaining Windows desktop objects or Start
                  menu entries that refer directly to Take Command.





        4DOS, 4NT, Take Command Introduction and Installation Guide               69 


        Chapter 7 / Take Command Startup and Configuration


                * Check the Take Command directory for any files you placed
                  there that you want to save.  Then delete the Take
                  Command files and directory from your hard drive.





















































        70                                      (c) 2003 JP Software Inc. 


                                                                       Index


        Index

        4
        4DOS
            branding, 36
            compatibility with
                memory, 42
                older DOS versions, 35
                operating system versions, 35
                video display, 43
            configuration, 35
            installation
                directory, 36, 40
                manual, 36
                uninstalling, 47
        4DOS.HLP, 40, 41
        4EXIT, 33
        4HELP.EXE, 40, 41
        4NT
            and operating system versions, 49
            configuration, 49
            installation
                directory, 51, 52
                manual, 51
                uninstalling, 54
            registering, 51
            under Microsoft Windows 98, and ME, 49
        4START, 33
            and startup command, 32
            single-step option, 32

        A
        Alias list, local and global, 42
        Aliases, 16
            local and global, 30, 57
            technical support for, 7
        ANSI driver, and 4DOS, 43
        APPEND command, and 4DOS, 44
        Applications, character-mode and DOS, under Take Command, 62
        Apps menu, 14
        AUTOEXEC.BAT
            and installation, 38
            and startup command, 32
            disabling, 29
            running, 30
            single-step option, 32
            starting KSTACK.COM, 38


        4DOS, 4NT, Take Command Introduction and Installation Guide               71 


        Index


        B
        Batch files, 17
            technical support for, 7
        Branding
            4DOS, 36
            of 4DOS electronic purchases, 37
            of CD-ROM copies, 37
            of downloaded minor upgrades, 37
            upgrades, 38

        C
        Caveman, 62
        Clipboard, 15
        Colors
            problems with, in 4DOS, 43
            setting, in 4NT, 31
        Colors, setting, in Take Command, 57
        Command history, local and global, 30, 57
        Command line enhancements, 11
        Command window, 14
        Commands, 10
        Compatibility (4DOS)
            and DOS, 43
            and Microsoft Windows 95/98/ME, 44
            and networks, 46
            and Novell Netware, 46
        COMSPEC
            environment variable
                setting automatically, 28
                setting manually, 39
            path, 28, 38
        COMSPEC path, 56
        CONFIG.NT, 49
        CONFIG.SYS
            and installation, 38
            DOS configuration utilities, 44
        Configuration, 15, 27
            .INI file, 33, 58
            4DOS, 35
            4NT, 49
            4START and 4EXIT, 33
            dialogs, 58
            OPTION command, 33, 58
            primary and secondary shells, 27
            starting Take Command, 55
            startup options, 28, 55
            Take Command, 55


        72                                      (c) 2003 JP Software Inc. 


                                                                       Index


            TCSTART and TCEXIT, 58
        Console session, in Take Command, 62
        Contacting JP Software, 5
        Critical errors, 30
        Customer service, 5

        D
        DBLSPACE, and 4DOS, 44
        DDE, 15
        Directory history list, local and global, 30, 57
        Diskless workstations, 46
        Disks
            drives, and 4DOS, 43
            free space, and 4DOS, 43
        DOS
            older versions, and 4DOS, 35
            shell, 9
        DR DOS, and 4DOS, 43
        Drag and Drop, 15
        DRVSPACE, and 4DOS, 44

        E
        Edit menu, 14
        Enhancements
            aliases and batch files, 16
            command line, 11
            commands, 10
            configuration, 15
        Environment, memory for, 29
        Exit codes
            4DOS and 4NT, 33
            Take Command, 59

        F
        FASTOPEN, and 4DOS, 44
        File names, on networks, and 4DOS, 46
        FORMAT /S command, and 4DOS, 44
        FTP site, JP Software, 5

        H
        Hard drives, and 4DOS, 43
        HELP command, MS-DOS, 44
        Help menu, 14
        Help system, 5, 25
            /? option, 25
            4DOS, 41


        4DOS, 4NT, Take Command Introduction and Installation Guide               73 


        Index


            4NT, 53
            key topics in, 26
            location of files
                4DOS, 40
                4NT, 52
                Take Command, 60
        History list, local and global, 42

        I
        INI directives, on startup command line~.~, 29, 56
        INI file~.~, 33, 58
            and manual installation of 4DOS, 39
            location of, 29, 56
            sections, 58
        Installation, 19
            directory
                4DOS, 36, 40
                4NT, 51, 52
                Take Command, 59, 60
            extracting individual files, 21
            manual
                4DOS, 36
                4NT, 51
                Take Command, 59
            of upgrades, 20
            reversing, 22
                4DOS, 47
                4NT, 54
                Take Command, 63
        InstallPath, 39

        J
        JP Software, contacting, 5
        JPHELP.CHM, 52, 53, 60

        K
        KSTACK.COM, 38
            and Windows 95/98, 45

        L
        Local and global aliases and history, 30, 42, 57

        M
        Memory, and 4DOS, 42
        Menu bar, 14
        Microsoft Windows


        74                                      (c) 2003 JP Software Inc. 


                                                                       Index


            desktop, changes during installation, 20
            registry extensions
                for 4DOS, 41
                for 4NT, 52
                for Take Command, 61
            registry, changes during installation, 20
            shortcuts
                for 4DOS, 41
                for 4NT, 52
                for Take Command, 61
            versions of, 3
        Microsoft Windows 95/98/ME
            and 4DOS, 3, 44
            and 4DOS primary shell, 44
            and and Take Command, 3
            and KSTACK.COM, 45
            AUTOEXEC.BAT, 45
            CONFIG.SYS, 44
            HELP command, 44
            installing 4DOS, 45
        Microsoft Windows 98/ME
            and 4NT, 49
        Microsoft Windows NT/2000
            and Take Command, 3
        Microsoft Windows NT/2000/XP
            CONFIG.NT, 49
            NTCMDPROMPT, 49
        MOVE command, 4DOS, 44
        MS-DOS / PC-DOS
            and 4DOS, 43
            APPEND command, 44
            FORMAT /S command, 44
            HELP command, 44
            version 6.x, 32, 34

        N
        Networks, 46
            accessing, 15
            diskless workstations on, 46
            file and directory names on, and 4DOS, 46
        Novell DOS, and 4DOS, 43
        Novell Netware, 46
            diskless workstations on, 47
        NTCMDPROMPT, 49

        O
        OpenDOS, and 4DOS, 43


        4DOS, 4NT, Take Command Introduction and Installation Guide               75 


        Index


        OPTION command, 33, 58
        Options menu, 14

        P
        Primary shell, 27
            and Windows 95/98, 44
        Prompt Solution newsletter, 8

        Q
        Quick help, 25

        R
        README.TXT, 5
        Reference manual, 4
        Registering
            4NT, 51
            Take Command, 60
        Registration, 8
        Resident portion (of 4DOS), 42

        S
        Scrolling problems, and 4DOS, 43
        Secondary shell, 27
            4NT, 49
        Service, 5
        Shell
            DOS shell, 9
            primary, 27
            secondary, 27
                4NT, 49
        SMARTDRV, and 4DOS, 44
        Start menu
            adding 4DOS, 41
            adding 4NT, 52
            adding Take Command, 61
        Starting Take Command, 55
        Startup files
            4DOS and 4NT, 33
            Take Command, 58
        Startup options
            4DOS and 4NT, 28
            Take Command, 55
        Status bar, 14
        System files, changes during installation, 20





        76                                      (c) 2003 JP Software Inc. 


                                                                       Index


        T
        Take Command
            and character-mode or DOS applications, 62
            and Windows features, 15
            configuration, 55
            installation
                directory, 59, 60
                manual, 59
                uninstalling, 63
            registering, 60
            window, 13
        Take Command products, 3
        TCEXIT, 58
        TCSTART, 58
            and startup command, 57
        Technical support, 6
        Title bar, 13
        Tool bar, 14
        Transient portion (of 4DOS), 42

        U
        Uninstalling
            4DOS, 47
            4NT, 54
            automated, 22
            Take Command, 63
        Upgrades, 8
            branding, 38
            installing, 20
        Utilities menu, 14

        V
        Video display, and 4DOS, 43

        W
        Web site, JP Software, 5













        4DOS, 4NT, Take Command Introduction and Installation Guide               77 
