Changeset 268

trunk/dll/ipf/archive.ipf

-              r10
+              r268
 :i1 id=aboutExtract.Extract from archives
 :artwork name='..\..\bitmaps\extract.bmp' align=center.
+:p.
 To extract from an archive, select the archive(s), then select
 :hp1.Extract:ehp1. from a context menu.
 …
 extraction, add masks for files to extract, tweak the command line for
 exotic settings, and select the extraction directory (the directory to
 which the files will be extracted.  You can drag file system objects
+which the files will be extracted. You can drag file system objects
 onto the Extract Directory entryfield to set the extraction directory,
 or you can type in one you like, or click the Walk button.
 :p.
 If you check the :hp1.Remember...:ehp1. checkbox, this dialog will
 remember some of its settings for the next time you use it.  Uncheck
+remember some of its settings for the next time you use it. Uncheck
 it and it'll forget them and use the defaults.
 :p.
 …
 not, so, for example, trying to extract "*.PKT" when the file inside the
 archive is "01234567.pkt" will fail to extract the file -- you'd have to
+use "*.pkt".  If in doubt, use both.
+use "*.pkt". If in doubt, use both or use the -C command line switch to
+force UNZIP to ignore case.
 :h2 res=90300 name=PANEL_ARCHIVE.Build an archive
 :i1 id=aboutArchive.Build an archive
 :artwork name='..\..\bitmaps\archive.bmp' align=center.
+:p.
 To build an archive, select some files, then select :hp1.Archive:ehp1.
 from a context menu.  You can add files to an existing archive by
+from a context menu. You can add files to an existing archive by
 link-dragging them onto the archive object, or dragging them onto an
 :hp1.:link reftype=hd res=90200.Archive Container:elink.:ehp1. window.
 …
 listbox from which to pick an archiver.
 After that, another dialog appears to let you modify how the archive
 will be created.  Additional masks may be entered (remember that the ZIP
+will be created. Additional masks may be entered (remember that the ZIP
 and UNZIP programs are case sensitive), the archiver command line
 tweaked, and so forth. Click :hp1.Okay:ehp1. to create the archive, or
 …
 :p.
 Note that the archive name may be an existing archive, in which case
 it's modified by adding the new files.  If some of the files are
+it's modified by adding the new files. If some of the files are
 already in the archive, they're replaced.

trunk/dll/ipf/arclist.ipf

-              r108
+              r268
 :i1 id=aboutArchiveListing.Archive Container
 Archive Container windows presents you with a list of an archive's
 contents.  The menus available here present you with commands which you
+contents. The menus available here present you with commands which you
 can perform on selected files and the archive as a whole, as well as the
 usual configuration of the window's appearance.  You get here by double-
+usual configuration of the window's appearance. You get here by double-
 clicking an archive file in an FM/2 Directory Container window.
 :p.
 …
 Besides the container showing the archive contents and a couple of
 informational fields above that, there's an entry field at the bottom of
 the window that shows the current :hp1.extract directory:ehp1..  This is
 the directory in which any extracted files will be placed.  (Extraction
+the window that shows the current :hp1.extract directory:ehp1.. This is
+the directory in which any extracted files will be placed. (Extraction
 refers to copying files from the archive onto your disk as normal
 files.)  To change the extract directory, enter a new directory into the
 …
 You can drag files onto the Archive Container's listing to add them to
 the archive, and you can drag files from the archive to an FM/2
 directory window.  OS/2's drag and drop "rendering" mechanism would make
+directory window. OS/2's drag and drop "rendering" mechanism would make
 this painfully slow for any other application's window, as each file is
 processed individually (imagine extracting each file in an archive by
 typing a separate command line for each to get an idea how slow it would
 be).  The menu extract items allow optimizing extraction so that only
+be). The menu extract items allows optimizing extraction so that only
 one "pass" needs to be done (note that :hp1.Files->Extract:ehp1. must
 also deal with the OS/2 command line length restriction of 1024 bytes,
 …
 around it.
 :p.
 You can get a popup menu in the container by pressing B2.
+You can get a context menu in the container by pressing B2.
 :p.
 Following is a discussion of the pull-down menus:
 …
 :p.
 :hp1.View:ehp1. causes FM/2 to extract the file(s) to a temporary
 directory and display it/them.  If, for some reason, the files don't
+directory and display it/them. If, for some reason, the files don't
 appear when you attempt to view them, try :hp1.Test:ehp1.ing the archive.
 :p.
 :hp1.Edit:ehp1. works as above but the file(s) are loaded into the
 configured editor instead of being viewed.  File(s) can then be
 :hp1.Refreshed:ehp1. back into the archive.  :hp2.Note&colon.:ehp2.
+configured editor instead of being viewed. File(s) can then be
+:hp1.Refreshed:ehp1. back into the archive. :hp2.Note&colon.:ehp2.
 Do not attempt to Refresh files that were stored with pathnames.
 The pathname will either be lost or an additional file without
 …
 :p.
 :hp1.Exec:ehp1. causes FM/2 to extract all selected files to a temporary
 directory and then runs the cursored file.  If you pick this from a
+directory and then runs the cursored file. If you pick this from a
 popup menu, that would be the file under the mouse pointer when you
 requested the popup.  This allows you to select DLLs, help files, data
+requested the popup. This allows you to select DLLs, help files, data
 files, etc. required to get the application to run correctly as well as
 the executable file.
 :p.
 :hp1.Print:ehp1. causes FM/2 to extract and print selected files.  This
+:hp1.Print:ehp1. causes FM/2 to extract and print selected files. This
 uses the FM/2 printing method, not the OS/2 printer objects (see
 Config->Printer in an FM/2 main window's pulldown menu).
 …
 :p.
 :hp1.Virus Scan:ehp1. causes FM/2 to extract the selected files and then
 run the configured virus checker.  See the :hp1.:link reftype=hd
+run the configured virus checker. See the :hp1.:link reftype=hd
 res=92200.internal Settings notebook's Files/Dirs page:elink.:ehp1..
 :p.
 :hp1.Extract All:ehp1. extracts all files from the archive to the
 extract directory.  :hp1.Extract All &amp. Exit:ehp1. does the
+extract directory. :hp1.Extract All &amp. Exit:ehp1. does the
 same thing but closes the archive listing window after starting the
 extraction.
 …
 directory). :hp1.Extract All w/ Dirs &amp. Exit:ehp1. does the same
 thing but closes the archive listing window after starting the
 extraction.  (:hp2.Note:ehp2. that if all you want to do to an archive
+extraction. (:hp2.Note:ehp2. that if all you want to do to an archive
 is extract from it, you can do so without ever opening a contents box;
 just pull up a context menu on the archive in an FM/2 main window and
 select :hp1.Extract:ehp1..  This is the fastest and most efficient
+select :hp1.Extract:ehp1.. This is the fastest and most efficient
 method of extracting files from an archive.)
 :p.
 …
 :hp2.Archivers:ehp2. are programs that create files composed of
 (usually) compressed data that represents, and allows recreation of,
 normal (uncompressed) files.  These archiver programs are widely used to
 create archive files for downloading from BBSs, information services and
+normal (uncompressed) files. These archiver programs are widely used to
+create archive files for downloading from
 the Internet, and to extract from those archive files once downloaded.
 They're also used to create archives locally for backup purposes, as the
 …
 :pt.&period.ARC
 :pd.Arc
+:pt.&period.TAR
+:pd.Tar
 :eparml.
 :p.
 …
 where the * will be a number indicating the version of the program.
 These are self-extracting archives (archives that extract themselves
 when you run the .EXE) so you don't get a chicken-or-egg scenario.  You
 can find them on BBSs, information services and the Internet -- in other
+when you run the .EXE) so you don't get a chicken-or-egg scenario. You
+can find them on the Internet (Hobbes) -- in other
 words, you can find them the same places where archive files are most
 often used.
+often found.
 :p.
 FM/2 can work with DOS archivers, but they aren't supported.  If you
+FM/2 can work with DOS archivers, but they aren't supported. If you
 decide you want to use your DOS archivers rather than OS/2 native
 archive programs, you'll have to figure it out on your own (see
 …
 the ARCHIVER.BB2 datafile that came with FM/2).
-:h2 res=94200 name=PANEL_AD_FRAME.Editing Archiver Details
-:i1 id=aboutEditArc.Editing Archiver Details
-:p.
-This dialog box, which you can reach from the Config menu, allows you to
-edit the details of an :link reftype=hd res=10015.archiver:elink.. Entry
-boxes are present for all the twenty one fields represented in
-ARCHIVER.BB2 (the text file that contains control information about your
-archivers which FM/2 uses to interface with the archivers).  It's
-probably easier for most people to edit ARCHIVER.BB2 directly with a
-text editor.
-:p.
-:hp1.NOTE&colon.:ehp1.  The simplest method to ensure that your archivers
-work properly with FM/2 is to make sure they're in a directory named in
-your PATH= statement, and check the names of the files to make sure they
-match what's on your system (i.e. UNZIP.EXE in both ARCHIVER.BB2 and on
-your hard disk, not UNZIP.EXE in one and UNZIP32.EXE in another).
-:p.
-In the event that you attempt to list an archive and FM/2 feels you've
-probably bungled the entry in ARCHIVER.BB2, you'll be given an
-opportunity to use this dialog to fix the entry.  In this case, you'll
-see the listbox at the right of the dialog filled with the listing of
-the archive that your archiver made.  You can highlight a line and click
-the << button next to the Start List or End List fields to move the line
-to that entry field (these are the most common mistakes, and FM/2 cannot
-find any files if the Start List string is wrong).  You can double-click
-on a listbox line to have FM/2 "parse" it into the Fld# text boxes for
-you, to make it easier to judge field positions for sizes, dates, and
-filenames.  The filename field in particular is extremely important.  If
-it's too high, FM/2 finds no files.  If it's "in range" but wrong, FM/2 gets
-the wrong fields for filenames.
-:p.
-You may still need to refer to your archiver's documentation, or run it
-to get the help on its command syntax.  FM/2 can't do everything for you,
-but it holds your hand as best it can.
-:p.
-Refer to the ARCHIVER.BB2 file that came with FM/2 for additional
-information and an example.
-:p.
-When you've completed editing the archiver's details, click Okay.  FM/2
-will ask you if you want to rewrite ARCHIVER.BB2 (be sure you save the
-original copy for its complete notes; FM/2 will back it up one version to
-ARCHIVER.BAK).  If you don't rewrite ARCHIVER.BB2, changes are good only
-for the current session (handy for testing).
-:p.
-You can also get to this dialog box from Select Files' Config submenu.
-:p.
-See also&colon.
-:p.
-:link reftype=hd res=94300.Archiver Details Fields:elink.
-:h3 res=94300 name=PANEL_ARCFLDS.Archiver Details Fields
-:i1 id=aboutArcFlds.Archiver Details Fields
-:p.
-:hp2.ID:ehp2.  This field contains an ID for the archiver; something for
-human consumption.  It's a good idea to include the version number of the
-archiver for reference.  An example might be "LHArc 2.11".
-:p.
-:hp2.Add:ehp2.  This field should contain the command that creates
-and adds files to an archive.  An example might be "PKZIP.EXE -a" (NOTE:
-This example assumes the file is on your PATH (see PATH= in CONFIG.SYS).
-If it's not, you'd need to give a full pathname, like
-"C&colon.\UTILS\PKZIP.EXE -a".) Note that commands should include the
-extension so that FM/2 can check them without guessing.  Above this
-field is a button labeled "See." If clicked, the program named in this
-field will be run (you'll be given the opportunity to add arguments to
-the command line) in another window. This lets you check command syntax
-and archiver version, as well as assuring that FM/2 can find your archiver
-executables.
-:p.
-:hp2.Move:ehp2.  This field should contain the command that moves files
-to the archive (adds then deletes the file).  An example might be
-"ARC.EXE mwn".
-:p.
-:hp2.Extension:ehp2.  This field contains the extension normally
-associated with files created by this archiver.  An example might be
-"ZOO" for files created by the Zoo archiver.
-:p.
-:hp2.Extract:ehp2.  This field contains the command that extracts files
-from the archive.  This command should not delete the files from the
-archive when it extracts them, and *must* be present for FM/2 to show you
-a member of the archive (commands other than Extract and List may be
-left blank if necessary).  An example might be "PKUNZIP.EXE -o".  Note
-the "-o" option given; this tells PKUNZIP to automatically overwrite any
-existing files (FM/2 will check to see if any of the files exist and warn
-you if so).  It's important to always include your archiver's "don't
-stop for user input" option; some things occur as detached processes and
-you can't interact with them; the program would be hung, which is
-uncool. Above this field is a button labeled "See." If clicked, the
-program named in this field will be run (you'll be given the opportunity
-to add arguments to the command line) in another window. This lets you
-check command syntax and archiver version.
-:p.
-:hp2.Extract w/Dirs:ehp2.  This field contains the command that extracts
-files from the archive and places them into directories embedded in the
-archive.  An example might be "LH.EXE x /o /s".
-:p.
-:hp2.Signature:ehp2.  This field contains the signature for the archive
-type.  There is usually a byte or few in a particular place in any
-archive that indicates that it is, indeed, an archive of that type.  FM/2
-uses these signatures to "sniff out" which archiver is used to
-manipulate the archive.  Since these signatures sometimes contain
-characters which are "unprintable," you can use \x<hexnum> to represent
-any "strange" characters.  A side effect of this is that two backslashes
-are required to represent a single backslash ("\\" == "\").  See
-:link reftype=hd res=99500.C-style encoding:elink. for more information.
-:p.
-To determine what an archiver's signature is, either ask the archiver's
-author or check several different archives of the type for one or more
-bytes present in each at the same location, usually near the beginning
-of the file.
-:p.
-This field must be entered and valid for FM/2 to detect this type of
-archive (see also Sig(nature) Pos(ition)).
-:p.
-:hp2.List:ehp2.  This field contains the command to list the archive's
-contents.  This command *must* be present and correct for FM/2 to work
-properly with this type of archive.  An example might be "ZOO.EXE v".
-:p.
-:hp2.Test:ehp2.  This field contains the command to test the archive's
-integrity.  An example might be "PKUNZIP.EXE -t".
-:p.
-:hp2.Add with paths:ehp2.  This field contains the command to add files
-to the archiver with their paths (i.e. \FM3\FM3.EXE instead of just
-FM3.EXE).  This can be omitted if the archiver doesn't support the
-command.  An example might be "ZIP.EXE" (Zip defaults to adding paths).
-:p.
-:hp2.Move with paths:ehp2.  As above, but moves the files instead of
-just adding them.  An example might be "PKZIP -m -P".
-:p.
-:hp2.Add and recurse:ehp2.  Adds files to the archive, with paths, and
-recurses into subdirectories.  An example might be "LH a /s".
-:p.
-:hp2.Delete:ehp2.  This field contains the command to delete files from
-the archive.  An example might be "LH.EXE /o /d".
-:p.
-:hp2.Sig(nature) Pos(ition):ehp2.  This field contains a number
-indicating how many bytes into the file the signature is located.  If
-this number is negative, FM/2 looks from the end of the file instead of
-the beginning.
-:p.
-:hp2.F(ile)Name Pos(ition):ehp2.  This field tells FM/2 which field on
-the line of an archive listing is the file name.
-Archive listing fields are numbered from 0.
-The file name position item consists of 4 subfields separated by commas.
-All subfields must be present and correct for FM/2 to get the right
-file names from the archive listing.
-The first is the field number.
-The second is a flag which is set to 1 to indicate that the file
-name is the last field on the line.
-This allows unquoted archive member names to contain spaces
-The third is a flag which is set to 1 to indicate that the file name starts
-at the second character of the field.
-This allows files that are surrounded by unusual bracketing characters.
-The fourth is a flag which is set to 1 to indicate the the file name
-stands alone at the first field in the listing line and
-the file details are on the next line.
-:p.
-To understand what "field on the line of an archive listing" means,
-think of a text line as being broken up into tokens, or words, separated
-by spaces.  These tokens, or words, are fields.  Therefore,
-:p.
-I like Ike.
-:p.
-contains three fields.  Field 0 is "I", field 1 is "like", and field 3
-is "Ike."  Think of it like this&colon.
-.br
-:xmp.
- +--------------------+
- |  0   |  1   |  2   | Field Numbers
- +------+------+------+
- |  I   | like | Ike  | Field Contents
- +------+------+------+
-:exmp.
-:p.
-:hp2.OldS(i)z(e) Pos(ition):ehp2.  This field tells FM/2 which field on
-the line of an archive listing is the old (uncompressed) size of the
-file.  If this isn't available or you don't care about it, you can enter
-a -1 to disable detection of this field entirely.
-:p.
-:hp2.NewS(i)z(e) Pos(ition):ehp2.  This field tells FM/2 which field on
-the line of an archive listing is the new (compressed) size of the file.
-If this isn't available or you don't care about it, you can enter a -1
-to disable detection of this field entirely.
-:p.
-:hp2.Date Pos(ition):ehp2.  This field tells FM/2 which field on
-the line of an archive listing is where the time/datestring is.  If this
-isn't available or you don't care about it, you can enter a -1 to
-disable detection of this field entirely.  You can optionally follow this
-number with a comma and another number that indicates the type of the
-date from any of the formats in the following list&colon.
-.br
-:xmp.
-.  02-08-96  23&colon.55&colon.32
-.   8 Feb 96 23&colon.55&colon.32
-.   8 Feb 96  11&colon.55p
-.  96-02-08 23&colon.55&colon.32
-:exmp.
-:p.
-:hp2.NumDateF(ie)lds:ehp2.  This field tells FM/2 how many fields comprise
-the time/datestring.
-:p.
-:hp2.Start-of-list:ehp2.  The line that comes just before the list of
-files in the archiver listing (see example below).  You can use the
-:hp2.<<:ehp2. button to insert a selected line directly from the listbox
-into this field.
-:p.
-:hp2.End-of-list:ehp2.  The line that comes just after the list of
-files in the archiver listing (see example below).  You can use the
-:hp2.<<:ehp2. button to insert a selected line directly from the listbox
-into this field.
-:p.
-Here's an example of an ARC listing (5.12mpl, command "ARC l"; you may
-need to widen the help windows for this to look right...):
-:p.
-:xmp.
-Name          Length    Date
-============  ========  =========    <--this line is start-of-list
-MAKEFILE           374  28 Nov 89
-QSORT.C          14279  29 Nov 89
-QSORT.EXE        24629  29 Nov 89
-STUFF.H            371  29 Nov 89
-        ====  ========               <--this line is end-of-list
-Total      4     39653
-:exmp.
-:p.
-Note the filename is in position 0, old length in position 1, and the
-date starts in position 2, with 3 parts, and there's no new length
-field (so it'd be -1).  Compare that to the archiver entry for
-ARC 5.12mpl in the "stock" ARCHIVER.BB2 and you should get a feel for
-what all those fields mean.
 :h2 res=98300 name=PANEL_ARCERR.Archive Errors
 :i1 id=aboutArchiveErrors.Archive Errors
 Sometimes FM/2 can't get information from the archiver about an archive.
 There are a couple of reasons this could happen&colon.  The information
+There are a couple of reasons this could happen&colon. The information
 in ARCHIVER.BB2 may be incorrect for the archive type, or the archive may
 be damaged.  Possibly the file "smelled" like an archive but wasn't.
+be damaged. Possibly the file "smelled" like an archive but wasn't.
 Perhaps you selected :hp1.View->As archive:ehp1. on a file that wasn't
 actually an archive.
 :p.
 When this happens, this dialog appears.  You'll be given as much
+When this happens, this dialog appears. You'll be given as much
 information as possible, including the text of what the archiver had to
 say about the archive when it was asked to list its contents, presented
 in an MLE, and allowed four choices&colon.  :link reftype=hd
+in an MLE, and allowed four choices&colon. :link reftype=hd
 res=94200.Edit the archiver details:elink., Test the archive (if you
 have told FM/2 how to test archives with this archiver in ARCHIVER.BB2),
 View the archive, or Cancel the whole thing.
 :p.
 Generally speaking, first Test the archive.  If the archive is okay or
+Generally speaking, first Test the archive. If the archive is okay or
 if the test won't run at all, the problem is most likely in your archive
 information record in ARCHIVER.BB2.  You can View the archive to assure
+information record in ARCHIVER.BB2. You can View the archive to assure
 yourself that it is, in fact, an archive, and perhaps hunt down the
 signature so you can add it to ARCHIVER.BB2 if it's not a listed archive

trunk/dll/ipf/assoc.ipf

-              r10
+              r268
 :i1 id=aboutAssociations.Associations
 :artwork name='..\..\bitmaps\assoc.bmp' align=center.
+(Note&colon.  if you're wondering why FM/2 has Associations separate
+:p.
+(Note&colon. if you're wondering why FM/2 has Associations separate
 from OS/2's, see the :link reftype=hd res=90401.Why separate
 Associations?:elink. topic.  Also note that you can :link reftype=hd
+Associations?:elink. topic. Also note that you can :link reftype=hd
 res=90402."fall through" to OS/2's associations:elink. if desired.)
 :p.
 …
 :p.
 You can use this facility to cause editors specific to different
 datafile types to start when the datafile is selected.  For instance, if
+datafile types to start when the datafile is selected. For instance, if
 you associate "*&period.ICO" with "ICONEDIT.EXE %a" the icon editor will
 be started with the selected icon file when you double-click an icon. A
 special association command line, "<>", causes FM/2 to open the default
+WPS view of an object.  :hp8.Warning&colon.:ehp8.  Do not use this on a
+file associated with AV/2 as you will cause an endless loop as AV/2
+constantly starts itself.
+WPS view of an object.
 :p.
 Signatures provide a mechanism to further test a matching file to
 determine that it is the proper type.  For example, all OS/2 &period.INF
+determine that it is the proper type. For example, all OS/2 &period.INF
 (information) files have the string "HSP" at position 0 of the file. By
 using signature "HSP" at offset 0 for the filemask "*&period.INF" and
 …
 :p.
 To delete an association, select it in the listbox, then click
 :hp1.Del:ehp1..  You should be aware that the association deleted is
+:hp1.Del:ehp1.. You should be aware that the association deleted is
 the one matching the entry fields, specifically the mask, signature
 and offset fields.
 …
 :p.
 The :hp1.Find:ehp1. button brings up a standard OS/2 open dialog that
 you can use to point-and-click at the desired executable file.  It's
+you can use to point-and-click at the desired executable file. It's
 pathname will be entered into the command line entry field.
 :p.
 The :hp1.Close:ehp1. checkbox will cause FM/2 to close after executing
 this association.  Please be sure that's the behavior you really want
+this association. Please be sure that's the behavior you really want
 before checking this button.
 :p.
 The :hp1.Environment:ehp1. MLE control lets you enter environment strings
 for the program to inherit.  Generally speaking, this is only for running
+for the program to inherit. Generally speaking, this is only for running
 DOS programs as any strings entered here are interpreted as DOS settings.
 For example, :hp3.IDLE_SECONDS=5:ehp3. would adjust the DOS setting
 IDLE_SECONDS to 5.  Names of DOS settings are as shown in the Settings
+IDLE_SECONDS to 5. Names of DOS settings are as shown in the Settings
 notebook for a DOS program.
 :p.
 …
 :i1 id=aboutWhyAssociations.Why separate Associations?
 Under OS/2's WPS you can set up associations so that double-clicking a
 datafile object invokes a program.  Usually you would use this to start
+datafile object invokes a program. Usually you would use this to start
 the program that edits the file; for example, if you double-clicked a
 graphics file you'd want your graphics editing program to be started.
 …
 However, while using a file manager, you would probably prefer to have
 a simple viewer started to look at the file quickly so you can decide
 what to do with the file.  Therefore, FM/2 allows you to set up
+what to do with the file. Therefore, FM/2 allows you to set up
 Associations for files that are different than those that OS/2 uses.
 This lets you invoke viewers in FM/2 via double-click, but invoke
 editors in OS/2 via double-click.
 :p.
 Moreover, FM/2's Associations can be a bit smarter than OS/2's.  You can
+Moreover, FM/2's Associations can be a bit smarter than OS/2's. You can
 associate a signature with a filemask and only files that match both
 will be viewed with the associated executable.  You can even use these
+will be viewed with the associated executable. You can even use these
 signatures to invoke OS/2's own associations, providing added assurance
 that the right executable is being invoked.  For example, if you have
+that the right executable is being invoked. For example, if you have
 a plain text file with the extension ".INF," OS/2 would try to view it
 with VIEW.EXE, which wouldn't know what to do with it.  If you make an
+with VIEW.EXE, which wouldn't know what to do with it. If you make an
 FM/2 Association and give "HSP" as the signature at offset 0 of the file,
 only OS/2 INFs will be passed to VIEW.EXE.
 …
 You can access OS/2's associations for a file system object at any time
 by pressing the F6 key or holding down Ctrl while double-clicking the
 object.  This causes a default WPS open to be performed on the object.
+object. This causes a default WPS open to be performed on the object.
 :p.
 If you want to access OS/2's associations by an unaugmented double-click,
 enter "<>" as the executable in the FM/2 Association definition.  This
 causes FM/2 to do a default WPS open on the object.  Note that if you
+enter "<>" as the executable in the FM/2 Association definition. This
+causes FM/2 to do a default WPS open on the object. Note that if you
 wanted :hp2.all:ehp2. objects to use OS/2's associations, you'd need only
 one FM/2 Assocation (filemask "*", executable "<>").
+one FM/2 Association (filemask "*", executable "<>").

trunk/dll/ipf/attribs.ipf

-              r10
+              r268
 :i1 id=aboutAttribsList.Attributes
 :artwork name='..\..\bitmaps\attrlist.bmp' align=center.
+This dialog allows you to set the attributes and (optionally) date and
+time of all objects in a selected group from one popup dialog.  The
+:p.
+This dialog allows you to set the attributes and/or date and
+time of all objects in a selected group from one popup dialog. The
 dialog presents you with spinboxes to change the date and time (defaults
 to current time and date) and checkboxes to set the attributes
 (ReadOnly, System, Hidden and Archived).  You can also modify the
+(ReadOnly, System, Hidden and Archived). You can also modify the
 selected list of objects by pushing the :hp1.Select:ehp1. button. If you
 only want to change the objects' attributes and not their date and time,
 …
 The initial state of the checkboxes and date/time spinbuttons has no
 relationship to the actual state of the objects being manipulated if
 more than one object was selected and acted upon by the command.  This
+more than one object was selected and acted upon by the command. This
 command affects all selected objects at once.
 :p.
 The attribute checkboxes are "3-state" checkboxes.  This type of checkbox
+The attribute checkboxes are "3-state" checkboxes. This type of checkbox
 can have three different meanings:  reset attribute (cleared box), set
 attribute (checked box), or ignore attribute (greyed box, "indeterminate
+attribute (checked box), or ignore attribute (grayed box, "indeterminate
 state," meaning leave this attribute unchanged).
+:p.
 :artwork name='bitmaps\3state.bmp' align=center.
+:p.
 Note that checking the :hp1.Use Date/Time checkbox:ehp1., setting the
 date/time to the current date/time, and leaving the attribute checkboxes
 greyed results in a "touch" of the file system objects selected for the
+grayed results in a "touch" of the file system objects selected for the
 command (works like the *nix Touch command -- if you don't know what
 that is, don't worry too much).  You can use the :hp1.Leave all
 attrs:ehp1. button to grey all the attribute checkboxes at once.  If
 all attribute checkboxes are already greyed, clicking this button causes
+that is, don't worry too much). You can use the :hp1.Leave all
+attrs:ehp1. button to gray all the attribute checkboxes at once. If
+all attribute checkboxes are already grayed, clicking this button causes
 the attributes and date/time of the first item in the listbox to be
 assigned to the controls of the dialog.

trunk/dll/ipf/chklist.ipf

-              r2
+              r268
 :h1 res=95600 name=PANEL_CHECKLIST.Checking Lists
 :i1 id=aboutCheckList.Checking Lists
 On occasion you may be asked to check a list of objects.  You'll be
 presented with a list of highlighted objects in a listbox.  To remove an
 object from the list, unhighlight it (:hp6.hint:ehp6.&colon.  hold down
 the Ctrl key while clicking to unhighlight a single item).  When you've
 got the list the way you want it, click Okay.  Click Cancel to abort the
+On occasion you may be asked to check a list of objects. You'll be
+presented with a list of highlighted objects in a listbox. To remove an
+object from the list, unhighlight it (:hp6.hint:ehp6.&colon. hold down
+the Ctrl key while clicking to unhighlight a single item). When you've
+got the list the way you want it, click Okay. Click Cancel to abort the
 action.
 :p.
 …
 when you drop files onto an FM/2 Directory Container or object within
 one, or onto a directory object in the Drive Tree, or onto an object in
 the Collector.  You can then pick the action to be performed from the
 buttons below the listbox.  You can remove an object from the listbox if
+the Collector. You can then pick the action to be performed from the
+buttons below the listbox. You can remove an object from the listbox if
 you've changed your mind about including it in the action (hint: hold
 down the Ctrl key while clicking to unhighlight a single item).
 …
 :p.
 The :hp1.Shadow:ehp1. toggle causes :hp1.Object:ehp1. to create Shadow
 objects instead of "real" objects.  Directory objects are always created
+objects instead of "real" objects. Directory objects are always created
 as Shadow objects.
 :p.
 Note that creating Shadows in directories not under the Desktop folder
 probably isn't desireable.
+probably isn't desirable.
 :p.
 The :hp1.Launch:ehp1. button causes FM/2 to bring up the Execute dialog

trunk/dll/ipf/cmdline.ipf

-              r2
+              r268
 :i1 id=aboutCmdline.Editing Commandline
 Enter any optional arguments to the program here as you would on the
 command line.  Remember that, when passing commands to a command
+command line. Remember that, when passing commands to a command
 processor such as CMD.EXE, like DIR, it's CMD.EXE /C DIR, not just
 CMD.EXE DIR.
 :p.
 :hp1.Full Screen, Maximized, Minimized, Invisible, Default&colon.:ehp1.
 control how the program will be run.  Default is usually in a window
 with OS/2 controlling the size of the initial window.  Note that PM
+control how the program will be run. Default is usually in a window
+with OS/2 controlling the size of the initial window. Note that PM
 programs will always run on the desktop in a window and programs marked
 full screen only will always run in a full screen session.  This
+full screen only will always run in a full screen session. This
 corresponds to START /FS, /MAX, /MIN, /I or just START.
 :p.
 :hp1.Keep when done&colon.:ehp1.  determines whether the window will
 remain until you close it, or go away when the command completes.  It's
 like START /K.  For reasons of safety (too complex to explain briefly)
+:hp1.Keep when done&colon.:ehp1. determines whether the window will
+remain until you close it, or go away when the command completes. It's
+like START /K. For reasons of safety (too complex to explain briefly)
 you aren't allowed to Keep a DOS session; this flag is ignored for DOS
 executables.
 :p.
 The :hp1.Environment:ehp1. MLE control lets you enter environment strings
 for the program to inherit.  Generally speaking, this is only for running
+for the program to inherit. Generally speaking, this is only for running
 DOS programs as any strings entered here are interpreted as DOS settings.
 For example, :hp3.IDLE_SECONDS=5:ehp3. would adjust the DOS setting
 IDLE_SECONDS to 5.  Names of DOS settings are as shown in the Settings
+IDLE_SECONDS to 5. Names of DOS settings are as shown in the Settings
 notebook for a DOS program.
 :p.
 Note&colon.  FM/2 automatically stores command lines you use here for
 you if the :hp1.Save command line:ehp1. checkbox is checked.  You can
+Note&colon. FM/2 automatically stores command lines you use here for
+you if the :hp1.Save command line:ehp1. checkbox is checked. You can
 get to them by clicking the :hp1.V:ehp1. button beside the entry field.
 Up to 250 command lines can be stored in this manner, kept in a file
 named CMDLINES.DAT between sessions.  Pressing the :hp1.Delete:ehp1. key
+named CMDLINES.DAT between sessions. Pressing the :hp1.Delete:ehp1. key
 (or clicking the :hp1.Del:ehp1. button that appears) while one of the
 names in the listbox is highlighted will remove it. Pressing :hp1.Ctrl +
 Delete:ehp1. will remove (wipe) all entries.
 :p.
 Tech note&colon.  FM/2 picks the directory in which to start the process
+Tech note&colon. FM/2 picks the directory in which to start the process
 using the following criteria&colon.
 .br

trunk/dll/ipf/collect.ipf

-              r10
+              r268
 :i1 id=aboutCollector.Collector
 :artwork name='..\..\bitmaps\collect.bmp' align=center.
+:p.
 The :hp1.Collector:ehp1. is a temporary place to hold objects that you
 want to manipulate later; it allows you to temporarily group objects
 regardless of where they're physically stored in the file system.  No
+regardless of where they're physically stored in the file system. No
 physical (disk) storage is used; the Collector just holds the objects
 (something like WPS shadows) until you're ready to do something with
 them.  You might think of it as an additional clipboard containing names
 of file system objects.  Note that objects in the Collector, unlike
+them. You might think of it as an additional clipboard containing names
+of file system objects. Note that objects in the Collector, unlike
 objects in main tree and directory containers, show their full
 pathnames.
 :p.
 You can drag file system objects from and to the Collector.  Be careful
+You can drag file system objects from and to the Collector. Be careful
 where you drop the objects; directories and files already in the
 Collector are "targets." If you drop on a directory, the files are moved
 …
 :p.
 The Collector allows you to manipulate the files it contains just as you
 would in a main tree or directory window.  Popup menus are available
 just as they are in a main window.  The popup for the collector
 container obtained over container whitespace allows clearing the
+would in a main tree or directory window. Context menus are available
+just as they are in a main window. The context menu for the collector
+container obtained by clicking mouse B2 over container whitespace allows clearing the
 container, collecting files from the clipboard (a good way to import a
 selection from some other program that might save a list of files, one
 …
 :p.
 Additionally, the pulldown menu gives you access to a :link reftype=hd
 res=91600.Seek and scan:elink. function.  This leads to a dialog that
+res=91600.Seek and scan:elink. function. This leads to a dialog that
 lets you search for and Collect files based on filemasks and text
 content.
 :h3 res=91600 name=PANEL_GREP.Seek and scan
+:h2 res=91600 name=PANEL_GREP.Seek and scan
 :i1 id=aboutGrep.Seek and scan
 :i1 id=aboutGrepDupe.Find duplicate files
 This dialog, accessed from a Collector context menu, allows you to
+This dialog, accessed from the Utilities menu or a Collector context menu, allows you to
 search for files (by filemasks and, optionally, text within the files)
 and :link reftype=hd res=90100.Collects:elink. the files found.
 …
 :p.
 In the :hp6.Filemasks:ehp6. entry field you can enter one or several
 filemasks.  To enter multiple masks, separate them with semi-colons.
 Entries can total up to 8095 bytes in length.  You can use exclusion
+filemasks. To enter multiple masks, separate them with semi-colons.
+Entries can total up to 8095 bytes in length. You can use exclusion
 masks as well by prefacing that portion of the mask with a forward slash
 (/), which can be used to speed up the search by excluding paths or
 filemasks that you are not interested in finding.  Example&colon.
+filemasks that you are not interested in finding. Example&colon.
 "C&colon.\*;/C&colon.\OS2\*;/C&colon.\DESKTOP;D&colon.\*;/*.DLL".
 :p.
 The :hp6.Add:ehp6. and :hp6.Delete:ehp6. buttons can be used to add the
 current filemask to the listbox for later retrieval or delete a line
 from the listbox if you want to get rid of it.  The :hp6.Append:ehp6.
+from the listbox if you want to get rid of it. The :hp6.Append:ehp6.
 checkbox allows you to control whether selected masks replace what is
 in the Filemasks entry field, or are appended to the current contents.
 …
 :p.
 The :hp6.Walk:ehp6. button brings up the :link reftype=hd res=91500.Walk
 Directories:elink. dialog.  When you select a directory in the dialog
+Directories:elink. dialog. When you select a directory in the dialog
 it's added to the Filemasks entry field.
 :p.
 …
 :p.
 In the :hp6.Search text:ehp6. MLE you can enter text that must be found
 for the file to match.  All files matching the filemask(s) are searched
 for this text.  If no text is entered, a simple file find is performed.
 Note that each line of the MLE is a separate search string.  If any of
 the strings are found, FM/2 will consider a match to be made.  You can
+for the file to match. All files matching the filemask(s) are searched
+for this text. If no text is entered, a simple file find is performed.
+Note that each line of the MLE is a separate search string. If any of
+the strings are found, FM/2 will consider a match to be made. You can
 enter up to 4096 characters in this MLE, and as many lines as you like
 within that limitation.  Note that a "line break," for our purposes
+within that limitation. Note that a "line break," for our purposes
 here, is created when you press [Enter] in the MLE; word wrap is not
 a consideration.
 :p.
 Simple regular expressions are supported.  These can be briefly
+Simple regular expressions are supported. These can be briefly
 summarized&colon.
 :parml compact tsize=11 break=none.
 …
 :p.
 The :hp6.Include Subdirs:ehp6. checkbox controls whether the search
 extends into subdirectories.  If the box is checked, subdirectories are
+extends into subdirectories. If the box is checked, subdirectories are
 searched.
 :p.
 …
 :hp6.Search text:ehp6. entry field.
 :p.
 The :hp6.Case Senseitive:ehp6. checkbox, if checked, makes text searches
 case sensitive.  Otherwise they are not ('c' matches 'C' and 'c').
+The :hp6.Case Sensitive:ehp6. checkbox, if checked, makes text searches
+case sensitive. Otherwise they are not ('c' matches 'C' and 'c').
 :p.
 The :hp6.Say files as found:ehp6. checkbox tells FM/2 to display the
 …
 :p.
 The :hp6.Search files:ehp6. checkbox, when checked, tells FM/2 to look
 inside files for the text in the Search text entry field.  This has no
+inside files for the text in the Search text entry field. This has no
 effect if no search text was entered.
 :p.
 The :hp6.Search EAs:ehp6. checkbox, when checked, tells FM/2 to look at
 the text EAs of files for the text in the Search text entry field.  This
+the text EAs of files for the text in the Search text entry field. This
 has no effect if no search text was entered.
 :p.
 The :hp6.Find duplicates:ehp6. checkbox, when checked, tells FM/2 to
 find :hp2.potential:ehp2. duplicate files.  Files with the same name are
+find :hp2.potential:ehp2. duplicate files. Files with the same name are
 found, as are files with the same size and date/time.
 :hp9.Note&colon.:ehp9. Finding duplicates is a time and resource
 consuming operation due to the usually large number of files, and
 therefore comparisons, involved (FM/2 on a 486/66DX2 with 32 mb RAM
 required about 7 minutes to search 11,000 files for dupes).  Once
+therefore comparisons, involved (FM/2 on a P3/500 with 256 mb RAM
+required about 4 minutes to search 12,000 files for dupes). Once
 potential dupe files have been found and Collected you can use the
 Collector's sort and information facilities and commands to check the
 …
 :p.
 The :hp6.CRC dupes:ehp6. checkbox, when checked, causes FM/2 to
 determine and check the CRCs of potential duplicate files.  Only files
+determine and check the CRCs of potential duplicate files. Only files
 with matching CRCs will then pass the dupe test begun as described
 above.  This approximately doubles the time it takes to find potential
+above. This approximately doubles the time it takes to find potential
 duplicate files, depending on how many potential dupes there are, but
 not using it means that invariably a few files will be flagged as
 possible dupes that aren't (this is possible even with this switch on,
 but far less likely).  Note that in order to CRC a file, FM/2 must be
+but far less likely). Note that in order to CRC a file, FM/2 must be
 able to open it -- if it can't, FM/2 will consider the two files being
 compared to be duplicates.
 …
 The :hp6.No size dupes:ehp6. checkbox, when checked, tells FM/2 to not
 consider files as potential dupes unless their names match (size/date
 matches aren't considered).  Be aware that you will probably miss true
+matches aren't considered). Be aware that you will probably miss true
 duplicate files if you turn this off, as not all dupes have the same
 name.
 …
 The :hp6.Ignore extensions:ehp6. checkbox, when checked, tells FM/2 to
 ignore the (last) extension on filenames when checking for dupes by
 name.  This is handy when you're comparing files in BBS upload
+name. This is handy when you're comparing files in BBS upload
 directories where the same file may have been archived with different
 archivers, resulting in identical rootnames but different extensions.
 :p.
 The :hp6.Larger:ehp6. entry field can be used to find files larger than
 the number of bytes input (zero means all files).  The :hp6.k:ehp6.
+the number of bytes input (zero means all files). The :hp6.k:ehp6.
 button next to the entry field multiplies the value by 1024 for you to
 make kilobytes instead of bytes.  The :hp6.Smaller:ehp6. entry field
+make kilobytes instead of bytes. The :hp6.Smaller:ehp6. entry field
 works the same except that it causes files smaller than the number of
 bytes input to be found.  When used together (both fields are nonzero),
+bytes input to be found. When used together (both fields are nonzero),
 files found will be greater than the Larger field's value or less than
 the Smaller field's value.
 …
 The :hp6.Newer:ehp6. and :hp6.Older:ehp6. entry fields work similarly.
 When non-zero, these fields cause the search to find only files newer
 or older than the number of days entered.  The :hp6.m:ehp6. buttons
+or older than the number of days entered. The :hp6.m:ehp6. buttons
 multiply the value by 30 for you to make "months" instead of days.
 :p.
 The :hp6.AllHDs:ehp6. button prompts you for a single simple filemask
 (one without a drive or path) then builds a :hp6.Filemasks:ehp6. string
 that will search all hard drives for that mask.  Similarly, the
+that will search all hard drives for that mask. Similarly, the
 :hp6.LocalHDs:ehp6. builds a mask for all local hard drives, and
 :hp6.RemoteHDs:ehp6. builds a mask for all remote (LAN) hard drives.
 :p.
 The listbox on the left top of the dialog contains a list of valid
 drives.  You can double-click one of these drives to add a mask for
+drives. You can double-click one of these drives to add a mask for
 that drive to the entry field.
 :p.
 …
 :p.
 Click :hp6.Okay:ehp6. when ready to search, or :hp6.Cancel:ehp6. to exit
 without searching.  Note that this function is designed to run in the
+without searching. Note that this function is designed to run in the
 background while you're doing other work, rather than running full-tilt
 and making you wait for it.
 :p.
 :hp9.Quicky instructions for file finding:ehp9.&colon.  type a mask into
+:hp9.Quicky instructions for file finding:ehp9.&colon. type a mask into
 the :hp6.Filemasks:ehp6. entry field (for example, "C&colon.\*.BAK") and
 press [Enter].
 :p.
 :hp9.Quicky instructions for dupe finding:ehp9.&colon.  type a mask into
+:hp9.Quicky instructions for dupe finding:ehp9.&colon. type a mask into
 the :hp6.Filemasks:ehp6. entry field, check :hp6.Find Duplicates:ehp6.,
 check :hp6.CRC dupes:ehp6. if you want greater accuracy (and more time
 …
 See also :link reftype=hd res=98500.See all files:elink..
 :h4 res=100050 name=PANEL_ENV.Enter environment variable name
+:h3 res=100050 name=PANEL_ENV.Enter environment variable name
 :i1 id=aboutEnterEnvironment.Enter environment variable name
 This dialog, reached from the :link reftype=hd res=91600.Seek and Scan
 files dialog:elink., allows you to enter or select the name of an
 enviroment variable (like PATH, LIBPATH, DPATH, etc.) that points to a
 list of directories separated by semi-colons.  The Seek and Scan dialog
+environment variable (like PATH, LIBPATH, DPATH, etc.) that points to a
+list of directories separated by semi-colons. The Seek and Scan dialog
 will then build the filemask for you from that list of directories.
 :p.
 Some of the most frequently encountered environment variable names are
 displayed in the listbox.  If you select one, its name is placed in the
 entry field for you.  You can also type in a name.  Click :hp1.Okay:ehp1.
+displayed in the listbox. If you select one, its name is placed in the
+entry field for you. You can also type in a name. Click :hp1.Okay:ehp1.
 when you have entered the desired name, or click :hp1.Cancel:ehp1. if
 you changed your mind and don't wish to use an environment variable
 name.
 :h3 res=98500 name=PANEL_SEEALL.See all files
+:h2 res=98500 name=PANEL_SEEALL.See all files
 :i1 id=aboutSeeAllFiles.See all files
 FM/2 can present a window listing all the files on one or more drives.
 This command is part of the :link reftype=hd res=90100.Collector:elink.,
+and can be accessed from the Collector's context menu.  There's also a
+shortcut command under the :link reftype=hd res=92100.Utilities:elink.
+submenu on the main FM/2 window.  Selecting :hp1.Miscellaneous->Show all
+files:ehp1. (Ctrl + S) from a Drive Tree directory's context menu can
+also get you here.
+:p.
+After you select the drives to list from a dialog, FM/2 will scan the
+selected drives and then fill a custom list control with the names of
+and can be accessed from the Utilities menu or the Collector's context menu.
+Selecting :hp1.Miscellaneous->Show allfiles:ehp1. (Ctrl + S) from a Drive
+Tree directory's context menu will also get you here.
+:p.
+After you select the drives to scan from a dialog, FM/2 will scan the
+selected drives and then fill a custom control list with the names of
 all the files found.
 :p.
 Once the filenames are displayed, together with their sizes, attributes
 and last written dates and times, you can perform a variety of actions
 with selected files from the list.  Commands exist to sort the listing
+with selected files from the list. Commands exist to sort the list
 in several ways and to filter and select files in several ways.
 :p.
 You can also drag selected files from the list.
 :p.
 You can use the Filter to pare a listing down to a smaller subset.  For
+You can use the Filter to pare a list down to a smaller subset. For
 example, if you are viewing all the files on the C&colon. drive, you can
 limit the view to all the files in C&colon.\OS2 and subdirectories with
+limit the view to all the files in C&colon.\OS2 and its subdirectories with
 the filter "C&colon.\OS2\*".
 :p.
 FM/2 displays Hidden and System files in red, Readonly files in blue,
 and all others in black on a light grey background.  Selected files are
 displayed in reverse video (white text on a black background).  These
 colors are configurable.  The current file has a ">" pointing at it in
 the left margin.  Single selections and swipe selections are supported,
+and all others in black on a light gray background. Selected files are
+displayed in reverse video (white text on a black background). These
+colors are configurable. The current file has a ">" pointing at it in
+the left margin. Single selections and swipe selections are supported,
 as well as select and deselect all, and select and deselect based on
 masks and/or attributes.
 …
 You can press the first letter of a file (as displayed; if fullnames are
 on, you must type the first letter of the full filename, including path)
 to "find" a file that begins with that letter.  In fact, in this window,
+to "find" a file that begins with that letter. In fact, in this window,
 you can type more than one letter of a filename (each within one, count
 'em, one, second of the previous) to narrow the search further -- something
 …
 :p.
 Double-clicking a file results in a default action as in Directory
 Containers (usually a view of the file).  If you need a refresher, check
 the :link reftype=hd res=90000.General Help:elink. topic.  The keyboard
+Containers (usually a view of the file). If you need a refresher, check
+the :link reftype=hd res=90000.General Help:elink. topic. The keyboard
 equivalent is the Enter key.
 :p.
 A large subset of the commands available in Directory Containers is
 available in this window.  See the :link reftype=hd res=93700.Context
 menus:elink. topic for more information.  Commands in this window
+available in this window. See the :link reftype=hd res=93700.Context
+menus:elink. topic for more information. Commands in this window
 always apply to selected files.
 :p.
 …
 and preserve...:ehp6. and :hp6.Move and preserve...:ehp6.. These
 commands copy or move the selected files but preserve the directory
 relationship of the files.  The effect of this can be non-obvious, so
+relationship of the files. The effect of this can be non-obvious, so
 use with care.
 :p.
 Let's say you select three files&colon. G&colon.\FOO\BAR\DUDE,
 G&colon.\FOO\BAR\WOW\DUDE and G&colon.\FOO\BAR\RUFF\DUDE.  If you select
+G&colon.\FOO\BAR\WOW\DUDE and G&colon.\FOO\BAR\RUFF\DUDE. If you select
 :hp1.Copy and preserve:ehp1. and pick a destination directory of
 H&colon.\HERE, the resultant files will be H&colon.\HERE\DUDE,
 …
 :p.
 The :hp6.Duplicates...:ehp6. command can be used to find files that are
 potential duplicates in the window.  There are several options that you
+potential duplicates in the window. There are several options that you
 can select in the :link reftype=hd res=100035.dialog:elink. that
 appears. Duplicate finding can take a considerable amount of time, but
 you can continue to do things in other windows while you wait.
 :p.
 See also&colon.  :link reftype=hd res=91600.Seek and Scan:elink.
 :h4 res=98600 name=PANEL_DRVSWND.Pick drives
 Highlight the drive(s) to list, then click Okay.  Click Cancel to abort.
+See also&colon. :link reftype=hd res=91600.Seek and Scan:elink.
+:h3 res=98600 name=PANEL_DRVSWND.Pick drives
+Highlight the drive(s) to list, then click Okay. Click Cancel to abort.
 :p.
 FM/2 will quickly load all the files on the selected drives into an ugly
 but fast custom list control for you to further examine and manipulate.
+but fast custom control list for you to further examine and manipulate.
 :p.
 The custom control is used rather than a container due to the slowness
 of containers when dealing with such large numbers of records.  You can
+of containers when dealing with such large numbers of records. You can
 verify this by using :link reftype=hd res=91600.Seek and scan:elink. to
 Collect the same files into the Collector container, if you're a
 masochist.
 :h4 res=100035 name=PANEL_DUPES.Duplicate finding options
 Select from the options for finding duplicate files.  Files must meet
+:h3 res=100035 name=PANEL_DUPES.Duplicate finding options
+Select from the options for finding duplicate files. Files must meet
 :hp1.all:ehp1. selected criteria to be considered duplicates (dupes).
 Therefore, the more options you check, the more likely the files you're
 …
 files.
 :p.
 Note that CRCing files can take considerable time.  Only files that
+Note that CRCing files can take considerable time. Only files that
 match all other criteria will be CRCed, and files will only be CRCed
 once (i.e. the logic's not :hp1.totally:ehp1. stupid), but it will take
 longer.  FM/2 will display some info about where it is during the dupe
+longer. FM/2 will display some info about where it is during the dupe
 check, and checking is done in a background thread at a low priority so
 that other windows and applications remain useable.  FM/2 must be able
+that other windows and applications remain usable. FM/2 must be able
 to open the file for reading to CRC it -- if it cannot do so, it will
 consider the file a match based on the other criteria specified.
 :p.
 After finding duplicate files, you can "restore" the rest of the files
 by using the :hp6.Filter:ehp6. command.  It often helps to set the
+by using the :hp6.Filter:ehp6. command. It often helps to set the
 Sort to Name or Size when viewing files found as potential duplicates
 to best see their relationships.

trunk/dll/ipf/command.ipf

-              r10
+              r268
 :i1 id=aboutCommands.Editing Commands
 :artwork name='..\..\bitmaps\command.bmp' align=center.
+:p.
 This dialog allows you to edit the commands that are available in the
 Commands submenu.  There is always a :hp1.Do it yourself:ehp1. command
+Commands submenu. There is always a :hp1.Do it yourself:ehp1. command
 in the Commands submenu, and it is the default for the conditional
 cascade. The Do it yourself command supplies the names of selected files
 as the command line and allows you to enter a command to be performed on
 the files in an entry field.  Note that OS/2 command lines are limited
+the files in an entry field. Note that OS/2 command lines are limited
 to 1,000 characters.
 :p.
 …
 :p.
 To delete a command, select it in the listbox, then click
 :hp1.Del:ehp1..  You should be aware that the command deleted
+:hp1.Del:ehp1.. You should be aware that the command deleted
 is the one matching the entry field, specifically, the title field.
 :p.
 …
 :p.
 The :hp1.Find:ehp1. button brings up a standard OS/2 open dialog that
 you can use to point-and-click at the desired executable file.  It's
+you can use to point-and-click at the desired executable file. It's
 pathname will be entered into the command line entry field.
 :p.
 The :hp1.Environment:ehp1. MLE control lets you enter environment
 strings for the program to inherit.  Generally speaking, this is only
+strings for the program to inherit. Generally speaking, this is only
 for running DOS programs where any strings entered here are interpreted
 as DOS settings. For example, :hp3.IDLE_SECONDS=5:ehp3. would adjust the
 DOS setting IDLE_SECONDS to 5.  Names of DOS settings are as shown in
+DOS setting IDLE_SECONDS to 5. Names of DOS settings are as shown in
 the Settings notebook for a DOS program.
 :p.
 …
 :i1 id=aboutReorderingCommands.Reordering Commands
 This dialog, accessed from the Edit Commands dialog, allows you to
 rearrange the order of Commands.  You take selected items from the left
+rearrange the order of Commands. You take selected items from the left
 listbox and Add them to the end of the right listbox with the
 :hp1.Add>>:ehp1. button. When you've moved everything to the right
 listbox, click :hp1.Okay:ehp1..  Click :hp1.Cancel:ehp1. if you change
+listbox, click :hp1.Okay:ehp1.. Click :hp1.Cancel:ehp1. if you change
 your mind.
 :p.
 In reality, you don't need to move everything to the right listbox.  You
+In reality, you don't need to move everything to the right listbox. You
 can move only what you want moved to the top of the list, then click
 Okay.  Anything remaining in the left listbox is added to the end of
+Okay. Anything remaining in the left listbox is added to the end of
 what's in the right listbox.
 :p.
 …
 :pd.listfile name (first places full filenames in a list file; user
 Command should delete listfile when complete, but FM/2 will clean any
 left over up when FM/2 closes).  This is an advanced command -- see
+left over up when FM/2 closes). This is an advanced command -- see
 EXAMPLE.CMD in the FM/2 distribution archive for a skeleton program that
 you can use to do work on the filenames listed in the listfile.  You can
+you can use to do work on the filenames listed in the listfile. You can
 use %! more than once in the same command line -- the listfile will only
 be built once, but the name of that listfile will be inserted each time.
 …
 :p.
 When you enter a metastring into a command line, the metastring is
 replaced with the appropriate text.  For example, "%c /C MYCMD.CMD %a"
+replaced with the appropriate text. For example, "%c /C MYCMD.CMD %a"
 might become "CMD.EXE /C MYCMD.CMD d&colon.\file1 d&colon.\file2
 d&colon.\file3".

trunk/dll/ipf/comp.ipf

-              r10
+              r268
 :artwork name='..\..\bitmaps\linkdrag.bmp' align=center.
+:p.
 The :hp1.Compare Directories:ehp1. dialog shows you a comparison
 breakdown of two directories.  You can highlight files here and
+breakdown of two directories. You can highlight files here and
 :link reftype=hd res=90100.Collect:elink. them for later processing,
 or drag them elsewhere.
 :p.
 The dialog presents two containers side-by-side.  Vertical scrolling of
 the containers is synched so that scrolling one scrolls both.  The files
+The dialog presents two containers side-by-side. Vertical scrolling of
+the containers is synced so that scrolling one scrolls both. The files
 are listed so that they are in alphabetical order, with gaps in the
 containers where a file exists in one but not the other.  This provides
+containers where a file exists in one but not the other. This provides
 easy, at-a-glance comparison of the directories' contents.
 :p.
 It is possible to change the directory of a container by direct editing
 of the container title.  You can change both directories simultaneously
 by clicking the :hp6.Dirs:ehp6. button.  You can include all the files
+of the container title. You can change both directories simultaneously
+by clicking the :hp6.Dirs:ehp6. button. You can include all the files
 in all subdirectories by checking the :hp6.Include subdirs:ehp6. button.
 :p.
 …
 Snapshots can be used to see what changed in a directory from one point
 in time to another (for instance, to see what installing a program might
 have changed in your system directories).  You can also
+have changed in your system directories). You can also
 :hp1.Filter:ehp1. what shows in the containers.
 :p.
 The line of :hp1.Actions&colon.:ehp1. pushbuttons allow you to
+The row of :hp1.Actions&colon.:ehp1. pushbuttons allow you to
 :hp6.Delete:ehp6. files from either directory and to :hp6.Move:ehp6. or
 :hp6.Copy:ehp6. files from one directory to another.  You can
+:hp6.Copy:ehp6. files from one directory to another. You can
 double-click a file to view it, or request a context menu on it to
 compare it to its counterpart in the other directory.
 …
 Several selection/deselection techniques are available via pushbuttons
 to enable you to select files based on their comparison. The pushbuttons
 operate on both containers.  You can also select and deselect files in
+operate on both containers. You can also select and deselect files in
 the containers manually with the mouse and/or keyboard.
 :hp2.Hint&colon.:ehp2.  mouse selection works slightly differently when
+:hp2.Hint&colon.:ehp2. mouse selection works slightly differently when
 you hold down the Ctrl key while clicking.
 :p.
 :hp2.Brief description of selection/deselection button options&colon.:ehp2.
 :p.
 :hp6.Same:ehp6.  All items which match name and size exactly.
+:hp6.Same:ehp6. All items which match name and size exactly.
 :p.
 :hp6.Identical:ehp6.  All items which match name, size and date exactly.
+:hp6.Identical:ehp6. All items which match name, size and date exactly.
 :p.
 :hp6.Both:ehp6.  All items which are present in both containers (only
+:hp6.Both:ehp6. All items which are present in both containers (only
 name used as criteria).
 :p.
 :hp6.One:ehp6.  All items which are present in only one of the
+:hp6.One:ehp6. All items which are present in only one of the
 containers (only name used as criteria).
 :p.
 :hp6.Newer:ehp6.  All items which have a counterpart in the other
+:hp6.Newer:ehp6. All items which have a counterpart in the other
 container and are the newer of the pair.
 :p.
 :hp6.Older:ehp6.  All items which have a counterpart in the other
+:hp6.Older:ehp6. All items which have a counterpart in the other
 container and are the older of the pair.
 :p.
 :hp6.Smaller:ehp6.  All items which have a counterpart in the other
+:hp6.Smaller:ehp6. All items which have a counterpart in the other
 container and are the smaller of the pair.
 :p.
 :hp6.Larger:ehp6.  All items which have a counterpart in the other
+:hp6.Larger:ehp6. All items which have a counterpart in the other
 container and are the larger of the pair.
 :p.
 :hp6.All:ehp6.  All items in both containers.
+:hp6.All:ehp6. All items in both containers.
 :p.
 :hp6.Invert:ehp6.  Inverts selection state of all items in both containers.
+:hp6.Invert:ehp6. Inverts selection state of all items in both containers.
 :p.
 See also :link reftype=hd res=99100.Selection:elink..
 …
 that have no matching files in the other directory (click the
 :hp1.One:ehp1. button on the left side of the dialog). Copy these files
 to the other directory.  Now deselect all files (click the
+to the other directory. Now deselect all files (click the
 :hp1.All:ehp1. button on the right side of the dialog) and select all
 newer files (click the :hp1.Newer:ehp1. button on the left side of the
 dialog).  Copy these files to the other directory.  The directories
+dialog). Copy these files to the other directory. The directories
 should now match exactly -- deselect all files and select identical
 files (click the :hp1.Identical:ehp1. button), and all the files should
 be selected (to confirm).
 :p.
+If you're looking for more powerful directory matching software, you
+might be interested in Larry Waibel's :hp1.PMDirMatch:ehp1. shareware
+program.  Larry can be contacted on Compuserve at user ID 71333,2463,
+and he hangs out in the OS2SHARE (library 1 of OS2BVEN) forum. You can
+easily set FM/2 up to use PMDirMatch automatically using the :link
+reftype=hd res=98400.Compare page:elink. of the internal Settings
+notebook.
+If you're looking directory matching features not included in FM/2, you
+might find them in the programs available on Hobbes
+http&colon.//hobbes.nmsu.edu/cgi-bin/h-search?key=directory+compare&amp.pushbutton=Search
+You can easily setup FM/2 to use one of these programs automatically using the :link
+reftype=hd res=98400.Compare page:elink. of the internal Settings notebook.
 :h3 res=91550 name=PANEL_WALKEM2.Select two directories
 …
 This dialog lets you pick two directories by "walking" through the
 directory structure of your drives.  See also :link reftype=hd
+directory structure of your drives. See also :link reftype=hd
 res=91500.Walk Directories:elink..
 :p.
 When the desired directories are displayed in the entry fields of
 the dialog, click :hp1.Okay:ehp1. to exit.  Click :hp1.Cancel:ehp1. to
+the dialog, click :hp1.Okay:ehp1. to exit. Click :hp1.Cancel:ehp1. to
 exit without selecting directories.

trunk/dll/ipf/config.ipf

-              r2
+              r268
 :p.
 FM/2 can be configured as you like it using the commands under this
 submenu.  It is highly recommended that you step through the items in
 this submenu when you first begin to use FM/2, both to familiarize
+menu. It is highly recommended that you experiment with the items in
+this menu when you first begin to use FM/2, both to familiarize
 yourself with the available configuration options and to make FM/2
 work the way you like it to work.
 :p.
+To change fonts and colors, FM/2 uses the WPS Font and Color Palettes.
+The Config menu contains commands to call up these objects for you.
+:p.
+This submenu affects general FM/2 behavior.  Each class of container has
+This menu affects general FM/2 behavior. Each class of container has
 its own configuration menu that allows you to set the type of view,
 filtering, and so on.  To get the popup menu that controls the
+filtering, and so on. To get the popup menu that controls the
 container's appearance, request a :link reftype=hd res=93700.context
 menu:elink. while the pointer is over an empty area of the container, or
 select the Views pulldown submenu.
 :p.
+The :hp6.:link reftype=hd res=99400.Toggle quicklists:elink.:ehp6.
+command causes a dropdown listbox to appear below the toolbar (if one is
+being used; below the pulldown menu, if one is being used, or titlebar
+if not) and above other windows.  The listbox contains the directory
+names you've assigned in the :link reftype=hd res=91500.Walk
+Directories:elink. dialog.  If you pick one, a Directory Container for
+that directory is opened (hold down the Shift key while clicking to
+change an existing Directory Container instead). If the dropdown listbox
+is already present, this command causes it to disappear.
+:p.
+A Drive Finder dropdown listbox also appears with the quicklist;
+selecting a drive in this list causes the Drive Tree container to scroll
+to show the selected drive and make it the current object.
+:p.
+Finally, a Setup dropdown list also appears that contains names of
+setups (Drive Tree location, Directory Container locations and
+associated directory names). Pick a setup name, and FM/2 reopens and
+repositions the windows as they were when you saved the setup.  A
+context menu requested on the setup list entry field is used to save and
+delete setup names.  To add a name, enter it in the entry field of the
+dropdown, request a context menu, and select :hp1.Save state as
+name:ehp1.  To delete a name, put it in the entry field, request a
+context menu and select :hp1.Delete state name:ehp1.
+:p.
+The :hp6.Autoview:ehp6. submenu controls the Autoview window.  The
+The :link reftype=hd res=94600.Settings notebook:elink. is accessed from
+this menu.
+:p.
+The :link reftype=hd res=100065.Set Target directory:elink. is the next menu
+item and can also be accessed using CTRL+T.
+:p.
+Five menu items to toggle various FM/2 functions on and off are next.
+The first two :link reftype=hd res=91800.Toolbar:elink. and :hp6.Autoview:ehp6.
+have submenus.
+:p.
+The:hp6.Toolbar:ehp6. submenu default is to toggle the toolbar on and off
+The other two items allow you to make the toolbar text only or you can
+add titles under the toolbar icons. Additional functions to edit the toolbar
+can be found on the context menu obtained by clicking B2 over a tool icon
+on the toolbar (see :link reftype=hd res=91800.Toolbar:elink. for more information)
+You can switch between toolbars using the dialog that appears if you click B2 over
+an area of "white space" on the toolbar or by selecting load toolbox from the previously
+discussed context menu.
+:p.
+The :hp6.Autoview:ehp6. submenu controls the Autoview window. The
 default for this conditional cascade menu is the :hp6.Toggle autoview
 window:ehp6. command, which causes an autoview window to appear above
 the status line at the bottom of the screen.  As you move the cursor
+the status line at the bottom of the screen. As you move the cursor
 from object to object, FM/2 displays the first few lines of file objects
 in this window.  If the autoview window is already displayed, clicking
 this command causes it to disappear.  You can also set the what is to
+in this window. If the autoview window is already displayed, clicking
+this command causes it to disappear. You can also set the what is to
 be autoviewed -- either the file's .COMMENTS EA or the start of the
 file's contents (similar to the *nix HEAD program).  When .COMMENTS EAs
+file's contents (similar to the *nix HEAD program). When .COMMENTS EAs
 are being viewed, you can edit them and the changes will be saved when
 you switch the focus from the Autoview window.  You can reach this
+you switch the focus from the Autoview window. You can reach this
 editable Autoview window with the Ctrl + Tab hotkey if you are allergic
 to your mouse.
 …
 Clicking the contents Autoview window with B1 causes the file to be
 viewed. Clicking with B3 (or chording with B1 and B2 simultaneously)
 causes the extended attributes to be viewed.  If viewing .COMMENTS
+causes the extended attributes to be viewed. If viewing .COMMENTS
 rather than contents, you can pick :hp1.View file:ehp1. from the
 context menu.
 :p.
+The :hp6.:link reftype=hd res=99400.Toggle quicklists:elink.:ehp6.
+command causes a set of dropdown listboxes to appear below the toolbar
+and above other windows. The listboxes include&colon.
+.br
+A Drive Finder dropdown listbox.
+,br
+A States dropdown listbox (Fm/2 configurations you have saved with specific name).
+.br
+A Commands dropdown listbox (External command that have been added to FM/2).
+.br
+A Directory dropdown listbox (Directory names you've assigned in the
+:link reftype=hd res=91500.Walk Directories:elink. dialog).
+.br
+A Toolboxesdropdown listbox also appears if the :hp6.Toolbar:ehp6. is on.
+:p.
 The :hp6.Toggle bottom buttons:ehp6. menu item turns off and on a row of
 buttons that appear just above the status line(s).  The buttons display
+buttons that appear just above the status line(s). The buttons display
 the name, date, and attributes of the currently selected object, and the
 filter status of the current container.  If clicked with B1, a command
+filter status of the current container. If clicked with B1, a command
 is generated (rename, info, edit date/attributes and filter dialog
 respectively).  If clicked with B2, a context menu appears (the same one
 you get if you click B2 on the first status line).  If clicked with B3,
+respectively). If clicked with B2, a context menu appears (the same one
+you get if you click B2 on the first status line). If clicked with B3,
 the sort changes for the current container:  filename, last write date,
 file size and reverse sort respectively.
 :p.
 The :hp6.Toggle drivebar:ehp6. menu item turns off and on a bar showing
 all available drives.  You can click these drive buttons to find or
+all available drives. You can click these drive buttons to find or
 switch to a drive (depending on the active window when the button is
 clicked), drag objects onto the buttons, request a context menu on a
 …
 already exists).
 :p.
+The menu also provides access to the dialogs for editing
+:link reftype=hd res=90400.Associations:elink.,
+:link reftype=hd res=90700.Commands:elink. and :hp6.Archivers:ehp6.
+(:link reftype=hd res=94200.Edit Archiver Data:elink.)
+:p.
+To change fonts and colors, FM/2 uses the WPS Font and Color Palettes.
+The Config menu contains commands to call up these objects for you.
+:p.
+:p.
 See also&colon.
 .br
 :link reftype=hd res=97600.FM/2 window layout:elink.
 .br
+:link reftype=hd res=99400.Using quicklists:elink.
+.br
+:link reftype=hd res=91800.Toolbar:elink.
+.br
+:link reftype=hd res=90400.Associations:elink.
+.br
+:link reftype=hd res=90700.Commands:elink.
+.br
+:link reftype=hd res=94200.Edit Archiver Data:elink.
+.br
+:link reftype=hd res=94600.Settings notebook:elink.
+.br
+:link reftype=hd res=100065.Set Target directory:elink.
+:h2 res=91800 name=PANEL_TOOLBAR.Toolbar
+:i1 id=aboutToolbar.Toolbar
+:artwork name='bitmaps\toolbar.bmp' align=center.
+The :hp1.toolbar:ehp1. is a collection of buttons that invoke some of
+the commands in the pulldown or popup menus.  Placing the mouse pointer
+on a button and pressing and holding B2 displays brief help for the
+button on the titlebar.
+:p.
+Some of the buttons will allow objects to be dragged onto them; for
+example, you can drag objects onto the trashcan to delete them.  Note
+that the hotspot of the mouse pointer itself should be over the button
+before releasing, not the icon being dragged (icons are slightly offset
+from the mouse pointer to give better target visibility).  Target
+emphasis is provided in the form of a black outline around the button,
+and the arrow pointer turns into a hand when above a toolbox icon.
+:p.
+This toolbar submenu is a conditional cascade menu, meaning that if you
+click other than on the boxed arrow a default command is executed (the
+toolbar is toggled off and on), but if you click on the boxed arrow you
+get a submenu of items you can select (the other choices are Text
+Toolbar, which will cause the toolbar to appear as "normal" buttons with
+text on them, or Toolbar Titles, which will cause text to appear below
+the toolbar bitmap buttons).
+:p.
+Toolbar buttons are user-configurable.  To change the toolbar, click
+mouse button two (usually the right button) while the mouse pointer is
+over a button to pop up a context menu.  You can get the "Load Toolbox"
+dialog by clicking B2 on a blank area of the toolbar, and the "Add
+Button" dialog by chording on a blank area of the toolbar.
+:p.
+For advanced/curious users&colon.  Information on what buttons are in the
+toolbar is kept in a file named FM3TOOLS.DAT.  This file is an ASCII
+(plain text) file that contains information defining the toolbar.  The
+file contains comments that explain its format.
+:p.
+FM/2 allows you to create customized toolboxes that can be loaded as
+required to provide toolboxes for specific activities.  Although FM/2
+provides ways to edit the toolbar internally, it's probably easier to
+load the definition files into a text editor and make the changes
+manually en masse.
+:p.
+If you'd like to see a different toolbar layout (and try out the Load
+Toolbox command), right-click on the toolbar, pick Load Toolbox from the
+resultant menu, and pick a toolbox from the listbox.  Then you might try
+creating your own and saving it with the Save Toolbox command.
+:p.
+See also&colon.
+.br
+:link reftype=hd res=96300.Reorder Tools:elink.
+.br
+:link reftype=hd res=94400.Edit Tool:elink.
+.br
+:link reftype=hd res=96400.Add Tool:elink.
+.br
+:link reftype=hd res=94000.Save Tools:elink.
+.br
+:link reftype=hd res=94500.Load Tools:elink.
+:h3 res=96300 name=PANEL_REORDERTOOLS.Reorder Tools
+:i1 id=aboutReorderTools.Reorder Tools
+This dialog, accessed from the context menu of a tool button, allows you
+to rearrange the order of the toolbar's tool buttons.  You take selected
+items from the left listbox and Add them to the end of the right listbox
+with the :hp1.Add>>:ehp1. button. When you've moved everything to the
+right listbox, click :hp1.Okay:ehp1..  Click :hp1.Cancel:ehp1. if you
+change your mind.
+:p.
+In reality, you don't need to move everything to the right listbox.  You
+can move only what you want moved to the top of the list, then click
+Okay.  Anything remaining in the left listbox is added to the end of
+what's in the right listbox.
+:p.
+The :hp1.<<Remove:ehp1. button can be used to move selected items from
+the right listbox to the bottom of the left listbox.
+:h3 res=94400 name=PANEL_EDITTOOL.Edit Tool
+:i1 id=aboutEditTool.Edit Tool
+This dialog allows you to change the help and text strings and flags
+associated with a button.  Edit as desired, then click Okay.  Click
+Cancel if you change your mind.
+:p.
+The :hp1.Help:ehp1. field should contain text to remind you what the
+button's command does.  For example, a button that deletes files and
+directories might have help reading "Delete files and directories".
+:p.
+The :hp1.Text:ehp1. field should contain very brief text that will be
+placed on the button (if the tool id has no bitmap associated with it).
+:p.
+The :hp1.Droppable:ehp1. checkbox determines if the tool can have objects
+dropped on it or not.  See list below.
+:p.
+The :hp1.Visible:ehp1. checkbox determines if the tool is visible or not.
+:p.
+If the :hp1.Separator:ehp1. checkbox is checked, FM/2 puts a bit of
+whitespace after the button (separates it from the next button).
+:p.
+If you check the :hp1.User-defined bmp:ehp1. checkbox, FM/2 will allow
+you to use your own bitmap.  Bitmaps are named after the :hp1.ID:ehp1.
+of the button -- for example, the bitmap file for ID 1005 would be named
+"1005.bmp".  Clicking the :hp1.Edit bmp:ehp1. button will cause ICONEDIT
+to be loaded with the bitmap, ready to edit.  (Note that bitmaps should
+be 28 x 28.)
+:p.
+The :hp1.ID:ehp1. field identifies the command that is associated with
+this button.  See the :link reftype=hd res=96401.Tool IDs:elink. topic.
+:h3 res=96400 name=PANEL_ADDTOOL.Add Tool
+:i1 id=aboutAddTool.Add Tool
+This dialog is accessed from the context menu of a tool button, or if you
+turn on the toolbar when there are no tools defined.
+:p.
+To add a tool, fill in the fields as appropriate and click Okay.  Click
+Cancel if you change your mind.
+:p.
+The :hp1.Help:ehp1. field should contain text to remind you what the
+button's command does.  For example, a button that deletes files and
+directories might have help reading "Delete files and directories".
+:p.
+The :hp1.Text:ehp1. field should contain very brief text that will be
+placed on the button (if the tool id has no bitmap associated with it).
+:p.
+The :hp1.Droppable:ehp1. checkbox determines if the tool can have objects
+dropped on it or not.  See list below.
+:p.
+The :hp1.Visible:ehp1. checkbox determines if the tool is visible or not.
+:p.
+If the :hp1.Separator:ehp1. checkbox is checked, FM/2 puts a bit of
+whitespace after the button (separates it from the next button).
+:p.
+If you check the :hp1.User-defined bmp:ehp1. checkbox, FM/2 will allow
+you to use your own bitmap.  Bitmaps are named after the :hp1.ID:ehp1.
+of the button -- for example, the bitmap file for ID 1005 would be named
+"1005.bmp".  Clicking the :hp1.Edit bmp:ehp1. button will cause ICONEDIT
+to be loaded with the bitmap, ready to edit.
+:p.
+The :hp1.ID:ehp1. field should be assigned a number that tells FM/2 what
+the command associated with the button is.  See :link reftype=hd
+res=96401.Tool IDs:elink. topic.
+:h3 res=96401 name=PANEL_TOOLIDS.Tool IDs
+:i1 id=aboutToolIDs.Tool IDs
+:xmp.
+ID     Command                                              Droppable?
+====   =================================================    ==========
+   View Files                                           Y
+   Edit Files                                           Y
+   Make Directory                                       N
+   Object Information                                   Y
+   Rename Files/Directories                             Y
+   Delete Files/Directories                             Y
+   Permanently Delete Files/Directories                 Y
+   Set Attributes and Date/Time of Files/Directories    Y
+  Walk Directories                                     N
+  Select All Files                                     N
+  Deselect All                                         N
+   Archive Files/Directories                            Y
+   Extract From Archives                                Y
+   Create Objects                                       Y
+   Create Shadow Objects                                Y
+   Copy Files/Directories                               Y
+   Move Files/Directories                               Y
+   Kill Process                                         N
+   Undelete Files                                       N
+   Instant Command File                                 N
+   OS/2 Command Line                                    N
+   Filter Container                                     N
+   Edit Associations                                    N
+   Edit Commands                                        N
+   Rescan                                               N
+   Print Files                                          Y
+   Extended Attributes                                  Y
+   View INI Files                                       Y
+   Save List to Clipboard                               Y
+   Save List to File                                    Y
+   Collect Files/Directories                            N
+   Collect Files/Directories from list file             Y
+   Bookshelf Viewer                                     N
+   Open Default                                         Y
+   Directory sizes                                      N
+   UUDecode                                             Y
+   Merge                                                Y
+   Exit FM/2                                            N
+   First Command                                        Y
+   Second Command                                       Y
+&period...
+   First Toolbox                                        N
+   Second Toolbox                                       N
+&period...
+:exmp.
+Note&colon.  Other Commands can also be used; just add to 4000 as required
+to get the number of the command.  For instance, Command 4 would be ID
+.  Command buttons use the text field; others shown have bitmaps
+associated with them in FM/2's resources.  Remember that if you change
+your Commands around, you need to resync the tools to the Commands...
+:p.
+Note&colon.  Toolbox buttons on a toolbar cause the appropriate toolbox
+to be loaded from QUICKTLS.DAT (one filename per line, blank lines and
+lines beginning with ";" ignored).  The file named on the first line is
+the First Toolbox, and so forth.  You can have up to 50 toolbox buttons
+defined (total).
+:p.
+This list isn't complete; ask me if you'd like a command added that
+doesn't appear, and I'll tell you if it can be added and what the ID is,
+if so.
+:h3 res=94000 name=PANEL_SAVETOOLS.Save Toolbox
+:i1 id=aboutSaveTools.Save Toolbox
+FM/2 allows you to save toolboxes (groups of tools) for later recall
+with the :link reftype=hd res=94500.Load Toolbox:elink. command.
+:p.
+Type the name of the file to hold the toolbox definitions into the entry
+field below the listbox, or select a file displayed in the listbox (it
+will be overwritten).  FM/2 saves the toolbox definitions into the file.
+:p.
+The files are given an extension of &period.TLS if you don't specify an
+extension.  The listbox shows files in the FM/2 directory that have the
+extension .TLS (which is my way of suggesting that you follow this
+convention).
+:h3 res=94500 name=PANEL_LOADTOOLS.Load Toolbox
+:i1 id=aboutLoadTools.Load Toolbox
+FM/2 allows you to load toolboxes (groups of tools) which were saved
+with the :link reftype=hd res=94000.Save Toolbox:elink. command.
+:p.
+Type the name of the file that holds the toolbox definitions into the
+entry field below the listbox, or select a file displayed in the
+listbox.  FM/2 loads the toolbox definitions from the file and updates
+the toolbar.
+:p.
+This allows you to have groups of specific-purpose buttons which you can
+load for different types of activities.  You don't have to use it, but
+it's there if you would like to do so.
+:p.
+Clicking :hp1.Okay:ehp1. without typing in or selecting a filename
+results in FM/2 reloading the default toolbox from FM3TOOLS.DAT.
+:p.
+If I may, here's how I'd recommend using this facility&colon.
+:p.
+First, save the full toolbar under a new name (perhaps ALL.TLS).  Next,
+delete any buttons that you don't want in your customized toolbar.
+Finally, add any Command buttons that you do want in the customized
+toolbar and save the new toolbox (as <something>.TLS).  By starting with
+the full toolbar, you'll spend more of your time deleting buttons you
+don't want (a trivial task) and less adding buttons.
+:h2 res=99980 name=PANEL_FLAGS.Drive flags
+:i1 id=aboutFlags.Drive flags
+Here you can set flags for various drives.  Command line switches
+override these flags.  The flags are stored in FM/2's INI file and
+loaded when FM/2 starts, so this is an alternative to all the
+esoteric drive command line switches :hp1.except:ehp1. the
+:hp2.Ignore:ehp2. switch.
+:p.
+:hp6.No prescan:ehp6.  Setting this causes FM/2 to :hp1.not:ehp1.
+pre-scan removable drives.  You have to double-click the drive
+before it's checked to see if it has any subdirectories.  This is
+handy for those of you with CD carousels.
+:p.
+:hp6.Don't load icons:ehp6.  Prevents FM/2 from loading icons for
+files and directories on this drive.  If the drive contains only
+DOS programs and data files or is a very slow drive, you might
+want to check this one.
+:p.
+:hp6.Don't load subjects:ehp6.  Prevents .SUBJECT EAs from being
+automatically loaded on this drive.  Again, if your drive is slow or you
+don't use .SUBJECTs with objects on this drive, you might want to check
+it.
+:p.
+:hp6.Don't load longnames:ehp6.  Prevents .LONGNAME EAs from being
+automatically loaded on this drive.  You've got the idea by now,
+right?
+:p.
+:hp6.Slow drive:ehp6..  Check this for drives which have extremely slow
+seek times (like ZIP and EZ removable hard drives).  The Autoview window
+and associated messages are disabled for this drive, and the "Quick Arc
+find" method is always used, whether on globally or not, which snaps up
+response time. I may take other shortcuts for drives with this attribute
+later (loosen error checking).  For such slow drives you may also want
+to check the various :hp1.Don't load...:ehp1. flags listed above.
+:p.
+:hp6.Include files in tree:ehp6.  If you check this, files will be shown
+as well as directories in the Drive Tree for this drive.  I have no
+idea why you would ever want to check this.
+:p.
+You get this dialog by selecting Edit->Drive flags from a context menu
+requested on a drive (root directory) in the Drive Tree or VTree window.
+:p.
+Note&colon.  To set the drive flags on a removable drive, like a floppy
+or CD-ROM, be sure you put a disk in the drive first.  FM/2 won't let
+you set drive flags on a currently invalid disk.
+.im notebook.ipf
 :h2 res=100065 name=PANEL_TARGETDIR.Set Target directory
 …
 .im command.ipf
+.im notebook.ipf
+.im databar.ipf
+:h2 res=94200 name=PANEL_AD_FRAME.Editing Archiver Details
+:i1 id=aboutEditArc.Editing Archiver Details
+:p.
+This dialog box, which you can reach from the Config menu, allows you to
+edit the details of an :link reftype=hd res=10015.archiver:elink.. Entry
+boxes are present for all the twenty one fields represented in
+ARCHIVER.BB2 (the text file that contains control information about your
+archivers which FM/2 uses to interface with the archivers). It's
+probably easier for most people to edit ARCHIVER.BB2 directly with a
+text editor.
+:p.
+:hp1.NOTE&colon.:ehp1. The simplest method to ensure that your archivers
+work properly with FM/2 is to make sure they're in a directory named in
+your PATH= statement, and check the names of the files to make sure they
+match what's on your system (i.e. UNZIP.EXE in both ARCHIVER.BB2 and on
+your hard disk, not UNZIP.EXE in one and UNZIP32.EXE in another).
+:p.
+In the event that you attempt to list an archive and FM/2 feels you've
+probably bungled the entry in ARCHIVER.BB2, you'll be given an
+opportunity to use this dialog to fix the entry. In this case, you'll
+see the listbox at the right of the dialog filled with the listing of
+the archive that your archiver made. You can highlight a line and click
+the << button next to the Start List or End List fields to move the line
+to that entry field (these are the most common mistakes, and FM/2 cannot
+find any files if the Start List string is wrong). You can double-click
+on a listbox line to have FM/2 "parse" it into the Fld# text boxes for
+you, to make it easier to judge field positions for sizes, dates, and
+filenames. The filename field in particular is extremely important. If
+it's too high, FM/2 finds no files. If it's "in range" but wrong, FM/2 gets
+the wrong fields for filenames.
+:p.
+You may still need to refer to your archiver's documentation, or run it
+to get the help on its command syntax. FM/2 can't do everything for you,
+but it holds your hand as best it can.
+:p.
+Refer to the ARCHIVER.BB2 file that came with FM/2 for additional
+information and an example.
+:p.
+When you've completed editing the archiver's details, click Okay. FM/2
+will ask you if you want to rewrite ARCHIVER.BB2 (be sure you save the
+original copy for its complete notes; FM/2 will back it up one version to
+ARCHIVER.BAK). If you don't rewrite ARCHIVER.BB2, changes are good only
+for the current session (handy for testing).
+:p.
+You can also get to this dialog box from Select Files' Config submenu.
+:p.
+See also&colon.
+:p.
+:link reftype=hd res=94300.Archiver Details Fields:elink.
+:h3 res=94300 name=PANEL_ARCFLDS.Archiver Details Fields
+:i1 id=aboutArcFlds.Archiver Details Fields
+:p.
+:hp2.ID:ehp2. This field contains an ID for the archiver; something for
+human consumption. It's a good idea to include the version number of the
+archiver for reference. An example might be "LHArc 2.11".
+:p.
+:hp2.Add:ehp2. This field should contain the command that creates
+and adds files to an archive. An example might be "PKZIP.EXE -a" (NOTE:
+This example assumes the file is on your PATH (see PATH= in CONFIG.SYS).
+If it's not, you'd need to give a full pathname, like
+"C&colon.\UTILS\PKZIP.EXE -a".) Note that commands should include the
+extension so that FM/2 can check them without guessing. Above this
+field is a button labeled "See." If clicked, the program named in this
+field will be run (you'll be given the opportunity to add arguments to
+the command line) in another window. This lets you check command syntax
+and archiver version, as well as assuring that FM/2 can find your archiver
+executables.
+:p.
+:hp2.Move:ehp2. This field should contain the command that moves files
+to the archive (adds then deletes the file). An example might be
+"ARC.EXE mwn".
+:p.
+:hp2.Extension:ehp2. This field contains the extension normally
+associated with files created by this archiver. An example might be
+"ZOO" for files created by the Zoo archiver.
+:p.
+:hp2.Extract:ehp2. This field contains the command that extracts files
+from the archive. This command should not delete the files from the
+archive when it extracts them, and *must* be present for FM/2 to show you
+a member of the archive (commands other than Extract and List may be
+left blank if necessary). An example might be "PKUNZIP.EXE -o". Note
+the "-o" option given; this tells PKUNZIP to automatically overwrite any
+existing files (FM/2 will check to see if any of the files exist and warn
+you if so). It's important to always include your archiver's "don't
+stop for user input" option; some things occur as detached processes and
+you can't interact with them; the program would be hung, which is
+uncool. Above this field is a button labeled "See." If clicked, the
+program named in this field will be run (you'll be given the opportunity
+to add arguments to the command line) in another window. This lets you
+check command syntax and archiver version.
+:p.
+:hp2.Extract w/Dirs:ehp2. This field contains the command that extracts
+files from the archive and places them into directories embedded in the
+archive. An example might be "LH.EXE x /o /s".
+:p.
+:hp2.Signature:ehp2. This field contains the signature for the archive
+type. There is usually a byte or few in a particular place in any
+archive that indicates that it is, indeed, an archive of that type. FM/2
+uses these signatures to "sniff out" which archiver is used to
+manipulate the archive. Since these signatures sometimes contain
+characters which are "unprintable," you can use \x<hexnum> to represent
+any "strange" characters. A side effect of this is that two backslashes
+are required to represent a single backslash ("\\" == "\"). See
+:link reftype=hd res=99500.C-style encoding:elink. for more information.
+:p.
+To determine what an archiver's signature is, either ask the archiver's
+author or check several different archives of the type for one or more
+bytes present in each at the same location, usually near the beginning
+of the file.
+:p.
+This field must be entered and valid for FM/2 to detect this type of
+archive (see also Sig(nature) Pos(ition)).
+:p.
+:hp2.List:ehp2. This field contains the command to list the archive's
+contents. This command *must* be present and correct for FM/2 to work
+properly with this type of archive. An example might be "ZOO.EXE v".
+:p.
+:hp2.Test:ehp2. This field contains the command to test the archive's
+integrity. An example might be "PKUNZIP.EXE -t".
+:p.
+:hp2.Add with paths:ehp2. This field contains the command to add files
+to the archiver with their paths (i.e. \FM3\FM3.EXE instead of just
+FM3.EXE). This can be omitted if the archiver doesn't support the
+command. An example might be "ZIP.EXE" (Zip defaults to adding paths).
+:p.
+:hp2.Move with paths:ehp2. As above, but moves the files instead of
+just adding them. An example might be "PKZIP -m -P".
+:p.
+:hp2.Add and recurse:ehp2. Adds files to the archive, with paths, and
+recurses into subdirectories. An example might be "LH a /s".
+:p.
+:hp2.Delete:ehp2. This field contains the command to delete files from
+the archive. An example might be "LH.EXE /o /d".
+:p.
+:hp2.Sig(nature) Pos(ition):ehp2. This field contains a number
+indicating how many bytes into the file the signature is located. If
+this number is negative, FM/2 looks from the end of the file instead of
+the beginning.
+:p.
+:hp2.F(ile)Name Pos(ition):ehp2. This field tells FM/2 which field on
+the line of an archive listing is the file name.
+Archive listing fields are numbered from 0.
+The file name position item consists of 4 subfields separated by commas.
+All subfields must be present and correct for FM/2 to get the right
+file names from the archive listing.
+The first is the field number.
+The second is a flag which is set to 1 to indicate that the file
+name is the last field on the line.
+This allows unquoted archive member names to contain spaces
+The third is a flag which is set to 1 to indicate that the file name starts
+at the second character of the field.
+This allows files that are surrounded by unusual bracketing characters.
+The fourth is a flag which is set to 1 to indicate the the file name
+stands alone at the first field in the listing line and
+the file details are on the next line.
+:p.
+To understand what "field on the line of an archive listing" means,
+think of a text line as being broken up into tokens, or words, separated
+by spaces. These tokens, or words, are fields. Therefore,
+:p.
+I like Ike.
+:p.
+contains three fields. Field 0 is "I", field 1 is "like", and field 3
+is "Ike."  Think of it like this&colon.
+.br
+:xmp.
+ +--------------------+
+ |  0   |  1   |  2   | Field Numbers
+ +------+------+------+
+ |  I   | like | Ike  | Field Contents
+ +------+------+------+
+:exmp.
+:p.
+:hp2.OldS(i)z(e) Pos(ition):ehp2. This field tells FM/2 which field on
+the line of an archive listing is the old (uncompressed) size of the
+file. If this isn't available or you don't care about it, you can enter
+a -1 to disable detection of this field entirely.
+:p.
+:hp2.NewS(i)z(e) Pos(ition):ehp2. This field tells FM/2 which field on
+the line of an archive listing is the new (compressed) size of the file.
+If this isn't available or you don't care about it, you can enter a -1
+to disable detection of this field entirely.
+:p.
+:hp2.Date Pos(ition):ehp2. This field tells FM/2 which field on
+the line of an archive listing is where the time/datestring is. If this
+isn't available or you don't care about it, you can enter a -1 to
+disable detection of this field entirely. You can optionally follow this
+number with a comma and another number that indicates the type of the
+date from any of the formats in the following list&colon.
+.br
+:xmp.
+. 02-08-96  23&colon.55&colon.32
+. 8 Feb 96  23&colon.55&colon.32
+. 8 Feb 96  11&colon.55p
+. 96-02-08  23&colon.55&colon.32
+:exmp.
+:p.
+:hp2.NumDateF(ie)lds:ehp2. This field tells FM/2 how many fields comprise
+the time/datestring.
+:p.
+:hp2.Start-of-list:ehp2. The line that comes just before the list of
+files in the archiver listing (see example below). You can use the
+:hp2.<<:ehp2. button to insert a selected line directly from the listbox
+into this field.
+:p.
+:hp2.End-of-list:ehp2. The line that comes just after the list of
+files in the archiver listing (see example below). You can use the
+:hp2.<<:ehp2. button to insert a selected line directly from the listbox
+into this field.
+:p.
+Here's an example of an ARC listing (5.12mpl, command "ARC l"; you may
+need to widen the help windows for this to look right...):
+:p.
+:xmp.
+Name           Length     Date
+============  ========  =========    <--this line is start-of-list
+MAKEFILE           374  28 Nov 89
+QSORT.C          14279  29 Nov 89
+QSORT.EXE        24629  29 Nov 89
+STUFF.H            371  29 Nov 89
+        ====  ========               <--this line is end-of-list
+Total      4     39653
+:exmp.
+:p.
+Note the filename is in position 0, old length in position 1, and the
+date starts in position 2, with 3 parts, and there's no new length
+field (so it'd be -1). Compare that to the archiver entry for
+ARC 5.12mpl in the "stock" ARCHIVER.BB2 and you should get a feel for
+what all those fields mean.

trunk/dll/ipf/context.ipf

-              r10
+              r268
 :h1 res=93700 name=PANEL_CONTEXT.Context menus
 :i1 id=aboutContext.Context menus
+:h1 res=93700 name=PANEL_CONTEXT.Context Menus
+:i1 id=aboutContext.Context Menus
 :link reftype=hd res=97800.Context menus:elink. (also called popup
 menus) are used extensively in FM/2, just as they are in the WPS.
 …
 :p.
 Commands that affect the container as a whole are found in context menus
 requested over whitespace (any empty area of the container).  Commands
+requested over whitespace (any empty area of the container). Commands
 that affect the objects within the container are requested over the
 object of interest.  If an object is :link reftype=hd
+object of interest. If an object is :link reftype=hd
 res=98000.highlighted:elink. when a context menu is requested, the
 commands will usually affect all highlighted objects; otherwise, any
 …
 FM/2's :link reftype=hd res=93300.Files menu:elink. shows the same menu
 that would be obtained if you requested a context menu over the current
 object.  FM/2's :link reftype=hd res=93800.Views menu:elink. shows the
+object. FM/2's :link reftype=hd res=93800.Views menu:elink. shows the
 same menu that would be obtained if you requested a context menu over
 the current window's whitespace.  :hp9.Note&colon.:ehp9.  FM/2 Lite's
+the current window's whitespace. :hp9.Note&colon.:ehp9. FM/2 Lite's
 pulldown menus are simplified, but the context menus have all the
 commands available, so the Files and Views menus aren't exact matches
 …
 :p.
 When a menu command leads to a dialog, the command name is followed by
 dots (i.e. "Attributes...").  In cases where commands have :link
+dots (i.e. "Attributes..."). In cases where commands have :link
 reftype=hd res=100005.accelerator key equivalents:elink., the :link
 reftype=hd res=97700.accelerator key:elink. is listed after the command
 (i.e. "Info...    Ctrl + i").
+(i.e. "Info...   Ctrl + i").
 :p.
 :hp2.See also&colon.:ehp2.
 …
 :i1 id=aboutContextObject.Context menus affecting objects
+Commands are listed in the order they appear on the file object context
+menu. Some commands apply to file, directory and drive objects. Others apply to
+only one or two types of objects. Items not appearing on the file object menus
+are inserted at the relative point they appear in the directory and/or drive menu.
+Small icons appear with each entry to indicate which types of objects file :artwork runin name='\bitmaps\file.bmp'.
+directory :artwork runin name='\bitmaps\fldr.bmp'. and/or drive :artwork runin name='\bitmaps\drive.bmp'. they are associated with.
 (Note that not all commands are available for all objects on all drives;
 CD-ROM drives obviously wouldn't allow Delete and Move commands, for
 instance, since they're read-only drives.)
+instance, since they're read-only drives. In this case the command(s) are grayed out)
 :p.
 These context menus are shadows of the :link reftype=hd
 res=93300.Files:elink. pulldown menu.
+:artwork name='..\..\bitmaps\view.bmp' align=center.
+:p.
+:artwork name='..\..\bitmaps\rename.bmp' align=center.
+:p.
+:hp6.:link reftype=hd res=91400.Rename:elink.:ehp6. allows you to rename
+objects. You are notified of conflicts as they occur. An easier method
+for renaming one object is to point at its text, hold down the ALT key,
+and click mouse button one; however, this command allows you to use
+wildcards when renaming if you desire.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:artwork name='..\..\bitmaps\copier.bmp' align=center. :artwork name='..\..\bitmaps\mover.bmp' align=center.
+:p.
+:hp6.Copy and Move:ehp6. copy or move objects. :hp2.:link reftype=hd
+res=90000.Drag and drop:elink. is recommended over using the menu
+commands for moving and copying.:ehp2. When using the menu commands, the
+:link reftype=hd res=91500.Walk Directories:elink. dialog appears to allow
+you to select a target directory.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:hp6.Copy and rename:ehp6. and :hp6.Move and rename:ehp6. allow you to
+change the names of the destination files as you copy and move using
+the standard rename dialog. You can also copy or move with wildcarding,
+like you can from the command line (COPY thisfile.txt *.bak) by using
+wildcards in the filename portion of the destination.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:hp6.Copy and preserve:ehp6. and :hp6.Move and preserve:ehp6. are only
+available in the Collector and See all files windows. These commands
+copy or move the selected files but preserve the directory relationship
+of the files. The effect of this can be non-obvious, so use with care.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+Let's say you select three files&colon. G&colon.\FOO\BAR\DUDE,
+G&colon.\FOO\BAR\WOW\DUDE and G&colon.\FOO\BAR\RUFF\DUDE. If you select
+:hp1.Copy and preserve:ehp1. and pick a destination directory of
+H&colon.\HERE, the resultant files will be H&colon.\HERE\DUDE,
+H&colon.\HERE\WOW\DUDE and H&colon.\HERE\RUFF\DUDE.
+:p.
+Note that drives are not considered when preserving directory
+relationships, so if one of our three files above resided on drive
+F&colon., the results would be the same.
+:p.
+:hp6.:link reftype=hd res=99995.Merge:elink.:ehp6. lets you merge
+several files together into a single file (you get to set the order of
+the files to be merged and the name of the file to which they're
+merged). :artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:hp6.WPS Copy:ehp6. and :hp6.WPS Move:ehp6. work like their standard
+counterparts, except that WPS techniques are used. There is more
+overhead using this method, so only use it when you need it -- for
+example, when moving a directory containing a program suite to
+maintain the link between program objects and the program executables
+in the directory. :artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:artwork name='..\..\bitmaps\view.bmp' align=center.
+:p.
 The :hp6.View:ehp6. conditional cascade submenu allows you to view the
 current object.  Since this is a conditional cascade submenu, you can
+current object. Since this is a conditional cascade submenu, you can
 click on the button to get a list of choices or click elsewhere to get
 a default viewing action (noted below).
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
 :p.
 :hp6.Autoview:ehp6. views objects through the :link reftype=hd
 res=92200.configured viewer:elink..  This is the default for the
+res=92200.configured viewer:elink.. This is the default for the
 Files->View conditional cascade submenu when a file is the current
 object.  When you select Autoview, FM/2 guesses whether the file is text
+object. When you select Autoview, FM/2 guesses whether the file is text
 or binary data and views it accordingly.
+:artwork runin name='\bitmaps\file.bmp'.
 :p.
 :hp6.as text:ehp6. causes FM/2 to view the current file object as text,
 using the :link reftype=hd res=97000.configured text viewer:elink. or
 the internal if none is configured.
+:artwork runin name='\bitmaps\file.bmp'.
 :p.
 :hp6.as binary:ehp6. causes FM/2 to view the current file object as
 binary data, using the :link reftype=hd res=97000.configured binary
 viewer:elink. or the internal if none is configured.  Binary data is
+viewer:elink. or the internal if none is configured. Binary data is
 usually viewed as a :link reftype=hd res=98800.hex dump:elink..
+:artwork runin name='\bitmaps\file.bmp'.
+:hp6.as archive:ehp6. causes FM/2 to open the file in the :link reftype=hd
+res=90200.Archive Container:elink. :artwork runin name='\bitmaps\file.bmp'.
+(only works for archive file types where the underlying program (i.e. Infozip for .zip files)
+is defined in archiver.bb2 and the program is in the system path.)
+:artwork runin name='\bitmaps\file.bmp'.
+:p.
 :artwork name='..\..\bitmaps\info.bmp' align=center.
+:p.
 :hp6.Information:ehp6. brings up a dialog telling you everything you
 ever wanted to know about file system objects but were afraid to ask.
 …
 Otherwise, you get a :link reftype=hd res=95700.comprehensive
 dialog:elink. that, besides showing you all the pertinent information
 about the object, shows the object's icon. That icon is important.  You
+about the object, shows the object's icon. That icon is important. You
 can get a context menu on it, and you can drag other objects onto it to
 change the object's icon.  If the object is an icon or pointer file
+change the object's icon. If the object is an icon or pointer file
 (*.ICO or *.PTR) you can use it to :link reftype=hd res=95500.change a
 system pointer:elink. (for instance, you could change OS/2's usual arrow
 pointer to a finger).  You can draw pointers yourself using OS/2's
+pointer to a finger). You can draw pointers yourself using OS/2's
 ICONEDIT program, or find them pre-drawn in several collections of icons
 and pointers freely available on BBSes.  This is the default command for
+and pointers freely available on the internet. This is the default command for
 the Files->View conditional cascade submenu when the current object is a
+directory.
+directory. (Note: Info is the first item on the drives menu)
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Quick Tree:ehp6. appears in Directory Containers. You can use this
+to quickly select a subdirectory into which to switch the Directory
+Container. Obviously, if there are no subdirectories to select from,
+FM/2 will ignore this command except to tell you.
+:artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:hp6.Update objects:ehp6. updates objects by refreshing the information
+FM/2 has on them from disk to make sure it's current (an alternative to
+rescan for special situations).
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Hide objects:ehp6. hides objects (removes them from view in the
+container) until you rescan, use the :link reftype=hd res=93400.Filter
+dialog:elink. or switch directories.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
 :artwork name='..\..\bitmaps\playmm.bmp' align=center.
+:p.
 :hp6.Multimedia:ehp6. attempts to play the objects via MMPM/2 using
 FM2PLAY.EXE (from the FM/2 Utilities collection, distributed separately
 in FM2UTILS.ZIP).  Obviously, the objects must be multimedia objects
+in FM2UTILS.ZIP). Obviously, the objects must be multimedia objects
 (sound files, movies, midi files, etc.) for this to have the desired
 effect, and MMPM/2 must be installed in your system.  Note:  for this
+effect, and MMPM/2 must be installed in your system. Note:  for this
 command to work properly with large numbers of files (where the length
 of the resultant command line would exceed the OS/2 command line length
 …
 supports the /# command line switch. To test your version of
 FM2PLAY.EXE, run FM2PLAY /? and see if /# is listed as a supported
+switch.  If not, upgrade to a new version of the FM/2 Utilities.
+:p.
+:hp6.Update objects:ehp6. updates objects by refreshing the information
+FM/2 has on them from disk to make sure it's current (an alternative to
+rescan for special situations).
+:p.
+:hp6.Hide objects:ehp6. hides objects (removes them from view in the
+container) until you rescan, use the :link reftype=hd res=93400.Filter
+dialog:elink. or switch directories.
+switch. If not, upgrade to a new version of the FM/2 Utilities.
+:artwork runin name='\bitmaps\file.bmp'.
 :p.
 :artwork name='..\..\bitmaps\edit.bmp' align=center.
+:p.
 The :hp6.Edit:ehp6. conditional cascade submenu allows you to edit the
 current object.  Since this is a conditional cascade submenu, you can
+current object. Since this is a conditional cascade submenu, you can
 click on the button to get a list of choices or click elsewhere to get a
 default editing action (noted below).
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
 :p.
 :hp6.Autoedit:ehp6. edits objects through the :link reftype=hd
 res=92200.configured editor:elink..  This is the default for the
+res=92200.configured editor:elink.. This is the default for the
 Files->Edit conditional cascade submenu when a file is the current
+object.  When you select Autoedit, FM/2 guesses whether the file is text
+or binary data and edits it accordingly.
+object. When you select Autoedit, FM/2 guesses whether the file is text
+or binary data and edits it accordingly.
+:artwork runin name='\bitmaps\file.bmp'.
 :p.
 :hp6.as text:ehp6. causes FM/2 to edit the current file object as text,
 using the :link reftype=hd res=97000.configured text editor:elink. or
 the internal if none is configured.
+:artwork runin name='\bitmaps\file.bmp'.
 :p.
 :hp6.as binary:ehp6. causes FM/2 to edit the current file object as
 binary data, using the :link reftype=hd res=97000.configured binary
 editor:elink..  Binary data is usually edited as a :link reftype=hd
 res=98800.hex dump:elink..  No default binary editor is provided at
+editor:elink.. Binary data is usually edited as a :link reftype=hd
+res=98800.hex dump:elink.. No default binary editor is provided at
 this time, but that may change.
+:artwork name='..\..\bitmaps\ea.bmp' align=center.
+:hp6.:link reftype=hd res=95000.Extended Attributes:elink.:ehp6. allows
+you to view an object's extended attributes (EAs) and to edit and add
+text attributes.
+:artwork runin name='\bitmaps\file.bmp'.
+:p.
+Edit :link reftype=hd res=99980.Drive flags:elink. is found on the drives context
+menu. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
 :artwork name='..\..\bitmaps\attrlist.bmp' align=center.
+:p.
 :hp6.:link reftype=hd res=95900.Attributes:elink.:ehp6. leads to a
 dialog that sets objects' attributes and (optionally) date/time. This is
 the default for the Files->Edit conditional cascade submenu when a
 directory is the current object.
+:p.
+:hp6.Subject:ehp6. allows you to give an object a description.  This
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:artwork name='..\..\bitmaps\ea.bmp' align=center.
+:p.
+:hp6.:link reftype=hd res=95000.Extended Attributes:elink.:ehp6. allows
+you to view an object's extended attributes (EAs) and to edit and add
+text attributes.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Subject:ehp6. allows you to give an object a description. This
 makes use of the same EA (.SUBJECT) that the WPS uses for object
 descriptions -- you can see and edit it on the File page of an object's
 Settings notebook.
+:artwork name='..\..\bitmaps\rename.bmp' align=center.
+:hp6.:link reftype=hd res=91400.Rename:elink.:ehp6. allows you to rename
+objects.  You are notified of conflicts as they occur.  An easier method
+for renaming one object is to point at its text, hold down the ALT key,
+and click mouse button one; however, this command allows you to use
+wildcards when renaming if you desire.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:artwork name='..\..\bitmaps\print.bmp' align=center.
+:p.
+:link reftype=hd res=99985.:hp6.Print:ehp6.:elink. prints text files.
+It'd be a good idea to have a printer to which to print, and have
+configured it first, before trying to use this. If using the standard
+WPS, be sure you have a printer object configured for the device you've
+told FM/2 to use, or you may wind up with FM/2's printing thread blocked
+for eternity awaiting access to a nonexistent or inaccessible device.
+Actually, if using the standard WPS, it's recommended that you simply
+drag files to the printer object and drop them instead of using this
+command. :artwork runin name='\bitmaps\file.bmp'.
+:p.
+:artwork name='..\..\bitmaps\opend.bmp' align=center.
+:p.
+The :hp6.Open:ehp6. conditional cascade submenu allows you to open the
+current object. Since this is a conditional cascade submenu, you can
+click on the button to get a list of choices or click elsewhere to get a
+default open action for files is to either run them (executable files) or open them
+based on their file association. :artwork runin name='\bitmaps\file.bmp'.
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+The :hp6.Settings notebook:ehp6. option opens the object's WPS properties notebooks.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+Open a directory or drive as a WPS Folder in either :hp6.icon, details or tree:ehp6. view
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+Open a new FM/2 window (container; the default for directories and drives).
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+Opening a file's Default view will honor any OS/2 associations that you have
+setup. Remember that F6 or Ctrl + double-click opens an object's
+default WPS view, and Ctrl + Shift + double-click opens an object's
+WPS Settings notebook.
+:p.
+:artwork name='..\..\bitmaps\object.bmp' align=center.
+:artwork name='..\..\bitmaps\shadow.bmp' align=center.
+:p.
+Next is a conditional cascade submenu called :hp6.Create Objects:ehp6.,
+with Shadows as the default command. Create shadows appears as a
+a top level menu item on the drives object menu.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.:link reftype=hd res=93600.Shadow:elink.:ehp6. builds WPS shadow
+objects on your desktop or :hp6.Shadows in folders:ehp6. for selected
+object(s). :artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+You can also create :hp6.Real Objects:ehp6. for files
+:artwork runin name='\bitmaps\file.bmp'.
+:p.
+The save lists submenu allows you to save lists to the clipboard or a file
+:p.
+:artwork name='..\..\bitmaps\saveclip.bmp' align=center.
+:p.
+:hp6.Save/Append to clipboard:ehp6. allows you to save selected objects to the
+clipboard as a text list, one per line. This is a good way to transfer
+selections of files to other programs; for instance, you might copy a
+list of files to the clipboard and feed it to a terminal program to send
+the files over a modem or network.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:artwork name='..\..\bitmaps\savelist.bmp' align=center.
+:p.
+:hp6.:link reftype=hd res=96000.Save to list file:elink.:ehp6. lets you
+save selected objects as a list to a text file. Lists can include file
+sizes, subjects, etc.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:artwork name='..\..\bitmaps\collect.bmp' align=center.
+:p.
+:hp6.Collect File(s):ehp6. calls up the :link reftype=hd
+res=90100.Collector:elink. and places the selected files and directories
+into it. You can also open the Collector and drag things into it.
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Collect List in file(s):ehp6. collects the files listed inside the
+selected files (see :hp6.Save to list file:ehp6. above). The filename
+should be the first item on each line of the list. If spaces are
+contained in the filenames, enclose the filenames in "quote marks."
+Filenames must be full pathnames (d&colon.\path\filename). Directories as
+well as files can be Collected. :artwork runin name='\bitmaps\file.bmp'.
+:p.
+:artwork name='..\..\bitmaps\archive.bmp' align=center.
+:p.
+:hp6.:link reftype=hd res=90300.Archive:elink.:ehp6. allows you to build
+an archive containing the selected object(s).
+:artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:artwork name='..\..\bitmaps\extract.bmp' align=center.
+:p.
+:hp6.:link reftype=hd res=91000.Extract:elink.:ehp6. allows you to
+extract files from selected archives. :artwork runin name='\bitmaps\file.bmp'.
+:p.
+:hp6.UUDecode:ehp6. decodes files that were encoded with UUEncode, a
+common protocol on the Internet. Files created by UUDecoding are
+appended if they already exist. :artwork runin name='\bitmaps\file.bmp'.
+:p.
 :artwork name='..\..\bitmaps\delete.bmp' align=center.
+:hp6.Delete:ehp6. deletes objects.  If the :link reftype=hd
+:p.
+:hp6.Delete:ehp6. deletes objects. If the :link reftype=hd
 res=92400.Confirm Delete:elink. toggle is on or one or more directories
 are among the selected objects, you get a dialog showing the selected
 objects and asking you to confirm that you really meant what you said.
+In that dialog you have a chance to remove some of the objects.  If you
+have Undelete enabled for the drive on which the objects reside, they
+may be recoverable.
+In that dialog you have a chance to remove some of the objects. If you
+have OS/2's Undelete enabled for the drive on which the objects reside, they
+may be recoverable. :artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
 :artwork name='..\..\bitmaps\permdel.bmp' align=center.
+:p.
 :hp6.Permanent Delete:ehp6. deletes objects as above, but they will not
 be recoverable (which may make the deletion faster).  It should be noted
+be recoverable (which may make the deletion faster). It should be noted
 that when deleting directory objects, the file objects within the
 directory can never be recovered, but deleting all the file objects
 …
 :link reftype=launch object='CMD.EXE' data='/C HELP UNDELETE'.HELP
 UNDELETE:elink. at a command line for more information on enabling
+Undelete).
+:artwork name='..\..\bitmaps\print.bmp' align=center.
+:link reftype=hd res=99985.:hp6.Print:ehp6.:elink. prints text files.
+It'd be a good idea to have a printer to which to print, and have
+configured it first, before trying to use this.  If using the standard
+WPS, be sure you have a printer object configured for the device you've
+told FM/2 to use, or you may wind up with FM/2's printing thread blocked
+for eternity awaiting access to a nonexistent or inaccessible device.
+Actually, if using the standard WPS, it's recommended that you simply
+drag files to the printer object and drop them instead of using this
+command.
+:artwork name='..\..\bitmaps\mover.bmp' align=center.
+:artwork name='..\..\bitmaps\copier.bmp' align=center.
+:hp6.Move and Copy:ehp6. move or copy objects.  :hp2.:link reftype=hd
+res=90000.Drag and drop:elink. is recommended over using the menu
+commands for moving and copying.:ehp2. When using the menu commands, the
+:link reftype=hd res=91500.Walk Directories:elink. dialog appears to allow
+you to select a target directory.
+:p.
+:hp6.Copy and rename:ehp6. and :hp6.Move and rename:ehp6. allow you to
+change the names of the destination files as you copy and move using
+the standard rename dialog.  You can also copy or move with wildcarding,
+like you can from the command line (COPY thisfile.txt *.bak) by using
+wildcards in the filename portion of the destination.
+:p.
+:hp6.Copy and preserve:ehp6. and :hp6.Move and preserve:ehp6. are only
+available in the Collector and See all files windows.  These commands
+copy or move the selected files but preserve the directory relationship
+of the files.  The effect of this can be non-obvious, so use with care.
+:p.
+Let's say you select three files&colon. G&colon.\FOO\BAR\DUDE,
+G&colon.\FOO\BAR\WOW\DUDE and G&colon.\FOO\BAR\RUFF\DUDE.  If you select
+:hp1.Copy and preserve:ehp1. and pick a destination directory of
+H&colon.\HERE, the resultant files will be H&colon.\HERE\DUDE,
+H&colon.\HERE\WOW\DUDE and H&colon.\HERE\RUFF\DUDE.
+:p.
+Note that drives are not considered when preserving directory
+relationships, so if one of our three files above resided on drive
+F&colon., the results would be the same.
+:p.
+:hp6.:link reftype=hd res=99995.Merge:elink.:ehp6. lets you merge
+several files together into a single file (you get to set the order of
+the files to be merged and the name of the file to which they're
+merged).
+:p.
+:hp6.WPS Copy:ehp6. and :hp6.WPS Move:ehp6. work like their standard
+counterparts, except that WPS techniques are used.  There is more
+overhead using this method, so only use it when you need it -- for
+example, when moving a directory containing a program suite to
+maintain the link between program objects and the program executables
+in the directory.
+:artwork name='..\..\bitmaps\shadow.bmp' align=center.
+:artwork name='..\..\bitmaps\object.bmp' align=center.
+:hp6.:link reftype=hd res=93600.Shadow:elink.:ehp6. builds WPS shadow
+objects on your desktop (or other selected folder) for selected
+object(s).  You can also create :hp6.Real Objects:ehp6. (except for
+directories, for which you can only create shadow objects).  Both these
+options (where applicable) are in a conditional cascade submenu called
+:hp6.Create Objects:ehp6., with Shadows as the default command.
+:artwork name='..\..\bitmaps\opend.bmp' align=center.
+The :hp6.Open:ehp6. conditional cascade submenu allows you to open an
+object's Settings notebook, open directories as WPS Folders, or open a
+new FM/2 Directory Container window for directories (the default for
+directories).  Note that when WPS Folders are opened, they come up in
+the background.  This is an OS/2 bug, and IBM has been notified. Opening
+a file's Default view will honor any OS/2 associations that you have
+setup.  Remember that F6 or Ctrl + double-click opens an object's
+default WPS view, and Ctrl + Shift + double-click opens an object's
+WPS Settings notebook.
+:artwork name='..\..\bitmaps\archive.bmp' align=center.
+:hp6.:link reftype=hd res=90300.Archive:elink.:ehp6. allows you to build
+an archive containing the selected object(s).
+:artwork name='..\..\bitmaps\extract.bmp' align=center.
+:hp6.:link reftype=hd res=91000.Extract:elink.:ehp6. allows you to
+extract files from selected archives.
+:p.
+:hp6.UUDecode:ehp6. decodes files that were encoded with UUEncode, a
+common protocol on the Internet.  Files created by UUDecoding are
+appended if they already exist.
+:artwork name='..\..\bitmaps\saveclip.bmp' align=center.
+:hp6.Save to clipboard:ehp6. allows you to save selected objects to the
+clipboard as a text list, one per line.  This is a good way to transfer
+selections of files to other programs; for instance, you might copy a
+list of files to the clipboard and feed it to a terminal program to send
+the files over a modem or network.
+:artwork name='..\..\bitmaps\savelist.bmp' align=center.
+:hp6.:link reftype=hd res=96000.Save to list file:elink.:ehp6. lets you
+save selected objects as a list to a text file.  Lists can include file
+sizes, subjects, etc.
+:p.
+:artwork name='..\..\bitmaps\collect.bmp' align=center.
+:hp6.Collect File(s):ehp6. calls up the :link reftype=hd
+res=90100.Collector:elink. and places the selected files and directories
+into it.  You can also open the Collector and drag things into it.
+:p.
+:hp6.Collect List in file(s):ehp6. collects the files listed inside the
+selected files (see :hp6.Save to list file:ehp6. above).  The filename
+should be the first item on each line of the list.  If spaces are
+contained in the filenames, enclose the filenames in "quote marks."
+Filenames must be full pathnames (d&colon.\path\filename).  Directories as
+well as files can be Collected.
+:p.
+:hp6.Quick Tree:ehp6. appears in Directory Containers.  You can use this
+to quickly select a subdirectory into which to switch the Directory
+Container.  Obviously, if there are no subdirectories to select from,
+FM/2 will ignore this command except to tell you.
+Undelete). :artwork runin name='\bitmaps\file.bmp'. :artwork runin name='\bitmaps\fldr.bmp'.
+:p.
+:artwork name='..\..\bitmaps\rescan.bmp' align=center.
+:p.
+:hp6.Rescan:ehp6. rescans the selected drive. FM/2 tries
+very hard to keep all its windows up to date, but things outside FM/2
+can cause changes that FM/2 cannot know about automatically. This
+command will ensure that your display is current.
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Expand:ehp6. expands the tree from the point where the context menu
+was requested to the bottom of the branch. This isn't the same as clicking
+the [+] symbol as it expands :hp1.all:ehp1. branches.
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Collapse:ehp6. collapses the tree from the point where the context
+menu was requested to the bottom of the branch. This isn't the same as
+clicking the [-] symbol as it collapses :hp1.all:ehp1. branches.
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+The Miscellaneous cascade menu appears on directory and drive context menus
+The following appear on this cascade.
+:p.
+:hp6.:link reftype=hd res=95200.Sizes:elink.:ehp6. brings up a dialog
+showing how many bytes are in the selected directory and its
+subdirectories. :artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:artwork name='..\..\bitmaps\mkdir.bmp' align=center.
+:p.
+:hp6.Make Directory:ehp6. allows you to create new directories. The
+name of the directory where you requested the context menu is filled in
+as a starting point for convenience. Directories may be created many
+levels deep in one pass.
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Show all files:ehp6. is a command available on drive and directory objects
+and in the container menu of Directory Containers. It invokes the
+:link reftype=hd res=98500.See all files:elink. window and shows all
+the files in the directory and all its subdirectories.
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.:link reftype=hd res=92500.Undelete Files:elink.:ehp6.
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Check Disk:ehp6. runs PMCHKDSK.EXE on the selected drive. This
+tests the drive and can correct some deficiencies. This is available
+only in context menus requested on drives (root directories). Note
+that OS/2 cannot correct defects on disks that are in use by the
+system or programs (including FM/2). :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Format Disk:ehp6. runs PMFORMAT.EXE on the selected drive.
+:hp8.Formatting a disk will destroy any information already on the
+disk.:ehp8. This is available only in context menus requested on drives
+(root directories). :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Optimize:ehp6. runs a .CMD file with the name <Filesystem>OPT.CMD,
+giving the drive to optimize as a command line argument. Therefore, for
+a FAT drive C&colon. "FATOPT.CMD C&colon." would be run (through the
+command interpreter defined in %COMSPEC% or CMD.EXE if none is defined)
+for an HPFS drive D&colon. "HPFSOPT.CMD D&colon." and for an JFS drive E&colon. "JFSOPT.CMD
+E&colon.". CMD files are supplied with FM/2 that call utility programs from FM2UTILS.ZIP (a
+separate collection of free-for-the-using utilities, sometimes named
+FM2UTL.ZIP) or for JFS defragfs.exe supplied with OS2. You may modify these command files as required for your
+system, even to call other programs than those supplied. Always be sure
+to check the disk before trying to optimize it, and (in the case of the
+FAT optimizer) it's a good idea to back up first. You shouldn't run the
+FAT optimizer on compressed drives -- use the utilities that came with
+your compression program instead. :artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Detach:ehp6. detaches a network drive.
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Eject:ehp6. ejects removable media from drives (for instance,
+opens the door of a CD ROM drive).
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Lock:ehp6. locks a removable drive.
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.Unlock:ehp6. unlocks a removable drive.
+:artwork runin name='\bitmaps\drive.bmp'.
+:p.
+:hp6.:link reftype=hd res=90900.Drive Info:elink.:ehp6. is the first menu item on the drives
+context menu. :artwork runin name='\bitmaps\drive.bmp'.
 :h2 res=93710 name=PANEL_CONTEXTCNR.Context menus affecting containers
 …
 appears beside its icon.
 :p.
 :hp6.Text:ehp6. switches the container to Text view.  Text view is the
+:hp6.Text:ehp6. switches the container to Text view. Text view is the
 fastest view for a container to maintain, but provides the least
 information on the objects it contains.
 :p.
 :hp6.Details:ehp6. switches the container to Details view.  Details view
+:hp6.Details:ehp6. switches the container to Details view. Details view
 shows a great deal of information on the objects it contains, including
 file sizes, dates, and times, but it is the slowest view for a container
 to maintain.
 :p.
+The :hp6.Details Setup:ehp6. submenu allows you to control what is shown
+in a Details view. Each possible field in the details view for the drive
+type is shown. If the field is checked, FM/2 will show it. If not, it
+won't. Set the current view to Details view and you can see the changes
+as they occur. Note that for Directory Containers, the context menu
+items change the current container only. Use the internal :link
+reftype=hd res=94600.Settings notebook:elink. to change the default for
+subsequently created containers.
+:p.
 :hp6.Mini Icons:ehp6. is a toggle controlling whether icons are shown
 full size or in miniature in views that show icons.
 :p.
+The :hp6.Details Setup:ehp6. submenu allows you to control what is shown
+in a Details view.  Each possible field in the details view for the drive
+type is shown.  If the field is checked, FM/2 will show it.  If not, it
+won't.  Set the current view to Details view and you can see the changes
+as they occur.  Note that for Directory Containers, the context menu
+items change the current container only.  Use the internal :link
 reftype=hd res=94600.Settings notebook:elink. to change the default for
+:artwork name='..\..\bitmaps\filter.bmp' align=center.
+:p.
+:hp6.:link reftype=hd res=93400.Filter:elink.:ehp6. leads to a dialog
+that lets you set filemasks and attributes for objects to include in the
+container's display. Note:  For Directory Containers, this sets the
+default for _this_ container. Use the internal :link reftype=hd
+res=94600.Settings notebook:elink. to change the defaults for
 subsequently created containers.
+:artwork name='..\..\bitmaps\rescan.bmp' align=center.
+:hp6.Rescan:ehp6. rescans the directory associated with a container, or
+the drive from the current object down in a tree container.  FM/2 tries
+very hard to keep all its windows up to date, but things outside FM/2
+can cause changes that FM/2 cannot know about automatically.  This
+command will ensure that your display is current.
+:p.
+The :hp6.Sort submenu:ehp6. allows you to control how objects are sorted
+based on several criteria.  You can also tell FM/2 to always display
+directories ahead of or behind files.  Note that :hp1.Last access
+date:ehp1. and :hp1.Creation date:ehp1. are only meaningful for HPFS
+file systems; FAT file systems do not track this information.  The
+difference between :hp1.Pathname:ehp1. and :hp1.Filename:ehp1. is only
+apparent in the Collector.  With the former, the entire pathname of the
+object is used to sort.  With the latter, only the filename portion is
+used to sort.  FM/2 maintains separate sort criteria for Drive Tree,
+Collector, Directory Container and Archive Container windows.  See
+:link reftype=hd res=97200.Directory Container sort page:elink. and
+:link reftype=hd res=97400.Collector Container sort page:elink..  Note
+that Ctrl + F7 will call up the Sort menu for a given container.  The
+internal :link reftype=hd res=94600.Settings notebook:elink. can be
+used to set the default for subsequently opened Directory Containers --
+the context menu item sets the sort for _this_ container only.
+:p.
+:hp6.Resort:ehp6. resorts items in a container.  If you have more than
+:p.
+:hp6.Resort:ehp6. resorts items in a container. If you have more than
 one Directory or Archive Container window open, selecting a new sort
 type only causes the container in which you requested the context menu
 to resort itself (although the change will affect all future rescans,
 resorts and insertions in that type of container).  This command lets
+resorts and insertions in that type of container). This command lets
 you resort a container so that the new sort type is reflected in the
 display.
+:artwork name='..\..\bitmaps\filter.bmp' align=center.
+:hp6.:link reftype=hd res=93400.Filter:elink.:ehp6. leads to a dialog
+that lets you set filemasks and attributes for objects to include in the
+container's display.  Note:  For Directory Containers, this sets the
+default for _this_ container. Use the internal :link reftype=hd
+res=94600.Settings notebook:elink. to change the defaults for
+subsequently created containers.
+:p.
+:artwork name='..\..\bitmaps\rescan.bmp' align=center.
+:p.
+:hp6.Rescan:ehp6. rescans the directory associated with a container, or
+the drive from the current object down in a tree container. FM/2 tries
+very hard to keep all its windows up to date, but things outside FM/2
+can cause changes that FM/2 cannot know about automatically. This
+command will ensure that your display is current.
 :p.
 :hp6.Parent:ehp6. moves directory containers to the previous (parent)
 …
 directory. This is sort of like a one-step "undo" when you switch
 a container to look at a different directory.
+:p.
 :artwork name='..\..\bitmaps\walk.bmp' align=center.
+:p.
 :hp6.:link reftype=hd res=91500.Walk Directories:elink.:ehp6. leads to a
 dialog that lets you walk through your directory structures, or recall
 …
 :p.
 :hp6.Show all files:ehp6. is a command available on directory objects
 and in the container menu of Directory Containers.  It invokes the
+and in the container menu of Directory Containers. It invokes the
 :link reftype=hd res=98500.See all files:elink. window and shows all
+the files in the directory and all its subdirectories.
+the files in the directory and all its subdirectories. (on submenu of miscellaneous)
+:p.
+:hp6.Find in drive tree:ehp6. hilites the directory the directory container is
+looking into on the drive tree. (on submenu of miscellaneous)
+:p.
 :artwork name='..\..\bitmaps\select.bmp' align=center.
+:p.
 :artwork name='..\..\bitmaps\deselect.bmp' align=center.
+:p.
 The :hp6.:link reftype=hd res=99100.Select:elink.:ehp6. submenu gives
 you many ways to highlight and unhighlight objects in a container.  This
+you many ways to highlight and unhighlight objects in a container. This
 lets you quickly build sophisticated selection sets of objects upon
 which you can perform tasks.
 …
 (highlight what isn't, unhighlight what is).
 :p.
+The :hp6.Sort submenu:ehp6. allows you to control how objects are sorted
+based on several criteria. You can also tell FM/2 to always display
+directories ahead of or behind files. Note that :hp1.Last access
+date:ehp1. and :hp1.Creation date:ehp1. are only meaningful for HPFS
+file systems; FAT file systems do not track this information. The
+difference between :hp1.Pathname:ehp1. and :hp1.Filename:ehp1. is only
+apparent in the Collector. With the former, the entire pathname of the
+object is used to sort. With the latter, only the filename portion is
+used to sort. FM/2 maintains separate sort criteria for Drive Tree,
+Collector, Directory Container and Archive Container windows. See
+:link reftype=hd res=97200.Directory Container sort page:elink. and
+:link reftype=hd res=97400.Collector Container sort page:elink.. Note
+that Ctrl + F7 will call up the Sort menu for a given container. The
+internal :link reftype=hd res=94600.Settings notebook:elink. can be
+used to set the default for subsequently opened Directory Containers --
+the context menu item sets the sort for _this_ container only.
+:p.
 Finally, FM/2 offers a full set of :hp6.Compare Selection:ehp6. tools
 that let you select and deselect files based on how they compare to
 unfiltered files in all other open Directory Containers (available only
 in Directory Containers).  To give you an idea how this might be
+in Directory Containers). To give you an idea how this might be
 helpful, imagine that you just hit the [Enter] key in the middle of
 typing a copy command, when you were reaching for the backslash key to
 complete a path. Before you realize what's happening and can hit Ctrl-C,
 you copied fifty files from a data directory to the root directory of
 your boot drive (you shoulda used FM/2! &colon.-).  Now you want to get rid of
 them, but you don't want to pick each one.  Open the data directory and
+your boot drive (you shoulda used FM/2! &colon.-). Now you want to get rid of
+them, but you don't want to pick each one. Open the data directory and
 the root, choose "Select if in all," then delete the selected files in
 the root directory.  You're done.
+the root directory. You're done.
 :p.
 These powerful selection tools are where a file manager really outshines
 command line file management, so be sure to take a look at them.  Note
+command line file management, so be sure to take a look at them. Note
 that Ctrl + F8 will call up the Select menu for a given container.
+:p.
+:hp6.:link reftype=hd res=100065.Set Target directory:elink.:ehp6. and
+:hp6.:link reftype=hd res=94600.Settings notebook:elink.:ehp6. are also on this menu.
+:p.
 :h2 res=93715 name=PANEL_CONTEXTTREE.Context menus affecting Drive Tree container
 :i1 id=aboutContextTree.Context menus affecting Drive Tree container
+:hp6.Expand:ehp6. expands the tree from the point where the context menu
+was requested to the bottom of the branch.  This isn't the same as clicking
+the [+] symbol as it expands :hp1.all:ehp1. branches.
+:p.
+:hp6.Collapse:ehp6. collapses the tree from the point where the context
+menu was requested to the bottom of the branch.  This isn't the same as
+clicking the [-] symbol as it collapses :hp1.all:ehp1. branches.
+:p.
+:hp6.Optimize:ehp6. runs a .CMD file with the name <Filesystem>OPT.CMD,
+giving the drive to optimize as a command line argument.  Therefore, for
+a FAT drive C&colon. "FATOPT.CMD C&colon." would be run (through the
+command interpreter defined in %COMSPEC% or CMD.EXE if none is defined)
+and for an HPFS drive D&colon. "HPFSOPT.CMD D&colon.".  CMD files are
+supplied with FM/2 that call utility programs from FM2UTILS.ZIP (a
+separate collection of free-for-the-using utilities, sometimes named
+FM2UTL.ZIP).  You may modify these command files as required for your
+system, even to call other programs than those supplied.  Always be sure
+to check the disk before trying to optimize it, and (in the case of the
+FAT optimizer) it's a good idea to back up first.  You shouldn't run the
+FAT optimizer on compressed drives -- use the utilities that came with
+your compression program instead.
+:p.
+:hp6.Check Disk:ehp6. runs PMCHKDSK.EXE on the selected drive.  This
+tests the drive and can correct some deficiencies.  This is available
+only in context menus requested on drives (root directories).  Note
+that OS/2 cannot correct defects on disks that are in use by the
+system or programs (including FM/2).
+:p.
+:hp6.Format Disk:ehp6. runs PMFORMAT.EXE on the selected drive.
+:hp8.Formatting a disk will destroy any information already on the
+disk.:ehp8. This is available only in context menus requested on drives
+(root directories).
+:artwork name='..\..\bitmaps\mkdir.bmp' align=center.
+:hp6.Make Directory:ehp6. allows you to create new directories.  The
+name of the directory where you requested the context menu is filled in
+as a starting point for convenience.  Directories may be created many
+levels deep in one pass.
+:p.
+:hp6.:link reftype=hd res=95200.Sizes:elink.:ehp6. brings up a dialog
+showing how many bytes are in the selected directory and its
+subdirectories.
+:p.
+:hp6.Eject:ehp6. ejects removable media from drives (for instance,
+opens the door of a CD ROM drive).
+:p.
+:hp6.Lock:ehp6. locks a removable drive.
+:p.
+:hp6.Unlock:ehp6. unlocks a removable drive.
+This menu includes many of the choices found on the
+:link reftype=hd res=93710.Context menus affecting containers:elink.
+This menu lacks the :hp6.view:ehp6. options except for :hp6.mini icons:ehp6. and doesn't include
+:hp6.select:ehp6., :hp6.filter:ehp6. or the :hp6.miscellaneous submenu:ehp6. items.
+The additional items it contains are described below&colon.
+:p.
+:hp6.Toggle icons:ehp6 turns the icons on and off in the Drive Tree container.
+:p.
+:hp6.Open Directory Container:ehp6. is used for:link reftype=hd res=98900.Opening a Directory Container:elink.
+:p.
+To remap (attach) a remote server to a local drive letter, enter the
+UNC server name in the entry field at the top center of this dialog,
+then select the drive letter from the left (attach) listbox to which to
+attach the server. Finally, click the :hp1.Attach:ehp1. button.
+:p.
+To detach a local drive letter from a remote server, select the
+drive letter from the right (detach) listbox, then click the
+:hp1.Detach:ehp1. button.
+:p.
+When you're through remapping drives, click :hp1.Done:ehp1..
+:p.
+According to IBM LAN Server documentation, a UNC name consists of a
+double backslash, the name of the server, another backslash, and the
+name of the resource&colon. \\servername\netname
+:p.
+Note that FM/2 saves the UNC names you enter in the listbox below the
+entry field. You can recall these names later by clicking on them.
+The :hp1.Delete:ehp1. button deletes the currently selected name from
+the listbox, and the :hp1.Clear:ehp1. button removes all names from
+the listbox. Names are added automatically. Up to 200 names can be
+stored in this manner (kept on disk between sessions in a file named
+RESOURCE.DAT).
 :p.
 :hp6.Partitions:ehp6. calls up :link reftype=launch object='CMD.EXE'
 data='/C HELP FDISKPM'.FDISKPM.EXE:elink. to allow you to modify the
 partitions on your hard drives.  :hp8.Extreme caution should be
+partitions on your hard drives. :hp8.Extreme caution should be
 exercised; read the help!:ehp8.
 :p.
 …
 :p.
 The :hp1.Save as:ehp1. entry field contains the name of the file to
 which the list will be saved.  The :hp1.Find:ehp1. button calls up a
 standard OS/2 open dialog to let you point and click at a file.  If the
 file exists, it will be appended.  :hp6.Hint&colon.:ehp6.  You can enter
+which the list will be saved. The :hp1.Find:ehp1. button calls up a
+standard OS/2 open dialog to let you point and click at a file. If the
+file exists, it will be appended. :hp6.Hint&colon.:ehp6. You can enter
 :hp1.PRN:ehp1. as the filename to print the list.
 :p.
 …
 the :hp1.Add:ehp1. button to add the current pattern (the one in the
 entry field), and the :hp1.Del:ehp1. button to remove the currently
 highlighted pattern from the listbox).  You can select one of the
+highlighted pattern from the listbox). You can select one of the
 patterns in the listbox to avoid retyping it (as you highlight a pattern
 in the listbox it'll appear in the entry field). The patterns are saved
 …
 :p.
 The :hp1.Pattern:ehp1. entry field contains a pattern that will be used
 to format the list.  Metastrings may be used to cause parts of a file
 description to be written where desired (see below).  Also note that the
+to format the list. Metastrings may be used to cause parts of a file
+description to be written where desired (see below). Also note that the
 pattern is run through a :link reftype=hd res=99500.C-style escape
 encoder:elink., so that \x1b would be interpreted as an ESCAPE
 …
 :p.
 When everything's set as you want it, click :hp1.Okay:ehp1. to save the
 list.  Click :hp1.Cancel:ehp1. if you change your mind.
+list. Click :hp1.Cancel:ehp1. if you change your mind.
 :p.
 Metastrings and their meanings (note&colon. these are different from those
 …
 :eparml.
 :p.
 Note that you can manipulate list files from REXX.  An EXAMPLE.CMD is
 included in the FM/2 archive to show you how it's done.  REXX scripts
+Note that you can manipulate list files from REXX. An EXAMPLE.CMD is
+included in the FM/2 archive to show you how it's done. REXX scripts
 written in this manner can be effectively used as Commands.
+:p.
+:h2 res=92500 name=PANEL_UNDELETE.Undelete Files
+:i1 id=aboutUndelete.Undelete Files
+:artwork name='..\..\bitmaps\undelete.bmp' align=center.
+:p.
+This leads to a dialog that interfaces with UNDELETE.COM to allow you to
+undelete files. The drive that will be operated on is determined by the
+highlighted object in the directory tree. This dialog filters out files
+that already exist on the disk. This only works if OS/2's del directories
+have been designated in config.sys. It doesn't interact with "Trashcans"
+:p.
+The :hp1.Mask:ehp1. entry field lets you set a mask (which can include
+a directory path). You can switch drives using the dropdown listbox.
+A :hp1.Subdirs:ehp1. button lets you choose whether to show files that
+can be undeleted in subdirectories as well.
+:p.
+You can always go directly to UNDELETE.COM if you have the need for more
+control. This is provided only for convenience.
+:artwork runin name='\bitmaps\fldr.bmp'. :artwork runin name='\bitmaps\drive.bmp'.
 .br

trunk/dll/ipf/databar.ipf

-              r2
+              r268
 :p.
 In addition, the databar can optionally show the free drive space on all
 local fixed drives (and, optionally, remote drives).  To force a drive's
+local fixed drives (and, optionally, remote drives). To force a drive's
 information bar to be updated immediately, click it once with B1. The
 drive information is presented in both text and as a colored bar showing
 the amount of free space in relation to the total drive's size.  The
+the amount of free space in relation to the total drive's size. The
 bar is usually green, but will turn blue and then red as space decreases.
 When a bar is red, it's probably time to do some archiving to get more
 free space on it (less than 10% of the drive remains free).  Double-click
+free space on it (less than 10% of the drive remains free). Double-click
 if running the Databar free-standing to open a VDir for the drive.
 :p.
 The swapper information includes the size of the swapfile, in kilobytes,
 and the amount of free space on the drive holding the swapfile, again,
 in kilobytes.  Double-click to open the Undelete program.  The memory
+in kilobytes. Double-click to open the Undelete program. The memory
 information includes the amount of free physical memory and total free
 memory (including available swapspace), also in kilobytes.
 …
 other information is updated about once every ten to sixty seconds. For
 about six seconds of every minute the time/date field displays the
 elapsed system time (how long the system's been up).  You can click the
+elapsed system time (how long the system's been up). You can click the
 time/date field with B1 to cause this info to show up briefly at any
 time, or double-click to open the System Clock's Settings window to
 …
 :p.
 You can move the databar by clicking and holding B1 on the databar and
 dragging it.  You can request a context menu on the date/time window to
 adjust some other items.  Double-clicking the databar anywhere but on
+dragging it. You can request a context menu on the date/time window to
+adjust some other items. Double-clicking the databar anywhere but on
 the bottom four fields with B1 will close it and restore FM/2 if you're
 not running the DATABAR.EXE miniapp.  If you're running the miniapp, or
+not running the DATABAR.EXE miniapp. If you're running the miniapp, or
 just feel like it, request a context menu on the databar and click the
 :hp1.Close Window:ehp1. command.  This context menu also lets you
+:hp1.Close Window:ehp1. command. This context menu also lets you
 configure the databar (if drives are displayed, if it floats to the top
 of other windows, etc.).

trunk/dll/ipf/dirsize.ipf

-              r233
+              r268
 :i1 id=aboutTotals.Total size of directories
 This dialog's container contains a breakdown of disk usage for a
 directory and its subdirectories.  The container is reached by selecting
+directory and its subdirectories. The container is reached by selecting
 :hp1.Miscellaneous->Sizes:ehp1. from a tree directory's context menu or
 by running the :hp1.Dir Sizes:ehp1. program object from the FM/2 Tools
 …
 numbers, as in&colon.
 :lines.
+  ADIR  4096k + 8192k = 12288k (8.24%)
+  ROOTDIR  4096KiB + 8192KiB = 12288KiB (8.24% of drive)
+        ADIR 8192KiB + 0 = 8192KiB  (66.67%)
 :elines.
 :p.
 …
 total number of kilobytes occupied by all subdirectories and any files and
 subdirectories they contain. The third number is the total of the first and second
+(addition performed in kilobytes). The
+percentage displayed for the first (parent) directory
+is the percentage of the used space the directory tree contains,
+in relation to the total used space on the drive. The percentages displayed
+for the other directories are
+(addition performed in kilobytes). The percentage displayed for the root
+directory or the highest level directory selected is the percentage of space
+that directory tree contains relative to the total drive space.
+The percentages displayed for the other directories are
 the percentage of the used space the directory tree contains, in relation
 to the entire displayed tree. A graph appears below the line displaying a
+to the space used by the entire displayed tree. A graph appears below the line displaying a
 "picture" of this percentage.
 :p.
 FM/2 also color-codes the text describing the directory.  Black text
 indicates that something is below the directory.  Blue text indicates
+FM/2 also color-codes the text describing the directory. Black text
+indicates that something is below the directory. Blue text indicates
 that nothing is below the directory (note there may be subdirectories,
 but they are empty).  Grey text indicates that the directory is totally
 empty.
+but they are empty). Gray text indicates that the directory contains
+no files but may or may not contain subdirectories.
 :p.
 The :hp1.Expand:ehp1. and :hp1.Collapse:ehp1. buttons can take a noticable amount
+The :hp1.Expand:ehp1. and :hp1.Collapse:ehp1. buttons can take a noticeable amount
 of time to process
 for large directory trees since each subdirectory must be processed.
 …
 :p.
 The first (parent) item in the tree shows the percentage of the drive
 used by the entire tree.  This is noted in the parentheses containing
+used by the entire tree. This is noted in the parentheses containing
 the percentage, and the graph for this item is green instead of red.
 :p.
 The totals reflect the size of files and extended attributes.  Due to
+The totals reflect the size of files and extended attributes. Due to
 minimum allocation units on the disk, more space may be physically
 allocated than is accounted for in the totals.  The text field just
+allocated than is accounted for in the totals. The text field just
 above the pushbuttons gives you stats that _do_ take allocation units
 into account, for the entire drive.  The actual byte counts
+into account, for the entire drive. The actual byte counts
 are rounded up to the next kilobyte for display.
 The 0k figure denotes a directory with a truly 0 byte count.
+The 0 figure denotes a directory with a truly 0 byte count.
 :p.
 You can double-click a directory to open it so you can see its files.
 …
 This is a quick way to see where your disk space has gone.
 :p.
 :hp6.Hint&colon.:ehp6.  You can get a printout of this information by
 entering :hp1.PRN:ehp1. as the name of the :hp1.Save:ehp1. file.  The
+:hp6.Hint&colon.:ehp6. You can get a printout of this information by
+entering :hp1.PRN:ehp1. as the name of the :hp1.Save:ehp1. file. The
 information printed is the same as that visible in the container, which
 is to say that unexpanded branches aren't printed, so you can be

trunk/dll/ipf/drvinfo.ipf

-              r10
+              r268
 :artwork name='..\..\bitmaps\info.bmp' align=center.
+:p.
 FM/2 will show you information about the drive from which you chose the
 :hp1.Info:ehp1. command in a context menu.
+:hp1.Info:ehp1. command in a context menu or files menu.
 :p.
 For writeable drives, you can change the drive's :hp1.label:ehp1. here
+For writable drives, you can change the drive's :hp1.label:ehp1. here
 by changing the text in the entry field and clicking :hp1.Okay:ehp1..
 :p.
 The dialog box shows you the type of file system, volume label, total
 and available sizes of the drive (megabytes, kilobytes and units), tells
+and available space on the drive (megabytes, kilobytes and units), tells
 you how the drive's resources are parceled into units, gives the drive's
 serial number and some :hp1.flags:ehp1..
 …
 These flags indicate special properties about the drive, like
 :hp1.Removable:ehp1. (the drive allows its media to be removed and
 changed) or :hp1.Not Writeable:ehp1. (the drive does not allow changes
+changed) or :hp1.Not Writable:ehp1. (the drive does not allow changes
 to be written to it).
 :p.
 …
 flags:elink. command.
+:h3 res=99980 name=PANEL_FLAGS.Drive flags
+:i1 id=aboutFlags.Drive flags
+Here you can set flags for various drives. Command line switches
+override these flags. The flags are stored in FM/2's INI file and
+loaded when FM/2 starts, so this is an alternative to all the
+esoteric drive command line switches :hp1.except:ehp1. the
+:hp2.Ignore:ehp2. switch.
+:p.
+:hp6.No prescan:ehp6. Setting this causes FM/2 to :hp1.not:ehp1.
+pre-scan removable drives. You have to double-click the drive
+before it's checked to see if it has any subdirectories. This is
+handy for those of you with CD carousels.
+:p.
+:hp6.Don't load icons:ehp6. Prevents FM/2 from loading icons for
+files and directories on this drive. If the drive contains only
+DOS programs and data files or is a very slow drive, you might
+want to check this one.
+:p.
+:hp6.Don't load subjects:ehp6. Prevents .SUBJECT EAs from being
+automatically loaded on this drive. Again, if your drive is slow or you
+don't use .SUBJECTs with objects on this drive, you might want to check
+it.
+:p.
+:hp6.Don't load longnames:ehp6. Prevents .LONGNAME EAs from being
+automatically loaded on this drive. You've got the idea by now,
+right?
+:p.
+:hp6.Slow drive:ehp6.. Check this for drives which have extremely slow
+seek times (like ZIP and EZ removable hard drives). The Autoview window
+and associated messages are disabled for this drive, and the "Quick Arc
+find" method is always used, whether on globally or not, which snaps up
+response time. I may take other shortcuts for drives with this attribute
+later (loosen error checking). For such slow drives you may also want
+to check the various :hp1.Don't load...:ehp1. flags listed above.
+:p.
+:hp6.Include files in tree:ehp6. If you check this, files will be shown
+as well as directories in the Drive Tree for this drive. I have no
+idea why you would ever want to check this.
+:p.
+You get this dialog by selecting Edit->Drive flags from a context menu
+requested on a drive (root directory) in the Drive Tree or VTree window.
+:p.
+Note&colon. To set the drive flags on a removable drive, like a floppy
+or CD-ROM, be sure you put a disk in the drive first. FM/2 won't let
+you set drive flags on a currently invalid disk
 :h2 res=95700 name=PANEL_INFO.Object Information
 :i1 id=aboutInfo.Object Information
 :artwork name='..\..\bitmaps\info.bmp' align=center.
+:p.
 This comprehensive dialog tells you just about everything there is to
 know about file system objects.  If information is being displayed for
+know about file system objects. If information is being displayed for
 more than one object, the objects may be scrolled through in the listbox
+at the top of the dialog.
+at the top of the dialog. The dialog is accessed from :hp1.View->Info:ehp1.
+of the objects context menu.
 :p.
 Note the object's icon is shown.  It's useable -- you can get a context
+Note the object's icon is shown. It's usable -- you can get a context
 menu on it, or you can drag other objects onto it to change the object's
 icon.
 :p.
 You can edit an object's EAs or WPS Settings notebook (Properties) by
 clicking the appropriate button.  If you want to see inside a file,
+clicking the appropriate button. If you want to see inside a file,
 double-click it in the listbox.
 :p.
 Click :hp1.Okay:ehp1. when you're through examining the objects.

trunk/dll/ipf/eas.ipf

-              r10
+              r268
 :i1 id=aboutEAs.Extended Attributes
 :artwork name='..\..\bitmaps\ea.bmp' align=center.
+:p.
 This dialog allows you to view and edit text Extended Attributes (EAs)
 for an object.  Binary EAs may be viewed but not edited.  You'd have to
+for an object. Binary EAs may be viewed but not edited. You'd have to
 be the sort who enjoys programming on a hex keypad to :hp2.want:ehp2. to
 edit a binary EA...
 …
 :p.
 :hp1.Multi-value single-type EAs:ehp1. are shown in an MLE control if
 the type is text.  Each line represents one 'record' of the EA.
+the type is text. Each line represents one 'record' of the EA.
 :p.
 :hp1.Multi-value mult-type EAs:ehp1. are also shown in an MLE control
 if all types are text.  Each line represents one 'record' of the EA.
+:hp1.Multi-value multi-type EAs:ehp1. are also shown in an MLE control
+if all types are text. Each line represents one 'record' of the EA.
 :p.
 In general, if you don't know the purpose of an EA you shouldn't change
 it.  In particular, EA names beginning with a period (i.e. .TYPE), as
 these EAs are used by the WPS.  An exception is the .SUBJECT EA, for
 which FM/2 provides a special context menu item.  This EA is used to
 store a simple text description of an object.  FM/2's details views can
+it. In particular, EA names beginning with a period (i.e. .TYPE), since
+these EAs are used by the WPS. An exception is the .SUBJECT EA, for
+which FM/2 provides a special context menu item. This EA is used to
+store a simple text description of an object. FM/2's details views can
 show this description and allow you to direct-edit it.
 :p.
 …
 See :link reftype=launch object='CMD.EXE' data='/C HELP
 EAUTIL'.EAUTIL:elink. in OS/2's Command Reference for more information
 on EAs and how to manipulate them.  Note that this dialog is not meant
+on EAs and how to manipulate them. Note that this dialog is not meant
 to be a full-featured super-powerful EA editor (though it does a decent
 job with text EAs and beats the pants off what comes with other file
 managers -- if anything at all comes with them, that is).  You can use
+managers -- if anything at all comes with them, that is). You can use
 :hp1.Config->Edit Commands:ehp1. to add such an external EA editor to a
 list of commands that you can run on selected files, if desired.
 …
 :i1 id=aboutADDEA.Adding an Extended Attribute
 To add an extended attribute (EA), enter its name in the top entry
 field, then select a type for it from the radio buttons.  Click Okay to
+field, then select a type for it from the radio buttons. Click Okay to
 create it, Cancel to abort.
 :p.
 OS/2 defines several Standard Extended Attributes (SEAs):
+OS/2 defines several Standard Extended Attributes (EAs):
 :p.
 :hp1..ASSOCTABLE:ehp1. is a multi-value multi-type (MVMT) EA.  FM/2 will
+:hp1..ASSOCTABLE:ehp1. is a multi-value multi-type (MVMT) EA. FM/2 will
 not create one of these, but you can with the Association page of a
 program object in the WPS.
 :p.
 :hp1..CLASSINFO:ehp1. is a binary attribute.  FM/2 will not create one
 of these, but the WPS does automagically as required.
+:hp1..CLASSINFO:ehp1. is a binary attribute. FM/2 will not create one
+of these, but the WPS does automatically as required.
 :p.
 :hp1..ICON:ehp1. is an icon attribute.  FM/2 will not create one of these
+:hp1..ICON:ehp1. is an icon attribute. FM/2 will not create one of these
 via the EA dialog, but you can change the icon of a file system object in
 other, more direct, ways with FM/2.
 :p.
 :hp1..CODEPAGE:ehp1. is an attribute (don't know the type).  FM/2 won't
+:hp1..CODEPAGE:ehp1. is an attribute (don't know the type). FM/2 won't
 make one.
 :p.
 …
 :p.
 :hp1..SUBJECT:ehp1. is an ASCII attribute (see a file object's File page).
 This describes the object.  FM/2 makes use of these for you.
+This describes the object. FM/2 makes use of these for you.
 :p.
 :hp1..COMMENTS:ehp1. is an MVMT attribute (see a file object's third
 …
 :p.
 :hp1..KEYPHRASES:ehp1. is an MVMT attribute (see a file object's third
 File page).  OS/2 documentation describes this as an MVST, but the WPS
+File page). OS/2 documentation describes this as an MVST, but the WPS
 objects create MVMTs.
 :p.
 …
 :hp1..LONGNAME:ehp1. is an ASCII attribute that gives the full name of a
 file when stored on a file system that doesn't support long filenames
 (like FAT).  Sometimes you'll see them even on files stored on HPFS
+(like FAT). Sometimes you'll see them even on files stored on HPFS
 drives, when invalid characters (invalid for the file system, like
 a colon not used for a path separator, for example) are used.
 …
 :p.
 When creating attributes of your own, you should :hp2.not:ehp2. begin
 them with a period.  Try using a convention like "JOES.ATTRIBUTE"
+them with a period. Try using a convention like "JOES.ATTRIBUTE"
 (yourname.attribtag) to make sure it doesn't conflict with the WPS or
 any apps you may run.
+any applcations you run.
 :p.
 &period.SUBJECT, .COMMENTS and .KEYPHRASES can be modified, deleted and
 added by the user without problem.  The other standard EAs are the
 domain of apps and the WPS and should be left alone.  You can, of
+added by the user without problem. The other standard EAs are the
+domain of apps and the WPS and should be left alone. You can, of
 course, create your own EAs and manipulate them with REXX or other types
 of programs.

trunk/dll/ipf/editor.ipf

-              r10
+              r268
 :artwork name='..\..\bitmaps\view.bmp' align=center.
+:p.
 The internal viewer is used to view files unless you have an external
 viewing program defined in the internal Settings notebook's :link
 reftype=hd res=92200.Viewers page:elink., or the :hp2.Fast internal
 viewer:ehp2. checkbox :hp1.off:ehp1..  This viewer loads and displays a
+viewer:ehp2. checkbox :hp1.off:ehp1.. This viewer loads and displays a
 one megabyte text file in less than two seconds on a 486/66. The :link
 reftype=hd res=93900."old" viewer:elink. loads large text files
 …
 :p.
 Both :link reftype=hd res=98800.hex:elink. and ASCII (plain text)
 display modes are supported, and a variety of text sizes.  These
+display modes are supported, and a variety of text sizes. These
 controls are under the :hp1.View:ehp1. pulldown submenu.
 :p.
 Selected lines are displayed in reverse video (white text on a black
 background).  The current line has a ">" pointing at it in the left
 margin.  Single selections and swipe selections are supported, as well
+background). The current line has a ">" pointing at it in the left
+margin. Single selections and swipe selections are supported, as well
 as select and deselect all (under the :hp1.Select:ehp1. pulldown
 submenu) and select/deselect all "found" lines (see :hp1.Search:ehp1.
 below).  Keyboard selection is performed with the spacebar, or you can
+below). Keyboard selection is performed with the spacebar, or you can
 hold down the Shift key while moving the cursored selection with the
 arrow keys.  Discontiguous lines can be selected.
+arrow keys. Discontiguous lines can be selected.
 :p.
 If you double-click a line in the viewer window, a listbox appears above
 the text containing that line.  Select (single-click) the line in the
+the text containing that line. Select (single-click) the line in the
 listbox and the viewer window will scroll to that line -- a sort of
 instant bookmarking facility.  To remove a line from this bookmark
 listbox, double-click it in the listbox.  See the :link reftype=hd
+instant bookmarking facility. To remove a line from this bookmark
+listbox, double-click it in the listbox. See the :link reftype=hd
 res=97600.FM/2 window layouts:elink. topic for a picture to help you
 understand this one -- or just try it.
 :p.
 The :hp1.Clipboard:ehp1. pulldown submenu allows you to save selected
 lines to the clipboard or a file.  :hp7.Warning&colon.:ehp7.  Warp
+lines to the clipboard or a file. :hp7.Warning&colon.:ehp7. Warp
 appears to have a 64K limit to the size of text that can be placed in
 the clipboard.  You can also save lines that you've double-clicked into
 the bookmark listbox.  When you write lines to a file, you append to the
+the clipboard. You can also save lines that you've double-clicked into
+the bookmark listbox. When you write lines to a file, you append to the
 file (if it already exists).
 :p.
 When you search for text in the file, you can search for more than one
 "phrase" at a time.  Each line you fill into the MLE on the
 :hp1.Search->Find text:ehp1. dialog is a separate search string.  You
+"phrase" at a time. Each line you fill into the MLE on the
+:hp1.Search->Find text:ehp1. dialog is a separate search string. You
 can also search case sensitively (i.e. 'A' doesn't match 'a'), translate
 C-like :link reftype=hd res=99500.\-encoded characters:elink. (\r = a
 …
 and/or select lines as they're found by checking the appropriate
 checkboxes on the Find First dialog. All matching lines are displayed in
 red.  The :hp1.Search->Next found line:ehp1. command moves to the next
+red. The :hp1.Search->Next found line:ehp1. command moves to the next
 highlighted line in the file (from the current position), and
 :hp1.Search->Previous found line:ehp1. moves to the previous highlighted
 line.  Colors are configurable.
+line. Colors are configurable.
 :p.
 If you're looking for more powerful viewing software, you might be
 interested in Michael Schacter's :hp1.Hyperview PM:ehp1. shareware
+program.  Michael can be contacted on Compuserve at user ID 76170,1627,
+and hangs out in the OS2SHARE (library 1 of OS2BVEN) forum. You can
+program. Now orphan ware it can still be found online. You can
 easily set Hyperview up to be used automatically by FM/2 using the :link
 reftype=hd res=92200.Viewers page:elink. of the internal Settings
 …
 :artwork name='..\..\bitmaps\edit.bmp' align=center.
 :artwork name='..\..\bitmaps\view.bmp' align=center.
+The internal viewer/editor is an extremely simplistic MLE window.  It is
+:p.
+The internal viewer/editor is an extremely simplistic MLE window. It is
 :hp2.strongly:ehp2. recommended that you replace it with a better one
 via the :link reftype=hd res=94600.Settings Notebook:elink.'s :hp1.:link
 reftype=hd res=92200.Viewers page:elink.:ehp1..  The reasons are
+reftype=hd res=92200.Viewers page:elink.:ehp1.. The reasons are
 simple&colon. a product designed specifically and exclusively for
 editing will generally do a better job, and MLEs tend to be sluggish
 when loading anything larger than about 58K.
 :p.
+Suggestions&colon. EPM (which comes with OS/2), or QEdit for OS/2 (an
+excellent and inexpensive text-mode editor from Semware highly
+recommended, and used, by FM/2's author) or Visual Slickedit by
+Microedge, PM and more powerful (and, of course, more expensive) than
+QEdit, also used by the author.  There are many other editors, freeware,
+shareware and shrinkwrap, available, I simply listed those with which I
+have some familiarity and feel I can recommend as very good software.
+Suggestions&colon. EPM (which comes with OS/2), There are other editors
+available.
 :p.
 There's :link reftype=hd res=99300.another, faster internal viewer (no
 …
 :p.
 The internal viewer/editor creates a window for each file being viewed/
 edited.  The :link reftype=hd res=91100.Windows->Dialog:elink. dialog
+edited. The :link reftype=hd res=91100.Windows->Dialog:elink. dialog
 can be used to quickly close several windows at once or find a
 particular window and bring it to the front.
 :p.
 :hp7.Note:ehp7. that when saving files the editor formats the file so
 that it appears as it does in the MLE.  The appearance of a file can be
+that it appears as it does in the MLE. The appearance of a file can be
 different in the MLE or in the created disk file depending on various
 settings under the editor's :hp1.Config->Format Control:ehp1., notably
 Wrap.  :hp8.Be sure you have these settings right for the way you want
+Wrap. :hp8.Be sure you have these settings right for the way you want
 the resultant file to look.:ehp8.
 :p.
 …
 FM/2 will allow you to change the codepage (character set) in use in the
 internal viewer by selecting a codepage from the listbox.  The codepage
+internal viewer by selecting a codepage from the listbox. The codepage
 must be one of those supported in your CONFIG.SYS (see :link
 reftype=launch object='CMD.EXE' data='/C HELP CODEPAGE'.CODEPAGE:elink.
 …
 In many areas, FM/2 allows you to use C-style backslash encoding (or
 more properly "escaping") to give constants you normally couldn't enter
 into an entry field or MLE.  There are some differences from standard
+into an entry field or MLE. There are some differences from standard
 C escaping, so pay attention.
 :p.

trunk/dll/ipf/errors.ipf

-              r2
+              r268
         or bad EAs in list.
   ERROR_EA_LIST_TOO_LONG
         FEAList > 64K-1 bytes.
+        EAList > 64K-1 bytes.
   ERROR_NO_MORE_ITEMS
         DosQFSAttach ordinal query.
 …
         Volume changed.
   ERROR_EAS_DIDNT_FIT
         EAS didnt fit.
+        EAS didn't fit.
 :exmp.
+Additional information for some error codes can be obtained by typing "Help <Error code &numsign.>"
+on an OS/2 command line.

trunk/dll/ipf/expert.ipf

-              r2
+              r268
 Lists:elink. and :link reftype=hd res=98900.Opening a Directory
 Container:elink. -- they'll contain some FM/2-specific info you'll
 need or be able to use up front.  You might also want to take a look
+need or be able to use up front. You might also want to take a look
 at the internal :link reftype=hd res=94600.Settings Notebook:elink.
 and its help to see how you can customize FM/2's behavior to your taste.
 …
 that link-dragging (holding Ctrl + Shift while dragging) is used to do
 comparing within FM/2 (still creates shadows when dropping on WPS
 objects).  Direct renaming works as expected.  Context menus can be
 requested on objects for other functions.  Double-clicking opens objects
 in the "best guess" view.  In other words, it works more-or-less like
+objects). Direct renaming works as expected. Context menus can be
+requested on objects for other functions. Double-clicking opens objects
+in the "best guess" view. In other words, it works more-or-less like
 the WPS with file maintenance-specific functionality added.
 :p.
 You now know how to do the basic file system maintenance operations
 (copy, move, delete, rename, etc.) -- go for it, and have fun.  The rest
+(copy, move, delete, rename, etc.) -- go for it, and have fun. The rest
 of the help will wait until curiosity gets the better of you -- and it
 will.  &colon.-)
+will. &colon.-)
 :p.
 :artwork name='bitmaps\expert.bmp' align=center.

trunk/dll/ipf/filter.ipf

-              r10
+              r268
 :i1 id=aboutFilter.Filter container
 :artwork name='..\..\bitmaps\filter.bmp' align=center.
+This dialog allows you to filter what's shown in a container.  A
+:p.
+This dialog allows you to filter what's shown in a container. A
 filemask or filemasks can be used to filter, and so can file attributes
 (except for archive listings where attributes are not applicable).  In
+(except for archive listings where attributes are not applicable). In
 addition, you can set attributes that _must_ be present on the objects
 to be shown (for instance, if you check :hp1.Hidden:ehp1. in the
 "Must-have Attribs" group, only objects with their hidden attribute set
 will show up).  You can specify whether FM/2 should always show
+will show up). You can specify whether FM/2 should always show
 directories whether they match the mask(s) or not by checking the
 :hp1.Always show directories:ehp1. checkbox to keep them visible.
 …
 :hp2.To be sure that everything in a container is displayed, clear any
 filemask, check all attributes in the Attribs groupbox and clear
 all attributes in the Must-have Attribs groupbox.:ehp2.  You can click
+all attributes in the Must-have Attribs groupbox.:ehp2. You can click
 the :hp1.All:ehp1. button to set the filter to show everything.
 :p.
 As you enter filemasks they're saved for later redisplay in this
 dialog's listbox.  If a filemask desired is in the listbox you can use
 it by selecting it (double-clicking it).  You can get rid of a mask in
+dialog's listbox. If a filemask desired is in the listbox you can use
+it by selecting it (double-clicking it). You can get rid of a mask in
 the listbox by highlighting it and clicking :hp1.Delete:ehp1..
 :p.
 …
 Some characters have the following special meaning:
 :p.
  :hp1.?:ehp1.  A question mark matches one character, unless what it would
+ :hp1.?:ehp1. A question mark matches one character, unless what it would
 match is a period, slash or backslash, in which case it matches no
 characters.
 :p.
  :hp1.*:ehp1.  An asterisk matches characters from the source to the target
+ :hp1.*:ehp1. An asterisk matches characters from the source to the target
 until it finds a filename character that matches the non-wild character
 following it in the filemask, or a period, slash, backslash or
 …
 Up to 24 masks may be "cascaded" by separation with semicolons.
 When specifying multiple filemasks, you can use '/' as the first character
 of a mask to mean _don't_ match this filespec.  Exclusions should usually
+of a mask to mean _don't_ match this filespec. Exclusions should usually
 be listed before inclusions to attain the desired effect.
 :p.
 …
 :eparml.
 :p.
 :hp1.A reminder&colon.:ehp1.  CD-ROM files are marked ReadOnly and will
+:hp1.A reminder&colon.:ehp1. CD-ROM files are marked ReadOnly and will
 not appear in your containers unless you have the ReadOnly attribute on
 (checked).  If you copy these files to your hard drive the ReadOnly
+(checked). If you copy these files to your hard drive the ReadOnly
 attribute goes with them; use the menu command
 :hp1.Files->Edit->Attribs:ehp1. (Ctrl + a accelerator) to reset it (you
 …
 :p.
 This dialog also appears when you are selecting or deselecting file system
 objects using a mask.  In this case, attribute information will be greyed
 out and an additional entry field (:hp1.Text&colon.:ehp1.) appears.  You
+objects using a mask. In this case, attribute information will be grayed
+out and an additional entry field (:hp1.Text&colon.:ehp1.) appears. You
 can enter text into this entry field, and only files containing the text
 and matching the mask(s) will be (de)selected.  The title bar will remind
+and matching the mask(s) will be (de)selected. The title bar will remind
 you why you called up the dialog.

trunk/dll/ipf/fm3.ipf

-              r10
+              r268
 document, is to look at the :hp2.Contents:ehp2. (which you'll get if you
 press Ctrl + F1 at the main window -- it may help you to maximize it
 within the help window).  The Contents view of a help file is something
+within the help window). The Contents view of a help file is something
 like the Table of Contents in a book, with each major topic representing
 a chapter.  Some topics have a "+" sign beside them to indicate that
+a chapter. Some topics have a "+" sign beside them to indicate that
 there are subtopics available in a hierarchal inverted tree structure;
 click the "+" and they'll be revealed.
 :p.
 The help sometimes has hypertext links shown in a different color, like
 the words "Context menu" a few paragraphs below.  You can select these
+the words "Context menu" a few paragraphs below. You can select these
 links to switch to a different topic related to the highlighted word(s).
 In this way you can browse through the help, moving from topic to topic
+as you feel the need for more specific help.  The :hp1.Previous:ehp1.
+button (or the Escape key) will move backwards through the hypertext
+links you've followed.
+as you feel the need for more specific help. The :hp1.Previous:ehp1. button
+ (IBM's view.exe)or the :hp1.Back:ehp1. button (NewView)
+(or the Escape key) will move backwards through the hypertext
+links you've followed. Please note that in "NewView" the :hp1.Previous:ehp1.
+and  :hp1.Next:ehp1. buttons navigate up and down the table of contents
+while the :hp1.Back:ehp1. and :hp1.Forward:ehp1. buttons navigate hyperlinks
 :p.
 To find something on a specific topic, click the :hp2.Search:ehp2.
+button at the bottom of the help window and enter some text.  This might
+button at the bottom of the help window and enter some text (IBM's view.exe)
+or use the search tab (NewView). This might
 be analogous to the index at the back of a book (although the help
 manager also provides an "index" of its own, which is something like the
 …
 :p.
 To find out about changing a volume label, enter "Label" as the "Search
 for&colon." text, check the "All sections" checkbox, then press [Enter].
+for&colon." text, check the "All sections" checkbox, if present, then press [Enter].
 :p.
 To find out how to open a new FM/2 window, enter "Open" as the "Search
 for&colon." text, check the "All sections" checkbox, then press [Enter].
+for&colon." text, check the "All sections" checkbox, if present, then press [Enter].
 :p.
 If you'd like a printout of any of the topics in the online help, click
 the :hp2.Print:ehp2. button at the bottom of the help window.  The :link
 reftype=hd res=93700.Context menu:elink. help topic would probably be a
 good one to print out.  Gives you something to read in the john.
+the :hp2.Print:ehp2. button at the bottom ("IBM's" View.exe) or top (NewView.exe) of the help
+window. The :link reftype=hd res=93700.Context menu:elink. help topic would probably be a
+good one to print out. Gives you something to read in the john.
 Remember that you can also use the :hp1.FM/2 Online Help:ehp1. icon in
 the FM/2 folder to view the help without starting FM/2 itself.
 :p.
 If you're stuck in a dialog, click that dialog's Help button.  That will
 usually take you directly to appropriate help.  One note of caution:
+If you're stuck in a dialog, click that dialog's :hp2.Help button:ehp2. That should
+take you directly to appropriate help. One note of caution:
 if you call up help for a dialog, be sure to dismiss the help before
 dismissing the dialog.  Many of the dialogs run in threads other than
+dismissing the dialog. Many of the dialogs run in threads other than
 thread 1 (the main thread), and there's a long-standing OS/2 bug that
+causes weird behavior if you do it the other way around to a dialog run
+in a thread other than thread 1.  Trust me.
+:p.
+So, if you're totally new to FM/2, :hp1.how to get started?:ehp1.
+First, run the :hp2.OS/2 Tutorial:ehp2. if you need help on the basics
+of using a mouse in general or using one with OS/2 in particular.  Next,
+read the help section titled :link reftype=hd
+causes weird behavior if you close a dialog run
+in a thread other than thread 1 after before closing its help file. Trust me.
+:p.
+So, if you're totally new to FM/2, :hp1.here is how to get started.:ehp1.
+First, read the help section titled :link reftype=hd
 res=91300.Terminology:elink. so we'll understand each other a bit
 better.  If you're still nervous about OS/2 conventions, try FM/2's
 :link reftype=hd res=99800.Tutorial:elink. topic for real hand-holding.
+better. If you're still nervous about OS/2 conventions, try FM/2's
+:link reftype=hd res=99800.Tutorial:elink. section for real hand-holding.
 Get an overview of some important FM/2 windows in the :link reftype=hd
 res=97600.Window layouts:elink. topic.  Then plunge into the :link
 reftype=hd res=90000.General Help:elink. topic to find out how to look
+res=97600.Window layouts:elink. section. Then plunge into the :link
+reftype=hd res=90000.General Help:elink. section to find out how to look
 at, Move, Copy, Rename and Compare files and directories (the basics).
 That will get you started, and we'll give you hints along the way about
 other places you might like to look (like :link reftype=hd
 res=93000.Hints:elink. &colon.-) when you're ready.  The previously
+res=93000.Hints:elink. &colon.-) when you're ready. The previously
 mentioned :link reftype=hd res=93700.Context menus:elink. topic will
 give you an overview of all the commands available in FM/2 (and there
 …
 notebook:elink. (accessible under the :link reftype=hd
 res=92000.Config:elink. menu), specifically at the :link reftype=hd
 res=99200.Quick page:elink..  There you'll see a few "standard"
 configurations you can try out to perhaps get an idea of the range of
 appearance and performance you can get out of FM/2 via the Settings
+res=99200.Quick page:elink.. There you'll see a few "standard"
+configurations you can try out to get an idea of the range of
+appearance and performance you can obtain from FM/2 via the Settings
 notebook and Config menu.
 :p.
 Command line help is in the :link reftype=launch object='E.EXE'
 data='READ.ME'.READ.ME:elink. file that accompanied the archive,
+data='\FM2\README'.README:elink. file that accompanied the archive,
 since you should have read that before trying to start FM/2. You did,
+didn't you?
+:p.
+There is one thing you should keep in mind about FM/2.  FM/2 is
+didn't you? Note&colon. This link only works if FM/2 is installed
+to a directory named FM2 on the boot drive. If not go to your FM/2
+install directory and double-click B1 on the file "README".
+:p.
+There is one thing you should keep in mind about FM/2. FM/2 is
 extremely powerful and has a lot of features, but :hp6.you don't have to
 use or even know them all:ehp6..  Most people will use only a few of
+use, understand or even know about them all:ehp6.. Most people will use only a few of
 FM/2's features on a regular basis (and not everyone will use the same
 combination), and that's fine -- find what works best for you and
 :hp2.use:ehp2. it.  If you find yourself needing some other feature,
+:hp2.use:ehp2. it. If you find yourself needing some other feature,
 call up the help, find it, and use it -- it'll be there whenever you
 need it.  But don't feel that, somehow, by not using every little nook
 and cranny of the program that you're missing out on something.  The
+need it. But don't feel that, somehow, by not using every little nook
+and cranny of the program that you're missing out on something. The
 idea is to use what you need; pick your tools from the arsenal and get
 some work done.
 …
 On the other hand, always assume that there's a way to do what you want
 with FM/2 (chances are good that there is), and ask the help window to
+Search for it.  If you can't find it there, drop me a line.
+Search for it. If you can't find it there, drop me a line at steve53@earthlink.net
+:h1 res=90000 name=PANEL_GENERAL.General Help
+:i1 id=aboutGeneral.General Help
+FM/2's main purpose is to show you what's on your file system and let you
+sling what's there around.
+:p.
+Here we'll cover the basics. Some familiarity with OS/2's WPS
+(WorkPlace Shell) is assumed. If you need refreshing, review the :link
+reftype=launch object='View.EXE' data='OS2UG.INF'.OS/2 Desktop Guide:elink.
+It's also assumed that you've already read the :link
+reftype=hd res=93200.How to use FM/2's help:elink. and :link reftype=hd
+res=91300.Terminology:elink. sections. If you feel that you need more
+in-depth help when we're through with this topic, try FM/2's :link
+reftype=hd res=99800.Tutorial:elink. section. Also review the FM/2 default
+:link reftype=hd res=100040.Mouse actions:elink. and a list of FM/2 :link reftype=hd
+res=100005.Accelerator (shortcut) Keys:elink.
+:p.
+There are several ways to view a directory with FM/2, just as there are
+with the WPS. Icon, Name, Text and Details views all offer different
+perspectives into the directory being "looked at" (see :link reftype=hd
+res=91300.Terminology:elink.). Views showing icons can use full-sized
+icons or smaller "mini-icons" to save space.
+:p.
+Details view can show a great deal of information about file system
+objects, and you can customize what is shown with the :hp2.Details
+Setup:ehp2. submenu (:link reftype=hd res=93800.Views
+menu:elink. or a Directory Container:link reftype=hd
+res=93700.context menu:elink.).
+:p.
+You can also place some limits on the amount of detail that FM/2 provides
+from the file system on the :link reftype=hd res=92400.Toggles:elink.
+page of the :link reftype=hd res=94600.Settings notebook:elink.. This
+can speed up FM/2's scanning of directories but can also make for duller
+screens with less information being presented to you. My advice to you
+is enjoy the bells and whistles OS/2 and PM provide.
+:p.
+Take a moment to set up the look of your Directory Container windows
+to match your taste -- everyone likes something different. Then meet
+me back here and we'll talk about manipulating those objects you see...
+:p.
+.br
+As we talk about manipulating objects, keep firmly in mind the concepts
+of :link reftype=hd res=98000."current object" and "highlighted
+objects":elink.. The current object is the one on which commands act (it
+has the dotted outline around it). If the current object is also
+highlighted, all highlighted objects will be affected.
+:p.
+:artwork name='..\..\bitmaps\rename.bmp' align=center.
+:p.
+:hp1.Renaming file system objects&colon.:ehp1.
+The simplest way to rename a file system object is to point at it with
+the mouse pointer, hold down the ALT key, and click the text of its name.
+FM/2 produces a mini MLE text entry field where you can type in a new
+name (this is :link reftype=hd res=98200.Direct Editing:elink.). When
+finished, click the object and a rename is performed. Note that you can
+even move the object to another directory when you do this (Also note
+that in Details view you can direct-edit the Subject field to change an
+object's Subject, and the Longname field to change an object's Longname
+on FAT drives.).
+:p.
+Using this method will not allow you to overwrite an existing file. You
+can use drag and drop (as detailed below for Move), the menu command
+:link reftype=hd res=91400.Rename:elink. or the :link reftype=hd
+res=91800.toolbar:elink. to facilitate overwriting.
+:p.
+If you'd like more detail, go to the :link reftype=hd
+res=99810.Rename:elink. tutorial.
+.br
+:artwork name='..\..\bitmaps\mover.bmp' align=center.
+:p.
+:hp1.Moving file system objects&colon.:ehp1.
+.br
+There are several ways to move a file system object. The most
+intuitive is :hp2.drag and drop:ehp2.. Using this method, you "grab"
+the file system object by pressing and holding B2 while the mouse
+pointer is over the object, then begin to move the mouse (still holding
+B2). The object's icon should begin to move with the mouse pointer.
+"Drag" this icon to where you want to move it (for instance, if you want
+to move a file from C&colon.\ to D&colon.\, drag the file to the Drive
+Tree's D&colon.\ object). When the object is where you want it, release
+B2 and the move is done.
+:p.
+When dragging an object into a Directory Container, remember that to
+place it into the directory into which the Directory Container "looks"
+you need to drop it on container "whitespace" (a part of the container
+not occupied by an object). For convenience, the two large status
+areas at the top of the container are considered whitespace.
+:p.
+If you get confused when dragging object(s), press the F1 key. This
+will give you some information about what you're doing. Pressing the
+Escape key will abort the drag.
+:p.
+Note that you can't move a file or directory onto another file (except
+for archive targets), only into a directory (moving into container
+whitespace in a Directory Container window is the same as moving into
+the directory the Directory Container "looks" into, and a minimized
+Directory Container window is "all whitespace"). Also note that the
+object you grab becomes the current object, and if it's also highlighted
+you'll drag all highlighted objects (you'll see visual feedback to this
+effect).
+:p.
+You could, of course, also select "Move" from the :hp1.:link reftype=hd
+res=93300.Files:elink.:ehp1. menu, a context menu, click the Move
+toolbar button, or type the accelerator key Ctrl + m (hold the control
+key down and type "m"). In this case, you'll get the :link reftype=hd
+res=91500.Walk Directories:elink. dialog where you can enter a target
+directory.
+:p.
+If you'd like more detail, go to the :link reftype=hd
+res=99820.Move:elink. tutorial.
+.br
+:artwork name='..\..\bitmaps\copier.bmp' align=center.
+:p.
+:hp1.Copying file system objects&colon.:ehp1.
+.br
+The procedure for copying file system objects is very similar to that
+for moving them. When you begin to drag the object, and until you
+release it, hold down the control (Ctrl) key. You'll notice that the
+dragged icon is "ghosted" to give visual feedback that a copy, not a
+move, is being performed. Note that you can copy a file onto an archive
+file as well as into a directory. You can also "clone" a file by dropping
+it into the directory where it already resides -- you'll get a rename
+dialog that will allow you to change the name, creating a file exactly
+like the other with a different name.
+:p.
+As for move above, there is a "Copy" menu item, a toolbar button,
+and Ctrl + c is the accelerator key.
+:p.
+If you'd like more detail, go to the :link reftype=hd
+res=99830.Copy:elink. tutorial.
+.br
+:artwork name='..\..\bitmaps\linkdrag.bmp' align=center.
+.br
+:hp1.Comparing file system objects&colon.:ehp1.
+.br
+There is one other type of drag and drop operation called a "link drag."
+To link drag, hold down the Ctrl and Shift keys while dragging.
+You'll see a "rubber band line" extend from where you grabbed the icon
+to the mouse pointer as a visual cue. Link dragging is usually used
+within FM/2 to do compare operations (see also :link reftype=hd
+res=99950.:hp2.Link Sets Icon:ehp2. toggle:elink.). What you drag will
+be compared to what you drop it on. Note, however, that if you drag to
+a WPS object (like the desktop or other folder), OS/2's version of a
+link drag is performed, which usually results in the creation of an object shadow
+If you'd like more detail, go to the :link reftype=hd
+res=99840.Compare:elink. tutorial.
+:p.
+Double-clicking an object in a Directory Container window causes its
+:hp1.default action:ehp1. to occur. What that action is depends on
+the type of object and how you've configured FM/2. Briefly, the FM/2
+defaults (which you can override) cause the object to be opened in the
+most likely manner. You can :link reftype=hd res=100060.read about this
+in more detail here:elink. in the tutorial section.
+:p.
+Other commands are accessed via :link reftype=hd
+res=97700.pulldown:elink.,  :link reftype=hd res=93700.context
+menu:elink. commands, toolbar buttons or accelerator keys. You can read about them by
+selecting the highlighted words "context menu" in this paragraph. FM/2
+also offers several general :link reftype=hd res=92100.utilities:elink.
+and many :link reftype=hd res=92000.configuration:elink. options which
+you may want to explore. But you now know how to perform the file system
+maintenance basics: Move, Copy, Rename and Compare. You are now, as the
+Smothers Brothers said, educated.
+:p.
+For more specific information on FM/2, click the :hp2.Contents:ehp2.
+button at the bottom of the help window. If you're still confused on
+the basics, try the FM/2 :link reftype=hd res=99800.Tutorial:elink.
+topic. You might also want to look at the :link reftype=hd
+res=98900.Opening a Directory Container:elink., :link reftype=hd
+res=99400.Using quicklists:elink. and :link reftype=hd res=97600.Window
+layout:elink. sections.
+.im mouse.ipf
+.im keys.ipf
 :h1 res=97600 name=PANEL_FM2WINDOWLAYOUT.FM/2 Window Layouts
 …
 :artwork align=left name='bitmaps\oall.bmp'.
 :p.
 :hp6.Note&colon.:ehp6.  You can turn optional windows and controls on
 and off.  Pick the ones you like, get the others out of your way (see
 the Config menu).  Surely no one uses all of them at the same time...
+:hp6.Note&colon.:ehp6. You can turn optional windows and controls on
+and off. Pick the ones you like, get the others out of your way (see
+the Config menu). Surely no one uses all of them at the same time...
 The autoview window, bottom buttons, quicklists, toolbar, drive buttons,
 status line #2, and even the pulldown menu can all be turned on and off
 …
 activate commands when clicked.
 :p.
 The :hp1.Toolboxes quicklist:ehp1. only appears when the
 :hp1.Toolbar:ehp1. is visible (see :link reftype=hd res=99400.Using
 quicklists:elink. topic).
 :p.
 Status bar #1 can be clicked to shift the focus to FM/2 without
 activating any commands.  In addition, if the Drive tree is the
+The :hp1."Toolboxes" quicklist:ehp1. only appears when the
+:link reftype=hd res=91800.Toolbar:elink. is visible (see :link reftype=hd res=99400.Using
+quicklists:elink. section).
+:p.
+Status line #1 can be clicked to shift the focus to FM/2 without
+activating any commands. In addition, if the Drive tree is the
 active window within FM/2's monolithic window, the Swapfile and
 memory available indicators in Status bar #2 will be immediately
 updated (otherwise they update about once every ten seconds).
 :p.
 You can get information on most parts of the window just by moving the
 mouse pointer over the part of interest (unless you've turned off
 bubble help in the internal Settings notebook).  For help with the
+memory available indicators in Status line #2 will be continuously
+updated (otherwise they update about every ten seconds).
+:p.
+You can get information on most areas of the window just by moving the
+mouse pointer over the area of interest (unless you've turned off
+bubble help in the internal Settings notebook). For help with the
 quicklists, which don't have bubble help, see :link reftype=hd
+res=99400.this topic:elink..
+:p.
+.br
+Here's a Directory Container window in more detail&colon.
+res=99400.Using quicklists:elink..
+:p.
+.br
+Here's a Directory Container window in more detail&colon. See
+:link reftype=hd res=98900.Opening a Directory Container:elink. and
+:link reftype=hd res=91900.Folder Button:elink. for more information
+:p.
 :artwork align=left name='bitmaps\dircnr.bmp'.
 :p.
 Here's :link reftype=hd res=100000.FM/2 Lite:elink. with an explanation
+of the things that are unique to it (except for the Alt-click to change
+sort in Details view -- that works in FM/2, too).  The toolbar and
+Autoview windows have been turned off to unclutter this illustration.
+of the things that are unique to it (Note&colon. Alt-click to change
+sort in Details view also works in FM/2). The
+Autoview window has been turned off to unclutter this illustration.
+:p.
 :artwork align=left name='bitmaps\fm4oall.bmp'.
 :p.
 Note that the current window, which would be affected by a pulldown menu
+command, is surrounded by a light red border.  In this case, it's the
 Drive Tree, so the Directory Container, or pane, that would change if a
 directory were double-clicked in the Tree is surrounded by a darker red
 border.  This color coding gives you instant feedback as to how the
 commands you select will work.
 :p.
 .br
 Here's a look at the text file viewer window -- the default text file
 viewer built into FM/2 that you get when you double-click a text file in
+Note that the active window, the window pulldown menu commands will
+effect, is surrounded by a light red border. When the Drive Tree is active as
+shown above the Directory Container that would change if a
+directory were double-clicked in the Tree is surrounded by a fine darker red
+border. This color coding gives you instant feedback as to what the
+commands you select will effect.
+:p.
+.br
+Here's a look at the default text file
+viewer built into FM/2. It is opened when you double-click a text file in
 a Directory container (you can configure a different one if you
 like)&colon.
+.br
 :artwork align=left name='bitmaps\newview.bmp'.
 :p.
 Here's how the window looks if you double-click some lines of text&colon.
+.br
 :artwork align=left name='bitmaps\newview2.bmp'.
+Here we've used the bookmark listbox (which we filled by double-clicking
+some lines of text) to make an index for the document being read, to
+enable us to move to different sections quickly.  See the :link
+reftype=hd res=99300.Internal viewer:elink. topic for more information.
+:h1 res=90000 name=PANEL_GENERAL.General Help
+:i1 id=aboutGeneral.General Help
+FM/2's main purpose is to show you what's on your file system and let you
+sling what's there around.
+:p.
+Here we'll cover the basics.  Some familiarity with OS/2's WPS
+(WorkPlace Shell) is assumed.  If you need refreshing, run the OS/2
+Tutorial.  It's also assumed that you've already read the :link
+reftype=hd res=93200.How to use FM/2's help:elink. and :link reftype=hd
+res=91300.Terminology:elink. topics.  If you feel that you need more
+in-depth help when we're through with this topic, try FM/2's :link
+reftype=hd res=99800.Tutorial:elink. topic.
+:p.
+There are several ways to view a directory with FM/2, just as there are
+with the WPS.  Icon, Name, Text and Details views all offer different
+perspectives into the directory being "looked at" (see :link reftype=hd
+res=91300.Terminology:elink.).  Views showing icons can use full-sized
+icons or smaller "mini-icons" to save space.
+:p.
+Details view can show a great deal of information about file system
+objects, and you can customize what is shown with the :hp2.Details
+Setup:ehp2. submenu (under the :link reftype=hd res=93800.Views
+menu:elink. or a Directory Container window's :link reftype=hd
+res=93700.context menu:elink.).
+:p.
+You can also place some limits on the amount of detail that FM/2 loads
+from the file system with the :link reftype=hd res=92400.Toggles:elink.
+page of the :link reftype=hd res=94600.Settings notebook:elink..  This
+can speed up FM/2's scanning of directories but can also make for duller
+screens and less information being presented to you.  My advice to you
+is to enjoy the bells and whistles OS/2 and PM provide.
+:p.
+Take a moment to set up the look of your Directory Container windows
+to match your taste -- everyone likes something different.  Then meet
+me back here and we'll talk about manipulating those objects you see...
+:p.
+.br
+As we talk about manipulating objects, keep firmly in mind the concepts
+of :link reftype=hd res=98000."current object" and "highlighted
+objects":elink.. The current object is the one on which commands act (it
+has the dotted outline around it).  If the current object is also
+highlighted, all highlighted objects will be affected.
+:p.
+:artwork name='..\..\bitmaps\rename.bmp' align=center.
+:hp1.Renaming file system objects&colon.:ehp1.
+The simplest way to rename a file system object is to point at it with
+the mouse pointer, hold down the ALT key, and click the text of its name.
+OS/2 produces a mini MLE text entry field where you can type in a new
+name (this is :link reftype=hd res=98200.Direct Editing:elink.).  When
+finished, click the object and a rename is performed.  Note that you can
+even move the object to another directory when you do this.  (Also note
+that in Details view you can direct-edit the Subject field to change an
+object's Subject, and the Longname field to change an object's Longname
+on FAT drives.)
+:p.
+Using this method will not allow you to overwrite an existing file.  You
+can use drag and drop (as detailed below for Move) or the menu command
+:link reftype=hd res=91400.Rename:elink. or the :link reftype=hd
+res=91800.toolbar:elink. to allow overwriting.
+:p.
+If you'd like more detail, go to the :link reftype=hd
+res=99810.Rename:elink. tutorial.
+.br
+:artwork name='..\..\bitmaps\mover.bmp' align=center.
+:hp1.Moving file system objects&colon.:ehp1.
+.br
+There are several ways to move a file system object.  The best and most
+intuitive is :hp2.drag and drop:ehp2..  Using this method, you "grab"
+the file system object by pressing and holding B2 while the mouse
+pointer is over the object, then begin to move the mouse (still holding
+B2).  The object's icon should begin to move with the mouse pointer.
+"Drag" this icon to where you want to move it (for instance, if you want
+to move a file from C&colon.\ to D&colon.\, drag the file to the Drive
+Tree's D&colon.\ object).  When the object is where you want it, release
+B2 and the move is done.
+:p.
+When dragging an object into a Directory Container, remember that to
+place it into the directory into which the Directory Container "looks"
+you need to drop it on container "whitespace" (a part of the container
+not occupied by an object).  For convenience, the two large status
+areas at the top of the container are considered whitespace.
+:p.
+If you get confused when dragging object(s), press the F1 key.  This
+will give you some information about what you're doing.  Pressing the
+Escape key will abort the drag.
+:p.
+Note that you can't move a file or directory onto another file (except
+for archive targets), only into a directory (moving into container
+whitespace in a Directory Container window is the same as moving into
+the directory the Directory Container "looks" into, and a minimized
+Directory Container window is "all whitespace").  Also note that the
+object you grab becomes the current object, and if it's also highlighted
+you'll drag all highlighted objects (you'll see visual feedback to this
+effect).
+:p.
+You could, of course, also select "Move" from the :hp1.:link reftype=hd
+res=93300.Files:elink.:ehp1. menu or a context menu, or click the Move
+toolbar button, or type the accelerator key Ctrl + m (hold the control
+key down and type "m").  In this case, you'll get the :link reftype=hd
+res=91500.Walk Directories:elink. dialog where you can enter a target
+directory.
+:p.
+If you'd like more detail, go to the :link reftype=hd
+res=99820.Move:elink. tutorial.
+.br
+:artwork name='..\..\bitmaps\copier.bmp' align=center.
+:hp1.Copying file system objects&colon.:ehp1.
+.br
+The procedure for copying file system objects is very similar to that
+for moving them.  When you begin to drag the object, and until you
+release it, hold down the control (Ctrl) key.  You'll notice that the
+dragged icon is "ghosted" to give visual feedback that a copy, not a
+move, is being performed.  Note that you can copy a file onto an archive
+file as well as into a directory.  You can also "clone" a file by dropping
+it into the directory where it already resides -- you'll get a rename
+dialog that will allow you to change the name, creating a file exactly
+like the other with a different name.
+:p.
+As for move above, there is a "Copy" menu item and a toolbar button,
+and Ctrl + c is the accelerator key.
+:p.
+If you'd like more detail, go to the :link reftype=hd
+res=99830.Copy:elink. tutorial.
+.br
+:artwork name='..\..\bitmaps\linkdrag.bmp' align=center.
+:hp1.Comparing file system objects&colon.:ehp1.
+There is one other type of drag and drop operation called a "link drag."
+To link drag, hold down the Ctrl and Shift keys while dragging.
+You'll see a "rubber band line" extend from where you grabbed the icon
+to the mouse pointer as a visual cue.  Link dragging is usually used
+within FM/2 to do compare operations (see also :link reftype=hd
+res=99950.:hp2.Link Sets Icon:ehp2. toggle:elink.). What you drag will
+be compared to what you drop it on.  Note, however, that if you drag to
+a WPS object (like the desktop or other folder), OS/2's version of a
+link drag is performed, which usually results in a shadow object being
+created.
+If you'd like more detail, go to the :link reftype=hd
+res=99840.Compare:elink. tutorial.
+:p.
+.br
+Double-clicking an object in a Directory Container window causes a
+:hp1.default action:ehp1. to take place.  What that action is depends on
+the type of object and how you've configured FM/2.  Briefly, the FM/2
+defaults (which you can override) cause the object to be opened in the
+most likely manner.  You can :link reftype=hd res=100060.read about this
+in more detail here:elink. in the tutorial section.
+:p.
+Other commands are accessed via :link reftype=hd
+res=97700.pulldown:elink. or :link reftype=hd res=93700.context
+menu:elink. commands or toolbar buttons.  You can read about them by
+selecting the highlighted words "context menu" in this paragraph.  FM/2
+also offers several general :link reftype=hd res=92100.utilities:elink.
+and many :link reftype=hd res=92000.configuration:elink. options which
+you may want to explore. But you now know how to perform the file system
+maintenance basics: Move, Copy, Rename and Compare.  You are now, as the
+Smothers Brothers said, educated.
+:p.
+For more specific information on FM/2, click the :hp2.Contents:ehp2.
+button at the bottom of the help window.  If you're still confused on
+the basics, try the FM/2 :link reftype=hd res=99800.Tutorial:elink.
+topic.  You might also want to look at the :link reftype=hd
+res=98900.Opening a Directory Container:elink., :link reftype=hd
+res=99400.Using quicklists:elink. and :link reftype=hd res=97600.Window
+layout:elink. topics.
+:h1 res=98900 name=PANEL_GENERALOPEN.Opening a Directory Container
+.br
+Here we're using the bookmark listbox (which is filled by double-clicking
+some lines of text) to make an index for the document,
+enabling us to move from section to section quickly. See the :link
+reftype=hd res=99300.Internal viewer:elink. section for more information.
+See also&colon.
+.br
+:link reftype=hd res=99000.Databar:elink.
+:h2 res=98900 name=PANEL_GENERALOPEN.Opening a Directory Container
 :i1 id=aboutOpeningDirectory.Opening a Directory Container
 There are several ways to open a Directory Container.
 :p.
 The most common is to double-click a directory in the Drive Tree.  If no
 Directory Container windows are open, one is created.  If one or more
+The most common is to double-click a directory in the Drive Tree. If no
+Directory Container windows are open, one is created. If one or more
 Directory Container windows are already open, hold down the Shift key
 while double-clicking (see picture below) -- otherwise the default
 action is to switch the most recently used Directory Container to the
 new directory rather than open a new one.
+:p.
 :artwork name='bitmaps\open.bmp' align=center.
 :p.
 An alternative is to click the :hp1.Open button:ehp1. in the Drive
 Tree's titlebar (see location indicated by the mouse pointer in the
 snapshot below). This opens a window for the directory highlighted in
+picture below). This opens a container for the directory highlighted in
 the Drive Tree.
+:p.
 :artwork name='bitmaps\openbutt.bmp' align=center.
 :p.
 Another alternative is to select the :hp1.Open->New FM/2 Window:ehp1.
 command from the :hp1.Files menu:ehp1. with the Drive Tree active, or
+Other alternatives are to select the :hp1.Open->New FM/2 Window:ehp1.
+command from the :hp1.Files menu:ehp1. with the Drive Tree active,
 (preferred) a context menu obtained on the directory you want to open
 (remember, you get a context menu by clicking mouse button 2 on an
+object).
+object) or the accelerator key Ctrl + o.
+:p.
 :artwork name='bitmaps\openmenu.bmp' align=center.
 :p.
 Yet another alternative is to invoke the :hp1.Utilities->Open Directory
 Container:ehp1. command (Ctrl + O accelerator -- remember, that "O"
 needs to be uppercase, so Shift if necessary).  Using this command
+needs to be uppercase, so Shift if necessary). Using this command
 invokes the :link reftype=hd res=91500. Walk Directories:elink. dialog
 and lets you pick the directory to open.
+:p.
 :artwork name='bitmaps\openmnu2.bmp' align=center.
+:p.
 The :hp1.Walk:ehp1. (walking dude) :hp1.button:ehp1. near the bottom
 right corner of the FM/2 window also invokes this command.  You can even
+right corner of the FM/2 window also invokes this command. You can even
 drag a file system object onto this button to open a new Directory
 Container for that object's directory.
+:p.
 :artwork name='bitmaps\walkbutt.bmp' align=center.
 :p.
 Finally, if you have the Drivebar toggled on (see the :link reftype=hd
+Finally, if you have the Drivebar on (see the :link reftype=hd
 res=92000.Config menu:elink. topic) and a 3-button mouse, you can click
 B3 (or hold down Ctrl while clicking B2) on one of the drive icons to
 …
 :p.
 Now, if that's not enough ways to open a Directory Container, I give up --
 go on back to Windoze and the Billy-mandated one way.  &colon.-)
+go on back to Windoze and the Billy-mandated one way. &colon.-)
 :p.
 You can also open directories from their objects in a Directory Container
 via context menu, Files menu or using the Shift modifier while
+via context menu, accelerator key, Files menu or using the Shift modifier while
 double-clicking.
+:h1 res=99400 name=PANEL_USERLISTS.Using quicklists
+:h2 res=91800 name=PANEL_TOOLBAR.Toolbar
+:i1 id=aboutToolbar.Toolbar
+:artwork name='bitmaps\toolbar.bmp' align=center.
+:p.
+The :hp1.toolbar:ehp1. is a collection of buttons that invoke some of
+the commands in the pulldown or popup menus. Placing the mouse pointer
+on a button and pressing and holding B2 displays brief help for the
+button on the titlebar.
+:p.
+Some of the buttons will allow objects to be dragged onto them; for
+example, you can drag objects onto the trashcan to delete them. Note
+that the hotspot of the mouse pointer itself should be over the button
+before releasing, not the icon being dragged (icons are slightly offset
+from the mouse pointer to give better target visibility). Target
+emphasis is provided in the form of a black outline around the button,
+and the arrow pointer turns into a hand when above a toolbox icon.
+:p.
+This toolbar submenu is a conditional cascade menu, meaning that if you
+click other than on the boxed arrow a default command is executed (the
+toolbar is toggled off and on), but if you click on the boxed arrow you
+get a submenu of items you can select (the other choices are Text
+Toolbar, which will cause the toolbar to appear as "normal" buttons with
+text on them, or Toolbar Titles, which will cause text to appear below
+the toolbar bitmap buttons).
+:p.
+Toolbar buttons are user-configurable. To change the toolbar, click
+mouse button two (usually the right button) while the mouse pointer is
+over a button to pop up a context menu. You can get the "Load Toolbox"
+dialog by clicking B2 on a blank area of the toolbar, and the "Add
+Button" dialog by chording on a blank area of the toolbar.
+:p.
+For advanced/curious users&colon. Information on what buttons are in the
+toolbar is kept in a file named FM3TOOLS.DAT. This file is an ASCII
+(plain text) file that contains information defining the toolbar. The
+file contains comments that explain its format.
+:p.
+FM/2 allows you to create customized toolboxes that can be loaded as
+required to provide toolboxes for specific activities. Although FM/2
+provides ways to edit the toolbar internally, it's probably easier to
+load the definition files into a text editor and make the changes
+manually en masse.
+:p.
+If you'd like to see a different toolbar layout (and try out the Load
+Toolbox command), right-click on the toolbar, pick Load Toolbox from the
+resultant menu, and pick a toolbox from the listbox. Then you might try
+creating your own and saving it with the Save Toolbox command.
+:p.
+See also&colon.
+.br
+:link reftype=hd res=96300.Reorder Tools:elink.
+.br
+:link reftype=hd res=94400.Edit Tool:elink.
+.br
+:link reftype=hd res=96400.Add Tool:elink.
+.br
+:link reftype=hd res=94000.Save Tools:elink.
+.br
+:link reftype=hd res=94500.Load Tools:elink.
+:h3 res=96300 name=PANEL_REORDERTOOLS.Reorder Tools
+:i1 id=aboutReorderTools.Reorder Tools
+This dialog, accessed from the context menu of a tool button, allows you
+to rearrange the order of the toolbar's tool buttons. You take selected
+items from the left listbox and Add them to the end of the right listbox
+with the :hp1.Add>>:ehp1. button. When you've moved everything to the
+right listbox, click :hp1.Okay:ehp1.. Click :hp1.Cancel:ehp1. if you
+change your mind.
+:p.
+In reality, you don't need to move everything to the right listbox. You
+can move only what you want moved to the top of the list, then click
+Okay. Anything remaining in the left listbox is added to the end of
+what's in the right listbox.
+:p.
+The :hp1.<<Remove:ehp1. button can be used to move selected items from
+the right listbox to the bottom of the left listbox.
+:h3 res=94400 name=PANEL_EDITTOOL.Edit Tool
+:i1 id=aboutEditTool.Edit Tool
+This dialog allows you to change the help and text strings and flags
+associated with a button. Edit as desired, then click Okay. Click
+Cancel if you change your mind.
+:p.
+The :hp1.Help:ehp1. field should contain text to remind you what the
+button's command does. For example, a button that deletes files and
+directories might have help reading "Delete files and directories".
+:p.
+The :hp1.Text:ehp1. field should contain very brief text that will be
+placed on the button (if the tool id has no bitmap associated with it).
+:p.
+The :hp1.Droppable:ehp1. checkbox determines if the tool can have objects
+dropped on it or not. See list below.
+:p.
+The :hp1.Visible:ehp1. checkbox determines if the tool is visible or not.
+:p.
+If the :hp1.Separator:ehp1. checkbox is checked, FM/2 puts a bit of
+whitespace after the button (separates it from the next button).
+:p.
+If you check the :hp1.User-defined bmp:ehp1. checkbox, FM/2 will allow
+you to use your own bitmap. Bitmaps are named after the :hp1.ID:ehp1.
+of the button -- for example, the bitmap file for ID 1005 would be named
+"1005.bmp". Clicking the :hp1.Edit bmp:ehp1. button will cause ICONEDIT
+to be loaded with the bitmap, ready to edit. (Note that bitmaps should
+be 28 x 28.)
+:p.
+The :hp1.ID:ehp1. field identifies the command that is associated with
+this button. See the :link reftype=hd res=96401.Tool IDs:elink. topic.
+:h3 res=96400 name=PANEL_ADDTOOL.Add Tool
+:i1 id=aboutAddTool.Add Tool
+This dialog is accessed from the context menu of a tool button, or if you
+turn on the toolbar when there are no tools defined.
+:p.
+To add a tool, fill in the fields as appropriate and click Okay. Click
+Cancel if you change your mind.
+:p.
+The :hp1.Help:ehp1. field should contain text to remind you what the
+button's command does. For example, a button that deletes files and
+directories might have help reading "Delete files and directories".
+:p.
+The :hp1.Text:ehp1. field should contain very brief text that will be
+placed on the button (if the tool id has no bitmap associated with it).
+:p.
+The :hp1.Droppable:ehp1. checkbox determines if the tool can have objects
+dropped on it or not. See list below.
+:p.
+The :hp1.Visible:ehp1. checkbox determines if the tool is visible or not.
+:p.
+If the :hp1.Separator:ehp1. checkbox is checked, FM/2 puts a bit of
+whitespace after the button (separates it from the next button).
+:p.
+If you check the :hp1.User-defined bmp:ehp1. checkbox, FM/2 will allow
+you to use your own bitmap. Bitmaps are named after the :hp1.ID:ehp1.
+of the button -- for example, the bitmap file for ID 1005 would be named
+"1005.bmp". Clicking the :hp1.Edit bmp:ehp1. button will cause ICONEDIT
+to be loaded with the bitmap, ready to edit.
+:p.
+The :hp1.ID:ehp1. field should be assigned a number that tells FM/2 what
+the command associated with the button is. See :link reftype=hd
+res=96401.Tool IDs:elink. topic.
+:h3 res=96401 name=PANEL_TOOLIDS.Tool IDs
+:i1 id=aboutToolIDs.Tool IDs
+:xmp.
+ID     Command                                              Droppable?
+====   =================================================    ==========
+   View Files                                           Y
+   Edit Files                                           Y
+   Make Directory                                       N
+   Object Information                                   Y
+   Rename Files/Directories                             Y
+   Delete Files/Directories                             Y
+   Permanently Delete Files/Directories                 Y
+   Set Attributes and Date/Time of Files/Directories    Y
+  Walk Directories                                     N
+  Select All Files                                     N
+  Deselect All                                         N
+   Archive Files/Directories                            Y
+   Extract From Archives                                Y
+   Create Objects                                       Y
+   Create Shadow Objects                                Y
+   Copy Files/Directories                               Y
+   Move Files/Directories                               Y
+   Kill Process                                         N
+   Undelete Files                                       N
+   Instant Command File                                 N
+   OS/2 Command Line                                    N
+   Filter Container                                     N
+   Edit Associations                                    N
+   Edit Commands                                        N
+   Rescan                                               N
+   Print Files                                          Y
+   Extended Attributes                                  Y
+   View INI Files                                       Y
+   Save List to Clipboard                               Y
+   Save List to File                                    Y
+   Collect Files/Directories                            N
+   Collect Files/Directories from list file             Y
+   Bookshelf Viewer                                     N
+   Open Default                                         Y
+   Directory sizes                                      N
+   UUDecode                                             Y
+   Merge                                                Y
+   Exit FM/2                                            N
+   First Command                                        Y
+   Second Command                                       Y
+&period...
+   First Toolbox                                        N
+   Second Toolbox                                       N
+&period...
+:exmp.
+Note&colon. Other Commands can also be used; just add to 4000 as required
+to get the number of the command. For instance, Command 4 would be ID
+. Command buttons use the text field; others shown have bitmaps
+associated with them in FM/2's resources. Remember that if you change
+your Commands around, you need to resync the tools to the Commands...
+:p.
+Note&colon. Toolbox buttons on a toolbar cause the appropriate toolbox
+to be loaded from QUICKTLS.DAT (one filename per line, blank lines and
+lines beginning with ";" ignored). The file named on the first line is
+the First Toolbox, and so forth. You can have up to 50 toolbox buttons
+defined (total).
+:p.
+This list isn't complete; ask me if you'd like a command added that
+doesn't appear, and I'll tell you if it can be added and what the ID is,
+if so.
+:h3 res=94000 name=PANEL_SAVETOOLS.Save Toolbox
+:i1 id=aboutSaveTools.Save Toolbox
+FM/2 allows you to save toolboxes (groups of tools) for later recall
+with the :link reftype=hd res=94500.Load Toolbox:elink. command.
+:p.
+Type the name of the file to hold the toolbox definitions into the entry
+field below the listbox, or select a file displayed in the listbox (it
+will be overwritten). FM/2 saves the toolbox definitions into the file.
+:p.
+The files are given an extension of &period.TLS if you don't specify an
+extension. The listbox shows files in the FM/2 directory that have the
+extension .TLS (which is my way of suggesting that you follow this
+convention).
+:h3 res=94500 name=PANEL_LOADTOOLS.Load Toolbox
+:i1 id=aboutLoadTools.Load Toolbox
+FM/2 allows you to load toolboxes (groups of tools) which were saved
+with the :link reftype=hd res=94000.Save Toolbox:elink. command.
+:p.
+Type the name of the file that holds the toolbox definitions into the
+entry field below the listbox, or select a file displayed in the
+listbox. FM/2 loads the toolbox definitions from the file and updates
+the toolbar.
+:p.
+This allows you to have groups of specific-purpose buttons which you can
+load for different types of activities. You don't have to use it, but
+it's there if you would like to do so.
+:p.
+Clicking :hp1.Okay:ehp1. without typing in or selecting a filename
+results in FM/2 reloading the default toolbox from FM3TOOLS.DAT.
+:p.
+If I may, here's how I'd recommend using this facility&colon.
+:p.
+First, save the full toolbar under a new name (perhaps ALL.TLS). Next,
+delete any buttons that you don't want in your customized toolbar.
+Finally, add any Command buttons that you do want in the customized
+toolbar and save the new toolbox (as <something>.TLS). By starting with
+the full toolbar, you'll spend more of your time deleting buttons you
+don't want (a trivial task) and less adding buttons.
+:h2 res=99400 name=PANEL_USERLISTS.Using quicklists
 :i1 id=aboutUserLists.Using quicklists
 FM/2's optional quickists (dropdown combo boxes) provide quick access
+FM/2's optional quicklists (dropdown combo boxes) provide quick access
 to&colon.
 :ul compact.
 …
 quicklists:ehp1. command (F8 accelerator).
 :p.
 The first list (starting from the left) contains drives.  If you select a
+The first list (starting from the left) contains drives. If you select a
 drive from the list, the Drive Tree scrolls to that drive and makes it the
+current object in the Drive Tree.  This can be handy when you have the tree
+expanded and don't want to collapse it.  This list is readonly.
+current object in the Drive Tree. This can be handy when you have the tree
+expanded and don't want to collapse it. This list is readonly.
+:p.
 :artwork name='bitmaps\userdriv.bmp' align=center.
 :p.
 …
 The second list is the State list, containing the names of saved States of
 the FM/2 window (what directories are open, where the windows are located,
 etc.).  You can add to this list by typing a name into the entry field,
+etc.). You can add to this list by typing a name into the entry field,
 requesting a context menu on the entry field, then selecting :hp1.Save
 State as name:ehp1. from the context menu.  FM/2 will save its current
+State as name:ehp1. from the context menu. FM/2 will save its current
 State under that name for later recall.
+:p.
 :artwork name='bitmaps\useradds.bmp' align=center.
+:p.
 This can be handy if you have different setups that you use frequently,
 as you can save and recall them when you need them rather than opening
 containers and setting them up to point at the directories you want and
 positioning them where you want each time.  For example, let's say
 you're connected to a LAN and have a BBS system running.  You might want
+positioning them where you want each time. For example, let's say
+you're connected to a LAN and have a BBS system running. You might want
 one State set up specifically for dealing with the LAN, one set up
 specifically for maintaining the BBS, and another (or few) for general
 work.  Once you've set FM/2 up in each of these conditions and saved the
+specifically for maintaining the BBS, and another (or a few) for general
+work. Once you've set FM/2 up in each of these conditions and saved the
 State under an easy-to-recall name, you can quickly move from State to
 State using the State list.  You'll find this :hp2.much:ehp2. faster and
+State using the State list. You'll find this :hp2.much:ehp2. faster and
 more flexible than the way DOS-think file managers do things.
 :p.
 …
 Holding down the Shift key while selecting a state name prevents FM/2
 from closing windows that are already open.
+:p.
 :artwork name='bitmaps\userstat.bmp' align=center.
 :p.
 .br
 The third list is the user-defined commands list.  User-defined commands
 allow you to extend FM/2 with commands of your own devising.  You can
+The third list is the user-defined commands list. User-defined commands
+allow you to extend FM/2 with commands of your own devising. You can
 add, change and delete commands with the :hp1.Config->Edit Commands:ehp1.
 menu item (or click B2 on the list).
+:p.
 :artwork name='bitmaps\cmdlist.bmp' align=center.
 :p.
 .br
 The fourth list is the commonly used directory list.  You can add a
 directory to this list as above; type in the name, select :hp1.Add
+The fourth list is the commonly used directory list. You can add a
+directory to this list as above; type in the name and select :hp1.Add
 pathname:ehp1. from a context menu.
+:p.
 :artwork name='bitmaps\useraddd.bmp' align=center.
+:p.
 You can also drag the pathname from the entry field (you'll be dragging
 the directory itself), or drag an object onto the control to add it to
 the list.  For example, if you have a Directory Container open and
+the directory itself), or drag an object onto the field to add it to
+the list. For example, if you have a Directory Container open and
 decide it'd be nice to have the directory name in this list, start a
 drag in the large status box at the top of the Directory Container (just
 …
 Directory Container for that path (hold down the Shift key while
 selecting the path to cause the current Directory Container to switch
 instead).  You can reverse this action with the :hp1.Quicklist
+instead). You can reverse this action with the :hp1.Quicklist
 switches:ehp1. toggle in the :link reftype=hd res=98400.Settings
 Notebook:elink..  In addition, the :hp1.Recent Dirs:ehp1. toggle can be
+Notebook:elink.. In addition, the :hp1.Recent Dirs:ehp1. toggle can be
 used to cause FM/2 to automatically add temporary entries for
 directories that you visit during a session.  You can add them as above
+directories that you visit during a session. You can add them as above
 to make them permanent if you desire.
 :p.
 …
 allows you to quickly place FM/2 into precisely the configuration you
 need to get real work done.
+:p.
 :artwork name='bitmaps\userdirs.bmp' align=center.
 :p.
 .br
 The last list (only present if the Toolbar is on) is a list of
 Toolboxes. You can select one from the list.  FM/2 automatically
 maintains this list for you.  Initially, the saved toolbox names are
 read in from disk (the FM/2 directory), and any you subsequently save
 are added to it on the fly.  The FM/2 archive includes a few Toolboxes
+Toolboxes. You can select one from the list. FM/2 automatically
+maintains this list for you. Initially, the saved toolbox names are
+read from disk (the FM/2 directory), and any you subsequently save
+are added to it on the fly. The FM/2 archive includes a few Toolboxes
 for you to look at and customize if you'd like.
+:p.
 :artwork name='bitmaps\usertool.bmp' align=center.
 :p.
 You can use the font and color palettes to set the colors and fonts
 used in these windows.  Note that you must set the entry field and
 listbox components separately.  To set the listbox component, drop
+used in these windows. Note that you must set the entry field and
+listbox components separately. To set the listbox component, drop
 onto the button, not the entry field.
 :p.
 The :hp1.Interface:ehp1. (list-and-arrow) :hp1.button:ehp1. at the
 bottom right corner of the FM/2 window toggles the quicklists on and off.
+:p.
 :artwork name='bitmaps\userbutt.bmp' align=center.
+.im folder.ipf
+.im databar.ipf
 .im tutor.ipf
 …
 :link reftype=hd res=90700.Commands:elink. are programs that can be run
 on selected objects by picking the programs by an assigned title from a
 dynamically built submenu of FM/2's Files pulldown menu.
+on selected objects by picking the program's title from a
+dynamically built submenu of FM/2's Files menu.
 :p.
 When commands are displayed in the submenu, visual queues are given as
 to the behavior of a given command.  Commands that are checked will run
 once for each selected file.  Commands that are framed will prompt the
+to the behavior of a given command. Commands that are checked will run
+once for each selected file. Commands that are framed will prompt the
 user to edit and accept the command line before running.
 :p.
 FM/2 provides accelerator keys for the first twenty commands in the
 submenu.  The accelerators are listed beside the command's title for
 reference.  This provides a "macro key" capability.
 :p.
 Don't overlook the power of Commands.  This is a simple way of extending
+submenu. The accelerators are listed beside the command's title for
+reference. This provides a "macro key" capability.
+:p.
+Don't overlook the power of Commands. This is a simple way of extending
 FM/2 to do things that it can't do on its own, to automate things, and
 to merge those old command line utilities with a PM selection shell (FM/2).
 …
 .im context.ipf
-.im folder.ipf
 .im arclist.ipf
 …
 .im walkem.ipf
+.im getnames.ipf
 .im chklist.ipf
 …
 .im errors.ipf
-.im keys.ipf
-.im mouse.ipf
-.im getnames.ipf
 :index.

trunk/dll/ipf/fm4.ipf

-              r2
+              r268
 :artwork name='bitmaps\fm4.bmp' align=center.
+"FM/2 Lite" is an alternate "personality" for FM/2.  It's invoked from
+:p.
+"FM/2 Lite" is an alternate "personality" for FM/2. It's invoked from
 the FM4.EXE executable rather than FM3.EXE.
 :p.
 This personality is a simplified version of the standard FM/2 interface.
 You get two Directory Containers and an optional Drive Tree.  You
+You get two Directory Containers and an optional Drive Tree. You
 have a choice in how to split the screen (:hp1.Windows->Tile
 backwards:ehp1.) -- vertically or horizontally.  The internal windows do
+backwards:ehp1.) -- vertically or horizontally. The internal windows do
 not have titlebars and cannot be moved or sized (the Drive Tree, if
 open, can have its width changed by dragging the right edge of the
 …
 :p.
 The Files, Views and Utilities menus have been simplified by omitting
 seldom used "advanced" commands.  The omitted commands are still
+seldom used "advanced" commands. The omitted commands are still
 available via :link reftype=hd res=93700.context menus:elink. and
 accelerator keys.  A few other features have been left out to simplify
 the interface.  If you consider yourself an advanced user, what are you
+accelerator keys. A few other features have been left out to simplify
+the interface. If you consider yourself an advanced user, what are you
 doing here?  &colon.-)
 :p.
 …
 If the Drive Tree is active and the current window, the Directory
 Container that will be affected by double-clicking a directory in the
 Tree is surrounded by a dark red line.  Tab and Shift-Tab can be used
+Tree is surrounded by a dark red line. Tab and Shift-Tab can be used
 to switch between the windows.
 :p.

trunk/dll/ipf/folder.ipf

-              r10
+              r268
 :h1 res=91900 name=PANEL_FOLDERBUTTON.Folder Button
+:h2 res=91900 name=PANEL_FOLDERBUTTON.Folder Button
 :i1 id=aboutFolderButton.Folder Button
 :artwork name='..\..\bitmaps\pmap.bmp' align=center.
+:p.
 Folder buttons appear on directory and archive containers at the top
 center of the window (below the title bar).  They provide several
+center of the window (below the title bar). They provide several
 shortcuts for their containers.
 :p.
 …
 You can also drag a file or directory object onto the folder button. In
 directory containers, the directory "switches" to "look at" the
 directory of the dropped object.  In archive containers, the extract
 directory changes to that of the directory of the dropped object.  This
+directory of the dropped object. In archive containers, the extract
+directory changes to that of the directory of the dropped object. This
 means that, for instance, you can set the extract directory for an
 archive to the same directory that the archive is in by dragging from a

trunk/dll/ipf/getnames.ipf

-              r2
+              r268
 This works exactly like the standard OS/2 file dialog with the exception
 that it contains a :hp6.UserDirs:ehp6. dropdown list.  See the :link
+that it contains a :hp6.UserDirs:ehp6. dropdown list. See the :link
 reftype=hd res=91500.Walk Directories:elink. topic for more info on
 user directories, including how to set them up.
 :p.
 The idea here is pretty simple -- you want to give the dialog a
 filename.  You can type it directly into the :hp6.Filename:ehp6. entry
+filename. You can type it directly into the :hp6.Filename:ehp6. entry
 field or select it using the list controls.
 :p.
 …
 drive. The :hp6.Directories:ehp6. listbox can be used to switch
 directories on the current drive (as can the :hp6.UserDirs:ehp6.
 dropdown).  The :hp6.Files:ehp6. listbox can be used to pick an existing
+dropdown). The :hp6.Files:ehp6. listbox can be used to pick an existing
 file.
 :p.

trunk/dll/ipf/hints.ipf

-              r2
+              r268
 :artwork name='bitmaps\secret.bmp' align=center.
+:p.
 This section contains hints about obscure functions, FM/2 "secrets" and
 other rubbish.
 …
 :p.
 Want to copy or move some files to a new directory?  Try dragging them
 onto an empty area (whitespace) of the Drive tree.  FM/2 will pop up a
+onto an empty area (whitespace) of the Drive tree. FM/2 will pop up a
 dialog allowing you to specify a name for a new directory into which to
 place the files.
 …
 To set the label of a drive, pick :link reftype=hd
 res=90900.Files->Info:elink. (Ctrl + i accelerator) on the root of the
 drive in the Drive Tree container.  You'll find :hp1.Format:ehp1. and
+drive in the Drive Tree container. You'll find :hp1.Format:ehp1. and
 :hp1.Chkdsk:ehp1. in that menu, too, under the :hp1.Miscellaneous:ehp1.
 submenu.
 …
 Remember, when using the :link reftype=hd res=93900.internal
 editor:elink. (but don't, use your favorite editor instead), FM/2 saves
 the file as it appears in the MLE.  If you don't want long lines wrapped
+the file as it appears in the MLE. If you don't want long lines wrapped
 (such as when editing CONFIG.SYS), turn wrap OFF before saving.
 :p.
 If you want to change the fonts used in the :link reftype=hd
 res=91500.Walk Directories:elink. dialog, drop a new font from the Font
 Palette onto a blank area of the dialog (not a control).  The new font
+Palette onto a blank area of the dialog (not a control). The new font
 will be used in the directory listboxes and path entry field the next
 time you use the dialog.  This is sometimes necessary when the default
+time you use the dialog. This is sometimes necessary when the default
 font for the dialog doesn't match up well to the codepage in use for
 non-US users, as non-ASCII characters might show up improperly.
 …
 association, try Open->Default from a context menu on the file object
 (F6 accelerator) or holding down the Ctrl key while double-clicking the
 object.  Alternatively, use <> as the command line for an :link
+object. Alternatively, use <> as the command line for an :link
 reftype=hd res=90400.association:elink. and it'll open the object's
 default WPS view, which will run the program associated with the object
 under the WPS if there is one.  Follow the hypertext link in this
+under the WPS if there is one. Follow the hypertext link in this
 paragraph for detailed explanations.
 :p.
 …
 and :link reftype=hd res=90100.Collecting:elink. them from that list
 file so you don't have to reselect them when you want to manipulate them
 later.  Note that FM/2 has a Reselect command under the Views->Select
+later. Note that FM/2 has a Reselect command under the Views->Select
 menu, but it only remembers the last selection set -- using the
 List/Collect method you can reselect even in another session.
 :p.
 Using :hp1.AV/2:ehp1. from the WPS&colon.  Drag an archive file onto the
 AV/2 object; this opens a view into the archive.  Drag any files you
+Using :hp1.AV/2:ehp1. from the WPS&colon. Drag an archive file onto the
+AV/2 object; this opens a view into the archive. Drag any files you
 want added to the archive into the container; they're added to the
 archive. To create a new archive, drag the objects to be archived onto
 the :hp1.Make Archive:ehp1. object.
 :p.
 For advanced users&colon.  You can add commands to FM/2's action bar
 menu. Create a file in FM/2's directory called FM3MENU.DAT.  Here's a
+For advanced users&colon. You can add commands to FM/2's action bar
+menu. Create a file in FM/2's directory called FM3MENU.DAT. Here's a
 sample&colon.
 :xmp.
+;
 ;Items listed in this file are added to FM/2's action bar (pulldown) menu.
 ;First word in a line MUST be MENUITEM.  Next comes ID of command (see
 ;FM3TOOLS.DAT).  Finally, the text to display on the menu for the command.
+;First word in a line MUST be MENUITEM. Next comes ID of command (see
+;FM3TOOLS.DAT). Finally, the text to display on the menu for the command.
+;
 ;Any line beginning with a semi-colon, like this one, is a comment.
 …
 is in, start a drag from the recessed text field next to the :link
 reftype=hd res=91900.Folder button:elink. and drop onto the Folder
 button.  If you always want the extract directory to be the same as the
+button. If you always want the extract directory to be the same as the
 directory in which the archive resides, enter * in the Ext. Path field
 of the internal Settings Notebook's :link reftype=hd res=99940.Archivers
 …
 the container to sort on that field (assuming the field is one of those
 on which FM/2 will sort -- filename, size, EA size, and dates are all
 valid).  Works in Archive Containers, too.
+valid). Works in Archive Containers, too.
 :p.
 Can't set the :hp3.default sort or view for new Directory
 …
 res=97100.internal Settings notebook:elink. instead of the popup menus.
 The popups only change the :hp1.current:ehp1. container -- the one on
 which you requested the context menu.  The Settings notebook determines
 how new containers that you open will appear.  This is a distinction
+which you requested the context menu. The Settings notebook determines
+how new containers that you open will appear. This is a distinction
 often overlooked by new users.
 :p.
 Old DOS hands will know this, but you can enter :hp2.PRN:ehp2. when you
 want output to go to a printer rather than a disk file.  You can even
+want output to go to a printer rather than a disk file. You can even
 specify different printers using LPT? (i.e. LPT1, LPT2, LPT3, etc.).
 :p.
 If nothing shows in a Directory Container, Archive Container, the
 Collector or Drive Tree although you :hp1.know:ehp1. there's something
 in it, check your Filter (Ctrl + f accelerator).  The Filter button for
+in it, check your Filter (Ctrl + f accelerator). The Filter button for
 the appropriate container will show the current filter status for the
 current container (F&colon.<All> means everything is visible, <Attr>
 means attributes are being used to filter, otherwise you'll see the
 current mask set). Remember to look at the attributes as well as the
 mask.  The :hp1.All:ehp1. button in the :link reftype=hd
+mask. The :hp1.All:ehp1. button in the :link reftype=hd
 res=93400.Filter dialog:elink. can be used to ensure that everything is
 visible.
 …
 drag the directory the Directory Container is "looking" into, and when
 you drop :hp1.on:ehp1. one of them, you drop into the directory the
 Directory Container is "looking" into.  They behave, for drag and drop
+Directory Container is "looking" into. They behave, for drag and drop
 and requesting context menus, like empty container space (whitespace).
 :p.
 To begin a direct edit of the current file's name using the keyboard,
 use Ctrl + F10.  To end (complete) the direct edit, use Ctrl + F11.  To
+use Ctrl + F10. To end (complete) the direct edit, use Ctrl + F11. To
 cancel an edit underway, use Escape.
 :p.
 PM uses several ALT + F? accelerators to control frame windows. However,
 this applies to the current frame window, which can be within the main
 FM/2 window when run monolithically.  Add Ctrl to these accelerators to
 affect the main window in that case.  For example, Ctrl + Alt + F9 will
+FM/2 window when run monolithically. Add Ctrl to these accelerators to
+affect the main window in that case. For example, Ctrl + Alt + F9 will
 minimize the main FM/2 window, while Alt + F9 will minimize whichever
 frame window has the focus.
 …
 the first button) on them will change your sort type.
 :p.
 Problem with ZIP or EZ drive -- slow scanning&colon.  See :link
 reftype=hd res=99980.Edit->Drive flags:elink. command.  The problem
+Problem with ZIP or EZ drive -- slow scanning&colon. See :link
+reftype=hd res=99980.Edit->Drive flags:elink. command. The problem
 is that these drives respond :hp1.very:ehp1. slowly to some commands
 and requests.  You can tweak the drive's flags to alleviate some of
+and requests. You can tweak the drive's flags to alleviate some of
 this.
 :p.
 Problem with details view refreshing -- top items come up blank.  This
 is one of those never-fixed OS/2 bugs.  Try :hp1.unchecking:ehp1. the
 Immediate updates toggle in the Settings notebook.  This usually works
+Problem with details view refreshing -- top items come up blank. This
+is one of those never-fixed OS/2 bugs. Try :hp1.unchecking:ehp1. the
+Immediate updates toggle in the Settings notebook. This usually works
 around this bug.
 :p.
 To find any directory in the Drive Tree quickly, type Ctrl + Shift + F
 with the Drive Tree active, then type in the pathname of the directory
 that you want to find.  To find the directory of a Directory Container
+that you want to find. To find the directory of a Directory Container
 in the Drive Tree, type Ctrl + Shift + F with the Directory Container
 active.
 …
 The :link reftype=hd res=90100.Collector:elink. can search for files
 based on a variety of criteria. The search function can also find
 potential duplicate files for you.  Potential duplicates can also be
+potential duplicate files for you. Potential duplicates can also be
 tracked down in the :link reftype=hd res=98500.See all files:elink.
 control.
 :p.
 You can selectively turn off FM/2's bubble help.  Use the internal
+You can selectively turn off FM/2's bubble help. Use the internal
 Settings notebook, turn to the :hp1.Bubbles:ehp1. page, and read the
 help.
 …
 "I double-clicked on an INI file and FM/2 showed it in the text viewer."
 The INI file may not be a standard OS/2 INI file (Windoze programs, for
 example, use *.INI files that are flat text files).  FM/2 will "fail"
+example, use *.INI files that are flat text files). FM/2 will "fail"
 quietly to view such files using the INI viewer when you double-click
 them since there's no reason to bother you each time you want to look at
 one.  If you're sure the file is a standard OS/2 INI file, use the
+one. If you're sure the file is a standard OS/2 INI file, use the
 Utilities menu to open the INI viewer, then choose Files->Other profile
 and enter the name of the file.  FM/2 will then tell you the reason that
+and enter the name of the file. FM/2 will then tell you the reason that
 it is unable to open the file -- you probably want to know about it since
 you're already in the INI viewer.
 …
 else, for that matter -- I mention self-extracting archives because FM/2
 will attempt to view them rather than run them when you double-click
 them), press Ctrl + F5.  This brings up the :link reftype=hd
+them), press Ctrl + F5. This brings up the :link reftype=hd
 res=90600.Command line:elink. dialog with the cursored file in the entry
 field.
 …
 :p.
 Alternatively, if running FM/2 monolithically, press F5 to get a
 miniature command line at the bottom of the window.  Enter any commands
+miniature command line at the bottom of the window. Enter any commands
 you'd like here, including :link reftype=hd
 res=100075.metastrings:elink..  Type /HELP in the command line entry
+res=100075.metastrings:elink.. Type /HELP in the command line entry
 field for brief information specific to this control.
 :p.
 Note that if you use the same command line time after time you will
 probably want to set up a :link reftype=hd res=90700.Command:elink.
 for the command line to save time.  With a Command, you can even
+for the command line to save time. With a Command, you can even
 execute a command line using an accelerator key -- can't beat that
 for speed.

trunk/dll/ipf/inis.ipf

-              r10
+              r268
 :artwork name='..\..\bitmaps\ini.bmp' align=center.
-INI files are a form of data file that OS/2 provides to applications and
-utilizes itself.  This viewer allows you to take a peek inside them.
 :p.
+Two special INIs are used by the system.  They are the User INI (usually
+OS2.INI) and the System INI (usually OS2SYS.INI).  Both are usually
+located in the \OS2 directory of your boot drive.  FM/2 will tell you
+INI files are a type of configuration file that OS/2 provides to applications and
+utilizes itself. This viewer allows you to take a peek inside them and modify
+them as needed. :hp2.:hp8.Caution:ehp8.:ehp2.Backup the INI file before modifying
+it since corruption of an INI file can result in failure of a program including
+the WPS to run.
+:p.
+Two special INIs are used by the system. They are the User INI (usually
+OS2.INI) and the System INI (usually OS2SYS.INI). Both are usually
+located in the \OS2 directory of your boot drive. FM/2 will tell you
 where they are when you view them.
 :p.
 …
 :p.
 A record in an INI is composed of three parts:  An application name,
 a keyname, and data.  This three-part format is represented in the
 window by three listboxes.  When you choose an application name and
+a keyname, and data. This three-part format is represented in the
+window by three listboxes. When you choose an application name and
 a keyname, you see the data associated with them.
 :p.
 …
 :hp1.Edit->Delete Application:ehp1., or to delete individual keynames,
 deleting the data associated with them with :hp1.Edit->Delete
 Keyname:ehp1..  You can also copy or rename entire application names
+Keyname:ehp1.. You can also copy or rename entire application names
 or application+keynames.
 :p.
 The :hp1.Files->User Profile:ehp1. command loads the user INI (usually
 OS2.INI) and the :hp1.Files->System Profile:ehp1. command loads the
 system INI (usually OS2SYS.INI).  The :hp1.Files->Other Profile:ehp1.
 command allows you to pick an INI file to load.  The
+system INI (usually OS2SYS.INI). The :hp1.Files->Other Profile:ehp1.
+command allows you to pick an INI file to load. The
 :hp1.Files->Refresh:ehp1. command will refresh the contents of the
 listboxes from the INI file on disk; handy if a background process might
 …
 The :hp1.Entries->Filter appnames:ehp1. command can be used to
 selectively remove or include application names from the first listbox
 via a dialog that pops up when the command is selected.  One filter
+via a dialog that pops up when the command is selected. One filter
 "mask" should be entered per line in the MLE; preface "masks" with "/"
 to cause the following mask to exlude rather than include items.
 …
 Note that the Filter command removes entries from the listbox;
 refiltering with a more inclusive set of masks will not restore filtered
 entries.  Use the :hp1.Files->Refresh:ehp1. command for that.
+entries. Use the :hp1.Files->Refresh:ehp1. command for that.
 :p.
 The :hp1.Utilities->Backup Profile:ehp1. creates a backup of the current
 profile.  You get to specify the filename.  The :hp1.Utilities->Change
+profile. You get to specify the filename. The :hp1.Utilities->Change
 System Profiles:ehp1. command lets you change the User and System
 profiles that OS/2 uses.  The :hp1.Utilities->Replace System
+profiles that OS/2 uses. The :hp1.Utilities->Replace System
 Profiles:ehp1. command lets you replace the default system profiles with
 new profiles; the old files are physically overwritten.
 :p.
 You can also drag from and to the top two listboxes in this window.  If
+You can also drag from and to the top two listboxes in this window. If
 you drag from the left window, you drag the current application name,
 all its keynames, and all the data associated with the keynames.  If you
+all its keynames, and all the data associated with the keynames. If you
 drag from the right window, you drag the current application and
 keynames, and all the data associated with the keyname.  You can either
+keynames, and all the data associated with the keyname. You can either
 move or copy the record(s) using the standard key modifiers (you did read
 the :link reftype=hd res=90000.General Help:elink. topic, didn't you?).
 …
 This window is reached via the :hp1.Utilities:ehp1. pulldown menu on
 FM/2's main window, or by selecting (double-clicking) an INI file in a
 directory window, or by starting it from the FM/2 folder.  The
+directory window, or by starting it from the FM/2 folder. The
 double-click behavior can be changed by specifying an association for
 *.INI under FM/2's main :hp1.Config->Edit Associations:ehp1. pulldown.
 …
 To add an INI record, fill in the three entry fields on the screen. The
 appname and keyname pair, together, should form a unique ID, or you'll
 end up replacing existing data rather than adding new data.  Then click
 Okay.  Click Cancel to abort.
+end up replacing existing data rather than adding new data. Then click
+Okay. Click Cancel to abort.
 :p.
 You can check the :hp1.:link reftype=hd res=99500.Use
 \-encoding:elink.:ehp1. checkbox if you want to enter or edit binary
 data.  FM/2 attempts to determine the type of data if you're editing
+data. FM/2 attempts to determine the type of data if you're editing
 rather than adding and sets the checkbox for you accordingly.
 :p.
 …
 FM/2 lets you change the INIs that OS/2 uses while OS/2 is still active.
 This, together with the Backup Profile command, allow you to create and
 use alternate profiles.  Note that this doesn't change the physical INI
+use alternate profiles. Note that this doesn't change the physical INI
 files, it just points OS/2 at the new files; when you reboot, the files
 specified in CONFIG.SYS are used.
 :p.
 There are a couple of potential uses for this function.  You might use
 it to maintain different desktops and switch between them.  You might
+There are a couple of potential uses for this function. You might use
+it to maintain different desktops and switch between them. You might
 use it to allow you to copy backed up profiles to OS2.INI and OS2SYS.INI
 (the default OS/2 profiles -- do this by first switching to a different
 set of profiles, then copying your backups onto OS2.INI and OS2SYS.INI,
 then restoring OS2.INI and OS2SYS.INI as the system profiles.  You can't
+then restoring OS2.INI and OS2SYS.INI as the system profiles. You can't
 do this normally as the system profiles are readonly and can't be
 overwritten.).
 :p.
 Note that when the change occurs, OS/2 will restart the WPS.  It's
+Note that when the change occurs, OS/2 will restart the WPS. It's
 recommended that you back up your system INIs before using this and
 shut down all other running processes first.
 …
 This dialog physically replaces the OS/2 system INIs with the INI files
 you select.  The change is permanent.
+you select. The change is permanent.
 :p.
 Note that when the change occurs, OS/2 will restart the WPS (twice).
 It's HIGHLY recommended that you back up your system INIs before using
 this and shut down all other running processes first.  (Use of this
+this and shut down all other running processes first. (Use of this
 after having used the :link reftype=hd res=96800.Change System
 Profiles:elink. command probably won't do what you expect unless you
 …
 keyname if copying or renaming a specific application+keyname pair).
 Once you've filled in the new name(s), click Okay to perform the
 operation.  Click Cancel if you change your mind.
+operation. Click Cancel if you change your mind.
 :h3 res=99700 name=PANEL_FILTERINI.Filter INIs
 …
 This dialog can selectively remove or include application names from the
 first listbox.  One filter "mask" should be entered per line in the MLE;
+first listbox. One filter "mask" should be entered per line in the MLE;
 preface "masks" with "/" to cause the following mask to exlude rather
 than include items.
 …
 Note that the Filter command removes entries from the listbox;
 refiltering with a more inclusive set of masks will not restore filtered
 entries.  Use the :hp1.Files->Refresh:ehp1. command for that.
+entries. Use the :hp1.Files->Refresh:ehp1. command for that.

trunk/dll/ipf/keys.ipf

-              r2
+              r268
 :h1 res=100005 name=PANEL_KEYS.Keys help
+:h2 res=100005 name=PANEL_KEYS.Keys help
 :i1 id=aboutKeys.Keys help
 :hp2.Directory Containers:ehp2.
 .br
 :hp1.Note&colon.:ehp1.  many commands also available in Drive Tree and
+:hp1.Note&colon.:ehp1. many commands also available in Drive Tree and
 Collector windows.
 :parml compact tsize=20 break=none.
 …
 :p.
 Remember, :link reftype=hd res=97700.accelerator keys:elink. are case
 sensitive -- Ctrl + r isn't the same thing as Ctrl + R.  The latter is
+sensitive -- Ctrl + r isn't the same thing as Ctrl + R. The latter is
 obtained by holding down both Ctrl and Shift while pressing the "R" key.

trunk/dll/ipf/merge.ipf

-              r2
+              r268
 This dialog allows you to order the files to be merged (they're shown in
 the listbox at the top of the dialog) and set the Target (the file that
 will contain the merged files).  The :hp1.Merge:ehp1. command is under
+will contain the merged files). The :hp1.Merge:ehp1. command is under
 the :hp1.Files->Copy:ehp1. conditional cascade menu.
 :p.
 When you click :hp1.Okay:ehp1., each file, in order, is appended to the
 Target filename.  The merged files are not deleted.  If :hp1.Append:ehp1.
+Target filename. The merged files are not deleted. If :hp1.Append:ehp1.
 is checked, the Target file is appended if it exists; otherwise, it's
 overwritten by the first merge file.  If :hp1.Binary:ehp1. is checked,
+overwritten by the first merge file. If :hp1.Binary:ehp1. is checked,
 the files are copied in binary mode; otherwise, they're copied in text
 mode.
 :p.
 To order the files, select a listbox item and click either
 :hp1.Top:ehp1. or :hp1.Bottom:ehp1..  You can also :hp1.Remove:ehp1. a
 highlighted file from the list.  If you need to, you can :hp1.Undo:ehp1.
+:hp1.Top:ehp1. or :hp1.Bottom:ehp1.. You can also :hp1.Remove:ehp1. a
+highlighted file from the list. If you need to, you can :hp1.Undo:ehp1.
 the changes you've made and put the listbox back like it was when the
 dialog first came up.
 …
 If you want to edit a file, double-click it in the listbox.
 :p.
 When you're done, click :hp1.Okay:ehp1..  If you changed your mind, click
+When you're done, click :hp1.Okay:ehp1.. If you changed your mind, click
 :hp1.Cancel:ehp1..

trunk/dll/ipf/mouse.ipf

r2	r268
1		:h1 res=100040 name=PANEL_MOUSE.Mouse click help
	1	:h2 res=100040 name=PANEL_MOUSE.Mouse click help
2	2	:i1 id=aboutMouse.Mouse click help
3	3

trunk/dll/ipf/notebook.ipf

-              r10
+              r268
 :i1 id=aboutSettings.Settings Notebook
 FM/2's internal Settings notebook lets you fiddle with some of the
 toggles and variables used to control how FM/2 behaves.  This is called
+toggles and variables used to control how FM/2 behaves. This is called
 up via the :hp1.:link reftype=hd res=92000.Config:elink.->Settings
 notebook...:ehp1. pulldown menu item.
 …
 :p.
 Note that settings changes generally don't take effect until you close
 the notebook by clicking the :hp1.Okay:ehp1. button.  The
+the notebook by clicking the :hp1.Okay:ehp1. button. The
 :hp1.Undo:ehp1. button will restore things to the way they were before
 you started fiddling about.  The :hp1.Quick:ehp1. page is a notable
+you started fiddling about. The :hp1.Quick:ehp1. page is a notable
 exception.
 :p.
 …
 :artwork name='bitmaps\dir.bmp' align=left.
+:p.
 This page contains controls that affect Directory Containers.
 :p.
 …
 Normally FM/2 updates the container as things change; for instance, if
 you're deleting several files, the container is updated after each file
 is deleted.  If you uncheck :hp6.Immediate updates:ehp6., FM/2 updates
+is deleted. If you uncheck :hp6.Immediate updates:ehp6., FM/2 updates
 the container after an atomic action completes (i.e. after all files
 moved by one operation have been moved).  This speeds up processing
 but allows the container to be temporarily "out of synch" with the real
+moved by one operation have been moved). This speeds up processing
+but allows the container to be temporarily "out of sync" with the real
 state of affairs.
 :p.
 …
 looks inside an open Directory Container when deciding what default to
 place in the Walk Directories dialog for a copy or move command invoked
 via keyboard, menu or toolbar button.  If this is checked, FM/2 looks at
+via keyboard, menu or toolbar button. If this is checked, FM/2 looks at
 the current item in the Directory Container and, if it's a directory
 object, uses that path.  If not checked, FM/2 uses the directory into
+object, uses that path. If not checked, FM/2 uses the directory into
 which the Directory Container is "looking."
 :p.
 The :hp6.Min dir on open:ehp6. toggle, if checked, causes FM/2 to
 minimize a Directory Container window if you open another Directory
 Container window from one of its objects.  When you close the new
+Container window from one of its objects. When you close the new
 Directory Container window the old window is restored.
 :p.
 …
 object starting with the depressed letter and the object is selected.
 Note that you can get this standard effect with this toggle left on by
 pressing the Shift key along with the letter.  Container searching
+pressing the Shift key along with the letter. Container searching
 allows you to enter multiple characters which are searched for at the
 start of filenames.  The record is made the current (cursored) object.
+start of filenames. The record is made the current (cursored) object.
 If the record matches all the letters typed exactly, it is also
 selected.  A pause of more than about two seconds in typing resets the
 search string.  :hp1.Warning:ehp1.&colon.  this doesn't work right on
+selected. A pause of more than about two seconds in typing resets the
+search string. :hp1.Warning:ehp1.&colon. this doesn't work right on
 some versions of Warp, where the OS/2 CM_SEARCHSTRING container
 message's behavior is buggy.  It's not dangerous, it just doesn't
+message's behavior is buggy. It's not dangerous, it just doesn't
 produce the expected results.
 :p.
 The :hp6.Multiple select cnrs:ehp6. and :hp6.Extended select cnrs:ehp6.
 checkboxes control the type of selection in some new containers (existing
 containers are not affected).  Collector, Directory Container and Archive
+containers are not affected). Collector, Directory Container and Archive
 Containers created after these settings are changed will have the type of
 selection desired (note:  unhighlighting both results in a single select
 container -- probably not desirable).  The default is Extended select.
+container -- probably not desirable). The default is Extended select.
 :p.
 The :hp6.Stay in Tree View:ehp6. switch, if checked, causes Directory
 Containers to remain in Tree View (if already in Tree View, of course)
 when you switch the Directory Container to look into a different
 directory.  Otherwise, FM/2 switches the Directory Container back to
+directory. Otherwise, FM/2 switches the Directory Container back to
 the last used view before you put it into Tree View.
+The :hp6.No folder menu:ehp6. switch, if checked, causes a B2 click on the
+folder icon to immediately load the previous directory in the Directory Container.
+Otherwise it results in the folder menu appearing.
 :h3 res=97100 name=PANEL_DCPAGEVIEWS.Directory Container views page
 …
 :artwork name='bitmaps\dir.bmp' align=left.
+:p.
 This settings page lets you set the type of view that will be used in
 new Directory Container windows.  Directory Containers that are already
+new Directory Container windows. Directory Containers that are already
 open won't be affected.
 :p.
 :hp6.Icon:ehp6.  In Icon view, the object's name appears below its icon.
 :p.
 :hp6.Name:ehp6.  In Name view, the object's name appears beside its icon.
 :p.
 :hp6.Text:ehp6.  Text view is the fastest view for a container to
+:hp6.Icon:ehp6. In Icon view, the object's name appears below its icon.
+:p.
+:hp6.Name:ehp6. In Name view, the object's name appears beside its icon.
+:p.
+:hp6.Text:ehp6. Text view is the fastest view for a container to
 maintain, but provides the least information on the objects it contains.
 :p.
 :hp6.Detail:ehp6.  Details view shows a great deal of information on the
+:hp6.Detail:ehp6. Details view shows a great deal of information on the
 objects it contains, including file sizes, dates, and times, but it is
 the slowest view for a container control to maintain.
 …
 :p.
 The :hp6.Field Titles:ehp6. group (analogous to the Views->Details Setup
 submenu) allows you to control what is shown in a Details view.  Each
 possible field in the details view is shown.  If the field is checked,
 FM/2 will show it.  If not, it won't.
+submenu) allows you to control what is shown in a Details view. Each
+possible field in the details view is shown. If the field is checked,
+FM/2 will show it. If not, it won't.
 :p.
 The :hp6.Filter:ehp6. entry field shows the current default filter mask
 for Directory Containers.  Moving to this field will bring up a dialog
 that lets you set a new filter.  The filter will be used for subsequently
+for Directory Containers. Moving to this field will bring up a dialog
+that lets you set a new filter. The filter will be used for subsequently
 created Directory Containers.
 …
 :artwork name='bitmaps\dir.bmp' align=left.
+:p.
 This page lets you set the type of sort for Directory Containers.
 Directory Containers that are already open won't be affected immediately
 …
 :p.
 You can also tell FM/2 to always display directories ahead of or behind
 files.  Note that :hp1.Last access date:ehp1. and :hp1.Creation
+files. Note that :hp1.Last access date:ehp1. and :hp1.Creation
 date:ehp1. are only meaningful for HPFS file systems; FAT file systems
 do not track this information.  The difference between
+do not track this information. The difference between
 :hp1.Pathname:ehp1. and :hp1.Filename:ehp1. is only apparent in the
 Collector.  With the former, the entire pathname of the object is used
 to sort.  With the latter, only the filename portion is used to sort.
+Collector. With the former, the entire pathname of the object is used
+to sort. With the latter, only the filename portion is used to sort.
 FM/2 maintains separate sort criteria for Drive Tree, Collector,
 Directory Container and Archive Container windows.  This page affects
 only Directory Container sorting.  The Collector has its own page; use a
+Directory Container and Archive Container windows. This page affects
+only Directory Container sorting. The Collector has its own page; use a
 context menu or View pulldown menu for other container types (like the
 Drive Tree).
 :p.
 :hp7.Note&colon.:ehp7.  This page controls how new Directory Containers
+:hp7.Note&colon.:ehp7. This page controls how new Directory Containers
 are created (already open containers are not affected), and the context
 menu in Directory Containers affects only the Directory Container from
 …
 :artwork name='bitmaps\collect.bmp' align=left.
+:p.
 This settings page lets you set the type of view that will be used in
 new Collector windows.  If the Collector is already open it won't be
+new Collector windows. If the Collector is already open it won't be
 affected unless you close and reopen it.
 :p.
 :hp6.Icon:ehp6.  In Icon view, the object's name appears below its icon.
 :p.
 :hp6.Name:ehp6.  In Name view, the object's name appears beside its icon.
 :p.
 :hp6.Text:ehp6.  Text view is the fastest view for a container to
+:hp6.Icon:ehp6. In Icon view, the object's name appears below its icon.
+:p.
+:hp6.Name:ehp6. In Name view, the object's name appears beside its icon.
+:p.
+:hp6.Text:ehp6. Text view is the fastest view for a container to
 maintain, but provides the least information on the objects it contains.
 :p.
 :hp6.Detail:ehp6.  Details view shows a great deal of information on the
+:hp6.Detail:ehp6. Details view shows a great deal of information on the
 objects it contains, including file sizes, dates, and times, but it is
 the slowest view for a container control to maintain.
 …
 :p.
 The :hp6.Field Titles:ehp6. group (analogous to the Views->Details Setup
 submenu) allows you to control what is shown in a Details view.  Each
 possible field in the details view is shown.  If the field is checked,
 FM/2 will show it.  If not, it won't.
+submenu) allows you to control what is shown in a Details view. Each
+possible field in the details view is shown. If the field is checked,
+FM/2 will show it. If not, it won't.
 :p.
 The :hp6.Filter:ehp6. entry field shows the current filter mask for the
 Collector.  Moving to this field will bring up a dialog that lets you set
 a new filter.  The filter will be used for subsequent invocations of the
+Collector. Moving to this field will bring up a dialog that lets you set
+a new filter. The filter will be used for subsequent invocations of the
 Collector.
 …
 :artwork name='bitmaps\collect.bmp' align=left.
+This page lets you set the type of sort for the Collector.  If the
+:p.
+This page lets you set the type of sort for the Collector. If the
 Collector is already open it won't be affected immediately, (see
 :hp1.Resort:ehp1. context menu command), but will use the new sort type
 …
 :p.
 You can also tell FM/2 to always display directories ahead of or behind
 files.  Note that :hp1.Last access date:ehp1. and :hp1.Creation
+files. Note that :hp1.Last access date:ehp1. and :hp1.Creation
 date:ehp1. are only meaningful for HPFS file systems; FAT file systems
 do not track this information.  The difference between
+do not track this information. The difference between
 :hp1.Pathname:ehp1. and :hp1.Filename:ehp1. is only apparent in the
 Collector.  With the former, the entire pathname of the object is used
 to sort.  With the latter, only the filename portion is used to sort.
+Collector. With the former, the entire pathname of the object is used
+to sort. With the latter, only the filename portion is used to sort.
 FM/2 maintains separate sort criteria for Drive Tree, Collector,
 Directory Container and Archive Container windows.  This page affects
+Directory Container and Archive Container windows. This page affects
 only :link reftype=hd res=90100.Collector:elink. sorting.
+:h3 res=92400 name=PANEL_TREEPAGE.Drive Tree page
+:i1 id=aboutTREEP.Drive Tree page
+:h3 res=99940 name=PANEL_ARCPAGE.Archive page
+:i1 id=aboutARCP.Archive page
+:artwork name='bitmaps\archive.bmp' align=left.
+:p.
+This page contains controls relating to archivers and Archive
+Containers.
+:p.
+The :hp6.Quick arc find:ehp6. toggle, if checked, causes FM/2 to check
+only files with extensions that match those configured in ARCHIVER.BB2
+as potential archives during a drag and drop operation. If you're
+dragging over files on a floppy or network directory, this can speed
+things up a bit.
+:p.
+The :hp6.Folder after extract:ehp6. toggle, if on, causes FM/2 to create
+a folder to hold objects extracted from an archive via an Archive
+Container. You'll be given an opportunity to abort the folder creation
+or to decide where the folder will be located and what it'll be named.
+:p.
+You can set a :hp6.Default archiver:ehp6. so that, when you're archiving
+files and directories, this archiver is the default for the :hp1.Select
+Archiver:ehp1. dialog.
+:p.
+If the :hp6.Show archiver activity:ehp6. toggle is checked, FM/2 runs
+archiver windows in the foreground. Normally it runs them in the
+background, minimized, so you'd have to use the task list to pull them
+to the foreground if you want to see them.
+:p.
+The :hp6.A/Virus:ehp6. field allow you to enter the command line
+(PATH/ANTIVIRUS&period.EXE parameters) for your antivirus software
+This must be done to enable virus checking of archives from FM/2.
+NVCC&period.EXE &percent.p /C is one possible command line option
+if you are using Norman Antivirus.
+:p.
+The :hp6.Ext. Path:ehp6. field, if anything is in it, gives the default
+directory in which to place extracted files. Otherwise, FM/2 takes a
+wild, hairy guess about where you want the extracted files to go
+(although it'll let you override manually). You can enter "*" as the
+extract path and FM/2 will use the directory in which the archive
+resides. The :link reftype=hd res=99970.Find:elink. button can be used
+to find a directory and fill this field in automatically.
+:h3 res=92400 name=PANEL_TREEPAGE.Tree page
+:i1 id=aboutTREEP.Tree page
 :artwork name='bitmaps\tree.bmp' align=left.
+:p.
 This page contains controls that affect the Drive Tree.
 :p.
 …
 The :hp6.Double-click Opens:ehp6. toggle, if on, causes FM/2 to always
 open a new Directory Container window when a Drive Tree directory is
 double clicked.  It's probably not useful to have both this toggle and
+double clicked. It's probably not useful to have both this toggle and
 the Follow Drive Tree toggle on simultaneously.
 :p.
 …
 :h3 res=99990 name=PANEL_TREESORTPAGE.Drive Tree sort/views page
 :i1 id=aboutTREESP.Drive Tree sort/views page
+:h3 res=99990 name=PANEL_TREESORTPAGE.Tree sort/views page
+:i1 id=aboutTREESP.Tree sort/views page
 :artwork name='bitmaps\tree.bmp' align=left.
+:p.
 This page contains controls that affect Drive Tree sorting and view type.
 :p.
 …
-:h3 res=99940 name=PANEL_ARCPAGE.Archive page
-:i1 id=aboutARCP.Archive page
-:artwork name='bitmaps\archive.bmp' align=left.
-This page contains controls relating to archivers and Archive
-Containers.
-:p.
-If the :hp6.Show archiver activity:ehp6. toggle is checked, FM/2 runs
-archiver windows in the foreground.  Normally it runs them in the
-background, minimized, so you'd have to use the task list to pull them
-to the foreground if you want to see them.
-:p.
-The :hp6.Quick arc find:ehp6. toggle, if checked, causes FM/2 to check
-only files with extensions that match those configured in ARCHIVER.BB2
-as potential archives during a drag and drop operation.  If you're
-dragging over files on a floppy or network directory, this can speed
-things up a bit.
-:p.
-The :hp6.Folder after extract:ehp6. toggle, if on, causes FM/2 to create
-a folder to hold objects extracted from an archive via an Archive
-Container.  You'll be given an opportunity to abort the folder creation
-or to decide where the folder will be located and what it'll be named.
-:p.
-You can set a :hp6.Default archiver:ehp6. so that, when you're archiving
-files and directories, this archiver is the default for the :hp1.Select
-Archiver:ehp1. dialog.
-:p.
-The :hp6.Ext. Path:ehp6. field, if anything is in it, gives the default
-directory in which to place extracted files.  Otherwise, FM/2 takes a
-wild, hairy guess about where you want the extracted files to go
-(although it'll let you override manually).  You can enter "*" as the
-extract path and FM/2 will use the directory in which the archive
-resides.  The :link reftype=hd res=99970.Find:elink. button can be used
-to find a directory and fill this field in automatically.
 :h3 res=92200 name=PANEL_VIEWPAGE.Viewers page
 :i1 id=aboutVIEWP.Viewers page
 :artwork name='bitmaps\viewer.bmp' align=left.
+:p.
 This page contains controls relating to viewers.
 :p.
 …
 Without this checked, FM/2 will use an internal MLE-based viewer/editor
 which can be considerably slower, but does allow the option of editing
 files.  It is strongly suggested that you check this option and use an
+files. It is strongly suggested that you check this option and use an
 external editor rather than the internal editor, since editors are
 rather complex programs in their own right, and the internal version is
 …
 The :hp6.Check for multimedia w/ MMPM/2:ehp6. toggle can be unchecked to
 cause FM/2 to :hp1.not:ehp1. use the MMPM/2 interface to determine
 whether or not a file to be viewed is a multimedia type.  The reason for
+whether or not a file to be viewed is a multimedia type. The reason for
 this toggle is to avoid crashing FM/2 if you've installed a buggy MMPM/2
+I/O procedure.  Some desktop "enhancement" programs install such buggy
+IOProcs.  If you can't get it fixed, at least you can work around it
+(sigh).  You can manually put back some of this functionality using
+FM/2's :link reftype=hd res=90400.Associations:elink. feature.
+:p.
+I/O procedure. Some desktop "enhancement" programs install such buggy
+IOProcs. If you can't get it fixed, at least you can work around it
+(sigh). You can manually put back some of this functionality using
+FM/2's :link reftype=hd res=90400.Associations:elink. feature. If you have
+installed Russel O'Connor's MP3 IOProcs you should uncheck this feature
+because it results in many non-multimedia programs being identified as
+multimedia and some multimedia not being identified as such. Use the
+:link reftype=hd res=90400.Associations:elink. instead.
+:p.
 The :hp6.Guess view type:ehp6. toggle, if on, causes FM/2 to guess at the
 type of the file being viewed (text or binary) and display it accordingly.
 :p.
 The :hp6.Run Viewer as child session:ehp6. toggle causes FM/2 to run the
 :hp1.Viewer:ehp1. program (see below) as a child session.  The main result
+:hp1.Viewer:ehp1. program (see below) as a child session. The main result
 of this is that the Viewer will close when FM/2 closes.
 :p.
 You can fill in the names of programs to run to view WWW (web --
 http&colon.//) or FTP (ftp&colon.//) internet components when they're
 encountered in text in the internal viewers here.  In the faster
+encountered in text in the internal viewers here. In the faster
 (non-MLE) internal viewer, double-clicking the line containing the
 component causes it to be viewed (you're given a choice of component if
 there's more than one on the line).  For WWW components, the prefacing
 "http&colon.//" is included.  For FTP components, the prefacing
 "ftp&colon.//" is :hp1.not:ehp1. included.  In the MLE-based internal
+there's more than one on the line). For WWW components, the prefacing
+"http&colon.//" is included. For FTP components, the prefacing
+"ftp&colon.//" is :hp1.not:ehp1. included. In the MLE-based internal
 viewer/editor, you highlight the desired text and choose to view the
 component from a context menu.  The command line that you enter here is
+component from a context menu. The command line that you enter here is
 automatically appended with a space and then the component descriptor
 from the text.
 …
 you have no text viewer, binary viewer or text editor configured here.
 It's recommended that you fill these fields in with whatever editors you
 like rather than use the internals.  The :link reftype=hd
+like rather than use the internals. The :link reftype=hd
 res=99970.Find:elink. button can be used to find a program and fill
 these fields in automatically (see :link reftype=hd
 res=99970.examples:elink. at that topic).  Don't forget that you can
+res=99970.examples:elink. at that topic). Don't forget that you can
 cause FM/2 to automatically use many different types of viewing programs
 based on the type of file using the :link reftype=hd
+res=90400.Associations:elink. feature.
+res=90400.Associations:elink. feature.
+:h4 res=99970 name=PANEL_FIND.Find button
+:i1 id=aboutFINDB.Find button
+:artwork name='bitmaps\find.bmp' align=left.
+:p.
+The :hp1.Find:ehp1. button can be clicked to bring up a dialog that will
+let you point-and-click on a file or directory name that will be
+imported to the current entry field. For example, if you're in the
+:hp6.Editor:ehp6. entry field and click Find, you'll get a standard OS/2
+open dialog which you may use to find your editor executable.
+:p.
+Examples:
+:p.
+Editor:  "EPM.EXE %a"
+.br
+or       "AE.EXE %a"
+.br
+or       "VS.EXE %a"
+.br
+or       "CMD.EXE /C START /C /FS EMACS.EXE %a"
+.br
+Viewer:  "HVPM.EXE /K %a" (Hyperview PM, excellent viewer)
+.br
+or       "LSTPM.EXE %a"
+.br
+or       "LIST2.EXE %a"
+.br
+Compare: "COMP.COM %a"
+.br
+or       "CONTRAST.EXE %a"
+.br
+or       "GFC.EXE %a"
+.br
+or       "CMD.EXE /C MYCOMP.CMD %a"
+.br
+DirCmp:  "PMDMATCH.EXE" (PMDirMatch, excellent directory comparitor)
+.br
+Virus:   "OS2SCAN.EXE %p /SUB /A"
+:p.
+See also :link reftype=hd res=100075.Metastrings:elink..
 …
 :p.
 If the :hp6.Dir Cmp:ehp6. field is filled in, FM/2 runs that when
 directories are to be compared.  FM/2 fills in the name of the two
+directories are to be compared. FM/2 fills in the name of the two
 directories after the text entered in this field -- no "%a" or other
 metastring is required.
 …
 :artwork name='bitmaps\monolith.bmp' align=left.
+:p.
 This page contains controls that affect FM/2 when run as a monolithic
 program (a Drive Tree and none or more Directory Containers contained
 …
 Container is opened.
 :p.
 The :hp6.Recent Dirs:ehp6. toggle is a 3-position toggle.  If checked,
+The :hp6.Recent Dirs:ehp6. toggle is a 3-position toggle. If checked,
 FM/2 places temporary entries for directories "visited" during a session
 to the user directory quicklist and Walk Directories dialog.  If greyed,
+to the user directory quicklist and Walk Directories dialog. If grayed,
 FM/2 also places temporary entries for any directory chosen using the
 :link reftype=hd res=91500.Walk Directories:elink. dialog.
 …
 checked, you'll have to set up each application separately, but
 configurations can be different than that in the monolithic FM/2
 application itself.  If you don't understand that, let's try this&colon.
+application itself. If you don't understand that, let's try this&colon.
 if you run the Visual Tree program a lot, you'll probably want to check
 this.  Otherwise, you won't.
+this. Otherwise, you won't.
 :p.
 If you check the :hp6.Free Drive Tree:ehp6. toggle, FM/2 will allow you
 to move the Drive Tree Container.  Otherwise it "pins" it in the upper
+to move the Drive Tree Container. Otherwise it "pins" it in the upper
 left corner of the client window.
 :p.
 Normally FM/2 leaves a space below the Drive Tree just the right size for
 a minimized window.  Checking the :hp6.No space under Tree:ehp6. toggle
+a minimized window. Checking the :hp6.No space under Tree:ehp6. toggle
 causes FM/2 to start without this space below the Drive Tree.
 :p.
 The :hp6.Save state of dir windows:ehp6. toggle, if checked, causes FM/2
 to "remember" the directory windows that are open when you close FM/2 so
 that it can open them again when you restart FM/2.  If you turn this on,
+that it can open them again when you restart FM/2. If you turn this on,
 be sure to play with the Free Tree and Autotile toggles under the Windows
 menu to achieve the desired effect (everyone will want a different
 effect).  You'll probably want to omit any directories from the command
+effect). You'll probably want to omit any directories from the command
 line if you turn on this toggle.
 :p.
 …
 :p.
 If :hp6.Split Status:ehp6. is checked, you get two status lines at the
 bottom of the FM/2 window instead of one.  The left status line typically
+bottom of the FM/2 window instead of one. The left status line typically
 contains information about the current container, the right about the
 current object in the container.  Cool.
+current object in the container. Cool.
 :p.
 The :hp6.Start minimized:ehp6. and :hp6.Start maximized:ehp6. toggles
 …
 The :hp6.Minimize to databar:ehp6. toggle, if on, causes FM/2 to
 minimize to a small, bar-shaped window (the :link reftype=hd
 res=99000.databar:elink.) showing some system information.  The
+res=99000.databar:elink.) showing some system information. The
 databar can be run separately if desired -- look in the FM/2 folder.
 :p.
 The :hp6.Tile horizontal:ehp6. toggle, if on, causes FM/2 to favor
 tiling windows so they're taller than wide.  I suggest you think twice
+tiling windows so they're taller than wide. I suggest you think twice
 before doing this; displaying files is basically a horizontal operation,
 not vertical (at least in countries that read left to right or right to
 left).  In other words, using this toggle will cause windows to be
+left). In other words, using this toggle will cause windows to be
 biased to display side-by-side rather than one above another, which
 means that the horizontal reading space is limited, resulting in more
 …
 The :hp6.Animate:ehp6. toggle, when on, causes internal FM/2 windows to
 be animated when they open and close (if you have animation turned on in
 the WPS System object, of course).  Silly.
+the WPS System object, of course). Silly.
 :p.
 The :hp6.Blue/yellow LEDs:ehp6. toggle, when checked, causes FM/2 to
 display the thread LED as blue (off) and yellow (on) LEDs rather than
 the default red (off) and green (on) LEDs.  The change will not show up
+the default red (off) and green (on) LEDs. The change will not show up
 on the application window until you close and then reopen FM/2.
 :p.
 …
 :artwork name='bitmaps\general.bmp' align=left.
+:p.
 This page contains controls that didn't seem to fit anywhere else.
 :p.
 :hp6.Confirm delete:ehp6. controls whether FM/2 will ask you to confirm
 the deletion of files (deleting directories or hidden/system files
 always requires confirmation).  It is recommended that you leave this
+always requires confirmation). It is recommended that you leave this
 option on; FM/2 will let you confirm all files on which you're acting
 from one dialog, so it has minimal impact and provides a safety net.
 :p.
 The :hp6.Verify disk writes:ehp6. toggle turns system-level write
 verification on and off.  This is like typing :link reftype=launch
+verification on and off. This is like typing :link reftype=launch
 object='CMD.EXE' data='/C HELP VERIFY'.VERIFY ON:elink. or VERIFY OFF at
 a command line.
 …
 The :hp6.Don't move my mouse!:ehp6. toggle keeps FM/2 from moving your
 mouse (to place it in the center of a popup menu or over the Okay button
 in some dialogs).  Some people like the help, others don't.  Take your
+in some dialogs). Some people like the help, others don't. Take your
 pick.
 :p.
 :hp6.Link Sets Icon:ehp6. changes the action of a link-drag.  If this
+:hp6.Link Sets Icon:ehp6. changes the action of a link-drag. If this
 toggle is set, a link drag causes FM/2 to try to set the icon of the
 target to the icon of the first dropped object (if the first dropped
 object has no .ICON EA and is not an icon file, the target's icon is
 reset.  Note that OS/2 sometimes buffers this info and an icon change
 may not show up immediately).  If not set, a link drag causes FM/2 to do
+reset. Note that OS/2 sometimes buffers this info and an icon change
+may not show up immediately). If not set, a link drag causes FM/2 to do
 a compare of the target with the dropped objects.
 :p.
 If :hp6.Default action Copy:ehp6. is checked, FM/2's windows perform a
 copy rather than move by default (note the highlighting on the mouse
 pointer as your cue).  Instead of pressing the Ctrl key to change a drag
+pointer as your cue). Instead of pressing the Ctrl key to change a drag
 from a move to a copy, you'll need to press the Shift key to change a
 drag from a copy to a move (don't ask me why).  Note that this is the
 opposite of the standard OS/2 behavior, so know what you're doing.  I
+drag from a copy to a move (don't ask me why). Note that this is the
+opposite of the standard OS/2 behavior, so know what you're doing. I
 remind you that pressing F1 when you have a target in an FM/2 window
 will display some help on what the drag command would have performed.
 …
 :p.
 FM/2 usually performs copy and move actions at the lowest "normal"
 priority available.  If you'd like FM/2 to use a true "idle" priority,
 check the :hp6.Idle Copy:ehp6. toggle.  Warning&colon.  if a DOS program
+priority available. If you'd like FM/2 to use a true "idle" priority,
+check the :hp6.Idle Copy:ehp6. toggle. Warning&colon. if a DOS program
 is running, even in the background, idle priority threads slow
 :hp2.way:ehp2. down.  :hp3.Performance at true idle with DOS programs
+:hp2.way:ehp2. down. :hp3.Performance at true idle with DOS programs
 running may not be acceptable.:ehp3.
 :p.
 …
 :p.
 :hp6.Default delete perm.:ehp6. controls which type of deletion is the
 default for the Delete context submenu.  If this is checked, the default
+default for the Delete context submenu. If this is checked, the default
 is permanent (unrecoverable) deletion.
 :p.
 …
 default, FM/2 allows you to confirm the target directory to be used when
 you elect to move or copy file system objects using menu or accelerator
 key commands.  Otherwise, the operation is performed without
+key commands. Otherwise, the operation is performed without
 intervention by you, moving or copying the objects to the :hp6.:link
 reftype=hd res=100065.Target directory:elink.:ehp6. (if one is set, of
 …
 :artwork name='bitmaps\scan.bmp' align=left.
+:p.
 This page contains controls related to how FM/2 scans your drives.
 :p.
 :hp6.Uppercase names:ehp6. and :hp6.Lowercase names:ehp6. control how
 FM/2 pretreats filenames before inserting them into the container.  The
 default is not to change the case of the filenames at all.  Changing
+FM/2 pretreats filenames before inserting them into the container. The
+default is not to change the case of the filenames at all. Changing
 these toggles will have an effect on the next rescan.
 :p.
 If :hp6.Load Subjects:ehp6. is checked, FM/2 loads object descriptions
 from their standard WPS .SUBJECT EAs during scans.  If you change the
+from their standard WPS .SUBJECT EAs during scans. If you change the
 state of this toggle, you'll need to rescan to get the change to show up
 in FM/2's containers.  Note that only the Details view shows Subjects.
 Subjects may be direct-edited when showing in the container.  You can
+in FM/2's containers. Note that only the Details view shows Subjects.
+Subjects may be direct-edited when showing in the container. You can
 also pick :hp1.Subject:ehp1. from a context menu, whether Subjects are
 being loaded during scans or not, to view and optionally change the
 object description.  You can turn this off to increase scanning speed.
+object description. You can turn this off to increase scanning speed.
 You can also adjust this on a drive-by-drive basis from the command line
 (see the :link reftype=launch object='E.EXE'
 data='READ.ME'.READ.ME:elink. that came with FM/2).
+data='\FM2\README'.READ.ME:elink. that came with FM/2).
 :p.
 If :hp6.Load Longnames:ehp6. is checked, FM/2 loads the .LONGNAME
 extended attribute for non-HPFS drives.  This attribute usually contains
+extended attribute for non-HPFS drives. This attribute usually contains
 a long name for objects that should be restored if the object is moved
 to an HPFS drive.  As for Subject, Longnames are only shown in the
 Details view.  You can turn this off to marginally increase scanning
 speed.  You can also adjust this on a drive-by-drive basis from the
+to an HPFS drive. As for Subject, Longnames are only shown in the
+Details view. You can turn this off to marginally increase scanning
+speed. You can also adjust this on a drive-by-drive basis from the
 command line (see the :link reftype=launch object='E.EXE'
 data='READ.ME'.READ.ME:elink. that came with FM/2).
+data='\FM2\README'.READ.ME:elink. that came with FM/2).
 :p.
 If :hp6.Load file icons:ehp6. and/or :hp6.Load directory icons:ehp6. are
 checked, FM/2 will load the icons of objects from the file system;
 otherwise it uses defaults.  Although turning these off can speed up
 scanning, it makes for boring containers.  This is PM, folks, enjoy the
+otherwise it uses defaults. Although turning these off can speed up
+scanning, it makes for boring containers. This is PM, folks, enjoy the
 bells and whistles! You can also adjust this on a drive-by-drive basis
 from the command line (see the :link reftype=launch object='E.EXE'
 data='READ.ME'.READ.ME:elink. that came with FM/2) so that you can, for
+data='\FM2\README'.READ.ME:elink. that came with FM/2) so that you can, for
 instance, skip reading in icons from very slow drives (CD or floppy, for
 example) and/or from disks containing only DOS programs (DOS programs
 don't normally have special icons associated with them, anyway).
 :p.
 :hp6.Notes:ehp6.&colon.  some very slow drives (like EZ and ZIP drives)
+:hp6.Notes:ehp6.&colon. some very slow drives (like EZ and ZIP drives)
 :hp1.will:ehp1. benefit from turning off some of the automatic
 information gathering above.  Experiment and adjust to taste. See also
+information gathering above. Experiment and adjust to taste. See also
 the :link reftype=hd res=99980.Drive flags:elink. topic.
 :p.
 …
 a find for more than one file at a time from working correctly. Symptoms
 range from invalid data returned to trapping of the requesting
 application.  While you'd think that these bugs would be fixed (and they
 are), new versions seem to reintroduce them again.  Therefore, FM/2
 provides the :hp6.Remote find bug:ehp6. toggle.  If checked, FM/2 will
 only ask for one file at a time from remote drives.  This is slower, but
 at least useable.  In the meantime, ask you system administrator to
+application. While you'd think that these bugs would be fixed (and they
+are), new versions seem to reintroduce them again. Therefore, FM/2
+provides the :hp6.Remote find bug:ehp6. toggle. If checked, FM/2 will
+only ask for one file at a time from remote drives. This is slower, but
+at least usable. In the meantime, ask you system administrator to
 upgrade the LAN software -- most of these bugs have been fixed in newer
 versions.
 :p.
 If you turn this toggle off (it's on by default) and FM/2 starts
 behaving strangely, turn it back off.  If FM/2 traps and you can't get
+behaving strangely, turn it back off. If FM/2 traps and you can't get
 to the settings page, disconnect from the network, start FM/2, then
 turn off the toggle.  If that's not possible for some reason, use
+turn off the toggle. If that's not possible for some reason, use
 FM/2's INI editor to view FM3.INI and delete the "RemoteBug" keyword
 from the INI (which will cause FM/2 to revert to the default setting).
 …
 even if they do contain subdirectories until you double-click the drive.
 Floppy drives A&colon. and B&colon. receive this treatment without this
 toggle; it's for other removable drives, like CD-ROM drives.  This was
+toggle; it's for other removable drives, like CD-ROM drives. This was
 added to allow folks with CD-ROM carousels to avoid having each CD
 loaded and scanned automatically at FM/2 startup.
 :p.
 The :hp6.Findbuf:ehp6. spin button controls how many files FM/2 searches
 for in one system call.  The higher this number, the faster FM/2 works
+for in one system call. The higher this number, the faster FM/2 works
 (with properly operating FSDs that support "finding" more than one file
 at a time -- unfortunately, the FSDs that can benefit the most from this,
 network FSDs, are the ones most often broken), but the more memory is
 temporarily consumed as a container is filled.  If you habitually work
+temporarily consumed as a container is filled. If you habitually work
 with directories containing great numbers of files and have sufficient
 memory, boosting this may be a good idea.  On the other hand, if you are
+memory, boosting this may be a good idea. On the other hand, if you are
 extremely limited in memory (less than 16 megs), reducing this might be
 the thing to do.  The range is 16 to 2048, with 128 the default.
+the thing to do. The range is 16 to 2048, with 128 the default.
 …
 :artwork name='bitmaps\bubble.bmp' align=left.
+:p.
 This page controls where FM/2 shows bubble help.
 :p.
 …
 :p.
 :hp6.Drivebar help:ehp6. controls whether FM/2 shows drive freespace
 when the mouse pointer passes over drivebar buttons.  FM/2 will not show
+when the mouse pointer passes over drivebar buttons. FM/2 will not show
 freespace for floppy drives A&colon. or B&colon., for CD-ROM drives, or
 for drives marked as Slow in the :link reftype=hd res=99980.Drive
 …
 :artwork name='bitmaps\flash.bmp' align=left.
+:p.
 This page allows you to select from a few pre-configured setups for FM/2
 in general.  You'll see this page automatically the first time you run
 FM/2.  Pick something that looks close to what you want without worrying
 too much about it  -- you can always change it later.  The idea is to
+in general. You'll see this page automatically the first time you run
+FM/2. Pick something that looks close to what you want without worrying
+too much about it  -- you can always change it later. The idea is to
 give you some quick choices about the general way you'd like FM/2 to
 look and behave, and allow you to tweak specifics later as you get some
 …
 You'll have to use the mouse and work from context menus and accelerator
 keys alone, but you'll have the maximum amount of free space within the
 main FM/2 window.  :hp3.Hint&colon.:ehp3. The System Menu contains the
+main FM/2 window. :hp3.Hint&colon.:ehp3. The System Menu contains the
 command to unhide the pulldown menu, if that's going too far for you.
 :p.
 …
 :p.
 :hp6.Max filenames:ehp6. puts FM/2's Directory Containers into a state
 that allows the most filenames per container.  Rather unattractive.
+that allows the most filenames per container. Rather unattractive.
 :p.
 :hp6.Max speed:ehp6. turns off some automatic information gathering to
 …
 Windows file manager, with one Directory container.
 :p.
 :hp6.Hector's way:ehp6. sets FM/2 up the way the author likes it.  Your
+:hp6.Hector's way:ehp6. sets FM/2 up the way the author likes it. Your
 mileage may vary.
 :p.
 …
+:h3 res=99970 name=PANEL_FIND.Find button
+:i1 id=aboutFINDB.Find button
+:artwork name='bitmaps\find.bmp' align=left.
+The :hp1.Find:ehp1. button can be clicked to bring up a dialog that will
+let you point-and-click on a file or directory name that will be
+imported to the current entry field.  For example, if you're in the
+:hp6.Editor:ehp6. entry field and click Find, you'll get a standard OS/2
+open dialog which you may use to find your editor executable.
+:p.
+Examples:
+:p.
+Editor:  "EPM.EXE %a"
+.br
+or       "Q.EXE %a"
+.br
+or       "VS.EXE %a"
+.br
+or       "CMD.EXE /C START /C /FS EMACS.EXE %a"
+.br
+Viewer:  "HVPM.EXE /K %a" (Hyperview PM, excellent viewer)
+.br
+or       "LSTPM.EXE %a"
+.br
+or       "LIST2.EXE %a"
+.br
+Compare: "COMP.COM %a"
+.br
+or       "CONTRAST.EXE %a"
+.br
+or       "GFC.EXE %a"
+.br
+or       "CMD.EXE /C MYCOMP.CMD %a"
+.br
+DirCmp:  "PMDMATCH.EXE" (PMDirMatch, excellent directory comparitor)
+.br
+Virus:   "OS2SCAN.EXE %p /SUB /A"
+:p.
+See also :link reftype=hd res=100075.Metastrings:elink..

trunk/dll/ipf/objcnr.ipf

-              r2
+              r268
 :i1 id=aboutObjectPath.Object Container
 This dialog allows you to select a new folder (directory) to hold
 objects that FM/2 creates.  By default it is <WP_DESKTOP>.   FM/2 tries
+objects that FM/2 creates. By default it is <WP_DESKTOP>.  FM/2 tries
 to find the directory being used as the desktop folder first in the OS/2
 system INI, and if that fails, uses the directory \DESKTOP on your boot
 drive as the "desktop window object" directory -- this is the OS/2 2.1+
+default.  I suppose future versions of OS/2 could break this and make
+an update necessary, but IBM seems to think (though won't guarantee) it
+should always work.
+default.
 :p.
 A button labelled :hp1.Desktop:ehp1. allows you to restore the default
 <WP_DESKTOP> setting.  This will work whether the above fails or not.
+A button labeled :hp1.Desktop:ehp1. allows you to restore the default
+<WP_DESKTOP> setting. This will work whether the above fails or not.
 :h2 res=93100 name=PANEL_QUICKTREE.Quick Tree
 …
 :p.
 If you select one of these subdirectories, the Directory Container
 window will switch to look into that directory.  You can click
+window will switch to look into that directory. You can click
 Cancel if you change your mind.
 :p.

trunk/dll/ipf/printer.ipf

-              r10
+              r268
 :i1 id=aboutPrinter.Print files
 :artwork name='..\..\bitmaps\print.bmp' align=center.
+:p.
 This dialog, which appears before a selected group of one or more files
 is to be printed, lets you finalize your selection and set the parameters
 …
 :p.
 The listbox at the top of the dialog contains the files that are to be
 printed.  You can unhighlight (deselect) any files that you do
 :hp1.not:ehp1. want to print.  :hp6.Hint:ehp6.&colon.  you might need to
+printed. You can unhighlight (deselect) any files that you do
+:hp1.not:ehp1. want to print. :hp6.Hint:ehp6.&colon. you might need to
 hold down the Ctrl key while clicking to unhighlight the first file.
 :p.
 …
 specify the printer to which output should go (default is PRN, the
 default system printer, but you could specify LPT1, LPT2, etc., or even
 a text file).  Note that FM/2's printing is really meant for situations
+a text file). Note that FM/2's printing is really meant for situations
 in which the PM printer objects and spooler aren't available -- you can
 just drag objects to the printer objects otherwise.
 :p.
 The rest of the controls are used to determine how FM/2 should format
 the text file for printing.  You can specify the width and length of the
+the text file for printing. You can specify the width and length of the
 page (in columns and rows respectively), how many lines to leave blank
 for bottom and top margins, how many characters to leave blank for left
 and right margins, whether to print pages sequentially or print first
 odd pages, then even pages (:hp1.Alternate pages:ehp1.).  You can specify
+odd pages, then even pages (:hp1.Alternate pages:ehp1.). You can specify
 the line spacing used (1 for single-spaced, 2 for double-spaced, etc.),
 and tell FM/2 if it needs to print a formfeed before and/or after each
+and tell FM/2 if it needs to send a formfeed before and/or after each
 file it prints.
 :p.
 Click :hp1.Okay:ehp1. when you're ready to print.  Click :hp1.Cancel:ehp1.
+Click :hp1.Okay:ehp1. when you're ready to print. Click :hp1.Cancel:ehp1.
 if you changed your mind and don't want to print anything.
 :p.
 :hp6.Notes&colon.:ehp6.
 :p.
 Not all files will print well with formatted printing turned on.  The
+Not all files will print well with formatted printing turned on. The
 file should :hp1.not:ehp1. contain any control codes aside from carriage
 returns and linefeeds.  The file's lines should be short enough to fit
 within the confines of width - (left margin + right margin).  For files
+returns and linefeeds. The file's lines should be short enough to fit
+within the confines of width - (left margin + right margin). For files
 that were formatted to be viewed on-screen, this may mean setting your
 printer to use a narrower typeface and increasing the width parameter in
 the FM/2 print setup dialog above 80.  Refer to your printer
+the FM/2 print setup dialog above 80. Refer to your printer
 documentation for how to change the default font.
 :p.
 When printing :hp1.Alternate pages:ehp1., FM/2 reverses the left and
 right margins when printing even numbered pages.  This is designed to
+right margins when printing even numbered pages. This is designed to
 let you print front and back (page 2 on the back of page 1, etc.) and
 then bind the result along the left side (left of page 1, right of page
 , etc.).  FM/2 will first print the odd numbered pages, beginning with
+, etc.). FM/2 will first print the odd numbered pages, beginning with
 page 1, then prompt you before beginning to print the even numbered
 pages, beginning with page 2, thereby allowing you to reload the printer

trunk/dll/ipf/rename.ipf

-              r10
+              r268
 :i1 id=aboutRenaming.Renaming
 :artwork name='..\..\bitmaps\rename.bmp' align=center.
+When you rename a file sytem object other than by :link reftype=hd
+:p.
+When you rename a file system object other than by :link reftype=hd
 res=98200.Direct Editing:elink., or a naming conflict arises, you get
 the Rename dialog.  Note that not all the controls discussed appear for
+the Rename dialog. Note that not all the controls discussed appear for
 simple rename procedures -- some are applicable only when copying or
 moving files.
 …
 renaming, the target name is initially the same as the source name). If
 the target file exists, you will be told whether the source is larger or
 smaller, older or newer.  You will be told whether the source and target
 are files or directories.  Sometimes you may see a warning "cannot
+smaller, older or newer. You will be told whether the source and target
+are files or directories. Sometimes you may see a warning "cannot
 access source."  This means that FM/2 could not open the source file in
 a test, and may indicate that the file is already in use and thus OS/2
 may not allow it to be renamed, moved or copied.  You can use this
+may not allow it to be renamed, moved or copied. You can use this
 information display to make decisions more easily.
 :p.
 After entering the new target name, click :hp1.Okay:ehp1..  If the new
+After entering the new target name, click :hp1.Okay:ehp1.. If the new
 target name exists, the display will be updated to reflect the new
 information.  You can, at that point, enter a new name to avoid the
+information. You can, at that point, enter a new name to avoid the
 conflict or click :hp1.Overwrite:ehp1. (which will destroy the old
 target file, keeping in mind that you can't overwrite a file with
 itself).  :hp1.Skip:ehp1. can be used to skip one file when you are renaming
 several in one action; nothing will be done for that file.  Click
+itself). :hp1.Skip:ehp1. can be used to skip one file when you are renaming
+several in one action; nothing will be done for that file. Click
 :hp1.Cancel:ehp1. if you change your mind and want to abort the whole
 thing.
 :p.
 The :hp1.Rename Existing:ehp1. button allows you to rename (move) the
 existing file system object which is causing a naming conflict.  For
+existing file system object which is causing a naming conflict. For
 example, if you are trying to copy a file to "C&colon.\MYFILE" and a
 "C&colon.\MYFILE" already exists, you could change the target name as
 …
 in combination to avoid seeing this screen again for naming conflicts.
 Files which have existing targets that do not match an overwrite
 characteristic will be automatically skipped.  For example, if you don't
+characteristic will be automatically skipped. For example, if you don't
 check either of the Overwrite... checkboxes, all existing files will be
 skipped, but if you check the ...older checkbox, all existing files
 older than the source file will be overwritten, while existing files
 newer than the source file will be skipped.  Exception:  You will always
+newer than the source file will be skipped. Exception:  You will always
 be prompted if you try to overwrite a directory with a file.
 :p.

trunk/dll/ipf/select.ipf

-              r10
+              r268
 :artwork name='..\..\bitmaps\select.bmp' align=center.
 :artwork name='..\..\bitmaps\deselect.bmp' align=center.
 The Ctrl + F8 accelerator calls up the Select menu for a given
 container. You can also, of course, get to it with the mouse via the
 …
 :p.
 What follows is an item-by-item description of the commands in the
 Select menu.  Where both Select and Deselect commands are available,
+Select menu. Where both Select and Deselect commands are available,
 only the Select command will be discussed to save space and avoid
 repetition.
 :p.
 :hp1.Select All:ehp1.  Selects all objects in a container.
+:hp1.Select All:ehp1. Selects all objects in a container.
 :hp1.Deselect All:ehp1. has an accelerator Ctrl + \.
 :p.
 :hp1.Select All Files:ehp1.  Selects all the file objects in a
 container.  The accelerator key Ctrl + / is assigned to this command.
+:hp1.Select All Files:ehp1. Selects all the file objects in a
+container. The accelerator key Ctrl + / is assigned to this command.
 :p.
+:hp1.Select All Dirs:ehp1.  Selects all the directory objects in a
+container.  The accelerator key Shift + Ctrl + ? is assigned to this
+command (same as for Select All Files with the addition of the Shift
+key).  :hp1.Deselect All Dirs:ehp1. has an accelerator Shift + Ctrl + |
+(same as Deselect All with the addition of the Shift key).
+:hp1.Select All Dirs:ehp1. Selects all the directory objects in a
+container. The accelerator key Shift + Ctrl + ? is assigned to this
+command :hp1.Deselect All Dirs:ehp1. has an accelerator Shift + Ctrl + |
 :p.
 :hp1.Select Mask:ehp1.  Allows you to select files that match a filemask.
+:hp1.Select Mask:ehp1. Allows you to select files that match a filemask.
 The same dialog is used for this command that's used for the :link
 reftype=hd res=93400.Filter:elink. command.  When you first initiate
+reftype=hd res=93400.Filter:elink. command. When you first initiate
 this command, FM/2 fills in a default mask built from the current
 object's name.  So, to quickly select all the *.BAK files in a
+object's name. So, to quickly select all the *.BAK files in a
 container, you could select one of the files, then type Ctrl + = (the
 accelerator assigned to Select Mask) and press [Enter] to accept the
 default filemask built by FM/2 (*.BAK).
 :p.
 :hp1.Select clipboard:ehp1.  If the OS/2 clipboard contains a list of files
+:hp1.Select clipboard:ehp1. If the OS/2 clipboard contains a list of files
 (such as can be created with the :hp1.Save to clipboard:ehp1. command),
 you can select any files present in both the container and the list with
 this command.  The accelerator for this command is Ctrl + ].  The
+this command. The accelerator for this command is Ctrl + ]. The
 accelerator for the Deselect clipboard command is Shift + Ctrl + }.
 :p.
 :hp1.Select List:ehp1.  If you've saved a list to a file (such as can be
+:hp1.Select List:ehp1. If you've saved a list to a file (such as can be
 created with the :link reftype=hd res=96000.Save to list file:elink.
 command), you can select any files present in both the listfile and the
 container with this command.
 :p.
 :hp1.Reselect:ehp1.  This command causes the container to reselect the
 last selected items.  The accelerator is Ctrl + '.
+:hp1.Reselect:ehp1. This command causes the container to reselect the
+last selected items. The accelerator is Ctrl + '.
 :p.
 :hp1.Invert selection:ehp1.  Selects what isn't, deselects what is.  In
+:hp1.Invert selection:ehp1. Selects what isn't, deselects what is. In
 other words, reverses the current selection set.
+The accelerator is Ctrl + ;.
 :p.
 :hp2.Compare selections:ehp2.
 …
 FM/2 provides Directory Containers with special selection commands that
 can be used to select file objects based on their relationship to file
 objects in other open Directory Containers.  These commands are extremely
+objects in other open Directory Containers. These commands are extremely
 powerful tools that can let you, for instance, compare two directories to
 see what's different about them.  See also :link reftype=hd
+see what's different about them. See also :link reftype=hd
 res=94900.Compare Directories:elink..
 :p.
 :hp1.Select if in all:ehp1.  This command selects any file objects that
+:hp1.Select if in all:ehp1. This command selects any file objects that
 exist in all open Directory Containers.
 :p.
 :hp1.Select if in more than one:ehp1.  Selects any file objects that
+:hp1.Select if in more than one:ehp1. Selects any file objects that
 exist in more than one open Directory Containers.
 :p.
 :hp1.Select if in one:ehp1.  Selects any file objects that exist in only
+:hp1.Select if in one:ehp1. Selects any file objects that exist in only
 one open Directory Container.
 :p.
 :hp1.Select newest:ehp1.  Selects the newest file objects that exist in
+:hp1.Select newest:ehp1. Selects the newest file objects that exist in
 more than one open Directory Container.
 :p.
 :hp1.Select oldest:ehp1.  Selects the oldest file objects that exist in
+:hp1.Select oldest:ehp1. Selects the oldest file objects that exist in
 more than one open Directory Container.
 :p.
 :hp1.Select largest:ehp1.  Selects the largest file objects that exist in
+:hp1.Select largest:ehp1. Selects the largest file objects that exist in
 more than one open Directory Container.
 :p.
 :hp1.Select smallest:ehp1.  Selects the smallest file objects that exist
+:hp1.Select smallest:ehp1. Selects the smallest file objects that exist
 in more than one open Directory Container.

trunk/dll/ipf/seticon.ipf

-              r2
+              r268
 object Information dialog.
 :p.
 Set the radio button of the system pointer you want to change.  Then
 click Okay.  Click Cancel to abort if you change your mind.
+Set the radio button of the system pointer you want to change. Then
+click Okay. Click Cancel to abort if you change your mind.
 :p.
 Changes to system pointers are persistent (they stick around even when

trunk/dll/ipf/shadow.ipf

-              r10
+              r268
 :i1 id=aboutShadow.Shadow
 :artwork name='..\..\bitmaps\shadow.bmp' align=center.
+:p.
 FM/2 has the ability to create shadows of objects on your WPS desktop
 (or in other WPS folders).  To create shadows, select objects in an FM/2
+(or in other WPS folders). To create shadows, select objects in an FM/2
 window, then select :hp1.Shadow:ehp1. from a context menu or the Files
 pulldown submenu (Create Objects submenu).
 :p.
 If only one shadow is being created, the shadow is placed directly into
 the folder you specify.  If more than one shadow is being created, FM/2
 first prompts you for the name of a folder.  This folder is then created
+the folder you specify. If more than one shadow is being created, FM/2
+first prompts you for the name of a folder. This folder is then created
 on the desktop and the shadows are placed inside that folder. You can
 move the shadows or folder elsewhere after that.
 …
 :i1 id=aboutObjects.Real Objects
 :artwork name='..\..\bitmaps\object.bmp' align=center.
+:p.
 FM/2 has the ability to create objects on your WPS desktop (or in other
 WPS folders).  To create objects, select objects in an FM/2 window, then
+WPS folders). To create objects, select objects in an FM/2 window, then
 select :hp1.Real Objects:ehp1. from a context menu or the Files pulldown
 submenu (Create Objects submenu).
 :p.
 If only one object is being created, the object is placed directly into
 the folder you specify.  If more than one object is being created, FM/2
 first prompts you for the name of a folder.  This folder is then created
+the folder you specify. If more than one object is being created, FM/2
+first prompts you for the name of a folder. This folder is then created
 on the desktop and the objects are placed inside that folder. You can
 move the objects or folder elsewhere after that.

trunk/dll/ipf/term.ipf

-              r2
+              r268
 :hp1.B2:ehp1. = Mouse button 2, usually the right button
 :p.
 :hp1.B3:ehp1. = Mouse button 3, usually the middle button.  Not all mice
 have three buttons.  OS/2 will let you redefine the buttons using the
+:hp1.B3:ehp1. = Mouse button 3, usually the middle button. Not all mice
+have three buttons. OS/2 will let you redefine the buttons using the
 WPS' Mouse object in the System Setup folder.
 :p.
 …
 :p.
 :hp1.:link reftype=hd res=97600.Pulldown menu:elink.:ehp1. = the action
 bar menu just under the title bar of a window.  If you don't know what a
+bar menu just under the title bar of a window. If you don't know what a
 title bar is, run the OS/2 tutorial.
 :p.
 :hp1.:link reftype=hd res=97600.System menu:elink.:ehp1. = the icon at
 the top left of most PM main windows.  You can close a window by
 double-clicking the System menu icon with B1.  Click once and you get a
+the top left of most PM main windows. You can close a window by
+double-clicking the System menu icon with B1. Click once and you get a
 menu (called, oddly enough, the system menu).
 :p.
 :hp1.:link reftype=hd res=97700.Conditional cascade menu:elink.:ehp1. =
 a submenu with the right-pointing link arrow contained in a button on
 the menu item.  When the button is clicked, the submenu displays
 (cascades) as with a normal submenu.  When the menu item itself is
 clicked, a default action from the submenu is activated.  You can see
 which submenu item is the default as it has a checkmark by it.  A
+the menu item. When the button is clicked, the submenu displays
+(cascades) as with a normal submenu. When the menu item itself is
+clicked, a default action from the submenu is activated. You can see
+which submenu item is the default as it has a checkmark by it. A
 conditional cascade menu generally gives you a default option for a
 command and several related commands; for instance, in an :link
 …
 cascade menu defaults to simply extracting the selected objects, but
 clicking the arrow button reveals several extract options that can be
 selected instead.  FM/2 uses conditional cascade menus to keep the menus
+selected instead. FM/2 uses conditional cascade menus to keep the menus
 organized in such a way that often used commands are immediately
 available but many more commands are still accessible.
 …
 buttons, usually with pictures on them, that you can click with your
 mouse to cause commands to be activated -- a sort of menu for
 illiterates.  The FM/2 toolbar can be turned on and off, can be changed
+illiterates. The FM/2 toolbar can be turned on and off, can be changed
 from icon to text buttons and back again, and can display text below
 the icon buttons.  Brief help appears on the title bar when the mouse
+the icon buttons. Brief help appears on the title bar when the mouse
 passes over a toolbar button.
 :p.
 :hp1.Toolbox:ehp1. = a collection of buttons in a toolbar.  FM/2 allows
+:hp1.Toolbox:ehp1. = a collection of buttons in a toolbar. FM/2 allows
 you to customize and save toolboxes which you can load into the toolbar
 as desired.
 :p.
 :hp1.:link reftype=hd res=99000.Databar:elink.:ehp1. = a window to which
 you can cause FM/2 to be "minimized," or which can be run separately, that
+you can minimize FM/2 to or which can be run separately, that
 shows occasionally updated information about your system, such as free
 drive space, threads/processes, time/date, etc.
 :p.
 :hp1.Drag and drop:ehp1. = an intuitive way of manipulating objects --
 this is more-or-less how you manipulate objects in the real world.  If
+this is more-or-less how you manipulate objects in the real world. If
 you don't know how to drag and drop, you :hp2.really:ehp2. should run
 the OS/2 Tutorial.  Drag and drop is a superior method for manipulating
+the OS/2 Tutorial. Drag and drop is a superior method for manipulating
 objects, as opposed to keyboard commands, because you choose both the
 command and the target in one operation.
 …
 of changing the text of an object, as when you change the name of an
 object on the WPS by pointing at it, holding down the ALT key and
 clicking the text with B1.  FM/2 supports direct editing of file system
+clicking the text with B1. FM/2 supports direct editing of file system
 object names as well as Subject and Longname fields in Details view.
 :p.
 …
 and press [Enter])  The default action may sometimes be modified by
 the Shift state of the keyboard (if you hold down Shift or Ctrl
 while double-clicking or pressing [Enter]).  The :link reftype=hd
+while double-clicking or pressing [Enter]). The :link reftype=hd
 res=90000.General Help:elink. topic explains default actions in detail.
 :p.
 :hp1.:link reftype=hd res=97700.Accelerator keys:elink.:ehp1. = key
 combinations that allow you to quickly give a program a command without
 going through menus or toolbars.  For example, FM/2's accelerator key to
 get help is Ctrl + F1.  Note that accelerators are case sensitive, so
+going through menus or toolbars. For example, FM/2's accelerator key to
+get help is Ctrl + F1. Note that accelerators are case sensitive, so
 that Ctrl + m isn't the same as Ctrl + M -- you'll need to hold down
 the Shift key or set Caps Lock to get the latter.
 …
 :hp1.:link reftype=hd res=97600.Drive Tree:elink.:ehp1. = the special
 window that's always open in FM/2 displaying your drives in "tree"
 format.  If subdirectories are available, there will be a "+" sign to
+format. If subdirectories are available, there will be a "+" sign to
 the left of the drive which you can click to show the subdirectories.
 Note that floppy drives (A&colon. and B&colon.) aren't checked for
 …
 :hp1.:link reftype=hd res=99400.Quicklists:elink.:ehp1. = optional
 dropdown combo boxes at the top of the FM/2 window (below the toolbar,
 if it's on) that give quick access to several often used things.  Also
+if it's on) that give quick access to several often used things. Also
 known as :hp1.user lists:ehp1..
 :p.
 …
 :p.
 :hp1.Mask:ehp1. = a filemask that can contain wildcard characters (* and
 ?) and select one or more files.  In FM/2, filemasks can usually contain
 multiple masks separated by semicolons.  See :hp1.Filter:ehp1. link
+?) and select one or more files. In FM/2, filemasks can usually contain
+multiple masks separated by semicolons. See :hp1.Filter:ehp1. link
 above for more information.
 :p.
 …
 upon which commands will act (also called the :hp1.cursored
 object:ehp1.). The current object in a container is indicated by a
 dotted outline around the object.  The current object may or may not
+dotted outline around the object. The current object may or may not
 also be highlighted. There can only be one current object in a
 container.
 …
 :hp1.:link reftype=hd res=98000.Highlighted objects:elink.:ehp1. =
 objects in a container which are indicated by a different color (usually
 darker) background.  If the current object is also highlighted, commands
 affect all highlighted objects.  Highlighted objects are sometimes
 referred to as :hp1.selected objects:ehp1..  Note that in the Drive Tree
+darker) background. If the current object is also highlighted, commands
+affect all highlighted objects. Highlighted objects are sometimes
+referred to as :hp1.selected objects:ehp1.. Note that in the Drive Tree
 there is always one highlighted object (which will also be the current
 object), but in other containers there can be many or no highlighted
 objects, and, depending on the selection type you use (see :link
 reftype=hd res=97000.Windows toggle page:elink.), the current object may
 not be a highlighted object.  Thus understanding the distinction between
+not be a highlighted object. Thus understanding the distinction between
 current and highlighted objects is important.
 :p.
 …
 :p.
 :hp1.Tree view:ehp1. = a container view similar to an inverted tree,
 with roots at the top and leaves at the bottom.  The FM/2 Drive Tree
+with roots at the top and leaves at the bottom. The FM/2 Drive Tree
 is an example of this sort of view, as is the default view of an
 OS/2 WPS Drive object.
 :p.
 :hp1.Icon view:ehp1. = a container view showing the object's name below
 the object's icon.  This is the default view for a WPS folder.
+the object's icon. This is the default view for a WPS folder.
 :p.
 :hp1.Name view:ehp1. = a container view showing the object's name beside
 …
 :p.
 :hp1.Details view:ehp1. = a container view showing full object
 information in rows.  A detail container is split into two sides with
+information in rows. A detail container is split into two sides with
 one vertical scrollbar serving both sides, and two separate horizontal
 scrollbars.  Details view shows more information on the objects within
+scrollbars. Details view shows more information on the objects within
 it than any other view; it also displays fewer objects for a given space.
 :p.
 :hp1.MLE:ehp1. = Multi Line Edit control.  This is something like a text
 editor.  They can (and do) come in all sizes.
+:hp1.MLE:ehp1. = Multi Line Edit control. This is something like a text
+editor. They can (and do) come in all sizes.
 :p.
 :hp1.Container whitespace:ehp1. = an empty part of a container (a part
 without an object on it).
+without an object on it).
 :p.
 :hp1.Monolithic application:ehp1. = FM/2 as run from the FM/2 program
 object, with the big window containing a Drive tree and Directory
 containers within it.  You can also run parts of FM/2 separately.
+containers within it. You can also run parts of FM/2 separately.
 :p.
 See also these pictures&colon.
 …
 :i1 id=aboutCURRENTOBJ.Current object &amp. selected objects
 :artwork align=left name='bitmaps\current.bmp'.
+:p.
 The current object is the one with the dotted outline; the mouse pointer
 is pointing at it.  The selected objects are those with the darker
 outline.  If the current object is also selected, commands affect all
 selected objects.  Otherwise, commands affect only the current object.
+is pointing at it. The selected objects are those with the darker
+outline. If the current object is also selected, commands affect all
+selected objects. Otherwise, commands affect only the current object.
 :h2 res=97700 name=PANEL_CASCADEMENU.Cascade menus &amp. accelerator keys
 :i1 id=aboutCASCADEMENU.Cascade menus &amp. accelerator keys
 FM/2 with a cascade menu off a pulldown menu open&colon.
+:p.
 :artwork align=left name='bitmaps\cascade.bmp'.
+:p.
 Notice the checked default action "FM/2 Window" on the Open cascade menu
 -- this is what would be executed if you clicked Open other than on the
 arrow button.  Clicking the button opens the cascade menu.  Standard
+-- this is what would be executed if you clicked Open instead of on the
+arrow button. Clicking the button opens the cascade menu. Standard
 submenus have arrows that are not buttons; clicking anywhere on one of
 thse items opens the submenu.
 …
 difference in appearance between the Miscellaneous cascade menu and the
 Select submenu.
+:p.
 :artwork align=left name='bitmaps\submenu.bmp'.
 :p.
 Finally, note that the :link reftype=hd res=93300.Files:elink. pulldown
 menu is a "ghost" for a context menu requested on a file/directory
 object.  The :link reftype=hd res=93800.Views:elink. pulldown is a
 "ghost" for a context menu requested over container whitespace.  Since
+object. The :link reftype=hd res=93800.Views:elink. pulldown is a
+"ghost" for a context menu requested over container whitespace. Since
 you can select the container and/or item while requesting a context menu
 in one smooth motion with a mouse, context menus are faster than
 …
 :i1 id=aboutCONTEXTSUBMENU.Context and sub menus
 FM/2 with a sub menu off a context menu open&colon.
+:p.
 :artwork align=left name='bitmaps\context.bmp'.
+:p.
 Here FM/2 is displaying a :link reftype=hd res=93700.context menu:elink.
 that was requested over whitespace in the Drive Tree.  This is the same
+that was requested over whitespace in the Drive Tree. This is the same
 thing you'd get if you'd clicked the :link reftype=hd
 res=93800.Views:elink. pulldown menu with the Drive Tree active
 …
 :i1 id=aboutDRAGDROP.Drag and drop
 FM/2 with a drag and drop operation underway&colon.
+:p.
 :artwork align=left name='bitmaps\dragdrop.bmp'.
+:p.
 Several files are being moved from a Directory Container to a directory
 in the Drive Tree.  Notice that in this picture several Directory
+in the Drive Tree. Notice that in this picture several Directory
 Containers are open with different views (Details, Text and Name view)
 and that mini-icons are used in the Drive Tree container.
 …
 :i1 id=aboutDIRECTEDIT.Direct editing
 :artwork align=left name='bitmaps\direct.bmp'.
+An example of direct editing.  Press and hold the ALT key while clicking
+the filename in the container with B1.  A new name can then be entered
+:p.
+An example of direct editing. Press and hold the ALT key while clicking
+the filename in the container with B1. A new name can then be entered
 into the small MLE by the object's icon (where the name usually shows),
 and another click of B1 will accept the input, while Escape will abort
 …
 :p.
 Note that the entire pathname of the object is presented for editing --
 this allows you to move the object as you rename it, if desired.  The
+this allows you to move the object as you rename it, if desired. The
 filename portion of the pathname is initially highlighted for you, so
 there's no extra work for a simple file rename.  FM/2 also tries to
 enlarge the MLE created to make things easier.  Standard OS/2 editing
+there's no extra work for a simple file rename. FM/2 also tries to
+enlarge the MLE created to make things easier. Standard OS/2 editing
 keys work as expected.

trunk/dll/ipf/tutor.ipf

-              r10
+              r268
 :i1 id=aboutTutorial.Tutorials
 :artwork name='bitmaps\tutor.bmp' align=center.
 This tutorial section is provided for the complete novice.  If you
+This tutorial section is provided for the complete novice. If you
 already know how to use OS/2's WPS in general and have used other OS/2
 PM applications, you probably don't need this tutorial.  Go forth and be
+PM applications, you probably don't need this tutorial. Go forth and be
 productive.
 :p.
 This tutorial addresses the most often used commands in FM/2 -- the only
+commands that most "file managers" provide.  There are, of course, many
+more commands available in FM/2.  However, once you have the methodology
+for these basic commands mastered, other commands are easy to use.  Of
+course, if you're totally new to OS/2 PM and WPS, you should first run
+the OS/2 tutorial.  I'm not kidding -- PM programs have similar user
+interfaces, and it all begins with the WPS, so the OS/2 tutorial is a
+must for the new OS/2 user to begin understanding :hp1.all:ehp1. his
+applications.
+commands that most "file managers" provide. There are, of course, many
+more commands available in FM/2. However, once you have the methodology
+for these basic commands mastered, other commands are easy to use.
 :p.
 Plesae pick a topic&colon.
 …
 :i1 id=aboutContextTutorial.Using Context menus
 To request a context menu, first point the mouse arrow at an object.
 Then click mouse button 2 (B2, usually the right button).  A context
+Then click mouse button 2 (B2, usually the right button). A context
 menu will then appear, if available.
 :p.
 …
 be shown if one were requested over the :hp1.current object:ehp1..
 Keyboard-only users can use the :hp1.Files:ehp1. menu instead of context
 menus.  But stop being unproductively stubborn, get a pointing device.
+menus. But stop being unproductively stubborn, get a pointing device.
 &colon.-)
 :p.
 …
 To make things a little clearer to users who haven't used OS/2's WPS
 before, take a look at the following three pictures&colon.
+:p.
 :artwork name='bitmaps\tcontxt1.bmp' align=left.
+A context menu that applies to one item.  The mouse arrow still points at
+:p.
+A context menu that applies to one item. The mouse arrow still points at
 the object on which the menu was requested -- that is the object that will
 be affected by the command selected from the menu.  You can see the dotted
+be affected by the command selected from the menu. You can see the dotted
 outline with rounded corners around the object.
+:p.
 :artwork name='bitmaps\tcontxt2.bmp' align=left.
+A context menu that applies to several items.  The mouse arrow still points
+:p.
+A context menu that applies to several items. The mouse arrow still points
 at the object on which the menu was requested -- since it is highlighted,
 all highlighted objects will be affected by the command selected from the
 menu.
+:p.
 :artwork name='bitmaps\tcontxt3.bmp' align=left.
+A context menu that applies to a container as a whole.  The menu was
+:p.
+A context menu that applies to a container as a whole. The menu was
 requested over container whitespace (an empty part of the container),
 not over any of the objects that it contains.
 …
 :h2 res=99810 name=PANEL_TRENAME.Rename tutorial
 :i1 id=aboutRenameTutorial.Rename Tutorial
+:p.
 :artwork name='..\..\bitmaps\rename.bmp' align=left.
+:p.
 Please select a method to learn about&colon.
 :p.
 …
 :h3 res=99811 name=PANEL_TRENAMEDIRECT.Rename by direct editing
 :i1 id=aboutRenameDirectTutorial.Rename by Direct Editing
+:p.
 :artwork align=left name='bitmaps\direct.bmp'.
+:p.
 To rename a file system object, hold down the :hp1.Alt:ehp1. key and
 click on the object's name with mouse button 1 (B1, usually the left
 button).  The entire pathname of the object appears in a framed control
 known as an :hp1.MLE:ehp1..  You'll initially be located at the start of
+button). The entire pathname of the object appears in a framed control
+known as an :hp1.MLE:ehp1.. You'll initially be located at the start of
 the filename with the filename (excluding the path) highlighted (ready
 to be replaced by whatever you type).  The usual editing keys work
+to be replaced by whatever you type). The usual editing keys work
 (arrows, home, end, insert, delete, etc.).
 :p.
 Type in the new name, then click the file system object again.  FM/2
+Type in the new name, then click the file system object again. FM/2
 renames the object and updates the display.
 :p.
 …
 :h3 res=99812 name=PANEL_TRENAMEDRAG.Rename by drag and drop
 :i1 id=aboutRenameDragTutorial.Rename by Drag and Drop
+:p.
 :artwork name='bitmaps\drename.bmp' align=left.
+:p.
 To invoke a rename using drag and drop, "grab" a file system object with
 the mouse by placing the mouse pointer on top of the object and
 depressing and holding mouse button 2 (B2, usually the right button).
 Still holding B2, "drag" the object to some whitespace (unoccupied space
 in the Directory Container -- a blank area) and then release B2.  The
+in the Directory Container -- a blank area) and then release B2. The
 :link reftype=hd res=91400.Rename dialog:elink. will then appear and you
 can enter a new name for the object.
 …
 :i1 id=aboutRenameKeyTutorial.Rename by Keystrokes
 Place the dotted cursor on the object you want to rename (make it the
 :hp1.current object:ehp1.).  Press Ctrl + r, the accelerator key
+:hp1.current object:ehp1.). Press Ctrl + r, the accelerator key
 for the Rename command, or pick "Rename" from the :hp1.Files menu:ehp1..
 :p.
 …
 :h2 res=99820 name=PANEL_TMOVE.Move tutorial
 :i1 id=aboutMoveTutorial.Move Tutorial
+:p.
 :artwork name='..\..\bitmaps\mover.bmp' align=left.
+:p.
 Please select a method to learn about&colon.
 :p.
 …
 :h3 res=99821 name=PANEL_TMOVEDIRECT.Move by direct editing
 :i1 id=aboutMoveDirectTutorial.Move by Direct Editing
+:p.
 :artwork align=left name='bitmaps\direct.bmp'.
+:p.
 To move a file system object, hold down the :hp1.Alt:ehp1. key and
 click on the object's name with mouse button 1 (B1, usually the left
 button).  The entire pathname of the object appears in a framed control
 known as an :hp1.MLE:ehp1..  You'll initially be located at the start of
 the pathname.  Type in the new pathname, then click the file system
 object again.  FM/2 moves the object and updates the display.
+button). The entire pathname of the object appears in a framed control
+known as an :hp1.MLE:ehp1.. You'll initially be located at the start of
+the pathname. Type in the new pathname, then click the file system
+object again. FM/2 moves the object and updates the display.
 :p.
 You can abort the move by pressing the :hp1.ESCape:ehp1. key.
 …
 :h3 res=99822 name=PANEL_TMOVEDRAG.Move by drag and drop
 :i1 id=aboutMoveDragTutorial.Move by Drag and Drop
+:p.
 :artwork name='bitmaps\tmove.bmp' align=left.
+:p.
 To move a file system object using drag and drop, "grab" a file system
 object with the mouse by placing the mouse pointer on top of the object
 and depressing and holding mouse button 2 (B2, usually the right
 button).  Still holding B2, "drag" the object to its destination (for
+button). Still holding B2, "drag" the object to its destination (for
 instance, onto a directory in the Drive Tree), and then release B2.
 :p.
 …
 :h3 res=99823 name=PANEL_TMOVEKEY.Move by keystrokes
 :i1 id=aboutMoveKeyTutorial.Move by Keystrokes
 Place the dotted cursor on the object you want to rename (make it the
 :hp1.current object:ehp1.).  Press Ctrl + m, the accelerator key
+Place the dotted cursor on the object you want to move (make it the
+:hp1.current object:ehp1.). Press Ctrl + m, the accelerator key
 for the Move command, or pick "Move" from the :hp1.Files menu:ehp1..
 :p.
 …
 :h2 res=99830 name=PANEL_TCOPY.Copy tutorial
 :i1 id=aboutCopyTutorial.Copy Tutorial
+:p.
 :artwork name='..\..\bitmaps\copier.bmp' align=left.
+:p.
 Please select a method to learn about&colon.
 :p.
 …
 :h3 res=99832 name=PANEL_TCOPYDRAG.Copy by drag and drop
 :i1 id=aboutCopyDragTutorial.Copy by Drag and Drop
+:p.
 :artwork name='bitmaps\tcopy.bmp' align=left.
+:p.
 To copy a file system object using drag and drop, press and hold the
 Ctrl key, then "grab" a file system object with the mouse by placing the
 mouse pointer on top of the object and depressing and holding mouse
 button 2 (B2, usually the right button).  Still holding B2 and Ctrl,
+button 2 (B2, usually the right button). Still holding B2 and Ctrl,
 "drag" the object to its destination (for instance, onto a directory in
 the Drive Tree), and then release B2.  During a copy drag, the dragged
+the Drive Tree), and then release B2. During a copy drag, the dragged
 object is "ghosted" rather than solid as during a move drag.
 :p.
 …
 :i1 id=aboutCopyKeyTutorial.Copy by Keystrokes
 Place the dotted cursor on the object you want to rename (make it the
 :hp1.current object:ehp1.).  Press Ctrl + c, the accelerator key
+:hp1.current object:ehp1.). Press Ctrl + c, the accelerator key
 for the Copy command, or pick "Copy" from the :hp1.Files menu:ehp1..
 :p.
 …
 :i1 id=aboutCloneTutorial.Clone Tutorial
 You :hp1.clone:ehp1. a file system object by copying it into the same
 directory that already holds it.  The :link reftype=hd res=91400.Rename
+directory that already holds it. The :link reftype=hd res=91400.Rename
 dialog:elink. will then appear because of the naming conflict, and allow
 you to specify a new name for the new, "cloned" copy of the object.
 …
 :h2 res=99840 name=PANEL_TCOMPARE.Compare tutorial
 :i1 id=aboutCompareTutorial.Compare Tutorial
+:p.
 :artwork name='..\..\bitmaps\linkdrag.bmp' align=left.
+:p.
 To compare file system objects, link-drag one object onto another.
 :p.
 A link drag is initiated by placing the mouse cursor on the object to
 be dragged, holding down the Ctrl and Shift keys, and clicking mouse
 button 2 (B2, usually the right button).  While still holding the keys
+button 2 (B2, usually the right button). While still holding the keys
 and B2, move the mouse to drag the object over the target object, then
 release B2.  During a link drag, a rubber-band line appears between the
+release B2. During a link drag, a rubber-band line appears between the
 source object and the dragged object.
 :p.
 You can change the compare program from FM/2's :link reftype=hd
 res=94600.Internal Settings notebook:elink..  An internal default is
+res=94600.Internal Settings notebook:elink.. An internal default is
 used if you leave the entry there blank.
 :h2 res=99850 name=PANEL_TVIEW.View tutorial
 :i1 id=aboutViewTutorial.View Tutorial
+:p.
 :artwork name='..\..\bitmaps\view.bmp' align=left.
+Viewing files can be as simple as double-clicking their objects.  FM/2
+:p.
+Viewing files can be as simple as double-clicking their objects. FM/2
 will attempt to do to the object what should "logically" be done, which,
 in the case of text files, archives and the like, is to view them.  If
+in the case of text files, archives and the like, is to view them. If
 you would like different actions taken, FM/2 provides :link reftype=hd
 res=90400.Associations:elink. to allow you to assign special viewer
 programs or actions to different file types.
 :p.
 You can also invoke viewing directly from the :hp1.Files:ehp1. and :link
+You can also invoke viewing directly from the :hp1.Files:ehp1., :link
 reftype=hd res=93700.context:elink. menus, or by pressing the Ctrl + v
 accelerator key.  In this case, no other default actions will be taken
 even if one might be "obvious" -- the object will simply be viewed.  If,
+accelerator key. In this case, no other default actions will be taken
+even if one might be "obvious" -- the object will simply be viewed. If,
 for example, you wanted to view an executable, this is the method you'd
 need to use (the default double-click action would be to run the
+need to use (the default double-click action would be to run an
 executable file, which is usually what you'd want to do).
 :p.
 You can change the viewing program from FM/2's :link reftype=hd
 res=94600.Internal Settings notebook:elink..  An internal default is
+res=94600.Internal Settings notebook:elink.. An internal default is
 used if you leave the entry there blank.
 :p.
 …
 :h2 res=99860 name=PANEL_TOPEN.Open tutorial
 :i1 id=aboutOpenTutorial.Open Tutorial
 "Opening" a file system object is an object-based concept.  When you
+"Opening" a file system object is an object-based concept. When you
 open a directory, you get a view of the file system objects (files and
 directories) contained within that object.  When you open an executable
 file, you cause it to execute.  When you open a data file, you usually
+directories) contained within that object. When you open an executable
+file, you cause it to execute. When you open a data file, you usually
 cause its owning application (if known) to execute with the data file
 being loaded by the application.  This is known as a "default" open.
+being loaded by the application. This is known as a "default" open.
 :p.
 But there are often several types of "open" operation that can be
 performed on an object.  For instance, you can open an object's Settings
 notebook.  FM/2 provides some variations on WPS open themes.  You can
+performed on an object. For instance, you can open an object's Settings
+notebook. FM/2 provides some variations on WPS open themes. You can
 open either a WPS folder or an FM/2 Directory Container for a directory
 object, for instance (to find out more about opening an FM/2 Directory
 Container for a directory object, see the :link reftype=hd
 res=98900.Opening a Directory Container:elink. topic).
+res=98900.Opening a Directory Container:elink. section).
 :p.
 To open an object's default WPS "view," use the F6 accelerator key, or
 press the Ctrl key while double-clicking the object.  The same type of
+press the Ctrl key while double-clicking the object. The same type of
 "open" will be done on the object that would be done if you directly
 double-clicked the object in a WPS folder object (remember, WPS folders
 …
 :p.
 For directory objects, you have the choice of WPS view type to open, as
 well -- Icon, Details or Tree view.  You pick these from the
+well -- Icon, Details or Tree view. You pick these from the
 :hp1.Open:ehp1. cascade menu on the :hp1.Files:ehp1. menu or a context
 menu requested on the object (you request a context menu on an object by
 placing the mouse pointer on the object and clicking mouse button 2,
 B2).  A command to open an FM/2 Directory Container is also on that
+B2). A command to open an FM/2 Directory Container is also on that
 cascade menu, and is the default.
 :h2 res=99870 name=PANEL_TDELETE.Delete tutorial
 :i1 id=aboutDeleteTutorial.Delete Tutorial
+:p.
 :artwork name='..\..\bitmaps\delete.bmp' align=left.
 :artwork name='..\..\bitmaps\permdel.bmp' align=left.
+:p.
 There are two styles of deleting under FM/2 -- a "regular" delete, that
 leaves the objects capable of being undeleted using OS/2's UNDELETE
 command or FM/2's Undelete Utility, and a "permanent" delete that does
 not leave the object recoverable.  "Permanent" deletions are usually
 faster than "recoverable" deletions.  You can select which type you want
+not leave the object recoverable. "Permanent" deletions are usually
+faster than "recoverable" deletions. You can select which type you want
 to be the default in FM/2's internal :link reftype=hd res=94600.Settings
 notebook:elink..
 :p.
 Note&colon.  You have to set up OS/2, using CONFIG.SYS, so that UNDELETE
 is enabled to do non-permanent deletions.  See :link reftype=launch
+Note&colon. You have to set up OS/2, using CONFIG.SYS, so that UNDELETE
+is enabled to do non-permanent deletions. See :link reftype=launch
 object='VIEW.EXE' data='CMDREF.INF UNDELETE'.UNDELETE:elink. in the OS/2
+online help.
+online help. Note&colon. FM/2 does not use the "Trashcan" that comes with
+eWorkPlace or XWorkPlace for non-permanent deletions. If you wish to use the
+"Trashcan" can drag the items directly to it from FM/2.
 :p.
 You can delete objects in many ways&colon.
 :p.
 :hp1.Drag and drop:ehp1.  Drag the object(s) to FM/2's toolbar Trashcan
 icon, or to the WPS's Shredder icon.  (You might want to pick up a
+:hp1.Drag and drop:ehp1. Drag the object(s) to FM/2's toolbar Trashcan
+icon, to the WPS's Shredder icon or to a Trashcan application. (You might want to pick up a
 replacement for the WPS Shredder like the free :hp1.mshred:ehp1. object
 written by the author of FM/2.)
 :p.
 :hp1.Files or context menu:ehp1.  Select the :hp1.Delete:ehp1. command
+:hp1.Files or context menu:ehp1. Select the :hp1.Delete:ehp1. command
 or pick the type of delete from the cascade menu.
 :p.
 :hp1.Keyboard:ehp1.  The Ctrl + d accelerator key performs a "regular"
+:hp1.Keyboard:ehp1. The Ctrl + d accelerator key performs a "regular"
 delete, Shift + Ctrl + D (also written as just "Ctrl + D" -- accelerator
 keys are case sensitive) performs a permanent delete.
 …
 :i1 id=aboutMkdirTutorial.Make Directory Tutorial
 :artwork name='..\..\bitmaps\mkdir.bmp' align=left.
+:p.
 To create a directory, use FM/2's Make Directory command.
 :p.
 You can pick this command from the :hp1.Files:ehp1. menu or a
 :hp1.context:ehp1. menu (under the Miscellaneous cascade menu).  You can
+:hp1.context:ehp1. menu (under the Miscellaneous cascade menu). You can
 click the button on FM/2's toolbar. Or you can use the Shift + Ctrl
 + "M" accelerator key.
 …
 FM/2 presents you with a small dialog box in which you can type the name
 of the directory that you want to create -- FM/2 will try to fill in the
 entry field with a guess at the first part of what you want, but you can
+entry field with a guess at the first part (parent directories) of what you want, but you can
 delete that if desired (:hp1.Shift + Home:ehp1., then touch the
 :hp1.Del:ehp1. key to do it quickly).
 :p.
 The directory created can be many levels deep.  FM/2 will create
+The directory created can be many levels deep. FM/2 will create
 intermediate subdirectories as required if they do not already exist.
 For example, if you have a directory \myapps and want to create a
 …
 :i1 id=aboutArchiveTutorial.Create Archive Tutorial
 :artwork name='..\..\bitmaps\archive.bmp' align=left.
+:p.
 To create a new archive, select the file system objects you want in the
 archive, then select :hp1.Archive:ehp1. from the :hp1.Files:ehp1. menu
 …
 the archive to be created and the type of archiving action (move or copy
 to archive, include subdirectories or not, recurse into subdirectories,
 etc.).  You can specify additional filemasks or place more obscure
+etc.). You can specify additional filemasks or place more obscure
 options on the command line to be executed.
 :p.
 …
 :i1 id=aboutExtractTutorial.Extract from Archive Tutorial
 :artwork name='..\..\bitmaps\extract.bmp' align=left.
+:p.
 To extract from an archive, first place the dotted cursor on the file
 (make it the :hp1.current object:ehp1.), then select the
 …
 :i1 id=aboutDoubleClick.Double-click actions
 Double-clicking a file system object causes a :hp1.default action:ehp1.
 to be taken.  FM/2 has its own set of defaults, but you can override
 those in many cases.  Here's a description of the FM/2 defaults and
+Double-clicking a file system object causes its :hp1.default action:ehp1.
+to be taken. FM/2 has its own set of defaults, but you can override
+those in many cases. Here's a description of the FM/2 defaults and
 how to change them&colon.
 :p.
 If the object is a directory, the Directory Container switches to look
 into that directory.  If it's a file, FM/2 first checks to see if you've
+into that directory. If it's a file, FM/2 first checks to see if you've
 assigned any :link reftype=hd res=90400.Associations:elink. that match
 the filename and signature (if applicable).  Next, FM/2 tries to view
 the file as an :link reftype=hd res=90200.archive:elink..  If it's not
+the filename and signature (if applicable). Next, FM/2 tries to view
+the file as an :link reftype=hd res=90200.archive:elink.. If it's not
 an archive, FM/2 checks to see if the file's an executable and runs it
 if so.  Then INI and HLP files are checked by extensions and viewed as
 such.  If all else fails, FM/2 views the file using the configured or
+if it is. Then INI and HLP files are checked by extensions and viewed as
+such. If all else fails, FM/2 views the file using the configured or
 internal viewer.
 :p.
 …
 WPS associations, runs executables, opens folders in their default view,
 or opens the Settings notebook for the object -- whatever
 double-clicking on the object in the WPS would do), and holding down the
 Shift key while double-clicking causes the file to be directly Viewed,
 bypassing the other steps listed above (for file objects; directory
 objects cause another FM/2 window to be opened).
+double-clicking on the object in the WPS would do). Holding down the
+Shift key while double-clicking causes file objects to be directly Viewed,
+bypassing the steps listed above for file objects (for directory
+objects this causes a new FM/2 container to be opened).
 :p.
 If you'd like more detail, go to the :link reftype=hd
 …
 :p.
 You can change what FM/2 does on a double-click of a file object by
 using FM/2's :link reftype=hd res=90400.Associations:elink..  This is
+using FM/2's :link reftype=hd res=90400.Associations:elink.. This is
 a very powerful tool for customizing FM/2's behavior, so when you're
 ready, be sure to look it over.

trunk/dll/ipf/util.ipf

-              r10
+              r268
 FM/2 offers several utilities to make your life a little easier&colon.
 :p.
-:link reftype=hd res=100045.Remap drives:elink.
-.br
 :link reftype=hd res=90100.Collector:elink.
 .br
 …
 :hp2.System Setup:ehp2. folder, and command line windows from this menu.
-:h2 res=100045 name=PANEL_REMAP.Remap drives
-:i1 id=aboutRemap.Remap drives
-To remap (attach) a remote server to a local drive letter, enter the
-UNC server name in the entry field at the top center of this dialog,
-then select the drive letter from the left (attach) listbox to which to
-attach the server.  Finally, click the :hp1.Attach:ehp1. button.
-:p.
-To detach a local drive letter from a remote server, select the
-drive letter from the right (detach) listbox, then click the
-:hp1.Detach:ehp1. button.
-:p.
-When you're through remapping drives, click :hp1.Done:ehp1..
-:p.
-According to IBM LAN Server documentation, a UNC name consists of a
-double backslash, the name of the server, another backslash, and the
-name of the resource&colon.  \\servername\netname
-:p.
-Note that FM/2 saves the UNC names you enter in the listbox below the
-entry field.  You can recall these names later by clicking on them.
-The :hp1.Delete:ehp1. button deletes the currently selected name from
-the listbox, and the :hp1.Clear:ehp1. button removes all names from
-the listbox.  Names are added automatically.  Up to 200 names can be
-stored in this manner (kept on disk between sessions in a file named
-RESOURCE.DAT).
 .im collect.ipf
 .im comp.ipf
+:h2 res=92500 name=PANEL_UNDELETE.Undelete Files
+:i1 id=aboutUndelete.Undelete Files
+:artwork name='..\..\bitmaps\undelete.bmp' align=center.
+This leads to a dialog that interfaces with UNDELETE.COM to allow you to
+undelete files.  The drive that will be operated on is determined by the
+highlighted object in the directory tree.  This dialog filters out files
+that already exist on the disk.
+:p.
+The :hp1.Mask:ehp1. entry field lets you set a mask (which can include
+a directory path).  You can switch drives using the dropdown listbox.
+A :hp1.Subdirs:ehp1. button lets you choose whether to show files that
+can be undeleted in subdirectories as well.
+:p.
+You can always go directly to UNDELETE.COM if you have the need for more
+control.  This is provided only for convenience.
+.im inis.ipf
 :h2 res=92600 name=PANEL_KILLPROC.Kill Processes
 :i1 id=aboutKillProc.Kill Processes
 :artwork name='..\..\bitmaps\killproc.bmp' align=center.
+:p.
 This leads to a dialog that allows you to kill most renegade processes.
 If you run into a window that just won't close, or one that hides itself
 but doesn't quite go away, this may let you kill the hung process.
 :p.
 Obviously you'll want to exercise some care here.  FM/2 will remove its
+Obviously you'll want to exercise some care here. FM/2 will remove its
 own PID (Process ID) from the list, but if you ran it from a command
 line you could still kill FM/2 by killing its parent.  You can also kill
 off the WPS (PMSHELL.EXE), but it should restart itself.  Some kernal
+line you could still kill FM/2 by killing its parent. You can also kill
+off the WPS (PMSHELL.EXE), but it should restart itself. Some kernal
 processes show up but can't be killed.
 :p.
 A checkbox allows you to set the Process Killer to use the undocumented
 DosQProcStat API instead of parsing PSTAT.EXE's output.  While this
+DosQProcStat API instead of parsing PSTAT.EXE's output. While this
 removes the requirement of having an English version of PSTAT.EXE, you
 should be aware that the DosQProcStat can be changed by IBM without
 notice, possibly causing the Process Killer to fail and/or trap.
 :h2 res=92700 name=PANEL_INSTANT.Instant Batch File
+:h2 res=92700 name=PANEL_INSTANT.Instant CMD File
 :i1 id=aboutInstant.Instant Batch File
 :artwork name='..\..\bitmaps\instant.bmp' align=center.
+This leads to a dialog that lets you quickly hack together a batch
+(command) file and run it (the currently highlighted tree directory will
+be its default directory).  The command file isn't saved; think of it as
+:p.
+This leads to a dialog that lets you quickly hack together a command
+(batch) file and run it (the currently highlighted tree directory will
+be its default directory). The command file isn't saved; think of it as
 an "extended command line" which allows you to enter more than one line
 at a time (for instance, when several tests must be made).
-:h2 res=92800 name=PANEL_COMMANDLINE.Command Line
-:i1 id=aboutCommandLine.Command Line
-:artwork name='..\..\bitmaps\cmdline.bmp' align=center.
-This brings up a windowed OS/2 command line.  F9 is the accelerator key
-for this command.
-:p.
-There are also commands to bring up a windowed DOS command line and
-a Win-OS/2 full screen session.
-.im inis.ipf
 :h2 res=94800 name=PANEL_VIEWINFS.View Bookshelf
 …
 FM/2 presents a listbox containing all the .INF files found in the
 directories listed in your BOOKSHELF environment variable (see
 SET BOOKSHELF= in CONFIG.SYS).  You select the .INF file(s) you want
+SET BOOKSHELF= in CONFIG.SYS). You select the .INF file(s) you want
 to view, then click the :hp1.View:ehp1. button.
 :p.
 If you selected more than one .INF file, FM/2 calls VIEW.EXE in such
 a way that all the files are presented at once (a single contents
 page appears listing the contents of all the .INF files).  Warning:
+page appears listing the contents of all the .INF files). Warning:
 Don't select more than one filename with the same title (left column
 of listbox) -- View.exe will choke if you do, and be unable to read any
 of the files.
+of listbox) -- IBM's View.exe will choke if you do, and be unable to read any
+of the files. However Newview works fine.
 :p.
 You can enter text into the entry field below the listbox, and FM/2 will
 try to find the first listbox entry with matching text as you go.  If
+try to find the first listbox entry with matching text as you go. If
 you click :hp1.Select:ehp1. FM/2 will highlight all matching entries
 (hint: empty the entry field and click Select to unhighlight
 everything).  If you click :hp1.Filter:ehp1. FM/2 will remove all but
+everything). If you click :hp1.Filter:ehp1. FM/2 will remove all but
 highlighted items from the listbox (:hp1.Rescan:ehp1. will refill the
 listbox).
 …
 The :hp1.AddDirs:ehp1. button will copy the contents of the entry field
 and add it to the directories listed in the BOOKSHELF environment variable.
 It should be in the same format as the HELP environment variable uses,
 fully qualified directory names separated by semi-colons.  The next time you
+It should be in the same format that the BOOKSHELF environment variable uses,
+fully qualified directory names separated by semi-colons. The next time you
 use the Bookshelf Viewer, FM/2 will remember this input and use it. This
 is an internal addition; your CONFIG.SYS and environment are not
 …
 :p.
 When you're done with the dialog, press [ESCape] or click
 :hp1.Cancel:ehp1..  Any open .INF files remain open until you close them
+:hp1.Cancel:ehp1.. Any open .INF files remain open until you close them
 (hint&colon. F3 will close an .INF file).
 :p.
 Note&colon.  this dialog is shared by the :hp2.:link reftype=hd
+Note&colon. this dialog is shared by the :hp2.:link reftype=hd
 res=94850.View Helpfiles:elink.:ehp2. and :hp2.View Bookshelf:ehp2.
 commands. If you click on either while this dialog is up, the dialog is
 simply brought to the foreground.  Close it if you want to switch
+simply brought to the foreground. Close it if you want to switch
 function. (This doesn't apply if you started this from the Bookshelf
 Viewer object in the FM/2 WPS folder.)
 …
 FM/2 presents a listbox containing all the .HLP files found in the
 directories listed in your HELP environment variable (see SET HELP= in
 CONFIG.SYS).  You select the .HLP file you want to view, then click
+CONFIG.SYS). You select the .HLP file you want to view, then click
 the :hp1.View:ehp1. button.
 :p.
 …
 The :hp1.AddDirs:ehp1. button will copy the contents of the entry field
 and add it to the directories listed in the HELP environment variable.
 It should be in the same format as the HELP environment variable uses,
 fully qualified directory names separated by semi-colons.  The next time
 you use the Bookshelf Viewer, FM/2 will remember this input and use it.
+It should be in the same format that the HELP environment variable uses,
+fully qualified directory names separated by semi-colons. The next time
+you use the HELP Viewer, FM/2 will remember this input and use it.
 This is an internal addition; your CONFIG.SYS and environment are not
 modified.
 :p.
 When you're done with the dialog, press [ESCape] or click
 :hp1.Cancel:ehp1..  Any open .HLP file will remain open until you close
+:hp1.Cancel:ehp1.. Any open .HLP file will remain open until you close
 it.
 :p.
 Note&colon.  this dialog is shared by the :hp2.:link reftype=hd
+Note&colon. this dialog is shared by the :hp2.:link reftype=hd
 res=94800.View Bookshelf:elink.:ehp2. and :hp2.View Helpfiles:ehp2.
 commands. If you click on either while this dialog is up, the dialog is
 simply brought to the foreground.  Close it if you want to switch
+simply brought to the foreground. Close it if you want to switch
 function. (This doesn't apply if you started this from the Helpfile
 Viewer object in the FM/2 WPS folder.)
+Viewer object in the FM/2 WPS folder or from the command line.)
+:h2 res=92800 name=PANEL_COMMANDLINE.Command Lines
+:i1 id=aboutCommandLine.Command Lines
+:artwork name='..\..\bitmaps\cmdline.bmp' align=center.
+:p.
+There are three different command line choices. The first
+brings up a windowed OS/2 command line. F9 is the accelerator key
+for this command. The last two bring up a windowed DOS command line and
+a Win-OS/2 full screen session respectively but only if you have installed DOS and
+Win-OS/2 support.

trunk/dll/ipf/walkem.ipf

-              r10
+              r268
 :artwork name='..\..\bitmaps\walk.bmp' align=center.
+:p.
 This dialog lets you pick a directory by "walking" through the
 directory structure of your drives.  It also lets you save and
+directory structure of your drives. It also lets you save and
 recall user-defined directories.
 :p.
 On the left is a listbox containing all your drive letters.  If you
+On the left is a listbox containing all your drive letters. If you
 select a drive, the directories on that drive fill the center listbox.
 :p.
 …
 :p.
 The listbox on the right of the window (:hp1.User List:ehp1.) contains
 only directories that you add to it.  To add a directory, click
+only directories that you add to it. To add a directory, click
 :hp1.Add:ehp1. when the desired directory name is displayed in the
 entry field at the bottom of the window.  To delete a directory,
 highlight it and click :hp1.Delete:ehp1..  To switch to one of these
+entry field at the bottom of the window. To delete a directory,
+highlight it and click :hp1.Delete:ehp1.. To switch to one of these
 user-defined directories, highlight it and click :hp1.Okay:ehp1. or
 double-click the directory.  You can add up to 100 directories.
+double-click the directory. You can add up to 100 directories.
 :p.
 You can also select directories from the Recent directories drop-down
 list at the top right of the window.  FM/2 adds to this list
 automatically as you traverse your drives.  Just drop down the list
+list at the top right of the window. FM/2 adds to this list
+automatically as you traverse your drives. Just drop down the list
 and click the directory of choice.
 :p.
 When the desired directory is displayed in the bottom entry field of
 the dialog, click :hp1.Okay:ehp1. to exit.  Click :hp1.Cancel:ehp1. to
+the dialog, click :hp1.Okay:ehp1. to exit. Click :hp1.Cancel:ehp1. to
 exit without selecting a directory.

trunk/dll/ipf/window.ipf

-              r10
+              r268
 :i1 id=aboutWindowMenu.Windows Menu
 :artwork name='..\..\bitmaps\window.bmp' align=center.
+The Windows submenu lets you control FM/2's child windows.  In addition,
+:p.
+The Windows submenu lets you control FM/2's child windows. In addition,
 you can select child windows to give the focus from the bottom of the
 menu.  Following is a discussion of the "permanent" commands on the menu.
+menu. Following is a discussion of the "permanent" commands on the menu.
 :p.
 :hp1.Tile&colon.:ehp1.
 …
 :p.
 Brings up a dialog that lets you minimize, restore or close selected
 child windows.  You can also chord the mouse on a blank portion of the
+child windows. You can also chord the mouse on a blank portion of the
 main client window to call up this dialog.
 :p.
 …
 :i1 id=aboutWindowDlg.Windows List
 :artwork name='..\..\bitmaps\window.bmp' align=center.
+:p.
 This dialog lets you minimize, restore or close selected child windows.
 It's accessed via toolbar button, :link reftype=hd

Context Navigation

Legend:

Download in other formats: