http://sof2.ravensoft.com/faq.htm

This will be updated frequently.  Stop here first before posting.

sorry, is that patch for both win2k and XP? It just says win2k on AMD's page.

and also, would you know if that agp patch is included in any windows updates?

EDIT: thanks destrox
EDIT2: ouch, looked in registry, didn't have the string so i used the .reg file to add it. ran a timedemo in q3 and went from 242 fps down to 193. sof2 ran the exact same fps. this file is not for me. sys specs: epox 8KHA+,amd 2000+xp,512mb 2100 ddr,asus gf3 ti 500 28.32, sb live x-gamer, win 2k sp2. thanks for the tips though  

Some of the pak file are about 1,000 to 2,000 off in the base folder and i checked my cd and they are the same there also
for example


base
Docs
Extras
Uninstall
802,816 cgamex86.dll     784kb
94,208 EaxMan.dll           92
143,360 ffx86.dll             140
2,273,280 gamex86.dll       2,220
200,704 IFC22.dll           196
241,664 Menusx86.dll       236
204,800 snd_alx86.dll       200
188,416 snd_dsx86.dll       184
1,064,960 SoF2.exe            1,040
1,531,963 SoF2MP.exe          1,497


In the base folder

102,985,472 maps.pk3             100,572
96,636,622 models.pk3             94,372
31,722,385 mp.pk3                  30,979
191,252,236 musicandsound.pk3      186,770
73,241,493 skins.pk3                    71,525
413,194,735 textures0.pk3              402,511
164,152,653 textures1234.pk3         160,306
69,463,128 therest.pk3                67,836


just wondering if there is somthing wrong??

The AMD-Win2000 registry patch is not needed for XP (it's already incorporated).
It is not contained in any updates. You have to add it manually.
All it does is extend a memory range. I seriously doubt it causes decreased frame rates.

Yes but there are more issues then just FPS problems.
Some of us have random reboots, or even syncronized reboots @ specific points.

So that theoretically could have helped, but it didnt for me.
But was a worthy try.

The problem with the listed sizes is that you're not looking at the right ones.
You're looking at Kilobyte sizes, which are based on 1024 bytes to a kilobyte.  That's why they appear off.
The exact sizes listed in the FAQ are exact byte sizes.  You can find these by right-clicking the file and selecting "Properties".

hyas RevTed.

"It has been noted that many problems involving missing or corrupted images, and menus with buttons that won't work, etc, may be a result of improperly installed pk3 files."

              I have had intermittent corrupted images, and all my pk3s are the exact size as the faq, and I tested them with winzip as instructed. All is cool on that front. So I guess for me at least the theory isn`t holding alot of water. lol