i'm doing this: setting up d3d with the render target being a backsurface of the primary. now i change the display mode and scrap all of the surfaces, create new surfs and reset the render target. d3d farts... my computer freezes (or overheats? puzzling.. temperature differences in computers are so minute...), and i spend the next 2 minutes watching the windows logo... In any case, what am i missing? i'm assuming the problem happens when i release the surfs, because d3d used to say "render target buffer lost". i didn't think much of it. giving it a new render target should clear up the problem, or not? also, setrendertarget increments the ref count for that surf right? do i JUST release it twice? or is there a way to kiss it off from d3d? what's the proper procedure? Thanks in advance, Alex. Forgot to add, i'm sure the surfs that are created are all fine... the error occurs later in the code. Edited by - AlexM on 2/6/00 10:39:16 PM Edited by - AlexM on 2/7/00 10:31:21 AM

somebody please answer this? i haven''t got a clue right now...