[THIN] Re: Add an extra CPU - NT 4 Terminal Server Edition - HP DL380G2
- From: "Johnny Henegar" <jhenegar@xxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 7 Feb 2003 09:03:22 -0500
Steve,
As long as you follow the KB article from below you should be ok :-)
------------------------------------------------------------------------
---------------------------
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;156358
SUMMARY
This article describes how to change Windows NT from single processor
support to multiprocessor support or from multiprocessor support to
single processor support.=20
MORE INFORMATION
Before you start, make sure that you have a complete, working backup of
the system files and the registry, and that you have a current Emergency
Repair Disk (ERD). To create an updated ERD, run Rdisk.exe from a
command prompt, and then select Update Repair Info.=20
To add support in Windows NT for an additional processor, follow these
steps:=20
NOTE: Some Compaq computers require a different HAL -- Halsp.dll. Refer
to the latest Compaq Software Support Disk SSD for details.=20
Install Windows NT to a separate folder on your hard disk, and then
restart your computer to the new installation of Windows NT.
In the %SystemRoot%\system32 folder of your original Windows NT
installation, rename the following files to alternate names:
Ntoskrnl.exe
Hal.dll
Kernel32.dll
Ntdll.dll
Winsrv.dll
Win32k.sys (additional file in Windows NT 4.0 only)=20
Determine which multiprocessor HAL your computer requires using the
following list:
Halast.dll =3D "AST Manhattan SMP"
Halsp.dll =3D "Compaq SystemPro Multiprocessor or 100%
Compatible"
Halcbus.dll =3D "Corollary C-bus Architecture"
Halmca.dll =3D "IBM PS/2 or other Micro Channel-based PC"
halmpsm.dll =3D "Micro Channel Multi Processor PC"
Halapic.dll =3D "MPS Uniprocessor PC"
Halmps.dll =3D "MPS Multiprocessor PC"
Halncr.dll =3D "NCR System 3000 Model 3360/3450/3550"
Haloli.dll =3D "Olivetti LSX5030/40"
Hal.dll =3D "Standard PC" (single processor HAL)
Hal486c.dll =3D "Standard PC with C-Step i486"
Halwyse7.dll =3D "Wyse Series 7000i Model 740MP/760MP"
=09
NOTE: The Ntkrnlmp.exe and appropriate HAL file need to be the same
version as that of the NT installation. Failure to get files from the
appropriate service pack will result in system instability and error
message on blue screens. This also applies for files that require manual
expansion with the Expand.exe tool that need to be obtained from the
service pack cd or directory location.
Copy the Ntkrnlmp.exe file and the appropriate HAL file from the Windows
NT CD-ROM to the %SystemRoot%\system32 folder of your original Windows
NT installation. If a service pack has been installed to the system,
copy the files from the current service pack version cd or install
location to the %SystemRoot%\system32 folder of your original Windows NT
installation. Once the files are in place, rename them to Ntoskrnl.exe
and Hal.dll, respectively.=20
Copy the Ntdll.dll file from the original Windows NT CD-ROM
%SystemRoot%\system32 folder of your original Windows NT installation.
If a service pack has been installed to the system, copy the files from
the current service pack version cd or install location to the
%SystemRoot%\system32 folder of your original Windows NT installation.=20
From a command prompt, expand the Kernel32.dll and Winsrv.dll files from
the Windows NT CD-ROM or installed service pack to the
%SystemRoot%\system32 folder of your original Windows NT installation.
For example, type the following commands:
expand kernel32.dl_ %systemroot%\system32\kernel32.dll
expand winsrv.dl_ %systemroot%\system32\winsrv.dll
NOTE: To properly expand files from the Windows NT CD-ROM, you must use
the Expand.exe utility included with Windows NT. The Windows NT
Expand.exe utility can only be run from a command prompt in a 32-bit
environment such as Microsoft Windows 95 or Windows NT.=20
NOTE: In Windows NT 4.0, the Win32k.sys file is also required. Expand it
from the original Windows NT CD-ROM or the installed service pack.
Restart your computer.
When the Windows NT kernel loads, ensure that it displays
"Multiprocessor kernel" during startup.=20
Support for the second processor is now installed and is ready for use.
To return to single processor support, restore the old files to the
original names in the %System Root%\System32 folder, and then restart
the computer.=20
NOTE: The files located on the Window NT CD-ROM and in the service packs
are multiprocessor-aware. To return to a single processor, you must
install Windows NT on a single-processor computer, install any
applicable service packs, and then copy the associated files from that
computer to the computer you want to return to a single processor. You
should also update the Setup.log file in the $SystemRoot%\Repair folder
to reflect the correct state of your computer in order for future
service packs and the repair process to function properly. To update the
Setup.log file you must manually enter the correct file and checksum
value. For a listing of the correct values, see the following article in
the Microsoft Knowledge Base:=20
168132 After Applying Service Pack NT Reports Single Processor=20
For additional information, see the following articles in the Microsoft
Knowledge Base:=20
ARTICLE-ID: 124541
TITLE : Use UPTOMP.EXE to Upgrade Single-Processor to Multiprocessor
ARTICLE-ID: 148245
TITLE : Upgrading from Uni- to Multi-Processor Requires Service Pack
ARTICLE-ID: 142660
TITLE : Upgrade from Uni- to Multiprocessor (Uptomp.exe)and Win32k.sys
NOTE: When you change to or from single or multiple processors, if you
are using Proxy 2.0 server on the same computer, you also need to
replace the Ipfltdrv.sys driver as well (%SystemRoot%\system32\drivers).
The single- processor version is 36 KB in size and is located on the
Proxy 2.0 CD-ROM in the Msproxy\I386\Routing\Up folder. The
multiple-processor version is 34 KB in size and is located on the Proxy
2.0 CD-ROM in the Msproxy\I386\Routing folder
------------------------------------------------------------------------
---------------------------
Hope this helps some :)
--Johnny
-----Original Message-----
From: ROSA Steve [mailto:Steve.ROSA@xxxxxxxxxx]=20
Sent: Friday, February 07, 2003 8:44 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Add an extra CPU - NT 4 Terminal Server Edition - HP
DL380G2
Hello,
Hardware : Compaq/HP Proliant DL380G2 - 1 CPU 1.133 GHZ
OS : MS Windows NT 4 Terminal Server Edition SP6 + Citrix MetaFrame 1.8
FR1
I would like to add an extra CPU to this server. I now that for "usual"
NT 4, I have to install the CPU and update the HAL. Is there any
difference for TSE servers ?
Many thanks in advance for your inputs and best regards
Steve Rosa
Fortis IT & Support
System Administrator
Corporate Centre
Rue Royale, 20
1000 Brussels
Belgium
E-mail : steve.rosa@xxxxxxxxxx
-- No attachments (even text) are allowed --
-- Type: text/plain
-- File: InterScan_Disclaimer.txt
********************************************
This Week's Sponsor: triCerat Inc.
Let triCerat simplify the administration=20
of your Terminal Servers.
http://www.triCerat.com
********************************************
For Archives, to Unsubscribe, Subscribe or=20
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
********************************************
This Week's Sponsor: triCerat Inc.
Let triCerat simplify the administration
of your Terminal Servers.
http://www.triCerat.com
********************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
