A program, probably the one you are writing, is throwing an exception that Windows then catches and throws back at you. Hard to say exactly where it is without more info. I often get this type of error when I don't correctly handle my input/output of files correctly. (A common occurance during testing, for me.)
If you can't fingure out where this is coming from you may have to do some debugging. There is an excellent two-part article at Bytamin-C's site (see
for part one). James P. Cottingham
I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that I am now qualified
to do anything with nothing.
For example, could it come from a TBitmap.SaveToFile(XXXX) in a directory where there is about 1000 or 2000 files? or a memcpy where I copy too much data for the ptr I use?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.