you could do:

Then, in TLIB.CFG, somewhere above your "PROJLEV %PROJNAME%" line, you would have a line like this:

More likely, you'll just make a .BAT file to build the C:\FAKEENV.XYZ file or to copy pre-built files to C:\FAKEENV.XYZ, perhaps like this:

Note, too, that TLIB 5.04 and 5.5x support extensive new configuration capabilities, which allow you to evaluate string and arithmetic expressions, test for file existance or size, expand and parse file and directory names, etc.. So, for example, you can easily use a directory naming convention to set your project level.

In general, an errorlevel status of 0 means that the operation succeeded, and an errorlevel status of 1 or higher indicates that an error occurred. (Click "View Log" or "Run" to see the history.)

Starting with TLIB 5.50t (circa 19-Jan-98), the default location for TLIB.INI is now the root of the C: drive, which is fine for most users.

TLIB for Windows recognizes the environment variable name TLIBINI to point to the directory where the TLIB.INI file is located. TLIB for Windows will create and use a TLIB.INI file in the directory you specify.

In order to make this work under Win 3.1x or Win9x, you must set TLIBINI equal to a directory name in your AUTOEXEC.BAT file. In NT 4.0 you can set or change environment variables via Start -> Settings -> Control Panel -> System -> Environment. Win2000 is similar to NT 4.0, set the environment variables via Start -> Settings -> Control Panel -> System -> Advanced -> Environment Variables...

For example, the following line in a Win95 AUTOEXEC.BAT:

...would cause TLIB for Windows to create its TLIB.INI file in C:\MYSTUFF\.

If you already have preferences in your TLIB.INI file that you want to keep, you can copy it to the directory you specify in your TLIBINI environment variable. You will need to set TLIBINI on each machine that will be running TLIB for Windows from the network drive.

Never - With Never selected, TLIB will always use the user ID specified by the ID parameter in TLIB.CFG. This choice will ignore the User Name field on the screen. If you have ID configured to get a network login name (e.g., "ID *NOVELL*") then you will probably want to check Never.

Always - With Always selected, TLIB will always use the user ID specified in the User Name field in the pop-up window. This behavior will ignore the ID parameter in your TLIB.CFG. It also saves the value from the User Name field in your TLIB.INI file, and will continue to use it until you change it again. Note that starting with TLIB 5.50t (circa 19-Jan-98), command- line (console mode) versions of TLIB also check the TLIB.INI file for an "always" user ID override, so that the "Always" choice will override your user ID for all versions of TLIB.

Ask - With Ask selected, TLIB for Windows will get the user ID from the ID configuration parameter and compare it to the ID set in the User Name field. If they are different it will ask you which ID you wish to use.

In TLIB 5.04h and later, the default setting is Ask. However, if TLIB seems to be ignoring your configured ID parameter, it may be because Always-override has been selected in TLIB for Windows.

We don't know the cause. However, most people can avoid or work around the problem in any of three ways:

1) Run the 32-bit version of TLIB for Windows, instead of the 16-bit version (of course, that won't help you for the Configuration Wizard, which is only 16-bit); or,

2) Set the "run in separate memory space" option for the shortcuts used to run 16-bit VB programs, including 16-bit TLIB and the TLIB Configuration Wizard; or,

3) Shutdown and restart your computer (a temporary fix).

But for one person running version 4.80.20000717 of the Netware Client, that wasn't sufficient. He had to:

  jfile \\ourserver\sys\tlibstuf\journal.dat
  path \\ourserver\sys\tlibstuf\libs\*\
  level n=dev d=\\ourserver\sys\tlibstuf\lvls\dev\ s=q a=y

The use of UNC paths in the TLIB.CFG file is a good idea if there is a chance that all users might not use the same drive letter mappings.

There are some things for which TLIB requires a drive letter, but they don't affect the TLIB.CFG file:

1) It is necessary to use a drive letter for the TLIB installation directory, where TLIB's .EXE and .DLL files reside. But it needn't be the same drive letter for every user, even if you install to a network directory. When the additional users run NETSETUP to create their shortcuts, etc., they can just path to it via whatever drive letter they have mapped to that network drive on that machine.

2) The other place you need drive letter access is when you set the "current directory" in TLIB's GUI. That is your "work directory" and it would be somewhat odd to have a work directory that didn't have a drive letter mapped for it. The reason TLIB requires a drive letter for the current directory is that it actually does a "chdir" (change directory) to make that the current directory, and Windows requires that the current directory have a drive letter.

  extension c,h,cpp,hpp,asm,bat,,doc,txt,jpg,gif

  libext ?$?????
  lokext ?^?????

But if you have TLIB configured without an EXTENSION parameter, that also fails.

  f:
  cd "\TLIBLIBS"
  attrib -r *.?$*
  ren *.c$ *.c_____$
  ren *.h$ *.h_____$
  ren *.a$m *.asm___$
  ren *._$ *.______$

This change will render the EXTENSION parameter completely unnecesssary unless you have source files with extensions that are more than 5 characters long. So this solution is preferable if your list if extensions is growing.