Quote: "so that it happens >50% of the time at least"
I can't I'm afraid as I said earlier it happens about 1 in 4 times but I can give you as much information as possible:
My system spec:
Intel(R) Pentium(R) 4 CPU 3.20GHz
6GB RAM
32 bit Windows Vista Business SP1
ATI FireGL V3100 Display adapter
DBPro:
Version 1.073
Upgrade 7.3
Plugins:
BlueGUI
DarkAI
DarkPhysics
D3DFunc.dll
DBProMultiplayerPlusDebug.dll
DBProODEDegbug.dll
DKAVM.dll
DKShop.dll
EZrotate.dll
gui2.dll
Matrix1Util_01.dll -> Matrix1Util_32.dll
printer.dll
SC_Collision.dll
ShaderData.dll
ZappoPrint.dll
Error report:
PARSER ERROR
------------
UNDEFINED PARSER ERROR
PROGRAM TRACE
-------------
ERROR TRACE
-----------
Failed to 'CFileBuilder::AddPCKToEXE'
Also running:
and...
Steps to reproduce:
1-Compile any DBPro code. The larger the amount of code the more often it happens so perhaps if you can get up to about 10,000 lines it might make it happen 50% of the time I'll try it tonight and edit this post with the results.
That's about all I can think of for the time being (anything else that might help?).
I'm sorry if you feel I'm being stupid or facetious, I am not trying to be either.
Quote: "For instance, I didn't go after Microsoft because the desktop search blocked Visual Studio from saving to a .cpp file. I didn't go to TGC because the AV blocked the DBPro compiler from updating the .exe I was compiling. I didn't go to Sun because one of the AV/search blocked Open Office from saving to a .odt document."
Perhaps you should have. Some companies, such as the one I work for will actually try to come up with a workaround if enough of their customers have a problem such as this. We have fixed several compatibility issues which were not directly down to our own software.
I am sorry if I have annoyed you by feeling that other companies should operate like ours when it is not necessarily the most obviously cost effective way of doing business. Our customers do like us though (most of the time).