Contents of the README file

Borland C++ "bad object module" workaround for TLIB.EXE

WHAT THIS ARCHIVE ADDRESSES===========================Borland is currently looking at a problem which sometimes occurs whenthe Borland C++ 3.1 linker processes library files (.lib files) generatedfrom the Borland C++ 3.1 tlib utility. The problem is that in a few rarecases, the linker reports "bad object module" when processing the .lib file.The problem is resolved by using the Borland C++ 3.0 tlib utility containedin this archive.

WHO SHOULD USE THIS VERSION OF TLIB===================================Few people will require the older version of tlib contained in thisarchive. It is recommended that if you are not experiencing any problemswith the version of tlib shipped with Borland C++ 3.1 that you continueto use that version. If you are getting a "bad object module" error messagefrom the linker on .lib files which the Borland C++ 3.1 tlib utility created,then try the tlib.exe in this archive.

OTHER CAUSES OF "BAD OBJECT MODULE"===================================It is possible to receive the bad object module error message for othervalid reasons. Be sure that the objs you have placed into your librarywere not compiled by a version of the compiler which is later then thelinker. Older versions of the linker will not understand the debuginformation produced by newer versions of Borland C++. For example,tlink 4.0 which ships with Borland C++ 2.0 will report "bad object module"for objs generated by Borland C++ 3.0 or 3.1. Also, be aware that the linkerlooks in the current directory for a .lib file before searching the lib searchpath. So the error can occur when you have a file with the same name as your.lib in the current directory, but that file is not a valid .lib file.