Hi guys, pre SP1 I was able to move the Traffic Explorer and Map windows in Traffic Toolbox to my second monitor while in windowed mode then switch to full screen mode and those windows would show on the second monitor. I can

Please forgive my "bumping", but I've done it in case someone that might have a solution missed my post.Thanks,George

Did you install FSX into the default folders or did you select a different folder?The SP1 handles the traffic toolbox differently then did pre SP1. There is a small utility you must run in the SDK folder that resets Traffic Toolbox so it can be found in a non default folder installation.The SDK docs for the new SDK update version A explains how to run the batch utility.

Hi Jim thanks for the reply.I had run the SDK update version A because prior to that the

I am not satisfied with the way FSX/SP1/SDK version "a" work with VISTA.I have had to turn off as much as possibile in VISTA (defender, indexing, DEP, Admin UDP, etc) so FSX is stable and to get features and paths to be recognized properly.Other issues are the dll files that FSX SDK places into WINSXS folder which the SDK cannot find. I had to copy some dll's up to the SYS32 folder so the newest version of the SP1 and SDK would work continuously.Even the FSX.exe is trying to find certain dll's that are in the WINSXS folder but are better suited if a copy of these dll's are in the SYS32 folder.I use VISTA PCTools and Norton 360 which helps in pointing to dll errors and where FSX/SP1/SDK is looking for these dll's.I also had to remove the SDK Version "A" update, defrag and then reinstall the original SDK and then the update. Once that was done then I had to run the SDK config batch file because I use my own path to FSX and not the default.

Roger that Jim!I

GeorgeI have 4 different commputers running FSX (3 XP's, 1 VISTA)I also purchased 4 FSX delux programs so activation would not be a problem. Each FSX with the SP1 shows slightly different behaviors amoung all 4 computers. It is no wonder that when someone has a paticular problem that posters give many different reasons on how to fix (tweak) it which then becomes more of a computer OS issue then a FSX issue.Most of what I see with path and dll issues are also present with the XP versions but there is no consistancey when loading FSX/SP1/SDK version "A". One of my XP's with default paths load traffic tools and all the 3rd party flawlessly except for dll's that FSX.exe is looking for but can't find. I reported this to FSinsider but SP1 did not address it.The XP's are a little more forgiving then the VISTA which is a new Alienware ALX duo core intel 3.2 Mhz, quad GTX 8800's and 4 GIG of Ram.With the XP's I still had to defrag and then install the SDK updates, run the SDK config batch before Traffic Toolbox would show properly. Those XP machines are using a non-default path for FSX. Tweaking the XP machines do vary with all the high end video cards used in each vs the VISTA machine with the GTX8800's. Just because one type tweak works for someone does not mean it is going to work for someone else.