@SatanicToothpaste
you can find most of the answers here; login and password are "guest".
the "binary" files as such for os 2.0 and greater aren't distributed yet, only the source files which you have to compile yourself.

and please, posting the same thing on different topics won't give you a quicker answer it may just upset people...


@robinsousa
due to the place where it gives you the error, the ndless binary as such may be compiled and can be probably (at your own risk) used
you just can as long you get this error not compile any "applications" yourself.

ok, then it's a more complicated problem.

msys either doesn't find the file or can't access it. The later may be because it is in C (Windows is sometimes very strange there)
so you could either try to move the files to D (if you have such a drive) or run msys as administrator.

As long as there seems to be nothing to gain with "0", you can as well add this "protection"
also everyone who really wants to experiment with it has probably no problems to set it "manually" at "0"

how did you get the source, because it's strange that os.h is missing.
it should be under /include

if you can compile ndless yourself, then yes but binaris exists only up to OS 1.7 as far as I now.

EDIT: I keep posting fraction of seconds after somone else...

All the tests now pass on OS 2.1.0 CAS and non-CAS.

A9A vs second

comments?

EDIT: noticed that the link was false... here is he right one