Make sure that the adapter you are performing the upgrade on is supported by the driver you're trying to upgrade to. See the appropriate page under About Drivers for a list of adapters supported by the driver concerned.
This page provides information about:
It also provides links to:
The QuickREV files:
QuickREV upgrades the version of the miniport driver on Windows workstations while maintaining the previous driver configuration.
QuickREV supports driver upgrade on the following platforms:
Windows 95 (OSR2)
Windows 98
Windows ME
Windows NT4
Windows 2000
Windows XP
QuickREV supports driver upgrade from one Microsoft NDIS specification to another supported NDIS specification on a particular platform.
The NDIS architectures that are supported are:
|
Platform |
NDIS Support |
|
Windows 95 (OSR2) / NT4 |
NDIS 3 / 4 |
|
Windows 98 / ME |
NDIS 3 / 4 / 5 |
|
Windows 2000 / XP |
NDIS 5 |
QuickREV supports upgrades from both Olicom and Madge miniport drivers to the latest Madge miniport drivers. The latest drivers support both Madge and Olicom cards. By using QuickREV, you avoid the need for multiple reboots of the computer and reduce the time you take to upgrade the network driver.
|
|
Make sure that the adapter you are performing the upgrade on is supported by the driver you're trying to upgrade to. See the appropriate page under About Drivers for a list of adapters supported by the driver concerned. |
|
|
This version of QuickREV does not support remotely managed upgrade using Wake-On-LAN (WOL) technology. However, a version of QuickREV incorporating WOL support is available on request. For details, visit the Madge website: http://www.madge.com/ |
To upgrade to a new miniport driver:
Navigate to the location of the QuickREV files.
Double-click the QuickREV
icon.
The NDIS Option Select window opens. For details, see The
NDIS Option Select Window.
Click OK.
The QuickREV window opens. For details, see The
QuickREV Window.
Click Upgrade.
The Advanced Driver Settings window opens. For details, see The
Advanced Driver Settings Window.
Click OK.
QuickREV runs the upgrade. On completion, an information pop-up opens,
showing details of the upgrade.
Click OK
to close the pop-up.
You are prompted to reboot your system.
Click OK to reboot.
|
|
If a reboot is not done the driver may not work properly. |
|
|
You can also run QuickREV from the command line. For details, see Command-Line Options. |
This window opens when you double-click the QuickREV icon, or run QuickREV from the command line without specifying the /batch (silent) option.
The NDIS Option Select window shows the current NDIS driver installed on the system. Depending on your windows platform, you can select which NDIS driver you want to upgrade to.
|
|
If the platform does not support a particular architecture, then the corresponding option is disabled. |
Select the driver to upgrade to.
Click OK.
The QuickREV window opens.
This window opens when you click OK from the NDIS Option Select window.
.
The QuickREV window shows the existing driver version and the version of the driver being upgraded to.
You can view information about the last time Madge QuickREV was used on the local computer:
Click
Info.
An information pop-up opens.
Click OK to close the pop-up.
You can upgrade your current driver to the driver version displayed in the Window.
If required,
check Force Upgrade to force
upgrade of the current driver.
This forces QuickREV to replace the driver software without checking
whether any of the new driver files are more recent than the current driver
files. (By default, if none of the new files is more recent than the existing
files, the upgrade does not take place.)
Click Upgrade.
See The Advanced Driver Settings Window below
for details of upgrade parameters.
To access the on-line Help, click Help.
To leave QuickREV without making any changes, click Exit.
This window opens when you click Upgrade from the QuickREV window.
The Advanced Driver Settings window enables you to change the default settings of the driver. The available options depend on the type and version of the driver.
The window above shows settings typical of Windows 95/98/ME/2000 and XP.
If required, change the settings.
Select the property concerned, then choose the appropriate value from
the drop-down-list.
Repeat for each property to be changed.
For details, see the appropriate Driver
Configuration page
|
|
To revert to the default driver settings, select Use Defaults. |
If required, create a script file from the selected settings.
Check Create Script (for details, see Create
Script below).
|
|
In case of Windows NT 4, the window does not have a Create Script checkbox. Instead, when you close the Advanced Settings window, a message box opens asking whether you want to create a script file with the selected settings. |
Click OK.
QickREV runs the upgrade. On completion, an information pop-up opens,
showing details of the upgrade.
Click OK
to close the pop-up.
You are prompted to reboot your system.
Click OK to reboot.
QuickREV logs upgrade information to a text log file.
By default, events are logged to QRLOG.LOG in the current working directory.
The format of entries is:
Instance ID, Computer Name, Date, Message.
|
|
You must have write access to the log file. |
|
|
This file grows indefinitely; truncate it as necessary. |
To change the log file name and or path, specify /logfile=file-name on the command line, in combination with /defaultpath if required (for details, see Command-Line Options).
QuickREV can be used to save the specified advanced settings for a particular driver in a script file. This file can subsequently be run to upgrade other systems.
To create an install script:
Run QuickREV on a single computer.
If the computer is running the current driver, force the upgrade (by
checking Force Upgrade in
the QuickREV window or by specifying /force on the command
line).
In the Advanced Settings window:
Specify the required settings.
Check Create Script.
Click OK.
A Save dialog opens.
|
|
In case of Windows NT 4, the window does not have a Create Script checkbox. Instead, when you close the Advanced Settings window, a message box opens asking whether you want to create a script file with the selected settings. |
If required, specify a name and path for the script file.
By default, the file-name is QUICKREV.QRS and the location is the current working directory.
You can now run upgrades using the saved settings by specifying /scriptfile on the command line. For details, see Command-Line Options.
|
|
Use the script file in conjunction with the /batch command line option to automate the upgrade. |
|
|
Do not use a script file generated for a specific adapter on a specific platforms for other adapter or other platforms. Doing this may render the adapter unusable, requiring you to reinstall the adapter. |
|
|
If you specified a network address in the Advanced Driver Settings window when you created the script file, QuickREV ignores this and preserves the existing LAA. |
To use the command line options, invoke QuickREV from a Command Shell or use the Run ... option on the Start menu.
|
/force |
Forces QuickREV to replace the driver software without checking whether any of the new driver files are more recent than the current driver files. (By default, if none of the new files is more recent than the existing files, the upgrade does not take place.) |
|
/batch |
Runs a silent upgrade, running QuickREV with minimal user intervention, either with default settings or with the settings in the specified script file. QuickREV does not confirm the success or failure of the upgrade, but records it in the log file. |
|
/reboot |
Reboots the system after a successful upgrade. /reboot can be used in conjunction with /batch to automate upgrades. |
|
|
The following options can be used in combination. /driverpath, /scriptfile and /logfile all override /defaultpath. |
|
/defaultpath=path |
The path to the new driver files, script file and log file. If not specified, this defaults to the current working directory. |
|
/driverpath=path |
The path to the new driver files. If not specified, this defaults to the /defaultpath. |
|
/scriptfile=filename |
The name and/or path to the script file to be used. If no path is specified, this defaults to the /defaultpath. If you specify a relative path, it must be relative to the current working directory. |
|
/logfile=filename |
The name and/or path to the text log file. If no path is specified, this defaults to the /defaultpath. |
See Also: