Re: 64 Bit operating system trends

Bob wrote:

Has anyone seen any info on how many x64 vs x86 versions of Windows
are in use currently? Or any trends on how the x64 versions are
rolling out? I can imagine that someday all machines will be running
an x64 opsys, but was curious if anyone had any guesses when x64 would
outnumber x86.

I think most any (guess >80%) new PC hardware is 64 bit CPUs. However
most of them will be used with 32 bit OS.

The situation somewhat reminds of the late 1980'es. Lots of 386 CPUs
sold, but they were just used for running faster DOS computers. First
by the next 486 generation (1989) bagan any real market change in using
features of the 386 CPU.

Doei RIF
.

Relevant Pages

  • Re: 32bit applications in TS on 2003x64
    ... Intel 64/AMD 64: implemented in nearly all current Intel and AMD CPUs ... Your HP server with its Xeon CPU has built-in support for Intel 64. ... That means you can install Windows Server 2003 x64 edition on the ...
    (microsoft.public.windows.terminal_services)
  • Re: [patch] Real-Time Preemption, -RT-2.6.11-rc3-V0.7.38-01
    ... plus it fixes an x64 SMP build error as well. ... * this function sends a 'reschedule' IPI to all other CPUs. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: WinXPx64 question
    ... target x86, x64 or both cpus. ... The default mode is to target both cpus. ... this setting, the same assembly can run either on x86 or x64, and the JIT ...
    (microsoft.public.dotnet.framework)
  • Re: 32bit applications in TS on 2003x64
    ... Would there be any benefits rebuilding/replacing server with x64? ... IA64: implemented in the Itanium CPUs, ... implemented in nearly all current Intel and AMD CPUs ... Your HP server with its Xeon CPU has built-in support for Intel 64. ...
    (microsoft.public.windows.terminal_services)
  • Re: 64 Bit operating system trends
    ... Or any trends on how the x64 versions are rolling ... I can imagine that someday all machines will be running an x64 ...
    (borland.public.delphi.non-technical)