Author: Andy McFarland
Date: 02:30:24 11/14/97
Go up one level in this thread
>I am definitely interested. Auto232 is the only semi-standard now, but >it doesn't do error-checking, is cumbersome to set up, and has different >problems with different programs. As far as I know it was originally >done from the outside in, by putting keystokes into the programs buffer, >and taking over the Standard I/O to reroute the "displayed" info to the >serial port. So a different driver has to be written for each program. >If you can convince a majority of the programmers to agree to an >interchange protocol (perhaps ICS or a superset or subset thereof), and >implement an ergonomic product that, for example, alternates sides in a >multi-game match, allows for restarting interrupted games, makes sure >both programs are ready if it is a new game, tests the connection and >reports on both sides, controls the clock and updates the programs, and >interfaces to ICC and FICS/Chessnet, I'd buy it in a flash, and I don't >think that I'm the only one. I am thinking about DDE, a shared file, or supplying a Windows .DLL as the method of communication with the chess playing program. The communication with the opponent could be a null modem, modem, TCP/IP, or connection through a chess server such as ICC. I have never used Auto232, but have some idea what information needs to be exchanged. I am very willing to be a part of a group that defines the protocol between opponents. Whatever software I produce will not support chess.net, will support ICC, maybe support FICS. I am not looking to sell my software to the non commercial chess playing programs or even to the commercial programs except if they want to redistribute my program. Andy
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.