"Michael Solomon" <user@#notme.com> wrote ...
> various other tweaks to get it done but the impression I got from your
> original response was that you were essentially telling the OP to forget
> it when, in fact, he had options open to him before giving up.
Fair comment ... I suppose I did sound prematurely pessimistic, in my first
response!
It looks like the remap function *is* supported in the P5B-V's BIOS, and was
fixed to work correctly in BIOS version 1005, released last month:
From
http://support.asus.com/download/dow...us&model=P5B-V
<quote>
Version 1005 2007/06/07 update
Description P5B-V BIOS 1005
"Support new CPUs. Please refer to our website at:
http://support.asus.com.tw/cpusupport/cpusupport.aspx
Fixed plug 4GB memory with remap function enabled will cause fail to install
Windows Vista 64 bit"
File Size 789.51 (KBytes)
</quote>
Just an extra wrinkle in the pudding - OP Mike noticed the memory problem,
while he was running Photoshop CS3. I haven't upgraded CS2 yet, but I think
CS3 is still a purely 32-bit set of applications. If so, Photoshop is
running as a 32-bit process in the WoW64 layer; not as a native 64-bit
process. Hence, it is by no means automatic that Photoshop will take
advantage of the 64 bit memory address range, even if it is running 64 bit
Windows.
The WoW64 layer can make a full 4GB of virtual address space available to 32
bit applications (which is good!). But this only happens if the application
is linked with the IMAGE_FILE_LARGE_ADDRESS_AWARE flag in the EXE header.
Until lately, very few 32 bit apps had this (SQL Server the only one I
know). Possibly the new Photoshop CS3 has this. An "ordianry" 32 bit
application still only sees 2Gb of user mode memory space, even when running
on the WoW64 on 64 bit Windows.
Of course, it would be nice for Windows itself to exploit the full 4GB of
physical memory. But it may not benefit Photoshop much as an individual
application, if Photoshop can still only use the 2GB of user mode, 32-bit
memory.
Anyway I haven't really thought through all the implications yet, for OP
Mike's problem. I just thought I'd through this into the mix. Still thinking
....
Cheers,
--
Andrew McLaren
amclar (at) optusnet dot com dot au