Fly Telluride

Agian thanks. I know I mentioned teamspeak and or remote access, and you indicated you where nor familure with them, pehaps that could help. I mentioned the steps were all adressed, and the only difference is of course your new DLL files. l nice. I will go back through every stepand apply them agian. If no changes well we are back to here. I am still courious as to why the warning as it has appeared at Flight1 in respect to there traffic program and your registred version of your program. I am almost tempted to purchase anothr traffic program and install on my laptop as to see if it affects FS9 on my Laptop where your program is registared. There are no PFC files loaded, so it might be intresting to see. Oh well, I tell you what, I appreciate your time and help. I realize I am light years behind you in computer skills. I wished we could have gotten every thing to work. I guess I will be ok till I want to adjust and settings or say load up a four prop plane and creat a specific assinment for it. I will not look forwrd to that. As I mentioned I have appplied all the steps as you instructed and am glade to go back and re-work them agian this weekend. If no changes as in the first time around I want bother you agian. I appreciate your help. Kind regards. Mark.

Hello, I hope you are well. I am in Medical implant sales and travel a couple nights par week and as such am away from the PC that has all the goodies on it. It is Thursday early PM and I may be home tonight in time to work further. I can assure you every step you have asked has been taken on my end. I appreciate your offering all of the steps ECT... The reason I do not comment on every single step is because if they are relatively simple I do them and if improvements where to happen I would report the news. I don’t need to go back and grab quotes, as I am sure you recall you telling me to do the steps and stop being so hesitant. So I tried to move it along for you. I have felt you are rather put off with me as to the time it takes me to get steps accomplished. Through out the discussion I have tried to communicate my fear of getting in over my head with changes and never being able to resolve this issue or even to get the system back to the way it was prior to the install when the menu started appearing covered on the lower bottom and rt sides. I feel no matter what I do here its causing you to be put off with me. With that said I have made every attempt to let you know I respect your bust schedule and most appreciate your extreme effort to help with this matter. I do really appreciate your effort to help me with the errors I have experienced from post install of the program mentioned at the beginning. I do not know what has happened here. All I know is prior to the install of the said program the PFC menu worked and wad visible all the way across and up and down. After the install of said program it is not. It may have not been fully programmed from my end, but it worked. I like you wished it was resolved. You mentioned if it came down to it I could change settings in a particular file, well that’s something that will be a problem for me as I as stated I am not the most savvy PC person in the world/ You asked the other day where I had been because you thought from my comments I wanted it fixed ASAP, well of course I do. However I have a family and other obligations in the case this week while being on the road with work. I have other obligations that take priority, and with that provide the means and time to spend on this hobby. You mentioned Project Magenta and I appreciate you bring it up. Someday I do appreciate you bringing it up. I hope someday to explore that. For now I am feeling like one man in the ocean with a small life raft with the problem from post install (the reason for saying post install is to reference for time line purposes). As you know I cannot re-install the dll from before the install and return the system to its prior state. I have no idea I mention the DLL's because that’s what I thought I remembered the warning saying from Flight 1. I am referencing the DLL warning they posted in reference to your registered version of your software. I hope that you were able to get with them. After you mentioned you were a little surprised that was on there site, the warning that is. The word surprised may not be what you said but for some reason I just remember that part of it seemed to be news. Anyhow, I am sitting in the Hospital food court area and need to run. As I mentioned it is not my intent to frustrate you in any way, All the steps have been followed all be it not as fast as you would like. That is my fault. I will do my best to learn things I don’t understand as fast as possible. I offered to purchased another copy of your registered program for my home PC as a jester of thanks for your help/ As I mentioned I have a registered copy on my lap top that’s with me now. I realize I don’t need the registered version on the home PC but out of respect and appreciation will still more than happily do. Out of your kindness you indicated not to worry about, but I am happy to do so. Maybe we can clear the way after the issues here are hopefully fixed as I would not want any override to hurt your efforts up to this point. I am worried here that you may be out of ways to attempt to get the PFC menu back in tact. I hope something good happens for it to be restored. I appreciate you effort and drive to assist me. I will try to be as much help as possible in accomplishing your instructions as quick as I can. I hope to hear back from you. I guess if all fails us we can put things back the way they were before the Traffic install. I was unable to do so but maybe there’s a way. But again perhaps this will fixed. Again thanks. Sincerely Mark.

