Files
TeslaRel410/BORLAND/INSTALL/SQLLINKS/REDIST.TXT
T
CydandClaude Fable 5 63312e07f9 source410: literal 4.10 source reconstruction + BC++ 4.52 fleet toolchain archived
- BORLAND/: Borland C++ 4.52 (chosen over 4.5 by byte-match: CODE/RP/CW32.LIB
  is identical to 4.52's install lib). BCC32/TLINK32/TLIB/MAKE run natively on
  Win11; CODE/BT/OPT.MAK is the shipped BTL4OPT.EXE's exact flag recipe
  (extender = Borland PowerPack DPMI32, not Phar Lap TNT).
- restoration/source410/: the literal 1995-form reconstruction of the missing
  BT game source (never mixed into CODE/). Round 1-3 state:
  * 6 of 10 surviving original TUs COMPILE CLEAN under the period toolchain
    (BTMSSN, BTCNSL, BTSCNRL, BTTEAM, BTL4MODE, BTL4ARND) - first builds
    since 1996.
  * BT_L4/BTL4APP.CPP pilot reconstruction: 12/12 functions, Fail() lands on
    its binary-recorded line 400 exactly.
  * BT/BTCNSL.HPP: console wire IDs recovered from the binary's ctors
    (Killed=9, Damaged=10, ScoreUpdate=13, DeathWithoutHonor=15 [T1];
    TeamScore=12 flagged [T4]).
  * MUNGA/: 8 engine-header backfills back-dated from the BT412 WinTesla tree
    (VDATA numbering decomp-verified; AUDREND's OpenAL-era virtual removed -
    the period compiler is the drift detector).
  * Tooling: backdate.py (WinTesla->1995 header transform), compile410.sh
    (per-TU verification sweep under authentic OPT.MAK flags).
  * README: corrected roadmap - MECH.HPP is the capstone grown with the mech
    TU reconstructions; BTREG.CPP green = the header-family milestone.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-19 07:33:26 -05:00

148 lines
4.2 KiB
Plaintext

BORLAND SQL LINK DEPLOYMENT
==============================================
The Borland SQL Links setup disks may be used for redistribution
as long as a following steps are followed:
1. Remove REDIST.TXT from the disk1.
2. Remove the line beginning with REDIST from the INSTALL.INI.
3. (optional) Remove the line beginning with REDIST from the FILELIST.TXT.
NOTE: In addition to the SQL Links files, client/server
applications require client files for interface to communication
protocols such as TCP/IP. Refer to your server documentation.
Redistributables for SQL Link Software
-------------------------------------
Licensed, registered users of the Client/Server version of this
product may redistribute the below-listed files ("SQL Link
Software Redistributables") with programs created with this
product, subject to all of the terms and conditions of the
Additional License Terms for Development Products. Note that
the SQL Link Software Redistributables can only be redistributed
for the specific purpose of executing end-user SQL Link Software
applications created with the Client/Server version of this
product. Although SQL Link Software applications developed with
Client/Server can be redistributed to an unlimited number
of servers for use by end-users, you may not "redistribute" or
otherwise share the SQL Link Software with other developers for
creating SQL Link Software applications.
THE SQL LINK SOFTWARE REDISTRIBUTABLES CONTAINED IN THIS PRODUCT
CANNOT BE CONCURRENTLY USED BY MORE THAN ONE DEVELOPER FOR
CREATING SQL LINK SOFTWARE APPLICATIONS.
Informix
--------
SQLD_INF.DLL
SQLD_INF.HLP
SQL_INF.CNF
SQLD_IN5.DLL
SQLD_IN5.HLP
SQL_IN5.CNF
LDLLSQLW.DLL
ISAM.IEM
OS.IEM
RDS.IEM
SECURITY.IEM
SQL.IEM
ZRDSTERM.IEM
Oracle
------
SQLD_ORA.DLL
SQLD_ORA.HLP
SQL_ORA.CNF
ORA6WIN.DLL
ORA7WIN.DLL
COREWIN.DLL
ORAWE850.LD
NWIPXSPX.DLL
NWNETAPI.DLL
Sybase and Microsoft SQL servers
--------------------------------
SQLD_SS.DLL
SQLD_SS.HLP
SQL_SS.CNF
W3DBLIB.DLL
DBNMP3.DLL
SYDC437.LD
SYDC850.LD
NWIPXSPX.DLL
NWNETAPI.DLL
3. InterBase SQL Link and Client Files
=======================================
The following files are redistributable under the same conditions
as listed above in the section titled "Redistributables for SQL
Link Software".
SQLD_IB.DLL
SQLD_IB.HLP
SQL_IB.CNF
CONNECT.EXE
CONNECT.HLP
GDS.DLL
REMOTE.DLL
INTERBAS.MSG
IUTLS.DLL
DSQL.DLL
NWIPXSPX.DLL
NWCALLS.DLL
NWNETAPI.DLL
TCP/IP Interface
----------------
(Redistributable only as part of an InterBase application)
The following files provide InterBase client applications their
interface to Winsock 1.1 compliant TCP/IP products.
MVWASYNC.EXE
VSL.INI
WINSOCK.DLL
MSOCKLIB.DLL
JSB TCP/IP VSL for Windows
--------------------------
(Redistributable only as part of an InterBase application)
For TCP/IP products that are not Winsock 1.1 compliant, InterBase
client applications will require one of the following files.
During installation, you will be prompted to select the TCP/IP
stack for which to install support. If the deployed application
needs to support a different TCP/IP stack, you must copy the
corresponding file from the installation disks.
File For...
---- ------
M3OPEN.EXE 3Com 3+Open TCP
Microsoft LAN Manager
Digital Pathworks for DOS
M3OPEN.DLL 3Com 3+Open TCP Version 2.0
MBW.EXE Beame & Whiteside TCP/IP
MFTP.EXE FTP PC/TCP
MHPARPA.DLL HP ARPA Service for DOS
MNETONE.EXE Ungermann-Bass Net/One
MNOVLWP.DLL Novell LAN WorkPlace for DOS
MPATHWAY.DLL Wollongong Pathway Access for DOS
MPCNFS.EXE Sun PC NFS
MPCNFS2.EXE Sun PC NFS v3.5
MPCNFS4.DLL Sun PC NFS v4.0
MWINTCP.EXE Wollongong WIN TCP\IP for DOS
Other communication protocols
-----------------------------
The InterBase workgroup server for NetWare supports Novell
SPX/IPX protocol. with the following client files: NWIPXSPX.DLL,
NWCALLS.DLL, and NWNETAPI.DLL The InterBase Workgroup Server for
Windows NT supports Microsoft Named Pipes protocol. No additional
client files are required to support Named Pipes, but the client
machine must have Microsoft LAN Manager or Windows for Workgroups
3.1.1 installed.