3DCHIPSET
YOUR SOURCE FOR 3D ACCELERATOR INFORMATION
3DCHIPSET / START

3DChipset — The 3D Accelerator Era

Illustrated early PC workbench with a generic graphics card and glowing wireframe scene

3DChipset covered the moment when the video card became the center of PC gaming conversation. From 1999 into the middle of the next decade, this site followed new 3D accelerators, driver releases, firmware experiments, utilities, reviews, graphics APIs, and the arguments that erupted whenever a new board met a familiar benchmark.

Reference mode: this is a historical publication. It carries release records and context, not software, firmware, current support, or live news.

A site for the accelerator crowd

D. Richard Solomon founded 3DChipset as a direct, practical stop for readers trying to understand what was changing inside their PCs. The 1999 welcome called the site a place dedicated to 3D video accelerators and described its role as “the middlemen” for consumers interested in the video-card field. That compact mission expanded quickly. Daily headlines sat beside vendor-organized driver pages, review links, utilities, and discussion boards.

The earliest layout used classic ASP pages such as the 1999–2000 news record. A 2001 merger with Gamers Ammo brought the strapline “Ammo For The Gamer” and an SSI generation represented by the 2001–2002 news page. By late 2002, PHP pages carried the line “Your Source For 3D Accelerator Information,” comments appeared beneath news items, and the driver, utility, BIOS, and forum sections had become distinct parts of the publication.

The hardware race it documented

The names read like a map of the period: NVIDIA RIVA TNT, GeForce, GeForce2, GeForce3, and GeForce4; ATi Rage and Radeon; 3dfx Voodoo; Matrox G400 and Parhelia; S3; PowerVR and Kyro; 3Dlabs; and Intel graphics. These were third-party companies and products covered editorially. Their presence here describes the market of the time and does not imply a support or commercial relationship.

The contest was not only about frames per second. Readers cared about 2D signal quality, texture filtering, full-scene antialiasing, transform and lighting, monitor output, video-in/video-out features, operating-system support, fan noise, power, and whether a driver behaved across the games they actually played. The graphics glossary explains the period vocabulary, while the accelerator timeline places the major families in sequence.

Browse by section

Reading the record safely

Old driver and firmware pages can be valuable evidence even when their binaries should not circulate. Version numbers show the cadence of graphics development; supported-card lists reveal how unified driver families grew; release notes show which features vendors were exposing. Here those pages are presented as documents of the era. Nothing is offered for installation, and no route leads to a driver or BIOS distributor.

For broader historical orientation, the Computer History Museum’s graphics-and-games timeline places the 3dfx Voodoo chip among major computing milestones, while the publication’s own month pages show what enthusiasts were reading day to day. Start with March 2002 or June 2002, then follow the release records deeper into the stack.

How the sections fit together

Each section answered a different question for the same reader. News pages established what had just changed. Driver records fixed a version to an operating system and card family. Utility notes described the controls enthusiasts used to inspect or tune a system. BIOS pages documented the far riskier experiments that circulated around particular boards. Reviews supplied the broader judgment: whether those parts, tools, and releases produced a machine that was enjoyable and dependable in everyday use.

Read together, those layers show why graphics coverage became so detailed. A board was never only its processor name. Memory configuration, cooling, display output, software support, game compatibility, and the maturity of its driver branch all affected the experience. This reference keeps those relationships visible while leaving obsolete binaries and hazardous procedures out of the publication.