good job +k for yoo
Can you tell me what service pack that version of XP is on ?Quote:
Joe, The one machine I'm having the problem on is XP and I tried a fresh CO2M8 folder (with no settings) and no clients running and I still get the access error.
Thanks prog4mer I appreciate that :DQuote:
you still do a good job for all this conquer players..!! respekt !! :pimp:
have a nice day !! ;)
Still getting the same error with the new test version. Windows XP service pack 3. I have included a screen print. I am very open to any other suggestions since I love this program. :confused:Quote:
This a test version of co2m8 for Ulfius and anyone who gets a error when they start the program.
Can you all please try it and let me know the results.
We are getting closer. It works until you try to close the Windows error message. If you click on the error report you get a txt file as follows:Quote:
Joe, Really strange now. When it first starts, it crashes and a Windows message comes up that the application must close, then 3-4 seconds later, the CO2M8 window opens and shows the client list. Unfortunately, clicking on Send Error or Don't Send closes CO2M8. I'm using XP Pro SP3 on that machine, but have another XP Pro SP3 machine that 1.54 works on (gremlins I guess).
<?xml version="1.0" encoding="UTF-16"?>Does this help? Once again I am running Win XP Home SP3, thanks again for your hard work. I love this program. :handsdown:
<DATABASE>
<EXE NAME="CO2m8.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="CO2m8.exe" SIZE="1064960" CHECKSUM="0xD0DA2962" BIN_FILE_VERSION="1.5.0.5" BIN_PRODUCT_VERSION="1.5.0.5" PRODUCT_VERSION="1.05.0005" FILE_DESCRIPTION="CO2 Account Manager Tool" COMPANY_NAME="MorningStar_Productions" PRODUCT_NAME="CO2m8" FILE_VERSION="1.05.0005" ORIGINAL_FILENAME="CO2m8.exe" INTERNAL_NAME="CO2m8" LEGAL_COPYRIGHT="MorningStar_Productions" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x10B658" LINKER_VERSION="0x10005" UPTO_BIN_FILE_VERSION="1.5.0.5" UPTO_BIN_PRODUCT_VERSION="1.5.0.5" LINK_DATE="09/21/2008 03:57:46" UPTO_LINK_DATE="09/21/2008 03:57:46" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="M8english.dll" SIZE="32768" CHECKSUM="0xF9BF4F4C" BIN_FILE_VERSION="1.0.0.49" BIN_PRODUCT_VERSION="1.0.0.49" PRODUCT_VERSION="1.00.0049" COMPANY_NAME="MorningStar_Productions" PRODUCT_NAME="M8english" FILE_VERSION="1.00.0049" ORIGINAL_FILENAME="M8english.dll" INTERNAL_NAME="M8english" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xE4AE" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.0.49" UPTO_BIN_PRODUCT_VERSION="1.0.0.49" LINK_DATE="09/19/2008 16:21:40" UPTO_LINK_DATE="09/19/2008 16:21:40" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x7D737C09" BIN_FILE_VERSION="5.1.2600.5512" BIN_PRODUCT_VERSION="5.1.2600.5512" PRODUCT_VERSION="5.1.2600.5512" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5512 (xpsp.080413-2111)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xF44A2" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5512" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5512" LINK_DATE="04/14/2008 00:11:24" UPTO_LINK_DATE="04/14/2008 00:11:24" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
TEST 3 WORKS GREAT!!! :handsdown::D:handsdown:Quote:
Well Ive come to the conclusion that the new encapsulation system just doesn't like some windows setups,
so what I'm going to do is release versions of co2m8 in both encapsulation formats.
The problem with the old format is that some virus detectors mark it as suspect.
But I guess if you can't get the new one working you would just have to risk the old one or not run the program at all.
Here is the final test, this is in the old format and I just want to confirm that it still works for those who were having problems.