Peter I hope to speak with you tommorow. Thanks so much for your help. Mark.

Thanks Pete. I am cuatious if I am unsure if I am following your directions correctly. SO I owe you an appology and at the same time want to followyour instruction from a to z. OK then, I am current with all that I can see and unzipped your last file into FS9 Main folder and of course your PFC DLL into the modules. The new program looks intresting. It told me on start up that the last two items where not conected or somthing about the last two items. All else checked ok. However the bottom 1/4 and rt 1/4 of the menu is like it was last pm. Of course the items in the menu relect your work but still the menu on the bottom and rt is the same as last pm. I will syand by and appreciate you help. I will try to ck here every 30 mins or so for a while this PM. Some guest over but yhis is rally important so they will have to be flexable as I appreciate your time. Thanks agian Marl.

I have the new PFC DLL you made and the Back up both in folders off to the side. I am unsure since you have the info on the sys32 versions I sent you what to do . I will leave the old version PFC DLL in the modules folder of fs9 till you tell for sure what the next step is. It sounds like we are past the step off testing each as I sent you the data on each of the files. Anyhow, better to be carfull here and not mess up agian, Thanks. Mark.

Pete I forgot it is COM I

Man, I cant see the list I jyst tried to send you of all the VERSIONS WITH DATES ECT I hope you get them I cant see them on my end saved. Please advise. Thank you. Mark

Pete here is the file name , location, date created and date modified along with the version# of all results from todays search of COMCTL32.DLL What comctl32.dll Location :\Documents and Settings\Mark\Desktop\FSUIPC\pt scr\search results Created Yesterday, July 03, 2005, 5:36:17 PM Modified Thursday, August 29, 2002, 6:40:50 AM Please look at the create and Version 5.82.2800.1106 Modify dates here? comctl32.dll C:\WINDOWS\$NtServicePackUninstall$ Wednesday, September 29, 2004, 11:34:54 PM Thursday, August 29, 2002, 6:40:50 AM 5.82.2800.1106 comctl32.dll C:\WINDOWS\system32 Saturday, August 18, 2001, 8:00:00 AM Wednesday, August 04, 2004, 3:56:41 AM 5.82.2900.2180 comctl32.dll C:\WINDOWS\ServicePackFiles\i386 Saturday, January 31, 2004, 10:20:50 PM Wednesday, August 04, 2004, 3:56:41 AM 5.82.2900.2180 comctl32.dll C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common- Thursday, December 25, 2003, 3:34:42 AM Saturday, August 18, 2001, 8:00:00 AM 6.0.2600.0 comctl32.dll C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common- Saturday, January 31, 2004, 10:34:29 PM Thursday, August 29, 2002, 5:41:32 AM 6.0.2800.1106 comctl32.dll C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common- Friday, April 16, 2004, 6:56:04 PM Friday, April 16, 2004, 6:56:04 PM 6.0.2800.1515 comctl32.dll C:\WINDOWS\WinSxS\x86_Microsoft.Windows.C Wednesday, August 04, 2004, 3:57:00 AM Wednesday, August 04, 2004, 3:57:00 AM 6.0.2900.2180 They are in the order the search engine reported them. I hope this helps you out. Mark.

Pete the one I just sent to you was the 3rd one down from the top. Agian from the list I typed out last PM. The 3rd one down is the only one that clearly says system32 or at least says it far enough up the file path where it is visable. I hope this helps. Mark.

