Changeset 915 for trunk/README
- Timestamp:
- Jan 10, 2008, 4:44:44 AM (18 years ago)
- File:
-
- 1 edited
-
trunk/README (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/README
r866 r915 6 6 ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 7 7 8 FM/2 3.09 adds "mailto:" so you can configure the ability to 9 double click an email address in the new viewer and have it 10 open a new email using that address. The viewer page in the 11 settings notebook was split into 2 pages to facilitate the 12 change. Additionally, We fixed some defects and enhance 13 performance in some areas such as commandline quoting. 14 8 15 FM/2 3.08 has had changes to its file filtering logic. 9 16 It now searches for the last extension if a mask like *.zip 10 17 is used. This change was made to over come the problem with 11 associations failing on files with multiple ".". You can 18 associations failing on files with multiple ".". You can 12 19 also seach for a complete string within the file names by 13 20 using the pattern *stuff* (stuff can't contain an * or ?). … … 17 24 18 25 FM/2 3.07 had changes made to its ini file structure. 19 These changes mean that the ini file is not backward 26 These changes mean that the ini file is not backward 20 27 compatible. Please backup you FM3.INI file before installing 21 so you can revert to an earlier version without losing some 28 so you can revert to an earlier version without losing some 22 29 of your customizations. Please note you need to leave a copy 23 of the fm3.ini file in the install directory in order to keep your 24 customizations in 3.07. The temp file fm3.!!! will not update 30 of the fm3.ini file in the install directory in order to keep your 31 customizations in 3.07. The temp file fm3.!!! will not update 25 32 the new ini as it is only used when fm2 is running. 26 33 27 File Manager/2 (FM/2) starting with version 3.6 is being 28 built with OpenWatcom. Changing compilers can introduce 34 File Manager/2 (FM/2) starting with version 3.6 is being 35 built with OpenWatcom. Changing compilers can introduce 29 36 unexpected problem so you may want to backup your current 30 install, or at minimum have a working copy of the FM/2 37 install, or at minimum have a working copy of the FM/2 31 38 version 3.5.9 warpin available for reinstall if problems arise. 32 39 To backup your current install simple zip up your install 33 40 directory with its subdirectories or copy them to a different 34 location.To restore simply copy the old FM/2 back to the 41 location.To restore simply copy the old FM/2 back to the 35 42 its original location. Remember you can't use the new FM/2 36 43 to do this since if it is running some files will be locked 37 44 and won't be replaced. If you didn't backup and need to go 38 back just install the 3.5.9 warpin package over the new 45 back just install the 3.5.9 warpin package over the new 39 46 install. It will warn you that the install is newer but just 40 tell it to install anyway. The warpin install process is 41 designed to save all your customizations. Don't delete the 42 new install if you don't have a backup since this will result 43 in the loss of any custom changes you have made. If you need 44 to delete it to get the reinstall to work. Backup up the new 45 install and then copy the *.bmp, *.tls, *.dat, *.cmd & *.ini 46 files back to the install directory after the reinstall. 47 Don't copy the *.str files as they are version specific. 47 tell it to install anyway. The warpin install process is 48 designed to save all your customizations. Don't delete the 49 new install if you don't have a backup since this will result 50 in the loss of any custom changes you have made. If you need 51 to delete it to get the reinstall to work. Backup up the new 52 install and then copy the *.bmp, *.tls, *.dat, *.cmd & *.ini 53 files back to the install directory after the reinstall. 54 Don't copy the *.str files as they are version specific. 48 55 If you have problems be sure to report it (See Support 49 at the end of this file). 56 at the end of this file). 50 57 51 58 File Manager/2 (FM/2) is a free OS/2(Warp)/eCS Presentation … … 325 332 =============== 326 333 327 FM/2 seems much slower than previous versions. 334 FM/2 seems much slower than previous versions. 328 335 The Find Buffer in FM/2 has been reworked to make it user 329 settable in more place and significantly enlarge it. This 336 settable in more place and significantly enlarge it. This 330 337 significantly increases the loading speed for large directories 331 However, most users will need to reset the buffer by going 338 However, most users will need to reset the buffer by going 332 339 to the settings notebook scanning page and setting FindBuf. 333 340 The new default for clean installs is 10240. We recommend you … … 403 410 operations 404 411 405 - Trying to run Global.exe from the command line in 4OS2 406 (perhaps other shells) results in the execution of 4OS2's "Global" 407 command. Global.exe can be run by placing it in quotes or 412 - Trying to run Global.exe from the command line in 4OS2 413 (perhaps other shells) results in the execution of 4OS2's "Global" 414 command. Global.exe can be run by placing it in quotes or 408 415 prefixing it with *. See 4OS2's documentation for more information. 409 416 410 - As with any OS/2 program significant changes (such as our 411 change to OpenWatcom) will result in the incompatibility of 417 - As with any OS/2 program significant changes (such as our 418 change to OpenWatcom) will result in the incompatibility of 412 419 older (VAC) exes with new dlls and vice versa. Attempting to run 413 OpenWatcom exes with a VAC dll loaded in memory or in your 414 libpath ahead of the new version will result in a SYS3175 in 420 OpenWatcom exes with a VAC dll loaded in memory or in your 421 libpath ahead of the new version will result in a SYS3175 in 415 422 popuplog.os2. The reverse gives a SYS2070. If you experience these 416 problems search your libpath for fm3dll.dll and remove or rename 417 it. Your libpath should have "." (without the quotes) as your 418 first entry to minimize the likelihood of this problem. FM/2's 423 problems search your libpath for fm3dll.dll and remove or rename 424 it. Your libpath should have "." (without the quotes) as your 425 first entry to minimize the likelihood of this problem. FM/2's 419 426 installer does not add the FM/2 directory to the libpath. 420 427
Note:
See TracChangeset
for help on using the changeset viewer.
