source: trunk/README@ 536

Last change on this file since 536 was 398, checked in by root, 19 years ago

Document stderr logging

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 15.1 KB
Line 
1 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
2 ³ F(ile) M(anager)/2 is free software from Mark Kimes ³
3 ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄŽ
4 ³ READ.ME file -- read before installing ³
5 ³ See end of document for contact info and license details ³
6 ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
7
8
9File Manager/2 (FM/2) is a free OS/2 3.0 (Warp)+ PM 32-bit
10file/directory/archive maintenance utility (a sort of super-Drives
11object, something midway between the Drives objects and a more
12traditional file manager) with plenty of bells, whistles and utilities,
13drag and drop, context menus, toolbars, bubble help and accelerator
14keys. If you know how to use OS/2, you already know how to use most of
15FM/2. You can easily glean the rest from the extensive online help,
16including tutorials.
17
18This document explains how to install FM/2, including upgrading from
19previous versions. It explains command line syntaxes (parameters in a
20program object) and how to get the program(s) running. The online help
21tells you how to actually use FM/2. I'll try to keep this brief.
22
23 This program is free software; you can redistribute it and/or modify
24 it under the terms of the GNU General Public License as published by
25 the Free Software Foundation; either version 2 of the License, or
26 (at your option) any later version.
27
28 This program is distributed in the hope that it will be useful,
29 but WITHOUT ANY WARRANTY; without even the implied warranty of
30 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
31 GNU General Public License for more details.
32
33 You should have received a copy of the GNU General Public License
34 along with this program; if not, write to the Free Software
35 Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
36
37
38FM/2 3.x installation instructions:
39==================================
40
41First-time installation:
42-----------------------
43 1. Unpack the FM2*.ZIP archive in a private directory (for example,
44 C:\FM2). UNZIP.EXE works nicely to unpack the file.
45
46 2. Run the provided INSTALL.CMD in that directory to build a folder
47 and program objects. INSTALL /? will give you simple command line
48 help on a couple of options.
49
50 3. Run it -- double-click the "FM/2" or "FM/2 Lite" object in the
51 File Manager/2 folder. Play, browse, have fun. Full help is
52 available from within the program, and it helps you with quick
53 initial setup the first time it's run.
54
55Upgrading existing versions of FM/2:
56-----------------------------------
57 If upgrading, just unpack the files in the FM/2 directory. Be
58 sure to overwrite old files. You might want to skip ARCHIVER.BB2
59 if you've customized it -- other customizations are automatically
60 preserved. You might then want to rerun INSTALL or just delete
61 *.TMP and *.ICO to clean up some stuff that you won't need when
62 upgrading. Note: don't attempt to unpack using FM/2 into the
63 directory in which FM/2 is already running -- OS/2 locks in-use
64 files and the upgrade won't be completed properly; not all files
65 will be unpacked.
66
67Moving FM/2:
68-----------
69 Rerun INSTALL.CMD if you move the FM/2 directory. This will make
70 sure all the objects in the folders and *.CMD files point to the
71 right place. Compare to other products, where'd you'd have to
72 reinstall if you could only figure out how to completely uninstall
73 the existing version...
74
75Uninstalling FM/2:
76-----------------
77 If you later decide to remove FM/2, run UNINSTAL.CMD in the FM/2
78 directory and follow simple directions. Both installation and
79 deinstallation are no-brainers. UNINSTAL will help you quickly
80 and easily remove all traces of FM/2 from your system, if you
81 don't like it for some reason. All programs should be so nice.
82
83
84First-time notes:
85================
86
87Starting FM/2 -- how it works, customizing parameters:
88-----------------------------------------------------
89If you start File Manager/2 (filename FM3.EXE) with no parameters, it
90opens the Drive Tree window but no directory windows (unless the "Save
91state of dir windows" toggle is checked -- see online help).
92
93File Manager/2 optionally accepts names of directories in the parameters
94field of its program object; it'll open a directory window for each one.
95Hint: If you often do different specific things with FM/2, you might
96set up a WPS object customized to start up ideally for each activity.
97For example, if you wanted to maintain your BBS areas, you might have
98one object with parameters like: "D:\BBSDIR D:\BBSDIR\MAILIN
99D:\BBSDIR\MAILOUT", and if you also like to use FM/2 to set icons on
100files, you might have another object with parameters like: "E:\MYICONS
101D:\NEWFILES". The State quicklist can also be used for this within FM/2
102itself -- see online help.
103
104You can exclude drives in the parameters by prefacing the drive letter
105with "/", and there can be more than one drive letter behind the "/"
106(i.e. "/BH" to exclude both drives B: and H:). Hint: Many people like
107to use /B to exclude "phantom" drive B: if they have a single-floppy
108system. Similarly, you can cause drives NOT to be prescanned by the
109Drive Tree by prefacing the drive letter with ";", drives NOT to load
110icons for objects by prefacing the drive letter with ",", drives NOT to
111load subjects for objects by prefacing the drive letter with "`" and
112drives NOT to load longnames for objects by prefacing the drive letter
113with "'". This can be handy if you have a very slow drive like a CD-ROM
114or Zip drive. FM/2 Lite recognizes these switches, too. See also the
115Drive Flags dialog in FM/2.
116
117If you place the plus sign "+" (alone, separated from anything else by
118spaces) in the parameters, FM/2 will log, to FM2.LOG, delete, rename,
119move and copy operations that are performed by drag-and-drop or with the
120menus. FM/2 Lite recognizes this switch, too.
121
122The parameter "-" (alone, separated from anything else by spaces) causes
123FM/2 to ignore, not load or save, the previous state of directory
124windows (see the "Save state of dir windows" toggle under Config
125Menu->Toggles in the online help) for that invocation.
126
127You can specify the name of an alternate INI file with "-<inifilename>"
128-- for example, "-C:\FM2\MYINI.INI".
129
130You can also specify the INI file location with the environment variable
131FM2INI -- for example: SET FM2INI=C:\FM2\MYINI.INI.
132
133How to get started using FM/2:
134-----------------------------
135Please read the following sections in the online help when you start
136FM/2 for the first time: "How to use FM/2's Help," "Terminology" and
137"General Help," then "Hints." A peek at the labelled "Window Layouts"
138pictures would probably be a good idea, too. The rest you can browse as
139you get time/feel the need; for instance, if you want to know what a
140toggle does, read the help under Settings notebook for that page (each
141Settings notebook page has its own Help button).
142
143If you prefer hardcopy help, print this file, run FM/2, press Ctrl + F1,
144click the "Print" button at the bottom of the help window that appears
145and then print both the "Contents" and "All sections" (keep an eye on
146the printer, after page 100 of "All sections" as the Help Manager will
147begin printing its own help then -- you may want to abort printing at
148that point). Advanced and/or curious users may also want to print
149FM3TOOLS.DAT and ARCHIVER.BB2. Be sure you have plenty of paper and ink
150handy -- the package is well documented. You'll probably also want a
151three-ring binder and hole punch to get it bound, as staples aren't
152going through that puppy. You can, of course, print only the sections
153that are of particular interest to you.
154
155You may want to either move ARCHIVER.BB2 (the data file containing
156information about archiver programs and archive files) to a directory in
157your PATH= statement or erase this one if you've customized an old one.
158FM/2 can still find, use and maintain ARCHIVER.BB2 on the PATH; it
159doesn't have to be in FM/2's directory (this allows it to be used by
160other programs as well, like XGroup, XBBS/2, LA, AV, ZTreeBold, etc.).
161Remember, FM/2 works best with OS/2, not DOS, archivers.
162
163Additional documentation:
164------------------------
165 FM3.HLP: FM/2's online help file.
166
167Look in the FM/2 Docs subfolder of the File Manager/2 folder for easy
168access to all documentation.
169
170
171Bonus programs:
172==============
173
174You'll note the extra objects that the Install program creates in the
175FM/2 Tools subfolder of the File Manager/2 folder. FM/2 is modular, so
176that you can get directly to some of its components without running the
177entire ball of wax. This may allow you to enhance the behavior of some
178of your other applications in the WPS tradition. You don't _have_ to
179keep these around, of course -- FM/2 itself contains all their
180functionality.
181
182 Archive Viewer/2: Intended for drag-and-drop operation (or WPS
183 association) with WPS objects or other
184 applications. Drag an archive onto it, drop it,
185 get an archive listing box. FM/2's installation
186 program sets up some associations between archive
187 files and this program by file extension (run
188 INSTALL with "NOASSOC" as an argument if you don't
189 want them). AV/2 will try to display whatever
190 you give it as sensibly as it can. Filename AV2.EXE.
191
192 EA Viewer: Drag a file system object onto it and it'll show
193 you the object's extended attributes. Filename
194 EAS.EXE.
195
196 INI Viewer: Drag an .INI file onto it and it'll show you its
197 contents. Filename INI.EXE.
198
199 Bookshelf Viewer: Shows all .INF files in a listbox and lets you
200 pick the one(s) you want to view. If you give any
201 command line argument, the .HLP files on the HELP
202 path will be shown instead (the Helpfile Viewer
203 object calls VIEWINFS.EXE with "dummy" for an
204 argument, for example). Filename VIEWINFS.EXE.
205
206 Process Killer: Lets you kill off renegade processes. An English
207 version of PSTAT.EXE must be on your PATH.
208 Filename KILLPROC.EXE.
209
210 Undeleter: Lets you undelete files (via interface with
211 UNDELETE.COM). Drag a file system object onto it
212 and it'll let you undelete files for that drive.
213 Filename UNDEL.EXE.
214
215 Visual Tree: Opens a Drive Tree window (like the WPS Drives
216 object with more horsepower). Filename VTREE.EXE.
217
218 Visual Directory: Opens a Directory Container window; drag a file
219 system object onto it and this will open its
220 directory (like a WPS directory Folder with more
221 horsepower). Filename VDIR.EXE.
222
223 Collector: Opens a Collector window. Filename VCOLLECT.EXE.
224 Two other objects, "See all files" and "Seek and
225 scan" are created which call up the Collector and
226 go directly to dialogs for the appropriate
227 purpose.
228
229 Global Viewer: Opens a global view of a drive or drives. Filename
230 GLOBAL.EXE.
231
232 Databar: Opens a databar showing some system information.
233 Filename DATABAR.EXE.
234
235 DirSize: Shows where drive usage is concentrated. Filename
236 DIRSIZE.EXE.
237
238 FM/2 Lite: A simplified interface for "dummies." Filename
239 FM4.EXE.
240
241FM/2's install creates FM2.CMD, AV2.CMD, VDIR.CMD, VTREE.CMD,
242VCOLLECT.CMD, UNDEL.CMD, KILLPROC.CMD, INI.CMD, EAS.CMD, DIRSIZE.CMD,
243VIEWINFS.CMD and VIEWHELP.CMD files for you in a directory "utils" off
244the install directory. You should add this directory to your PATH=
245statement in CONFIG.SYS (type HELP PATH at a command line for more
246info). If you prefer, FM/2's INSTALL builds a SETENV.CMD in the FM/2
247directory which you can call to set the PATH for FM/2 in any given
248session without modifying CONFIG.SYS.
249
250
251Troubleshooting:
252===============
253
254If FM/2 won't run, the probable culprit is CONFIG.SYS. Your LIBPATH
255statement should contain a ".\" entry. If yours doesn't, add it. It's
256standard for an OS/2 installation, but some buggy install programs knock
257it out because they translate entries to their full pathname before
258rewriting (so ".\" gets translated to whatever the current directory is
259for the buggy install program). What this ".\" entry does is allow a
260program to find and use .DLL files in the program's current directory --
261obviously something you want programs to be able to do, otherwise you'd
262have to put every application's .DLLs into directories already on the
263LIBPATH, or add the directories of all applications to the LIBPATH, a
264rather huge pain in the, uh, neck.
265
266If things in FM/2 are suddenly acting strange after an upgrade, first
267make _sure_ you unpacked _all_ the files and overwrote the old ones,
268then ran INSTALL.CMD to update your WPS objects.
269
270If the "FM/2 Online Help" object in the "FM/2 Docs" subfolder won't work
271properly, you've got a version of VIEW.EXE that won't directly display
272help (.HLP) files. Use SEEHELP.EXE from the FM/2 Utilities package to
273get around this problem (or upgrade your version of OS/2).
274
275Don't drag files over Netscape -- it will lock up if files (not WPS
276objects; there's a subtle difference) are dragged over it.
277
278If you get a popup dialog that needs to be reported to the maintainer, you
279can either take a screen shot or you can capture the information from STDERR
280with
281
282 FM3 2>STDERR.LOG
283
284This technique works for all the FM/2, FM/2 Lite and all the standalone
285applets.
286
287If you are having trouble with Drag and Drop operations, try the + command
288line switch described above. The content of FM2.LOG may be helpful.
289
290
291Known problems/shortcomings:
292===========================
293
294 - FM/2 does not properly report sizes of some files with long name
295 resident on Win95/NT drives.
296
297 - File List Container fails to fill after drive change SYS0039 error.
298
299 - Tree switching on Focus/Directory Change appears to be slower than
300 expected.
301
302 - Access to LS120 and FAT32 drives slower than expected
303
304 - Icon display in Directory Container does not always match WPS icons
305
306 - Spurious WPS Objects Handles created during some operations
307
308
309About FM/2:
310==========
311
312FM/2 was originally written by:
313
314 Mark Kimes
315 <hectorplasmic@worldnet.att.net>
316
317He has kindly allowed me to take over maintenance and support of FM/2 and to
318release the program under the GNU GPL license. I'm sure he would appreciate
319a Thank You note for his generosity.
320
321Support:
322=======
323
324There is a Yahoo group devoted to fm/2 at:
325
326 <http://groups.yahoo.com/group/fm2user/>
327
328You will find lots of friendly folks ready to help.
329
330You can reach me directly at:
331
332 Steven H. Levine
333 steve53@earthlink.net
334
335I also monitor the comp.os.os2.apps newsgroup and several others in the
336comp.os.os2.* hierarchy.
337
338Thanks and enjoy.
339
340$Id: README 398 2006-07-28 23:19:45Z root $
Note: See TracBrowser for help on using the repository browser.