Bass wrote:It's certently a memory issue when running FSX!!
I used to run 6gb 2000mhz, but i found out that was not enough!
I also needed to change fsx direction from D-drive to programs (x86) microsoft games on my C to get my addons running!!
Now, i upgraded memory to 12gb 2000mhz, and i haven't had any problems or issues yet.
Ofcourse it depends on the system, "coorperation" system between, what you got running behind win and drivers.
And Gary, if your files in win8 shows up as "read only", then you're not Adminstrator.
garymbuska wrote:Bass wrote:It's certently a memory issue when running FSX!!
I used to run 6gb 2000mhz, but i found out that was not enough!
I also needed to change fsx direction from D-drive to programs (x86) microsoft games on my C to get my addons running!!
Now, i upgraded memory to 12gb 2000mhz, and i haven't had any problems or issues yet.
Ofcourse it depends on the system, "coorperation" system between, what you got running behind win and drivers.
And Gary, if your files in win8 shows up as "read only", then you're not Adminstrator.
That is not the case I have full administrator rights this is just a goof in Windows 8 64 bit.
There is no reason for a txt file to be read only and even if I did not have administrator rights it would not make a txt file as read only unless I saved it that way.
My system at work has SYSCO installed and I do not have administrator rights and have no issues with TXT files. I can not run any exe files with out IT giving me permission as we like to say big brother is watching.
It is not a big deal but trust me that is what I discovered after installing FSX gold edition I could not figure out why I could not edit the cfg file and discovered the read only box was checked. Now I am going to go out on a limb here and say I doubt that the file is on the disk as a read only file (of course I could be wrong) but it really does not make any sense to do that and the cfg file was the only file that was that way.
It could be where the file is located at which is in a strange place. c:\users\<username>\AppData\Roaming\Microsoft\FSX\fsx.cfg
or something like that.
stephan wrote:I am not sure if you can drag and drop your sim folder to another hard drive. When you install the program,it creates other files that writes addresses of necessary files and when you move the sim folder,you are changing the addresses.Now,I am speaking of how things worked not so long ago. And I say this thru experience.But with the newer Windows,maybe it can be done. I scanned down the list of comments to you and I believe someone wrote that they had moved a program from one drive to another.If I am mistake,and no one said this,then like Fozzer suggested...it would be best to uninstall and reinstall the sim. It may be the best thing to do anyway. It prevents taking the chance of confusing your register and communications between file addresses on the hard drives. Again..I am speaking from the view of how things used to work in the computer world a few years ago.
OldAirmail wrote:Most of FSX is on the SSD.
The FSX related files that have been moved from the SSD and onto the 1TB hard drive are;
Scenery files (18 gig)
Sim Object files (10 gig).
FS Genesis World Terrain (4 gig)
MegaSceneryEarth - Pennsylvania (17.5 gig)
49.5 gig total in FSX files
Due to the extreme slowness of REX Essential Plus Overdrive, I've left all 12.8 gig on the SSD.
Fozzer wrote:..very interesting......!
FS 2004 and FSX programmed to use 32-bit memory addressing?
Which means, similar to old 8-bit (Sinclair Spectrum/Commodore C64, etc), and 16-bit programs (Amiga, etc), that the programs only had a certain number of addresses available to use, up the the maximum available at the time
Programs are written to address memory locations from the first address to the last address in the available memory area at the time.
----------------------------------
8, 32 and 64-bit binary encoding
Bit Value Decimal Equivalent
8-bit 11111111 255
32-bit 11111111111111111111111111111111 4,294,967,295
64-bit 1111111111111111111111111111111111111111111111111111111111111111 18,446,744,073,709,551,615
-----------------------------------
So...I assume that a program written to address the maximum of 32-bit addresses will be unable to USE/SEE more than 4 giga-bytes of system memory?
..any excess memory memory will only be used by other programs (operating system, etc), in memory?
Paul....Sinclair Spectrum 48k Programmer using 8-bit addressing...0000 to FFFF....A bit of a byte!.......!
Hexadecimal Addressing: http://www.microbuilder.eu/Tutorials/Fu ... cimal.aspx
Return to FS 2004 - A Century of Flight
Users browsing this forum: No registered users and 285 guests