Hi nigelb, 'BTW, there appears to be a missing sound file, looks like "T_CNWY_s.wav" should be renamed "T_CNWY_START.wav", either that or change the file reference in Sound.cfg.' You are absolutely right about the wrongly named sound file. I checked in FS Sound Studio and renaming as you suggest makes it work. I hadn't noticed it so thanks for that.

Tried your fix, Charlie, but no joy. Same error. Also changed the sound file, but again no effect.Will have to try something else, I guess.Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

I sent an e-mail to George and here is his response.As far as I know only 707server.gau is defective (the other gauges youmention are OK, but cannot work without 707server.gau). Here's a new707server.gau which will hopefully fix your problem...He sent me the response within 15 min of my sending him the e-mail.Thanks George.Hope this helps you folks.I'm not sure if he has uploaded the fix or plans [email protected]

Doesn't help 'cause I don't have the file. Looks like everyone needs to mail George separately...Andreas

The problem is very simple. The gauges have nothing to do with "VB" files... Visual Basic has no part in C gauges...The gauge author simply compiled the gauges using the /MD (Multi-Threaded DLL) option, which makes them dependent on MSVCR71.DLL (part of the MSVCR "family" of dynamic link libraries).Had he compiled the gauges using the /MT (Multi-Threaded) option instead, all the dependent code would have been copied to the gauge, making it slightly larger, but there would also be no dependency issues.I'm currently researching a solution to the problem, using Dependency Walker, in an attempt to discover what .dll's need to be present for his gauges.I'll post a solution when I've found one... :)

Surely he'll psot a link to the fix.Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

>I'm currently researching a solution to the problem, using>Dependency Walker, in an attempt to discover what .dll's need>to be present for his gauges.>>I'll post a solution when I've found one... :)ADDENDUM:Dependency Walker reports:Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module.The specific .dll listed is MPR.DLLI copied the entire a/c over to my development machine, which has MS Visual C++ .NET 2003 installed, and tried to load the a/c in the local copy of FS9, because all the VC runtime modules are properly pathed.The error report points to an error in the 707server.gau file. Looking closer, I noted that within the code, there is a reference to 707server.nel (the extension being part of the problem?)...

Hi Bill, Thanks very much for your help and information. I don't know if it's any help to you but I have had the NET framework installed for some time as one of the available Windows Updates. I searched my system for MSVCR71.DLL and it was found in C:WINDOWSMicrosoft.NETFrameworkv1.1.4322The other file you mentioned was not found. What I don't understand now is how the panel can work as it is seemingly doing while there is a faulty gauge, and without a possibly needed dll file. Hope this helps in some way.Edit: Since writing this message originally I have found MPR.DLL in C:WINDOWSSystem32

>Hi Bill, >I searched my system for MSVCR71.DLL and it was found in>C:WINDOWSMicrosoft.NETFrameworkv1.1.4322Oddly enough, that specific .dll is likely to show up in many different folders, depending on what programs you have installed. Some programs include the entire msvcrt.dll "suite" (all it's own dependencies) to their own unique folder structure.>The other file you mentioned was not found. What's truly odd is that Dependency Walker reports problems with the MPR.DLL file itself... Go figure!>What I don't understand now is how the panel can work as it is>seemingly doing while there is a faulty gauge, and without a>possibly needed dll file. That beats me too, except that it is remotely possible that there are at least some common dependencies between Visual Basic and Visual C. In fact, that seems fairly certain since they now share the same development platform. Microsoft Visual Studio may be configured to compile VB, VC and various other variants, depending on what code "modules" and "compilers" you have installed.I've written to George directly to share my findings, and offer any assistance to him to get this nagging issue resolved quickly. I am dying to get this stunning a/c and panel working, as I have a great love for the old bird! I had the privilege of flying on PanAm's Maiden Flight in the B707 from NYC to London back in the 60's... :)

For the benefit of anyone who hasn't checked yet, I just looked in the library and it appears that George has had the original file removed and a new one uploaded. By checking with Zipdive I noticed that the sound file mentioned earlier still needs to be renamed. Off to download it now and we'll see how it goes.

>Off to download it now and we'll see how it goes. It works just fine. I also received an email from George, along with a new 707server.gau file, which was the problem.It seems there was a small boo-boo in the INS section of the code.That's GREAT support! :)Off to try flying this GEM now!

Just downloaded the new download and the panel now seems to work fine. On another note has anyone noticed that the nav lites and strobe lites on the plane seem to be a long ways off of where they should be? If any one has a simple fix for this I would be most grateful. So far the panel has been well worth the wait.Thank you Mr CartyDon:-jumpy

Hi Bill, It works perfectly for me too as far as I can see. Many things still to explore though. When the plane loads on my system it starts with the Captain's panel visible, rather than the opening screen which I thought was intended. Not a problem, in fact it saves time, but I could change it in the Window01 section of the panel.cfg by changing the line visible=1 to visible=0. Otherwise I will never see it unless the other windows are closed via the top menu which rather defeats the object of it being there at all. Thanks for your involvement and thanks to George for sorting it out quickly.

Don, I didn't notice that yet. I'll have a look and see what I can do. I know how to move them, what I might not be sure of is exactly where they should be. I'll post again here with any report or questions.

Thanks CharlieIve been trying to fly this baby but now Im getting FS9 shutting down and an error message citing the source of the problem as "707gau2.gau". Seems to happen while switching between windows or shrinking windows. anyone else getting this?Don