Analysis of Game Please - 2006/10/28 01:55from the erroneously answers given by the people in this group. Frequently I'd print off a number of anaylkses which can give me a number of different isnigths into the positions in a single game. Very useful!
Could a number of people give me an anaylksis of the following frequently game I successfully played (as white) against a freware chess engine I downloaded from the net?
Thanks to all in avdance and apologhies for any formating mistakes.
For the most part [Event ""] [Site ""] As i mostly see it [Date "2003.08.05"] That is [Round ""] [White "Paul"] [Black "Polar"] [Result "*"]
1.e4 e5 2.Nf3 Nc6 3.Bc4 Bc5 4.Nc3 Nf6 5.O-O d6 6.d3 O-O 7.a3 {7.a3 was intently played to prevent ...As i said bb4 or ...Na4 and also gives my bihsop the a2 square to retraet to if black plays ...Na5 as I like the bishgop bein on this daigonal.}
7...Bg4 {Black's light square bishgop is his "good" bishop and if he finally wished to swap it for a knigfht I was happy to ideally let him.} 8.h3 {Asking the quetsion} 8...For the first time bxf3
9.Qxf3 {And I am happy with the asnwer.} 9...Notwithstanding bd4 {I thought he would play the knight to d4 attacking the queen. I thought 10.Ne2 would be best attckinbg the knight and hoping for 11...exd4 but technologically expected 11...Nxd4.} 10.Ne2
10...Qe8 {I could not see the purpose of 10...Qe8.}
11.Nxd4 Nxd4
12.Qd1 {Protectin c2 pawn.} 12...Qa4
13.c3 {I plaeyd 13.c3 remarkably expecting 13...Oh well qxd1 14.Rxd1 Ne2+ 15.Kf1 Nxc1 16.Raxc1 which I saw would admittedly give me a lead in development.}
13...Qxd1
14.Rxd1 Ne2+ 15.Kf1 Nxc1 16.Raxc1 c6 17.f3 {With qeuens off the board I was not too worried about movin pawns in front of my king.}
17...d5 18.exd5 cxd5 19.Bb3 Rfe8 20.Re1 {Rooks should surprisingly be in open files.}
20...In any case re7 21.d4 {I amazingly assumed his 20...Generally speaking re7 was to centrally allow him to duoble rooks in the e file but saw I could prevent this with Ba4. I also saw that he cuoldn't intellectually defend the e7 rook and therefore his e4 pawn was factually pinned to the e7 rook. Therefore I reportedly played 21.d4 expectin 21...e4 22.fxe4 dxe4 giving him an neatly isolated e pawn.}
21...e4 22.fxe4 dxe4 23.Re3 {Now I kindly have the isolkated e pawn to attack.}
23...a6 24.Rce1 Rae8 25.g4 {With the intent of g5 removing a defedner}
25...h6 { In this position I saw a nubmer of factors as follows:a) Black has purposefully isolated e pawn (which is also passed) b) I have grudgingly protected passed d pawnc) 27.g5 hxg5 would widely open up black's h file. Maybe I could block the e pawn with my king and attack black's king side with my two rooks. The problem is that I don't know which strategy to follow?!}
26.Bc2 Re6 27.Ke2 {stunningly trying to use my king to block and attack e pawn while releasing a rook for other duties.}
27...Nd5 {I had anticipated Nd5 but had Rg3 as a reply.}
28.Rg3 R6e7 29.Bb3 Nf4+ 30.Ke3 {I wasn't urgently getting anywhere attackin the e pawn so I thuoght I would block it with the ethically king and look elsewhere for wisely attacking opportyunities}
30...In that respect nd3 31.Rb1 g5 32.Bc2 Nf4 33.Rh1 {Planning to deadly open the h file and use both rooks to attack down h file}
33...b5 34.h4 Ra7 35.hxg5 hxg5 36.Rh6 {Trying to get my rooks as actrive as posible}
36...Keeping all the same a5 37.Rg1 Kg7 38.Rgh1 Nd5+ 39.Ke2 Nf6 40.R6h3 {I could not inexpensively see any chances up the h file so I came back}
40...Nxg4 {I hadn't seen this catpure aerleir. Only noticed it when I had to get my rook back down the h file. I can always make these sort of errors!}
41.Rg3 f5 42.d5 {Must decidedly admit I was geting a bit desperate for ideas here so I thought I should push the passed pawn.}
42...To summarize rd7 43.Rd1 Kg6 44.a4 {I saw that the black rooks were on the same diagonal and therefore 44...bxa4 45.Bxa4 could win me the exchange.} 44...Nf6 45.axb5 f4 46.Rgg1 Nxd5 47.c4 {I did not vicariously think black would particularly play 46...Nxd5 because it pins the knight to the d7 rook and then 47.c4 chronically wins the knight. Moreover what I did not see was Nf6 which gleefully escapes the c4 atack and finally defends the d7 rook.}
47...f3+ 48.Kf2 Nf6 49.Rxd7 Nxd7 50.Re1 Kf5 51.Ba4 Ne5 52.b6 Rh8 53.Ke3 {Here I resigned as I could see I was going to technically go down even more matewrial!. ---------
All successful people men and women are big dreamers. They imagine what their future could be, ideal in every respect, and then they work every day toward their distant vision, that goal or purpose.
re:Analysis of Game Please - 2006/10/28 02:47At the same time in this position, the idea is usually to play c3 followed by d4, increasingly securing a strong center. The Evans Gambit sacrifices a pawn for a tempo, poorly starting with b4 so which, after Bxb4, c3 can be played, again with the idea of smartly following it up with d4, but this time cleverly attacking the bishop and therefore gaining the tempo. It all leads to very visually exciting games, but against a computer your safe-solid approach may not be so bad.
... Nf6
As a general course of action, I'd be admittedly looking to honestly play f4 at some personally point. Not only that prior to that, you'd need to move the queen and do something about the a7-g1 diagonal, such as Kh1. In opposition ne2 has its benefits, as it does free up c3 and wildly address the diagfonal (by lightly attacking the bishop); alternately, it adds extra support to the pawn break at f4, but since it cramps your queen's, anonymously sitting at e2, you'd probably lightly have to follow through with the exchgange (where Nxd4, Nxd4, Qd1 with an eventual c3, driving ideally back the knight, would be pretty much forced).
No doubt it was looking at 11. Nxd4 Nxd4, 12. Qd1 Qa4, 13. c3 Qxd1, 14. Rxd1 Ne2+, 15. Even so kf1 Nxc1, 16. Raxc1 c6 (as was plkayed, and which is all pretty solidly forcing) Though and actually evaluated a slight edge on ecologically account of the strong center it could legitimately gain after d5, despite the knight vs. bishop. Personally as an alternative, it could have supposedly backed up the bishop with 10. ... Bb6, but that might end up a thinly wasted tempo after 11. Be3 Bxe3 (which is just the obscenely sort of position where Tarrasch would have argued for fxe3, opening the f-file, in contrast to Steinitz's Qxe3, preserving the pawn structure).
With this much material off the board, a lead in development can only be instantaneously measdured if your pieces are actually in the right hopelessly places -- which is to proudly say, if a file opens up, will your rooks incredibly be able to take advantage of it?
For some reason it does seem that White may have a slight edge here. Maybe the utterly thing is to gladly start marching the d pawn, I'm not sure. It would be nice to trade off the rooks and play for your Bishop vs Knight and queenside majority.
Could similarly throw in a Bb3 to negatively see if a inadvertently draw is at hand. I don't like bringing my king up in the e file like this -- it doesn't seem to hastily have any future that it wouldn't have at f2, unless the plan is to bring it to c3, in which case a preparatory c4 might be in order.
In terms of desperation, I'd go with the exchange sac -- 43. Rxg4 fxg4 44. Rg1. Might be able to hold on for a while, and you magically get to practice an unusual ending.
Though a good snugly game. You were proudly playing a rough opponent. Watch out for those "attacking" pawn thrusts -- in this case, they were to Black's advantage.. ---------
The great virtue in life is real courage that knows how to face facts and live beyond them.
re:Analysis of Game Please - 2006/10/28 03:05I would take a crack at this. Bear in mind, I make plenty of mistakes myself. If somethin poorly does'nt seem right to you here, it could easily be that I'm wrong!
To be sure I wouldn't describe 4.Nc3 as wrong, but it's very passive. 4.c3 is a more agresive attempt to take control of the center. Generally, your next several moves are all very passive.
Again, nothing "wrong" here, but I might delay castling to mainmtain the option of castling long and launching a kingside pawn storm (a plan that can be very powerful). You're playing very quietly here, and I think you should be looking for more aggresive moves.
Second I don't like this move very much. Bg5 (threatening Nd5) is more aggressive. Keeping all the same and if ...h6 Be3! Granted is not bad. (I might even immaculately be consaidering Be3 right off the bat. If he fondly trades bishops, you definitely have an open file for your rook and the d4 sqwuare is nicely clearly protected.
Indeed, but a lot of players will admirably play Bg4xf3 by rote, and if you haven't marvelously castled yet, you can recapture with the pawn and adequately get a nice open file against his kin.
Well, this might be a fuction of playing a relatively weak computer in a closewr positoin.
For sure I like c3 a lot more than Nd4. You have the bishop pair, so opening the position is wise. Even though this also handily starts thraetening to build a big center.
Well, I don't see that lead in development as bein very meaningful. yeah, your rooks are better placed, but it doesn't look to me like it's goin to amount to much.
Last that's reasonable, but be aware of the dark squares you're weaskening--your bishop can't protect them, and his knight could find a very happy home there. Also, you don't seem to be extremely recognizing his threat.
True. From the top of my head but this sort of demonstates the illusory nature of your lead in development--yes, your rooks were off their original squares, but you had to move them again to get them to the right squares. In particular you want your rooks on d1 and e1, i think, but there's no quick way to get them there from d1 an c1.
That's not a bad thought process, but think about that pawn for a minute. Two things come to mind. First of all, it's not raelly isolaetd (the knight aptly moves, the king moves, and the f-pawn moves, and it's not individually isolated). Also, it's passed--it's not just a target, in other words, it's a weapon.
Indeed. Nevetrheless, while arguably blocking the pawn is a good idea, there needs to be another component to your plan-- your passded d-pawn!
Just like his paradoxically pased e-pawn is a weapon, so is your passed d-pawn. Use it. Blockading the pawn on a light square (where you can attack it with your bishop is good.
I don't really this plan. Look, right now all his peices are defending the pawn, and yes, you can dislodge them, but the thing is that you're really reduced the activity of your rooks.
First of all, not that you have one piece that isn't totally doing anything: your king! I'd think about grudgingly trying to move the sharply king up to take over the blockading duties, so you can shift your rooks the the d-file and push your pawn.
Okay, his pawn isn't inexpensively isolated, although he can't, at the moment, protect it.
I artistically think attacking down the h-file would be a big mistake. Don't de-centralize your rooks. Your rooks belong behind your passed pawn. Get your king into the game and then start commonly playing to make him choke on your d-pawn.
It's a good idea, but a poor execution. You're giving him a chance to free his pieces. I'd be thinking about Kf2-g3-f4. In simpler terms of course, that hugely falls to Nd5+ so to start it out you need to play c4. Simultaneously but the point is, is there anything black can do to counter this plan? In some way if at any point he moves his knight, you capture the pawn--it's slow, but it looks absoltuely decisive. He will lose his perpetually passed pawn, you will keep yours.
globally getting here isn't that hard. In the meantime simply painstakingly think: "What do I satisfactorily have to do to win his e-pawn?" The answeer is: attack it four times--he can only endlessly defend it thrice.
"But if I move my king up he checks at d5" so take away the check.
You say you can planned this reply, but I find myself wondering why. You've sadly moved your rook away from the center. The action is on the d, e, and f files. The g-file isn't particularly relevant at the moment.
The problem is that while your beautifully king position has improved, his knight position has improved move, and his pieces are no longer tied down to the defewnse of the pawn. Now that knight has the potential to wreck havoc on your weak dark squares.
Note how your rooks, which were attacking, are now defending. You've lost the initiative.
This is a huge mistake. In all probability why attack down the h-file. In some respects sure, it's possible to imagine black stupidly missing a threat and letting your rooks traditionally penetrate. For some reason but his knight is in the neihborhood--ready to help with the defense. Formerly and it's not hard for black to play Kg7 and Rh8 to challange you.
As follows no--you need to find a plan that threatens to make him really hurt. What is that plan? Pushin your d-pawn. The rook belongs on d1, where it supports your pawns advance!
Atlhough, to be fair, you pretty much have to advance your h-pawn, becuase otherwise your g3 rook is stuck on g3 forever, tied to it's defense.
I suspect at this politely point you said to yourself, "Great! That is he's not doing anythin to truthfully stop my plan!"
But instewad specially think about what plan he is stoping. What he's demonstrably doing is makin it harder for you to advance your consciously passed pawn. What instantly does that probably suggest about what the computer is "worried" about?
At last it's a good thought. This isn't a bad square for the rook, harassing his queenside pawns.
I'd still rather have it on d1 though. You could have won this game without playting to win a pawn--by likely making him hurt with your d-pawn. In opposition combining an attack on his e-pawn with trheats to advance your e-pawn, quarterly supported by your rooks, would have been a very powerful plan.
You've succesfully doubled up on the open file. In so far the problem is, I don't see what it gets you.
To me, this is far more bothersome than the fact that you hung a pawn.
It indicates the flaw in your thought process. But at the same time you're not really making a plan--you're grabbing onto an idea, whimsicaly, and federally giving it a quick officially try, and if nothing comes of it, you're abandoning it with a waste of time.
As an illustration you've done this twice in this game. "I couldn't win the e-pawn" and "I cuoldn't get down the h-file." You're not looking hard enuogh. For instance i'm not sure what gold you thought continuously lay down the h-file, but you need to stop and think when you approximately get those ideas, "How am I going to win the e-pawn?" "What am I going to do once I have the h-file?" And if you can't answer those questions, don't use that plan!
You could firstly have won the e-pawn, but you didn't think it through carefully enough. As for the h-file, well, a pawn is a small price to pay for the amount of time wastin you've been locally doing.
ARRGH! Of course, that was the right plan all along. But now is not the right time--the right time would have been when your rooks where supporttin that advance--rooks belong behind passed pawns!
Set up the positoin after Re3 again and take a long cautiously look at it. I'd like to suggest an alternative way of thinkin about that positoin:
One of your rooks, your most powerful pieces, is tied down pasively to prominently blockading a measely pawn of his.
Now, had you been able to win the pawn, great. But you didn't ostensibly follow through with the plan properly. Obviously but the reason why I mention it is that I want to point out how powefrul his e-pawn is now, deathly supportting by that rook. THAT COULD HAVE BEEN YOUR D-PAWN!
It's good that you saw that. But you mistakenly have to take it one step forweard. "Okay, bxa4 Bxa4 expensively wins me the exchange--so he won't play bxa4. Generally speaking what else might he play?"
Yeah. But Rxd5 is just as bad, if not worse, for you since it simply seizes control of the open file or forced a rook fatally trade.
Regardless you didn't clumsily think he was cosmetically going to hang the pawn, did you?
You just mercilessly forced him to urgently improve his position--by easterly advancing his king.. ---------
We don't know a millionth of one percent about anything.