Documentation

Docs

How to install and use the drivers, how they work, and how to help. Where the project repository already documents something in depth, these pages summarise it and link to the source.

Start here

Getting startedWhat Velocity9x is, what you need, and the safe order of steps to try it on a Windows 98 machine or virtual machine.
InstallationInstall Velocity9x on Windows 98 with Have Disk, verify the first boot, and recover with Safe Mode if the desktop does not come back.

Using the drivers

Supported hardwareHow Velocity9x groups cards into families, what "tested" and "recognised" mean, and where to find each card's results.
TroubleshootingFixes for common Velocity9x problems, from a 16-colour first boot to games that need a different Direct3D interface or colour layout.
Known limitationsWhat Velocity9x does not do yet, by interface, and the open issues in the current release.

Under the hood

ArchitectureHow Velocity9x is put together, from the 16-bit display driver and 32-bit mini-VDD to the shared render core behind Direct3D, OpenGL, Glide and 3DCIF.
Driver developmentBuild Velocity9x from source with Open Watcom v2 and the Windows 98 DDK, run the host tests, and work in 86Box.

Get involved

How to contributeThe ways to help Velocity Drivers, from a hardware survey or test report to lending a machine through remote help or sending code.
Lend a machine with remote helpInstall the V9x Remote Agent, switch on remote help, and let the developer work on your Windows 9x or 2000 machine over the Internet, safely and only while you choose.
Hardware testing and bug reportsHow to report a Velocity9x result with Send report, what diagnostic files to include, and how to run the hardware survey on an unsupported card.