Problem upgrading from SP5 to SP6a

[PerryMc]

We have a Compaq Proliant 5500 server running Windows NT4 SP5 that I wish to upgrade to SP6a which I have downloaded from

http://www.microsoft.com.

The upgrade appears to go fine, but SP6a only seems to see 1 processor, while SP5 recognises that there are 2 processors, i.e. at the blue screen during reboot.

With SP6a, this causes the server to freeze at the 'Press alt-cntl-del' screen. I have to power off and on, then use HAL recovery mode to bring it up on 1 processor so that SP6a will allow me on to deinstall it.

I was thinking I could go into System on the control panel and change it to 2 processors there for this server and then do a restart.

However, I have another similar server to upgrade to SP6a, that also has 2 processors but doesn't have a HAL recovery mode set up.

Anybody run into this when they were upgrading?

Any thoughts or ideas, or even better, solutions, would be much appreciated.

Smile anyway,
Perry.

 

[datadan]

comcrap has some proprietary software you may need to use:

Download and apply new Compaq Server Managerment software 2.22a (or later) NTSSD.exe

You may then have some trouble with
Error: CAPI: The Installer could not find the signature file

This is an IE error: check out
Suggested fix: Q179636 on microsoft's knowledge base.

Good luck,

 

[PerryMc]

The NTSSD.exe I found on

http://www.hp.com

using their search facility was for Windows NT3.51. A search on Compaq Server Management did lead me to a download of Proliant Support Pack version 6.30A, so I installed that.

Had a look at Q179636, the file it mentions, winhlp32.exe is already in the right place on our server so doesn't seem to be a problem.

Unfortunately, it hasn't made any difference. SP5 still recognises 2 processors, I upgrade to SP6a and it only sees 1. I used HAL recovery mode to start up Windows NT4 SP6 on 1 processor, then changed it to 2 processors in control panel/system/environment and restarted the system, but it still changed back to 1 processor displayed on the blue startup screen and hung on me at the alt-ctrl-del to logon screen.

Thanks for the thoughts anyway, Datadan.

Smile anyway,
Perry.