Posted by member 7223 on 2003-02-22 14:26:04 link
There could be many causes to this. Generally, there's a program crash that eat all the cpu ressources. You give us no clue to diagnose the problem.
Try to identify when, exactly, the slowdown appears. Try first to kill every running apps. Then run litestep with the -nostartup command line parameter. If the slowdown appears here, you'll have to check what module makes litestep crash...
This could take some time...
Try to identify when, exactly, the slowdown appears. Try first to kill every running apps. Then run litestep with the -nostartup command line parameter. If the slowdown appears here, you'll have to check what module makes litestep crash...
This could take some time...