Which serves most people’s needs. Also note that x64 is the predominant architecture for home machines, and for those, 32 bit compatibility is being handled by the processor, and your 32 bit apps are running about as well as they would on the 32 bit chip.
A nitpick: the original IBM PC used the Intel 8088. There was no 80286 yet, in 1981.
:smack: You’re right.
I also discovered something I didn’t know before - the term ‘x86-64’ was actually in use by AMD before they came up with ‘AMD64’.
I also wanted to point out that despite this topic digression, the processor doesn’t limit the address space per se; it’s more of a function of the OS. Practically speaking, though, addressing a space larger than the processor word will be prohibitively slow.
One thing Quartz said applies to Macs as well - currently, if you have more than 4GB installed, each app only gets 4GB maximum.
The articles Sunspace linked to cover all of this quite well.
True that 32-bit apps generally will run just fine. I just got a laptop with 64-bit Vista, and have so far found the following things I use will not run:
- Cisco VPN software (this is a HUGE problem for me)
- VMWare (again, not cool, as I’m stuck with using Virtual PC, which sucks for Linux VMs)
- Pharos Uniprint client (pay-for-print software for printers at work)
I think that’s it so far. The Cisco and VMWare things are irritating because it seems like they’re not even making an effort. I have met my VPN needs by installing 32-bit XP into a Virtual PC and VPNing from inside there.
I’m surprised that VMWare does not make a 64-bit version of its software for 64-bit Windows. Makes me wonder what the VMWare Fusion I have on my Mac is.
Edit: VMWare Fusion. Says it will let me run 64-bit XP and 32-bit and 64-bit Vista. I’m currently running 32-bit XP in it.
That’s actually known as thrashing, not trashing. Well, unless you’re running a TRS-80…
I’m surprised too, but it seems to have something to do with the driver signing for the virtual network cards. Since Microsoft essentially makes a competing product (that of course works flawlessly, unless you’re trying to set up a Linux VM), that makes it a little less surprising that they wouldn’t be in a hurry to just sign the stupid drivers already.
By the way, I did find out when I was figuring this stuff out that if you press F8 during startup, you can disable the signed drivers requirement, but only for that sessions. So, I could do that and install VMWare just fine. But then every time I reboot my computer I would have to interrupt the startup and turn off the signed driver requirement if I wanted to run VMWare. There might be a switch that could go in the boot.ini file but I haven’t looked into it that closely.
I’m running VMware Workstation 6 on Vista x64 with no problems at all.
Then maybe it’s just VMware Server. I tried installing VMWare Server, newest version, and it gave me some stuff about unsigned drivers and basically failed the installation. Then, I noticed that any CD I inserted into my drive from then on kept being treated as an empty writable CD. I found information that this is common with these botched VMWare installs, and the workaround is to uninstall and reinstall the CD drive in device manager. I had to do this twice, I think it’s finally back to normal now.
I don’t mind Vista overall, but when something doesn’t work, it seems to fail spectacularly.