Skipping NT 3.x due to complications Join the discord community: https://discord.me/BobPony. The printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 drivers. If you want to use this driver, contact your system administrator about disabling this policy”.

เมื่อคุณพิมพ์ไปยังเครื่องพิมพ์เครือข่าย Windows NT, Windows ๒๐๐๐และ Windows Server ๒๐๐๓ใช้โปรแกรมควบคุมการพิมพ์บนเครื่องพิมพ์ตัดออกเสมอถ้าคุณไม่ได้ใช้การแก้. The driver disk (CD) has the drivers for windows 9X/NT/2000. I installed the driver using the havedisk option. It gets installed alright without any problem. This behavior when trying to install older drivers to Windows 10 is by design. We would recommend that you contact your printer manufacturer for updated drivers for Windows 10. You may be able to find workarounds when you search over the internet but this includes editing group policy settings or editing the registry.

The WinDriver™ 14.5.0 device driver development tool supports any device, regardless of its silicon vendor, and enables you to focus on your driver’s added-value functionality, instead of on the operating system internals. WinDriver’s driver development solution covers USB, PCI and PCI Express

• Easy user-mode driver development.
• Friendly DriverWizard allows hardware diagnostics without writing a single line of code.
• Automatically generates the driver code for the project in C, C#, Visual Basic .NET, Python, Java Delphi (Pascal), or Visual Basic 6.0.
• Supports any USB/PCI device, regardless of manufacturer.
• Enhanced support for specific chipsets frees the developer of the need to study the hardware’s specification.
• Applications are binary compatible across Windows 10/8.1/Server 2016/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP.
• Applications are source code compatible across all supported operating systems — Windows 10/8.1/Server 2016/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP, Embedded Windows 10/8.1/8/7, Windows CE (a.k.a. Windows Embedded Compact) 4.x–7.x (including Windows Mobile), and Linux.
• Can be used with common development environments, including MS Visual Studio, Borland C++ Builder, Borland Delphi, Visual Basic 6.0, MS eMbedded Visual C++, MS Platform Builder C++, GCC, Windows GCC, or any other appropriate compiler/environment.
• No WDK, ETK, DDI or any system-level programming knowledge required.
• Supports multiple CPUs.
• Includes dynamic driver loader.
• Comprehensive documentation and help files.
• Detailed examples in C, C#, Python, Java and VB.NET.
• HLK / HCK / WHQL certifiable driver (Windows).
• Two months of free technical support.
• No run-time fees or royalties.

WinDriver’s Top Features

• Fast: Shorten driver development cycle and time to market.
• Simple: No OS internals or kernel knowledge required.
• Stable: Field-tested on thousands of HW and OS configurations.
• Enhanced Chipset Support: Silicon partners libraries to jump-start your driver development. Special samples for various PCI/USB chip vendors, such as Altera and Xilinx. WinDriver generates a skeletal driver code, customized for the user’s hardware.
• Multiple OS support and cross platform: WinDriver product line supports ?Windows 10/8.1/Server 2016/Server 2012 R2/8/Server 2012/7/Server 2008 R2/Server 2008/Server 2003/XP, Embedded Windows 10/8.1/8/7, Windows CE/Mobile, and Linux. The same driver will run under all supported operating systems without any code modifications. Just recompile!
• Immediate Hardware Access and Debugging: Test your hardware through a graphical user-mode application, without having to write a single line of code. Monitor kernel level activity throughout the driver development process.
• Performance Optimization: Use WinDriver’s Kernel PlugIn technology to develop your driver in the user-mode — then run performance critical sections of it in the Kernel Mode (Ring 0) to achieve optimal performance.
• HLK / HCK/ WHQL Certifiable Driver: WinDriver’s Windows drivers are WHQL ready — you will not need to invest time and efforts on making your driver WHQL compliant. Jungo also can prepare the WHQL submission package for you.
• Field-proven quality: WinDriver’s technology enables you to concentrate on your core business and successfully create first-rate drivers without having to invest redundant resources in driver development from scratch.
• User-mode programming: WinDriver’s architecture enables driver development in the user mode, while maintaining kernel-mode performance.
• 64-bit Support: Allow utilizing the additional bandwidth provided by 64-bit hardware and enable 64-bit data transfer on x86 platforms running 32-bit operating systems. Drivers developed with WinDriver will attain significantly better performance results than drivers written with the DDK or other driver development tools that do not support this feature.
• Complete .NET Framework Support: Easily incorporate WinDriver’s C# or VB.NET code into your existing .NET application using the powerful object oriented managed extensions for C++ library.

