Re: RAM Upgrade

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


Bundy115;939887 Wrote:
Hello,

I have done several searches for this question with no luck so I
apologize
now if it is a repeat.

I am running Windows Vista x64 SP1. When I installed the OS my computer
had
4GB RAM installed. I have just upgraded to 8GB and enabled the "memory
remap" feature in the system BIOS.

When I view system settings indeed the system reports 8.00 GB memory.
My
questions are as follows;

1. I have read in a number of places on the web that even running vista
x64
if RAM is upgraded from 4.00 GB or less to over 4.00 GB then the OS
must be
re-installed. Is this a correct statement? I really do not want to have
to
pave my system and re-install everything!

2. Will a 32bit application installed on vista x64 be able to take
advantage of this extra memory? I am running Adobe After Effects CS4 (a
32
bit app). When it starts it reports that it is using 4.00 GB RAM (only
reported 3.1 GB with 4GB RAM installed) but under memory preferences it
shows
8GB available. Why is this?

Thanks very much in advance.

--
Bundy115

1)The problems seen with the 64bit editions of Vista is when errors
come up while having more then 2 or 3gb of memory installed. To correct
that you remove all but 2gb until after Windows is on and running.

Simply adding more memory doesn't require any full reinstall of Windows
as long as the edition supports the amount. For instance the Ultimate
64bit edition supports a higher amount then the Home Basic or Home
Premium editions.

2)With 4gb installed the Windows taskmanager will report some 3.5gb
total since roughly 515mb is automatically mapped out to hardwares. You
could have 100gb on and still only see the 3.5gb or so utilized due to
the limitations on the 32bit kernel itself. No it wouldn't see any
advantage.


--
Night Hawk
.

Relevant Pages

  • Re: Event Viewer - "unexpected shutdowns"
    ... be advised I ran the 'repair' options within the last two weeks a few times by booting from the Vista CD. ... The memory diagnostic tool ran cleanly - as reported during the test and after the reboot - nothing to report. ... The attempted chkdsk from the command prompt reported that I did not have the privilege & advised I had to run in 'elevated mode' - I had never heard or read such a term & have been a PC enthusiast since Windows 3.0 from 1990. ... PS - I should add that upon rebooting after an unexpected shutdown - Vista asks if Safe Mode is desired during rebooting. ...
    (microsoft.public.windows.vista.general)
  • Re: Event Viewer - "unexpected shutdowns"
    ... be advised I ran the 'repair' options within the last two weeks a few times by booting from the Vista CD. ... The memory diagnostic tool ran cleanly - as reported during the test and after the reboot - nothing to report. ... The attempted chkdsk from the command prompt reported that I did not have the privilege & advised I had to run in 'elevated mode' - I had never heard or read such a term & have been a PC enthusiast since Windows 3.0 from 1990. ... PS - I should add that upon rebooting after an unexpected shutdown - Vista asks if Safe Mode is desired during rebooting. ...
    (microsoft.public.windows.vista.general)
  • Re: Acronis Plop-in Clone Success with Vista 64
    ... Vista seemed completely ... If my memory is correct, this number is low, in the single digits. ... inability to boot into Windows, ... Windows Backup and Restore for backup. ...
    (rec.outdoors.rv-travel)
  • Re: Does Vista Home Premimum Play Nice With 4GB Memory?
    ... 32-bit Vista does not know how to manage 4 GB memory, which is odd, since ... It's not just Vista, it's *all* 32-bit client versions of Windows. ...
    (microsoft.public.windows.vista.general)
  • Re: Disk partitioning size
    ... Where are the tests and reports from all the others? ... and are the only one to know of such a major flaw with Windows XP ... criticized as Vista, 48-bit LBA was old news and mainstream when Vista ... their drives to fill up before the problem shows up just doesn't hold up ...
    (microsoft.public.windowsxp.general)