VBGamer

I had a problem with that too(maybe I still do... I haven't tried it without the fix since I got a new vidcard)... The problem I had seemed to be that SetDisplayMode was knocking DirectDraw out of exclusive mode. Even though both SetCooperativeLevel and SetDisplayMode return DD_OK, doesn't mean everthing is DD_OK!! :-) Even a call to CheckCooperativeLevel right before the offending line returned DD_OK. I think it may be a driver problem, but the solution is just to call SetCooperativeLevel again right before you create the primary surface. Seems to do the trick, and so far I've had no problems with it giving me "you've already set the coop level" errors. Another thing... On my machine it only happened when the app was compiled, and was totally fine in the VB IDE. Is that what it's doing to you too? Hope this whole mess gets cleaned up in DirectGraphics...