xp doesn't see my 3gb of ram, hep me


Recommended Posts

here a screenshot

since your available memory is more than 2GB, yet photoshop sees less then i believe you will need to move to 64bit architecture as 2GB mem per app is the limit of x86(32bit) architecture.

since your available memory is more than 2GB, yet photoshop sees less then i believe you will need to move to 64bit architecture as 2GB mem per app is the limit of x86(32bit) architecture.

Actually 3.25Gb is the limit of x86 architecture, however, XP has a limit of 2Gb of memory per process.

I would still recommend moving to x64 architecture simply because that is the way computers are headed, not to mention you'll need it if you plan to upgrade to 4Gb or more memory.

Edited by neo158
Actually 3.25Gb is the limit of x86 architecture, I would still recommend moving to x64 architecture simply because that is the way computers are headed, not to mention you'll need it if you plan to upgrade to 4Gb or more memory.

yes actual limit of 32bit architecture is 2^32=4GB, but the OS sees only upto 3.25GB, but for a single app limit is 2GB (http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx).

Actually 3.25Gb is the limit of x86 architecture, I would still recommend moving to x64 architecture simply because that is the way computers are headed, not to mention you'll need it if you plan to upgrade to 4Gb or more memory.

No, it is not. The virtual address spaces on 32-bit Windows are split half and half (2GB/2GB) between the application and the OS. To go beyond 2GB, the application has to manually map pages of memory in and out of the virtual address space, which means implementing your own memory manager. In 64-bit Windows it's 4GB/0GB for 32-bit apps, and 8TB/8TB for 64-bit apps.

Neither of them are "architectural" limits, they are Windows design limits.

32-bits = 4GB. If you have a 512MB video card, that has to fit in there. The OS can see all 4GB, but there's more than just your RAM that needs to use that address space. :)

hdhood's information about the 2GB partitioning is correct. There is information on how to configure your system to use 4GB tuning and large-address-aware applications here: http://msdn.microsoft.com/en-us/library/bb...28VS.85%29.aspx

It's not for the faint of heart, though.

yes actual limit of 32bit architecture is 2^32=4GB, but the OS sees only upto 3.25GB, but for a single app limit is 2GB (http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx).

thank all of you !

but if i use the swicht /3GB in boot.ini , could have an advantage?

maybe i could dismount 1gb of ram , and keep only 2gb of ram

thank all of you !

but if i use the swicht /3GB in boot.ini , could have an advantage?

You could do that, yes. Assuming Photoshop supports it. The only issue is that it reduces the operating system's part of the address space to just 1GB, which is not that much on modern systems. You can always just try it and see how it goes. Did you look into if Photoshop has any memory mangement settings?

maybe i could dismount 1gb of ram , and keep only 2gb of ram

What would that accomplish other than giving the system 1GB less to work with? It's not like having the extra GB there hurts anything just because PS can't use it (because Adobe is poop).

You could do that, yes. Assuming Photoshop supports it. The only issue is that it reduces the operating system's part of the address space to just 1GB, which is not that much on modern systems. You can always just try it and see how it goes. Did you look into if Photoshop has any memory mangement settings?

thanks

yes photshop can see more then 2gb but it's the only program

What would that accomplish other than giving the system 1GB less to work with? It's not like having the extra GB there hurts anything just because PS can't use it (because Adobe is poop).

because i can't see a benefit ,a gain having 3gb of ram

Well, it could be used by another program running at the same time. The point is that it doesn't hurt and does no damage. Removing it won't do anything useful. It won't improve performance or anything.

exactly, it will be useful for OS.

since if you use 3gb virtual address space for app & 1Gb for OS, then with only 2GB physical memory OS will also share it, it will be a net loss for photoshop.

if even /3gb switch doesn't works, you can try photoshop CS4 that does some memory management. best you move to x64.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!