I beat my first chess engine.

This game was between myself and a chess engine by the name of Comet B68: 

The conditions were 2 hours to think for each side, at 40 moves each side gets an additional 40 minutes. No handicaps were used, the engine was at full strength. No other applications were open, I received no help. Just me vs Comet B68 at full power. 

Here's how it all started, a chess buddy told me that and chess engine could scrape any human. I told him that was false, so he challenged me to a one game showdown against this engine Comet B68. I actually have never heard of this engine before. Can anyone give me some information about it? Like, it's rating and so forth. Also, any insight on the game out be appreciated, anything I could've done better, ideas etc.    

Humans > Machines

Like a boss c:

A very nice classic engine, about 2380 to 2400 on the CCRL rating list. The engine has a few diehard fans. One of the Comet fans likes version A90 even better:  http://talkchess.com/forum/viewtopic.php?t=47102

Information on Comet:

http://wbec-ridderkerk.nl/html/details1/Comet.html

http://chessprogramming.wikispaces.com/Comet

As of right now it's rated 2397. I'll play another game with it, and post it. Maybe I just got lucky that time lol.

Comet blundered badly with 26...Bxd4. (It needed to play 26...Rxd4.) Not really what I'd expect from a 2400 engine.

What was the time control for the game, and what was the hardware? Also, are you using a configuration file? (COMET.ICS)

Edit -  Oh, nevermind on the TC question, you gave the TC. Yeah, with a long time control, it shouldn't have made that huge of a blunder.

I loaded up Comet B68 and the pgn file of your game on my system in an effort to duplicate the blunder. I tried three different config file scenarios: no config file, the stock config file that comes with the Comet download, and my modified config file that uses a larger hash table. In all three cases, when I analyzed Black's move 26, Comet chose 26...Bxd4 for the first second or two, but after that it locked onto 26...Rxd4 and never let loose of that move.

So I have no explanation for Comet's blunder in your game; By all rights, it shouldn't have made it. Did you install Comet as a Winboard engine?

Maybe you could try to duplicate the blunder and see if Comet blunders the move consistently on your system.

One last comment - I kept playing around with different ways to analyze the blunder with Comet, clearing the hash, dumping the learn file (which gets recreated when Comet starts up again). In a few attempts, Comet would start with 26...Bxd4, then after a couple of seconds it would switch to 26...Rxd4, then a couple of seconds after that, it would switch back to 26...Bxd4, then at a total elapsed time of about 18 seconds, it would switch back to 26...Rxd4 and stay locked on that move.

But at a time control where it's thinking for around three minutes for each move, it definitely shouldn't have blundered this move.

nice game