FSDreamTeam forum
FS9 support => Zurich scenery for FS9 => Topic started by: MeatWater on December 16, 2007, 06:43:08 am
-
In order to prevent OOM errors I have enabled the >2GB switch in the header of the FS9.exe which is a common workaround. However, bglman.dll refuses to load when FS is started via this modified exe. Could this please be updated? Possibly bglman.dll "thinks" it is being decompiled which of course isn't the case.
-
No, it doesn't depend on the Addon Manager itself. There are no explicit checks made on FS9.EXE, and it doesn't even change if one has the official FS9.EXE or a modified FS9.EXE to bypass the CD check at start. In both cases, Addon Manager will work.
Instead, the fact that you changed the memory allocation for the FS9 executable (I presume you added the /LARGEADDRESSAWARE flag), might lead to believe that this has an unexpected effect on the internal allocation of FS modules, confusing bglman.dll, that expects some things to be at a specific address in ram. There are some safety measures, because (for example) the different ram allocation of different mainboards based on agp, pci or pci-express, is already taken care of. But apparently, the /LARGEADDRESSAWARE flag does something else.
Well, my compliements to you because that "common workaround" is not really *that* common, since you are the first to report this problem since 2005 when we started usign Addon Manager...
I might have a look into it, but I can't promise anything.
-
Thank you Umberto for the quick reply. Out of memory errors have become quite frequent in the past months, as people now finally start having the required hardware to push sliders to the right - at least in FS9. Most do not understand that - while the hardware itself might be capeable of coping with this - the operating system(s) start beeing the bottleneck. As you may know, neither FS9.exe nor FSX.exe are capeable of limiting their request for virtual memory to a value within limits predicted by the operating systems. Microsoft have build a patch for Vista, but in Windows XP the problem still prevails.
The tweak I use sort of tells both the application and the operating system that it is OK to ask for more virtual memory - as long as it is there. It allows the *.exe file to go "the official way" when asking for that extra chew, and tells the operating system not to panic in that case, a reaction that brought up the infamous "OOM" error message. Aircraft like the Flight1 Super 80 or PMDG 747 have become almost unflyable when using high detail settings flying into sophisticated sceneries like Zurich, Heathrow and others.
Using this workaround, all is fine and stable again. I can now enjoy the full range of possibilities given by both the hardware and flightsim add ons at a level never seen before.
Add to that the fact that FS of course isn't the only application that can profit from this setting: it works with a wide range of apps, such as video- and audio-editing software optimizing the memory usage of Windows in a way it should have been right from the start.
It would be a very high price though to trade in all bglman.dll dependant software in order to get this huge improvement, so please look into this. There's nothing like an IFR approach to LSZH in the VC of a high-end airliner with all sliders to the right. Do that without the tweak, and you'll get the OOM in 8 out of 10 cases. With the tweak, you just enjoy flying.
GERMAN READERS go HERE for a tutorial on how to apply the fix:
http://forum.flightxpress.net/showthread.php?tid=3840&pid=39919#pid39919
-
Hi Meatwater!
I'm sorry I can't help you with the problem you describe but...
Out of curiosity, can I ask what PC config you are using?
I looking to buy a new PC and I'm collecting as much info as I can about this OOM problems...
Thanks,
Sylvain
-
Hi Meatwater!
I'm sorry I can't help you with the problem you describe but...
Out of curiosity, can I ask what PC config you are using?
I looking to buy a new PC and I'm collecting as much info as I can about this OOM problems...
Thanks,
Sylvain
My specs are way too oversized for FS9 and even too much for FSX because I need the same pc to work (dv editing and audio production), therefore it wouldn't be a useful target to aim for (Quad6600 with 8GB RAM...you get the picture ;) )
-
My specs are way too oversized for FS9 and even too much for FSX because I need the same pc to work (dv editing and audio production), therefore it wouldn't be a useful target to aim for (Quad6600 with 8GB RAM...you get the picture ;) )
Errr I see yes ;D Thanks for your reply!
And you are actually still running Xp on that Rig? I thought XP could not use anything in excess of 3Gb RAM...
S.
-
I am running a triple boot config, XP for FS2004, Vista1 for FSX and Vista2 for most of the work. That way each version of FS gets the optimum environment. There is no use of more than 3GB for FS2004 anyway, even at peaks it wouldn't require more than 2GB.
-
Silvain, you still can get a nice computer when having lesser specs(as well as a lower price)!
try for example: a good intel P35 MB(asus P5K for example but other brands as well, google to Tom's hardware); Intel E6750 or E6850 dual core processor; DDR2 Ram 2x1Gb 800 Mhz/PC6400 or 1066 Mhz/PC8500; 2 HD's, one for the system(like the fast WD raptor 35 or 74 Gb, 10000rpm), the other for FS(can be any brand or size and 7400rpm);the new Nvidia 8800 GT video card, almost as fast as the 8800GTX, but way chaeper!. You'll need a power supply of at least 600 W, and a housing with extra fan(s).
You can run either FS9 or FSX with either XP or Vista with these specs. Have fun!
tompie
-
Please have look at this bglman.dll issue with the modified fs9.exe Umberto. I miss your beautiful airports without it!
-
As I've said, the only think I can promise, is to investigate the issue. However, I'm not sure at this time if it can be solved. The only thing that's for sure, it's not intentional. The Addon Manager doesn't check and doesn't care at all if FS9.EXE is altered. The problem seems to be a side effect of the new memory allocation strategy in >2GB mode.
-
As I've said, the only think I can promise, is to investigate the issue. However, I'm not sure at this time if it can be solved. The only thing that's for sure, it's not intentional. The Addon Manager doesn't check and doesn't care at all if FS9.EXE is altered. The problem seems to be a side effect of the new memory allocation strategy in >2GB mode.
This would be really very much apprechiated! I got a lot of positive feedback meanwhile, the sollution works indeed for most users and even improves performance on systems that did NOT suffer from the OOM-issue, so anyone else might give it a try as well.
-
We just released a test version that should work, look the top of the forum.
-
Great news! I'll try it after work today. Thank you very big Umberto! ;D
-
YOWZA! It works like a charm.
Just to avoid misunderstanding: on XP systems still try the 2560 value first, as higher values may result in XP instability. The new bglman.dll works very well with the value set to 2560!
Thank you Umberto!
-
Hi!
I just installed the new Addonmangager, but i get the following error messages:
- For security purposes, this program will not run while system debuggers are active. Please remove or disable the system debugger before trying to run this program again.
- then FS tells me that bglman.dll couldnt be loaded
I use Win XP Home and Kaspersky Inet Sec 7.0.
Oliver
-
You can try two things:
- disabling the antivirus or simply exclude fs2004 folder (with subfolders) or just fs2004\modules from scanning
- Are you running with CD4 inserted ? In this case, you can try use an FS9.EXE without CD4 check.
If the 2nd case solves the issue, that might be an useful feedback. In that case, I'm afraid we'll have to keep two separate versions, and who's using the >2GB patch should also patch a no CD FS9.EXE
-
Hy, i have exact the same Problem but only with the modified FS9.exe
(http://aycu20.webshots.com/image/37859/2003614969457201325_rs.jpg) (http://allyoucanupload.webshots.com/v/2003614969457201325)
I deaktivate DrWatson and remove all Reg-Entries and deaktivate my McAffee Firewall and Virusprotection but the same result.
Greetings Andy
-
For those having that problem, please let me know if you are using the original FS9.EXE with CD check, or a modified EXE to bypass the CD check at start.
-
Hi Umberto!
I used the FS9.EXE with CD Check. But now i installed the NoCD-Crack and everything works perfect!
Thanks for your fast reply!
Oliver
-
Hi. I'm getting the same error promts as Andy with bglman.dll version 1.45. Also the bglman.dll won't start. I'm on WinXPsp2 and FS9.exe with CD check. It occurs with both modified and unmodified FS9.exe.
-
So, it's now clear that, if you want to use the >2GB compatibile Addon Manager, you have to use FS9.EXE without CD check.
-
Ok, I hereby confirm that everything works fine with the "large addressaware modified nocd fs9.exe".
Thank you Umberto!
-
Thanks a lot for this new version.
Works great ! ;D
Bernhard
-
I'm still not shure if the 3GB switch really do have any effect at all though. But extensive testing yesterday with demanding software like Pmdg747, Suprunovs Yak-40, ASv6, UTEurope, and heavy airport addons all over Europe, didn't result in any OOM's. So far it seems very promising.
-
Guys what's the difference between the 3GB switch in the boot.ini and the PAE switch?
Rob
-
The /PAE switch is needed to allocate more than 4GB of physical memory (not virtual).
The /3GB switch, instead, changes the default allocation of memory inside the 4GB: from 2GB user space + 2GB kernel space, to 3GB user space + 1GB kernel space
We need the /3GB, together with the patched exe, for FS9. The /PAE and the /3GB switches, are also better not to be used together.
-
Hi!
I updated my C9-EHAM-Scenery to v1.04 today to get AES support. But now the modified FS9.exe wont work again. Same error as before the new Addonmanager. Any chance for an update?
Oliver
-
This is because the Cloud9 installer doesn't automatically check which FS9.EXE you have, and always installs the non-2GB compliant version.
Just remove bglman.dll, and run our Addon Manager standalone installer instead, it has already been updated these days to support EHAM 1.04.
-
Thanks for your quick answer Umberto. Everything is okay again. Support here is really great.
Thank you very much.
Oliver
-
Hi,
i'm doing hard to find a suitable fs9.exe with nocd to patch, which works also with 4GB and FS9 Zürich on my german FS 2004.
Currently i have a 4GB-patched FS9 up and running, all fine, except the Zürich scenery. Could anyone provide a patched fs9.exe with nocd and 4GB patch?
Sorry for this slight special request... But on the other hand it is really frustrating to deal with these type of copy protections. After this, i am quite sure, i have to activate my Yak-40 again :-(
Thanks Stefan
-
Currently i have a 4GB-patched FS9 up and running, all fine, except the Zürich scenery. Could anyone provide a patched fs9.exe with nocd and 4GB patch?
Quite simply, no. And I kindly ask you to refrain to post such requests in public.
The only legal thing we can do, is to detect which FS9.EXE you *already* have at installation time, and install the correct version of our executable. We can't help you finding a patched FS9.EXE, nor we can encourage any other users helping doing this on our forum.
It would have been nice and less work for us if we could support all possible FS9.EXE modifications with a single executable, and if it would have been possible, we already have done it by now, but unfortunately it isn't.
But on the other hand it is really frustrating to deal with these type of copy protections
Yes, but in this case, the annoying copy protection is the original CD check used for FS9. In fact, with FSX, since Microsoft moved to a more modern activation-based protection, like we are using, and we don't run into these issues with the FSX version of our products.
-
Quite simply, no. And I kindly ask you to refrain to post such requests in public.
I agree. Was a little bit stupid to ask here for the crack. So please ignore my request. However i have solved the problem and Zürich works really nice :-)
Stefan
-
I tried to install the new Addon Manager linked in this Forum and it won't work
with the Patched(3GB) FS9.exe ( with CD check) - I don't want to use any cracked Version
so is there any chance to get an Addon Manger working with the GB3 enhancement?
Kind regards
-
If there was a chance to have compatibility with >2GB patched FS9.EXE AND the original CD protection at the same time, we never took the extra steps of having to compile and maintain two separate versions of our executable and select the correct one during installation. It would have been much simpler for us to simply have one version, if it was possible indeed.
-
Only to get this right!!
- FS9.exe (original) patched(>2GB) - WinXP start normal = WORKS fine (used right now by me)
- FS9.exe (original) NOT patched - WinXP start with 3GB switch = Works fine
- FS9.exe (original) patched(>2GB) - WinXP start with 3GB switch = ERROR bglman.dll kann nicht geladen werden
and
- FS9.exe (noCDCrack) patched(>2GB) - WinXP start with 3GB switch = WILL properly WORK!
If this is right Iam the only using the ...
Kind regards
-
That's right. The XP 3GB setting doesn't really make any difference to Addon Manager (of course IS needed if you want to enable the >2GB patched FS9.EXE ). What's make a difference is patching of FS9.EXE for >2GB, that would create a problem with our regular version. The >2GB version of Addon Manager, instead, is not compatible with the original FS9 with CD checks.
The correct version it's automatically chosen by our installer, depending on which FS9.EXE it finds but if you already patched an original FS9.EXE (with CD checks) it will still crash the same, because we don't have a version that is both compatible with the original CD check and with the >2GB patch.