Hardware ID is used to identifed a particular workstation. This can be used to control what services/application are allowed to be run on the particular workstation.
The problem.
With "unqualified" PC's, CTOS III may report a Hardware ID, when
there isn't a Hardware ID device fitted.
I believe that CTOS is incorrectly reading the BIOS, and misidentifying "something" as a Hardware ID.
Writing a Hardware ID in these circumstances may well cause the BIOS to be corrupted. This was the case with one SG machine and a particular level of CTOS.
The fix?
As the problem appears with non-supported systems (ie. systems
not sold as CTOS machine by Unisys), it would be unreasonable to expect
Unisys to fix the problem.
The workaround
Remove the commands "Read Hardware ID" "Write Hardware ID" from
your command files.
Remove the RHWid.Run , WHWid.Run files from your system.
Disclaimer
This article is provided as is without any express or implied warranties.
While every effort has been taken to ensure accuracy of the information
contained in this article, the author assumes no responsibility for errors
or omissions, or for damages resulting from the use of the information
contained herein.
Dale 'Cat' Robinson - catfromdarwin@geocities.com
2 April 1999