IMG File Large Adress Aware & FSPX

[wolfc]

I have the IMAGE_FILE_LARGE_ADDRESS_AWARE bit set on fsx.exe to get that little bit of extra memory into FS.
But this results in a crash when
used in conjunction with fspassengers.
My guess is that fspassengers is not large address aware.

[JeffMcBride]

wolf,

Could you please supply your systems hardware and software specs?

Thanks,

JeffMc

[wolfc]

Vista Business 64-bit
FSX SP2
NVidia GeForce 180.48

Intel Duo E8400 @ 3.0 Ghz
4GB mem
2 x NVidia GeForce 8800 GTX

[Jbl]

Arg 64 bits ...

Dan ? Did you put the flag (IMAGE_FILE_LARGE_ADDRESS_AWARE) in your 32 bits program ?

"To enable an application to use the larger address space, set the IMAGE_FILE_LARGE_ADDRESS_AWARE flag in the image header. The linker included with
Microsoft Visual C++ supports the /LARGEADDRESSAWARE switch to set this flag. Setting this flag and then running the application on a system that does
not have 4GT support should not affect the application."

Wolf may be you can take off 1 go of RAM and retry a start ? Just have 3 go of RAM and the game should work ....



Post Edited ( 12-23-08 22:50 )

[wolfc]

Don't get me wrong. I explicitly changed the fsx.exe image to have the IMAGE_FILE_LARGE_ADDRESS_AWARE bit enabled. FSX itself and
LVLD-763 don't give any trouble, but FSPX does.

Using the original executable doesn't give any trouble. I had no problem doing a flight from San Fransisco to Las Vegas, except that I choose the
wrong field to land and had to put down hard.
(I've yet to try the LVLD-763 though.)

So I bought FSPX to get me to familiar airports again.

But sooner or later I'll probably hit an out of memory issue again... so hopefully this can be fixed. I'm not a windows programmer, but it should
mostly be a matter of using unsigned address pointers instead of signed.

[DanSteph]

I'll check this for patch...

Best

Dan