Win2k causing Counter-Strike FPS Slow Downs!

I recently obtained a copy of Windows 2000 Proffesional for my GA-7ZX series VIA KT133 Chipset Socket A - AMD T-Bird, 800 MHZ on Windows ME.

After scrubbing my HD for a fresh install of W2K, and successfully installing it, and updating all my drivers (Geforce 2, SB Live!, Intellimouse, HP CD-WRITER 8200, and Via 4 in 1 Drivers), in certain games I am experiencing pulsating slow downs. Almost like an IRQ interrupt signal. Sometimes its every 10 seconds, sometimes 30 seconds. But either way, my usual 99 FPS in Counter-Strike is throttled down to a good 4FPS in regular intervals. I have removed every accessory that I could in an attempt to see what is going on, but nothing has helped. I haven't tried any other games but Counter-Strike. Im down to my last wire here. Any reasons you can think of?

System Specs:


Win2k Pro
Gigabyte GA-7ZX
VIA KT133 Chipset Socket A
AMD T-Bird 800 Mhz
256 MBS PC-133 RAM
Geforce 2 GTS - 32 MBS
Creative Labs Sound Blaster Live! Value
20 Gig Maxtor
Microsoft w/ Intellieye


I am at a loss here. Thanks


Icy

will it also happen under half-life in solo play?

Or is it limited to multiplayer?

Man i feel bad.....I am a CS addict and I know if anything were interrupt my flawless game play I'd be very mad. With your specs the game should run flawlessly.

I'd disable the sound card. I notice my LPT port was conflicting with my Graphics card...Don't ask me how.....Windows ME sucks, but its probably a conflict of some kind. Are you using the netgraph console command or something else to bench your FPS.

joker: playing normal halflife solo, no. it works fine. playing cstrike in a lan game has the same fps problems as with internet.

other guy: i have cl_showfps 1 to clock my fps. never been a problem before. everything worked fine back on windows ME. dunno what is wrong now.

Ooohh..I noticed the SB Live! and KT133 Via chipset = <resources> -> munch munch munch. :)
you say certain games, would these certain games be using OpenGL or DirectX? I have a vaugly simular machine and DirectX seems to have some fps issues.
I do only around 30-45 fps in counter-strike but sometimes it does drop to about 15 fps (on WinME).
Try also checking the maxframerate_ in the config. Check www.tweak3d.net for some good tips on maximizing HL for network play. There is a setting that will minimize your frame rates during network play in the config somewhere.

no way. no way in hell. i payed a bunch for this talon, and it came with windows ME. works GREAT on windows me. i only upgraded to windows 2000 because i had it. if i can't play with everything set to HIGH, then i won't be doing it. back to windows ME for me. where i get 99 fps in counter-strike.

there are NO problems with windows ME. its only when i went to windows 2K. that is what i am trying to figure out!

opengl and direct 3d make no difference with my problems. happens on both, only multiplayer.

FIXED. added heapsize 128

I would seriously recommend not making w2k your choice for a primary gaming platform. I've had all sorts of problems with games in w2k. Most of them being related to video or input problems. If your a huge game player, do yourself a favour and dual boot with 98 or ME and just use them for games only (I havent installed office or anything apart from the "essential" apps on my 98SE boot.) It runs really sweet. ;)

Ok dont even go and start saying everything was fine with ME and now it sucks in Win2k. Me is the biggest piece of ******* **** ever and it specializes in slowing down your computer and being as inefficient as possibly. Win2k runs so much faster and as you found you just had a value wrong. Lets make sure that you are absolutly sure that Win2k is causing it before you start making accusitions like Win2k is bad WinMe was perfect! :D

you go boy tell that winME lover whos boss.

hehehe

btw all my games work as good if not better in win2k than they did in win98 which is basically better than winME so what does that tell ya.

you just have to be smart enough to be able to get them to work correctly. usually it is a case of drivers. or not haveing the correct windows updates.