MUD Clients
WinTin - Historical Windows 3.1 Client
Windows 3.1 TinTin III port with executable, original credits and documentation.
About this resource
Windows 3.1 TinTin III port with executable, original credits and documentation. 00README.WIN explicitly says sources were withheld because some code was used in commercial work. Do not label this package GPL or claim it includes source. The old executable is preserved without execution. Credits and licensing John Miller (WinTin port); Peter Unold (TinTin III) and the contributors named in CREDITS. Historical binary-only WinTin notices; redistribution permission unresolved. Historical package notices apply. No blanket redistribution grant for this complete historical bundle has been established. Do not substitute the current project license for the notices in this release. Licensing review remains required. Compatibility and security warnings Windows 3.1 and compatible WinSock stack. The README reports incompatibility with Trumpet WinSock and documents MCI commands. Original bytes and all included notices are preserved. Historical scripts and client commands may execute local commands or contact old endpoints. Archive integrity verification is not malware clearance or a comprehensive security audit. Mudhaven has not compiled or run this package; modern compatibility is unverified.
Compatibility
Windows 3.1 and compatible WinSock stack. The README reports incompatibility with Trumpet WinSock and documents MCI commands.
A download checksum confirms file integrity, not security or runtime compatibility. Review the source and included documentation before running unfamiliar software.
Attribution stays with the work.
License
Historical binary-only WinTin notices; redistribution permission unresolved
Original Author
John Miller; Peter Unold and TinTin III contributors
Credits
John Miller (WinTin port); Peter Unold (TinTin III) and the contributors named in CREDITS.
Availability here does not replace the original license. Retain copyright notices, contributor credits, and any applicable attribution or notification requirements.
Download integrity
Recorded filenames, sizes, and available SHA-256 checksums for each attachment.