No, I meant in my case I was going to maintain both FSX & P3D installs on the same PC. If you don't want FSX anymore, go ahead with P3D, you won't need FSX for installing what is intallable in P3D. Just buy Estonia migration tool and you're fine.

 

Cheers,

Dirk.

 

Dirk, can you possibly respond to my 'what if' question?...it might be relevant and I was thinking maybe someone like you who understands how Estonia works you might be able to answer that question.

Dirk, can you possibly respond to my 'what if' question?...it might be relevant and I was thinking maybe someone like you who understands how Estonia works you might be able to answer that question.

 

Noel, what was that again?

 

Otherwise you don't need FSX if you want to fully install (including many FSX payware addons) and fly P3D only.

 

Dirk.

Noel, what was that again?

 

'What if' one were to first install P3D, then use Estonia MT to install all add ons desired into P3D. Once completed, now do a new install of FSX, then install add ons into FSX? What do you think, would that approach possibly avoid the troublesome issues you seem to be referring to when you put both FSX & P3D on one drive?

'What if' one were to first install P3D, then use Estonia MT to install all add ons desired into P3D. Once completed, now do a new install of FSX, then install add ons into FSX? What do you think, would that approach possibly avoid the troublesome issues you seem to be referring to when you put both FSX & P3D on one drive?

 

Sorry, can't help you here, Noel. I had FSX installed then I added P3D. But even if you installed everything like you said, don't you think you would want to add more newer planes and sceneries as they are released? That's when you would have serious inconveniences having both on the same boot.

 

Dirk.

 

There's no performance penalty out of running OS + FSX off the same SSD so long as AHCI is enabled for the SATA controller. With AHCI the drive can run more than one task at a time so there's no need to keep the OS and other programs isolated. Now if for some reason you want to keep them apart, obviously you'll need some extra drives

 

Dazz, is there performance penalty of keeping multi-boots on the same SSD drive? On HDD there was performance difference when booting off the OS that was located 'deeper' inside on the disk. Just a thought. With solid state I could use different dedicated boots off the same SSD (say 240Gb) and have FSX and P3D isolated therefore on another SSD (500Gb).

 

Thanks,

Dirk.

Sorry, can't help you here, Noel. I had FSX installed then I added P3D. But even if you installed everything like you said, don't you think you would want to add more newer planes and sceneries as they are released? That's when you would have serious inconveniences having both on the same boot.

 

Dirk.

 

Ahh, interesting. OK, well if that's the case I will go w/ one or the other as my primary aim is to have OS & Sim on one high perf SSD big enough for plenty of expansion. I'll probably just start w/ FSX and if P3D V2 becomes a true no-brainer then will wipe it clean and start fresh w/ P3D.

 

Thanks for your insights Dirk and have a nice holiday,

 

Noel

 

... and have a nice holiday,

 

Noel

 

You too, Noel.

 

Dirk.

Dazz, is there performance penalty of keeping multi-boots on the same SSD drive? On HDD there was performance difference when booting off the OS that was located 'deeper' inside on the disk. Just a thought. With solid state I could use different dedicated boots off the same SSD (say 240Gb) and have FSX and P3D isolated therefore on another SSD (500Gb).

 

No penalty with SSD's.

So you have three options

 

1.- Both OS in the same SSD

2.- Each OS in it's own SSD, but only one Boot Manager in one of those SSDs, meaning that both OS's will boot off the same SSD and you will get an OS bootup menu to choose from one of them each time you start the system. something like this:

 

 

This means you will always need both SSD's installed for it to work, and the boot drive should be the one where the Boot Manager sits (the drive where you originally installed the first OS).

With both SSD's hooked up, if you install an OS onto SSD #1, Windows will write the Boot Manager in this first SSD. When you later install the OS #2 onto the second SSD, Windows will still use the Boot Manager that's in the first SSD for this second OS install, so you'll need to boot off drive #1 for both OS installs.

 

3.- Each OS in it's own SSD, and each SSD with it's own Boot Manager. To achieve this you'll need to hook up only the SSD you're installing Windows to, both of the times. So you should unplug all drives except the SSD where you want OS #1, then unplug this first SSD, hook up the second and install the sewcond OS. This ensures a new Boot Manager gets installed for the second OS in the second SSD.

Then you either boot off SSD #1 or SSD #2 to choose from OS #1 & OS #2 by selecting the relevant boot drive in your BIOS, or pressing F2 upon startup to pick one drive from the Boot Drive Menu

All is clear, Dazz.

 

Enjoy your holidays.

 

Thanks,

Dirk.

Each OS in it's own SSD, and each SSD with it's own Boot Manager. To achieve this you'll need to hook up only the SSD you're installing Windows to, both of the times. So you should unplug all drives except the SSD where you want OS #1, then unplug this first SSD, hook up the second and install the sewcond OS. This ensures a new Boot Manager gets installed for the second OS in the second SSD.

Then you either boot off SSD #1 or SSD #2 to choose from OS #1 & OS #2 by selecting the relevant boot drive in your BIOS, or pressing F2 upon startup to pick one drive from the Boot Drive Menu

 

I've used a different approach for this issue w/ HDDs. I have XP 32 for Gigastudio and a few games installed on one drive, and have Vista 64 for FSX on another drive. The big difference is they're isolated completely from each other, but for a purpose: I keep XP at stock clock speed, and Vista 64 on my overclocked profile, so I simply make my boot selection from the F8 boot manager rather than the windows boot manager. I have FSX on a 3rd WD Velociraptor drive. I think for my next build I may do the same, keeping XP on a HDD but Vista 64 & FSX on the big SSD. Not seeing a compelling reason to leave VistA for Win7 FSX from replies provided by y'all. Dunno of P3D needs Win7 over Vista 64.

I've used a different approach for this issue w/ HDDs. I have XP 32 for Gigastudio and a few games installed on one drive, and have Vista 64 for FSX on another drive. The big difference is they're isolated completely from each other, but for a purpose: I keep XP at stock clock speed, and Vista 64 on my overclocked profile, so I simply make my boot selection from the F8 boot manager rather than the windows boot manager. I have FSX on a 3rd WD Velociraptor drive. I think for my next build I may do the same, keeping XP on a HDD but Vista 64 & FSX on the big SSD. Not seeing a compelling reason to leave VistA for Win7 FSX from replies provided by y'all. Dunno of P3D needs Win7 over Vista 64.

 

Actually this is exactly what I meant with option #3, except that it was F8 and not F2 to select the boot drive menu without getting into the BIOS. How do you keep XP at stock clocks and Vista overclocked Noel?

How do you keep XP at stock clocks and Vista overclocked Noel?

 

The BIOS on my ASUS mobo has two overclocking profiles which include all parameters in the entire boot configuration, so include which drives to boot from. So I dedicate one to XP (and its dedicated HDD) and set it up at default clock speed for CPU/DRAM and the other I reserve for Vista 64 (and its dedicated HDD) using overclocked GPU/DRAM settings. So with this method you do have to hit Del to get into the BIOS so it's not so elegant in this regard, but it's quite quick as you're just selecting a profile, then hitting F10 to save and continue booting up. If my next build's BIOS allows me this control I will most likely do the same thing however instead of having Vista/FSX on two sep drives as I have now will keep it on the one larger SSD.