December 12, 201114 yr Hi Everyone,I thinking of buying the PMDG 737 - 800 - 900 and maybe other in this range too. Trouble is a Polish friend has told me that he couldn't install it. It went into C: by default. If I buy it should I put it in the FSX 'Airplane' folder?Quick answers if possible please. I'll be in England tomorrow only.britpol Board- ASUS P5QD Turbo CPU- Intel® Core Duo CPU 3.00GHz GC- ATI Radeon HD 4800 RAM- 4 gig Joystick- Cyborg F.L.Y.5 (HID)
December 12, 201114 yr The installer looks for the location of your FSX installation...that's where the 737 NGX should go. Wayne KlocknerUnited Virtual
December 12, 201114 yr Had my FSX been in Program Files it would have gone there. I changed my last install to C:FSX and as this was done properly the Windows Registry was aware of it. Consequently it reported that location to the PMDG 800/900 and the 600/700 installs. I doublechecked to make sure the setting in the path box, that it received from the registry, was correct. Then pressed OK to continue. You should have no problem at all as long as you use a level of common sense about it, no offence intended.Though the location is C:FSX it actually uses C:FSXMicrosoft Flight Simulator X and this can be where some people get confused, it has to be the folder where the FSX.exe is contained. Then it sets up a PMDG folder where none previously existed. Or uses any correct folders already set up, as in the case of already having a JS41, 747 or MD11 in there for example. I have 2 of them, not got the MD11 yet (Santa?), and it correctly performed the necessary additions.Steve
December 12, 201114 yr Author Thanks guys,Absolute beginner here with a lot of years under the belt. Hence, a very slow learner.britpol Board- ASUS P5QD Turbo CPU- Intel® Core Duo CPU 3.00GHz GC- ATI Radeon HD 4800 RAM- 4 gig Joystick- Cyborg F.L.Y.5 (HID)
December 12, 201114 yr Commercial Member The installer looks for the location of your FSX installation...that's where the 737 NGX should go.Yeah, you shouldn't tell it to install anywhere other than where the installer wants to install it.Chances are, he either didn't run the installer with Admin privileges, the registry didn't point the installer to the right place (it happens from time to time), or (and I'm not trying to be accusatory, but it must be said) it wasn't a legal copy. Kyle Rodgers
December 13, 201114 yr Author Well gentlemen I thank you for your thoughts. This is not the only software I've had trouble with, not that I have much.As for the last comment from scandinavian13 concerning 'legal' copy. I'll just say that I'm a new pensioner who has a little money to spare and I wouldn't know where to get one from..But I've checked other comments on the forum and several accusations have been made against others. Is this the norm? I hope not or I'll move to another forum.But as said, many thanks for the advice.britpol Board- ASUS P5QD Turbo CPU- Intel® Core Duo CPU 3.00GHz GC- ATI Radeon HD 4800 RAM- 4 gig Joystick- Cyborg F.L.Y.5 (HID)
December 13, 201114 yr Commercial Member Note that I said "I'm not trying to be accusatory"...Meaning, I'm not accusing you openly of pirating software, but software piracy is hugely prevalent (google any software by name and you'll be inundated with torrents) in today's networked society. As such, I just pointed out an illegal copy could cause problems. That's it. There's no reason to overreact and say you'll go somewhere else. Kyle Rodgers
December 14, 201114 yr Author Thank you for your comments scandinavian13. As I mentioned, I'm a pensioner and far, far from computer literate. Hence my problems getting used to flight simming and it's software. I think it's time to move away from this subject and stick to simming. I accept your comments my friend. I hope that if I post more questions on this forum, you will offer me the knowledge you clearly have.britpol Board- ASUS P5QD Turbo CPU- Intel® Core Duo CPU 3.00GHz GC- ATI Radeon HD 4800 RAM- 4 gig Joystick- Cyborg F.L.Y.5 (HID)
December 15, 201114 yr Commercial Member You should never have to manually set the install path - if it's coming up with C: or something like that, the registry entries for FSX are probably hosed - run a tool like Flight1's Registry Repair tool and it'll fix it. Ryan MaziarzFor fastest support, please submit a ticket at http://support.precisionmanuals.com
Create an account or sign in to comment