Classic British Flight Sim

Yo Pop-Pickers..

I've recently started using my flightsim pc again (as opposed to the old dog I use day-in, day-out) and it's been giving me one of those famous M$ error screens then closing. No idea why but on checking the last twice it's happened, I found the text file that it wants to send to M$. Here's a bit of it...

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="fs9.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="cabdir.exe" SIZE="167936" CHECKSUM="0xC0B39D43" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="05/31/2003 22:15:25" UPTO_LINK_DATE="05/31/2003 22:15:25" />
<MATCHING_FILE NAME="ChilkatZip.dll" SIZE="585728" CHECKSUM="0x4F16B745" BIN_FILE_VERSION="9.9.3.0" BIN_PRODUCT_VERSION="9.9.3.0" PRODUCT_VERSION="9, 9, 3, 0" FILE_DESCRIPTION="Chilkat Zip ActiveX Component" COMPANY_NAME="Chilkat Software, Inc." PRODUCT_NAME="Chilkat Zip" FILE_VERSION="9, 9, 3, 0" ORIGINAL_FILENAME="ChilkatZip.DLL" INTERNAL_NAME="ChilkatZip" LEGAL_COPYRIGHT="Copyright 2000-2002, Chilkat Software, Inc." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="9.9.3.0" UPTO_BIN_PRODUCT_VERSION="9.9.3.0" LINK_DATE="09/18/2003 14:56:20" UPTO_LINK_DATE="09/18/2003 14:56:20" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="ChilkatZip2.dll" SIZE="1515520" CHECKSUM="0x8D02E640" BIN_FILE_VERSION="12.1.0.0" BIN_PRODUCT_VERSION="12.1.0.0" PRODUCT_VERSION="12, 1, 0, 0" FILE_DESCRIPTION="Chilkat Zip ActiveX Component" COMPANY_NAME="Chilkat Software, Inc." PRODUCT_NAME="Chilkat Zip" FILE_VERSION="12, 1, 0, 0" ORIGINAL_FILENAME="ChilkatZip.DLL" INTERNAL_NAME="ChilkatZip" LEGAL_COPYRIGHT="Copyright 2000-2005, Chilkat Software, Inc." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="12.1.0.0" UPTO_BIN_PRODUCT_VERSION="12.1.0.0" LINK_DATE="09/03/2005 20:45:00" UPTO_LINK_DATE="09/03/2005 20:45:00" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="cs707_uninstal.exe" SIZE="85785" CHECKSUM="0x7958A15" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/05/2000 07:40:44" UPTO_LINK_DATE="07/05/2000 07:40:44" />
<MATCHING_FILE NAME="csC130J_uninstall.exe" SIZE="63199" CHECKSUM="0x5603ED80" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="08/26/2005 18:19:06" UPTO_LINK_DATE="08/26/2005 18:19:06" />
<MATCHING_FILE NAME="csC130_uninstall.exe" SIZE="62375" CHECKSUM="0x16F50EF" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="08/26/2005 18:19:06" UPTO_LINK_DATE="08/26/2005 18:19:06" />
<MATCHING_FILE NAME="DFA36FloatplaneUninstal.exe" SIZE="81394" CHECKSUM="0x41A236B5" ...........

This ring any bells with anyone out there??? What the hell is a GRABMI_Filter when it's at sea?? :think:

ATB

DaveB :tab:

This is whats causing the problem Dave....

Chilkat Software, Inc

What ever has been installed from this lot has added something to driver.cab that doesn't work properly. Any ideas what it could be?

This is what it is.. Its a module that software developers can use, Its probably been installed as part of something else...

Chilkat SSL COM Component License: Freeware

Chilkat SSL is a free COM component that makes it extremely easy to communicate securely over a TCP socket using either the SSLv3 or TLSv1 protocols. This component is designed to be used by C++ applications, and cannot be used from Visual Basic or ASP.

[/quote]

Honestly.. err.. NO I'll have a look and see what's on the end of it!!

Tks for that

