No. This post is a different issue than yours, because the user never managed to run FS9 without a crash, not even the first time. He never posted again to say what happened next so, we don't know if he fixed it or not, but it was the same problem as yours.
You are saying that your FS9 DOES works with the Addon Manager installed, but only once.
In fact, this problem looks more like the 2nd link you posted:http://www.fsdreamteam.com/forum/index.php?topic=2641.0
But it was proven in the end it was an antivirus problem, in this case the antivirus didn't warned the user, but made FS9 crash without any security warning. This was solved by correctly configuring the antivirus.
I had already set my anti-virus so that it ignores the FS9/modules folder, and I don't get any warning about bglman.dll when I install the scenery.
As explained in ALL thread, this is NOT enough. It's not enough to just exclude the FS9\modules folder. This is required, but not enough because, for the Addon Manager files to go there in the first place, you need to first allow their *installation*
Since during installation, they are copied from a temporary folder with a random name, and excluding the whole Windows %TEMP% folder is a HUGE security hole, you HAVE to turn the antivirus ENTIRELY OFF when installing, in order to allow the current files to be copied in the FS9\modules folder, that will ALSO need to be excluded, for when you turn the antivirus back on.
I have tried copying all the bglman files that appear after a first successful install
If you are not turning off the antivirus entirely when installing, you'll never get a successful install in the first place.
I have also downloaded the files form here, and done the same thing, but this doesn't help, FS9 still disappears on a second run after installation
If you are not turning off the antivirus entirely when doing this, your download will be blocked as well.
BTW, 'virtuali', in the second of the above posts, says "Please, do not use the C9 installers, they will just mess your system again, and you'll be back are to start from scratch." Not sure what that means
It means installers for C9 products made by Cloud9, before we took over their support. Some people might still have old C9 installers, but we updated some, which includes EHAM. Our Cloud9 Web page indicates which installers have being updated by FSDT so, if you just downloaded EHAM, this doesn't concern you, because your installer it's not a C9 one.
So why does the scenery work at first then make it so that I can't run FS any more?
Because something is changing them. It's even possible you might have a real virus that attacks executable code the first time is launched, which is very common.
We can verify if this is the case, this way, please do EXACTLY as asked:
Install this utility here: http://code.kliu.org/hashcheck/downloads/HashCheckInstall-latest.exe
It's a small shell extension that can be used to verify file integrity. After installing it, do the following:
- TURN YOUR ANTIVIRUS OFF, and never turn it on for the time being
- Download the files from here:http://www.fsdreamteam.com/download/setup/bglman/release_mscd/bglman.dllhttp://www.fsdreamteam.com/download/setup/bglman/bglman.dathttp://www.fsdreamteam.com/download/setup/bglman/bglman_fsdt.dathttp://www.fsdreamteam.com/download/setup/bglman/bglman_skymakers.dathttp://www.fsdreamteam.com/download/setup/bglman/bglman_qwings.dat
Copy them in the FS9\modules folder, and immediately check the MD5 checksum for each file you downloaded. You can check the checksum, by right-clicking on each file, and selecting "Properties", then the "Checksums" tab, with several checksums will be listed. Note of the resulting MD5 checksum.
Now, with the antivirus still OFF, run FS9. According to your description of the problem, it should run fine at least once.
Immediately after you quit FS9, check the MD5 checksums for the bglman*.* files again, and be sure it hasn't changed. If it has, you can be fairly sure you HAVE something (most likely a virus) that is changing the files. It can't be the antivirus, since you still have it off at this time.
If the checksum is the same for ALL files, try running FS9 again, still with the antivirus OFF. It's possible it will run again.
If it ran twice in a row this time, try a 3rd launch, this time with the antivirus ON (but of course, with the FS9\modules folder excluded!). Exit, and check the checksums again. If they differ, then you can be sure it's the ANTIVIRUS that is modifying the files, probably trying to "heal" them, but in fact is corrupting them. This would indicate your exclusion somehow didn't work.