Graphics Utility Reference
3DChipset’s utility section catalogued the small programs enthusiasts used to expose driver options, adjust clocks, manage displays, create per-game settings, remove old driver traces, and support graphics APIs. This is a description of those tools and categories, not a software library.
How the utility pages were organized
The 2001 introduction explained four fields. “Chips Supported” identified compatible graphics families, sometimes at a series level rather than by every retail board name. “Dates of Utilities” used written month names to reduce confusion between American and international date order. “OS Supported” helped readers distinguish Windows releases. “Categories” grouped tools by what they changed: game software and fixes, overclocking, card tweaking, display functions, or cleanup.
That taxonomy mattered because two utilities aimed at the same graphics family could do very different things. One might merely reveal a hidden control-panel option. Another might alter clock settings. A third could remove driver remnants after an uninstall. Their risk, permanence, and usefulness were not interchangeable.
Representative utilities
- PowerStrip
- A broad display and graphics-card utility associated with resolution, timing, refresh, and tuning controls across several vendors.
- CoolBits
- A small NVIDIA-oriented tweak associated with exposing additional driver control-panel settings, especially clock controls.
- RivaTuner
- A detailed tuning and diagnostic utility discussed across NVIDIA hardware generations.
- RadLinker
- An ATi-oriented tool for linking graphics settings with individual applications.
- Driver Cleaner
- A cleanup utility intended to remove remnants from previous graphics-driver installations.
- ATI Tray Tools
- A compact settings and profile utility for Radeon-era systems.
- GLSetup
- An older effort to help Windows users obtain an OpenGL driver appropriate to supported graphics hardware.
Support meant community knowledge
The original page directed readers toward the 3DChipset forums when a utility caused trouble and suggested contacting a utility’s developer. The modern site carries neither route. The useful history is that support was distributed: site editors catalogued tools, developers maintained them, and readers compared results in forums. No single index could guarantee that a tweak would work on every board revision and operating-system combination.
Tweaking versus firmware
Most utilities acted through a running operating system or driver, making them conceptually different from a video-card BIOS change. That did not make aggressive tuning harmless, but it usually made the layer easier to understand and reverse than firmware. The BIOS history explains why firmware material receives a stronger warning.
Using the reference today
Read these names as a guide to the period’s concerns: refresh-rate control on CRTs, hidden driver switches, per-game profiles, overclocking, driver replacement, and OpenGL availability. Do not assume that old executables are trustworthy, compatible, or useful now. The site intentionally provides no route to acquire them.
For the API context behind tools such as GLSetup, the Khronos OpenGL overview describes OpenGL as a cross-platform graphics API. For the community categories that surrounded these tools, visit the forum history.
Utilities as diagnostic instruments
The best use of a period utility was often observational. It could report a clock value, expose a driver option, show refresh-rate behavior, or help a reviewer reproduce a setting. That role is easy to overlook because enthusiast discussion frequently emphasized overclocking. In practice, repeatable configuration was just as important to credible comparison.
Utility names and functions are preserved here so old reviews and forum posts remain intelligible. The descriptions do not establish present-day safety, authenticity, or compatibility. Many tools expected operating systems, driver models, permissions, and hardware interfaces that no longer resemble a current PC. This reference supplies no executables, mirrors, activation material, or instructions for bypassing safeguards.
The safest modern use of the list is bibliographic: it helps decode tool names mentioned in period articles and explains which part of the graphics stack each utility attempted to expose.