Fsinn and vista

While we agree it's unlikely that Flight Simulator will be fixed, I'll give you a logical step that you might find hard to conclude, but that component of FSInn won't be completed either.

They were presented with and update just before SP2 was released. But I really don't think the bashing is a way to promote such consideration.

Again, look at the first page the latest news that will come up when you enter the link you posted: www. The release you describe is the release of the beta project to the community. I believe it's something you should have something good to say about, not a cause for bashing the effort.

I can't identify with how you can see it as good for one by a cause to bash the other. When you speak of media player, you're probably thinking of the Sky Blue Radio feature which the installation steps describe how to disable to avoid the exit error. I don't think you can show me a link with someone having a problem with FSInn and Media player. I scan the internet often to look at issues that people might have with it. It's something I haven't seen.

If I find something new, I'll study a resolution and link it to the installation steps for the convenience of all the FSInn users. While I agree that would be something noble, your messages on this matter hardly appear to me as an effort to help the user by giving support. It appears mare like and issue to discourage the user from giving the pilot client of his choice a chance. I really don't think avid Mac users should jump in every time the see a question from a PC user of how to use his PC by telling him to dump his PC and buy a Mac.

I would find him intentions especially suspect if he happened to pick components that were common with both a PC and Mac to bash the PC while praising the Mac. The first user immediately gave this user a link that resolves that issue as well as any other issue someone would have with FSInn. Sorry you missed the page. You're still giving false information about setting up FSInn.

That's might also be a reason that you had a bad experience with it. I'm sorry you did. But the steps are very simple. While I do everything I can to keep the quick installation reference sheet extremely short, I did include, "you must not put a check mark to run any of the FSInn modules as administrator" in the sheet.

You continue to try to force this step, which shouldn't be done and can cause problems. You also complain about this step that shouldn't be done, for having to do it. This, like all the other items you're throwing out has nothing to do with FSInn and is very misleading. It's a very rare occasion. Having a registry issue is rare. Many people have Flight Simulator running without corrupted registers.

However, for the few that might have a registry issue, like any other problem a person might have with FSInn, it's provided VIA the very small installation sticky. If you take a break from bashing FSInn for requiring an uncorrupted registry, you might also notice Squawkbox looks for one also. I don't see a lot of your messages giving support to the Squawkbox users who have the installation issue.

The response to most of those comes from either me or Norman. Norman usually tells them to download the registry tool from flight1. I usually tells people to download fs9tool. No bashing, no fanfare. Just repair the registry and proceed with the install. FSInn doesn't come into the picture.

By the way, this is the Squawkbox developers reply to the corrupted registry issue: It appears to be described "Installer fails if registry entries not in place". The resolution appears to be "wontfix". I don't make this reference about Squawkbox or its developers as a bash. But again, I believe it's very misleading for you to bash the FSInn developers for doing what might not be as uncommon as you try to suggest when it comes to FSInn. I can't identify with the all that.

But I guess a person can drive all over town to go across the street. But it might be more convenient to just walk across the street. In other words, just person the steps in the quick reference sheet and as you mention, it'll work fine. Too bad you missed it. And for some reason, even as now, it has been suggested to this user with an issue, you're trying hard to bury it. The first reply gave him a quick installation reference sheet that won't fail.

For some reason, you're suggestion that there's some type of requirement of spending lots of valuable time going all over the web. I don't see a problem with suggesting a different client, per se. However it's one thing to suggest a difference client and something else confuse the whole issue by posting a lot of false statements about the product in question; and also make statements that are common with both and suggest dropping the one for that common component.

I believe it's very much in order for the new user to have this information also. He had a simple installation glitch. The first reply gave him the resolution to that, plus the installation steps that will resolve just about any issue he might have with FSInn.

You confuse the issue by giving suggestions about installation the client that would cause problems. Idealistically the next person that has a simple issue with FSInn will see the truth about the ease of operation and will not be confused what you've placed here as possibly everywhere you see an FSInn question. You might not be doing this on purpose. But if you look at the link from the initial response, you'll see you're giving false installation suggestions.

I don't see others making comments to bash FSInn. Only you. Hi, Gregory. You're right the installation problem was very minor. It's also very rare that it happens. Manually copying the. The installation is very simple. Just follow the installation steps given by your Sim-bud and you shouldn't have any problems.

