| 1 | :h2 res=100100 id='PANEL_TROUBLE'.
|
|---|
| 2 | Troubleshooting
|
|---|
| 3 | :p.If FM&slash.2 won&apos.t run&comma. &lpar.Error Message&colon. FM3RES.STR isn't in right format, at least for this version of FM/2.&rpar.
|
|---|
| 4 | the probable culprit is CONFIG&per.SYS&per. Your LIBPATH statement should contain a "&per.&bsl." entry&per.
|
|---|
| 5 | If yours doesn&apos.t&comma. add it&per. It&apos.s
|
|---|
| 6 | standard for an OS&slash.2 installation&comma. but some buggy install programs knock
|
|---|
| 7 | it out because they translate entries to their full pathname before
|
|---|
| 8 | rewriting &lpar.so "&per.&bsl." gets translated to whatever the current
|
|---|
| 9 | directory is for the buggy install program&rpar.&per. What this "&per.&bsl." entry does is
|
|---|
| 10 | allow a program to find and use &per.DLL files in the program&apos.s current directory
|
|---|
| 11 | &endash.&endash. obviously something you want programs to be able to do&comma. otherwise
|
|---|
| 12 | you&apos.d have to put every application&apos.s &per.DLLs into directories already on the
|
|---|
| 13 | LIBPATH&comma. or add the directories of all applications to the LIBPATH&comma. a
|
|---|
| 14 | rather huge pain in the&comma. uh&comma. neck&per.
|
|---|
| 15 | :p.If things in FM&slash.2 are suddenly acting strange after an upgrade&comma.
|
|---|
| 16 | first make &us.sure&us. you unpacked &us.all&us. the files and overwrote the old
|
|---|
| 17 | ones&comma. then run INSTALL&per.CMD to update your WPS objects&per.
|
|---|
| 18 | :p.If the "FM&slash.2 Online Help" object in the "FM&slash.2 Docs" subfolder
|
|---|
| 19 | won&apos.t work properly&comma. you&apos.ve got a version of VIEW&per.EXE that won&apos.t
|
|---|
| 20 | directly display help &lpar.&per.HLP&rpar. files&per. Use SEEHELP&per.EXE from the
|
|---|
| 21 | :link reftype=hd res=100090.FM&slash.2 Utilities:elink. package to
|
|---|
| 22 | get around this problem &lpar.upgrade your version of OS&slash.2 or switch to NewView.exe&rpar.&per.
|
|---|
| 23 | :p.Don&apos.t drag files over Netscape &endash.&endash. it will lock up if files &lpar.not WPS
|
|---|
| 24 | objects&semi. there&apos.s a subtle difference&rpar. are dragged over it&per.
|
|---|
| 25 |
|
|---|
| 26 | :h2 res=100105 name=PANEL_KPROBLEMS.
|
|---|
| 27 | Known problems&slash.shortcomings
|
|---|
| 28 | :p. &endash. FM&slash.2 does not properly report sizes of some files with long
|
|---|
| 29 | name resident on Win95&slash.NT drives&per.
|
|---|
| 30 | :p. &endash. File List Container fails to fill after drive change SYS0039
|
|---|
| 31 | error&per.
|
|---|
| 32 | :p. &endash. Tree switching on Focus&slash.Directory Change appears to be slower
|
|---|
| 33 | than expected&per.
|
|---|
| 34 | :p. &endash. Access to LS120 and FAT32 drives slower than expected
|
|---|
| 35 | :p. &endash. Icon display in Directory Container does not always match WPS icons
|
|---|
| 36 | :p. &endash. Spurious WPS Objects Handles created during some operations
|
|---|
| 37 | :p. &endash. PM has a 64k draginfo buffer for compatibility with 16 bit programs.
|
|---|
| 38 | This limits each drag operation to a maximum of about 1800 objects, however in some testing
|
|---|
| 39 | we were limited to under 1700. The main problem is PM is happy to over write this buffer.
|
|---|
| 40 | The result is significant corruption of share memory forcing a reboot. We have limited drag
|
|---|
| 41 | operations to maximum number of objects that will fit in the dragitem
|
|---|
| 42 | structure (700-1700 depending on path length and other factors)
|
|---|
| 43 | to prevent this problem.
|
|---|
| 44 | :p. &endash. Trying to run Global.exe from the command line in 4OS2 (perhaps other shells)
|
|---|
| 45 | results in the execution of 4OS2's "Global" command. Global.exe can be run by placing
|
|---|
| 46 | it in quotes or prefixing it with *. See 4OS2's documentation for more information.
|
|---|
| 47 | :p. &endash. As with any OS/2 program significant changes (such as our change to OpenWatcom)
|
|---|
| 48 | will result in the incompatibility of older (VAC) exes with new dlls and viceversa. Attempting to run
|
|---|
| 49 | OpenWatcom exes with a VAC dll loaded in memory or in your libpath ahead of the new version
|
|---|
| 50 | will result in a SYS3175 in popuplog.os2. The reverse gives a SYS2070. If you experience these
|
|---|
| 51 | problems search your libpath for fm3dll.dll and remove or rename it. Your libpath should have "."
|
|---|
| 52 | (without the quotes) as your first entry to minimize the likelyhood of this problem. FM/2's installer
|
|---|
| 53 | does not add the FM/2 directory to the libpath.
|
|---|
| 54 | :p. &endash. Accessing a subdirectory on a vfat (fat) formatted USB removable drive may result
|
|---|
| 55 | in a SYS3175. If this occurs try accessing the directory using "open" from the context (popup)
|
|---|
| 56 | menu. Mounting it using netdrives' vfat plugin also solves the problem.
|
|---|
