Scott Miller

Thanks, Joe, I'll give it a try (I actually have it already, but wasn't sure it world work in this case. Still not sure if it will fix FS2002's product ID: registry error problem).

After reinstalling FSX recently (after a HD went south on me), I started up FS2004 and got the EULA acceptance window. I clicked "yes" and FS2004 started up without a problem so I didn't give the odd incident further thought. I just happened to click on the "about" option under the Help menu and notice that instead of listing the Product ID number the screen says "Product ID: Registry Error". FS2004 starts up ok, but is this going to cause problems down the road? Will it keep addon scenery or aircraft from installing properly (if at all)? What's the best way to fix it? Uninstall the fs9.1 update and FS2004 itself then reinstall both or uninstall the former and just reinstall FS2004 over itself? Will either option screw up my FS9.cfg and scenery.cfg files or any aircraft/scnery addons I've installed on FS2004?I still have FS2002 installed on my system and the same thing happened to it as well...This is really odd. Neither FS2002 or 2004 were affected in any way the first time I installed FSX...

Jahman, you were right on. After installing all the available updates for Windows XP, I tried installing UT2 (2.09) again and it installed, and runs, properly (finally)! I'll know better than to put off running the automatic updates next time (which hopefully won't be for a good LONG time)!BTW, I did submit a post about all this (as I mentioned) to the Flight One UT2 forum (mentioning, as I did here, that I had turned off automatic updates when I reinstalled Widnows XP). The folks on the UT forum tried to help, offering a couple of suggestions (turning automatic updates for windows wasn't one of them). When the suggestions didn't pan out I decided to submit a post here in the hope of having better luck here. I did! Thanks, guys!

Yeah, that's on my list of things to do. I turned off automatic updates (actually, I've never had automatic uupdates turned on but used the "notify me but don't install" option) when I reinstalled Windows XP Pro so that Windows wouldn't install any updates released prior to SP3. In doing so I hoped to limit the updates that will have to be installed to those that have been released after SP3 came out.I decided to uninstall UT2 again (along with simConnect.msi since it fixed nothing). The "smartassembly" error message is gone again and the (FSX) AI aircraft are back. I'll turn on Windows updates then I'm going to try reinstalling my original version of UT2 then restore all my FSX files from a backup I did before replacing my bad primary hard drive (FSX and all the addons were installed on my secondary hard drive which I wiped clean when I installed the replacement primary HD). I was going to restore all my addon scenery and aircraft from this backup anyway. I figure a full restore from this backup is worth the risk. If successful, all I should have to do is install a schedule update containing the UT2 SP2 and hopefully I'll be good to go (knock on wood!)...If it doesn't work then its on to Plan B (uninstalling FSX Gold, all addons and redoing everything from scratch)...if UT2 still gives me problems then it'll be time to find a replacement for UT2 (or deep six FSX altogether)...

