Can't start some elements of FMGS

[jeehell]

Hi Barry,

did you try installing again the software without the antivirus running? it oculd be it corrupted some files...

Regards,
JL

[Barrykensett]

This is academic but I carried out the following:
Unloaded FMGS and deleted the folder. Did antivirus scan and then disabled. Downloaded fresh copy of FMGS and loaded to c:/FMGS. Loaded for non-fs PC, no standbys, just basic panels. Clicked starter and updated software. Clicked starter again, FCU and OHD loaded normally, ND, PFD, MCDU, EIS all gave error messages and failed.
If I do this on the other PC that I am now using on the network all programs start as I would expect. There is something about this particular PC, strange since it was my desktop for a few years and has been the instructor station on the sim for the last five years. The one I am using instead is even older but with no problems. I could reload the operating system and try again but really this PC is ready for the scrapyard so no pressure, it's just the unknown that bugs me!
Barry

[jeehell]

Yes that bugs me as well. I can only guess an issue with OpenGL and your graphic cards/drivers....

JL

[Barrykensett]

Sorry to raise this issue again, I got over the error during trials by ditching that PC. However I have now started getting the system running on my flight simulator and the problem has re-visited me. I can't ditch another PC.
in summary then: all modules run fine on the FS PC. Moved the SD, EWD and all standbys to another networked PC and all run fine. However trying to put the ND and PFD on the third PC gives me the error message that EIS has encountered problem and needs to close.
Both of the add on PCs are the same spec and set up the same. Both are XP, Firewalls off, widefmgs set up same on both.
Tried reloading FMGS.
Any more suggestions welcome as this is now a show stopper.
Barry
www.a320sim.com

[jeehell]

Hi Barry,


can you give more detailed info on your computer specs and network setup?(manufacturers, drivers,models, etc)
what version of my software are you running?
did you try to copy the folder of the working computer to the flawed computer?
regarding antivirus software, was it off during install and while running the soft?this has been a recurring issue for some, particularly avast is a pain. Sometimes you only get a fraction of a second before it locks a file...
I'll try to make a log file while running everything, it may help.

regards,
JL

[Barrykensett]

OK some more details
PC2 details:
Motherboard Winfast K8M890-8237
Processor Amd Athlon 64 3200+
Memory 2048Mb
Graphics ATI Radeon X1950 GT Driver 6.14.10.6706

OS Windows XP Pro SP3
Anti Virus AVG Free 2014
Anti malware Spybot S & D

A320 FMGS B35.3 2014-09-27
Updater applied all PC's

Network
PC1 Win7 P3D and FSX (Jeehell A320 model used on both). AST and FMGS Servers
PC2 XP (AST PFD and ND), FMGS PFD and ND
PC3 XP (AST SD, EWD, Standbys, SIOC, FO MCDU(IOKeys)) FMGS SD, EWD, Standbys
PC4 XP (AST OH, CPT MCDU) (No FMGS loaded yet)
PC5 W7 (FS Commander, Active Sky Next, AST Instructor Station, VPilot) (No FMGC loaded yet)
All PC's on same network, no firewalls active (Rely on router).
WideFS working on all PC's. Simconnect working PC5 & PC1.

Trial outside the simulator all modules ran OK on W7 laptop. When adding XP PC all modules ran OK except PFD & ND.
First trials in the simulator all modules run on PC1 satisfactorily.
Second trials PFD and ND loaded on PC2 - not working *. EWD,SD and standbys loaded on PC3 - all working.
* Error message "EIS has encountered problem, needs to close, tell Microsoft etc" four times.

I have never had problems with AVG but will try loading again with AV off. Have tried copying files from PC1 to PC2 but still fails.
Note the two PC's I have used on testing where PFD & ND work are Windows 7. The two where it fails are both Windows XP.

Barry
www.a320sim.com

[jeehell]

Hi Barry,

This really seems like an error because of the navdb.dll module, which may be blocked by your AV.
This navdb.dll is the only link to ND/PFD. As you noticed, all instruments (PFD,ND,SD,EWD) are inside the same file EIS.exe. But the navdb is loaded only on PFD and ND.
Maybe try to see if your AV soft can have exclusions folders.

Regards,
JL

[Barrykensett]

Will try but I am away for a week. Just noting that things worked OK on PC 1 and that has same AVG.
thx for help.
Barry

[jeehell]

Anyway, when you're back at testing, I've added back a logging I removed some time ago.
In the EIS folder, you' have ini files, one for each EIS (PFD.ini, ND.ini, etc...).
In those files, add the following line:
log=yes

This will make the log files (called Log_PFD/txt, etc...) not empty anymore. I will need the files on the computers where the EIS crashes.

Regards,
JL

[Barrykensett]

OK bit more information. Firstly stopped the AV. Downloaded FMGC again. Also redownloaded the navdata file.
Note above I am only trying to run ND's and PFD's on PC2, I therefore only selected those items when loading. When I looked for the ND and PFD .ini files they were not there. I then went back and looked at PC1 where I originally ran the nD and PFD satisfactorily and the .ini files were there. It was necessary therefore to load more files. I loaded the same setup that I used on PC1 with the exception of the server. The .ini files were now there and I added log=yes to the ND and PFD. When I ran it I got he same errors but there was nothing in the log txt files. Note now I am also running the SD,EWD,MCDU, FCU and OH on this PC. Only the FCU and the OH worked, all of the rest gave the usual error message so it is not just the ND and PFD and hence not presumably linked to the navdata. Basically it is everything with a "screen" so perhaps OpenGL is the common factor?
Any more ideas?
Sorry to be a pain.
Barry