Page Three

 
 
By Jason Brooks  |  Posted 2005-05-16 Email Print this article Print
 
 
 
 
 
 
 


Microsofts x64 editions of Windows XP Professional and Windows Server 2003 enable organizations to get the most out of their AMD64- and EM64T-based hardware. However, while processors based on these architectures natively run most existing 32-bit applications without a hitch, sites contemplating the upgrade need to watch out for these potential 32/64-bit trouble spots:

  • 32-bit hardware drivers and kernel-mode applications must be ported to run on Windows x64. AMD has assembled a list of compatible drivers and applications at www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_ 2252_869_875%5e10454,00.html?redir=IEGFC07.

  • Windows x64 wont run 16-bit code. Microsoft provides some workaround information for this issue at support.microsoft.com/?kbid=896458&SD=tech.

  • Windows x64 editions drop support for a number of legacy protocols and subsystems, including MS-DOS, OS/2 and POSIX subsystems and the IPX/SPX, AppleTalk, Services for Macintosh, DLC LAN, NetBEUI, IrDA and OSPF protocols.

    Source: eWEEK Reporting

    Senior Analyst Jason Brooks can be reached at jason_brooks@ziffdavis.com.

    Check out eWEEK.coms for Microsoft and Windows news, views and analysis.



    •  
     
     
     
    As Editor in Chief of eWEEK Labs, Jason Brooks manages the Labs team and is responsible for eWEEK's print edition. Brooks joined eWEEK in 1999, and has covered wireless networking, office productivity suites, mobile devices, Windows, virtualization, and desktops and notebooks. JasonÔÇÖs coverage is currently focused on Linux and Unix operating systems, open-source software and licensing, cloud computing and Software as a Service. Follow Jason on Twitter at jasonbrooks, or reach him by email at jbrooks@eweek.com.
     
     
     
     
     
    Manage your Newsletters: Login   Register My Newsletters























     
     
     
     
     
     
     
     
     
     
     
     
    Rocket Fuel