Server can't startup after installing SP6a

Archived from groups: microsoft.public.windowsnt.misc (More info?)

This is most likely a hardware issue and you should contact IBM or go into
the BIOS/CMOS and have a look for keyboard lock settings or something to
that affect. This doesn't even look like the Operating system has begun to
come up yet so this is probably not related at all to the SP6 install and
was just waiting for a reboot to come up with this error.

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server


"Gerald" <anonymous@discussions.microsoft.com> wrote in message
news:6F3AB260-CE51-4063-9B32-9462E24FB6FD@microsoft.com...
> Hi,
>
> My customer is running Windows NT Server 4.0 SP6 on an IBM Netfinity
Server
> with FACT Accounting Software. They upgraded to SP6a and upon restarting,
> the following message is received.
>
> Quote
> The RF-ID Tag has changed.
> System-security - Keyboard is locked.
>
> PXE-M04: Initializing network book device using interrupt 18h.....
>
> Adaptec AHA-2940 Ultra/Ultra W SCSI BIOS v1.3S8
> ...Recognising SCSI HDD info
> ...
> ...
> ...
> ...
> ...
> SCSI BIOS Installed Successfully!
>
> System-security - Keyboard is Unlocked.
> 176 The System has been tampered with.
> Turn power to your system OFF and then ON.
> Your system is now locked.
> Unquote
>
> Please advise me how I can resolve this issue.
>
>
> Thanks and best regards,
> Gerald Yeo