I am looking for someone who has experienced the same problem and found a solution to it. I have been in touch with FSD's support on this and they have been very kind in trying to help me.I have successfully installed the FS2004 land, amphibian and ski Porter on a new notebook running under Vista (T8300 Core 2 duo, 4GB DDR2, NVidia GeForce 9500M GS Turbocache with 512 MB dedicated memory), as well as the land and amphibian FSX versions, but I am unable to install the FSX ski version. I have downloaded the latest install file from FSD and their support did send me a licence repair tool, but to no avail: the installer would crash upon starting (seamingly) the activation process. I have sent the error code produced by the failed installation to FSD.If you have experienced the same problem and have found a solution, I would be very interested to learn about it.Thanks,J.J.Jean-Jacques StruyfBraine-L'AlleudBelgium

Start your machine in "Safe Mode" then run the intaller...Reboot the system, load FSX and go skiing... er, I mean flying!

Bill, I had tried that before already. Just to make sure, I tried once more before answering your reply here. It is definitely the installer that fails. Upon starting the installer, I get this error at address C1FE0BC139872467993AF36F1A. After having received the error the installer quits but the on-line activation window remains open and when I click on "activate", the activation process completes successfully.J.J.Jean-Jacques StruyfBraine-L'AlleudBelgium

That's too bad. I'd hoped that this would help you to be successful. I have no idea whatever what that address means in terms of their installer. :*

Yes, it's too bad, because this will prevent me from buying any new plane from them despite the fact that they produce very good ones. FSD planes are amongst my preferred ones, together with Carenado, Dreamfleet, Eaglesoft and PMDG.I did send them the report and they said that a program wasrun on my computer which has damaged critical data used by the FSD license system. I used the license repair tool that they did send to me, but the installer still failed. That is why I was wondering if I could find here someone who had exprerienced the same problem and found a solution to it.Thanks for trying to help me Bill,J.J.Jean-Jacques StruyfBraine-L'AlleudBelgium

Jean-Jacques,Don't give up. Sens us a message through our support terminal and we will get deeper into it and see what needs to be done to correct the problem.Tim Dickenshttp://www.fsd-international.com/team/TD_forum_sig.gif

Thanks Tim, I'll do that.J.J.Jean-Jacques StruyfBraine-L'AlleudBelgium

>Yes, it's too bad, because this will prevent me from buying>any new plane from them despite the fact that they produce>very good ones. FSD planes are amongst my preferred ones,>together with Carenado, Dreamfleet, Eaglesoft and PMDG.>>I did send them the report and they said that a program was>run on my computer which has damaged critical data used by the>FSD license system. I used the license repair tool that they>did send to me, but the installer still failed. That is why I>was wondering if I could find here someone who had>exprerienced the same problem and found a solution to it.>>Thanks for trying to help me Bill,>>J.J.>>Jean-Jacques Struyf>Braine-L'Alleud>Belgium Well I recently had a similar error code when I tried to reinstall my FSD aircraft after reinstalling FSX on another drive and was told that I was a thief and the installer failed because the registry had been modified by the use of a KeyGen device and I would have to reformat my computer in order to use FSD aircraft again. Well, I told them that I'm 64 years old and didn't know what a KeyGen was never mind how to use it and had valid licenses for the C337, C115, Saratoga & Seneca but it fell on deaf ears. They acknowledged the valid licenses but claimed the following illegal fsd aircraft were also on my computer: Piper Cheyenne 400 V1 , Pilatus Porter V1, Piper Navajo V1, Aerostar 700, Piaggio Avanti, T38/C17 and Cessna 0-2A. I've never had nor tried to install any of them and most aren't even compatible with FSX anyway.. In the past I use to be an FSD apologist always scoffing at reports like this until it happened to me. Hope you have better luck then I did.

All is fine now. Tim Dickens did send me a new installer and everything is working well.A big thank you to FSD' support.J.J.Jean-Jacques StruyfBraine-L'AlleudBelgium

Congratulations and thank you Tim:I hesitate to respond as I am still useing my FS9 FSD models in FSX with results that are pleasing to me and I am afraid you will be mad at me for not buying your latest FSX models.Responses like yours to this post negate all negative posts relative to FSD IMHO (including the one previous to this reply). Your kind reply and others like it produce the best advertisement FSD could have for your dandy contributions.Keep up the good work.Respectfully:RTH

I concur with that. This is not the first time that I am being helped by FSD technical support, and I have always been very happy with it. My first attempt with FSD's support about this install problem led me to believe that the problem might lie within my own system. This is why I came here, in search for someone who might have experienced a similar situation and maybe had found a solution. But Tim finally could reproduce my problem and gave me a new installer.Jean-JacquesJean-Jacques StruyfBraine-L'AlleudBelgium