Han o sinox running Windows drivers through NDIS

Han o Sinox not only can run Windows applications through wine, but also run Windows drivers through NDIS

Han o sinox using the Windows NDIS driver

The implementation method is to use Ndisgen to convert the Windows driver sys driver into a kernel module KO file, and then let the system load into the KO module can be used. The NDIS driver is responsible for simulating the conversion effort.

Thanks to Bill Paul's work, Sinox has been able to "directly" support the network-driven interface standard (NDIS, Wpaul Driver Interface specification). Sinox Ndisulator (also known as Project Evil) can support the binary form of the Windows driver and let it believe that it is running Windows. Because the NDIS (4) driver uses the driver for Windows binary form, it can only be used on i386 and AMD64 systems.

Note: The NDIS (4) driver is primarily designed with support for PCI, CardBus, and PCMCIA devices, and USB devices are not currently supported, so the USB wireless card is not available,

To use Ndisulator, you need three things:
1.
The source code of the kernel, already has

2.
The binary form of the Windows XP driver (with the extension. SYS)

3.
Windows XP driver configuration file with the extension. INF)

You need to find these files for your card. In general, these files can be found on the CD or manufacturer's website that comes with the card. In the following example, we use the w32driver. SYS and W32driver. INF to represent these files.

Note: You cannot use the windows/i386 driver on AMD64. You must use the WINDOWS/AMD64 driver to work properly on it.

The next step is to assemble the driver in binary form into a kernel module. To complete this task, you need to execute Ndisgen (8) as the root user:
# Ndisgen/path/to/w32driver. Inf/path/to/w32driver. SYS

Ndisgen (8) is an interactive program that prompts you to enter some additional information that is required, which, when completed, generates a kernel module file in the current directory that can be loaded with the following command:
# kldload./w32driver.ko

In addition to the kernel modules that you just generated, you must also load both the Ndis.ko and If_ndis.ko kernel modules, which are usually done automatically when you load a module that requires NDIS (4). If you want to load them manually, you can use the following commands:
# Kldload NDIS
# Kldload If_ndis

The first command loads the NDIS Pocket Port driver Encapsulation module, while the second command loads the actual network interface.

Now check DMESG (8) to see if an error has occurred. If everything works, you'll see output similar to the following:
Ndis0:mem 0xf4100000-0xf4101fff IRQ 3 at device 8.0 on PCI1
Ndis0:ndis API version:5.0
Ndis0:ethernet Address:0a:b1:2c:d3:4e:f5
ndis0:11b rates:1mbps 2Mbps 5.5Mbps 11Mbps
ndis0:11g rates:6mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps

After that, you can use the NDIS0 device as you would with other network interfaces (such as DC0).

As with any other module, you can configure the system to automatically load the NDIS module at startup. First, copy the generated module W32driver.ko to the/boot/modules directory. Next, add in the/boot/loader.conf:
W32driver_load= "YES"

Han o sinox running Windows drivers through NDIS