Latest Version

[MikeAtBookup]

Chess Openings Wizard Professional for Macintosh - The latest version is Build 203 released May 6, 2024.

Chess Openings Wizard Express for Macintosh - The latest version is Build 190 released February 1, 2024.

Chess Openings Wizard Professional for Windows - The latest version is Build 201 released May 4, 2024.

Chess Openings Wizard Express for Windows - The latest version is Build 191 released February 2, 2024.

Android - The latest version is Build 66 released November, 2023.

iPad and iPhone - The latest version is Build 65 released November, 2023.


http://www.bookup.com/home/chess-openin ... am-status/ is the bug list and suggestion list for Windows and Macintosh.

http://www.bookup.com/home/chess-openin ... d-android/ is the bug list and suggestion list for Android and iPad.

[BIBLEFreak]

Update and the additional font features well received.

Update retained all settings, including watch files, ebooks, and file locations.

Keep up the great work Mike.

[phunt1_14]

The pieces are sticky in their movement.

[MikeCrockett]

Command menu allows you to clear rate symbols but no corresponding command to set them has been implemented.

Export for EDP seems a little funky, sometimes generating empty files, sometimes generating too much data. Hard to manage content.

Doesn't seem to interface well with Stockfish 7 x64 during EDP analysis.

Opening a book on program launch sometimes opens the same book several times.

[MikeAtBookup]

The pieces are sticky in their movement.

You can set the pieces to move instantly. I am working on better animation code that will make the pieces move more smoothly.

[MikeAtBookup]

Command menu allows you to clear rate symbols but no corresponding command to set them has been implemented.

Export for EDP seems a little funky, sometimes generating empty files, sometimes generating too much data. Hard to manage content.

Opening a book on program launch sometimes opens the same book several times.

I've never seen the program open the same ebook more than once. It should prevent that if you try to open the same ebook twice.

EPD files should be controlled by the selections you make; only positions not yet analyzed for example.

I'll have to check on the command to set the rate symbols.

Doesn't seem to interface well with Stockfish 7 x64 during EDP analysis.

I've heard other complaints about Stockfish 7 (and not earlier versions) and I'm not sure what the issue is.

[MikeCrockett]

The PGN Export "Export Comments" check-box does not function. The resulting PGN files are identical when checked or unchecked.

[MikeCrockett]

Doesn't seem to interface well with Stockfish 7 x64 during EDP analysis.

I've heard other complaints about Stockfish 7 (and not earlier versions) and I'm not sure what the issue is.

Mike - I think this issue goes beyond Stockfish 7. I went back to the earlier version that comes packaged with your install and got some bad analysis results. This may be a parsing issue within COW and how it interprets the engine responses. Perhaps a data buffer needs to be cleared ?

I took my original ebook and removed all previously generated pv computer evaluations. I then imported this clean ebook back into COW Windows Build 60. I requested the following engine parms to be set:

uci
setoption name Hash value 1024
setoption name Threads value 2

I asked to use engine: stockfish-18-32-ja

After computer analysis I exported the ebook back into PGN format and cut & pasted the first 25 lines of output... notice the pv scores repeat themselves on numerous lines:


[Event "?"]
[Site "?"]
[Date "????.??.??"]
[Round "?"]
[White "?"]
[Black "?"]
[Result "*"]

1. Nf3 e6 (1...Nf6 2. d4 (2. e3 e6 (2...c5 3. c4 (3. d4 {pv +80
stockfish-18-32-ja}) (3. a3 e6 (3...Nc6 {pv +80 stockfish-18-32-ja}) (3...d5
{pv +80 stockfish-18-32-ja}) (3...e5 {pv +80 stockfish-18-32-ja}) {pv +80
stockfish-18-32-ja}) (3. Nc3 Nc6 {pv +80 stockfish-18-32-ja}) (3. b3 d5
4. Bb2 Nc6 (4...g6 5. Ba3 Nbd7 (5...Qc7 6. Bb2 Bg7 7. c4 d4 8. exd4 cxd4
9. Nxd4 Qb6 (9...O-O 10. Nc3 (10. Be2 Ne4 (10...Rd8 11. Nc3 (11. Qc1 Bg4
(11...Qf4 12. Nf3 Bg4 (12...Nc6 13. Nc3 (13. O-O Bg4 14. h3 (14. d4 {pv +80
stockfish-18-32-ja pv 1.Nh4 Nc6 +32 stockfish-18-32-ja}) (14. d3 Qxc1 15. Rxc1
Nb4 16. Bc3 (16. Nbd2 Nxd3 17. Bxd3 Rxd3 18. h3 Be6 19. Nf1 {pv +80
stockfish-18-32-ja pv 1.Ne5 Bxg2 2.Kxg2 Re8 3.Nc4 Rad8 4.Rad1 Rxd6 5.Rxd6 +52
stockfish-18-32-ja}) {pv +80 stockfish-18-32-ja pv 1.Nxd6 Bxd6 +28
stockfish-18-32-ja}) {pv +80 stockfish-18-32-ja pv 1.Bxf6 Bxf6 -8
stockfish-18-32-ja}) {pv +80 stockfish-18-32-ja pv 1.Bf4 O-O -16
stockfish-18-32-ja}) {pv +80 stockfish-18-32-ja pv 1...O-O 2.Nc3 Nc6 3.e3 d5
4.Qxc8 Bxc8 5.Nxd5 Nxd5 6.Rxd5 Be6 7.Bxe7 Bxd5 8.Bxf8 Rxf8 9.Ng5 -36
stockfish-18-32-ja}) (11...a6 {pv +80 stockfish-18-32-ja pv 1...O-O 2.e4 Nc7

I'm going to keep looking at this to see if a work-around can be identified. I'll post again if I come up with something.

[MikeAtBookup]

Hey Mike,

I'm not at all clear what's happening. EPD analysis puts out the position only once. I suppose you could export the same set of positions more than once to the same EPD file and that would result in multiple lines of analysis for the same position.

Are you selecting to Erase the EPD file each time when exporting?

[MikeCrockett]

Hey Mike,

I'm not at all clear what's happening. EPD analysis puts out the position only once. I suppose you could export the same set of positions more than once to the same EPD file and that would result in multiple lines of analysis for the same position.

Are you selecting to Erase the EPD file each time when exporting?

Yes, I did erase the EDP file contents before beginning the update and I only ran the EDP update once.

What I think is odd, each PGN remark has two PV comments with the first one being repeated across the others. This makes me think the logic that is parsing the engine response has some data area that isn't being reinitialized between different EDP positions.

If you would like to send me a private email, I'll be happy to document the steps I took and upload the PGN files I used to create the issue.