Building a 2002 LAN Party PC: GeForce 4 Ti + Athlon XP

Building a 2002 LAN Party PC: GeForce 4 Ti + Athlon XP

Building a period-correct 2002 LAN party PC comes down to four anchor parts: an Athlon XP 2200+ on a Socket A board (the Abit NF7-S is the community favorite), a GeForce 4 Ti 4600, an Audigy-class sound card, and a Cat5e-ready NIC. Install Windows XP, then load drivers in the order chipset → GPU → sound → NIC. Done right, it runs UT2003, Quake III, Counter-Strike 1.6, and Battlefield 1942 at the frame rates that defined the era.

Editorial intro (~280w) — 2002 LAN culture context

If you carried a beige tower across a parking lot in 2002, you remember the ritual: the folding table, the power strip daisy-chain that tripped the breaker, the guy with the unmanaged hub who slowed everyone down, and the satisfying thunk of a CRT going onto a card table that was never rated for it. The 2002 LAN party PC build is a snapshot of a very specific moment — DirectX 8 was the target, AGP 4x was standard, DDR had just gone mainstream, and the GeForce 4 Ti line had landed in February 2002 to define the high end. A 2002 gaming PC was fast enough to run Unreal Tournament 2003 and Battlefield 1942 at the resolutions a 19-inch CRT could actually display, and cheap enough that a teenager with a summer job could assemble one.

This is a full build log, not an event recap. Where our earlier piece on the 2002 Athlon XP + GeForce 4 Ti era focused on the LAN scene itself, this one is the parts table, the install order, and the network checklist — the thing you'd actually print and tape inside the case. The goal: a machine that boots Windows XP, posts a clean ~1024×768, and holds a steady frame rate across the four games that mattered at a 2002 BYOC. Per AnandTech's 2002 platform coverage, the Socket A ecosystem of that year was unusually builder-friendly: mature nForce2 chipsets, dual-channel DDR, and a deep used-parts market today. That combination is why an Athlon XP build remains the sane starting point for anyone recreating a 2002 LAN rig now.

Key Takeaways

• A period-correct 2002 LAN party PC build centers on an Athlon XP 2200+, an Abit NF7-S (nForce2) motherboard, a GeForce 4 Ti 4600, and an Audigy-class sound card.
• The GeForce 4 Ti 4600 launched in February 2002 as the era's flagship; per TechPowerUp's GPU database it pairs naturally with AGP 4x boards and DirectX 8.1 titles.
• Driver order matters: chipset first, then GPU, then sound, then NIC. Installing out of order on Windows XP is the classic source of stuttering audio and flaky networking.
• For the 2002 gaming PC workload — UT2003, Quake III, CS 1.6, Battlefield 1942 — period reviews put a Ti 4600 build comfortably above 60 fps at 1024×768 in all four.
• No Audigy 2 ZS on hand? The modern Creative Sound Blaster Audigy FX is the budget retrofit path — PCI, EAX-capable, and still sold new.
• Pair the build with a 19-inch CRT at 1024×768@85 Hz for the authentic look and the input latency the games were tuned around.

Parts list: Athlon XP 2200+, NF7-S motherboard, GeForce 4 Ti 4600, Audigy 2 ZS

The shopping list for an authentic 2002 athlon xp build:

If you're servicing one of these from a modern machine — pulling the old IDE drive to image it, say — a USB bridge like the Unitek SATA/IDE to USB 3.0 Adapter or the Vantec CB-ISATAU2 makes the drive readable on a current PC without opening the retro box.

Period-correct Windows XP install + slipstream

The era-appropriate OS is Windows XP — Home or Professional, RTM through SP1 if you want strict 2002 accuracy, though most builders slipstream SP3 for USB and stability and call it close enough. The slipstream itself is the one prep step worth doing before you touch the hardware:

1. On a modern PC, use nLite (or RVMintegrator for a pure-2002 toolchain) to fold your service pack of choice into the XP source files.
2. While you're in there, integrate the nForce2 chipset drivers and the IDE/SATA controller driver. This is what spares you the F6-floppy dance.
3. Burn the result to a CD-RW.
4. In the NF7-S BIOS, set the boot order to CD first, enable the onboard devices you'll use (LAN, audio off if you're adding the Audigy), and confirm the IDE drive is detected.
5. Install. XP on this hardware lands in well under 30 minutes.

