its like a programme error of some kind, the player reged up and it (the software)glitched out somehow and they couldnt get back in, the other player just a minuate i'll get it
Last Night I bought into a $1,000 Bounty Game. Upon the game's start there was an error, but it did not stay on the screen I only caught a glimpse as the client completely blacked out, I had to shut down and come back in. The game then played fine until it sat me out, when the tables broke down to 2 tables. I couldn't play, I shut down and I could not log back onto the client. I paid either $15.50 or $16.50 to play this tournie. I found out this morning I was blinded off at Number 13.
So between Friday's $15 dollars spent for games that did not function correctly (the ladies game did) & last night was either $15.50 or $16.50.
That's now $30 I donated without wanting to donate. I don't have a problem buying into a tournie and not cashing, it happens (quite frequently). I do have a problem though spending $30 and not being able to play because of an issue out of my control and one I do feel is on your endThese errors regardless the cause* are becoming costly for me. I have lost $41.00 to date.

,,thats just apart of it heres another player,you ar not the only 1 with this problem

I got the same here with XXXXXX and vista on my comp, it happens a lot that i have
to reboot because the games hang !
not only in tourny's but also at ring games, i just get thrown ouit of them


there is an isseu with vista and merge, get a lot of error #3 and #9 and some times loose manifest ??same 2nd player

happens to me also and i am not playing badbeat rooms, this afternoon was playing the
625 teed and 1 ring game yellowstone, and got thrown out of the yellowstone in the
middle of a hand i just raised

lost the hand including the raise
its quit disturbing, and i am afraid to play any tourney or ring game now, this has
cost me enough money now.
besides it was a yellowstone table i started for the doubble cp and had to start a new table


and this is from someone elseI've been complaining about runtime error trap #3 since December 2007 on the Com site....You think they'd know what to do by now...






and theres a little more but thats the just of it all
