Do you already have an account? I also tried this for the second network card, but no luck there. JoeSchmoe , Jul 16, Here is how to get them for Asus ZPlus: Looking for the HWID.
| Uploader: | Doukus |
| Date Added: | 7 September 2018 |
| File Size: | 24.43 Mb |
| Operating Systems: | Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X |
| Downloads: | 43774 |
| Price: | Free* [*Free Regsitration Required] |
But as I have no need for a second network card, I don't care. Your name or email address: JoeSchmoe e11d63x64.inf, Jul 16, After doing some research on the subject, it turned out that manufacturers sometimes disable network support for certain operating systems in.
Intel(R) Gigabit Connection, Intel(R) Gigabit Network Connection, Win7x64, Win8x64
I started out doing exactly what is described here and it didn't work for me. Often times you can use have disk and select the driver, even if the INF doesn't match, and force it. Apperently it's name is slightly different and perhaps I would have to alter another file for that. Intel should of course make drivers for this chipset for Windows Server and Asrock should not use this chipset unless it would support all recent MS operating systems.
After installing Windows Server trial on my new system built around Asus ZPlus motherboard I found that all Windows 8 drivers worked except the network.
Than I had another look at the content of the CD and compared that with what was mentioned here. In the past this never was an issue.
[HOW-TO] Force Windows 8 network driver to install under Windows Server 2012
I did not download any drivers from Intel, I e1d6364.inf used the CD that was provided with the mainboard. Hope that I helped someone by leaving this post here.
When setup for network drivers was run it could not find any known network adapters. The source of information for this guide was this page for a different network card: This is kind e1d63x64.inf an old thread, but just a quick thx for the tip how do force the intel driver to work with win server. So thx e1d63s64.inf to JoeSchmoe who saved me from buying an additional intel nic.
Select the path where the path of the. It should similar but not identical! I also tried this for the second network card, but no luck there.
Enable any not officially supported Intel Ethernet Adapter in Windows Server | SabrNET
To know which file exactly to modify i used Powershell: Jul 31, 3. The setup program still reported that it couldn't find ant correct Intel Network card. No, create an account now. If other people see this, just a quick headsup.
Jul 31, 4.
It costed more than euro's, it can handle up to 22 hard drives, it has an integrated SAS controller and it has active cooling. But I must say who are they to tell pfo1000 what to use or not to use in my server. Also note that the title where you need to add these lines has now become: I went to device management, clicked on one of my network cards and pointed the folder to NDIS64 where I had made this change.
Index of /SUPERMICRO/X10SLA-F/DRIVER/LAN/PRO1000/Winx64/NDIS63
I used the same 2 sites that you linked but I think I didn't follow all of the steps. Jul 16, 1. A month ago I tried for 3 days to get my iV nic working but was unsuccessful.
I tried to run setupBD executable instead of the dxsetup executable. I blame both Intel and Asrock for this problem.
Comments
Post a Comment