Frequently Asked Questions (FAQ)
This file is the start of a FAQ (Frequently Asked Questions list) for TLIB Version Control users. These questions and answers are in no particular order. _________________________ Q: What does tech support cost? A: Tech support is free. Just call us at 1-919-481-0149. Or send an email to firstname.lastname@example.org. (Don't be afraid to pester us if you don't get a quick answer; we get a LOT of email, and the squeaky wheel sometimes gets greased sooner.) [6-Aug-1999] _________________________ Q: When I tried to run the 32-bit GUI version of TLIB, WTLIB32.EXE, I got "Runtime error 50003, unexpected error." What caused this, and how can I fix it? A: This happens to some people when they try to run WTLIB32.EXE without first running SETUP.EXE or NETSETUP.EXE. The solution is to run NETSETUP.EXE. (This will also create your start menu shortcuts.) The error is due to having out-of-date or mismatched versions of Microsoft's OCX and/or DLL files. TLIB 5.51a gives a more informative error message. Run NETSETUP.EXE, and the problem will go away. [12-Aug-1999] _________________________ Q: Configuring TLIB's IF-ENDIF blocks to tell TLIB which files are Binary and which are Text is a pain. Can't you make this automatic? A: TLIB 5.51a supports configuring FILETYPE AUTOmatic. [21-Aug-1999] _________________________ Q: Where's your TLIB Add-In for Visual Basic 6.0? A: In TLIB 5.51a (just released) [12-Aug-1999] _________________________ Q: I wish TLIB's compiler-native project file support worked with my obscure compiler/assembler/editor/whatever. A: Give us a call. If we can figure out how to parse your tool's project files, we can probably add this support to TLIB. You'll have to help us out by providing us with a few sample project files, and by testing it for us. [6-Aug-1999] _________________________ Q: I'm running TLIB 5.04d, and I get a "Bad dot command" error for one of the TLIB libraries. A: If you're running TLIB 5.03/beta, or TLIB 5.04 prior to 5.04f, then there is a situation in which a bug in TLIB can cause a bogus "Bad dot command" error to be reported. The bug is fixed in 5.04f. The situation occurs when TLIB 5.03..5.04e is processing a text-format library file created by an earlier version of TLIB, and in which some lines were terminated by LF alone instead of CR+LF. The library is actually undamaged and works fine with TLIB 5.04f or later. [28-Jan-1997] _________________________ Q: I just installed my upgrade to TLIB for Windows, and something has me stumped. How can I change the current project level? When working in DOS, we had a DOS environment variable referenced in the TLIB.CFG file, to set the named project level. However, in Windows you can't change the environment variables after Windows starts, because every program gets a fresh copy of the environment. A: The easiest solution, which is closest to what you are used to doing, is to just to change a file instead of an environment variable. E.g., Instead of doing: SET PROJNAME=whatever you could do: ECHO SET PROJNAME=whatever >C:\FAKEENV.XYZ Then, in TLIB.CFG, somewhere above your "PROJLEV %PROJNAME%" line, you would have a line: INCLUDE C:\FAKEENV.XYZ 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: @REM - SETLEV.BAT @rem (Assumes that your TLIB.CFG has an "include c:\fakeenv.xyz" line) @echo off if '%1'=='' goto givehelp if not exist z:\\zumbach\sys\levls\%1\tlibwork.trk goto badlevl :doit echo SET PROJLEV=%1 >C:\FAKEENV.XYZ echo. echo Okay, your TLIB project level is now %1 goto xit :badlevl echo. echo Warning: z:\\zumbach\sys\levls\%1\tlibwork.trk doesn't exist. choice The reason may be that %1 is a bad project level name. Continue? if errorlevel 3 goto badlevel if errorlevel 2 goto xit if errorlevel 1 goto doit goto xit :givehelp echo. echo Usage: echo SETLEV levelname :xit 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. Most users have just a single TLIB.CFG file in the TLIB install directory (the directory in which TLIB*.EXE and TLIB*.DLL reside). The TLIB.CFG file can have special-case configuration stuff for a particular project level or a particular user or whatever, as needed. See RELEASE.TXT (or RELEASE.WRI) and CONFIG.TXT (or CONFIG.WRI). [28-Jan-1997] _________________________ Q: What is the status column in the file picklist in TLIB for Windows? A: The status column in the file picklist displays the equivalent of a DOS errorlevel returned after a TLIB operation, for each source file. In command-line versions of TLIB, it is only possible to return one errorlevel, so command-line versions of TLIB return the highest (most severe) errorlevel seen for any of the files processed. However, Windows GUI versions of TLIB display the errorlevels for each file. 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.) In 16-bit TLIB for Windows, you can wave your mouse cursor over the word "Status" and TLIB will describe it in the "help bar" at the bottom of the main screen. [28-Jan-1997] _________________________ Q: We have TLIB for Windows installed on a network drive and now all of us are sharing the same TLIB.INI file. How can we set up individual TLIB.INI files? A: Older versions of TLIB for Windows, by default, used to store the TLIB.INI in the TLIB installation directory. In multi-user TLIB installations it was necessary to set the TLIBINI environment variable to tell TLIB where to store the TLIB.INI files (normally on each user's private hard disk drive). 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 Win95, 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: set tlibini=c:\mystuff\ ...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. Note: The 16-bit and 32-bit versions of TLIB for Windows use the same TLIB.INI file, so you can use them interchangably without losing your most-recently-used lists, etc.. [28-Jan-1997, 10-Aug-2000] _________________________ Q: I just used a co-worker's TLIB for Windows and it gave me their user ID. Why didn't it get my ID from the network? A: Note: please also see the next Q&A, below. There is an option under the File menu in TLIB for Windows called Change User ID. If you select this option, you will get a pop-up window with a field for entering a user name, and three different radio-button options with choices for how TLIB should determine the user ID. These choices determine whether TLIB should override the user ID set by the ID parameter in your TLIB.CFG file with the user ID you enter in the pop-up window's User Name field. The choices are Never-override, Always-override, and Ask: 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. Note: if you want to disable this feature altogether, you may remove the "CW" command from the COMMANDS list in TLIB.CFG. [28-Jan-1997] _________________________ Q: Why won't the 32-bit versions of TLIB correctly look up my TLIB user ID from my Novell Netware login name? A: This capability is in TLIB 5.51a (just released). Note: please also see the previous Q&A, above. [12-Aug-1999] _________________________ Q: I got an "Out of memory" error running TLIB.EXE. What can I do about it? A: You are probably running a DOS real-mode only version of TLIB. Try running one of the protected mode TLIBs, such as TLIBX.EXE, TLIB2.EXE (under OS/2 or NT), or TLIB32C.EXE (under Win95/98 or NT), or either the 16-bit or 32-bit GUI Windows TLIB. (Note: depending upon what version of TLIB you bought, and how old it is, you may not have all of the protected mode TLIBs.) [20-Aug-1999] _________________________ Q: How will TLIB Version Control help me meet the requirements of FDA regulation 21 CFR Part 11? A: See FDA21CFR11.html [27-Jul-2000] _________________________ Q: I tried to run Configuration Wizard or the 16-bit GUI TLIB, and got a GPF in USER.EXE at 0001:6797. Why did it happen, and what can I do about it? A: This is related to Novell Netware. It happens only with 16-bit Visual Basic programs (like the 16-bit versions of TLIB for Windows), and only on Windows machines which use Novell Netware. We've only seen this under Windows 2000, and do not know whether or not it can happen under other versions of 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: 4) Reboot and start the computer in "Workstation Only" mode (selected at the Novell login screen). Typically, you would do this just to run the TLIB Configuration Wizard. Then, after you exit the Configuration Wizard, you can restart your computer again and let the Novell Netware client load as usual. [5-Feb-2001, 12-Dec-2001]
Last modified: 25-Apr-03 (version 17)
Copyright © 2000-2001, Burton Systems Software.