Review those questions also. You won't have any issue that isn't resolved by reviewing those two messages. I'll still be glad to help if you do. By the way, I notice that Grunt is suggesting that you go all over the internet for fixes. He also gave you a list of steps to do. His list is bigger than the steps in the link you have above. His steps might cause you problems and confusion. By his messages, he had problems. Normally there isn't any issues Of course if you have a registry problem, it doesn't matter when you run it to fix it.

You don't sound dense the least. Glad to be of asistence. Great list!! You have an outline for a webpage there!! It was all very clear about 1-hour ago, but I'm having doubts again. Getting lots of good advise from multiple sources. Some of us can misinterpret enthusiasm as negative.

Will also do a system restore point just in case. One other source would be the VATSim forums. I was reading and replying to the messages as I saw them. This last message appears to be good advice for the user with FSInn. The tone and intentions sounds different from the previous messages.

There's a chance that one of the problems you were having was looking for support on the FSInn web site. It wasn't designed as a support site, it was designed for being a programmers' site. Lots of people were frustrated because they logged on to the site and tried to get the developers to fix their OS and teach them how to use their computers.

The management didn't want that type of flow. I understand, it was something different than what you expected and was looking for. Wrong terminology but the error exists and has a workaround. I was going to answer more but with you saying I am making false statements and giving me credit for statements I did not say I feel further discussion is fruitless. The short of it and you can ignore it all you want is that there are well documented issues with FSInn that many people encoounter during the install.

They have been there since the beta was released and since it's a beta issues are expected and if development had continued they would have been addressed. Development ceased so we have to work with what we have. I gave Gregory a heads up for what he might expect so he won't get frustrated by fixing a problem and then finding another, fixing, it and then finding another and so on.

I felt that's better than saying follow this guide and it always works, it's only this issue, etc. If being honest and telling a user what he can expect ahead of time is what you consider bashing then so be it.

I use and have used both and will continue to do so and I'll be honest about both also - of course I haven't seen much discussion on SB here probably because it's not used as much. Each covered a different aspect so between them I got the whole story. The bottom line is that FSInn has install issues that many have encountered. But that is to be expected - it's beta and if development had continued the issues would have been fixed. Development did not continue so we work with what we have - a version of FSInn that works with FSX and that's a major plus.

The downside is we have an FSInn that has install issues and most people will see some of them I never had an issue with registry corruption or missing slashes for FSInn although I have for other apps if not all.

The best thing for all is to let the user know what he might see, that there are workarounds, and to keep perservering. When it's installed FSInn runs well and has some neat features that no one else has and since SB seems to be neglected and there are no others being developed it's the best choice you should see what X-Plane has!

I thought that was misleading. You suggest problems with FSInn as if it should be I'm trying to find a different word than bash that means harsh criticism harshly criticized, while having problems with computer applications are so common.

If you pick something that I said that you didn't say, I'll either apologize or point out that you misunderstood something that I had said. I thought you made a false statement by suggestion that FSInn was inferior to Squawkbox because it is released as Beta.

They are both. I quoted your statements that I disputed. I didn't just say you made those statements, I replied to your statements with facts. Please quote text of one of my messages that indicates a statement that you didn't say? I would be very glad to retract a mistake that I might have made, or clarify what I meant with everything I have to say. You said you have to run the modules as administrator. That is false. The application is very robust and some of the components will work when done wrong.

But that suggestion is a false statement and would possibly cause any one trying to use FSInn to have the same problems that probably made you drop it. Had you used the support channel that I gave to this user, you probably wouldn't have such harsh criticism about FSInn.

You make a lot of statements that I consider false. I'd be glad to see this well documentation you speak of. If it was so well documented, I believe you could link to it rather than just saying it. I gave you a link with a quick reference sheet that works. This is a fact. Your references about your well documents many install failure issues are something I'd be glad to learn. I wouldn't ignore it.

I'd add this documentation to expand my knowledge and ability to give better support. I appreciate your reference to all the problems you had. You had lots of problems and thought it would be best to bring the problems to a new user who doesn't have to have them. I can't see saying the application is beta with lots of issues and problems, check out Squakbox which I switched to because of the problems.

I can't deal with beta programs that are not being developed. You speak of my ignoring problems. Take a look at the link you gave me.

There is a forum there. There are four issues being discussed that were posted within the last 24 hours. It's clear that you're blind to the issues with Squawbox, but you very animate about bashing FSInn for having issues.

