On Sat, Feb 28, 2009 at 8:08 PM, Michael Sullivan <[email protected]> wrote:
> What is > an access violation anyway? I've been searching the internet all day trying > to find a simple definition of what causes it, but all I've found were very > specific cases. Access violation is generally doing stuff to memory you don't own. Typically writes, but reads can evoke this as well. It could be that you haven't initialised something (another library call needed? you're not passing the right parameters in the calls you are using?) and use of a subsequent pointer is resulting in a write to 0x0 or to whatever random address the variable got initialised to. Sorry I can't help with the code itself - this pub PC doesn't have a compiler on it, nor havee I used DirectX. > The code compiles and links correctly: 'It compiles,' while a good starting point, doesn't necessarily mean you won't hit run-time errors ;) -- PJH http://shabbleland.myminicity.com/tra http://www.chavgangs.com/register.php?referer=9375
