469,903 Members | 1,506 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,903 developers. It's quick & easy.

After conversion to 2005 now I get an error on exit

I got my 2003 code to compile in (old syntax) 2005. It runs, except I now
HAVE to set my Form to DoubleBuffered or else my drawn primitive graphics
flicker like crazy (which I had handled in 2003 via manual double buffering,
which I now removed).

Anyway, the application works, but now exits with some sort of exception:

First-chance exception at 0x0097a0e6 in PAO_Tools.exe: 0xC0000005: Access
violation writing location 0x00000011.
The thread 'Win32 Thread' (0xbb4) has exited with code -1073740791
(0xc0000409).

The thread 'Win32 Thread' (0xc08) has exited with code -1073740791
(0xc0000409).

The thread 'Win32 Thread' (0x264) has exited with code -1073740791
(0xc0000409).

The thread 'Win32 Thread' (0xdac) has exited with code -1073740791
(0xc0000409).

The program '[1644] PAO_Tools.exe: Managed' has exited with code -1073740791
(0xc0000409).

The program '[1644] PAO_Tools.exe: Native' has exited with code -1073740791
(0xc0000409).

I have no idea how to go about tracking this, especially since my code
worked fine in 2003...

[==P==]

Nov 17 '05 #1
1 3011
I have more information. It turns ut my program exits without error if I
allow it to bring up the black console screen ala using the following:

int _main(void)
{
//application
}

for my main call. But if I disable it, ala:

int __stdcall WinMain(void)
{
// application
}

then it exits with an exception error. Why should bringing up the console
change whether it exits with an exception or not? Is there a new form to
'int stdcall WinMain()", a main() call that disables the console, which
replaces it? Note that I'm using 2005 express with old syntax turn on.

[==P==]

"Peter Oliphant" <po*******@RoundTripInc.com> wrote in message
news:uq**************@TK2MSFTNGP11.phx.gbl...
I got my 2003 code to compile in (old syntax) 2005. It runs, except I now
HAVE to set my Form to DoubleBuffered or else my drawn primitive graphics
flicker like crazy (which I had handled in 2003 via manual double
buffering, which I now removed).

Anyway, the application works, but now exits with some sort of exception:

First-chance exception at 0x0097a0e6 in PAO_Tools.exe: 0xC0000005: Access
violation writing location 0x00000011.
The thread 'Win32 Thread' (0xbb4) has exited with code -1073740791
(0xc0000409).

The thread 'Win32 Thread' (0xc08) has exited with code -1073740791
(0xc0000409).

The thread 'Win32 Thread' (0x264) has exited with code -1073740791
(0xc0000409).

The thread 'Win32 Thread' (0xdac) has exited with code -1073740791
(0xc0000409).

The program '[1644] PAO_Tools.exe: Managed' has exited with
code -1073740791 (0xc0000409).

The program '[1644] PAO_Tools.exe: Native' has exited with
code -1073740791 (0xc0000409).

I have no idea how to go about tracking this, especially since my code
worked fine in 2003...

[==P==]

Nov 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

14 posts views Thread by junky_fellow | last post: by
10 posts views Thread by Robert | last post: by
1 post views Thread by musosdev | last post: by
5 posts views Thread by Martin JÝrgensen | last post: by
3 posts views Thread by sony.m.2007 | last post: by
reply views Thread by Salome Sato | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.