Dec 292017
 
Patch for BC++ 3.1 TLIB Utility. Fixes "BAD OBJECT FILE RECORD" error. This will fix Rogue Waves TOOLS.H++ v5.x DLL bug. From Borlands BBS.
File TLIB30.ZIP from The Programmer’s Corner in
Category C++ Source Code
Patch for BC++ 3.1 TLIB Utility. Fixes “BAD OBJECT FILE RECORD” error. This will fix Rogue Waves TOOLS.H++ v5.x DLL bug. From Borlands BBS.
File Name File Size Zip Size Zip Type
README 1822 796 deflated
TLIB.EXE 37220 20650 deflated

Download File TLIB30.ZIP Here

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 when
the Borland C++ 3.1 linker processes library files (.lib files) generated
from the Borland C++ 3.1 tlib utility. The problem is that in a few rare
cases, the linker reports "bad object module" when processing the .lib file.
The problem is resolved by using the Borland C++ 3.0 tlib utility contained
in this archive.

WHO SHOULD USE THIS VERSION OF TLIB
===================================
Few people will require the older version of tlib contained in this
archive. It is recommended that if you are not experiencing any problems
with the version of tlib shipped with Borland C++ 3.1 that you continue
to use that version. If you are getting a "bad object module" error message
from 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 other
valid reasons. Be sure that the objs you have placed into your library
were not compiled by a version of the compiler which is later then the
linker. Older versions of the linker will not understand the debug
information 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 linker
looks in the current directory for a .lib file before searching the lib search
path. 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.



 December 29, 2017  Add comments

Leave a Reply