I have a laptop that I would like to load Active sky evoultion on. I have intstalled it, and when I tried to start it, right away it could not locate fsx. What do I do to tell it its on a network, and fsx is on another computer? I guess thats the first thing to do..

An easy thing to try would be to use the free TweakFS FSX Registry Utility to try and set your laptop's registry to point to your PC's FSX Folder over the network (I'm not sure it will work with networked folders, but it might), and if that works, try and install ASE, as ASE would now know where to look for FSX. Cheers, - jahman.

An easy thing to try would be to use the free TweakFS FSX Registry Utility to try and set your laptop's registry to point to your PC's FSX Folder over the network (I'm not sure it will work with networked folders, but it might), and if that works, try and install ASE, as ASE would now know where to look for FSX. Cheers, - jahman.

HelloJahman haver you ever set up ASE over a network?

I have a laptop that I would like to load Active sky evoultion on. I have intstalled it, and when I tried to start it, right away it could not locate fsx. What do I do to tell it its on a network, and fsx is on another computer? I guess thats the first thing to do..

Hello You will need to set up the necessary network shares and configure a couple of simconnect configuration files.The easiest way is to read from Page 52 of the ASE manual which describes in easy steps how to configure ASE over your networkThis takes you through setting up the network shares and on to configuring Simconnect.There is a Hifi Simulations forum here at avsim where the developer Damian Clark will be happy to help you get this working.

HelloJahman haver you ever set up ASE over a network?

No, I was just advising an real easy alternative to try, and if it didn't work, nothing lost. Is that wrong? Cheers, - jahman.

HelloThe intent was not in any way wrong, you were only trying to be helpful.It was never really an alternative though was it?, and could potentially have caused further issues. It was clearly a networking/simconnect issue and the answer lies in the ASE manual thoughtfully provided with the product.If the FSX directory plus a few more locations are not shared correctly then no amount of pointing the client machines registry towards FSX is going to establish a network connection. I tend to make a policy of only answering questions that I have personal experience of and am sure of the correct answer otherwise what is the point.

HelloThe intent was not in any way wrong, you were only trying to be helpful.It was never really an alternative though was it?, and could potentially have caused further issues.

No, no further issues could have been triggered due to connecting his laptop with his FSX PC, something he would have to do anyway. Note he does not have FSX installed on his laptop, so running the FSX Registry utility on his laptop wouldn't have caused any issues there either (and it's a great tool to have, so it was worth a try).

It was clearly a networking/simconnect issue and the answer lies in the ASE manual thoughtfully provided with the product. If the FSX directory plus a few more locations are not shared correctly then no amount of pointing the client machines registry towards FSX is going to establish a network connection. I tend to make a policy of only answering questions that I have personal experience of and am sure of the correct answer otherwise what is the point.

Fair enough, but in this case you are also answering a question without providing specific information, only an indication to go read the manual (which was going to be my next recommendation anyway if what I recommended first didn't work and if no one else chimed in with specifics). Cheers, - jahman.

No, no further issues could have been triggered due to connecting his laptop with his FSX PC, something he would have to do anyway. Note he does not have FSX installed on his laptop, so running the FSX Registry utility on his laptop wouldn't have caused any issues there either (and it's a great tool to have, so it was worth a try). Fair enough, but in this case you are also answering a question without providing specific information, only an indication to go read the manual (which was going to be my next recommendation anyway if what I recommended first didn't work and if no one else chimed in with specifics). Cheers, - jahman.

Hello "The easiest way is to read from Page 52 of the ASE manual",That was about as specific as it is possible to be, a direct link to the correct information.I run ASE over my network and really the info in the manual is the quickest way to set it up without problems.I would not have been able to explain the setup in any clearer terms than the text written by Damien.It is exactly for this purpose that the developer took the time to write that chapter.

Agreed, which is why my next recommendation would have been exactly that. The reason I don't refer the OP to the manual first is I assume the OP already checked the documentation. Cheers, - jahman.

HelloIt was obvious to anyone who has actually read the documentationit or been involved with any networking that the OP had not even got as far as the index.Now it is great to help folk with their issues but there is nothing wrong with taking the decision not to post if you genuinely do not know anything about the question.Which you obviously didn't, to offer the suggestion to edit the registry in an effort to set up a network share speaks volumes.

"Let Being Helpful Be More Important Than Being Right!"

"Let Being Helpful Be More Important Than Being Right!"

HelloFair enough Bill , I will refrain in future from offering any correct advice, I'll leave it to those who prefer random shots in the dark while being "helpful". After seven years and over 2500 posts mostly trying to help folks, I think sadly it is time for me to leave the Avsim forums.

Which you obviously didn't, to offer the suggestion to edit the registry in an effort to set up a network share speaks volumes.

That is incorrect: As I stated previously, I suggested a network share (which he will need anyway), and separately the use of a valuable tool to point the registry in his laptop to the FSX install on his PC. Note that we are all human here, so in our attempts to help others at times we may be more successful and at other times, less. In any case there is room for all, so if your decision to leave the forum is just because of me, I ask you reconsider, as I would welcome you to stay. Cheers, - jahman.

HelloFair enough Bill , I will refrain in future from offering any correct advice, I'll leave it to those who prefer random shots in the dark while being "helpful". After seven years and over 2500 posts mostly trying to help folks, I think sadly it is time for me to leave the Avsim forums.

Actually, my "suggestion" was offered generically to everyone, not just you in particular. Especially in technical forums there's no good reason why it should resemble a playground where the guys resort to comparing sizes in a game of "one upmanship..."

yea Im sorry guys I let ya's down... I thought I read through the manual quite thourghly, but obviously I did not, becuase just as stated, on page 52 there is a very clear discription of how to get it set up on a network. I havn't tried to hook it up yet with the new info that I learned, but I think it shouldnt be a problem now (I hope) Thankyou, and I hope nobody is leaving avsim, becasuse all in all, it is a nice community. Happy flying,Michael