titanfyre

I maintain Virtual Display Studio for Windows: one 1080p60 virtual monitor, explicitly connected by your app and removed when its owner closes. Win11/GPU qualification pending; OEM terms by quote. titanfyre/Virtual-Display-Studio AI-assisted.

Building a Windows remapper or test tool? I've added demo/evaluation driver sources, build instructions and file-specific licenses to my SDK projects. Commercial driver terms stay separate. Browse input, virtual-device and diagnostics APIs: titanfyre/Titan-Input-Tools

I develop Virtual Storage Fault Lab for Windows QA: fail every Nth matching read/write on its 64 MiB RAM disk. Physical drives aren't targets. MIT app/SDK; private driver, OEM terms by quote. titanfyre/Virtual-Storage-Fault-Lab AI-assisted.

Building a Windows remapper or device-testing app? I maintain C++ SDKs for physical input capture and virtual USB devices. Evaluate the matching signed demos first; business/OEM licensing is agreed per integration. titanfyre/Titan-Input-Tools #Windows #Cpp

My existing Windows tools and SDK examples are listed here: physical/virtual input, device testing, networking, media and diagnostics. Check each README for setup, licensing and tested scope; some are engineering previews. titanfyre/Titan-Input-Tools

Custom Windows kernel driver development - EUR 100 for an agreed small scope Need a small Windows kernel driver for a peripheral, a virtual device or a test setup? I offer custom development for EUR 100, paid by PayPal or Stripe, after we agree on the exact scope. The work is AI-assisted, with final review and finishing by me. For a small, agreed task, I aim to have the implementation ready within a few hours. Microsoft signing goes through Partner Center and depends on acceptance and processing, so that timing is separate. Some of my existing projects: TitanCSA/Interceptor-Keyboard-Mouse TitanCSA/Vdevice All my tools: titanfyre/Titan-Input-Tools If you have a legitimate use case, reply with what the driver should do, your Windows version, and the device model or protocol. Please leave private details out of public comments. I'll check whether it fits the EUR 100 scope before we agree to proceed.

Inject bounded read/write errors into a 64 MiB Windows lab disk (C++17) I maintain Virtual Storage Fault Lab for testing how Windows software handles storage I/O errors. A private Storport driver exposes one disposable 64 MiB RAM-backed disk; the native UI, CLI and two-file C++17 SDK control a fault policy on that disk. Choose a sector range, read/write direction and every Nth matching request to fail. For example, fail every fourth matching read. Windows can retry requests, so that isn't a promise that exactly every fourth application call fails. Changing a policy doesn't generate a workload or format a disk. Use disposable fixtures: injected errors can make a mounted lab filesystem unusable. The SDK accepts no physical-drive path. The validation notes document Windows 10 x64 VM installation/runtime/removal tests, including Driver Verifier. Windows 11, Secure Boot/HVCI and broader deployment qualification remain pending. Public application/SDK/installer source is MIT. The signed private driver has separate evaluation/commercial terms; this evaluation has no enforced trial timer or online activation. Production/OEM integration and support are separate offerings. The README has the exact tested scope and installation details.

Input Replay Lab: Windows keyboard/mouse timelines with bounded replay (C++17) I maintain Input Replay Lab, a native C++17 tool for experimenting with repeatable Windows input QA. Choose one keyboard or mouse, explicitly record its events, inspect the timeline, then replay it once to a selected device of the same family. Timelines can be saved as JSON or exported as CSV. The app records locally, only after you choose Record. Stop cancels replay and releases its held keys/buttons. Timestamps are taken when the app receives events; replay reports submission scheduling lateness, not end-to-end input latency. The application source is MIT. Live capture/replay uses my Interceptor Keyboard & Mouse driver: the bundled signed demo needs administrator rights and has a one-hour allowance per Windows kernel boot. Kernel source and unrestricted production licensing are separate. The public tests cover offline serialization, cancellation and fake-transport replay. Physical-device routing and behavior in your receiving app still need testing on your target system; see the README for scope and limits.

I made native C++ tools for working with Windows input devices I build Windows tools for people writing remappers and device-test software. The main distinction is changing input from a physical device versus creating a new virtual one. Interceptor Keyboard & Mouse handles physical keyboards and mice separately: TitanCSA/Interceptor-Keyboard-Mouse Interceptor is the combined keyboard/mouse/controller edition using Get_Input_With_Timeout()/Send_Input(). Existing apps using that API should keep its matching SDK and driver: TitanCSA/Interceptor Interceptor Gamepad & Controller focuses on physical controllers, with examples for button swaps, inversion, deadzones and response curves: TitanCSA/Interceptor-Gamepad-Controller Vdevice creates virtual USB devices from descriptors and reports, with keyboard, mouse and controller examples: TitanCSA/Vdevice Windows Input Bridge is a separate combined edition using Read()/Write() and move-only batches. Choose it to evaluate that API; it isn't a drop-in Interceptor update. Live hardware validation of this new edition is still pending: StrikeFound/Windows-Input-Bridge I also maintain smaller tools for input replay, HID fixtures, controller reports, driver diagnostics and other Windows integrations. This directory lists their scope and whether they're an evaluation or source preview: titanfyre/Titan-Input-Tools The input projects target Windows 10/11 x64 and include C++ SDKs and examples. User-mode source is MIT; kernel source is private, with separate binary terms. The public input-driver demos require administrator rights and last one hour per Windows kernel boot. Each edition needs its matching driver and SDK; controller compatibility depends on the model and connection. For a full input-driver version without the demo limit or commercial/OEM licensing, add titancsa on Discord and mention the project and intended use. Pricing and terms are discussed directly.

Windows driver diagnostics with HTML/JSON reports - Driver Readiness Inspector I've been working on a small Windows tool that puts device and driver details in one place: PnP problem codes, package versions, associated services and signing observations. It exports a local HTML or JSON report. Repo: titanfyre/Driver-Readiness-Inspector It's a native C++ application for Windows 10/11 x64, with MIT-licensed source. No installation, extra driver or admin prompt is needed. It reads system state; it doesn't certify whether a driver is safe or compatible. I'd be interested in feedback on the report format, especially whether unknown fields and signing results are clear.