Pete is this it is the one closest to the list I typed out for you last PM comctl32.dll C:\WINDOWS\system32 5.82.2900.2180 Thank you. Mark.

Heelo, 1st I will be glad to check the folder your asking about. Please tell me whee the System 32 folder is located and the path to the folder you want the version number of please. I am unclear here. YOu mentioned It sounds like it was NEVER right the way it was in any case -- the COM port problem especially. Well the menu worked where I could select the quads that did not stay in the settings. I do however look forward to getting all the planes to slave to a quad once this is reconfigured. I will go ahead with the file you sent and place it in modules after a Back up of the one there now. Also in reguard to the COMCTL32 folders I will need to know where to access them from. The info I suplied yesterday on them was from the search resullts and I was not able to follow them from the search results to there folder. OK Please tell me where the sys 32 is and the path to the folder you want the version of and I will get it to you please.

I just re-sent the pic and the INI. I hope these find you. Please advise. Thank you. Mark.

Hello Pete: You mentioned “Fine. The PFC.DLL is designed to deal with this smoothly and automatically, either be automatic detection of the aircraft type, or by you "registering" each of your aircraft with a specific quadrant. The latter method is surer, but either should work provided you've enabled each quadrant you own.” Yes most of the time it dose, however every so often it will act as if it is unsure which quad is being attached. I know we tell it but with the menu blocked that is a problem. This is mainly between the old style Baron and the New style Baron quads. Oh well. I am looking forward to the feature you described here. That's crazy! Once the correct COM port is set in the PFC.INI file it is NEVER changed again unless you explicitly set it. Even if you unplug the device, the driver will still sit there trying to activate it, forever if need be. I use a Cirrus II system and it all connects with serial or pins what ever the proper terminology is. I don’t have your manual handy but I thought I read there or maybe from Eric at PFC that the serial connections are the most stable. Oh yea I forgot above to mention that most of the aircraft I sim in I set up per your manual and indeed almost always they adapt as set up, adapt relating to the proper assignments in the menu being in place. I think the resets are when its say another piston twin that’s not assigned and I would click Baron quad in the drop down to speed along. You are right if assigned I should never need to see the menu, but to assign the planes I need the menu. I open a lot of zips but don’t create them. My secretary dose that, and she would cause me harm if I asked her to send FS9 files. I could however send another e-mail to you an attach the PFC INI, please let me know. Are the instructions for the windows 32 file you kindly attached as follows: Re-boot and once on desk top before I run and program from there place the file you attached into the windows system 32 folders? Will I need to overwrite or choose no if the message appears when doing this? Also please keep in mind if you want to connect over the web, Teamspeak, remote assistance or what everwould benifit your time the most just let me know. Do you think this can be put back the way it was? I almost feel that I had spent some time in the modules folder that a file next to one I was working with could have been deleted or somthing like that. I dont remember this happening put it is like in Plane accidents 90% of Plane accidents are Pilot error, or so says the workshop leader I heard recently. OK I just e-mailed you (same address as last PM) the PFC INI. Agian I appreciate your time and effort. Mark.

Hey Pete I am just wantinga confirmation you recived the pic and the last verbage I sent was making sence. When ever you get time. Agian I appreciate the help. Now that I think I can send pics would you like one of my last secretary, blonde and.....kidding of ccurse. Talk with you soon. Agian thanks.

OK your pic is on the way. Mark.

