FAC257

Pete >>with that anti-everything stuff running.<< I can certainly understand where that would be a frustrating obstacle. I'm wondering now if the anti-everything stuff I have installed is what might be at the root of this problem. I'm always online even when not flying online. If for some reason my anti-everything set up tried to verify an action of some sort trying to get in or out of my LAN while I was flying, I'm wondering if it could possibly be triggering FS9/FSUIPC into a "false restart" and the creation of that second .tmp debugger file. Possibly during the real weather updating process????? The FS9/FSNav/FSUIPC setup across different systems is probably going to be fairly consistant but coupled with all the different security programs and hardware in different stages of online updates you have a mess. Maybe FS9 is just getting a bit confused. You've given me an idea to look a little more closely at my security settings both hardware and software. I'm going to try some different experiments to see if there's any affect on my problem. Thanks FAC257

Hi Pete >>but it sounds like something is obscuring the whole operation on your screen, or there's some problem with the video drivers.<< Good thoughts and avenues I've already traveled a bit. When I fly off line I'm practically always in full screen mode and when I fly online I'm always in windowed mode. But your thoughts made me try something a little different during tonight's online flying which I'll get to in a second. The other idea about a video driver problem is the first place I also send folks when doing trouble shooting. With the video drivers I've tried it two ways. I use an nVidia 6800 Ultra and had been using the 71.89 set of drivers for I believe about 6 months or so since they first came out. I had not considered switching from this set in the interim because they have proven to be rock solid on my system with great performance and zero problems. Just recently I switched to the 81.98 set for no other reason than I figured I was falling behind in the upkeep and wanted to give them a shot. During this dual FSUIPC message testing I was in a position with my system, to be able to try both sets on fairly clean post-format installs. After a total reformat I put back only my neccessary software and drivers plus FS9 with no add-ons except FSUIPC and FSNav. First using the time proven 71.89s and then after another total reformat I set it up using the 81.98s. same results both times. I can fly fine and dandy for as long as I want using either set. By the same token, using either set, within a few minutes after starting FSNav, FS9 locks up. The only way to get FS9 shut down is to use the Task Mgr. When I try to restart FS9 I get the dual FSUIPC message. This is a 100% of the time repeatable event using either driver set. Your idea that something maybe happening underneath my FS9 during this event was a good one. In order to see what I could see I set up for tonight's online flying a little differently than usual. I use dual monitors and normally I have the windowed mode FS9 running on my primary monitor and items like FSNav, the FS9 comms window and the live voice comms window running on the second monitor. If a message window pops up it's always on the primary display. Tonight I set it up where FS9 in windowed mode was running on the secondary display. On the primary I had only FSNav and the FS9 comms window open. These later two I shrunk them down to a very small size so that I could see 90% of my primary display area. If a pop up message happened it had no place to hide. About 2 or 3 minutes after take off FS9 locked up. The exact condition was that the image in the sim was frozen, sound still going, sim stayed connected to the comms server and the FS9 server. I could even save my flight, and from recent experience I've learned that the save works and my aircraft will be flying right where I made the save,even though the sim was locked up. No pop up messages on either screen. In order to get FS9 off my screens I had to use the Task Mgr. As soon as the dual FSUIPC message popped up when trying to restart FS9 I checked the Task Mgr listings. Sure enough that goofy temp file "~E5D141.tmp" was in the list twice. As long as it is listed twice FS9 will not restart. If I delete either one of the listings FS9 starts normally. For the rest of our 3 hour online flight I ran everything set up exactly how I just described it except without ever starting FSNav. The result as I already knew it would be was that the event never occured again. The above is another 100% of the time repeatable event. >>No, never. Where did you get that impression?<< My "Duhhh" on this one. I had just assumed that being a module type of thing, that FSNav needed FSUIPC. While doing some looking and learning before flying I ran into "Does not require FSUIPC" on the FSnav page. How I missed that I can only atribute to old age. >>Ah .... so maybe if you could get a copy of 4.6 you could at least eliminate 4.7 or nail it that way?<< Before I wrote you the first message that was already on my list of things to try. I'm sure I'll figure it out at some point. This is too smart of a community to not figure out a thing like this if it really is an issue being experienced by others than me. If it turns out to be one of those system specific oddities I'll probably have another "duuhh" moment and let you know what I found. Thanks again for all your input so far

Pete, thanks for the quick reply. It's got me scratching my head also. I think it' pretty clear in the community that FSNav is a very well respected and much used products. That's what has me puzzled. I'm pretty good at isolating cause and effect sort of things and the only thing item that keeps coming back to the top of the list is FSNav. As long as it's not installed I can fly on ond off line with no problems. As soon as it is installed the problem reappears. When I say "go down" it refers to FS9 locking up tight and the message mentioned in the previous part of this thread by tlivio, pops up on my screen. This is the one about two versions of FSUIPC cannot be installed at the same time. I too have looked through my folders and there is no other copy installed. The odd thing is that I'm under the impression that FSUIPC is required for FSNav to work. In my experimental process I pulled FSUIPC out of the modules folder and it didn't seem to affect FSNav's functions??? I was starting that think that the module fsnav.dll was some how acting as the other mysterious FSUIPC. After reading your thought on a second background version still running, that makes much more sense. The only thing that I think I see from looking through the posts in here trying to find an answer to my particular problem is that there seems to be maybe an issue with FSNav 4.7 giving folks some headaches that they weren't seeing with version 4.6. I really appreciate your input and the main reason I ended up in here looking for an answer is that when I punched in the search words "FSNavigator and FSUIPC" after clicking "Supprt Forum" on the FSNav home page and the long list of topics popped up, I started reading from the top down. I just now saw the dedicated FSNav forum way down at the bottom. :)

Hey Guys, I've been digging for an answer to this problem ever since purchasing my first copy of FSNav (4.7) just a week or so ago. This dual FSUIPC.dll copy lock-up problem is exactly what's been beating me up me in both on and off line flying. Through several total re-installs of FS9 and testing my add-ons one at a time, this problem only starts up when I load and try to use FSNav 4.7. This is not a random event. If I run FSNAV for any length of time, it's a 99.99% chance FS9 is going to go down. This is even on a fresh install of FS9 with the only two add-ons being FSUIPC and FSNav. With the percentage of probabilty being very high that FSNav is at the root of the trouble on my particular system, is there a work around for this at this time? BTW I'm running FSUIPC 3.53 Thanks!