Tech?Update!: "Driver Issue" in 64-Bit Systems

The early 64-bit versions of operating systems like Microsoft Windows were designed for server systems because servers are required to deliver high performance and need to address a lot of storage space for this. Client systems (PCs, notebooks), on the other hand, were able to perform fully with 32-bit versions for a long time. But developments in the IT world accelerate at a rapid pace. Nowadays a great number of client systems are run with 64-bit operating systems, benefitting from more available storage space, e.g. for bandwidth-hungry applications like gaming etc. As a result 64-bit versions are about to become a standard – a trend which is driven by the spreading out of Windows 7 and its 64-bit versions.

Development of Drivers for 64 Bit Systems
However, there are some stumbling blocks ahead on the way to a 64-bit future. One of them are the device drivers, often simply called "drivers". These components are close to an operating system's core so that in case of failure, virus infections etc. drivers can bring the whole operating system down. In order to ensure perfect alignment with the respective devices, they are usually developed and distributed by the device vendors themselves. So printer vendors, for example, provide for the availability of drivers for their product range, developing drivers for various operating systems and their versions matching different models of their product lines.  

Code Signed Drivers for System Stability
To ensure that these drivers really run with an operating system and not cause failure, Microsoft has set up a code signing program for the development of device drivers. Microsoft operating systems allow only code signed drivers to access the system.  

As the trend of client systems on 64-bit versions is developing into a standard, device vendors are faced with the challenge to develop and code sign device drivers for the 64-bit versions of new operating systems such as Windows 7 and Apple's Snow Leopard. Before buying and installing 64-bit systems they might want to check whether suitable drivers for their peripherals are available. Otherwise they very likely will encounter problems using their peripheral devices.

SEH UTN-Manager for All Windows Versions From XP Upwards
The SEH UTN-Manager virtualizes USB drivers based on Windows XP, Vista, or Windows 7 for the relevant devices. For the latest version of our UTN-Manager, we provide code signed versions for both the 32- and 64-bit versions of Windows 7. You can utilize the updated UTN-Manager 1.2.x, including its full functional range, in both Windows 7 versions

For more detailled information, please refer to the Internet:

About 32- and 64-bit versions:

• Infopackets: "32-bit Vs. 64-bit Systems: What's The Difference?" 
• Microsoft: "32-bit and 64-bit Windows: Frequently Asked Questions" 
• Self Seo: "Difference Between 32 bit and 64 bit OS"

About Code Signing:

• Microsoft: "About Code Signing: Introduction to Code Signing"
• Microsoft: "Driver Signing Requirements for Windows"
• Microsoft: "Requirements for Device Driver Signing and Staging" 
• Microsoft: "Digital Signatures for Kernel Modules on Systems Running Windows Vista"