Hello Everyone,

 

First post, so hope I get the etiquette correct.

 

I bought and installed FSX on a large mechanical hard drive. I did it that way because I knew it would require a fair amount of space. The drive is part of a RAID array.

 

The sim operates as it should, and I've not made any tweaks or changes - more or less virgin state.

 

When I restart a flight or, say, change the time of day from day to dusk or night, it takes a long time to reload the scenery - maybe 20-30 seconds. To help this I plan on buying an SSD and moving FSX to the SSD. It's not the only one in my system, I have a 120g SSD system drive and about 500g RAID for data.

 

Is it possible to copy the files over to the SSD and reset some pointers (directory locations etc.) to point to the new location? Or should I uninstall and re-install on the new drive? If it involves editing the registry I'm OK with that.

 

Thanks for any suggestions

 

Henry

 

My system:

Quad core, 8g ram, older Radeon video card, Windows 7 64bit.

120G SSD, 500G RAID

22" and 23" monitors

FSX w/ service pack 1

Running minimum startup programs, and careful about unneeded processes

 

P.S. I am planning on Processor/MOBO/video card upgrade in near future.

What about Ben Cap's tutorial on moving FSX to an SSD? Looks like a neat solution.

 

See here.

 

http://forum.avsim.net/tutorials/article/8-moving-fsx-over-to-an-ssd/

 

Baz

Word Not Allowed is correct. If it is on a separate drive (not c:) you can just copy the FSX directory to the new drive and it will work as long as the drive letter remains the same.

This is what I did, works perfectly.

 

1. Original setup was fsx on drive 1, C:\fsx

2. Renamed C:\fsx to C:\fsxold

3. Created new C:\fsx (empty folder)

4. Installed new ssd drive 2 hardware, formatted volume ntfs

5. In "change drive letters and paths" for this new volume set a path C:\fsx

6. Moved contents of C:\fsxold to C:\fsx (which now is physically on the new ssd)

 

This is what was recommended in the comment to the Ben Cap tutorial.

 

scott s.

.

Thanks for the info everyone.

 

Henry

All - I have a follow on question to the OPs question, however my suituation is the other way around.

 

I've got FSX on my C: - which is an SSD - which is also where windows resides.

 

I like the fact that everything loads rather quickly, however am rapidly running out of space. Is there any way that I can move some parts of the FSX installation over to the D drive but still keep most items on the C? If so, what would you suggest to move and how do you go about it?

 

Thanks,

When I restart a flight or, say, change the time of day from day to dusk or night, it takes a long time to reload the scenery - maybe 20-30 seconds. To help this I plan on buying an SSD and moving FSX to the SSD. It's not the only one in my system, I have a 120g SSD system drive and about 500g RAID for data.

 

Thats actually pretty good load time. I have 2 SSD's in RAID0 totalling 1TB, and load time is 16 seconds minimum, so your "Cost-per-second" will be VERY high to shave off a few seconds load time.

How about unticking the scenery your not going to be using that day and/or de-selecting the "Empty cache on exit"?

All - I have a follow on question to the OPs question, however my suituation is the other way around.

 

I've got FSX on my C: - which is an SSD - which is also where windows resides.

 

I like the fact that everything loads rather quickly, however am rapidly running out of space. Is there any way that I can move some parts of the FSX installation over to the D drive but still keep most items on the C? If so, what would you suggest to move and how do you go about it?

 

You can move any scenery, by updating the paths listed in scenery.cfg, or any simobject categories, by updating the paths in fsx.cfg. I suppose move scenery you don't use that often.

 

Alternatively you can do the same thing by moving all files out of any folder, and create a new folder on the second drive and move all the files there, then create a symbolic link / junction link back to the original location. I use a little utility junction link magic v2 for this. This way no need to edit the cfg files.

 

scott s.

.