Very slow rig

[Niege]

I am assimilating another rig in my office but it's very weird. It's a P-III, 1Ghz, 256 and WinME, and I'm running SETI Driver on it, as I am on another very similar machine running W98FE. On the one already in production I get times of 6-7 hrs per WU. On the new one it's saying times of 5-6 DAYS! I checked the BIOS and can't see anything remarkably wrong. Any suggestions?

 

[Spacehead]

On the new one it's saying times of 5-6 DAYS!

Is that common or just for one particular WU? Maybe just delete that WU & try another.
Any other progs hogging CPU time?

 

[Baldy18]

6-6.5 hours should be normal for a rig of that speed.

 

[Coquito]

Flush & try again is usually is the best first line of action.

Bah, I'm only getting 7-7 1/2 per wu on my 1ker. :|

 

[Niege]

The rig has processed a couple of WUs now with the same result. Hardly anyone uses the rig except as needed in a conference room, but now when I have used it for other applications (Excel, Act!) I notice that in every application it's incredibly slow - more like a P-90 than a P-1000. It has a crappy video card with only 16MB, but that shouldn't affect the processing speed.

 

[Coquito]

Have you done a search for any adware, malware(viruses & trojans) & bloatware?

 

[nbarb99]

Download Wintop and see if anything is taking up the CPU time.

 

[InlineFive]

Run AdAware to check for Spyware/Adware that might be slowing it down.

 

[Niege]

Thanks, guys. I did a virus check: no virii. I ran Ad-Aware: no glaring thing. I used msconfig and unchecked every unnecessary startup process. Haven't gotten Wintop yet, but in the Task Manager in ME there doesn't appear to be much running. In any case I rechecked the specs and they're right (PIII-1000, 256MB), but I'm still getting 5-6 Days per WU. My Celeron 400 with 128MB does one in 18 Hours. I think next I'll dl Wintop and Sandra and see what, if anything goes on. Very perlexed.

 

[Coolkid]

It's most likely another program stealing CPU cycles, try Wintop like nbarb suggested 🙂

 

[lobadobadingdong]

what motherboard is it using? it could be a simple case of incorrect bios settings. make sure the internal/external cache's are enabled, video bios shadow should also be enabled. disable agp fast writes(if the option exists on that board)