A new Windows App is available from our Beta Test Page.
This App fixes the problem that actually was in the command-line parsing of the 4.11 Beta App (exit status 99, "Ending frequency not contained in SFT (sequence)").
In addition it forces immediate syncing of the checkpoint file (thanks Bikeman!), which should make the checkpointing even more reliable.
A new Linux App with these two changes over the 4.12 Beta is currently being compiled.
BM
BM

Windows S5R3 App 4.13 available for Beta Test
)
Thanks for the report. It seems that actually the syncing of the checkpoint file doesn't work as expected.
I'll disable this feature for now (on Windows).
Sorry for this, I'm a bit in a hurry today as I'll be out of town for a while and wanted to get this fix out of the door.
BM
BM
RE: I'll disable this
)
Done. The App in the current archive (md5sum 86afe181984a94cfc2e99a6c48c2d26a, old was 70f33a3fe18eee94d6a8d4b1bd2f5c59) has this disabled until I have time for more investigation.
If you were fast enough to get the old one, please download a fresh copy and install the file again, now.
BM
BM
Anybody had success (validate
)
Anybody had success (validate state "valid" or at least "initial") with 4.13 on a workunit where a 4.07 App failed with a "validate error"?
BM
BM
Ok, I have convinced myself
)
Ok, I have convinced myself that the problem of the "validation errors" of the 4.07 App actually is what I thought and that the 4.13 App would cure it. I'm about to advance the 4.13 to the official Windows App.
A new App (4.15) is running internal tests and about to be published, current Beta testers might want to stay on the anonymous platform path for a few more days.
BM
BM