Quote:
XP was originally released as a 32-bit OS.
MS did briefly release two 64-bit versions of XP for Intel's Itanium processor, with a 32-bit x86 emulation layer for compatibility with existing software. One version, the 2002 edition, was based on Windows XP's code base. Another version, the 2003 edition, was based on Windows Server 2003, but with XP's default theme and bundled apps. But neither ever gained acceptance in the marketplace. XP for the Itanium was quietly killed off in 2005 when HP, the final distributor of Itanium-based workstations, pulled out.
MS followed up on this with an AMD64 (x86-64) edition of Windows XP in 2005, also based on the Windows Server 2003 code base but with XP's look and features, shortly after the Itanium edition was discontinued. Although MS maintained active sales of this OS right up until the introduction of Windows Vista, it remained on the fringes in the marketplace, with most users choosing to stick with the 32-bit edition for compatibility reasons.
Quote:
If I buy 64bit hw and run a 32bit OS on it, can I take full advantage of 64bit apps?I don't know.
32-bit editions of Windows XP cannot run 64-bit apps.
Quote:
Forcing developers to write for a new os and, at the same time for a 10 year old one will be expensive and time consuming.It will make the transition for MS to a fully 64bit system a lot slower.I bet Ms's strategy is,similar to Apple, to convince private users to adopt the OS and subsequently companies.
But MS itself will have to write the next version or Office for both Xp and Win7..Since they are still officially supporting it..
But MS itself will have to write the next version or Office for both Xp and Win7..Since they are still officially supporting it..
Heck, MS still officially supports Windows 2000 until July 13, 2010, but they have stopped releasing new versions of Office and Internet Explorer for that operating system.
Most developers who care about supporting the 10-year-old operating system, probably don't bother creating two versions of the software - one for the old OS and one for the new one. They probably just write the app to work with the 10-year-old OS, and stick with only those APIs which have remained stable in the intervening time according to MS's documentation.







