> hi there!
> When adding a extra processor to NT system , is there anything else that has
> to be done or does the OS recognise the new processor automatically?
IIRC, there is a file in the Windows NT4 resource kit named
uptomp.exe. Run it. The otherwise alternative would be to do
a clean installation after the second CPU has been inserted
into the motherboard.
Karl-Stephan Werkmeister - 03 Jul 2005 00:55 GMT
> [...] there is a file in the Windows NT4 resource kit named
> uptomp.exe. Run it. The otherwise alternative would be to do
> a clean installation after the second CPU has been inserted
> into the motherboard.
Be aware of some troubles you may later get if you use uptomp.exe without
further modifications, eg:
http://support.microsoft.com/default.aspx?scid=KB;en-us;168132&sd=tech
http://support.microsoft.com/?scid=kb%3Ben-us%3B841384&x=13&y=9
http://support.microsoft.com/?scid=kb%3Ben-us%3B142660&x=17&y=11
and/or if you later go back to a single-CPU configuration:
http://www.gtweb.net/faq-a.html#nt-q16
Stephan
Frank - 05 Jul 2005 04:01 GMT
I am using NT4 sp6a and when I run uptomp, it asks for the location of
hal.dll. When I specify the CD (NT4 no sp), I get a corrupt ntfs.sys error on
bootup. I downloaded sp6a and extracted it to a directory with the /x and
when I run uptomp and tell it to look at the sp6a extracted folder, it
re-prompts me. What should I do?
> > hi there!
> > When adding a extra processor to NT system , is there anything else that has
[quoted text clipped - 4 lines]
> a clean installation after the second CPU has been inserted
> into the motherboard.
Mistoffolees - 09 Jul 2005 19:32 GMT
> I am using NT4 sp6a and when I run uptomp, it asks for the location of
> hal.dll. When I specify the CD (NT4 no sp), I get a corrupt ntfs.sys error on
> bootup. I downloaded sp6a and extracted it to a directory with the /x and
> when I run uptomp and tell it to look at the sp6a extracted folder, it
> re-prompts me. What should I do?
The location of hal.dll should be the one already in the
computer, under \winnt\system32. But remember the caveat:
Might be better to insert the second CPU and do a clean
installation because there is no guarantee that the multi-
processor hal.dll may be generated properly.