Pete. I installed the new FSUIPC dll and there was no difference. I Did the exersice with the (alt m f) and yes this menu is also cut off on the rt 1/4 and bottom 1/4. In fact in the second box down on the rt side of the menu I could barley make out the letter P which appeared to be the start of the second word. You asked "By the way, if you had your PFC equipment all working once, why are you needing to set basic things up again, like the COM port? All those details are stored in your PFC.INI file. Did you delete it for some reason? " The reason is that when I switch from say a B200 to a Beaver, I switch thottle quads to match up to the plane. Right or wrong perodically the com will reset asking me to choose from the drop down menu. Agian right or wrong it has reset periodically. I could just never change thottle quads (my attempt at a laugh). I am on the lap top now but willl go back to desk top and attemy to get you a photo. I know squat about all this but wanted to know if I sent you my modules folder, and also if I was to replace the comctl32.dll C:\WINDOWS\system 32 is 597 KB Applic Exte 8/4/2004 in case it was damaged in the cutting and pasting from trying to restore the system to the time before the install of UT. Just a thought as it would be logical that areas I have been are vernable to mistakes and I was in these areas. You know best. You asked "You can edit these things in the INI file instead of using the options screen if you are really desparate. But it hasn't been that long. You first posted a message on my Forum on Thursday, remember? I replied within 2 hours of thatwith questions that you've only just started to answer (and haven't finished yet!). Your next message wasn't until Sunday (what happened to Friday and Saturday if it was so important?), and that message was merely a repeat of the first one. It is only early Monday morning here (00:45 am) as I write this, so really all of this stuff has been done in one day -- yet you keep moaning about not flying? I have other thingd that require time from my weekends. I wished I could sim all day. I am not moaning just wished I could have seen thew a crystal ball. You time is valuable and I appreciate it very much. My comment of things will be brighter is a common saying where I live. Folk talk I guess, ha ha. you asked Please tell me what happened to your PFC.INI file, from the time when you say "it all worked". Ok, Just some ideas. Trying to be of some help. The PFC INI is in there. I tried to stear clear as it looked if it remembers settings and since I cannot get to them to select settings well I stayed away. I will try your picture now so I hope to e-mail you soon. Also if remote access, Team speak or anything would help in saving your time please let me know and I will do what ever we need to do to move forward. Thanks man. Mark.

I cant get the comctl32.dll files to copy and paste for you to see. So I will have to type them here for you, comctl32.dll C:\WINDOWS\$NtServicePackUni 544KB Appli Ext 8/29/2002 comctl32.dll C:\WINDOWS\system 32 is 597 KB Applic Exte 8/4/2004 comctl32.dll C:\WINDOWS\ServicePackFiles\i386 597KB App Ex 8/4/2004 comctl32.dll C:\WINDOWS\Winsxs\x86_Micro 900KB Appli Ext 8/18/2001 comctl32.dll C:\WINDOWS\Winsxs\x86_Micro 900KB Appli Ext 8/29/2002 comctl32.dll C:\WINDOWS\Winsxs\x86_Micro 900KB Appli Ext 4/16/3004 comctl32.dll C:\WINDOWS\Winsxs\x86_Micro 1026KB Appli Ext 8/4/2004 OK there are all of them. Agian I had to type each one so I am worried about errors. The search results would not copy and paste nor can I get alt prt screen to work. I will keep working on the print screen alt to see if I can get a snap shot of the menu. I hope this helps you in you efforts to remedy my mess. Oh well no simming this weekend but the future can be briter. Thank you. Mark.

Pete; All is ready in reference to updating the FSUIPC to the 3.48. Please note that I will hold till I am clear on how you want it updated. Also do I do the steps you mentioned in the instructions for 3.48 ie the FSUIPC.INI file stepss. Agian I am real worried I (me) that I will make some stupid errors on my end. I guess its the fact I relaced the PFC and FSUIPC dll's back to the ones from the current PFC (I know these are not current but they where what was there before the UT install) page in an effort to follow the warning from UT in an effort to replace things to there previous state in an effort to restore the sim. Also where to a gain acess to a copy (the windows file that you mentioned) that works correctly. At least for the time being I can optian these files from my lap top place onto a disc a ne ready to go if and when needed. I havebbt D/L any thing on the Desk top since the install mess I made in an effort to keep things simple. Thank you. Mark

Also Pete, Sorry but I forgot. You told me you understood the menu issue but stated "Er, sorry, I cannot picture that. what "should be the back ground" in what menu? What's a "menu mode"? " Thata why I re-explianed the menu. I realize you wrote it nut the comment had me confussed. Please except my appologiy for re-stating the menu issues. I was just trying to help. Mark.

