Finally getting new tasks only seconds after running out. May not be worth the hassle.

For me this time out script does not work as I can make a WU in less than 92 sec so each time it runs it reports the completed tasks and then does not get anymore.

Also, if I disable the network for 15 min, then report it the same sort of deal.

It seems like its only possible to get task in batches of 300 with the current setup of the project

The only script that I know of that work is listed here
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4532&postid=69286#69286

You can try my program "7.15.0" mentioned further down this thread but you would have to give up 7.16.11 "the latest and greatest" as my app is a mod of 7.14.dontremember

The problem (feature ?) is with the Milkyway server not the SETI client or manager.

Just wanted to add a comment since the mention of our client was in the linked workaround post. We had the opinion that our Pandora client was just too powerful to leak out into the SETI masses because of its ability to completely obliterate any server side restrictions on getting work or the amount of work. The cliche saying of "with great power comes great responsibility" was in our forethought. So that is why we restricted it to just the GPUUG team members. Not because we we wanted to horde it all to ourselves.

If everyone had access to the client, unbridled use would bring every project to its knees. So we made sure all our members using the client avowed to use it responsibly so as to not upset SETI or the other projects our team members are attached to.

We had a very good developer that was able to keep modifying the client as needed to overcome the foibles and restrictions of various projects. I was the one that suggested the removal of the ten minute delay here at Milkyway since that was the most aggravating issue for me.

---

I'm happy to not work around the features in a major way, I can get a far bit of work with my powershell script.

Enter-BoincSession
$netmsg = Get-BoincMessage | Where-Object {$_.Body -like '*network*'}
$boinctime = [INT] ((Get-Date) - $netmsg[($netmsg.Length -1)].Timestamp.LocalDateTime).TotalMinutes
$mwtasks = (Get-BoincTask | Where-Object {$_.ProjectUrl -like '*milkyway*'}).Count
If ($boinctime -ge 10){
	Set-BoincMode -NetworkMode Always
	Start-Sleep -s 92
	Get-BoincProject | Where-Object {$_.ProjectName -like '*milkyway*'} | Update-BoincProject
	}
If ($mwtasks -eq 0){
	Set-BoincMode -NetworkMode Always
	Start-Sleep -s 92
	Get-BoincProject | Where-Object {$_.ProjectName -like '*milkyway*'} | Update-BoincProject
}
If (($mwtasks -gt 0) -and ($boinctime -eq 2)){Set-BoincMode -NetworkMode Never}
$boinctime
$mwtasks
(Get-BoincStatus).NetworkMode

You need the PSBoinc from https://www.powershellgallery.com/packages/PSBoinc/1.1

So will 7.15.0 work after December 17?

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4816

So will 7.15.0 work after December 17?

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4816

Should. Looks like that branch used SSL 1.1 as minimum except for Android which allowed SSL 1.02

---

So will 7.15.0 work after December 17?

https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4816

since 15 is bigger than 2 then yes it should, it's a Linux type numbering system, each set of numbers escalates as they continue thru the releases and if you ever want to find the latest version and some beta versions as well you can always check here, they are in release order https://boinc.berkeley.edu/dl/?C=M;O=D and yes 7.2.? is listed way down the list

This still works great in case anyone wonders. Tried it out today after a long Hiatus from MW and its doing what it needs to!

(in windows 10 anyways)