14.07.2021 Views

how to play chess endgames book

In this companion volume to Fundamental Chess Endings, Müller and Pajeken focus on the practical side of playing endgames. They cover all aspects of strategic endgames, with particular emphasis on thinking methods, and ways to create difficulties for opponents over the board. Using hundreds of outstanding examples from modern practice, the authors explain not only how to conduct 'classical' endgame tasks, such as exploiting an extra pawn or more active pieces, but also how to handle the extremely unbalanced endings that often arise from the dynamic openings favoured nowadays. All varieties of endgames are covered, and there are more than 200 exercises for the reader, together with full solutions.

In this companion volume to Fundamental Chess Endings, Müller and Pajeken focus on the practical side of playing endgames. They cover all aspects of strategic endgames, with particular emphasis on thinking methods, and ways to create difficulties for opponents over the board.

Using hundreds of outstanding examples from modern practice, the authors explain not only how to conduct 'classical' endgame tasks, such as exploiting an extra pawn or more active pieces, but also how to handle the extremely unbalanced endings that often arise from the dynamic openings favoured nowadays. All varieties of endgames are covered, and there are more than 200 exercises for the reader, together with full solutions.

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

66 How TO PLAY CHESS ENDGAMES

1 @e3 @d6 2 .i.e2 @e7 3 .i.d3 @d6 4 @f3

@e7 5@g4

Now the gS-pawn is protected and White can

move his knight.

s .. .tors 6 tog1 toh1 1 tof3 wd6

Now the black king is also tied to the protection

of the e5-pawn.

8 @g3 .i.e8 9 @f2 .i.c6 10 @e3 .i.d7 11 c4

bxc4 12 .i.xc4 .i.c8 13 a4 .i.b7 14 aS .i.c8 15

.i.d3! 1-0

Another good technical move. Of course 15

b5 also wins, but then 15 ... @c5 would have to

be taken into account. Anand wants to play b5

only on the next move and thus deprive Black

even of this slight hope. Ponomariov saw the

writing on the wall and resigned.

The next example is substantially more complicated:

I 6 ... .i.xf5? 17 @xfS loc7 18 .i.g7 loe8 19

.i.h8 (zugzwang) +- (Ribli).

17 srs .i.d318 .i.e7+@c719 loe3@c8 20

@g4 @c7 21 @h5 log7+ 22 @h6 toes

22 ... lof5+? fails because of the boxed-in

black king: 23 loxf5 .i.xfS 24 .i.xf6 +-.

23h4

Before undertaking any concrete action,

White improves his h-pawn's position, so that

if it comes down to a pawn-race the h-pawn

will have less distance to cover.

23 ... @cS 24 hS @c7 25 log2 @c8?

Under pressure, Illescas makes an error.

Since the king's best square is c7, he should

have made a waiting move with the bishop,

such as 25 ... .i.c2.

26 lof4 .i.c2 (D)

3.02

V.Kramnik - M.Illescas

Dos Hermanas 1997

First White should improve his knight, hence

his king must protect c4:

1 @d2! .ae4 2 .i.cl .i.g2 3 @c3.an 4 .i.h6

.i.g2 5 .i.f4 .i.fl

Now the knight can be transferred to e3,

where it defends c4:

6 lob2 00 7 lodl .i.g2 8 loe3 .i.e4 9 .i.h6

toes

Next the king moves back to the kingside:

10 @d2 loc7 11 we2 toes 12 ~r2 loc7 13

@g3 .i.d3 14@g4 loe8 15 @f4 .i.bl 16 lofS+

~d8

All White's pieces are now in their best positions

and the time has come to act decisively.

However, Krarnnik selects the wrong piece sacrifice:

27 .i.xf6?

27 log6! (Nunn) 27 ... hxg6 28 hxg6 @c7

(28....i.d3 29 g7 loxg7 30@xg7 .i.xc4 31 .i.xd6

.i.xb5 32 @f8 +-) 29 g7 loxg7 30 @xg7 .i.d3

31 @f7 .i.xc4 32 .i.d8+ @b7 (32... @c8 33 e7

.i.xb5 34 e8'& .i.xe8+ 35 @xe8 bS 36 .i.xf6 b4

37 @e7 +-) 33 @xf6 .i.xb5 34 @e7 c4 35

@xd6 c3 36 .i.f6 c2 37 .i.g5@c8 38 @e7 +-.

27 ... loxf6 28 @g7 loe8+ 29 @f7 loc7 30 e7

h6

30 ... .i.dl !? 31 h6@d7 32 Wf8 .i.c2 33 loe6

foes 34@f7 .i.g6+ 35 @f8 lof6 36 lof4 .i.e8 37

loe6 log4 38 log7 .i.g6 39 e8'lW+ .i.xe8 40

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!