Enable Multiprocessor

Question

Ok it's my fault that I wanted to test out the diff between Uni and Multiprocessor with HT enabled in my BIOS   It was running Multiprocessor but I noticed that the startup of windows was pretty slow for a 2.8E HT compare to a 2.0B P4 chip. So I decided to install Uniprocessor in the device manager and test it out...
alas... same thing. Now I decided to change it back to Multiprocessor but I don't know how to. Have went through a few posting and everything points back to reinstall back XP pro. Is there anyway out instead or reinstalling or formatting my pc?
Funny thing is in device manager under processor I can see it shows 2 processor b ut when I look at the performance in Task Manager, it only shows me one processor....

Answer 1

Found the below solution.. am not sure whether will be it be solve. Can only test it in another few days times
Installing Just the Checked Operating System and HAL
Instead of installing the complete checked build on your computer, you can install the free build of the system, and then install the checked versions of just the operating system image and HAL. If you use this procedure, you can configure the boot loader to provide you with two boot options. One boot option is for the free build. The second boot option starts the system using just the checked operating system image and HAL, but uses free versions of all other system components.
This approach, compared to installing the complete checked build, provides the following advantages:
·   Drivers get the benefit of the operating-system and HAL debug checks. At the same time, because free versions of system components other than the operating system and HAL are being used, the performance impact on the entire system is minimized.
·   A single installation (and thus one system directory, one set of executable components, and one set of registry parameters) can use either the checked or the free version of the operating system image and HAL, as determined at boot time.
To install the checked versions of the operating system image and HAL, you must copy the appropriate files from the checked distribution medium to the %SystemRoot%\system32 directory using new, unique file names. Then you must instruct the system to offer an option that uses these files during system startup. There are a few important guidelines to keep in mind when installing checked operating system and HAL images on an otherwise free installation:
·   The operating system image and HAL must be kept in synch at all times. Therefore, if you use a checked version of the operating system image, you must also use the checked version of the HAL (and vice versa). Failure to keep a system's operating system image and HAL coordinated can make the system unbootable.
·   Do not overwrite the free versions of the operating system image and the HAL that are installed during the installation of the free build. Overwriting the free versions of the operating system image and HAL can make the system unbootable, and can make it difficult to recover from errors. Therefore, always be careful to use new, unique file names when copying the checked versions of the operating system and HAL to the %SystemRoot%\system32 directory.
·   Make sure the checked distribution you use is the same Service Pack number as that of the free system. For example, if you are installing the checked operating system image and HAL onto a system for which Service Pack 2 of a free build system is installed, make certain that the checked distribution you are using is also Service Pack 2.
If you follow these guidelines, installing the checked versions of the operating system and HAL is easy.
Use the following steps to install a partial checked build.
Step 1: Identifying the Files To Install
Your first step in installing a partial checked build is to determine the version of the operating system image and HAL files that were used to install the free build on your system.
Several different versions of the operating system and HAL images are supplied on the NT-based operating system distribution medium. These different versions exist to support different combinations of processors and other system hardware. When the operating system software is installed, the installation procedure automatically identifies which operating system image and HAL image to use, and copies the appropriate files from the distribution medium to the system's %SystemRoot%\system32 directory.
The operating system image file that is installed depends on whether one or multiple processors are to be supported, and on whether Physical Address Extension (PAE) is supported. (PAE is active on systems with more than 4 GB of physical memory.). The file names on the distribution medium are as follows:
ntoskrnl.exe
Uniprocessor x86 architecture systems with 4 GB of physical memory or less.
ntkrnlpa.exe
Uniprocessor x86 architecture systems with PAE support.
ntkrnlmp.exe
Multiprocessor x86 architecture systems with 4 GB of physical memory or less.
ntkrpamp.exe
Multiprocessor x86 architecture systems with PAE support.
Likewise, there are several different names for the HAL.
During system installation, the installation procedure determines the appropriate operating system image and HAL to install on your system. The selected files are copied to the %SystemRoot%\system32 directory during installation, using fixed, well-known, names. The use of these fixed names makes it easy for the loader to locate these files at boot time. The fixed names for these files are:
ntoskrnl.exe
Operating system image for x86 systems with 4 GB or less of physical memory.
ntkrnlpa.exe
Operating system image for x86 systems with more than 4 GB of physical memory.
hal.dll
Loadable HAL image.
Note that in some cases, depending on the system's hardware configuration, one or more of the files may be renamed to the appropriate fixed name. In other cases, the file name on the distribution medium is the same as the required fixed file name.
Your first step in installing the checked operating system image and HAL is to determine the original names of the images that were copied to your system during system installation. You do this by examining the file %SystemRoot%\repair\setup.log. This is a hidden file, so you will have to change its attributes before it can be displayed by the MS-DOS® dir command.
The setup.log file indicates the files that were copied from the distribution medium to the %SystemRoot%\system32 directory during the system installation process. Here is an example of a setup.log file:
[Paths]
TargetDirectory = "\WINNT"
TargetDevice = "\Device\Harddisk0\Partition1"
SystemPartitionDirectory = "\"
SystemPartition = "\Device\Harddisk0\Partition1"
[Signature]
Version = "WinNt5.1"
[Files.SystemPartition]
NTDETECT.COM = "NTDETECT.COM","f41f"
ntldr = "ntldr","3e8b5"
arcsetup.exe = "arcsetup.exe","379db"
arcldr.exe = "arcldr.exe","2eca9"
[Files.WinNt]
\WINNT\system32\drivers\kbdclass.sys = "kbdclass.sys","e259"
\WINNT\system32\drivers\mouclass.sys = "mouclass.sys","7e78"
\WINNT\system32\drivers\uhcd.sys = "uhcd.sys","10217"
\WINNT\system32\drivers\usbd.sys = "usbd.sys","5465"
(…several similar lines omitted…)
\WINNT\system32\framebuf.dll = "framebuf.dll","10c84"
\WINNT\system32\hal.dll = "halmacpi.dll","2bedf"
\WINNT\system32\ntkrnlpa.exe = "ntkrpamp.exe","1d66a6"
\WINNT\system32\ntoskrnl.exe = "ntkrnlmp.exe","1ce5c5"
\WINNT\inf\mdmrpci.inf = "mdmrpci.inf","96a3"
You can identify which operating system image and HAL files were installed on your system by searching setup.log for the fixed operating system image file names. Make a note of the original file names used on your system, because you will need to copy the checked versions of these same files from the checked distribution kit. You will find the standard, well-known, file name on the left of the equal sign. Its original name from the distribution medium will be immediately to the right of the equal sign on the same line.
In the sample setup.log file shown above, you can see that two operating system image files were copied to the \winnt\system32 directory (which is %SystemRoot%\system32) during installation. The file ntkrpamp.exe is copied from the distribution medium to ntkrnlpa.exe and the file ntkrnlmp.exe is copied from the distribution medium to ntoskrnl.exe. From this sample, you can also see that the HAL file (with the fixed name hal.dll in the %SystemRoot%\system32 directory) was originally named halmacpi.dll.
Warning  Some HAL files have deceptively similar names. For example, halacpi.dll and halapic.dll are two commonly used HALs. Be careful to use the correct version of the HAL for your system. Selecting the wrong HAL will result in a system that is not bootable.
Step 2: Copying the Checked Files
Now that you know the names of the files that were used during your system installation, you can copy the checked versions of these files to your system. Find the files you have identified in the checked distribution kit. Then copy these files to the %SystemRoot%\system32 directory of your system, giving them new, unique, file names. The copies of these files must follow the 8.3 naming convention. One way to ensure unique, 8.3-compliant file names is to rename the file types from their original file types (.dll or .exe) to .chk when they are copied. Thus, using the example started in Step 1, you would copy files from the checked distribution kit as follows:
If the original file name in the checked distribution is:    Copy it to the following file name in %SystemRoot%\system32:
ntkrnlmp.exe   ntkrnlmp.chk
ntkrpamp.exe   ntkrpamp.chk
halmapic.dll   halmapic.chk
Some files in the checked distribution are provided in compressed form. These files are indicated with an underscore character as the last character in their file type. For example, if you look for the file halapic.dll in the checked build distribution kit, but you find the file halapic.dl_, you have found the correct file, but in compressed form.
To decompress compressed files from the checked distribution, use the Expand utility (%SystemRoot%\system32\expand.exe). For example, to expand halapic.dl_ and name the expanded file halapic.chk, you can use the following command from a command prompt window:
> expand halapic.dl_ halapic.chk
Step 3: Editing boot.ini
After you have copied the checked files to the %SystemRoot%\system32 directory, you must create a boot-time option that allows the system to be started using these checked files. You do this by editing the file boot.ini.
For general instructions, see Editing the boot.ini File.
In this specific case, you need to create a new boot-time option that allows you to start the system with the checked version of the operating system image and HAL that you have installed.
Locate the line in the [operating systems] section of boot.ini that refers to your Windows installation. Make a second copy of it, and add to the end of the copied line the following parameters:
/kernel=KernelFile /hal=HalFile
where KernelFile is the name of the checked version of the operating system image file that you previously copied from the checked distribution kit, and HalFile is the name of the checked version of the HAL that you previously copied from the checked distribution kit.
If the line that describes your operating system contains the /PAE parameter, be sure to use the checked version of the operating system image that supports Physical Address Extension. If the line that describes your operating system does not have the /PAE parameter, use the checked version of the operating system image without PAE support.
You should also change the quoted text on the new line, so that you will be able to identify which line is the free build and which line is the partial checked build.
Here is an example of such a boot.ini file:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2000 Checked" /fastdetect /kernel=ntoskrnl.chk /hal=halacpi.chk
If you will be using the checked build with a kernel debugger, you should also add the proper debugging-related parameters. (The /kernel and /hal parameters do not enable debugging automatically.) See Editing the boot.ini File for details.
Once you have made your changes, save the changes and exit from the editor. The next time you boot this system, a new operating system boot option will be displayed that allows you to select your checked operating system image and HAL.