Results 1 to 2 of 2
Thread: winoldap Woes
2002-12-31, 13:46 #1
- Join Date
- Oct 2001
- Bellevue, Nebraska, USA
- Thanked 1 Time in 1 Post
After upgrading my second system (an old 500MHz AT) with a run-of-the-mill 1.7 Celeron on a no-frills Biostar board, I have been experiencing problems with multiple instances of "winoldap" running. This is a WinMe system. The problem occurs with I fire up my command-line client for SETI. Immediately, one instance of winoldap will appear in Task Manager. However, if I leave the system running for several hours (my normal practice is to have my systems running 24/7) soon I will have several and then many (up to 21 so far!) instances of winoldap running. Needless-to-say, soon my system has slowed to half a crawl. Exiting SETI does not cause the winoldaps to close. "Ending" the task results in "This program not responding" error. Eventually, I can get every instance closed but then they will start opening up again. I am thinking it may be connected to the screen saver/sleep modes.
Searching the net points to drivers - I have used the drivers out-of-the-box for the monitor, Video card (this is the same VC used in the old system), and audio card and also upgraded to the latest drivers - same thing.
It did not happen before the upgrade with the same OS installed on the same hard drives. Also using the same monitor and video card.
No problems on the XPP and two XP Home systems running same SETI config.
Freedom is NOT Free!
Heat is the bane of all electronics!
2003-01-04, 17:48 #2
- Join Date
- Apr 2001
- Tunbridge Wells, United Kingdom
- Thanked 0 Times in 0 Posts
Re: winoldap Woes
I ran a newer version of the Seti program on Me without any problems. Me doesn't seem to like anything DOS-related, so maybe this would be your best bet.
Personally, I've switched to searching for a cure for Cancer with United Devices. The benefits seemed a bit more concrete.We never really grow up, we only learn how to act in public.