"Kenton W. Mellott" <melken@co.tds.net> wrote in message
news:3fb873e8_1@newspeer2.tds.net...

I appreciate your input.  My endeavors with

http://www.vassaux.net/seti/eng/

came up completely empty as far as an executable program goes.  The

outline

for the whole process was quite informative and useful though, especially

as

it relates to Windows' 'regedit' file.

I found out I had to put my startup batch file in Windows' Startup and not
the autoexec.bat.  DOS doesn't do long filenames so it does not copy the
files properly to MS- RAMDRIVE.

I think I finally got Window's Task Manager to copy my files over to the
hard drive every couple of hours now.  It didn't want to use an batch file
with XCOPY in it.  So I programmed a simple executable to do the same

thing.

Even though I used a batch file to feed it a command line also, the Task
Manager seemed to use that okay, if I dropped the repeat time down and was
there using the computer, at first.  I kept increasing the time between
repeats and now it seems to be working at 2 hours.

Another concern may be arising, though.  I shut the machine down after it
had completed a workunit on the RAM drive, but I'm suspecting it wasn't

yet

copied to the hard drive.  I was trying to send the results back but my
internet connection was not working.  So that failed.

After I restarted the machine, the internet connection now is working.

But

SETI at first display partial completion then restarted the work unit as
though it was a new one.

Anyone know what up?

Sincerely,

Gregory D. MELLOTT

I need to add that using the Task Manager seems to be keeping my computer
from turning the monitor back on.  That has been the case recently, anyway.
When I turn that off and just switch off the monitor, things have been going
OK.  I may need to check if my BIOS is set to do any such action,  as I have
noticed that it can generate the same conflict with Windows' power
management.

Sincerely again,

Gregory D. MELLOTT teching for Kenton W. MELLOTT