Squawbox is a fine program just like FSInn. I don't know of any programs that are popular that people don't have issues with. I understand that you see it different. But you might consider that what you're saying is based on people like yourself that are doing haphazard things with the application rather than showing respect for the installation steps and usage. I won't as you say ignore the issues. I'm trying to explore the issues and address them. You might consider not ignoring the resolutions.

I understand that you don't believe it, because you didn't test it for yourself. But using the installation link will provide a very easy install and successful experience with FSInn. I see you subsequently retyped most of the steps in a message to him and he was up and running.

I believe bringing up a whole lot of issues that a user won't have if they follow the installation steps would be a bigger burden and more frustrations than it's worth.

Had I read your comments with my first question about FSInn and I didn't know what I know, I probably would have thought I was speaking with a very experienced export and have been frightened away from it. I probably would have went to Squawkbox as you suggested, and looking at the Squakbox support forums, possible had just as many if not more issues and felt relieved with a whew, what if I had went the hard way.

It's unlikely if you reply to a Squawkbox user's question that he's having problems installing Squawbox with a big, you're using an unsupported, discontinued, beta. You're probably just say run the registry repair tool and the thread would be over. That probably wouldn't frighten the user away from the application. I believe to tell the user, as I'm doing, that he won't have any problems as long as he follow the short quick installation reference card. The four steps will give him an initial connection.

After then he'll be a single click away after starting Flight Simulator. If you have a question, just yell. I'm sorry, but I have to dispel your "facts" about the application being such a great source of frustration. I don't think it has to be.

Ok you guys.. FSInn is installed and there's no apparent problem other that the firewall messages. No need to keep bantering about clients, etc. Thanks for the help!! The google search for keywords in this group doesn't find Jack anymore. No fire intended. But with me, where FSInn is concerned, support and resolutions if there are problems, abounds. For convenience and consistency I always start out with the installation sticky.

In this case, like all your questions so far, this is provided. Click on the original link you posted, then click on the provided link to the FSInn Manual.

By the way, thanks for the compliment on the operations of FSInn. I believe it's very stable and ahead of its time. I'm certain there'll be an FSInn or pilot client by a different name to appear in time for the next generation of Flight Simulators that materialize. Let me know how you make out with the pictures and features. While I'm not the author, I praise the developers for the great job of the details, I proofed the manual with passion before it was released.

I had the Chat window error but could not recall that you posted the comment above. Someone kept initiating a Chat session but I could not respond. It kept chiming and chiming. Eventually the controllers left duty at KBOS.. Had to run FSInn alone from the start menu first. Actually submitted a flight plan and did a short flight last night. It even showed up on ServInfo!! Next I need to connect a Mic. Would you prefer a clip-on Mic, or one on a long sloping boom with desktop pedestal?

I'm sure it was frustrating. This is why I strongly encourage FSInn users to read the original link you posted in its entirety. I have also kept it short to make it easy for it to be read in its entirety. It goes from the initial download to the first connection. I know you know now after having suffered frustration.

But when you first got the error if you had glanced at the link you could have just opened FSInn from the start menu and replied from there or from the other FSInn panel you had. Some people mention that you have to restart Flight Simulator. But you don't. Just click on the resolution and you're in business. If you haven't read that link, I strongly suggest that you do.

Controllers control their space just like in the real world. If you are located in a vicinity that isn't manned, you're on your own to use Unicom for separation. So the show they really control is their space. Take a look at the required reading section and the First Flight Lesson. They don't turn off ATC in flight simulator. This is mentioned in that quick reference sheet the link in your original post.

I believe you'd be surprised at how much is covered in just a small amount of text. People understandable can get frustrated and a bit overwhelmed when looking everywhere to get FSInn up and running. This might have something to do with some of the frustration that Grunt felt which caused him to go to Squawbox.

However, knowing these things ahead of time and getting them taken care of doing the install can spare the user of frustration.

You'll have a better chance of seeing it as the very consistent and stable application that it is. I don't mind answering any of your questions. I'm just giving you a heads up for some of the issues that might appear as annoyances that you don't notice, but could be spared from by reading the installations page.

Were you even at Hawthorne? You can have it refresh automatically by setting options in the connections parameters. You have a plane that FSInn doesn't recognize. Use the "Edit Current Used Plane" option. Then fill out the known information under the Green User tab. The pulldown IP list wasn't populated like in the illustrations, just one that didn't work. I was never at Hawthorne, but parked on the south ramp of LAX. It didn't make any sense.