Activation is the gotcha: a genuine 2002-era retail key is the clean path. After install, do not let Windows Update auto-install a display driver — you want to control the GPU driver version yourself, which the next section covers.

Network stack for 2002: Cat5e, hubs vs switches, BYOC checklist

The whole point of this machine is to plug it into other machines. The 2002 reality:

• Cabling: Cat5e was already the norm by 2002 and runs 100 Mbit without complaint. Make your own runs or buy pre-made; either is period-correct.
• Hubs vs switches: This is the one place where "period-correct" and "good idea" diverge. Plenty of 2002 LANs ran on cheap 10/100 hubs — and everyone on a hub shares one collision domain, so one person's torrent (or one bad NIC) tanked the room. A small 8-port 10/100 switch was the upgrade everyone wanted. Use a switch. Nobody at the table will know, and nobody will miss the lag.
• Protocols: TCP/IP over a flat 192.168.x.x range. IPX/SPX is the deep-cut throwback some 2002 titles still spoke; install it from the XP CD only if a specific game needs it.
• BYOC checklist to tape inside the case lid:
• Power cable + a known-good power strip (don't trust the host's)
• Cat5e patch cable, 10–25 ft
• CRT + video cable + the monitor's power brick
• Keyboard, mouse, mousepad (a hard pad — optical mice of 2002 hated cloth)
• Headphones (be a good neighbor)
• Game discs + CD keys written on the sleeves
• A small switch if you're the type who brings infrastructure
• Sharpie, gaff tape, a multi-tool

Driver order: chipset, GPU, sound, then NIC

This is the section that separates a build that "just works" from one that crackles, stutters, and drops off the LAN. On Windows XP, install in this order and reboot when prompted between each:

1. Chipset first — nForce2 platform drivers. This installs the AGP GART driver, the IDE/SATA driver, and the memory controller bits. Everything else assumes these are in place. Skipping this is the #1 cause of "my GeForce 4 runs like a GeForce 2."
2. GPU second — NVIDIA Detonator/ForceWare. For a 2002-authentic feel, the Detonator 40-series (40.72) is the period sweet spot for the GeForce 4 Ti; ForceWare 45.23 is the slightly later "just works" pick. Install, reboot, then set 1024×768@85 Hz in Display Properties.
3. Sound third — Audigy drivers. Whether it's an Audigy 2 ZS or the retrofit Audigy FX, install its package after the chipset so the PCI bus enumeration is stable. Reboot.
4. NIC last. Onboard nForce2 LAN gets its driver from the chipset package, but verify it in Device Manager and let Windows finish before you plug into the switch. An add-in 3Com/Intel card gets its own driver here, dead last.

Do it in this order on a fresh XP install and the machine is LAN-ready in one sitting. Do it out of order and you'll be reformatting at 11 PM while everyone else is fragging.

Game tests: UT2003, Quake III, CS 1.6, Battlefield 1942 — frame rates

What does an Athlon XP 2200+ / GeForce 4 Ti 4600 build actually deliver across the 2002 LAN canon? Per the period reviews this rig was benchmarked against — AnandTech and Tom's Hardware GeForce 4 Ti coverage from 2002 — at the era-standard 1024×768:

• Quake III Arena — utterly trivial for this hardware. Period benchmarks routinely show this class of card well past 200 fps at 1024×768; the engine is CPU-bound long before the Ti 4600 breaks a sweat. At a LAN this is your "lock it at the monitor's refresh and forget it" title.
• Counter-Strike 1.6 — same story. The GoldSrc engine is light; you're refresh-rate-limited. A 19-inch CRT at 85–100 Hz is the actual ceiling, not the GPU.
• Unreal Tournament 2003 — the genuine workout of the four. Per AnandTech's UT2003 flyby/botmatch numbers from 2002, a Ti 4600 paired with a fast Athlon XP held comfortably above 60 fps at 1024×768 with detail up, dipping in heavy botmatches but staying very playable. Drop to 800×600 and it's a non-issue. This is the game that justified buying the Ti 4600 over the Ti 4200.
• Battlefield 1942 — the RAM-hungry outlier. With 512 MB it runs fine at 1024×768 medium; with 1 GB the big 64-player maps stop hitching during streaming. Period coverage put a Ti 4600 build in the smooth-and-playable range here, which in 2002 was exactly what people wanted for the game everyone was actually playing at the LAN.

