Let me know if solved. For CUDA 80 only.

I just tried Linux and windows, Linux couldn't find any tasks and windows found a task but immediately errored.

Hello, no it is not solved !
It ill be solved when PRJ will make a reneal of license and fully restat whole project and all server !
But first, they need to pay licence !

Only Windows for the Short/Long apps:
https://www.gpugrid.net/apps.php

I updated the short and long apps (version 923). Should fix the problem. As far as I know Linux was not affected.

I updated the short and long apps (version 923). Should fix the problem. As far as I know Linux was not affected.

If the new versions work properly, where are the workunits set up to use those new versions?

I updated the short and long apps (version 923). Should fix the problem. As far as I know Linux was not affected.

Task 21304404 on normally-reliable host 45218 (Windows 7, GTX 970) has started and is running - seemingly normally. Result likely midday tomorrow.

Mine is running Long run Cuda 80's today on Win 10 pro Yeah.. Glad they got the Lic issue for Win10 fixed or whatever they did.

Thanks

I now have an application running. A rather bad initial runtime estimate, but that is typical for new versions. Likely to finish in the next 5 hours. Running under Windows 10 Pro.

Anyone try a 20xx card yet? It would be nice to know if the Turing is working now too.

Anyone try a 20xx card yet? It would be nice to know if the Turing is working now too.

It is still the ACEMD2 app, so Turing not working yet.

I updated the short and long apps (version 923). Should fix the problem. As far as I know Linux was not affected.

What?

Linux version has been dead since May! 3 full months.

A post of your own.
https://www.gpugrid.net/forum_thread.php?id=4925&nowrap=true#51818

I updated the short and long apps (version 923). Should fix the problem. As far as I know Linux was not affected.

What?

Linux version has been dead since May! 3 full months.

A post of your own.
https://www.gpugrid.net/forum_thread.php?id=4925&nowrap=true#51818

mmonnin,
The update is only concerning the problem about windows/nvidia licence.
It not speak about Linux. Please read all.
If you run under other than Windows, it not apply for .

I updated the short and long apps (version 923). Should fix the problem. As far as I know Linux was not affected.

What?

Linux version has been dead since May! 3 full months.

A post of your own.
https://www.gpugrid.net/forum_thread.php?id=4925&nowrap=true#51818

mmonnin,
The update is only concerning the problem about windows/nvidia licence.
It not speak about Linux. Please read all.
If you run under other than Windows, it not apply for .

You are incorrect. The same thing happened last year and in May for the Linux version. The same problem is not limited to Windows. Toni didn't acknowledge it here but did in May. That's what I was pointing out.

Maybe I'm saying something wrong but my antivirus says that you' re site have been infected by IDP.Generic.

Maybe I'm saying something wrong but my antivirus says that you' re site have been infected by IDP.Generic.

Exclude the Boinc directories from your a/v as it's a false positive, any real virus will try to infect other files on your computer and be flagged. Boinc doesn't really have viruses, the units come from Servers and that would be bad for business so they are all well protected. What Boinc does have is alot of back and forth communication between the Servers and our pc's making it LOOK like activity a virus might do so the 'heuristics' in all a/v programs now sometimes flag it.

... What Boinc does have is alot of back and forth communication between the Servers and our pc's ...

you need to differentiate between the various BOINC projects.
While, for example, some sub-projects of LHC (like CMS) does indeed send back and forth a lot of data all the time, this is not true for GPUGRID. Once a task has been downloaded and started crunching, there is no such additional data transmission until the task is finished and being uploaded.
So GPUGRID crunching should not induce a false A/V alarm (at least not on basis of an unusual high data traffic).

So I see the Windows folks got another year of license on their acemd2 app.

So why don't we Linux users get work for our tested acemd3 app so we can crunch too?

I 100% agree!

So I see the Windows folks got another year of license on their acemd2 app.

So why don't we Linux users get work for our tested acemd3 app so we can crunch too?

Have none of the project team tried rebuilding the current Linux application with no change except a new version number?

If one has, what went wrong?

So I see the Windows folks got another year of license on their acemd2 app.

So why don't we Linux users get work for our tested acemd3 app so we can crunch too?

Have none of the project team tried rebuilding the current Linux application with no change except a new version number?

If one has, what went wrong?

Why do they need to rebuild? The latest 2.03(CUDA80) and 2.04(CUDA100) acemd3 apps worked fine on all the test WU's.

Just release the bloody work units!

So I see the Windows folks got another year of license on their acemd2 app.

So why don't we Linux users get work for our tested acemd3 app so we can crunch too?

Have none of the project team tried rebuilding the current Linux application with no change except a new version number?

If one has, what went wrong?

Why do they need to rebuild? The latest 2.03(CUDA80) and 2.04(CUDA100) acemd3 apps worked fine on all the test WU's.

Just release the bloody work units!

WHY aren't they offering Linux workunits? I'm assuming that it is because the latest Linux applications no longer work, but you appear to be assuming that it is some other reason.