Match user intent

The SocketWrench Freeware Edition (historically developed by Catalyst Development Corporation) is a lightweight, 32-bit ActiveX control (.ocx). It simplifies Windows Sockets (Winsock) programming by abstracting the complex standard Windows Sockets API. It enables developers to build both client and server applications over TCP/IP and UDP protocols without a steep learning curve. Core Features

Protocol Flexibility: Fully supports both TCP (connection-oriented) and UDP (connectionless/datagram) networking protocols.

Dual Operations: Allows toggling between synchronous (blocking) mode, which waits for data to process, and asynchronous (non-blocking) mode, which triggers events when data arrives.

Broad Compatibility: Integrates into legacy development tools such as Visual Basic 6.0, Microsoft Office VBA, and Delphi.

Zero Royalty Fees: Permits the distribution of compiled freeware, shareware, or commercial software binaries with no runtime fees.

RAS Dialer: Includes a bonus Remote Access Services (RAS) control to initiate and manage dial-up connections directly from code. Implementation Guide

To implement the SocketWrench Freeware control, you must place the .ocx component onto your development form and handle its properties and methods. 1. Fundamental Properties

AutoConnect: Set to True to connect instantly when a remote host address is specified.

Blocking: Set to True for synchronous execution or False for asynchronous, event-driven networking.

PeerAddress / RemoteHost: The target server IP address or domain name.

PeerPort / RemotePort: The standard port number designated for the traffic (e.g., 80 for HTTP). 2. Primary Methods

Connect(): Initiates a client handshake with the specified remote host.

Listen(): Switches the control into a server state to await incoming connections.

Accept(): Programmatically accepts an incoming client connection queue.

Read(): Extracts incoming text or byte streams from the socket buffer.

Write(): Transmits text, lines, or raw binary arrays across the established socket.

Disconnect(): Safely closes the session and releases the system socket handle. 3. Core Implementation Architecture

For an asynchronous implementation, your application’s logic flows through event handlers:

[Form Load] ──> Set RemoteHost & RemotePort ──> Call Connect() │ ┌────────────────────────────────────────────────────┘ ▼ [OnConnect Event] ──> Triggered when connection completes successfully │ ├─> [OnRead Event] ──> Data arrived ──> Call Read() method to process data │ └─> [OnClose Event] ──> Connection broken ──> Clean up local resources Use code with caution. Modern Ecosystem Alternatives

The original standalone Freeware Edition (such as version 6.0) has moved to legacy status. Developers looking for current solutions typically migrate to the broader SocketTools Platform. The modern iterations support secure TLS 1.⁄₁.3 encryption, native 64-bit architectures, and direct .NET assemblies.

If you are working on a specific legacy system integration, consider looking up discussions on VBForums to see how other engineers map old SocketWrench components to current development requirements.

If you would like to proceed with setting this up, please let me know your development environment (e.g., VB6, VBA, C++), whether you are building a client or a server, and if you need a code template to handle data transmission.

Thread: Socketwrench 3.5 or 3.6 Freeware edition – Dynazip libs