4GB or 8GB in Win XP 64?

[Guest nihongo]

Is it possible to upgrade to XP64 edition and boost your memory up to 4GB or 8GB (Max 32GB) so we can do without these 'OOM' errors?Any ideas?I know I get system hangs if I run netscape or other programs whilst flying in FS2004. I suppose that is what my other computer is for.

[Mike T 208]

Hello:If your your system is hanging just because you are running FS9 and netscape together you have problems with your current system. You should post your system and hardware specs and the add-ons you are running in FS9 and programs you have running in the background in XP. There is no way in heck you need XP64 and 4-8GB of RAM. Save your money and reformat your computer.

[jfri 42]

>Is it possible to upgrade to XP64 edition and boost your>memory up to 4GB or 8GB (Max 32GB) so we can do without these>'OOM' errors?>>Any ideas?>I have 1 Gb RAM & Win XP Home 32 bit and I don't experience OOM errors running FS9 + Active Sky + RadarContact 4

[Guest fabrytnix]

before all read here: http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchI have tried that solution but no way with 3 GB of ram: too much disk swapping.Now I've installed Vista x64 and 8 GB ramNot any more OOMs or disk swapping in long haul flight with UT, very complex sceneries (as Aerosoft EDDF or Heathrow UK2000, 9D VHHX), AS+GE, fsgenesis mesh (all world), advanced aircraft (PMDG, PSS, Level-D etc...) and FS 9.1You shouldn't have problems with XP x64 (much, much better 8GB than 4 I think)but remember:you have likewise to hack fs9 to get more than 2 GB of memory (as explained in post linked above)and if you use some devices as sony voice recorder or other usb devices you may have problem with 64 bit drivers

[Guest nihongo]

Mike, Ifi and Fabrizio thanks for your posts. I am running EDDF, Megascenery NC v2 and SC, plus PSS 757 777 and PMDG 737NG. I also got the France FlightParis and Nord Alpes, as well as the Paris airport payware. After I installed too much aircraft and scenery I think either the gauges files were messed up, but at least I think it was too much.A fresh reinstall certainly cleaned things up, but apparently somewhere on my system I have an IRQ conflict, somewhere (I got a blue screen, and have had quite a few (during FS9) system locks unrecoverable, had to restart). I can't find it in 'System'. How can I find it?I am going to keep it simple from now on.DXdiag here.------------------System Information------------------Time of this report: 4/24/2008, 20:32:31 Machine name: DHOME Operating System: Windows XP Home Edition (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.070227-2254) Language: English (Regional Setting: English)System Manufacturer: System manufacturer System Model: System Product Name BIOS: Phoenix - AwardBIOS v6.00PG Processor: Intel® Core2 CPU 6300 @ 1.86GHz (2 CPUs) Memory: 2046MB RAM Page File: 421MB used, 3518MB available Windows Dir: C:WINDOWS DirectX Version: DirectX 9.0c (4.09.0000.0904)DX Setup Parameters: Not found DxDiag Version: 5.03.2600.2180 32bit Unicode------------DxDiag Notes------------ DirectX Files Tab: No problems found. Display Tab 1: No problems found. Sound Tab 1: No problems found. Music Tab: No problems found. Input Tab: No problems found. Network Tab: No problems found.--------------------DirectX Debug Levels--------------------Direct3D: 0/4 (n/a)DirectDraw: 0/4 (retail)DirectInput: 0/5 (n/a)DirectMusic: 0/5 (n/a)DirectPlay: 0/9 (retail)DirectSound: 0/5 (retail)DirectShow: 0/6 (retail)---------------Display Devices--------------- Card name: NVIDIA GeForce 8600 GTS Manufacturer: NVIDIA Chip type: GeForce 8600 GTS DAC type: Integrated RAMDAC Device Key: EnumPCIVEN_10DE&DEV_0400&SUBSYS_82411043&REV_A1 Display Memory: 256.0 MB Current Mode: 1280 x 1024 (32 bit) (60Hz) Monitor: Plug and Play Monitor Monitor Max Res: 1600,1200 Driver Name: nv4_disp.dll Driver Version: 6.14.0011.6921 (English) DDI Version: 9 (or higher)Driver Attributes: Final Retail Driver Date/Size: 12/5/2007 01:41:00, 5773568 bytes WHQL Logo'd: Yes WHQL Date Stamp: n/a VDD: n/a Mini VDD: nv4_mini.sys Mini VDD Date: 12/5/2007 01:41:00, 7435392 bytesDevice Identifier: {D7B71E3E-4740-11CF-FA68-4AA200C2CB35} Vendor ID: 0x10DE Device ID: 0x0400 SubSys ID: 0x82411043 Revision ID: 0x00A1 Revision ID: 0x00A1 Video Accel: ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive {335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalStretch Registry: OK DDraw Status: Enabled D3D Status: Enabled AGP Status: EnabledDDraw Test Result: Not run D3D7 Test Result: Not run D3D8 Test Result: Not run D3D9 Test Result: Not run-------------Sound Devices------------- Description: SoundMAX HD Audio O Default Sound Playback: Yes Default Voice Playback: Yes Hardware ID: HDAUDIOFUNC_01&VEN_11D4&DEV_1986&SUBSYS_1043818F&REV_1005 Manufacturer ID: 65535 Product ID: 65535 Type: WDM Driver Name: ADIHdAud.sys Driver Version: 5.10.0001.4151 (English) Driver Attributes: Final Retail WHQL Logo'd: Yes Date and Size: 10/6/2005 01:21:10, 141312 bytes Other Files: Driver Provider: AnalogDevices HW Accel Level: Full Cap Flags: 0xF5F Min/Max Sample Rate: 100, 192000Static/Strm HW Mix Bufs: 33, 32 Static/Strm HW 3D Bufs: 33, 32 HW Memory: 0 Voice Management: Yes EAX 2.0 Listen/Src: Yes, Yes I3DL2 Listen/Src: Yes, YesSensaura ZoomFX: Yes Registry: OK Sound Test Result: Not run---------------------Sound Capture Devices--------------------- Description: SoundMAX HD Audio I Default Sound Capture: Yes Default Voice Capture: Yes Driver Name: ADIHdAud.sys Driver Version: 5.10.0001.4151 (English) Driver Attributes: Final Retail Date and Size: 10/6/2005 01:21:10, 141312 bytes Cap Flags: 0x41 Format Flags: 0xCCC-----------DirectMusic----------- DLS Path: C:WINDOWSSYSTEM32driversGM.DLS DLS Version: 1.00.0016.0002 Acceleration: n/a Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal Registry: OK Test Result: Not run-------------------DirectInput Devices------------------- Device Name: Mouse Attached: 1 Controller ID: n/aVendor/Product ID: n/a FF Driver: n/a Device Name: Keyboard Attached: 1 Controller ID: n/aVendor/Product ID: n/a FF Driver: n/a Device Name: Top Gun Afterburner Attached: 1 Controller ID: 0x0Vendor/Product ID: 0x044F, 0xB101 FF Driver: n/a Device Name: Microsoft Wireless Optical Mouse