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