COMMAND

    UPTOMP

SYSTEMS AFFECTED

    WinNT

PROBLEM

    G. Chatten found following.  Not sure if anyone else has had  this
    problem, but an existing NT4/SP5 system was "ghosted" over to  new
    SCSI drives and a  new box with dual-450's.   System came up  fine
    and ran  12 hours  in single  processor mode.   After getting  the
    latest UPTOMP.INF file from  MS, dumping the \I386  directory from
    the original  CD on  the hard  drive, over-write  those files with
    the SP5 kit to be on  the same level.  Change the  repair.log file
    in the \system32  directory to reflect  the correct CRC  per MS KB
    and ran UPTOMP using a "standard pc" HAL and the "merge" files  we
    put together from the above.  Ref Microsoft KB's:

        Q156358 - ftp://ftp.microsoft.com/bussys/winnt/kb/Q156/3/58.TXT
        Q124541 - ftp://ftp.microsoft.com/bussys/winnt/kb/Q124/5/41.TXT
        Q142660 - ftp://ftp.microsoft.com/bussys/winnt/kb/Q142/6/60.TXT

    This method has  worked before on  5 boxes with  NT4/SP4, however,
    this was the first box to be UPTOMP'd that already had SP5  loaded
    on it.  NT booted up  with the multi-processor kernel -- but  only
    reported 1  processor (bios  boot shows  two), and  died on the NT
    Server  splash  screen.   After  restoring  original  files   from
    UPTOMP.OLD to \system32;  system runs fine  back in single  mode -
    Swapped processors;  repeated UPTOMP;  same result.   After coping
    HAL.DLL  and  the  other  files  replaced  by  UPTOMP from another
    working NT4/SP5 box running  dual processors and over-wrote  those
    files in the "problem"  PC's \system32 directory.   Multiprocessor
    now showing two and running like a champ.

SOLUTION

    Sounds  like  the  new  UPTOMP  has  the  same  problems (bug) the
    SP3/early SP4 ver. had.   The problem: the SETUP.LOG file  is used
    to ID the files installed by  the service pack, and it is  written
    during  the  initial  installation.   When  you  apply  a  SP, the
    original  single  proc  files  are  reinstalled over the MPS files
    installed during the upgrade.  Here's the fix (Note: the following
    is  extracted  from  Q168132  for  a  Non-Compaq Intel machine and
    edited. See the full article for ALPHA, Compaq, etc).

    By modifying the %SystemRoot%\Repair\Setup.log file, you can  tell
    the  service  pack   Update.exe  program  to   load  the   correct
    multiprocessor components (thus taking you back to  multiprocessor
    support and at  the same time  ensuring that future  service packs
    install  correctly).   Modify  the  entries  under   [Files.WinNT]
    section (of %SystemRoot%\Repair\Setup.log) to the following:

        \<%SystemRoot%>\System32\Ntoskrnl.exe = "NTKRNLMP.EXE","e76ab"
        \<%SystemRoot%>\System32\Kernel32.DLL = "KERNEL32.DLL","5b7f8"
        \<%SystemRoot%>\System32\Winsrv.DLL = "WINSRV.DLL","37b4e"
        \<%SystemRoot%>\System32\Ntdll.DLL = "NTDLL.DLL","59c19"
        \<%SystemRoot%>\System32\win32k.sys = "WIN32K.SYS","132603"

    Then select the appropriate HAL and modify the line:

        \<%SystemRoot%>\System32\hal.DLL = "HALMPS.DLL","1a01c"

    Save the modified Setup.log to the %SystemRoot%\Repair directory.