Board index » cppbuilder » Application Error presumably caused by C++ Builder Direct...

Application Error presumably caused by C++ Builder Direct...

Has anyone seen an EAccessViolation in module wininet.dll when C++ Builder
Direct tries to fire?  It kills the IDE if you OK the Application Error
messagebox.  Any way to shut off the Builer Direct applet?  Any known
workarounds or fixes?

Thanks,
Joe

 

Re:Application Error presumably caused by C++ Builder Direct...


Quote
>>Has anyone seen an EAccessViolation in module wininet.dll when C++ Builder

Direct tries to fire?

No, sorry. Could be some other installation messed up wininet.dll or other
DLLs.

--
Kent (TeamB and TurboPower Software)
C++Builder Developer's Journal (http://www.reisdorph.com)

Re:Application Error presumably caused by C++ Builder Direct...


On Tue, 26 Oct 1999 08:51:46 -0700, "Jon Doe" <jon...@anyaddress.not>
wrote:

Quote
>Has anyone seen an EAccessViolation in module wininet.dll when C++ Builder
>Direct tries to fire?  It kills the IDE if you OK the Application Error
>messagebox.  Any way to shut off the Builer Direct applet?  Any known
>workarounds or fixes?

IIRC,  there were a couple users who were behind some firewall software
which had similar problems.  I do not know what their final resolution was,
but it seems that only a few people which happen to be using a custom
WININET.DLL file seem to be having this problem so far...

I do not know of a work-around without replacing the custom (bad?)
WININET.DLL file with the original Windows one.  Be aware that doing this
might cause one's firewall to stop functioning properly (if it is using a
function which only resides in the custom DLL)...

Jerry Bloomfield (TeamB)
--
Jerry Bloomfield                                     JersW...@wwa.com
Proud Member of Borland's TeamB
"We'll do anything if you don't pay us."

Other Threads