Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ucdavis!egg-id!ui3!dickow
From: dickow@ui3.UUCP
Newsgroups: comp.sys.cbm
Subject: Re: chess programs
Message-ID: <60015@ui3.UUCP>
Date: Fri, 23-Jan-87 23:40:09 EST
Article-I.D.: ui3.60015
Posted: Fri Jan 23 23:40:09 1987
Date-Received: Mon, 26-Jan-87 01:36:44 EST
References: <285@oswego.UUCP>
Organization: MRC, University of Idaho
Lines: 35

A comment from Richard Kinne about a statement of mine...
>>In article <60009@ui3.UUCP> dickow@ui3.UUCP writes:
>>
>>...and once it [ChessMaster 2000] castled when the rook was threatened,
>>which I beleive is against standard rules.
>>
>>Bob Dickow, University of Idaho School of Music

>	Actually, the ruling for castling is that you cannot castle when your
>KING is threatened.  Your rook has nothing to do with it.  You also cannot
>castle accross check meaning if your KING has to cross a threatened sqaure
>you cannot castle. ......

Boy, is MY face red! After playing chess for years, I have discovered one
more subtlety of the game. Thanks for pointing this out. I recently asked
a friend about this, and he pointed me in the right direction too. After
thinking about it, I don't think I was actually even IN the playing position
under discussion, though I knew about the King-under-threat and castling-
squares-under-threat aspects of this rule. Also, now I have more respect
for my ChessMaster 2000 as a piece of programming...I already respected
its ability to clobber me more often than not.

Bob Dickow, (...egg-id!ui3!dickow)





           
  


			

----------