Yep, I was thinking the same thing many times, but i'm on the trail like a houndog now. It's 3.1 and it's out there, if you'll go to the org site after searching for 'Borland C++ 3.1'. So is 5.3 but it has version 3 TASM and if I used 5.3, TASM is going to be under the BC5 path. Makefile has borlandc as part of the path and I read about that connection in the 4.5 text files on my CD finally pertaining to proper upgrading which appears to be wholesale directory deletion until you get to 4.5 and then it's a file list to back up, do this, and do that. Like being tossed into the deep end of the pool to learn how to swim, I think the 4.1 version I got on the web has been stepped on and just doesn't work right. Kinda odd version 5.3 is still using version 3 TASM to me. It also has TASMX for Windows DOS box and from there they go to TASM32 but it can still build 16 bit code if you link it with TLINK, which also comes in 32 bit flavors if that is your bent.
As to my problems with no TASM in 4.5, well that's because I installed the run from CD files which don't do the 16 bit stuff. Needed to navigate to the folder where CMD16.PAK is at and run that install executable and then I would have gotten TASM just like that. I see 5.3 is built exactly the same way too. And I might still do that after I clean house and put 3.1 on there all alone to do this with. Jeeze, if I can do this is there even a need to post it when done?
Further info here for those stuck at too high a version:
A) Installing over previous versions of Borland C++.
As a general rule, it is not recommended that you install
Borland C++ 4.52 over any version earlier than 4.51.
It is recommended that you delete the Borland C++ directory
tree (BORLANDC if you have Borland C++ 3.1, BC4 if you have
Borland C++ 4.0, or BC45 if you have Borland C++ 4.5) prior
to installing. In addition, you will need to delete the
following files in the Windows directory (WINNT under NT, WIN95
under Windows 95): owl.ini, bcw.ini, borhelp.ini,
openhelp.ini, winsight.ini, workshop.ini.
If you are installing over Borland C++ 4.0 or greater,
you need to backup the RTL BIDS and OWL .DLLs prior to
deleting the directory tree. Otherwise, any applications which
need to link these libraries at runtime will need to be rebuilt.
If you are installing over a previous installation of
Borland C++ 4.51 or 4.52, you need to delete the Group file
for Borland C++ (Under Windows 3.1, this is
WINDOWS\BC45.GRP). The installation program cannot
properly create this file if it already exists on your
I got that error prone 4.1 TASM in a version 5 bundle, and then found a better 5.3 bundle. Kinda curious what's in 4.5 now, but that will have to wait until after some sleep and some housecleaning.