🚀 go-pugleaf

Sounds like a situation where the programmer's credo applies:
reinstall and reboot. You don't mention if your development machine
is also the one you use for tests/demos, but I get the impression
the binaries crash on any machine.

If so, the problem is probably either a corrupted BCB or a corrupted
Windows. Reinstall BCB, or reinstall Windows if necessary.
Or rollback to a previous restore point if you have it.
Or perhaps a Windows Update?

Before you do anything drastic, though, ask yourself if there's a
pattern to your programs. Do they use threads? If they do, and you
don't synchronize your VCL controls, things like this may occur
(access violations, don't know about the long delays).

Or do they perhaps use browser/internet controls? It might be that
some pesky adware program has overwritten some dlls having to
do with this. Try using Ad-Aware - http://www.lavasoftusa.com -
to scan your system.

Troels


Evan Dorn wrote in message <3edc29ee$1@newsgroups.borland.com>...
>
>Hello!
>
>I'm developing a custom app for a client using OpenGL in BCB5.  Two days
ago, I went to run a demo of the app, which had been stable the previous
night.  It crashed partway through with an access violation like this:
>
>(Access violation at address 400341C7 in module 'VCL50.BPL'.  Read of
address 00000059)
>
>I've gone back and looked and since that error appeared I cannot get decent
behavior out of ANY program which uses VCL components.  Any attempt to draw
a VCL component takes at least 60 seconds, often longer, to appear onscreen.
In large programs, access errors like the above appear at strange times,
like while setting a variable or calling a function in code that has nothing
to do with VCL components.
>
>These errors occur when I recompile any VCL code, even things I retrieve
from CVS that have been frozen and stable for months.
>
>Binaries compiled before two days ago do not exhibit these problems; they
run fine.
>
>I'm not aware of changing any settings.  I literally left the computer to
fall asleep after a night of coding; the code was stable at that point.  The
next morning, went back to the computer, hit F9 to see where i'd left off,
and the problem appeared.   I haven't been able to work on the code since
then.
>
>Tearing my hair out, would be extremely appreciative and gracious for any
help or suggestions!
>
>Thanks so much,
>Evan
>
>P.S.  If it matters, the machine is a gateway laptop running Win2k.  This
is the only windows machine i have easily available, and was loaned to me by
the client.