I upgraded to Win2K a few weeks ago and, after some inital problems, got
FS2K running pretty well. Sometimes, though, I'd fire it up and get
terrible screen resolution and extremely slow frame rates -- 3-5/sec,
where usually it's in the 15-20/sec range. Reboots didn't seem to help;
it just seemed as if sometimes it worked and sometimes it didn't.
Tonight it was running ugly, so I opened up the Win2K task master and
found a process called FS2000.icd which was taking up between 97%-99% of
CPU cycles, even when FS2K was paused! No wonder the beast is slow; if
FS2000.icd is taking up that many cycles when paused, you know there's
no overhead for actually flying.
I'm assuming that this is the main thread running FS2k. Why would it
suck up that much CPU time? As I said, most often FS2k runs much faster,
and I'm betting that when that's the case, this process doesn't take up
that much of the CPU, but I'm darned if I can get it to run better
tonight.
Any ideas? Does it seem normal that this FS2000.ICD would take damn near
every CPU cycle? Machine is a PII, 450mhz, 384 mg ram, Logitech Wingman
(non-FF).
John
Im not an expert so you will need one of them, put there is some command you
can add to some programs to limit their cycles
