Thanks for the advice, Vanguard.
To answer your question, the #1 reason I want to switch to XP64 is so I can
use more than 4gig RAM. I do some things that are RAM intensive such as (but
not limited to):
(a) Manipulating large 3D scenes with many objects;
(b) Photoshopping large 300dpi image files; and
(c) Editing large videos


--
Scotter
Tyan Thunder K8WE
Dual Opteron 252s (2.6ghz)
4 gig Corsair XMS DDR400 RAM
XFX 7800 GTX 256 w/VGAsilencerV3
500 gig Hitachi SATA 300
160 gig Seagate SATA 150
Dual Dell 24" wide aspect LCDs
550W Antec power supply
X-Fi Platinum Soundblaster
-
"Vanguard" wrote in message
...
"Scotter" wrote in message
...
You may want to look again at the subject line.
I'll make it more clear:
*Right now* I'm running XP32.
*Soon* I'll run XP64 with the 64-bit version of Outlook Express... UNLESS
you are telling me the XP64 Outlook Express is 32-bit?


You should ask over in the microsoft.public.windows.64bit.general group as
to whether or not Outlook Express got recompiled into a 64-bit
application. However, that doesn't prevent a 32-bit application running
as a proxy, like SpamPal, from working with other e-mail programs since
obviously OE is just sending packets to whatever server to which it
connects and hasn't a concept if that server is running as a 32-bit app or
even what platform it runs on (the mail server to which you connect is
probably not running Windows).

If you use some wrapper or some app that somehow "integrates" with OE, and
if OE is 64-bit, then, yes, you will probably run into problems in trying
to use a 32-bit wrapper spam filter with OE since, as I've heard, 64-bit
apps cannot make calls to 32-bit DLLs. But since SpamPal runs as a proxy,
the only thing passing between SpamPal and OE are the packets, the same
packets (with some headers added to the data for the spam tagging) that
you would also be getting from the mail server (i.e., you are
communicating via TCP rather than some API).

Under 32-bit versions of Windows, WoW (Windows on Windows) is used to
translate system API calls from 16-bit applications to the 32-bit API.
Under 64-bit versions of Windows, WoW64 is used to translate calls from
32-bit apps to the 64-bit API (yeah, I know, WoW went from low-to-high for
bit width while WoW64 goes high-to-low ... go figure Microsoft to make it
backwards). There is no way Microsoft could afford to drop all its
current customers and require all apps to be 64-bit, especially for an
interim version of Windows. While drivers run in the privileged kernel
layer (so you'll need to make sure there are 64-bit drivers for all your
hardware - have fun with that), that is NOT a requirement for
applications.

So what critical applications do you use that have 64-bit versions that
would perform significantly better or faster under Windows 64-bit than do
their 32-bit cousins under the older 32-bit Windows (and without any
changes in hardware)? Most likely all your critical apps are still just
32-bit, and they will run slower under the compatibility mode (WoW64). You
may end up disappointed with the move to Windows 64 if you don't really
have the need for that OS and the availability of 64-bit apps to take
advantage of the 64-bit OS and 64-bit hardware.