Custom Query (75 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (37 - 39 of 75)

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Ticket Resolution Summary Owner Reporter
#51 fixed Detect distro on which we're installing and select LIBPATH accordingly Lewis Rosenthal
Description

The tooltip for lSwitcher Hook says that the default path for the dll is eCS\dll. In the path box below, however, the path field is populated with C:\SYS\DLL. This eCS 2.1 machine has no \SYS directory on it, and C:\SYS is not going to be in LIBPATH, no way, no how.

Fixing the tooltip to be more generic is one thing (it should not be necessary to advise the user of the default when he can easily see for himself, down below). Fixing the default path is another.

#52 fixed Select better (DOS-accessible) default location for LSWITCHD TSR Lewis Rosenthal
Description

The default location for lSwitcher seems to be C:\TOOLS\lSwitcher, but this won't work for the DOS TSR ("lSwitcher" is too long). Suggest one of the following options:

  1. Use lSwitch or LSW for program directory if we're going to keep everything together and runnable from the installation directory.
  2. The TSR could be put into its own package and placed elsewhere, in a DOS-accessible (8.3) directory in order to be used (of course, all directories in the path to be traversed must also be DOS-accessible).
  3. The TSR could be put into its own package, defaulting to the same directory as the rest of the files, but with its own tooltip advising that it should be moved to a DOS-accessible (8.3) path in order to be used. The path field should be editable to allow direct installation to such a location.
#53 fixed Document usage of LSWITCHD TSR Lewis Rosenthal Lewis Rosenthal
Description

I have been using:

LSWITCHD.EXE /SH

in my AUTOEXEC.BAT for well over a decade. I have no recollection what the /SH switch is supposed to do. The TSR itself has no built-in help (e.g., LSWITCHD /? doesn't work), and apparently, there is no /U switch to unload it from memory (which isn't a big deal).

There is no mention of proper placement of the executable or how it works (it does nothing itself other than access lswhook.dll). It isn't very useful in DOS windows (but again, this isn't documented anywhere).

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
Note: See TracQuery for help on using queries.