| re: CHEFS::slagra.reo.dec.com::slade_g
The two machines, Celebris GL 6xxx and Celebris GL 6xxx DP, use
different bioses at the very least. I don't know the other differences
because no one has supplied me with the info. We do not currently have
a DP bios on our BBS/web.
/Bill
|
| G'Day,
You have to be careful which single processor machine they have.
The original single processor GL 6200 is not upgradeable. There is only
one CPU socket on the motherboard. The DP capable machines use a different
motherboard, obviously with two CPU sockets, and you don't need to do anything
other than plug in the 2nd CPU and it's voltage regulator.
This is only from the hardware perspective. If they already have NT
installed it wont automatically use the 2nd CPU. There are many notes in
various conferences about converting and installed NT OS to the multiprocessor
version. For me, I'd rather resinstall.
David.
|
| OK Thanks for the info.
The Celebris inquestion has got 2 sockets.
It turns out that the customer wasn't seating the processor properly.
As for the NT, there is a utility called UPGRADE.EXE, which takes care
of installing the MP Kernal.
Again thanks for your help
Graham
|
| re: <<< Note 7407.5 by PCBUOA::KRATZ >>>
You told me it's UPTOMP.EXE in the NT Resource Kit
Cheers,
/Thien
================================================================
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 box
|