Loaded up back to Boston and the controllers has left. Also tonight.. ServInfo cannot update itself from the server. It says the data is 1hr, 37min old last was Does that happen now and then? The original messages tell exactly what to put in the settings and were to get working IP numbers. Yes, this happens every now and then. There currently is a problem with the data servers. It usually doesn't last long. Of course the description you just gave with Servinfo's behavior is an indication.

My logs indicate it started about 4 hours ago and is still a problem at this time. Unfortunately you can't check to see your location status until this data server issue is resolved. What Link?? I guess I have to read the PRC page again. I have a couple hours but I always flew around Texas and there were no controllers.

The tower controller in Las Vegas called me up just to chat. He wasn't busy either. I think he means the link in the OP.. It's a big and daunting step, and for anyone mildly interested in the Virtual air world, a good place to start is by installing ServInfo. The more users the better! I know that you know about this stuff many of you already. Yes, I did read over all of the instruction from three advisers but when it came to tackling the whole thing initially it can be a challenge there were details missing.

Let me point out one such detail from link in OP.. It says.. One of the figures showed a drop-down IP list which wasn't there. Please don't mistake the tone here as harsh or angry. I'm only identifying a tripping point for the new user. You may want to edit or clarify this important step. I've been giving this support for nearly 6 years.

Most of the people I'm not saying you who have problems, have problems, because they haven't read looked at or tried the steps. It's an extremely rare occasion that people who actually follow the steps have problems. I am extremely meticulous about keeping the quick reference sheet small. On rare occasions someone will give me a suggestion for something that should be added.

However, on most of those occasions, adding the note would be a bit redundant and have the effect of making the sheet bigger. On most occasions the additional information wouldn't be so helpful, because the ones who actually have problems with it, are the ones who haven't read or tested the steps anyway. Those people would still miss those added steps if they were there. As far as using the word server IP, that's not necessary. You can actually put the server name there. Most people are familiar with punching in servers or IP numbers because many of them have already experimented with Flight Simulator's multiplayer features, as well as other multiplayer games.

I don't mean to sound callous and inconsiderate by not updating the link based on your suggestion. I'm just pointing out some of the considerations that have gone into play while considering what you feel is missing. This can occur when the user running the application is logged on under a different user account than the user account who installed the application, and the installation package installed the application on a per user basis.

Thanks James for your input. So I assume the registries in Vista 32 and Vista 64 are different. Maybe this is the problem - Vista 32 and Vista 64 aren't talking to one another. I am a real novice when it comes to Registries so I normally leave well alone. I only look or change something specific if I have clear instructions too follow. Hi do me a favour and on your second PC try startig FSinn from the start button under FSFDT, you will see a number of icons there so click on Control Panel, this might get past the problem, afterthat you should be able to start FSinn in the normalmanner.

It loads and displays the Control Panel. If the file is there then perhaps it's not been properly registered during the install process. Search "values" but not "data" and "keys". Chat, etc. Thanks James for explaining what Wycliffe was on about. OCX or one of its dependencied not correctly registered: a file is missing or invalid.

Can you clarify- in an earlier post you said that you could load the control panel and all buttons apart from SET are working, but in your last post you said that bringing up the control panel results in an error with COMDLG Copying an OCX file is not enough; it has to be "registered".

OCX and it's not present then something has gone awry during the installation process I guess we knew that already! What's also interesting is that you say that you used to have this working on this machine; suffered a hard disk crash; reinstalled FSInn and then this problem started.

Can you tell me a little more about your hard disk layout- the implication is that you did not lose your Vista system drive as you don't refer to reinstalling Vista first. Were FSInn and FSX on the same drive presumably not as you asked in your first post about whether you would need to reinstall FSX, so you obviously didn't lose that installation. I was going down your route about the registry etc when I saw your question regarding UAC.

I never thought about trying with it off Thanks for all your time in helping me to sort it out. I really appreciate it. You will be able to leave a comment after signing in.

By Kevin Swindlehurst, November 12, By Henry Cleaver, August 5, By John Pettit, May 18, By John Pettit, May 16, By Nigel Radley, April 15, Share More sharing options Followers 2. Recommended Posts. Don Fraser Posted October 9, Posted October 9, I have developed a strange problem with FSInn and I don't know what to do. It works fine on my main PC but when I try to operate it from my 2nd PC I keep getting the Run-Time error '' I have trolled through the various forums and I haven't come across anyone having the same problem.

Thanks Don. Link to comment Share on other sites More sharing options James Reynolds Posted October 9,