These operations might not work in future versions of the Microsoft Windows operating system.įor more information about modifying kernel code and data structures, see the Patching Policy for 圆4-based Systems white paper and the 64-Bit Patching FAQ.įor general information about programming with a 64-bit compiler, see 64-Bit Programming with Visual C++. Modify undocumented kernel data structures.Įven though the preceding operations will not trigger a bug check on x86-based or Itanium-based systems, drivers should not perform any of these operations on any platform. Modify hardware dispatch tables, such as the interrupt dispatch table (IDT) or global descriptor table (GDT). In particular, drivers must not:Īttempt to modify kernel code at run time. Any driver that attempts to modify such code or data will cause the system to bug check (with the CRITICAL_STRUCTURE_CORRUPTION bug check).ĭrivers for 圆4-based systems must avoid operations that might trigger this bug check. Installing drivers yourself To manually install a driver You must be signed in as an administrator to follow these steps. Under Important updates, choose Install updates automatically (recommended).
Tap or click Choose how updates get installed. It is always good to include your PC Specs, make and model in the question. Tap or click Update and recovery, and then tap or click Windows Update. If not, you always have the option to download a bit non-important ones from the manufacturer drivers. The 64-bit version can then call UpdateDriverForPlugAndPlayDevices, specifying a FullInfPath parameter that identifies the location of the 64-bit versions of all files.On 圆4-based systems, kernel code and certain kernel data structures are protected from modification. Usually, Windows update would install all of the necessary ones like Graphics and Chipset. Instead, it must call CreateProcess (described in the Windows SDK documentation) to start the 64-bit version of the application. If the return value is ERROR_IN_WOW64, the 32-bit application is executing on a 64-bit platform and cannot update inbox drivers. The 32-bit version of the application must check the value returned by UpdateDriverForPlugAndPlayDevices. That is, the 32-bit version should be invoked by Autorun (described in the Microsoft Windows SDK documentation), so that it starts automatically when a user inserts your distribution disk. If you are writing a device installation application, the 32-bit version must be the default version.
Provide one or more cross-platform INF files that use decorated INF sections to control platform-specific installation behavior. For more information, see Porting Your Driver to 64-Bit Windows. Provide both 32-bit and 64-bit compilations of all kernel-mode drivers, device installation application, class installers, and co-installers. If your device will be installed on both 32-bit platforms and 64-bit platforms, you must follow these steps when you create a driver package:
0 kommentar(er)
