Disadvantages to moving to a 64 bit processor

[ddemott]

Are there any disadvantages to moving from a 32 bit processor to a 64 bit processor? It seems that if all 32 bit software runs on a 64 bit processor, there really isn't any reason why you shouldn't go 64. Your thoughts??

[SRTDodge05]

There isnt any disadvantages to moving to a 64bit cpu. Today i dont think you can even buy a amd or intel cpu that isnt 64bit.

[k0NG0]

The CPU is a non-issue. Always has been with x86. There are only benefits, since all new CPUs that don't suck are 64-bit enabled.

The OS is a different story.

[SRTDodge05]

64bit os is where you can run into problems with hardware drivers and software.

[jaketerminate]

There are none, anyways you shouldve already moved to 64bit if you have bought a computer recently.

[ddemott]

I see. So if you confirm that all your hardware as 64 bit drivers, then you should be safe.

Originally Posted by SRTDodge05

64bit os is where you can run into problems with hardware drivers and software.

[SRTDodge05]

Originally Posted by ddemott

I see. So if you confirm that all your hardware as 64 bit drivers, then you should be safe.

In the most part yes you'll be fine in the 64bit os. If you were to move to a 64bit os i would go with vista 64bit.

[Rick_EE]

Right now, is there an advantage for a 64 bit OS?

[SRTDodge05]

Originally Posted by Rick_EE

Right now, is there an advantage for a 64 bit OS?

Only if you want to run more then 4gb of memory and both your cpu and os to be on the 64bit stage. That would be the only reason why i would upgrade. If the software you install is 64bit it mite run at litte faster then the 32bit would. If 64bit really had some big advantages over 32bit lot more people would be using it.

[3 of 7]

There are some security differences with Vista 64 compared to X86... I discovered this when trying to install sandboxie.
This is from their site

Sandboxie cannot be installed on Windows Vista, x64 Editions for the following two reasons.
Driver Signing

With Windows Vista x64, Microsoft has introduced mandatory code signing for drivers. Since Sandboxie relies on a driver component to ensure software isolation, it cannot be loaded into Windows Vista x64 without compromising the integrity of the system.

Acquiring the code signature is not in itself an insurmountable task. However, the next reason will show why this is pointless at this time.
Kernel Patch Protection (PatchGuard)

In 64-bit editions of the Windows platform, Microsoft has extended the core of the operating system, the kernel, in such a way that it routinely performs self-checks to detect any tampering. This miracle of an extension is affectionately nicknamed PatchGuard.

The software isolation provided by Sandboxie is not something that the stock Windows kernel supports, and in order to implement this, Sandboxie must make some changes to the kernel. This is detected by PatchGuard as tampering, and so the system crashes soon after Sandboxie is installed.

Note that the PatchGuard used in initial (* see below) versions of Windows x64, specifically Windows XP 64-bit Edition, is less aggressive than the PatchGuard used in Windows Vista x64. For this reason, Sandboxie can and does work in earlier editions of Windows x64.
* Update
On August 14, 2007, Microsoft has issued Windows Update KB932596 to Windows XP 64-bit which brings the Windows XP PatchGuard up to par with the Windows Vista PatchGuard. Effectively this Windows Update will cause an incompatibility between Sandboxie and Windows XP 64-bit, which will manifest as the occasional system crash. To use Sandboxie on Windows XP 64-bit, you must first remove Windows Update KB932596.

Sandboxie - Windows Vista 64