Sign in to follow this  
Sesquashtoo

A tip...don't have your P3D on the root of your X: drive...

Recommended Posts

As I had went out and purchased a new drive just to host my P3D install....and had no intention of putting anything else upon it, I thought (thought it would be faster access, etc...) to install directly to the drive, which in this case was my F: drive.  

 

Well..since having P3D, there were a lot of times, that P3D would ramp up to 99 percent of the set-up travel mask...and then CTD.  If I deleted the SHADER folder..I could on the next attempt get to the numbers.  Well...Virtuali from GSX fame, told me yesterday in a thread (I was having his GSX installer crash out on me...) that that was a NO NO..and it would/could cause all sorts of install/running problems with software.

 

HE WAS RIGHT!

 

I (what a PAIN!) reinstalled my entire P3D in F:\P3D\ ...and not only did GSX install without a fuss...but now...each and every time I fire up P3D...there has been no further CTD's at the 99 percent load factor (not all the time..but more than less....)

 

So...like myself, if any of you have installed P3D on the root of ANY of your drives....uninstall...and reinstall within a folder. I only have the one folder, and will keep it that way. 

 

I just thought to put this out there...and I had no idea that not having software (I had never done this to date....) in a folder to separate it one layer from the root of the drive could spell install/uninstall and run trouble of the software in question.

 

Cheers!

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

Dont get you so well. The P3D v2 installer do it with folders by itself. What did you do?

Spirit

Share this post


Link to post

Yeah I an not understanding. My installation is on E/P3DFull/P3D. Is this ok?

Share this post


Link to post

Dont get you so well. The P3D v2 installer do it with folders by itself. What did you do?

Spirit

I manually sent it to the root, thinking it was going to be 'better'....than within one layer down, in a folder.  What a dutz.  Of course, I shall never do that again...!

Share this post


Link to post

Hi Mitch,

well, now you know it. :o

Spirit


Yeah I an not understanding. My installation is on E/P3DFull/P3D. Is this ok?

That's pretty well.

Spirit

Share this post


Link to post

Yeah I an not understanding. My installation is on E/P3DFull/P3D. Is this ok?

Yes...for your installation is in a folder...

 

Mine was (all the files that the P3D installer routine placed..were on the F: drive and not as such F:P3d\

 

I had no folders ...all the files were naked...and that caused me all sorts of problems, as was so correctly pointed out to me in a thread here, yesterday...the 'can't install GSX thread'.

Share this post


Link to post

P3Dv2 is fine in any location. I have FSX, XP10 and P3Dv2 on C: with Windows 8 and they all run SUPER. I also never had any problems with FSDT Products

Share this post


Link to post

I really don't grasp why people don't let the software install in the path it defaults to (just choose a desired drive, leave the rest of the path alone). If it's for addons... anything that doesn't function within that path shouldn't be used.

Share this post


Link to post

P3Dv2 is fine in any location. I have FSX, XP10 and P3Dv2 on C: with Windows 8 and they all run SUPER. I also never had any problems with FSDT Products

They can be in any location...but need to be inside a folder. My F: drive had no folder...and I wanted to install right to the root. That was not a good idea, as I found out...and have since corrected...

 

The point of my head's-up thread was to document what problems I had in doing so...and for others to avoid it all-together...  Put all sim files into its own folder..and you are good to go.  I only ever did this once...with P3D's initial install,..and now know better.... :)

Share this post


Link to post

In shorter sentences, do not attempt to install to this drive:path...

X:\

Do install to something like this...

X:\P3Dv2

Share this post


Link to post

I have had no issues with installing in root drive at all..my addons work well

Share this post


Link to post

I have had no issues with installing in root drive at all..my addons work well

Try installing GSX Ground Services from the latest installer. It won't.....

 

If P3D is in a folder....no problem. Ten seconds...and you have GSX.....(of course you have to have purchased the rights to it...)

Share this post


Link to post

It's a commonly known bad idea to install Flightsim-anything in its default location C:\Program Files (x86)\Microsoft Games\..  The permissions for this old game is from the Window 2000/XP generation and they were never designed to cooperate with UAC (Vista and later) - admin or not.

 

Your best/fastest location for reading the 100's of thousands of files is to install it just off the root of a dedicated (NON PARTITIONED) HDD, such E:\FSX or E:\P3Dv2, etc...  When finished installing all add-ons and tweaks, then defrag the dedicated HDD, sorting by filename with a quality 3rd party defrag-tool.

 

You should never install any program directly to the root of any drive (as the OP discovered).

