Hello again, all!

After I got this adorable Panel to work (with various re-installs) I jammed into the next problem: When I set up a flight with the Ah let's say CRJ700 and then switch to BAE146 I have no problems at all. But when I set it up with the BAe right at the beginning the sim goes belly up, giving me to read this nasty message about what happened.
It's every time the same reason. Some dll called ntdll.dll does the whoopee and this isn't a FSX dll at all. Now I checked if I have the latest version, which is what I have.
So.... Anyone any clues or am I dammed to start my flights through the backdoor?

BTW:
XP SP2
FSX SP1
Core 2 Duo 6600
2GB Ram
NVidia 7600GT 256MB PCI-e

Palani

PS: Edited Subject to something more specific

Try takeing the dll file out of the module folder and place it in the main flight sim folder and try it then.

But it isn't a Flightsim dll. This is a system dll. And it hangs around in windows\system32.

Don't know then sorry

Hi Palani,

I think the sound gauge may have something to do with your problem as I see your using FSX SP1.

Apparently some of the API's in the gauge got deprecated by Microsoft when they put out SP1.

I've passed the new version to Matthias that Doug Dawson sent me, but while we're waiting for Matthias to implement this update I'll post a new thread on what to do in the interim period.

best.... Adrian W

@Matthias_L: Thank you for your sorrows - I still think the panel is worth that I tinker with it for a while. And please don't get me wrong. I still appreciate your work on this awesome panel.

Yes, I think it's got something to do with that sound. Because I have that flickering on the startermotor, too. I have to crank it like my old granada. As real as it gets, right?

Hey Palani,

was your old Ford Granny British built ?

If so, it too could be BAe !!!

BRITISH ANTIQUE equipement....

Best.... Adrian W.

P.S. Glad the new sound gauge solved your CTD's. I'm also pleased that I'm not the only one having engine start problems, as an interim measure use the autostart function on the APU panel (the red square), that works fine.

Hi Adrian!
Ah - that'll be the reason. I've always asked myself what that "wrong configuration" light on the dashboard means

You mean actually autostart? No - I won't do that. Me and my BAe go way back and I am so used to this startup procedure that I am sneering at all those autostart planes like those that came with the sim. My BAe is an old lady and if she has her funny little ways - well, then so be it.
And if that starter motor finally goes belly up - that virtual starter motors don't cost a fortune, I'll have that repaired

Let you TO equals your landings
Palani

I'm of the same opinion Palani,

I too prefer 'cold and dark' and rather go through the whole procedure than take shortcuts, in fact I hardly ever touch a Microsoft job, too easy !!

I hope Matthias can solve our problems soon so we can get down to some serious flying.

BTW are you getting the same bugs as me, with the HDG hold on approach to final and the braking upon landing ?

may your landings also equal your takeoffs...... Adrian W.

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

@ Matthias,
until you have FSX installed, if you need some ideas tested, just send them to me. I'm ready, willing and hopefully able.

Best.... Adrian W

Hi Adrian

The matter with the HDG is a story of its own. I cannot be too precise because with that online flying I had too much on my hands to say it happens around 4000ft (Which was the alt you referred to, didn't you?). But it could be something llike that, yes. Once and again it switched that AP off for good and flew by hand (like in the olden days, you know).
But yesterday I was stashed in a holding for at least half a century and got experimental. I realized that the heading bug wanders around, when you switch between HDG and LNAV. So I choose the heading with LNAV position - and guess: It works. Don't ask me why.

Hello

@Matthias: I see what you're poiting out (it is written in the manual somewhere after all) But nevertheless: It's just llike I've written. Normally I fly with vasFMC (aka simple FMC) which I have to turn off, when ATC points me to a shortcut or gives me vectors for approach. After then I have to use LNAV. Maybe some trigger event that doesn't get undone?

@Adrian: No, I don't have any braking problems whatsoever. She's braking like a hero - brake temp shoots up to 'round 700° - everything is fine

best regards
Palani