Also please understand that the reason for mentioning a registered version was to express my support of your work, and if a fee is needed I am open to that. It was my way of trying to let you know I realize that this is work for you and I dont take your help for granted. Thank you. Mark.

Peter, I thought you did not understand the problem I have with not being able to see the full menu page (any page be it throttles, yoke ECT...) and most worrisome not being able to click on the area that makes choices. The example I made of choosing the com selection on the first page or so is a good example. Please let me know if we are on the same page with this. Also, please tell me if you want me to place the dll into the modules as I want to know if it will overwrite the other. I thought I remembered reading somewhere that it was important to assure there where only one dll file in the modules folder. I appreciate your help and do not mean to frustrate. I really did not understand where we where in terms of being on the same page. It is obvious I am light years behind you with this stuff. My PC has been stuck now for a week and I am worried to do anything until perfectly clear. I cannot make a choice in the first page when I should be selecting which com to select. I cannot see or click on the section as it is covered as I mentioned. For what ever reason last week when I started FS9 the PFC hardware was on (the lights on the radio stack ECT...) put any input I made on the hardware from PFC would not show on the SIM. I clicked on the PFC tab across the top and there was the fist page wanting me to make a COM selection, and I was unable to do this as it was partially covered up. Thus my PC now sits, as I feel the need to be sure of any more steps I make. I have tried replacing the PFC and your dll (the version I mentioned in the initial e-mail) but it will not go back to the way it was prior to the install of UT. I realize I have frustrated you with these basic needs I have. But here I sit. I thank you for your time and will sit tight till I am sure of the next step to take. I am really worried about digging a deeper hole for myself at this point. Thank you

Graet thanks for the feedback let me see if I can do these one at a time. The menu, I am speaking of when you are in FS9 and if you go to the windows mode you will have menu across the top of your screen. One of the items across the top (in windows mode) is PFC. This is Precision Flight Controls. If I click on this then It will bring up there screen. There screen is the screen where you make choices for the hardware to interact with the software (or so it seems). For example in your documentation that I downloaded from PFC you discussed the "com I" or other com choices that needed to be made when setting up things. Things is a term I am using to reference the set up that includes the PFC Cirrus II, FS9, your download of FSUIPC (what ever version you recommend, I could not tell which one you recommended, if you could clarify that would be great. Please remember that I have re-installed the version I mentioned as per the UT instructions with the same bad results). The best way I can explain is that the area where I chose to select a com choice is no longer visible. Part of that area is, but the area where the box drops down is not. So, please specify the version of the non- registered FSUIPC (I use your registered in my lap top and unless needed will only need to buy one copy) needed. Then please keep in mind that all through the menu (menu the area where you configure the PFC hardware, for example choosing the default settings for your avionics ECT...) is covered on the bottom 1/4 and the RT 1/4 through out the selection process. Process is my way of explaining the tabs across the top of the menu that allows you to set up your toke buttons, console selections, ect...) in other words you see the different menu pages but cannot see the area where you make your selections. The bottom line I think is that even when I reinstalled your FSUIPC to put things back the way they where before installed the UT. (UT is my way of stating Ultimate Traffic) This is what the instuctions for this was from the UT people. The sate this warning about your payware version of FSUIPC. The solution as I read was to install the FSUIPC back into the system. So I went to may folder where I D/L your FSUIPC per PFC and I re-installed and stilll have the same issues. I dont see at this point how uninstalling UT would help if I have already re-installed your FSUIPC with no improvemnts, but who knows. I would like to keep UT, Please spell out more questions as I will gladly help as much as I can to give you all the information you need to assist. I appricate your help. Please note: the documentation I referenced from you was per the link at PFC where the had your guide for setting up the hardware ect... Also, this is where I am at now in trying to resolve the issues. Later after this is hopfully repaired then I will be glade to get different or new versions of your or others software. Aldo if I must do this now then thats ok too. I just dont see why when it worked prior to UT that it cant work the same if the FSUIPC's are replaced unless I must dump the UT for now. Thanks agian. Mark.