Bottom line on performance: this build was over-specced for Quake III and CS, well-matched to UT2003, and adequate-to-good for BF1942 — which is precisely the balance a 2002 buyer was paying for.

Audigy FX retrofit option for builders without 2 ZS access

Genuine Audigy 2 ZS cards have gotten pricey and the capacitors are now 20-plus years old. If you can't source a good one — or you just want a card you can buy new with a warranty — the Creative Sound Blaster Audigy FX is the pragmatic retrofit. It's a low-profile PCI card, it carries the Sound Blaster name and EAX-style processing, and Creative still sells it. It is not a bit-for-bit clone of the 2002 SoundStorm/Audigy experience — the DSP feature set is leaner — but for a LAN rig where the job is "clean positional audio in CS and UT2003 through headphones," it does the job, installs cleanly on Windows XP in the driver order above, and frees you from gambling on dried-out 2002 silicon. Treat it as the "I want this build playable this weekend" choice; chase a pristine Audigy 2 ZS later if authenticity itches. (As an Amazon Associate, SpecPicks earns from qualifying purchases; pricing on Amazon and eBay may vary.)

Period-correct CRT pairing

The build isn't done until it's on the right glass. A 2002 LAN setup means a CRT — ideally a 19-inch shadow-mask or aperture-grille tube (the Sony Trinitron-based models are the prestige pick, but a solid Dell/Viewsonic 19-inch is what most people actually hauled around). Run it at 1024×768@85 Hz — high enough refresh that the image doesn't flicker, low enough resolution that the GeForce 4 Ti never strains. The reasons this matters beyond nostalgia: CRTs have effectively zero input latency and no fixed native resolution, so the 2002 games — which were tuned and competitively played on exactly this hardware — feel the way their designers intended. An LCD will work, but you'll be adding latency the era didn't have and scaling artifacts the games weren't built for. If you go CRT, budget for the weight (a 19-inch tube is 40-plus pounds) and a sturdier table than the one that betrayed you in 2002.

Bottom line

A 2002 lan party pc build is one of the most satisfying retro projects precisely because the era's parts are abundant, the platform is forgiving, and the target is unambiguous: DirectX 8.1, AGP 4x, 1024×768 on a CRT. Anchor it with an Athlon XP 2200+, an Abit NF7-S, a GeForce 4 Ti 4600, and an Audigy-class card; slipstream Windows XP with the nForce2 drivers baked in; install chipset → GPU → sound → NIC, in that order; and bring a switch, not a hub. The result runs Quake III and CS 1.6 against the monitor's refresh ceiling, holds 60-plus fps in UT2003, and plays BF1942 smoothly with a gig of RAM. If a real Audigy 2 ZS won't cooperate, the Creative Sound Blaster Audigy FX gets you to the LAN this weekend. Tape the parts list inside the case lid, find a table that can hold the CRT, and you've got the 2002 gaming PC, faithfully rebuilt.

Citations and sources

• AnandTech — GeForce 4 Ti launch and UT2003 performance coverage, 2002: https://www.anandtech.com/
• Tom's Hardware — GeForce 4 Ti 4600 / Ti 4200 reviews and 2002 GPU hierarchy: https://www.tomshardware.com/
• AnandTech — Athlon XP 2200+ (Thoroughbred) and nForce2 platform reviews, 2002: https://www.anandtech.com/
• TechPowerUp GPU Database — NVIDIA GeForce 4 Ti 4600 specifications: https://www.techpowerup.com/gpu-specs/
• Creative — Sound Blaster Audigy FX product page and Windows driver downloads: https://www.creative.com/

This piece is editorial synthesis based on publicly available information. No independent first-party benchmarking is reported.