Velocity9x goals and some (mostly) ranting
· 6:30
The goals of the Velocity9x project and why it exists, with 3DMark 99 Max running on the GMA 950 netbook. If you are interested in helping, this is where to start.
Open source
Most of what Velocity9x runs on came from someone testing their own machine. Real hardware reports are the most valuable thing you can contribute: every one of them moves a card, a game or a fix forward.
Install a release on a machine you can recover, run something, and send what happened, good or bad, with Send report.
How to report →Card not supported? The read-only DOS survey collects what a new driver family is built from.
Run the survey →Install the V9x Remote Agent and switch on remote help, so the developer can work on your hardware directly. You can pause it at any time.
Enable remote help →Real captures and measured numbers, with the card, machine, driver version, resolution and settings, improve the games pages.
What to include →Velocity9x is GPL-3.0-or-later, built with Open Watcom v2 and the Windows 98 DDK.
Build from source →Bugs, test reports, survey results and remote-help requests all go to the Velocity9x issue tracker.
Issue tracker →Remote help
The V9x Remote Agent runs on Windows 95, 98, Me and 2000. With remote help switched on, the developer can run programs, see the screen, use the keyboard and mouse, copy files and restart the machine over the Internet, as if it were on their desk.

· 6:30
The goals of the Velocity9x project and why it exists, with 3DMark 99 Max running on the GMA 950 netbook. If you are interested in helping, this is where to start.
· 2:43
The test bench used for Velocity9x development: the machines and period PCI cards, and the V9x Remote Agent, the open-source remote-control tool that lets an AI coding agent drive a Windows 98 machine to automate and speed up testing.