Author Topic: DFW for FSX Serious start up Issue  (Read 50923 times)

b787

  • Newbie
  • *
  • Posts: 3
Re: DFW for FSX Serious start up Issue
« Reply #60 on: March 12, 2011, 09:03:29 pm »
Yes , you are right but when I disable Bglmanx.dll in dll.xml this module (EZDOK) is working again!  ???

That doesn't mean it's a bglmanx.dll problem.

The most likely source of potential conflict between two modules, is the C++ runtime library that they were compiled with and how they signal to Windows this, by using an embedded manifest file. Our module use the VC++ 2005 (SP1) runtime, which is the same as used by FSX and of course includes a proper manifest file inside to tell Windows about this. Even if this info might not tell much to you, it might be helpful if you report it to EZDOK developers, maybe they'll have an idea what the problem could be.

Another thing you can try, is to rearrange the *order* of the modules in the DLL.XML, this could make a difference.

Rearranging the order of the modules in the DLL.XML did not help.

I reported your advice to EZDOK developer.

But here are my Microsoft Visual C++ 2005 Redistributable status on "Programs and Features" Win7 64:

Microsoft Visual C++ 2005 ATL Update kb973923 – x86 8.0.50727.4053   (250KB)
Microsoft Visual C++ 2005 Redistributable            (426KB)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022      (2.52MB)
Microsoft Visual C++ 2008 Redistributable – x64 9.0.30729.4148      (788KB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.21022      (3.51MB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148      (596KB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.17      (238KB)

Regards

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: DFW for FSX Serious start up Issue
« Reply #61 on: March 12, 2011, 09:20:42 pm »
Rearranging the order of the modules in the DLL.XML did not help.

I reported your advice to EZDOK developer.

But here are my Microsoft Visual C++ 2005 Redistributable status on "Programs and Features" Win7 64:

The installed runtimes don't look wrong. However, just being installed, doesn't ensure all their files are in good order. Since you have the latest version of the 2005 runtime (4053), try this alternate bglmanx.dll, with is linked against that one, and see if it makes any difference:

www.fsdreamteam.com/download/setup/bglmanx/4053/bglmanx.dll

If it doesn't, it's very likely an issue with EZDOK.

mikeallenbrown

  • Newbie
  • *
  • Posts: 3
Re: DFW for FSX Serious start up Issue
« Reply #62 on: March 29, 2011, 05:50:38 pm »
I'm new here ... but I too have this same issue. I admit, I didn't read every page here in this thread but skipped to the last couple pages. I thought it would be best to keep all this in the same thread, but, I can make a new one if that is what I should do.

I have registered copies of your JFK, PHNL, and Hawaii 1 scenery's....they all work great, zero issues. KLAS is installed but still in trial version.

I'm interested in buying DFW but get the bglmanx.dll warning. What is different with this package compared to the others?....soon as I delete DFW things are great. I once had ezDok installed but didn't like the product so I uninstalled it. I see that there is a bglmanx.dll alternate, but I am unsure where to put it.

Specs: Win7 64, FSX only, tons and tons of addons

Thank you.

Mike

EDIT: Also...I don't have nor use any anti-virus software

mikeallenbrown

  • Newbie
  • *
  • Posts: 3
Re: DFW for FSX Serious start up Issue
« Reply #63 on: March 29, 2011, 11:04:18 pm »
...found where to put the file, but still have the same problem.

Mike

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51443
    • VIRTUALI Sagl
Re: DFW for FSX Serious start up Issue
« Reply #64 on: March 29, 2011, 11:08:39 pm »
Can you contact me via email (address is on the "Contact Us" page ) ? I would like to run some tests.

mikeallenbrown

  • Newbie
  • *
  • Posts: 3
Re: DFW for FSX Serious start up Issue
« Reply #65 on: March 30, 2011, 12:49:09 am »
Done

Mike