I can make a work around that is slower and does not give me the read error. So I thought about how to do this, the problem so far rears its ugly head on my Vista related systems, had not had a chance to work with a Windows 7 yet, but good chance it will show up there as well. So I was trying to figure out what function to call to figure out what OS I was running and got this response:
From IamM:
Quote: "That's not a smart way to deal with the problem - there's nothing specific about Vista that disables the reading of a surface, so your 'fix' would work right up until you encounter exactly the same problem with an XP or Windows 7 system.
See if you have anti-aliasing enabled in the drivers, and double-check that you are creating the surface correctly in the first place.
"
Big Question now. Is how do you create the surface correctly? I moved the quote from the original thread to here. Since the questions are similar in nature.
I am using this method:
dbCreateBitmap(1, nScreenXSize, nScreenYSize);
dbCreateBitmap(2, nScreenXSize, nScreenYSize);
nScreenXSize & Y are the screen size of the computer running the program.
Is there another way of formatting this that I should be aware of?
There are many answers but just one question" ~ Jerilith the Mad