The following was posted (over several posts) on Flight One's UT forum. I've re-edited it and posted it here in the hope that someone will be able be of help (not that Flight One's support people haven't tried, they just haven't come up with anything, so far, that has worked). Anyway, here goes (it's going to be a bit lengthy):1st PostI recently lost the primary hard drive on my system and had to replace it requiring a complete reinstall of Windows XP Pro and all my software, including FSX and UT2. I'm having problems reinstalling UT2.I've tried several times to reinstall my original UT2 version (1.04) along with the SP1, the hotfix for SP1 version 2.07 (needed as UT2 crashes after the SP1 is installed without it), along with hotfix1, 2 and 3 for UT2 itself. When I then attempt to run UT2 I get 2 error messages:1st: Program Error: Error loading FSX aircraft information. Object reference not set to an instance of an object.2nd: Program Error: Could not load file or assembly 'System Core , Version 3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e099' or one of its dependences. The system could not find the file specified.After a few seconds UT2 goes ahead and loads. The Update window states that 2 UT2 files and the flight schedule file are out of date. I installed the Winter 2010 schedule update (I hadn't check to see if any subsequent updates had been released) which apparently installed the SP2 for UT2. This did not fix the problem. I still got the error messages.I tried all this at least 3 times getting the same result each time so I uninstalled UT2 yet again and down loaded the current UT2 installer (for verion 2.09) from Flight1's website. When I tried to run it I got an error message stating that the ultimatetraffic2.exe file size was incorrect and that it needed to be in the same folder as the ultiimatetraffic2.000 file!I downloaded the current installer again, turning off my firewall and NAV software (as suggested by Flight1's support person on their UT forum) which I wasn't happy about doing, but it worked. I was able to install version 2.09 ok, but I still get the same error messages when I start UT2 up.What on earth is going on here? I didn't have any problems installing UT2 the first time? Is Windows XP missing something (I opted to turn off updates turned until I get all my software installed. Aside from a few addon scenery files, UT2 is literally the last item).Second Post (here is where things get lengthy!):When I ran UT2 after installing v2.09 I got the same two error messages during startup I got when I attempted to reinstall my original version of UT2. What's worse is that I also get both errors when I attempt to use various items within UT2.When I try to select/unselect items on the AI Labels page I get error number 2 (Object reference not set to an instance of an object" error message". If I try to save the changes I get an "Unhandled exception has occurred in your application" error.I get error #2 when I click on "aircraft repaints" and when I enter something in the "search for...box on the electronic statusboard page and then click on "view". In most cases, I can click on "continue" to clear the error message, but not in this case. I have to click on "quit" and then restart UT2.In the instances where I get the "Unhandled exception" error and click on details here is what I get:See the end of this message for details on invokingjust-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.NullReferenceException: Object reference not set to an instance of an object. at ..() at ..(Object , EventArgs ) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)************** Loaded Assemblies **************mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll----------------------------------------UltimateTraffic2 Assembly Version: 2.9.0.0 Win32 Version: 2.9.0.0 CodeBase: file:///F:/FSX/Flight%20One%20Software/Ultimate%20Traffic%202/UltimateTraffic2.exe----------------------------------------System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll----------------------------------------System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Data.SQLite Assembly Version: 1.0.65.0 Win32 Version: 1.0.65.0 CodeBase: file:///F:/FSX/Flight%20One%20Software/Ultimate%20Traffic%202/System.Data.SQLite.DLL----------------------------------------System.Data Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll----------------------------------------System.Transactions Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll----------------------------------------{92b4f56c-8992-46b6-9774-f0799fa6ca8c} Assembly Version: 0.0.0.0 Win32 Version: 2.9.0.0 CodeBase: file:///F:/FSX/Flight%20One%20Software/Ultimate%20Traffic%202/UltimateTraffic2.exe----------------------------------------System.EnterpriseServices Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:<configuration> <system.windows.forms jitDebugging="true" /></configuration>When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.I get the "Unhandled exception" AND the "SystemCore" error messages when I click on Utilities/Flight Plans.I get the "Unhandled exception" error message only when I click on Utilities/Parking Codes.I get the "Unhandled exception" error message when I click on Traffic Options/Aircraft Repaints.I don't understand why I'm having any of these problems. I NEVER did with the previous, and 1st, UT2 install. With at least half of the features (that I know of at the moment) in UT2 not functioning properly, if at all, UT2 is pretty much useless!Third Post:Just ran FSX. When I started it up I got the expected "Do you trust" messages for UT2. Theses were followed by an unexpected message stating something about "smartassembly" was required for UT. Then when I loaded a B737-500 at KONT there were no UT2 AI aircraft in sight. The 737-500 was the only aircraft anywhere at KONT!The situation has now gone well beyond "totally unacceptable"! Unless all the problems I'm currently having with UT2 (which as I said I never had before!) can be resolved I'm going to have to uninstall UT2 permanently!In response to this, Flight One's tech support guy suggested I try a file called "Simconnect.msi" to repair FSX. Not only didn't fix FSX, I am still left with the problems with UT2 itself!Well, at this point I'm hoping that someone here (AVSIM's FSX forum) can come to my rescue! If not, then I guess I'll have little choice but to uninstall FSX and the few addons (including UT2 of course) that I've installed so far (actually I only have a handful of addons for FSX, FS2004 is still my preferred version of FS) and reinstall FSX and the addons from scratch. While I only dabble in FSX and have no plans to do more than that, still, I want FSX (and the few addons I have for it) to work properly (as they all did before I suffered the hard drive malfunction). Otherwise there'll be no chance whatsoever that I'll ever trade in FS2004 for FSX. (which will require a new system anyway). The FSX fans here could be my only hope!

Actually, that is what I did. I clicked on the Combatstick then clicked again on the Pro Pedals. They switched places on the JoyID list alright. However, when I called up the Windows control panel and clicked on the game controllers icon, it still shows the Pro Pedals listed first and the Combatstick second.

Hi, Jahman!Well, the first time I tried using JoyID I dragged the Combatstick over the Pro Pedals (which is listed first) thereby moving the Combatstick into slot #1 and bumping the Pro Pedals into slot #2. When I clicked on the Game Controllers icon in the Windows Control Panel, however, it still listed the Pro Pedals first. I went back and tried JoyID again this time pulling down the File menu and clicking on "Save" (or Save as, I forget). Again I checked Control Panel, but the Pro Pedals still appear first in the list. What am I doing wrong?

I recently had to replace my primary hard drive and reinstall everything including my CH 568 Combatstick USB, CH Flight Yoke USB, and CH Rudder Pedals USB. Windows XP is now insisting that my CH USB Pro Pedals be listed first in the game controllers list in the XP Control Panel and my CH 568 Combatstick USB or my CH Flight Yoke USB second. This wasn't the case before having to replace my primary hard drive.This isn't a problem for Flight Simulator and Combat Flight Simulator 2 & 3 along with a few other sims I have (including Falcon 4.0 AP). However, other (older) sims like Rowan's Battle of Britian, Falcon 4.0 SP, B17 , European Air War, Jetfighter V, and all the IL-2 titles I have, insist on trying to use the CH USB Rudder Pedals for the flight controller because the CH Rudder Pedals are listed first in the game controller list in the Control Panel.As I said, before my previous boot hard drive went south on me, I was able to use either my Combatstick for DH Flight Yoke USB and my Pro Pedals US with all of the above sims (along with FS, CFS, and Falcon 4.0 AF). Only sims (such as CFS 1 and apparently, Falcon 4.0 which came out before there was support for rudder pedals) never did work with rudder pedals.I do seem to remember having this problem in the past (several years in the past) ehen I installed the now defunct primary hard drive and that I somehow managed to fix the problem. Unfortunately, it happened so long ago (3 or 4 years at least) that I don't remember how I managed to fix it! I do seem to recall that it was a stroke of sheer luck that I managed to stumble across the solution at the tme!I've tried several tricks I came across on the Internet, but none of them have worked so fax. A small utility I came across called "JoyID" is suppose to change controller IDs but I haven't had any success with it yet (perhaps I'm just not using it correctly). In any case, I'm hoping someone can help me correct this problem so I won't have to control the rudder via the keyboard (I really hate auto-coorindated flight) which is a real wet blanket on the "as real as it gets" concept all self respecting flight simmers strive for (G)!

Yeah, you're probably, right....

Flight1's product description for Airport Studio says its compatible with FS9 and FSX. Any chance it might work with FS2002 as well? I have a major problem with both payware and freeware airport scenery in that I frequently seen UT AI and static aircraft embedded in terminal buildings, jetways, other aircraft, etc. or sitting in the middle of taxiways, parking lots, etc. I've seen this even when the airport scenery comes with a AFCAD file. On the otherhand, I rarely see this problem in FS2004.I think (at least hope!) Airport Studio could solve this problem if it could be made to work with FS2002...

You're pretty close to the truth (about it being a FMC/FMS bug). According to Mavigraph the CRJ FMS cycle info is hardcoded and can't be changed by their navdata update installer (in a sense this is a bug since whoever wrote the code for the CRJ FMS failed to realize this!). Thanks for the info about where the CRJ and 737 databases are located. I was beginning to think that installing the CRJ update was a waste of time since both are installed in the same feelthere folder (I didn't know there was a difference between the navdata and ND folders)!Scott

Last August I posted a message here about Navigraph's FMS update installer NOT updating the FMS for thefeelthere/Wilco's CRJ. Unfortunately, in spite of being viewed by nearly 350, it didn't illicit a single response! Surely I'm not the only person who has experienced this problem (in fact I know I'm not as I found a couple of posts on Navigraph's support forum about this problem, none contained a solution).At any rate, I still haven't been able to update the FMS on Wilco's CRJ. I've never had any problem updating the FMS on Wilco's 737 and 777 aircraft (which Navigraph supplies a different installer for). The FMS installer for the CRJ reports a successful install but when I start up FS2004 and load a CRJ plane, it's FMS display still lists the JUL04 cycle. I installed the latest CRJ FMS update to a dummy folder and found a "feelthere" folder in it containing a navdata folder, which appears to be identical to the 737/777 FMS navdata folder in FS2004.If the two are identical then why separate installers for the 737/777 and CRJ navdata updates and why can't the CRJ's FMS read it? A response, ANY response, would be appreciated! Thanks!Scott Miller

Actually, the problem was caused by something about the zipped file not being compatible with PKzip. Your comments gave me the idea of unpacking the zipped file using the Compressed (zipped files) Folder option. The installer ran properly once I did that. Even though PKzip has been around quite a while it still works just fine most of the time. Every once in a while, though, I come across a zipped file that gives it fits for some reason...PKzip couldn't unpack Navigraph's FMS zipped data files for several months starting back in November. It was able to unpack them last month ok though...

Just downloaded the free edition of the CLS Piper Arrow from SimMarket. When I tried to install it I got "CLS Piper Arrow.exe is not a valid Win32 application". I'm running Windows (XP Pro to be exact) so why am I getting this message? Post the same message on CLS' support forum and was told to download the Piper Arrow from their webshop page and try to install it again. I did but got the same message! I noticed that both copies of the download file were 162mb but when unzipped the exe file along with the pdf manual and repaint files total less than 80mb...weird! Obviously, I could use a bit of help here...Thanks! Scott Miller

Say, JP, what driver version are you using with your GF6600 card? I upgraded from the driver that came with my GF7600 GS to the NVidia Graphics Driver 6.14.12.6089 (260.89)/Nvidia NView (125.36). Considering rolling back my Nvidia driver back to the original to see if upgrading the driver might be (as lease partially) the cause of all this.Something else that occurred to me is that I switched from the purely feelthere/Wilco FS2004 only 737PIC to the Just Flight - feelthere/Wico FS2004/FSX version (if I recall correctly, previous to upgrading the graphics driver). Which do you think might be more likely the cause or contributed the most to the problem?Incidentally, I just discovered that FS won't let me make a saved flight using a 737PIC plane the default saved flight anymore whereas it in the past (just how far into the past though I have no way of telling at this point! If I manually edit the FS9.cfg file to make such a saved file the default saved flight and try to run FS2004 I get the CTD...I can make any saved flight using any other plane the default flight, just not one using a 737PIC plane!Scott

My system is an AMD3200+ Athlon 64 2.2Ghz, GF7600 GS 512mb, 2GB ram.Actually, I really don't have that many addons (Active Sky, FDC LIve Cockpit, Ultimate Traffic, and FSFlying School plus a handful of single instrument addons including the ISG FMS, EZ-GPS, the Reality XP Wx500 radar).However, I do have a fair number of aircraft including the payware commerical aircraft 737PIC, ERJ145PIC, CRJ vol. 1, PMDG 737NG & 747-400, ATR72-500, QW757,and 777 Pro with a slew of repaints, particularly for the 737s (my aircraft of choice). My payware GA include the Carenado Skylane 182, Centurion Piper Dakota, F33A, V35B, F1 Conquest, Meridian, PC-12, and the Lionheart Quest Kodiak and Epic Dynasty. My freeware aircraft include the ATR series by Francisco Sánchez-Castañer, BAe-146 (PAD), the Tinmouse 737-200, DeHavilland Twin Otter, PAD Dash 8 series, Dreamwings Embraer 170, PAD Embraer 190, Project Fokker 100/70 and F28s along with a few other odds and ends. Lots of repaints for several of these as well.Actually, I think what drags my system down the most is my scenery addons. All of which, aside from FS Global 2005, I've acquired only in the last couple of years including World Airports 1 - 3 , US Airports 1, and individual airports from Blueprint and Imagine Simulations and Fly-Tampa along with a number of freeware scenery files such as those from the Friendly Frame Rate folks and Shehryar 'Shez' Ansari's equally incredible scenery for KONT, KSNA and KBUR. Many of these drag my frame rate down into the single digits! Once I get clear of such extremely dense scenery as this, however, into "open air space" at cruise altitude, my frame rate jumps back up to the 20+ range...In the end, though, you're probably right something being wrong about my FS9 install (which this current problem may have brought to a head). A new install from scratch is probably in order (unless I hit the lottery and can get my hands on a top of the line gaming system)! With all the addon aircraft and scenery I have now the thought of even attempting a new install and having to reintall all this makes me go weak in the knees!Scott

Actually, no, it also happens, as I mentioned, if I select a 737PIC plane while setting up a flight from scratch in the "create a flight" menu. I hadn't ever needed to select a default plane to start a flight before, but if the FS9.1 update turns out to be the culprit, I may have to start (since the QualityWings 757 and the PMDG 747-400 both require the 9.1 update)! Actually, it appears that selecting pretty much ANY aircraft before switching to a 737PIC plane will do the trick. I know that selecting a PMDG 737 works every time...I do have to be careful to be in the 2D cockpit view of another plane when selecting a 777 Pro or Flight 1 Meridian (and to save a flight involving either aircraft in the cockpit view). In the case of the 777 Pro, failure to do so results in the instrument/view selector shows up partially hidden by the windscreen frame. Trying to save a fight involving the Meridian in anything but the cockpit view freezes FS up or causes it to crash (I forget which since it's been a while since I made the mistake of trying to save a flight with it in spot view)...I have noticed that the more changes, addons, etc. I make to any version of FS the flakier it tends to get! FS2004 in particular also takes a good deal longer to load that it initially did. Anywhere from about 6 minutes for a typical aircraft/airport combo to at least 2 or 3 times that long if a PMDG 747-400 or similar plane and scenery requiring a extremely dense scenery setting are involved! My system, a 5 year old 2.2 Ghz system (I know, a museum piece by today's standards), still gives me a (barely) acceptable frame rate of 12 - 20 in dense scenery, is of course, partially to blame for this...still, if there is anything (short of a new system of course!) that would improve the load/frame rate situation, I'd love to get it!Flipping the Render to Texture setting, as Bob suggested, didn't help. It was on so I switched it off but still got the CTD when I tried to switch from a 737PIC plane to something else...I'll try switching the clouds off next but I have my doubts it'll do any good (except to improve my frame rate!) either...Scott

A couple of weeks ago, after reinstalling the FS9.1 update and the 1.2 update for PMDG's 747-400, I suddenly started getting CTDs immediately on attempting to load a saved flight, ANY saved flight, regardless of the aircraft in the saved flight. I thought I had fixed the problem after finding three different [Display.Device] entries in my fs9.cfg fiile (one for the current graphics card in my system and 2 for previous graphics cards). Removing the obsolete entries and a Trilinear=1 line I also found seemed to solve the problem, or so I thought!Last night I installed a 737PIC repaint then started FS2004 up selecting a saved flight using a Delta 737PIC. The flight loaded ok, but when I try to switch to a different aircraft (ANY aircraft) I get an immediate CTD. This problem occurs ONLY after loading a flight using a 737PIC plane. It occurs immediately from the "create a flight" menu if I select a 737PIC plane. It occurs even when attempting to load from one 737PIC plane to another. It does NOT occur, however, after switching to or from a Wlico ERJ145PIC plane or a Wilco CRJ vol. 1 aircraft. It ONLY occurs when a 737PIC plane is loaded first. If I load a flight using a different plane, say a PMDG 737NG, I can switch to a 737PIC plane ok, but if I then try to load another plane, including any 737PIC plane, the CTD instantly occurs.To my knowledge, this problem never occurred before the FS9.1 and/or PMDG 747-400 1.2 updates were installed ("attempted" to install in the case of the PMDG 1.2 update. After the initial problem two weeks ago occurred, I uninstalled the PMDG 747-400 1.2 update. I have no plans at this point to try to reinstall it either!). I have the FS2004/FSX version of the feelthere/Wilco 737PIC sold by Just Flight. The problem does not occur in FSX. In any case, it appears that either the FS9.1 update and/or the PMDG 747-400 1.2 update has damaged FS2004 in some way that escapes me!Is there a patch that is required for the FS2004 737PIC to run under the FS9.1 update (assuming it is the cause of the problem)? There is a patch available for the FS2004 CD based version on the Wilco website but the website doesn't say what the patch is for. I'm extremely hesitant to run it without knowing exactly what it will do. Installing it might make matters far worse!Has anyone else run into this problem? Any assistance would be appreciated!

I've noticed that in most of the 50+ liveries I've downloaded the soda cans visible in the beverage caddy behind the co-pilots seat have the "livery" of the ever popular "Jetc" PMDG brand (we all have at least a half dozen cases in our garage, right?) of soft drinks. A few repainters, though, went the extra mile and replaced the PMDG Jetc "livery" (how dare they!) with other brands, including that of the throughly disgusting Coke brand (G)! A couple accidentally left the soda cans unpainted (that or they prefer the generic brand). Question: How'd they do that? More importantly, since I don't see a separate file for this like the manual.bmp file, which file contains the soda livery? Is it one of the usually generic cockpit files used in all the repaints (and usable in any repaint)? If so, which one?

You can get off your high horse, friend! I am well aware that I am not PMDG nor was I attempting to set the price for their addons. IT WAS STRICTLY A SUGGESTION, which, if you had taken a moment to think about it before jumping down my throat, might have occurred to you! Maybe YOU don't mind getting soaked for something that's been around as long as QOTS has been regardless of the quality, but I do! Particularly when you consider that when the FSX version, which includes the 400F variant, was released, it's asking price was less than FS9's version which doesn't!Please spare me your sarcasm in the future!Oh, and just for the record, I purchased QOTS (the FS9 version) from Aerosoft, not PMDG.

Actually, perhaps both! The curse? I spend all night trying to recover FS9 after installing the 1.20 update to my 1.1B version I purchased as Jan but only got working, prior to installing the update, a couple of days ago. Initially, it caused a CTD if I attempted to switch to the 2D panel view. I couldn't figure out why until I tried to install QualityWing's 757 and was informed by the installer that the FS9.1 wasn't installed (though the FS9.1 installer said it was!)! Once I got the FS9.1 properly installed both the QW 757 and PMDG 747-400 installed without incident, and functioned, flawlessly...or so I though!The blessing? After installing the 1.2 update last night, however, things took a nasty turn for the worst! As soon as I tried to load a saved flight FS9 unceremoniously dumped me back to Windows! After hours of trying everything I could think of, I finally decided to compare, line by line, my current FS9.cfg file with a two year old backup copy that still worked. I found three different [Display.Device] entries each one for a different video card, one for the current card and two more for two previous cards (all NVidea GeForce cards). Removing the obsolete entries didn't immediately solve the problem as one might have expected. It was only after removing the "Trilinear=1" line from the Display Device entry that I finally got both FS9 and the PMDG 747-400 working again! The curious thing is, FS9 (and the PMDG 747-400 (once I got the FS9.1 update properly installed) worked just fine (more or less) with the duplicate display device entries and trilinear line. It wasn't until I installed the PMDG 747-400 1.2 update that I started having major problems. I guess you could say I owe a note of thanks to PMDG for this else there's no telling how long I'd have blissfully gone on using a corrupted FS9.cfg! Even so, I have doubts about attempting to install the 1.2 update again (certainly, I won't try to until I get a chance to do a proper backup of FS9)!Partially as a result of all this (but also because I think it makes sense), I'm thinking of re-organizing the FS9.cfg file so all the entries are in ABC order. Will this work or do certain entries have to appear in a certain order to work properly (if at all)?

You're kidding?! I wouldn't have paid the outrageous $69 price PMDG continued to charge, until just a couple of months ago, for QOTS years after they released the FSX version (as a number of payware FS2002 vendors did when FS2004 was released). I'm sure as heck not going allow myself to get ripped off for another $30 for an addon that by all rights ought to be offered to registered QOTS users as a free addon (or at the very least, at a reduced price) this late in the product's life cycle. In fact, if PMDG were to release the FS9 400F addon to QOTS as a free or discounted addon to registered users it would almost certainly encourage a good many folks, who were as put off at the sky high price QOTS previously sold for as I was, to finally purchase the product. It would be a win-win situation for all concerned! :(

Is the B747-400F for the FS9 version of PMDG's QOTS available anywhere (other than PMDG)? I see it's still being sold for 29.95 on the PMDG website. It would be nice, given the fact that the price is finally being sold by PC Aviator and Aerosoft for $35, if PMDG reduced the price for the 400F addon to something around $19.95! I downloaded several 400F liveries from the PMDG website only to discover it isn't included with the main QOTS product (I picked up the 747-400x product at Best Buy a year ago (for $29.95, a real steal at the time). I in my haste to order the QOTS in case someone discovered their mistake and raised the price againneglected to notice that the 400F wasn't included in the FS9 version (G)!

Of course I read your message! Didn't you read my reply? If so, how about answering my questions then instead of being so rude?!"Try this and comeback posting"?! Don't you mean "Try this and let me know if it works"?!ScottScott