BillW50 wrote:
In ,
Paul typed:
And I have fixed DST with tzedit, back when I was running Win2K.

How long did you run Windows 2000, Paul? I ran it a lot between 2000 to
2006. Then for a few days in 2009. And now I am running it again. I am
surprised how many modern applications it still can run. It would have
been nice if Microsoft allowed IE7 to run on Windows 2000. But there are
other browsers besides IE. ;-)

I'm using Windows 2000 once again on this machine, because XP has high
DPCs for some reason. It seems related to the WiFi driver. But Windows
2000 is using the same driver and it is ok there. Go figure.

And somebody came out with a patch to fix DST for older Windows versions
including Windows 2000. That is what I used.


I still use Win2K for maintenance (as part of dual boot), but I don't
run it regularly. It's not a good environment for testing games now,
because of the game installer check for the OS version.

Win2K and WinXP are really close when it comes to binary compatibility,
and for a period when they overlapped, you could expect any program written
for one to work with the other. It took some extra effort on Microsoft's part,
like putting a few extra things in DirectX, to spoil that on purpose. For
a while, I was patching out OS checks in a game installer with a hex editor,
but that doesn't always work.

The solution for the browser, is to run something else.

For the Wifi, all I can suggest is reviewing any settings in Device Manager,
such as perhaps interrupt consolidation. But that won't help if the
Wifi is currently idle, that would be more for constant packet transfer,
where you wanted less processor overhead. Some Wifi have their own processor
in the MAC chip, and that offers an opportunity to do more without
interrupting the host. I think it was put there, so you could do things
like Wake On LAN while the computer sleeps (Wifi continues to run).

Paul