Well, my goal was not to frustrate you more or make you upset with me.

My first post simply pointed out that there may be a difference in reported
memory depending on where you look: e.g. System Property may report 4GB, but
task manager may report less.
I didn't refer to BCEDIT until you replied with: "I suppose I should have
asked "what are the steps required for using PAE to actually remap
addressing to the extended areas?"

To that, I sent you to the instruction manual.
Have a nice day.

"Sarah White" wrote in message
...
I'm amazed that you're bothering to tell me that; my original post (top of
this thread) said that I used BCDEDIT to enable PAE.

As for changing "how memory is reported" I have two conflicting reports.

Report 1) Control Panel\System: 4.0GB (2.75GB before BCDEDIT - PAE)
Report 2) Task manager "performance tab" (Physical Memory) Total 2813MB

If you're saying style-2 (task manager or other) reports won't be changed
by PAE, are you able to cite / reference a specific article? I'm curious
if this is because my signed, WHQL drivers are trying to use the same
address as a large portion of my RAM, or if some entirely unexplained
thing is going on.

As for style 1, I hate to break it to you, but control panel - system
(easily opened using [win] + [break] keys) is reporting a different
(higher) number now that I'm using PAE: it actually says 4.0 GB now!

Thanks, good idea for providing that link explaining BCDEDIT under the new
windows bootloader. I personally found it a bit confusing (was very much
accustom to using boot.ini) Personally, I like the abbreviated info (even
though it isn't official) that I found he

http://www.ocmodshop.com/ocmodshop.aspx?a=989

Note: I'm quite confused about the terms "nx" bit and "hot add" memory and
a few other terms in there. I know there was a reference in my bios menu
for something that might have been the "nx" bit... Some kind of security
feature under the same screenfull of settings that had virtualization,
disable core 1 (only use core 0) and CPU throttling.

Mark H wrote:
The point is:
If you don't have more than 4GB of memory, PAE will not change how
memory is reported.

It is supported, but only through BCEDIT:

Only server OS systems can support more then 4GB of memory with a 32bit OS
since the use memory mapping to provide 4GB of logical memory to different
running process which map to different physical memory addresses.
Vista 32 bit like most if not all personnel computer Boss can not address
more then 4GB since it does not use memory mapping.
"Sarah White" wrote in message
...
I'm amazed that you're bothering to tell me that; my original post (top of
this thread) said that I used BCDEDIT to enable PAE.

As for changing "how memory is reported" I have two conflicting reports.

Report 1) Control Panel\System: 4.0GB (2.75GB before BCDEDIT - PAE)
Report 2) Task manager "performance tab" (Physical Memory) Total 2813MB

If you're saying style-2 (task manager or other) reports won't be changed
by PAE, are you able to cite / reference a specific article? I'm curious
if this is because my signed, WHQL drivers are trying to use the same
address as a large portion of my RAM, or if some entirely unexplained
thing is going on.

As for style 1, I hate to break it to you, but control panel - system
(easily opened using [win] + [break] keys) is reporting a different
(higher) number now that I'm using PAE: it actually says 4.0 GB now!

Thanks, good idea for providing that link explaining BCDEDIT under the new
windows bootloader. I personally found it a bit confusing (was very much
accustom to using boot.ini) Personally, I like the abbreviated info (even
though it isn't official) that I found he

http://www.ocmodshop.com/ocmodshop.aspx?a=989

Note: I'm quite confused about the terms "nx" bit and "hot add" memory and
a few other terms in there. I know there was a reference in my bios menu
for something that might have been the "nx" bit... Some kind of security
feature under the same screenfull of settings that had virtualization,
disable core 1 (only use core 0) and CPU throttling.

Mark H wrote:
The point is:
If you don't have more than 4GB of memory, PAE will not change how
memory is reported.

It is supported, but only through BCEDIT:

Let's try one more time, but I'll just give instructions:

From elevated cmd prompt:
bcdedit /set PAE forceenable
Reboot

The reboot is required before proceeding.
Most likely, not all RAM is being reported.
That's because on 32-bit OS, DEP is required when PAE is running. (Even
if not supported.)
DEP may cause other problems.

From elevated cmd prompt:
bcdedit /set nx AlwaysOff
bcdedit /set PAE forceenable
Reboot

It is proven that PAE and Creative sound cards won't work together.
There may be other configurations that don't work.

To turn off:
From elevated cmd prompt:
bcedit /set nx AlwaysOn
bcedit /set PAE default
Reboot

If it still doesn't work, it's not supported by your machine.



"Sarah White" wrote in message
...
I upgraded (a so-called "clean install" on same partition... it made xp
pro x64 unusable by renaming various system folders) to windows vista
home basic hoping that PAE would work.

