> Perhaps you can find a way around. Just set up a batch script what kills the
> boinc manager and execute this before the backup process starts (there should
> be an option in the programm or do it as a scheduled task)
>

That would be nice except it doesnt kill that easily. With Boinc Manager 4.56 you have to kill Boinc Manager, Boinc and the Seti being processed at the time. If you dont, something is always left running.

In any case, that really isnt a GOOD answer but thanks for the suggestion. It should do what previous Boincs did and not interfere with a shutdown or reboot command.

Greg.

Perhaps you can find a way around. Just set up a batch script what kills the boinc manager and execute this before the backup process starts (there should be an option in the programm or do it as a scheduled task)

---

BOINC Doc | Team-Site | BOINC-Podcast

> Greg,
>
> Which backup program are you using? Does it attempt to shutdown BOINC
> itself or does it merely reboot the machine and startup the machine in a mode
> where it is the only thing running?
>

On the Win98SE machines it is Drive Image 2002. That particular prog needs to be rebooted and the prog loads an image of a boot floppy to do the backup. The prog causes a reboot at a set time and the reboot is the thing that attempts to shut Boinc Manager down. Boinc manager WONT shut down under those circumstances. Even a simple Shut Down in the normal way via start button wont happen with Boinc manager running as it complains it has to be shut down first. I got Steve Gibson's Wizmo which forces a rude shutdown regardless of what is running and it is the only reliable way to shut the machine down without first exiting Boinc Manager. Note that if I DO exit Boinc Manager, I can shut down normally.

> Can you reboot your computer without shuting down BOINC, without causing
> the OS to say it failed to logoff/shutdown because it was unable to close
> BOINC?
>
>

If I need to reboot or shut down normally or if the backup prog is doing the rebooting, Boinc Manager interferes on all occasions and wont let a reboot or shutdown happen. The simple solution would be for me to be able to time when Boinc manager should exit. Eg, a preference saying "Terminate program at what time?" and I fill that time in for 5 minutes before the backup. That way it should work fine if Boinc Manager gracefully unloaded.

Greg.

Greg,

Which backup program are you using? Does it attempt to shutdown BOINC itself or does it merely reboot the machine and startup the machine in a mode where it is the only thing running?

Can you reboot your computer without shuting down BOINC, without causing the OS to say it failed to logoff/shutdown because it was unable to close BOINC?

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog

> >
> > While all that is going on, my P3 600Mhz and P2 400Mhz both running
> Boinc
> > Manager 4.56 as well exit Boinc and Seti gracefully UNLESS a program I
> use for
> > backing up (image) causes the machines to reboot in order to do that
> backup.
> > When that happens, they freeze and wont exit, throwing up complaints
> that
> > Boinc has to be shut down before they can do a thing.
> >
> > Greg.
> This is a normal occurence for Win98 machines, they HATE to be shutdown with
> programs running. This was a problem for Classic for YEARS! Still is, but
> there is a work around. You have to add a small file to each directory that
> has Seti in it and then it will be fine. Ask on the newsgroups or MIRC.
>

Sorry but that just isnt true. I ran classic Seti for years with these same image backup progs and no probs at all. In fact, earlier Boincs didnt cause this problem either. This has only started with 4.56 Boinc Manager.

Greg.

>
> While all that is going on, my P3 600Mhz and P2 400Mhz both running Boinc
> Manager 4.56 as well exit Boinc and Seti gracefully UNLESS a program I use for
> backing up (image) causes the machines to reboot in order to do that backup.
> When that happens, they freeze and wont exit, throwing up complaints that
> Boinc has to be shut down before they can do a thing.
>
> Greg.
This is a normal occurence for Win98 machines, they HATE to be shutdown with programs running. This was a problem for Classic for YEARS! Still is, but there is a work around. You have to add a small file to each directory that has Seti in it and then it will be fine. Ask on the newsgroups or MIRC.

---

Interesting problems that may be associated with a new CPU I have more than anything else but I have no proof, just suspect this.

What happens is that, on XPSP2, when I exit Boinc Manager (boincmgr.exe), it peacefully shuts down and sometimes shuts down Boinc and Seti WUs. Sometimes just Boinc Manager shuts down and leaves the rest running.

At the same time, when I start up the machine, BoincView starts TWICE for unknown reasons and freezes. I have to, routinely, terminate Boincview and restart it and then all goes normally.

None of this happened, though, until recently when I made one change to this particular computer. It WAS a P4 1.7Ghz and now is a P4 3.4Ghz. It was the only hardware change made on the machine. Eg, I pulled the 1.7Ghz CPU out and shoved the 3.4 in on the same motherboard etc.

In the meantime, my laptop which is the same as it always was and also running Boinc Manager 4.56 but not Boincview, exits gracefully every time.

While all that is going on, my P3 600Mhz and P2 400Mhz both running Boinc Manager 4.56 as well exit Boinc and Seti gracefully UNLESS a program I use for backing up (image) causes the machines to reboot in order to do that backup. When that happens, they freeze and wont exit, throwing up complaints that Boinc has to be shut down before they can do a thing.

P4 3.4ghz runs XPSP2 fully updated.
Laptop (P3 1.13Ghz) runs XPSP2 fully updated.
P3 600 runs 98SE
P2 400 runs 98SE.

I feel the major problem on the P4 3.4 is the speed of the CPU or something else about the CPU that may not get on quite well with Boinc Manager 4.56 and also Boincview and on the 98SE machines, it is just some message that shouldnt come up from Boinc Manager that does, nevertheless and stops the reboot happening.

Oh and I also checked my Windows (SFC /SCANNOW on XP machines and SFC and check all files on 98SE machines) and though the P4 3.4Ghz did have a problem on one file that was replaced, it hasnt changed anything after it being fixed and a reboot done.

While all this isnt enough to stop me running the programs, they ARE annoying problems nonetheless and I hope that possibly, someone doing the programming will note and be able to fix it.

Anyone needing something tested on my machines, just let me know and I will do it.

Greg.