WORKING WITH INSTRUNET i2x0/i60x DEVICE DRIVERS TROUBLESHOOTING > INSTALLATION >
To Update the i2x0/i60x Windows Device Driver...
Make sure you are on a Windows Xp/Vs/7/8/10 Computer,
Verify that the instruNet software has already been installed on the computer by identifying the START / PROGRAMMING FILES / INSTRUNET directory in the START menu.
Visually verify that your i2x0/i60x controller card is firmly inserted into its connector
Run the Device Manager program by selecting START / Control Panels / System / Hardware tab /
Device Manager Button. The Device Manager program contains a list of devices
(e.g. pci, pcmcia cards) installed on your computer.
Click on "Data-Acquisition Cards", locate the i2x0/i60x hardware, double-click
on the card itself , press the Driver tab, and click the Uninstall button.
Restart your computer.
When your computer boots up, it will see your instruNet i2x0/i60x hardware and will
note that a driver (i.e. sys/inf file) is not attached.
At this point, one must NOT install the default driver (i.e. the old one),
yet instead one must navigate via
the Browse button to the latest instruNet driver files at the following locations. If you installed instruNet onto a Windows 64bit Computer, then the following files will reside in the "Program Files (x86)" directory instead of "Program Files".
i240/i60x USB Driver For 32 or 64bit Windows ≥ XP Sp3 Program Files \ instruNet \ Drivers \ iNet USB Driver \
If you continue to have problems, please see Troubleshooting i2x0/i60x Installation.
Note that the i230 does not run under Win NT and the i240/i60x USB controller does not run under Windows < Xp Sp3.
Working with instruNet Driver Files
Installing New Hardware
The instruNet_Setup.exe software ≥ v1.4 installs inf and sys driver files for the i2x0/i60x controllers. Then, later, when an i230 pcmcia or i240/i60x USB is attached
to the Windows computer, the computer already has the drivers, and the install occurs without prompt. However, in the i200 PCI case, the end
user must navigate after inserting the card to the inet.sys/inetpci.inf files at "Program Files \ instruNet \ Drivers \ PCI Win Nt-2k-Xp
instruNet Driver Files after Installation
The Installer stores drivers at the following locations. If one cannot see the INF or Driver directories, select START \ Control Panels \
Folder Options, click the View tab, and then select "Show hidden files and folders". The iNet32.dll and iNet32_WinXp.dll files are not
part of the formal instruNet Windows OS hardware driver, yet are used heavily by instruNet World and interface software (e.g.
DASYLab, C, Basic). In some cases, the inf/sys files are not copied to the Windows directory until a card is inserted in the computer. Below is a list
of driver files installed onto your computer after you install the instruNet Hardware and Software.
i240/i60x USB Driver
Windows \ Inf \ oem version of inet_usb_installer.inf
Windows \ System32 \ winusb.sys (included w/ OS or coinstaller)
Windows \ System32 \ WinUSBCoInstaller (included w/ OS or coinstaller)
Windows \ System32 \ WdfCoInstaller (included w/ OS or coinstaller)
Windows \ Inf \ oem version of inet_usb_installer.inf
Windows \ SysWow64 \ winusb.sys (included w/ OS or coinstaller)
Windows \ SysWow64 \ WinUSBCoInstaller (included w/ OS or coinstaller)
Windows \ SysWow64 \ WdfCoInstaller (included w/ OS or coinstaller)
i230 PCMCIA Driver
Windows \ Inf \ inetPcm.inf
Windows \ System32 \ Drivers \ iNetPcm.sys
i200 PCI Driver
Windows \ Inf \ inetpci.inf
Windows \ System32 \ Drivers \ iNet.sys
Windows \ System32 \ iNet32.dll
Windows \ System32 \ iNet32_WinXp.dll
Windows \ SysWow64 \ iNet32.dll (32bit DLL runs on 64bit OS)
instruNet Driver Files before Installation
The instruNet_Setup.exe installer places a copy of the driver files at the following locations. If your computer asks for a .sys, .inf, or
.vxd driver file (upon seeing new hardware); please navigate to one of the below directories.
Win ≥ XP Sp3
Program Files \ instruNet \ Drivers \ iNet USB Driver \ inet_usb_installer.inf, coinstallers
The Device Manager program contains a list of devices (e.g. pci, pcmcia cards) installed on your computer. One runs this software
by selecting START / Control Panels / System / Hardware tab / Device Manager Button.
Debugging USB Hardware
If an instruNet i240/i60x controller is unstable in any way,
try removing USB Hub and connect instruNet directly to computer.
If you have many USB devices attached to the computer or you
see a "resource limitation message"; try
removing several USB devices, attach instruNet, and restart computer.
For details on why this
might help, please google search "usb endpoint limitation".
Identifying the State of your i2x0/i60x Controller
An installed i2x0/i60x product is in one of 3 states:
OS does not see the physical card due to card/motherboard malfunction, card not
seated well, or conflict with other card/driver.
OS sees card yet Driver (i.e. .inf/.sys or .ini/.vxd files) cannot establish connection
due to card/motherboard malfunction, card not seated well, conflict with other card/driver, or Driver not installed properly or not at all
(Remove / Update driver, noted below, might remedy this last case).
OS sees card, Driver is installed, and Driver has successful
connected the card to the OS / Computer.
To identify which state your card is in: Install your card, open the Device Manager, as
noted above, and look for a "Data-Acquisition Cards" category with a card listed under it. If you don't see that card, you are in State
#1. If you see the card, yet see a yellow mark on its icon, you are in State #2 and the error message in its Property dialog
summarizes your problem (this message is helpful when interacting with your supplier). If you see that card without the yellow mark,
and the Property dialog says "Driver Installed Correctly", then you are in State #3. If there is a conflict with other pci/pcmcia cards
(typically State #2), then emailing a Registry Report might be helpful.
Removing a Driver on Windows Xp/Vs/7/8/10
To remove a Driver (i.e. .inf/.sys files), one must enter the Device Manager (described above), click on "Data-Acquisition Cards",
locate the i2x0/i60x, double-click on the card itself , press the Driver tab, click Driver Details, write down the location of the
driver files, and then click the Uninstall button. The location of the files is probably similar to that noted above under "instruNet Driver
Files after Installation". After Uninstalling, check that these files have been deleted from your computer, and if they haven't, delete
them manually and Restart your computer. This pertains to "iNetPcm.inf", "iNetPcm.pnf", and "iNetPcm.sys" for the i230 PCMCIA
card; and "inetpci.inf", "inetpci.pnf" and "iNet.sys" for the i200 PCI card. In some cases, the wrong driver attaches to the device, and in that case, one might need to delete an oemXX.inf file,
as described here.
Updating a Driver on Windows Xp/Vs/7/8/10
The instruNet_Setup.exe install program updates the i2x0/i60x drivers when run (i.e. it writes to the Windows inf and driver directories).
However, if one wants to do this manually after running the instruNet_Setup.exe, follow the above instructions in "Removing a Driver", yet press the "Update Driver" button instead of the "Uninstall" button. One must then navigate to the directory
noted above in "instruNet Driver Files locations before sys/inf Installation" for the inf/sys files.
Fixing Wrong Driver Attached To Device
In some cases, the wrong driver attaches to a device, and the Remove/Update
driver does not fix it. The problem is the computer keeps reattaching the wrong driver after you remove/update. To see if this is the case, open Device Manager, find your
instruNet device, right click Properties, click Details tab, select "inf name"
property and write down the name of the displayed .inf file
(e.g. "oemXX.inf" where XX is a number). This is a COPY of the file that the OS is
attaching to your hardware (not the original driver).
Now find this file with Windows Explorer (e.g. at "Windows / Inf / oemXX.inf"),
make a copy of this file and place on desktop (e.g. copy, paste),
add ".txt" to the end of the file name, open with Word Pad, and see if it says
"instruNet" near the top of the file. If not, the OS is attaching the
wrong driver. To fix this, physically disconnect the device,
rename "Windows / Inf / oemXX.inf" to "Windows / Inf / oemXX-DISABLED.inf", rename "Windows / Inf / oemXX.PNF" to "Windows / Inf / oemXX-DISABLED.PNF",
physically re-attach the device, and browse to the driver file as described above if it asks for a driver. Do not
do "Auto" or "let OS search/select for driver", you want to BROWSE.