Author: Robert Hyatt
Date: 05:38:38 09/15/98
Go up one level in this thread
On September 15, 1998 at 07:17:34, Peter Herttrich wrote: >On September 15, 1998 at 06:24:51, Amir Ban wrote: > >>On September 15, 1998 at 04:14:17, Roberto Waldteufel wrote: >> >> >>>This has been a problem for me while developing Rabbit. I started out using a >>>16-bit DOS compiler, and I implemented Auto232 fairly successfully under DOS >>>when Rabbit was invited to play in FSV Summer98, although I had trouble with >>>Rabbit playing book moves too fast. Then I got a faster 32-bit Windows compiler >>>and ported Rabbit to that - my DOS program became a Windows program and Auto232 >>>has not worked since then. I am very interested to make Rabbit compatible with >>>some form of autoplayer so it can more easily participate in computer chess >>>tournaments, but I am completely stuck with Windows! >>> >> >>auto232 for Win32 is available free in source-code from from Stefan >>Meyer-Kahlen. Go back to the root of this thread. I think the purpose of the >>thread was that Stefan was trying to make this point crystal clear. >> >> >>>If a new protocol and interface is going to become available, I hope to support >>>it in Rabbit. My guess is that quite a few other programmers will be ready to >>>support it as long as it is easy to implement. I like the idea of a separate >>>interface and engine, but I would need to know exactly how to communicate >>>between Rabbit and the the Autoplayer. Has anybody actually started work on the >>>project yet? >>> >> >> >>There is no new protocol and interface planned by anybody. > >Amir, so i have a question to you: You will ignore for the future >the Windboard/Xboard interface/protocol ? > > >No way for a new protocol over a lan? >Sticking with old unstable/incomplete yunkie-232 Protocol? > >In the moment i get the impression, the better way has no chance, >because it's from the freeware-scene and not from the commercial >one. Sounds and smells very like Micro$oft behavier. > >1.000.000.000 flys can not go wrong, so eat more .... ? > >Amir, this is not a personal attack against you. It's against >the whole group, which favors the old RS232 Interface. > > >Hey, for the xth time, every stupid shoot-em-up-game is able, >to communicate through a lan. >We have 1998, not 1979. > >If every developer would glue at such old standards, where is >the progress? > > > > >> >>Amir > >Peter Here is my suggestion: download xboard. Look at the file engine-intf.txt and study the commands that are given. There is a set "to-engine" and a set "from-engine". I'll make a summary of this later today and post it here. Next, let's figure out if anything is missing. Then we can develop the following pieces of code: 1. an interface program for unix that will connect to an interface program for unix or windows to allow auto-play. 2. an interface program for windows that will connect to an interface program for unix or windows to allow auto-play. 3. (possibly) an interface program that will talk to a windows auto-232 program over a serial connection only. 1 and 2 will be able to connect via serial cable *or* lan, and will allow a linux program to talk to a windows program if needed... I will volunteer to write the unix interface program and distribute it. We need someone that can do something similar for windows. Then the problem is solved once and for all. Those wanting to remain with the old standard can do so. New programs can adhere to the more complete protocol. I already know of at least *one* commercial program that will support the winboard protocol in the next version. Perhaps we can convince others. But I do agree that "just because it is working and in use at present doesn't imply that it is satisfactory and should be left unchanged."
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.