Problem with 7.0.54

[nanoprobe]

Just an FYI to anyone who crunchers Milkyway@Home. Do not try to run MW on the new client. There is a bug and it stops the downloads. Developers have been notified and confirmed the problem. There may be others but that is the only one I know about. Here is the error.

3/8/2013 5:00:51 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/8/2013 5:00:51 PM | Milkyway@Home | Requesting new tasks for ATI
3/8/2013 5:00:52 PM | Milkyway@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
3/8/2013 5:00:52 PM | Milkyway@Home | [error] No close tag in scheduler reply

[Mumps]

Just an FYI to anyone who crunchers Milkyway@Home. Do not try to run MW on the new client. There is a bug and it stops the downloads. Developers have been notified and confirmed the problem. There may be others but that is the only one I know about. Here is the error.

3/8/2013 5:00:51 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/8/2013 5:00:51 PM | Milkyway@Home | Requesting new tasks for ATI
3/8/2013 5:00:52 PM | Milkyway@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
3/8/2013 5:00:52 PM | Milkyway@Home | [error] No close tag in scheduler reply

Thanks for the heads up nanoprobe!

[Slicker]

Just an FYI to anyone who crunchers Milkyway@Home. Do not try to run MW on the new client. There is a bug and it stops the downloads. Developers have been notified and confirmed the problem. There may be others but that is the only one I know about. Here is the error.

3/8/2013 5:00:51 PM | Milkyway@Home | Sending scheduler request: Requested by user.
3/8/2013 5:00:51 PM | Milkyway@Home | Requesting new tasks for ATI
3/8/2013 5:00:52 PM | Milkyway@Home | [error] Can't parse workunit in scheduler reply: unexpected XML tag or syntax
3/8/2013 5:00:52 PM | Milkyway@Home | [error] No close tag in scheduler reply

Several of us have been hounding them to use a real XML library instead of their home grown one which looks like XML but isn't compliant with the XML 1.0 specifications. But our requests fall on deaf ears. That or they get real defensive about how great their code is. There are real performance issues that their method causes for projects (e.g. the use of elements vs attibutes doubles the bandwidth) but they evidently have enough grant money to pay for their network lines that they do not care.