Notes to IBM Token Ring PCI Family's ** MANAGED DRIVER UPGRADE ** Version 1.00 Usage: WINDOWS 2000 trmdu00 [options] WINDOWS NT 4.0: trmdunt [options] WINDOWS 98: trmdu98 [options] WINDOWS 95: trmdu95 [options] options: /b=[y,n] : boot after completion. default = yes. /d=[y,n] : allow downgrade (i.e. backoff to an older driver) default = no. /f=[y,n] : write status and errors to output file. default=yes. /n=[filename] : name of output file if /f=y. default=myout.dat Dependencies: New driver, new inf file, and all other necessary files from the install diskette must reside in same directory as MANAGED DRIVER UPGRADE exec. Notes: Supports all PCI token-ring adapters with Vendor ID = 1014, Device ID = 003E. MANAGED DRIVER UPGRADE exec will automatically create a log file called myout.dat to record errors and document status. Check this file first if any problems occur. Logging can be supressed using the /f option. The name of the output file can be customized using the /n option. MANAGED DRIVER UPGRADE is meant to be executed by automatic software distribution mechanisms such as Tivoli's TME 10 Software Distribution. It can be run manually from a DOS window or command window too. However it has been observed on Windows 95 that the system may not reboot wihtout user intervention if run from a DOS window. For systems with more than one token-ring adapter, automatic software distribution mechanisms typically will run once for each adapter. Hence MANAGED DRIVER UPGRADE will update only one adapter per execution. For the second and each subsequent execution, MANAGED DRIVER UPGRADE will automtically skip the adapters that have already received the upgrade and select the first adapter that has not received the upgrade. The downgrade (/d) option is not supported by the Windows NT operating system. The MANAGED DRIVER UPGRADE exec will successfully complete (and reboot if /b option is selected) in this case, but the driver will remain unchanged. To manually downgrade the driver, one must remove the adapter from the Network panel, reboot, then add the adapter back using the Network panel, pointing NT to the older driver and inf file. Also for the Windows NT operating system, a userid with administrative authority must be used. If a user with insufficient privilege is used, the MANAGED DRIVER UPGRADE exec will appear to have completed successfully, but the driver will remain unchanged. Refer to Windows NT documentation for details on how to set up userids. Multiple drivers, supporting different NDIS levels, are typically shipped on the install diskette. MANAGED DRIVER UPGRADE should be able to determine which to use from the INF file. However, some older INF files were shipped without enough information for this determination. If this case is detected, MANAGED DRIVER UPGRADE will select the new driver that is at the same NDIS level as the old driver. However, in the case of Windows98, the MANAGED DRIVER UPGRADE will always use the NDIS 5 driver. Change History: 1.00 Initial creationDownload Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.