OliThink 5.1.1. released

[OliverBr]

http://home.arcor.de/dreamlike/chess/index.html

Changes to 5.1.0:

-Extension for passed pawns (after losing matches in endgame)
-Including SEE stuff to cut the qsearch-tree
-Clean exit via return from main instead of "exit"
-And the new logo on the page thanks to Jim Ablett

Oliver Brausch

[geots]

http://home.arcor.de/dreamlike/chess/index.html

Changes to 5.1.0:

-Extension for passed pawns (after losing matches in endgame)
-Including SEE stuff to cut the qsearch-tree
-Clean exit via return from main instead of "exit"
-And the new logo on the page thanks to Jim Ablett

Oliver Brausch

This version does the same thing as 5.1.0- wont move on 32 bit system. Jim Ablett fixed 5.1.0 so it would work- do you think you or he might possibly do the same thing for 5.1.1 (Read his threads about 5.1.0, and you will see he said it would not move for him either till he gave it a fix.)

Best,

[OliverBr]

http://home.arcor.de/dreamlike/chess/index.html

Changes to 5.1.0:

-Extension for passed pawns (after losing matches in endgame)
-Including SEE stuff to cut the qsearch-tree
-Clean exit via return from main instead of "exit"
-And the new logo on the page thanks to Jim Ablett

Oliver Brausch

This version does the same thing as 5.1.0- wont move on 32 bit system. Jim Ablett fixed 5.1.0 so it would work- do you think you or he might possibly do the same thing for 5.1.1 (Read his threads about 5.1.0, and you will see he said it would not move for him either till he gave it a fix.)

Best,

Maybe something is strange/wrong with my win xp 32 bit. I now compiled olithink.c via command line and cannot run the executable on my system. I update the executable on my homepage. Please check if this executable now runs on your systems. Thanks!

Edit: I just downloaded the executable from Jim. It doesn't run on my win xp 32 bit and brings the same error as my command line executable, that doesn't run either. Maybe this has something to do with my processor (AMD 4600 64bit)?

[Jim Ablett]

int main(int argc, char **argv)
{
int i, ex = -1;
setbuf(stdout, NULL);
setbuf(stderr, NULL); < xxxx wrong

Should be

setbuf(stdin, NULL);

Jim.

[OliverBr]

int main(int argc, char **argv)
{
int i, ex = -1;
setbuf(stdout, NULL);
setbuf(stderr, NULL); < xxxx wrong

Should be

setbuf(stdin, NULL);

Jim.

Interesting... I changed this now. But do you have an explanation why it worked for me on my 32bit and seemed to work on linux and win 64bit even with the wrong setbuf?

[Jim Ablett]

int main(int argc, char **argv)
{
int i, ex = -1;
setbuf(stdout, NULL);
setbuf(stderr, NULL); < xxxx wrong

Should be

setbuf(stdin, NULL);

Jim.

Interesting... I changed this now. But do you have an explanation why it worked for me on my 32bit and seemed to work on linux and win 64bit even with the wrong setbuf?

Hi Oliver,

I/O buffering could already be disabled on your systems through an environment variable setting.

Jim.

[Jim Ablett]

Sorry Oliver, still getting a crash on exit with >

if (!strncmp(buf,"quit",4)) return -2;

Anyone with the same problem can use the exes on my homepage till it's fixed.
I compiled mine with ExitProcess() to get round the problem.

Jim.

[Jim Ablett]

Sorry, need to make a correction to my last post.

Oliver's binaries are OK. I only get a crash on exit when I
compile the latest src myself with Intel/MSVC.

Jim.