WinDriver products are accompanied with highly detailed technical references that are designed to assist you in various stages of the development process. If you have just started evaluating or using WinDriver, you may find our Quick Start Guideshelpful. Should you require more in-depth information, or would like to know more about the technical aspects of WinDriver, please refer to our Online Manual. For other technical resources, such as FAQs and technical documents — see WinDriver’s Support Page.

WinDriver for Servers/Data Centers

With Specific API for Server such as IPC, Buffer sharing, SRIOV and more. To enhance your WinDriver usage for you Server FPGA based devices.

WinDriver in your development product, API or SDK.

If you wish to use WinDriver within a development product, an API, or any part of a development product or environment you need to purchase the WinDriver SDK license.

WinDriver support for Windows 10 IoT Core.

Starting WinDriver 12.5 WinDriver supports Windows 10 IoT Core x86, x64 and ARM.

Partners

WinDriver features a set of ready-made libraries and hardware access functions that provides enhanced support for our PCI/PCI Express and USB hardware Partners.

Read more about our Partners.

Customers

WinDriver has thousands of customers worldwide that have used it to create numerous design wins. From scientific equipment to defense systems, from medical devices to consumer electronics, WinDriver assisted customers in focusing on their core expertise, by providing a straightforward yet reliable driver development solution.

Read our customer success stories

See Also

WinDriver Manuals:

USB HTML | PDF

PCI/PCIe/ISA HTML | PDF

Martin Kellermann | Staff Strategic Application Engineer| Xilinx

Jungo’s professional services unit provides a complete Windows Hardware Certification (aka WHQL) submission service for
WinDriver customers.

This article describes an issue where you can't install a shared network printer locally on a Windows Server or Windows-based computer.

Original product version: Windows 10 – all editions, Windows Server 2012 R2
Original KB number: 888046

Symptoms

If you try to install a shared network printer, you experience symptoms if the following conditions are true:

• You have a shared network printer that is installed on a Microsoft Windows 2000 Advanced Server-based print server.

• You try to install the shared network printer locally on a computer that is part of a Windows domain.

• You try to install the shared network printer locally on a computer that is running one of the following operating systems:

  • Windows XP Service Pack 1 (SP1)
  • Windows Server 2003

In this scenario, you experience the following symptoms if you try to install a shared network printer:

• If you try to install the printer on a Windows XP SP1-based client by using the Add Printer Wizard or by using the printer share name from the PrintServerNamePrinterShareName location, you receive the following error message:

  A policy is in effect on your computer which prevents you from connecting to this print queue. Please contact your system administrator.

• If you use the Add Printer Wizard to try to install the printer on a Windows Server 2003-based client, you receive the following error message when you click Finish to complete the printer installation:

  Unable to Install Printer. The printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 drivers. If you want to use this driver, contact your system administrator about disabling this policy.

Cause

This issue occurs if the printer driver that is installed on the print server is a third-party printer driver. You can't install a shared network printer that has a third-party printer driver locally on a Windows XP SP1-based computer if you're a regular user or a member of the Power Users group. Windows XP SP1 doesn't enable regular users or members of the Power Users group to install third-party drivers. In Windows XP SP1, only the following people have permission to install a third-party driver:

• Local administrator
• Members of the Administrators group
• Members of the Power Users group that have the Load and unload device drivers policy permissions

If the Windows XP SP1-based computer is joined to a Microsoft Windows NT 4.0-based domain, regular users and members of the Power Users group can install third-party printer drivers to the Windows XP SP1-based client computer. You may experience issues in installing a third-party printer driver on a Windows XP SP1-based computer if the Windows XP SP1-based computer is part of a workgroup or part of a Microsoft Windows 2000-based domain.

In Windows Server 2003, you can't install a shared network printer locally if the printer driver that is installed on the print server uses third-party kernel-mode printer drivers. A policy setting in Windows Server 2003 prevents users from installing printers that use third-party kernel-mode print drivers.

This issue may also occur if the following conditions are true:

• DNS reverse zone lookup isn't configured.
• DNS is configured incorrectly on the print server.
• DNS issues on the print server.

Resolution

To resolve this issue, modify the Group Policy settings for the Group Policy object (GPO) that has printer policies defined for the domain users on the domain controller. To do this, use one of the following methods.

Method 1