Share this post


Link to post

It's a commonly known bad idea to install Flightsim-anything in its default location C:\Program Files (x86)\Microsoft Games\..  The permissions for this old game is from the Window 2000/XP generation and they were never designed to cooperate with UAC (Vista and later) - admin or not.

 

Your best/fastest location for reading the 100's of thousands of files is to install it just off the root of a dedicated (NON PARTITIONED) HDD, such E:\FSX or E:\P3Dv2, etc...  When finished installing all add-ons and tweaks, then defrag the dedicated HDD, sorting by filename with a quality 3rd party defrag-tool.

 

You should never install any program directly to the root of any drive (as the OP discovered).

I have FSX installed in the default path. I have Prepar3D installed in the default path.

 

Both reside on an SSD drive.. the rest of your statement does not apply.

 

I have zero problems.

 

I can also assure you that the 'permissions' are not an issue as the individual application can't control it's permissions. The OS is the permission problem and there are guidelines on how to avoid problems when writing software for the OS. When developers refuse to abide by them, things go wrong. Simple as that.

 

As everything I use in the sim abides by the security requirements of the OS... I have zero problems.

Share this post


Link to post

 

In shorter sentences, do not attempt to install to this drive:path...

X:\

Do install to something like this...

X:\P3Dv2

That's right...that pretty well sums up the intent of the thread.   It must be an O.S. 'thing'.

Share this post


Link to post

I have FSX installed in the default path. I have Prepar3D installed in the default path.

 

Both reside on an SSD drive.. the rest of your statement does not apply.

 

I have zero problems.

 

...

I complete agree. Besides, today generally people don't install their flight sim to the OS drive, so it doesn't really matter. Even if one does install to c:/program files (x86)/... it rarely causes any problems. This is another issue from 8 years ago.

Share this post


Link to post

So this is a Virtuali issue?

 

I've installed P3D to V:\  without issues.

 

Cheers, Rob.

Share this post


Link to post

So this is a Virtuali issue?

 

I've installed P3D to V:\  without issues.

 

Cheers, Rob.

Rob...with all the files of P3D and its other FOLDER files within those out upon the actual root level of the drive.......I had CTD's quite a bit at the 99.9 percent flight loading, before the shaders took over.  I also could NOT successfully install GSX from the full installer.  I took Virtuali's advice to put it all in a P3D Root folder...and I no longer have ANY CTD episodes..as well as the installer worked perfectly.  The installer would find my F:\ but would crap out as soon as it tried to put files to the drive.  With F:\P3D in play...not one problem. I run with W7 Ultimate 64 bit.

 

Mitch

Share this post


Link to post

I've installed P3D to V:\  without issues.

Rob, did P3D then not create its own folder?

Share this post


Link to post

 

 


Rob, did P3D then not create its own folder?

 

I can re-test a clean full install if you like to double check, but no folder was created when I did this a few months back.  It make take a while for me to get around to re-testing this as I've got several other beta products for P3D 2.x I'm testing on right now.

 

As far as Virtuali ... and this root drive scenario, it'll be a while before I can get to testing that ... now that KIAH is out and KDEN I might "try" Virtuali again -- hopefully FSDT and FB new work isn't using any ASM related stuff.

 

Cheers, Rob.

Share this post


Link to post

It's not really that important to me Rob. I just have a high aversion to installing anything to any drive's root level, largely stemming from the bitter experiences of having to fix customer's computers back in the ancient days of DOS...

 

Many of these folks literally had no directory (now called folder) structure at all, but had everything dumped into C:\ including all of their documents. It would sometimes take days to sort out and fix the mess, and was always an expensive and painful lesson for the customer. :Money Eyes:

Share this post


Link to post

 

 


I just have a high aversion to installing anything to the any drive's root level, largely stemming from the bitter experiences of having to fix customer's computers back in the ancient days of DOS...

 

Agree, I don't typically do this either, I think I was just testing out something when I did do this - temp install.  I normally run at least 1 dir down on a separate physical drive.  I do try to avoid making my dirs too verbose as I have on occasion ran into path length issues.

Share this post


Link to post

We always called it "Shot gun blasting" the drive. :)

Share this post


Link to post

I do try to avoid making my dirs too verbose as I have on occasion ran into path length issues.

That is precisely the reason why I recommend that folks not install any of the FSX/P3D SDKs to their "suggested default paths..."

 

...as it is entirely possible that the complete paths may well be too long when trying to invoke some of the DOS type command line utility programs with all of the switches and parameters required! :Black Eye:

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this