存储在NAS中的备份文件，并将启动映像发送到客户端(客户端与服务器的型号相同)，以便PXE引导和映像或恢复其驱动器。

轻松的工作。

问题是驱动程序支持。

由于我有很多时间，我测试了尽可能多的解决方案来安装驱动程序：

对于Windows 8,8.1,10,12012,2012 r2和2016，我尝试在全新安装后和完全更新后安装驱动程序版本23.2。

我也尝试使用版本21，据​​我所知，这是第一个为这张卡提供支持的版本。

全部失败，并显示“此计算机上没有Intel适配器”的消息。

如果我试图让Windows在文件夹中查找驱动程序，它会说没有找到驱动程序，如果我尝试从e1d64x64.inf加载的列表中选择驱动程序，则只列出该卡的LM变体，没有

五

到目前为止，已知一种解决方法是手动安装卡的LM变体的驱动程序。

我不知道是否有任何差异，但它是有用的。

如果在此之后我再次运行驱动程序安装程序，有时它将安装正确的驱动程序，有时它不会。

但是，当我的备份软件在我的启动映像或整套驱动程序中注入此驱动程序(e1d64x64.inf)时，客户端启动时不会加载任何网络驱动程序。

我在论坛中读到，当硬件ID与驱动程序文件中的描述不匹配时，您会收到该错误消息，因此我检查了它是什么。

在我的特定机器中，网卡被列为Intel以太网连接(4)I219-V。

Windows设备管理器中的硬件ID是：

PCI \ VEN_8086＆放大器; DEV_15D8＆安培; SUBSYS_20688086

当我查看英特尔套件中NDIS64文件夹中的INF文件时，它会显示此设备的以下值：

[Intel.NTamd64.6.3.1]

;

displayName Section DeviceID

;

----------- ------- --------

％E15D8NC.DeviceDesc％= E15D8.6.3.1，PCI \ VEN_8086＆amp; DEV_15D8

％E15D8NC.DeviceDesc％= E15D8.6.3.1，PCI \ VEN_8086＆amp; DEV_15D8＆amp; SUBSYS_00008086

我决定添加一行来自Windows设备管理器的信息并尝试从设备管理器安装驱动程序无效，但后来我注意到另一个区域略有不同的标题，没有任何对此硬件I​​D的引用

，以及“Section”值没有后缀的地方。

所以，对于那个区域，我添加了这一行：

[Intel.NTamd64.6.3]

;

DisplayName Section DeviceID

;

----------- ------- --------

％E15D8NC.DeviceDesc％= E15D8，PCI \ VEN_8086＆amp; DEV_15D8＆amp; SUBSYS_20688086

如果我让Windows查看此驱动程序所在的文件夹，它会检测到它并尝试安装它，但它会抱怨驱动程序的安全目录(e1d64x64.cat)中没有此硬件的字符串。

考虑到我对INF文件所做的修改，这是有道理的。

因此，我删除了INF中的CAT文件引用，禁用了签名强制执行，并且看，我能够通过将Windows指向它来安装驱动程序。

在禁用驱动程序签名实施后，它还可以在其他版本的Windows上运行。

到目前为止，我还没有注意到它的功能有任何问题。

这让我回到原来的问题。

虽然我可以通过禁用签名强制使驱动程序在完整的Windows环境中工作，但我发现你无法在WinPE上禁用该东西。

所以，我回到了正方形1.我有一个功能但未签名的驱动程序，我无法用于PXE启动我们的客户端计算机来运行我们的备份软件。

我无法修改软件的图像，只会注入我提供的驱动程序，如果没有签名则会崩溃。

但签名的驱动程序不起作用。

有没有办法为这个特定的VEN / DEV / SUBSYS组合获得第三方签名驱动程序？

英特尔有人愿意调查吗？

谢谢你的帮助。

以上来自于谷歌翻译

以下为原文

Hello

I have a NUC7i3BNK that is used mostly to host a Quickbooks database, and we want to use it as a sort of backup server. This machine would access the backup files stored in a NAS and would send a boot image to the clients (the clients are the same model as the server) to PXE boot and image or restore their drives. Light work.

The problem is the driver support. Since I have a lot of time, I tested as many solutions as I could to get the driver to install:

For Windows 8, 8.1, 10, 2012, 2012 r2 and 2016, I tried installing driver version 23.2 after fresh installs and after fully updating.

I tried that also with version 21, which, as I understand, was the first version to offer support for this particular card.

All fails with the message about "No Intel adapters are present on this computer". IF I try to have Windows look for the driver in a folder, it will say no driver was found, and if I try to pick a driver from a list loaded from e1d64x64.inf, only the LM variants of the card are listed, none of the V.

By now it's known that a workaround is to manually install the driver for the LM variant of the card. I don't know if there are any differences, but it's functional. If after this I run the driver installer again, sometimes it will install the right driver, and sometimes it won't.

However, when I have my backup software inject this driver (e1d64x64.inf) in my boot image, or the whole set of drivers, no network driver is loaded when the client boots up.

I read in the forums that you get that error message when the hardware ID doesn't match the descriptions in the driver file, so I checked what it was. In my specific machine, the network card is listed as Intel Ethernet Connection (4) I219-V. The hardware ID's from Windows Device Manager are these:

PCI\VEN_8086&DEV_15D8&SUBSYS_20688086

When I looked at the INF file from the NDIS64 folder in the Intel bundle, it shows these values for this device:

[Intel.NTamd64.6.3.1]

; DisplayName                   Section              DeviceID

; -----------                   -------              --------

%E15D8NC.DeviceDesc%            = E15D8.6.3.1,       PCI\VEN_8086&DEV_15D8

%E15D8NC.DeviceDesc%            = E15D8.6.3.1,       PCI\VEN_8086&DEV_15D8&SUBSYS_00008086

I decided to add a line with the information from the Windows Device Manager and tried to install the driver from the Device Manager to no effect, but then I noticed another area with a slightly different header that didn't have any references to this hardware id, and where the "Section" values didn't have suffixes. So, for that area, I added the line:

[Intel.NTamd64.6.3]

; DisplayName                   Section        DeviceID

; -----------                   -------        --------

%E15D8NC.DeviceDesc%            = E15D8,       PCI\VEN_8086&DEV_15D8&SUBSYS_20688086

If I have Windows look into the folder where this driver is, it detects it correctly and attempts to install it, but it will complain that the string for this hardware is not present in the security catalog (e1d64x64.cat) of the driver, which makes sense, given the modifications I made to the INF file. So, I deleted the CAT file reference in the INF, disabLED the signature enforcement, and lo and behold, I was able to install the driver by pointing Windows to it. It also worked on the other versions of Windows, after disabling the driver signature enforcement. I haven't noticed any problems in its functioning so far.

Which brings me back to my original problem. Although I could make the driver work in a full windows environment by disabling signature enforcement, I found out that you can't disable the thing on WinPE. So, I'm back to square 1. I have a functional but unsigned driver that I can't use for PXE booting our client computers to run our backup software. I can't modify the software's image, it will just inject the drivers I provide it with, and crash if they're not signed. But the signed driver doesn't work.

Is there any way to get a third party signed driver for this specific VEN/DEV/SUBSYS combination? Is anyone at Intel willing to look into it?

Thanks for your help.

0