EDIT: That particular file is from ActiveSky2004 Ben (which I still have installed.. well, ver 4.5 anyway. I'll bin it and see what happens
ATB

DaveB :tab:

Hi Ben,

Well.. I removed all that cr@p and got this instead...

<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="fs9.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="cabdir.exe" SIZE="167936" CHECKSUM="0xC0B39D43" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="05/31/2003 22:15:25" UPTO_LINK_DATE="05/31/2003 22:15:25" />
<MATCHING_FILE NAME="cs707_uninstal.exe" SIZE="85785" CHECKSUM="0x7958A15" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="07/05/2000 07:40:44" UPTO_LINK_DATE="07/05/2000 07:40:44" />
<MATCHING_FILE NAME="csC130J_uninstall.exe" SIZE="63199" CHECKSUM="0x5603ED80" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="08/26/2005 18:19:06" UPTO_LINK_DATE="08/26/2005 18:19:06" />
<MATCHING_FILE NAME="csC130_uninstall.exe" SIZE="62375" CHECKSUM="0x16F50EF" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="08/26/2005 18:19:06" UPTO_LINK_DATE="08/26/2005 18:19:06" />
<MATCHING_FILE NAME="DFA36FloatplaneUninstal.exe" SIZE="81394" CHECKSUM="0x41A236B5" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/16/2003 14:15:18" UPTO_LINK_DATE="12/16/2003 14:15:18" />
<MATCHING_FILE NAME="DFA36R1Uninstal.exe" SIZE="90030" CHECKSUM="0x41A236B5" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/16/2003 14:15:18" UPTO_LINK_DATE="12/16/2003 14:15:18" />
<MATCHING_FILE NAME="DFA36RC2UpdateUninstal.exe" SIZE="75430" CHECKSUM="0x41A236B5" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="12/16/2003 14:15:18" UPTO_LINK_DATE="12/16/2003 14:15:18" />
<MATCHING_FILE NAME="dw15.exe" SIZE="186696" CHECKSUM="0x2487C3F" BIN_FILE_VERSION="10.0.3912.0" BIN_PRODUCT_VERSION="10.0.3912.0" PRODUCT_VERSION="10.0.3912" FILE_DESCRIPTION="Microsoft Application Error Reporting" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft Application Error Reporting" FILE_VERSION="10.0.3912" ORIGINAL_FILENAME="DW.Exe" INTERNAL_NAME="DW" LEGAL_COPYRIGHT="Copyright© Microsoft Corporation 1999-2001.  All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x33007" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="10.0.3912.0" UPTO_BIN_PRODUCT_VERSION="10.0.3912.0" LINK_DATE="03/13/2002 17:08:05" UPTO_LINK_DATE="03/13/2002 17:08:05" VER_LANGUAGE="Language Neutral [0x0]" />
<MATCHING_FILE NAME="ebueula.dll" SIZE="73779" CHECKSUM="0x14C3B55C" BIN_FILE_VERSION="1.2001.7.3001" BIN_PRODUCT_VERSION="1.2001.7.3001" PRODUCT_VERSION="1, 2001, 7, 3001" FILE_DESCRIPTION="EulaDll" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft Corporation EulaDll" FILE_VERSION="1, 2001, 7, 3001" ORIGINAL_FILENAME="EulaDll.dll" INTERNAL_NAME="EulaDll" LEGAL_COPYRIGHT="Copyright © 1998-2001 Microsoft Corporation" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1C10E" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.2001.7.3001" UPTO_BIN_PRODUCT_VERSION="1.2001.7.3001" LINK_DATE="05/28/2003 03:02:44" UPTO_LINK_DATE="05/28/2003 03:02:44" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="fs2000.exe" SIZE="33792" CHECKSUM="0x106806E9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="04/03/2003 00:19:42" UPTO_LINK_DATE="04/03/2003 00:19:42" />
<MATCHING_FILE NAME="fs2002.exe" SIZE="33792" CHECKSUM="0x106806E9" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="04/03/2003 00:19:42" UPTO_LINK_DATE="04/03/2003 00:19:42" />... e t c

Seems it's finding something new to pick on each time :roll:

ATB

DaveB :tab:

I am not an expert Dave, but I think something is b*ggered

Have to agree with TV, doesn't look good dave. Nothing been installed lately?

Given the number and variety of installations mentioned in that error report, I would hazard a guess that its some common component - perhaps related to payware?

Looking for that GRABMI_FILTER_PRIVACY error on the web, just about every possible application seems capable of causing it.

One of the few FS2004 specific suggestions for curing it (but not proven to work) was:

"Go into My Documents/Flight Simulator files and delete the default flight.
Then start up FS9 and create a new default flight. "

Believe it or not, that is what I've just done (well.. in a manner of speaking.. I deleted the FS9.cfg and built a new one) and I managed to get far enough in a default Cessna to doze off. Thank goodness that wasn't a live VA flight! :k:

I CBA to fault-find now but will continue digging tomorrow Strange but I never thought I'd be considering a 'reinstall' of FS9 with FSX on the shelves

ATB

DaveB :tab:

DaveB wrote:

........ Strange but I never thought I'd be considering a 'reinstall' of FS9 with FSX on the shelves

ATB

DaveB :tab:

Hi Dave
I was in a electronics store the other day, browsing around
looking at the newest Saitak controllers I noticed two people
who had crossed my path with copies of FS 2004 in their paws
, I asked them why did they choose 2004 over FSX.......

"the reviews on the web said to many problems with it and the price",


I wonder where they got their informantion from



Now in all seriousness I hope you do sort your problem