Final notice: we expect to run out of the old format data files in the next 24 hours. The new data format will be shipped automatically as soon as the old sets are depleted. If you're using an app_info.xml file please update to the latest binaries (BRP4 v1.22 or later).
Thanks,
Oliver
- posted 12 Mar 12 ~1714
Really. Gig's up in 24 hrs, eh?
Then how comes I gots me 3 - as I'm lookin' at my screen right now (count 'em) - S6Bucket WU's to crunch? And the server is showing ~77,000 S6 Bucket WU's still waiting to be served. And that's not even including the other two - nonBRP4 - type applications.
A healthy dose of head sup! would be 'preciated here.
FWIW: I'm not using an app_info.xml file (just running the generic stuff that gets servered).
We did have two transitions recently, that are technically independent:
- S6Bucket -> S6LV1
- 8Bit -> 4Bit BRP4 data
If you are using the 1.22 version of BRP4 Apps, you shouldn't notice anything of the second one, the new data files end in ".bin4" instead of ".binary", that's all. This just happens to coincide with the other app transition.
Final notice: we expect to run out of the old format data files in the next 24 hours. The new data format will be shipped automatically as soon as the old sets are depleted. If you're using an app_info.xml file please update to the latest binaries (BRP4 v1.22 or later).
Thanks,
Oliver
- posted 12 Mar 12 ~1714
Really. Gig's up in 24 hrs, eh?
Then how comes I gots me 3 - as I'm lookin' at my screen right now (count 'em) - S6Bucket WU's to crunch? And the server is showing ~77,000 S6 Bucket WU's still waiting to be served. And that's not even including the other two - nonBRP4 - type applications.
If you had read Oliver's message a bit more carefully, you might have noticed the "If you are using an app_info.xml" and "BRP4 v1.22 or later". You are NOT using app_info.xml so the message doesn't apply to you. You have received new GW tasks (S6Bucket) and NOT BRP4 tasks so for a second reason, the message doesn't apply to you.
You may well get BRP4 tasks in future. If so, they will be the new data format and, since you are not using app_info.xml, there is absolutely no reason for you to be concerned in any way. All necessary changes will be handled automatically. The whole purpose of Oliver's message was to warn people who were running BRP4 tasks under AP that they would need to make manual adjustments to app_info.xml if they wished to continue with BRP4 work.
The much more important thing you should be worrying about is why ALL the tasks you received BEFORE the three S6Bucket tasks, finished with computation errors. Your computer is quite ancient (SSE only) and it seems to be having difficulty with FGRP and BRP4 CPU tasks, which tend to be quite demanding. Perhaps you should check for overheating. In any case you should consider disabling BRP4 CPU tasks because they would take an extremely long time to crunch on your hardware and you risk losing all that time to comp errors anyway. Perhaps GW tasks only is the best choice for your machine.
Quote:
A healthy dose of head sup! would be 'preciated here.
FWIW: I'm not using an app_info.xml file (just running the generic stuff that gets servered).
RE: Final notice: we expect
)
- posted 12 Mar 12 ~1714
Really. Gig's up in 24 hrs, eh?
Then how comes I gots me 3 - as I'm lookin' at my screen right now (count 'em) - S6Bucket WU's to crunch? And the server is showing ~77,000 S6 Bucket WU's still waiting to be served. And that's not even including the other two - nonBRP4 - type applications.
A healthy dose of head sup! would be 'preciated here.
FWIW: I'm not using an app_info.xml file (just running the generic stuff that gets servered).
We did have two transitions
)
We did have two transitions recently, that are technically independent:
- S6Bucket -> S6LV1
- 8Bit -> 4Bit BRP4 data
If you are using the 1.22 version of BRP4 Apps, you shouldn't notice anything of the second one, the new data files end in ".bin4" instead of ".binary", that's all. This just happens to coincide with the other app transition.
BM
BM
Thank you, I have switched to
)
Thank you,
I have switched to previous driver 285.62 and everything goes well now.
Rene
RE: RE: Final notice: we
)
If you had read Oliver's message a bit more carefully, you might have noticed the "If you are using an app_info.xml" and "BRP4 v1.22 or later". You are NOT using app_info.xml so the message doesn't apply to you. You have received new GW tasks (S6Bucket) and NOT BRP4 tasks so for a second reason, the message doesn't apply to you.
You may well get BRP4 tasks in future. If so, they will be the new data format and, since you are not using app_info.xml, there is absolutely no reason for you to be concerned in any way. All necessary changes will be handled automatically. The whole purpose of Oliver's message was to warn people who were running BRP4 tasks under AP that they would need to make manual adjustments to app_info.xml if they wished to continue with BRP4 work.
The much more important thing you should be worrying about is why ALL the tasks you received BEFORE the three S6Bucket tasks, finished with computation errors. Your computer is quite ancient (SSE only) and it seems to be having difficulty with FGRP and BRP4 CPU tasks, which tend to be quite demanding. Perhaps you should check for overheating. In any case you should consider disabling BRP4 CPU tasks because they would take an extremely long time to crunch on your hardware and you risk losing all that time to comp errors anyway. Perhaps GW tasks only is the best choice for your machine.
Cheers,
Gary.