Root | Home Hobbes | UnixOS2 | OS2Ports | VOICE | OS/2 World | News and Rumors Select Let me pick from a list of device drivers on my computer.Ĭlick the Have Disk button and enter the full path to the e1e6232e.inf file.OS/2 Site - OS/2 software and information. Select Browser my computer for driver software. Under the Driver tab, click Update Driver. Right click the NIC device and choose Properties. inf file or it won't load any of it. Now save the file and close Notepad.įind the network card in Computer Management / Device Manager. The NDIS 6.3 area is empty anyways. Apparently there is a rule, no empty areas allowed in an. Now we need to edit the e1e6232e.inf file. We can use good old notepad.Ĭ:\Users\.\PRO1000\Win圆4\NDIS63\> notepad e1e6232e.infĪbout 40 lines down, you will see the following entry: Now let's go to a folder among the extracted files.Ĭ:\Users\bri\AppData\Local\Temp\> dir /adīy default the Intel driver extracts to a folder called "RarSFX0" (that's a ZERO on the end, not an O). We will want to CD into that folder, and into the following path:Ĭ:\Users\bri\AppData\Local\Temp\> cd RarSFX0\PRO1000\Win圆4\NDIS63 Reboot (yes, a reboot is required, I tested it)Īn easy way to unpack the driver files is to just double click the PROWin圆4 icon, but do not click Next or Cancel when the install form appears. The files will be unpacked in your user's temp folder. We just need them to sit there for a while. Run CMD.exe to get a command prompt. It will most likely need to be elevated, so you might have to hold down CTRL+SHIFT+ENTER to launch it elevated.Ĭ:\> bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS inf file. You won't be able to install the modified driver without this step: You will need to first disable driver signing, as we are going to modify the. It turns out that there is an error in a file named e1e6232e.inf. Here are the steps to fix it:
You think to yourself, "I'll just get online and Google the answer" but find very little to answer the problem at hand. You may come across this well written article, which describing an issue where Intel purposely disabled some of their drivers for certain platforms, and how to get around it. Unfortunately, that did not turn out to be the problem here, as the PRO 1000 drivers are indeed enabled. However, the article above was the inspiration I needed to find the problem.
0 kommentar(er)