1. Configure the Load and unload device drivers policy setting for the Power Users group. To do this, follow these steps:
   1. Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
   2. In the navigation pane, right-click your domain name, and then click Properties.
   3. Click the Group Policy tab, click the GPO that you want to modify, and then click Edit.
   4. In Group Policy Object Editor, locate and then click the Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment folder.
   5. Locate and then double-click Load and unload device drivers.
   6. Click to select the Define these policy settings check box, and then click Add User or Group to add the Power Users domain group.
   7. In the Add User or Group dialog box, click Browse to locate the Power Users domain group. Under Enter the object names to select, type Power Users, and then click Check Names to resolve the group name. Click OK three times.
2. Turn off the Disallow installation of printers using kernel-mode drivers policy. To do this, follow these steps:
   1. In the left pane, locate and then click the Computer ConfigurationAdministrative TemplatesPrinters folder.
   2. Locate and then double-click Disallow installation of printers using kernel-mode drivers, click Disabled, and then click OK.
3. Disable the Point and Print Restrictions policy. To do this, follow these steps:
   1. In the left pane, locate and then click the User ConfigurationAdministrative TemplatesControl PanelPrinters folder.
   2. Locate and then double-click Point and Print Restrictions, click Disabled, and then click OK.
4. On the File menu, click Exit.
5. Click Start > Run, type cmd.exe, and then click OK.
6. At the command prompt, type gpupdate /force, and then press ENTER.
7. Repeat steps 5 through 6 on the Windows XP SP1-based and Windows Server 2003-based client computers of the domain.

Method 2

1. On the Windows Server 2003-based print server, click Start > Run, type Cmd, and then click OK.

2. At the command prompt, type C:, and then press ENTER.

3. Type Cd, and then press ENTER.

4. Type Ipconfig /all, and then press ENTER.

5. Write down the IP address of the print server computer.

   Note

   The output for the Ipconfig /all command may resemble the following:

   Windows IP Configuration
   Host Name . . . . . . . . . . . . : MachineName
   Primary Dns Suffix . . . . . . . : DomainName.com
   DNS Suffix Search List. . . . . . : DomainName.com
   Ethernet adapter LAN:
   IP Address. . . . . . . . . . . . : 169.0.0.10
   Subnet Mask . . . . . . . . . . . : 255.255.252.0
   DNS Servers . . . . . . . . . . . : 169.0.0.1169.0.0.2169.0.0.3

6. On the Windows XP-based client computer, click Start > Run, type Cmd, and then click OK.

7. At the command prompt, type C:, and then press ENTER.

8. Type Cd, and then press ENTER.

9. Type Nslookup PrintServer_IP, and then press ENTER.

   Note

   PrintServer_IP is the IP address that you wrote down in step 5.

10. Make sure that the output of the NsLookup command contains the correct fully qualified domain name (FQDN) of the print server. If it is incorrect, you must contact the network administrator to resolve the DNS issue.

More information

When you disable the Point and Print Restrictions policy that is located under User ConfigurationAdministrative TemplatesControl PanelPrinters, users can use the Point and Print functionality to select any shared printer to which they have access. For more information about this policy, see the following Microsoft Knowledge Base article: 319939 Description of the Point and Print Restrictions policy setting in Windows Server 2003 and Windows XP

How to use the registry to set the Point and Print Restrictions policy

Important

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

The Point and Print Restrictions policy can also be set under the following registry subkey:

HKEY_CURRENT_USERSoftwarePoliciesMicrosoftWindows NTPrintersPointAndPrint
Value: InForest
Type: REG_DWORD
Data: 0 or 1

A setting of 0 disables this entry. A setting of 1 restricts printer access to printers in the forest.

Value: Restricted
Type: REG_DWORD
Data: 0 or 1

A setting of 0 disables this entry. A setting of 1 restricts all printers.

Value: TrustedServers
Type: REG_DWORD
Data: 0 or 1

Policy That Blocks Nt 4.0 Drivers Windows 10 64-bit

A setting of 0 disables this entry. A setting of 1 allows printers to appear in the server list dialog box.

For more information about printer installation related issues in Windows XP and Windows Server 2003, click the following article numbers to view the articles in the Microsoft Knowledge Base:

Policy That Blocks Nt 4.0 Drivers Windows 10 Bluetooth Speaker

326473 You are prompted for administrator credentials when you try to install a plug and play printer

Policy That Blocks Nt 4.0 Drivers Windows 10 Download

282011 Printer driver is not compatible if a policy is enabled on your computer

319939 Description of the Point and Print Restrictions policy setting in Windows Server 2003 and Windows XP

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Microsoft Windows Server 2003 x64 edition separately, contact Microsoft for technical support.