================================================================ Design and Usage notes for UniProcessorTOMultiProcessor upgrade utility ================================================================ Usage Notes: UPTOMP.EXE requires the following files to run: UPTOMP.INF this file describes the files to be replaced as a part of the upgrade processs. This file must be present in the Default directory, the directory that contains the UPTOMP utility or the WINDOWS directory. TXTSETUP.SIF on each disk that contains upgrade files (either HAL or system files). TXTSETUP.SIF contains information about the disk(s) where the upgrade files are located and the destination directories of those files Using the utility, UPTOMP will check to see that the system it is running on is currently a Uniprocessor system, then prompt the user for the location of the upgrade HAL file. The default value for this dialog is determined by the following algorithm: the path defined in the registry under the: LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\UPtoMP key and assigned to the "Files" value. The CD-Rom path for the current machine The A: drive if neither of the above yields a path. When the user has selected the HAL to install and the disk on which it may be found, the user is then prompted for the path to the Windows NT system files (typically found on the distribution media). Once the system file information (e.g. location and destination) has been recorded the user will be informed that the upgrade process is not reversable and if they are still sure they want to upgrade their system. If they elect to continue, the system will copy the files from their respective source directories to a temporary directory created under the %temp% dir. Before copying the system files from the temp dir to the system32 dir, the files to be replaced are moved to a subdir of system32 where they can be used to restore the system should the upgraded files not work properly. After the original system files have been safely moved, the files in the temp dir are moved to the system32 dir and then the temp dir is deleted. If all goes well, the user will be given a final dialog box that: a) informs them that the upgrade was successful b) the system will need to be restarted for this change to take effect c) that they should run RDISK after the system restarts to update the saved configuration. They are presented with the chioce of restarting the computer immediately or closing the application without restarting the computer. Design Notes: The UPTOMP utility function are based on the Copy List which is an internal linked list of structures, each of which contains the copy information for a single file to upgrade. This list is built when the program starts using data from the UPTOMP.INF file. The Welcome dialog modifies the "HAL" file entry in the copy list. (The HAL entry is a special entry in the list and is identified by the bHalEntry flag set TRUE). The "HAL" entry is modified to reflect the user's choice from the dialog box, replacing the "generic" entry from the UPTOMP.INF file. The System dialog reads the Windows NT TXTSETUP.SIF file to update the remaining (i.e. NON-HAL) file entries. The copy & upgrade process consists of the following steps: a) create the temporary (i.e. work) directory and the archive sub-dir b) copy the files from the source disks/paths and expand them into the temp directory --- Errors that occur up to this point will NOT effect the operation of the system. --- c) move the system files to be replaced into the archive directory (They cannot be copied since they are most likely still open by the OS). --- Errors at this point will require the saved files to be moved from the archive dir back to the original (system32 in most cases) directory before trying to restart NT. d) move the files from the temp dir to the destination (i.e. system32) dir. --- Errors at this point will require the saved files to be moved from the archive dir back to the original (system32 in most cases) directory, overwriting the new files, before trying to restart NT. e) delete the temporary directory f) present the restart dialog boxDownload 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.