I had assumed that 4GB RAM would be no problem (the intel e6600 core2duo
in this system supports 64bit instructions, and as a result PAE works on
linux just fine) though it is not doing what I expected.

After installing Vista SP1 (came out recently) from windows update, I
decided to try using BCDEDIT.EXE and set PAE to "force enable" mode...
Not working as expected!!!

Well, pressing [windows logo key on keyboard] and [break] at the same
time (you can also bring that up by right clicking what XP called "my
computer" and selecting "properties") ... windows now reports: Memory
(RAM) 4.0 GB ... it was too good to be true:

http://support.microsoft.com/kb/283296

--snip--

Article ID : 283296
Last Review : February 28, 2007
Revision : 4.4

""" Windows Server 2003 Enterprise Edition loads a standard VGA video
driver for NVidia... """

APPLIES TO
• Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)

--snip--

Wrong on two counts!!!

A) I'm using nvidia's latest WHQL drivers

Windows is not using "standard VGA video driver" but is using Nvidia's
latest digitally signed vista 32 bit drivers (Version 175.16) Digital
Signer: Microsoft Windows Hardware Compatibility

B) I'm running windows vista (with signed, WHQL drivers) and windows
task manager still reports "physical memory (MB) 2813" on the
performance tab!!!

I upgraded WinXP Pro x64 partition to vista because... let me think...
Sure, 4GB was nice, but practically ZERO driver support for XP Pro x64

As for your comment about "Only server OS systems..."

I suppose it is known that the limit is 4gb on XP (why though?)
-- http://msdn.microsoft.com/en-us/library/ms791485.aspx

The 4GB limit is really just OS developers being lazy (or greedy?)
Truly, PAE / NUMA / 4GB limit is far more reliable on linux (lol)
.... What do I know; I'm just a developer that has vista for gaming.

My opinion, greed -- the 64 bit OS is unnecessary to access 4GB or more
of memory, but then you are EMULATING 32bit mode for gaming and other
apps. My very first thought was to check vista's "help and support" ...

1) go to your start menu and open "help and support" in windows vista.
2) type "PAE" in the search
3) the only result is "Physical address expansion (PAE) (definition)"

They even admit / explain it's "up to 64 GB" but didn't mention they
will deny you access to your ram / hold out and sell you "upgraded"
64bit version of windows to make an extra buck. Just my $0.02

JW wrote:
Only server OS systems can support more then 4GB of memory with a 32bit
OS since the use memory mapping to provide 4GB of logical memory to
different running process which map to different physical memory addresses.
Vista 32 bit like most if not all personnel computer Boss can not
address more then 4GB since it does not use memory mapping.

Has anyone tried this?

Type what's between the " " in a CMD prompt as admin

" *BCDEdit /set PAE forceenable* " enable use of 4GB RAM
" *BCDEdit /deletevalue PAE* " disable ability to see 4GB RAM


--
pacinitaly

pacinitaly wrote:
Has anyone tried this?

Type what's between the " " in a CMD prompt as admin

" *BCDEdit /set PAE forceenable* " enable use of 4GB RAM
" *BCDEdit /deletevalue PAE* " disable ability to see 4GB RAM


Why? What's your point?

Oldfart;1005859 Wrote:
pacinitaly wrote:
Has anyone tried this?

Type what's between the " " in a CMD prompt as admin

" *BCDEdit /set PAE forceenable* " enable use of 4GB RAM
" *BCDEdit /deletevalue PAE* " disable ability to see 4GB RAM


Why? What's your point?

have you read the thread?

answer: so you can see the full 4GB of ram


--
pacinitaly

"pacinitaly" wrote in message
...

Has anyone tried this?

Type what's between the " " in a CMD prompt as admin

" *BCDEdit /set PAE forceenable* " enable use of 4GB RAM
" *BCDEdit /deletevalue PAE* " disable ability to see 4GB RAM


Windows desktop OS's only use PAE to enable DEP. The address windowing
extensions aren't enabled except in Windows server OS's.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
http://www.vistahelp.ca/phpBB2/

Kerry Brown;1006127 Wrote:
"pacinitaly" wrote in message
...

Has anyone tried this?

Type what's between the " " in a CMD prompt as admin

" *BCDEdit /set PAE forceenable* " enable use of 4GB RAM
" *BCDEdit /deletevalue PAE* " disable ability to see 4GB RAM


Windows desktop OS's only use PAE to enable DEP. The address
windowing
extensions aren't enabled except in Windows server OS's.

--
Kerry Brown
MS-MVP - Windows Desktop Experience: Systems Administration
'VistaHelp.ca • Index page' (http://www.vistahelp.ca/phpBB2/)


WOW, good to know, glad I set it back to default


--
pacinitaly