General Category > General Discussion

Really Frustrated

(1/3) > >>

mal998:
Hi All,
I haven't posted here before, but I am a long time customer of FSDreamteam. I own quite a few airports including KFLL, all the airports of Hawaii, Dallas, Vancouver etc. I have read all the comments regarding the crash problems with the updated software and I have to tell you I am totally frustrated with the so-called solutions. I have now tried every recommendation and none of them are solving my installation problems for FSX. That renders all of my airport products useless. It's not just the money spent but the fact that I can't use the damn airports I find really frustrating. My home field is Ft. Lauderdale and now I am forced to use default scenery. After all the years I have spent in flying the sims (since'85) that is really shameful. I hope that the FSDreamteam will review the new software and solve the install problems soon. I really miss my FSDT airports. Oh, BTW, I had no problem installing KFLL into P3D v3. Go figure?

virtuali:

--- Quote from: mal998 on February 19, 2017, 04:58:10 pm ---Oh, BTW, I had no problem installing KFLL into P3D v3. Go figure?
--- End quote ---

That was the only really important information you needed, so you must surely know the problem (like in all other cases you might have read) is something in you FSX installation, since the software is obviously exactly the same in FSX and P3D.

Now, if you reported your FSX problem more precisely, it might be useful to help you finding what is your FSX problem, and we'll help you anyway, even if it wasn't caused by any of our software, like in all cases we reviewed so far.

mal998:
Virtuali, thank you for the reply. I am running Windows Vista 64 bit.

I downloaded a new file for KFLL and the StandAloneManage. I used those new files for an attempt at installing KFLL. 

First I made sure old dat and dll files were not present.

I installed the KFLL airport files first and then the stand alone manager.

When I tried to start up FSX the first screen I got was permission to run the Couatl Scripting Engine which I ok'd.
The next screen I got was an error screen that said "Flight Simulator has encountered a problem with third party software (addon): Name bglmanx Dynamic Link Library version 3, 1, 0, 1 Company VIRTUALI Sagl File bglmanx.dll do you want to run this software (not recommended)?
I hit the yes button and next screen stated bglmanx.dll Entry Point Not Found...the procedure entry point K32EnumProcessModules could not be located in the dynamic link library kerne32.dlll.
Asked if I wanted to run that software I hit the yes button and FSX crashed.

I think I will remove FSX and do a clean install to see if that rectifies the FSTD install problems. If that does not fix the issue, there is a real possibility that the problem lies in my Windows Vista 64 bit installation at which point I have no idea what the problem might be.

virtuali:

--- Quote from: mal998 on February 20, 2017, 08:15:22 pm ---next screen stated bglmanx.dll Entry Point Not Found...the procedure entry point K32EnumProcessModules could not be located in the dynamic link library kerne32.dlll.
--- End quote ---


--- Quote ---here is a real possibility that the problem lies in my Windows Vista 64 bit installation at which point I have no idea what the problem might be.
--- End quote ---

Are you SURE you have installed the latest Addon Manager ? We had another Vista user reporting this error a couple of weeks ago, but we found what the issue was: we used a new API call which is not supported anymore under Vista (you'll see the same error message if you try to run Office 2013 under Vista), which is used to check if Couatl is still running on exit and close it, but I'm fairly sure the problem shouldn't happen anymore with the current version, since we replaced that call with a Vista-compatible one now.

PedroSMP:
Folks, (2 images attached)

I also have this exactly same problem after reinstall the GSX today (7 times), either with the FSDT GSX global install pack or after reinstall the latest stand alone Addon Manager.   

Note though, that if I respond "no" in the first error (attachement 1)

"Flight Simulator has detected a problem with a third-party software program (add-on): ...",

 FSX starts and runs ok, just the Virtuali/Couatl menus are not available in FSX/addons, even SODE menu and funtionalities are available.

Some help will be much appreciated.

Thank you

Navigation

[0] Message Index

[#] Next page