source: trunk/README@ 1330

Last change on this file since 1330 was 1278, checked in by Gregg Young, 17 years ago

Update .def files etc for 3.14 release

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 24.0 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 ³
6 ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
7
8FM/2 3.14: This release updates many of the icons and bitmaps
9used in FM/2. In addition, more updates have been made to the
10toolbars to activate the new toolbars follow the instruction for
11using CFGMGR in the section about version 3.13. One other change
12may require some user intervention. Inadvertently the expected
13name of the filters data file was change in version 3.12 from
14filters.dat to filter.dat. We have corrected this, however, this
15means your filters may be spread across 2 different files or may
16seem to have disappeared. If they have disappeared go to the FM/2
17directory and rename the file filter.dat to filters.dat. This should
18restore your saved filters. If you find you have both filter.dat and
19filters.dat use a text editor to add the contents of filter.dat
20to filters.dat.
21
22This release also contains some menu changes with unformatted drives
23using the "drives" context menu, the elimination of more than one
24default on some submenus and menu items such as "format" being
25disabled for network drives and enabled for removables. Some of the
26changes should make FM/2 more responsive (Let us know if you notice
27a difference). We have also included some bug fixes.
28
29FM/2 3.13: Many of the changes in this release are related to
30the toolbars. A new feature is that the current toolbar, along
31with the current Target directory, are now saved and restored
32with states. Toolbar code and documentation has been improved, new
33toolbar button bitmaps have been added and bugs have been fixed.
34
35The installation of FM/2 will not replace existing user
36customization files like the toolbar files. So, if this is not
37your first installation of FM/2, some of these improvements will
38not be available because of the old, pre v3.13 toolbar files. It
39is therefore recommended that you run the following:
40
41 CFGMGR /INSTALL /DEFAULTS /TOOLBARSONLY /UNATTENDED
42
43CFGMGR is a REXX program located in the FM/2 installation directory.
44If run as given above it will copy your existing toolbar files into
45a "User_config_backup" subdirectory and then install FM/2 default
46toolbar files. If you have done some customizations of FM/2 toolbars
47you can use a text editor and/or file comparison utility like GFC
48to "merge" your changes, now found in the backup subdirectory,
49with the default files now found in the FM/2 directory. If you want
50more control over the operation of CFGMGR, then leave off the
51/UNATTENDED parameter. Without the /UNATTENDED parameter CFGMGR
52will ask your permission before replacing each file.
53
54The delete = move to trash can is off by default (turn it on on the
55General settings notebook page). FM/2 now checks for adequate disk
56space to avoid data loss.
57
58We also fixed some additional bugs and provide some performance
59enhancements. If you have had trouble with "broken pipe" errors
60copying to a netdrives samba drive let me know if it now works
61better. I have built in some retries for this error but can't test
62it since I don't see the problem. Also please report back to us anytime
63you see the Debug error report to author box with as much detail about
64what you were doing as possible. Thanks
65
66FM/2 3.12 Fixes a bug introduced in 3.11 (trap when viewing
67multiple files from an archive at the same time). It also adds
68Open Default, Open Settings and via an accel key ctrl + l Open
69Multimedia (using FM2play.exe) to the archive viewer. FM/2 now
70uses the system TMP/TEMP directory for it temporary files and
71cleans up after a crash on the next restart. FM/2 creates a
72subdirectory of the pattern $FM2*.*. The settings notebook can
73now be closed using esc, F3 or enter; the last 2 save any
74changes that have been made. You can now select which environment
75variables to show when using show the environment in the drive
76tree. Just add or remove from the list on the "Tree" page of
77the notebook. It defaults initially to the current list. You can
78now save/append either a full pathname or just a filename or a
79list of either to the clipboard. We have changed the wording
80in the menus to make this easier to find. We fixed a few other
81minor issues see the history for more details.
82
83FM/2 3.11 adds the option of having delete move the objects
84to the Xworkplace trashcan. Undelete will open the trashcan
85so you can restore deleted files. The only short coming is you
86will need to rescan in order to see the restored file.
87We also added a reserved state which allows you to return
88FM/2 to the state it was in on start up (the shut down state).
89We have improved the filtering of file names that contain
90multiple periods and fixed FM/2's failure to always follow
91the details settings from the setup notebook. The primary
92task achieved for this release was the addition of fortify
93support which allowed us to fix a handful of memory usage
94related bugs. We fixed a few other minor issues see the
95history for more details.
96
97Fm/2 3.10 adds the ability to set the command line length
98to correspond to the command shell you are using. We have
99moved some menu items to submenus to reduce menu clutter
100while adding "unhide" to reveal previously hidden items and
101adding a settings notebook submenu to allow selection of the
102page you wish to visit. We have updated the look of several
103dialogs and containers including adding the ability to remember
104size location and presentation parameters. We have reworked
105the save state on close so it will save the different states
106of multiple directory containers and in greater detail. This
107state can also be restored at anytime during a session by
108selecting it from the "States" drop down. We have provided better
109progress indicators to update the progress of long operations.
110We now provide both the SYM & MAP files in a separate warpin
111package. This will allow interested individuals the tools needed
112to assist with analysing any problem that may occur. This
113package is not needed to run FM/2. As always this update
114provides some performance enhancements and defect fixes.
115
116FM/2 3.09 adds "mailto:" so you can configure the ability to
117double click an email address in the new viewer and have it
118open a new email using that address. The viewer page in the
119settings notebook was split into 2 pages to facilitate the
120change. Additionally, We fixed some defects and enhanced
121performance in some areas such as commandline quoting.
122
123FM/2 3.08 has had changes to its file filtering logic.
124It now searches for the last extension if a mask like *.zip
125is used. This change was made to over come the problem with
126associations failing on files with multiple ".". You can
127also seach for a complete string within the file names by
128using the pattern *stuff* (stuff can't contain an * or ?).
129If "stuff" contains an * or ? the old method of searching
130(character by character)is used.Large (>4GiB) file support
131has been added.
132
133FM/2 3.07 had changes made to its ini file structure.
134These changes mean that the ini file is not backward
135compatible. Please backup you FM3.INI file before installing
136so you can revert to an earlier version without losing some
137of your customizations. Please note you need to leave a copy
138of the fm3.ini file in the install directory in order to keep your
139customizations in 3.07. The temp file fm3.!!! will not update
140the new ini as it is only used when fm2 is running.
141
142File Manager/2 (FM/2) starting with version 3.6 is being
143built with OpenWatcom. Changing compilers can introduce
144unexpected problem so you may want to backup your current
145install, or at minimum have a working copy of the FM/2
146version 3.5.9 warpin available for reinstall if problems arise.
147To backup your current install simple zip up your install
148directory with its subdirectories or copy them to a different
149location.To restore simply copy the old FM/2 back to the
150its original location. Remember you can't use the new FM/2
151to do this since if it is running some files will be locked
152and won't be replaced. If you didn't backup and need to go
153back just install the 3.5.9 warpin package over the new
154install. It will warn you that the install is newer but just
155tell it to install anyway. The warpin install process is
156designed to save all your customizations. Don't delete the
157new install if you don't have a backup since this will result
158in the loss of any custom changes you have made. If you need
159to delete it to get the reinstall to work. Backup up the new
160install and then copy the *.bmp, *.tls, *.dat, *.cmd & *.ini
161files back to the install directory after the reinstall.
162Don't copy the *.str files as they are version specific.
163If you have problems be sure to report it (See Support
164at the end of this file).
165
166File Manager/2 (FM/2) is a free OS/2(Warp)/eCS Presentation
167Manager 32-bit file/directory/archive maintenance utility
168(a sort of super-Drives object, something midway between the
169Drives objects and a more traditional file manager) with plenty
170of bells, whistles and utilities, drag and drop, context menus,
171toolbars, bubble help and accelerator keys. If you know how
172to use OS/2, you already know how to use most of FM/2. You
173can easily glean the rest from the extensive online help,
174including tutorials.
175
176This document explains how to install FM/2, including
177upgrading from previous versions. It explains command line
178syntaxes (parameters in a program object) and how to get the
179program(s) running. The online help tells you how to
180actually use FM/2. I'll try to keep this brief.
181
182This program is free software; you can redistribute it
183and/or modify it under the terms of the GNU General Public
184License as published by the Free Software Foundation; either
185version 2 of the License, or (at your option) any later
186version.
187
188This program is distributed in the hope that it will be
189useful, but WITHOUT ANY WARRANTY; without even the implied
190warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
191PURPOSE. See the GNU General Public License for more
192details.
193
194You should have received a copy of the GNU General Public
195License along with this program; if not, write to the Free
196Software Foundation, Inc., 59 Temple Place, Suite 330,
197Boston, MA 02111-1307 USA
198
199
200FM/2 3.x installation instructions:
201==================================
202
203Pre-requisite:
204 WarpIN 0.9.20 or higher must be installed.
205
206Install (or re-install) from a FM/2 ZIP file distribution
207---------------------------------------------------------
208
2091. Unpack the FM2*.ZIP archive in a private directory (for
210example, C:\TMP). (UNZIP.EXE works nicely to unpack the
211file.) Two WPI files, FM2.WPI and FM2UTILS.WPI will be
212unzipped.
213
2142. Follow the instructions for installing from WPI file(s)
215below.
216
217
218Install (or re-install) from a FM/2 WPI file distribution
219---------------------------------------------------------
220
2211. Open the WPS folder containing the WPI file(s).
222
2232. Double click on FM2.WPI. Since WarpIN associates itself
224with WPI files this will start WarpIN with FM2.WPI as the
225parameter.
226
2273, You may then install FM/2 to a directory of your choice
228and, if FM2UTILS.WPI is present, install FM/2 Utilities to
229a directory of your choice.
230
231NOTE: If you double click on FM2UTILS.WPI instead of
232FM2.WPI, you will only be able to install the FM/2
233Utilities. It is recommended that, even if you only want to
234install FM/2 Utilities, that you do so using FM2.WPI.
235
236
237Moving FM/2 and/or FM/2 Utilities:
238----------------------------------
239
2401. Copy your existing installation directory to the new
241location.
242
2432. If you have added your own icons to any of the FM/2
244folders, then you should move them elsewhere temporarily.
245
2463. Follow the instructions for de-installing below.
247
2484. Re-install the package using the installation
249instructions above. This will update the WarpIN database and
250reset your icons to the new locations.
251
2525. Move the icons you saved in step #2, back into the FM/2
253folders if you wish.
254
255
256De-installing FM/2 and/or FM/2 Utilities:
257-----------------------------------------
258
2591. Run Warpin without parameters.
260
2612. Right click on a package you want to de-install and
262select "de-install all packages".
263
2643. Click on OK in the "De-install Packages" window that
265appears.
266
267
268
269=================
270First-time notes:
271=================
272
273Starting FM/2 -- how it works, customizing parameters:
274
275If you start File Manager/2 (filename FM3.EXE) with no
276parameters, it opens the Drive Tree window but no directory
277windows (unless the "Save state of dir windows" toggle is
278checked -- see online help).
279
280File Manager/2 optionally accepts names of directories in
281the parameters field of its program object; it'll open a
282directory window for each one. Hint: If you often do
283different specific things with FM/2, you might set up a WPS
284object customized to start up ideally for each activity. For
285example, if you wanted to maintain your BBS areas, you might
286have one object with parameters like: "D:\BBSDIR
287D:\BBSDIR\MAILIN D:\BBSDIR\MAILOUT", and if you also like to
288use FM/2 to set icons on files, you might have another
289object with parameters like: "E:\MYICONS D:\NEWFILES". The
290State quicklist can also be used for this within FM/2 itself
291-- see online help.
292
293You can exclude drives in the parameters by prefacing the
294drive letter with "/", and there can be more than one drive
295letter behind the "/" (i.e. "/BH" to exclude both drives B:
296and H:). Hint: Many people like to use /B to exclude
297"phantom" drive B: if they have a single-floppy system.
298Similarly, you can cause drives NOT to be prescanned by the
299Drive Tree by prefacing the drive letter with ";", drives
300NOT to load icons for objects by prefacing the drive letter
301with ",", drives NOT to load subjects for objects by
302prefacing the drive letter with "`" and drives NOT to load
303longnames for objects by prefacing the drive letter with
304"'". This can be handy if you have a very slow drive like a
305CD-ROM or Zip drive. FM/2 Lite recognizes these switches,
306too. See also the Drive Flags dialog in FM/2.
307
308If you place the plus sign "+" (alone, separated from
309anything else by spaces) in the parameters, FM/2 will log,
310to FM2.LOG, delete, rename, move and copy operations that
311are performed by drag-and-drop or with the menus. FM/2 Lite
312recognizes this switch, too.
313
314The parameter "-" (alone, separated from anything else by
315spaces) causes FM/2 to ignore, not load or save, the
316previous state of directory windows (see the "Save state of
317dir windows" toggle under Config Menu->Toggles in the online
318help) for that invocation.
319
320You can specify the name of an alternate INI file with
321"-<inifilename>" -- for example: "-C:\FM2\MYINI.INI".
322
323You can also specify the INI file location with the
324environment variable FM2INI -- for example:
325 SET FM2INI=C:\FM2\MYINI.INI.
326
327
328------------------------------
329How to get started using FM/2:
330-----------------------------
331Please read the following sections in the online help when
332you start FM/2 for the first time: "How to use FM/2's Help,"
333"Terminology" and "General Help," then "Hints." A peek at
334the labelled "Window Layouts" pictures would probably be a
335good idea, too. The rest you can browse as you get time/feel
336the need; for instance, if you want to know what a toggle
337does, read the help under Settings notebook for that page
338(each Settings notebook page has its own Help button).
339
340If you prefer hard copy help, print this file, run FM/2,
341press F1, click the "Print" button at the bottom (IBM View)
342or top (Newview)of the help window that appears and then print
343both the "Contents" and "All sections" (keep an eye on the printer,
344after page 100 of "All sections" as the Help Manager will
345begin printing its own help then -- you may want to abort
346printing at that point). Advanced and/or curious users may
347also want to print FM3TOOLS.DAT and ARCHIVER.BB2. Be sure
348you have plenty of paper and ink handy -- the package is
349well documented. You'll probably also want a three-ring
350binder and hole punch to get it bound, as staples aren't
351going through that puppy. You can, of course, print only the
352sections that are of particular interest to you.
353
354Additional documentation:
355------------------------
356 FM3.HLP: FM/2's online help file.
357
358Look in the FM/2 Docs subfolder of the File Manager/2 folder
359for easy access to all documentation.
360
361
362Bonus programs:
363==============
364
365You'll note the extra objects that the Install program
366creates in the FM/2 Tools subfolder of the File Manager/2
367folder. FM/2 is modular, so that you can get directly to
368some of its components without running the entire ball of
369wax. This may allow you to enhance the behavior of some of
370your other applications in the WPS tradition. You don't
371_have_ to keep these around, of course -- FM/2 itself
372contains all their functionality.
373
374ARCHIVE VIEWER/2: Intended for drag-and-drop operation (or
375WPS association) with WPS objects or other applications.
376Drag an archive onto it, drop it, get an archive listing
377box. FM/2's installation program sets up some associations
378between archive files and this program by file extension.
379AV/2 will try to display whatever you give it as
380sensibly as it can. Filename AV2.EXE.
381
382EA VIEWER: Drag a file system object onto it and it'll show
383you the object's extended attributes. Filename EAS.EXE.
384
385INI VIEWER: Drag an .INI file onto it and it'll show you its
386contents. Filename INI.EXE.
387
388BOOKSHELF VIEWER: Shows all .INF files in a listbox and lets
389you pick the one(s) you want to view. If you give any
390command line argument, the .HLP files on the HELP path will
391be shown instead (the Helpfile Viewer object calls
392VIEWINFS.EXE with "dummy" for an argument, for example).
393Filename VIEWINFS.EXE.
394
395PROCESS KILLER: Lets you kill off renegade processes. An
396English version of PSTAT.EXE must be on your PATH. Filename
397KILLPROC.EXE.
398
399UNDELETER: Lets you undelete files (via interface with
400UNDELETE.COM). Drag a file system object onto it and it'll
401let you undelete files for that drive. Filename UNDEL.EXE.
402
403VISUAL TREE: Opens a Drive Tree window (like the WPS Drives
404object with more horsepower). Filename VTREE.EXE.
405
406VISUAL DIRECTORY: Opens a Directory Container window; drag a
407file system object onto it and this will open its directory
408(like a WPS directory Folder with more horsepower). Filename
409VDIR.EXE.
410
411COLLECTOR: Opens a Collector window. Filename VCOLLECT.EXE.
412Two other objects, "See all files" and "Seek and scan" are
413created which call up the Collector and go directly to
414dialogs for the appropriate purpose.
415
416GLOBAL VIEWER: Opens a global view of a drive or drives.
417Filename GLOBAL.EXE.
418
419DATABAR: Opens a databar showing some system information.
420Filename DATABAR.EXE.
421
422DIRSIZE: Shows where drive usage is concentrated. Filename
423DIRSIZE.EXE.
424
425FM/2 LITE: A simplified interface for "dummies." Filename
426FM4.EXE.
427
428FM/2's install creates FM2.CMD, AV2.CMD, VDIR.CMD,
429VTREE.CMD, VCOLLECT.CMD, UNDEL.CMD, KILLPROC.CMD, INI.CMD,
430EAS.CMD, DIRSIZE.CMD, VIEWINFS.CMD and VIEWHELP.CMD files
431for you in a directory "utils" off the install directory.
432You should add this directory to your PATH= statement in
433CONFIG.SYS (type HELP PATH at a command line for more info).
434If you prefer, FM/2's INSTALL builds a SETENV.CMD in the
435FM/2 directory which you can call to set the PATH for FM/2
436in any given session without modifying CONFIG.SYS.
437
438
439Troubleshooting:
440===============
441
442FM/2 seems much slower than previous versions.
443The Find Buffer in FM/2 has been reworked to make it user
444settable in more place and significantly enlarge it. This
445significantly increases the loading speed for large directories
446However, most users will need to reset the buffer by going
447to the settings notebook scanning page and setting FindBuf.
448The new default for clean installs is 10240. We recommend you
449change to this setting (or higher) unless you have very limited
450hardware (less than 32 meg of memory original Pentium or earlier).
451
452If FM/2 won't run, the probable culprit is CONFIG.SYS. Your
453LIBPATH statement should contain a ".;" entry. If yours
454doesn't, add it. It's standard for an OS/2 installation, but
455some buggy install programs knock it out because they
456translate entries to their full pathname before rewriting
457(so ".;" gets translated to whatever the current directory
458is for the buggy install program). What this ".;" entry does
459is allow a program to find and use .DLL files in the
460program's current directory -- obviously something you want
461programs to be able to do, otherwise you'd have to put every
462application's .DLLs into directories already on the LIBPATH,
463or add the directories of all applications to the LIBPATH, a
464rather huge pain in the, uh, neck.
465
466If things in FM/2 are suddenly acting strange after an
467upgrade, first check the integrity of the install using
468using WarpIN. If it shows a problem rerun the install
469package. If that fails try installing to a new directory
470or backup your existing directory so you can save any changes
471you made to the template files then uninstall and reinstall.
472Once you have FM/2 working migrate the *.ini, *.dat, *.tls,
473*.bb2 and *.cmd from your old install/backup to recover your
474custom settings
475
476If the "FM/2 Online Help" object in the "FM/2 Docs"
477subfolder won't work properly, you've got a version of
478VIEW.EXE that won't directly display help (.HLP) files. Use
479SEEHELP.EXE from the FM/2 Utilities package to get around
480this problem (or upgrade your version of OS/2).
481
482Don't drag files over Netscape -- it will lock up if files
483(not WPS objects; there's a subtle difference) are dragged
484over it.
485
486If you get a popup dialog that needs to be reported to the
487maintainer, you can either take a screen shot or you can
488capture the information from STDERR with:
489
490 FM3 2>STDERR.LOG
491
492This technique works for all the FM/2, FM/2 Lite and all the
493standalone applets.
494
495If you are having trouble with Drag and Drop operations, try
496the + command line switch described above. The content of
497FM2.LOG may be helpful.
498
499
500Known problems/shortcomings:
501===========================
502
503- FM/2 does not properly report sizes of some files with
504long name resident on Win95/NT drives.
505
506- File List Container fails to fill after drive change
507SYS0039 error.
508
509- Tree switching on Focus/Directory Change appears to be
510slower than expected.
511
512- Access to LS120 and FAT32 drives may be slower than expected
513
514- Icon display in Directory Container does not always match
515WPS icons
516
517- Spurious WPS Objects Handles may be created during some
518operations
519
520- Trying to run Global.exe from the command line in 4OS2
521(perhaps other shells) results in the execution of 4OS2's "Global"
522command. Global.exe can be run by placing it in quotes or
523prefixing it with *. See 4OS2's documentation for more information.
524
525- As with any OS/2 program significant changes (such as our
526change to OpenWatcom) will result in the incompatibility of
527older (VAC) exes with new dlls and vice versa. Attempting to run
528OpenWatcom exes with a VAC dll loaded in memory or in your
529libpath ahead of the new version will result in a SYS3175 in
530popuplog.os2. The reverse gives a SYS2070. If you experience these
531problems search your libpath for fm3dll.dll and remove or rename
532it. Your libpath should have "." (without the quotes) as your
533first entry to minimize the likelihood of this problem. FM/2's
534installer does not add the FM/2 directory to the libpath.
535
536- See http://svn.netlabs.org/fm2/report/1 for a complete list of
537currently active bugs
538
539
540
541About FM/2:
542==========
543
544FM/2 was originally written by:
545
546 Mark Kimes
547 <hectorplasmic@worldnet.att.net>
548
549He has kindly allowed me to take over maintenance and
550support of FM/2 and to release the program under the GNU GPL
551license. I'm sure he would appreciate a Thank You note for
552his generosity.
553
554Support:
555=======
556
557There is a Yahoo group devoted to fm/2 at:
558
559 http://groups.yahoo.com/group/fm2user/
560
561You will find lots of friendly folks ready to help.
562
563FM/2 is moving to Netlabs (thanks Adrian).
564
565Check it out at
566
567 http://svn.netlabs.org/fm2
568
569Not everything is in place yet, but this is the place to
570enter defect tickets and enhancement requests (username netlabs,
571password guest; please include a valid email so we can contact you
572if we need more information). Eventually, the mailing list and the
573file archives will all move to the Netlabs server where you can
574find the source code.
575
576You can reach us directly at:
577
578 Steven H. Levine
579 steve53@earthlink.net
580
581 or
582
583 Gregg Young
584 ygk@qwest.net
585
586We also monitor the comp.os.os2.apps newsgroup and several
587others in the comp.os.os2.* hierarchy.
588
589Thanks and enjoy.
590
591$Id: README 1278 2008-11-16 20:48:57Z gyoung $
Note: See TracBrowser for help on using the repository browser.