Hello, I presently use the Precision Flight Controls Cirrus II console with FS9 and the .DLL file, Version Release Date March 2005 version 3.47 FSUIPC.DLL This is the version recommended by PFC. On my laptop with FS9 and a Joystick I make use of the payware/Reg version of Pete's fine work. Here is what has happened. All was well with the set up mentioned above, PFC, FS9 and 3.47 .DLL. The Cirrus II console worked fine and running smooth. Last week I installed a product called Ultimate Traffic from Flight1. Now there are a couple of small issues that can get out of hand real fast. The issues that can get out of hand first. This is that when I click on the PFC tab across the top of the screen to view menu options the RT 1/4 and bottom 1/4 of the menu are as if the are covered by the what should be the back ground when in the menu mode. Best example is that I cannot make a choice in the menu for COM I or II. The reason is the place where you click to place the dot for your choice is covered as mentioned above. As long as I stay with the present throttle quad choice and do not need to access this and all other menu choices though out the menu pages (note that on all menu pages the RT 1/4 and bottom 1/4 of the screen is covered as what appears to be the background when normally in the menu mode). This was not the way things were prior to the install of Flight1 Ultimate Traffic. I have found on the web site for Flight1 that there is a warning of issues with Pete’s FSUIPC registered version. (Please note the system being discussed is set up with the hardware mentioned above and the PFC’s recommended FSUIPC version 3.47). Now the warning on Flight1’s web site is for the registered version of FSUIPC, as mentioned on the computer mentioned I use 3.47. Though out the Flight1 web site they discuss having a back up copy of the FSUIPC .DLL files to reinstall in case one is affected by the download of Ultimate Traffic and or Ultimate Traffic updates. Well I have gone back several times to re-install the 3.47 .DLL files with and without the corresponding PFC drivers in an effort to restore things as they were before the introduction of Flight1’s Ultimate Traffic. The end result is the same with the RT side and bottom ¼ of the menu appearing to be covered by what should be the back ground or appears to be the back ground for the PFC menu that is accessed from the PFC tab across the top of the screen when in the simulator mode. So flight1 resolves the issue by having the .DLL files placed back in the “modules folder” of FS9. Well as mentioned I have replaced the FSUIPC. The PFC driver file and a combination of the two. The result is the same. So I have tried the Flight1 remedy and no luck. Well one would think to uninstall flkight1 Ultimate Traffic to resolve the issue and hope that Flight1 refunds my cash. Well if I have already replaced the FSUIPC file and the PFC file and a combination of the two together (PFC has a D/L that installs both into the FS9 “modules folder”) then I am unsure if uninstalling Flight1’s Ultimate Traffic will matter. As they stated for the fix I have replaced the .DLL files. Real world, with the exception of PFC and there support team I am out here in no mans land. Except for PFC you cannot speak to anyone. You right a few letters only to receive a response with questions requiring more typing which if resulted in a solution would be great. But the bottom line is that getting a solution or my cash back from flight1 is a testing process. I have spelled the problem out as to exactly what happened. Sometimes I fill the click and paste questions are a way of dragging things out. I do not mean to sound negative, but I am really worn down with this. If nothing else I owe the readers of this problem a fee for at least letting off some steam. Computers are great, but a phone conversation at this point with the powers that be would be pretty nice right now. If any one has any ideas to resolve this I am open to, and thankful for any help. Flight1 has a web site at flight1.com, look for the Ultimate Traffic area and the UT updates, PFC has a web site at flypfc.com there you will see the area for drivers and find the D/L for PFC and Pete’s latest .DLL and drivers. I really appreciate the effort to help. Thank you, Mark.