It looks like you're using an Ad Blocker.

Please white-list or disable in your ad-blocking tool.

Thank you.


Some features of ATS will be disabled while you continue to use an ad-blocker.


High CPU Usage With Cmdline? Is This A Problem?

page: 1

log in


posted on Jun, 28 2002 @ 10:04 PM
Posted on the old board by Cherokee

first my computer spec's
window's ME
pent3 500
448 ram
now that i am using the command line version it is showing that it is using 81% of my processer which puts the system monitor if i use it at a steady 100%
ok now this my be a prob with my computer because when i have nothing running at all and have used control alt delete to get rid of everything there i don't need my system monitor is still showing 50% steady of my processer being used? anyone that know's more about computer's plz help

Reply on the old board by Bob88

Sound like you're OK. Seti is indeed CPU intensive. The command-line version runs on a 'low cpu priority' therefore it allows other applications cpu time when they need it. It basically uses your CPU when nothing else is.

posted on Jan, 29 2003 @ 07:02 AM
What is it that I'm looking for when I'm downloading the command-line version?

Is it *i386-winnt-cmdline.exe:* and then click one, or two?

I'm looking for a window-based (WindowsMe) command-line that you can run with SetiSpy.


new topics

log in