Why can I no longer swap in a GPS window from another plane?

[Mac6737]

A few years back, I was easily able to import a GPS window into a payware plane (e.g., Alabeo vintage aircraft) that lacked it. I did this a lot. I would find a resident FSX plane that had it, go to its panel.cfg and simply copy and paste the instructions for the GPS window into the second plane, making sure to add it to the list at the top of the file (i.e., "Window0X=GPS"). Never had any problems.

 

After replacement of my crashed PC last month, I upgraded substantially, switched to Windows 10, reinstalled FSX, SP1 and Acceleration (separate saga; see thread). I was able to get my links and product keys from FSpilotshop and others, and am back in business. Oh boy!

 

But my old trick no longer works. Yes, I first went to Properties\Security of the panel.cfg file of the transferee plane, and gave myself permission to do everything, but when I tried to save the amended panel.cfg, Windows would not let me. Said it was "unable to create file" or something, and told me to make sure the disk was not full. (I have 1.7 TB vacant!) BTW, all of these files were written onto my hard drive since the upgrade, and so there should be no compatibility problem, right?)

 

(Why Alabeo doesn't put GPS in many of its excellent products is another mystery, but not for here.)

 

Thanks all,

 

Mac6737

 

Windows 10

FSX with Acceleration

Core i7-8700

ASUS GTX 1070 video card

Z370 AORUS gaming motherboard

27" msi gaming monitor

[KChapman]

Is FSX installed in Program Files (x86)? Sometimes Windows won’t let you edit .cfg files when in this folder.

[Mac6737]

Certainly. That's the default. But FSX has been in there for at least a decade and I never had this problem before.

[MrUnSavory]

Yes, but it wasn't in there a decade ago in Windows 10.

[Mac6737]

Fair enough. So, what do you suggest? If I can't edit a .cfg file that's in FSX that's in ProgramFiles(x86), can I remove the damn file to the desktop or someplace, edit it there, and then put it back where it belongs?

 

BTW, when my PC crashed last month I was effectively forced to go with Windows 10. It has been an unrelenting PITA. All contacts lost, no way to an email folder, printer malfunctions. I have spent at least 30 hours in the past 3 weeks on problems solely resulting from going from Win 7 to 10.

[KChapman]

You can try moving, editing, and replacing- hadn’t thought of that to be honest. I ended up uninstalling and reinstalling FSX and all addons in a folder on the root of another drive.

[tiger1962]

Fair enough. So, what do you suggest? If I can't edit a .cfg file that's in FSX that's in ProgramFiles(x86), can I remove the damn file to the desktop or someplace, edit it there, and then put it back where it belongs?

 

BTW, when my PC crashed last month I was effectively forced to go with Windows 10. It has been an unrelenting PITA. All contacts lost, no way to an email folder, printer malfunctions. I have spent at least 30 hours in the past 3 weeks on problems solely resulting from going from Win 7 to 10.

 

Been there, done that and gone back to Windows 7 after 5 months of Windows 10 nonsense like this.

Any .cfg file tweaks you make have to be re-applied almost daily due to Windows 10 quietly 'repairing' your 'damaged' system files for you in the background, no matter WHERE the .cfg files are installed.

If you were getting the 'Unsupported Hardware' message before changing to Windows 10, there's a patch for that here: https://github.com/zeffy/wufuc

It works perfectly.

[CRJ_simpilot]

You most likely need to move your Sim installation to C:\FSX. The root of C drive, not the program files.

 

Windows 10 sucks! I wouldn't use it for a Sim at all. And I don't give two shts about anyone else using it either. Read Sig.

[Mac6737]

You most likely need to move your Sim installation to C:\FSX. The root of C drive, not the program files.

 

AFTERTHOUGHT: You have no idea how much pain & suffering went into getting FSX plus Acceleration reinstalled in Win 10. Now you want me to move it to the root? Besides, my REX SkyForce manual warns in dire terms (e.g., "serious damage to your computer") about putting REX into the same folder (e.g. ProgramFiles(x86)) as FSX. So REX is in my root folder (where the Rex installer put it). Five will get you 10 that if I put FSX in that root folder, I will be messed up but good.

 

So I agree with you about Win10, for many reasons other than FSX. But the one thing I think I've learned after messing with PCs since my Apple II in 1987 is that Murphy's Law applies: "If something can go wrong, it will go wrong." Also its first corollary: ". . . and at the worst possible time."

[bmatt569]

When I got my new laptop several years ago I decided then and there to partition my hard drive. The new partition is strictly for my flight sim stuff. (Drive letter is F, naturally. it contains the main folder, Flight. So, my path is F;//Flight/FSX, etc.

 

The laptop is using Win 10. I've never had any of the issues the OP stated. Hope this helps a bit.

[CRJ_simpilot]

I know that's a PITA, but that's what you should have done from the get go. There really needs to be in big bold letters on this site: "DO NOT INSTALL TO PROGRAM FILES!"

 

To be honest, and knowing how messed up Windows 10 is, you may still have issues. Others claim they don't but I've seen a lot of people have issues with updates. Especially that last April update crap.

[StringBean]

REX does not care where FSX is installed, as long as it is properly installed there and not simply moved.

 

The very reason that REX does not want to be in Program Files is why you should not put FSX there.

 

REX needs the freedom to change files in the FSX folder, as do you when wanting to edit a .cfg file for example.

 

For 99% of the software out there, there is no reason to edit the program files needed to make the software run.

 

This is not true with flight sim. It was designed for the end user to have the ability to modify the sim to their liking. That is why there are so many text-based files and easily edited image files instead of having everything compiled into machine code.

 

That ability to modify to your liking is severely hampered if you put FS in Program Files.

 

In the process of creating a 1000 Word documents you will never have a need (or the ability) to modify any of the Word program files.

 

peace,

the Bean