Hiring, or looking for work?Employers: post a job on Far Reach, compare proposals, and fund a milestone that is released when you accept the work. Freelancers: join Far Reach and get hired for what you do best.Post a job on Far Reach →Join as a freelancer →
Advertisement
Buy and Sell your new and used items in Nouhata.com
Download the SDK, documentation, turnkey business packages, checksums, and separately released KCPP/ICPP compiler suite.
Windows x64 development release
RayyanCAD - Schematic capture
Create and edit schematic pages with a floating parts palette, wires, buses, labels, direct printing and PDF output. Includes the InternetSQL 1.25 SDK, an installer and a detailed offline manual with parts-library tutorials.
Binary-only developer preview: native payment-state machine and Windows PC/SC reader diagnostics. No Python dependency. Does not yet authorize card payments.
Existing InternetSQL DLL and libraries, public headers, shells, provider and MCP components, Python wrapper, C/Python/SQL examples, manuals, and offline tests.
New in this drop (24 October 2026): a fix for INSERTs and lookups that never returned. Once a table’s index outgrew one 16 KB node — about 300 rows for a char(36) primary key, sooner for wider keys — rebuilding it wrote a root entry that pointed back at itself, and the next INSERT or lookup through that index spun at 100% CPU for ever. Every earlier 1.25 build has this, on Windows and Linux. The rows were never lost: an existing database heals when it is opened with this engine after its table file has changed since the index was last written. Also fixed: a logout inside the default database could blank the server’s database path, after which the server refused every client until it was restarted, and an over-long database name is now refused instead of being cut off.
Since 6 October 2026: SQL triggers and stored procedures.CREATE TRIGGER … AFTER INSERT | UPDATE | DELETE … FOR EACH ROW runs a body once per affected row and reads it through OLD.<column> and NEW.<column>, so an audit trail records that 5000.00 became 5500.00 for a named employee rather than that something changed. FOR EACH STATEMENT runs once per statement instead. CREATE PROCEDURE saves a sequence of SQL under a name and CALL runs it, including from inside a trigger body. LIST TRIGGERS and LIST PROCEDURES show what is defined, and the definitions are readable from the trigdefs and procdefs tables. Four runnable examples ship in examples/triggers/, and a new manual, Triggers and Stored Procedures, is in the SDK and readable online. Two things it states plainly rather than hiding: BEFORE triggers are stored and do not run in this release, so a trigger cannot yet refuse a write; and because the engine has no statement rollback, a failing trigger body does not undo the write that fired it — it reports on a line beginning TRIGGER FAILED, and that line is the signal. The drop now also carries LICENCE.txt and COPYRIGHT: free of charge, free to redistribute, with the examples and headers free to copy and modify.
An IEEE 1666-2023 SystemC simulator with TLM-2.0, plus power domains, DVFS, power gating, power states and energy per transaction.
Version: 1.0.1 (Windows x64) · Licence: free of charge, including commercial use
The simulator library for g++ and Visual C++, the tsystemc command line and MCP server, the host DLL, the programmer guide, and examples from a first counter to a power-aware SoC teaching project.
Documentation, public headers, examples and browsable manuals. TUWA-RTOS also carries the prebuilt kernel libraries; the KCPP and ICPP archive is documentation only, without the compiler binaries.
TUWA-RTOS
The prebuilt kernel library for arm64, RISC-V, x86-64 and x86-32, the public headers, API documentation, build and porting guides, BSP guidance and module documentation. Free to use, link and redistribute unmodified - see LICENCE-BINARY.txt in the archive; the headers, examples and board support sources are permissively licensed, because porting to a new board means editing a BSP.
Download the adjacent SHA-256 file and verify the archive before opening it. Evaluate the software with your own data, security requirements, workload, and provider before production deployment.