>> Im currenty running running seti command line, >> im knew to the command line..... >> im also using setidriver..... >> >> my question is. how do i get seti command line to start when the computer is boots up, >> getting seti driver to start at start up would be nice to, but that >> doesnt really matter to me at this point in time.
Make sure you have a directory that contains the setidriver and the command line client. Run setidriver and configure the number of cache units, client priority, proxy settings if needed, and make sure you save the config. Once that is done and working correctly, drag&drop the setdriver icon into your startup folder. Reboot and you should see the setidriver icon in your system tray. >> my second question, running 31 hours per unit to long for a computer running a >> k6-2 400 with windows ME (planning to update to win2k pro in few weeks) >> (runs 24/7 and is almost never used, if it is seti is turned on for >> weekly maintence and cd burning, and then seti is turned back on after >> finished) Celeron 233 running Linux takes 20 hours. Celeron 333 running Linux takes 17 hours. P3-733 running WinME takes 9 hours. 750 Athlon running WinMe takes 8 hours. == Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html This list sponsored by talkspace.net: building space communities online. Mailing list services provided by klx.communications -- www.klx.com
