Release Notes

Issue 8:
Description: When you execute cctk.exe on Microsoft Windows XP Professional or Microsoft Windows XP
Professional SP2, a blue screen may appear.
Resolution: This is a known Microsoft issue and Microsoft provides a fix for this. For more information, refer to
http://www:support.microsoft.com/kb/921337.
Issue 9:
Description: Following are the known issues on OptiPlex 740:
• floppy option does not work.
• usbemu option does not work.
• asset, minsizeofcontigmem, bioscharacteristics, and completioncode options may not work.
Issue 10:
Description: On Dell Precision workstation T3500, CCTK does not report the correct value of the turbomode
option. Though the option is enabled, CCTK reports it as disabled.
Issue 11:
Description: On Latitude XT2, the busratio option does not set the argument max.
Issue 12:
Description: When you install CCTK on a Linux system, after installing the omilcore rpm, the following
message is displayed: "To start all installed services without a reboot, enter the following command:
srvadmin-services.sh start".
Resolution: You can ignore the message and can proceed with the installation of other rpms.
Issue 13:
Description: CCTK log file does not capture information related to the sub options of commands.
Issue 14:
Description: On OptiPlex 760, CCTK may allow to set setup and system passwords with number of
characters lesser than what BIOS mandates.
Resolution: On Dell Precision Workstation M4400, the bootorder option may not display the correct number of
boot devices.
Issue 15:
Description: On OptiPlex 760, if system password is set, BIOS may not allow to set a setup password. CCTK
does not provide an error message in such a scenario.
Issue 16:
Description: When you upgrade CCTK 1.1 to 1.2.1, CCTK contains the previous version of User's Guide
along with a link to 1.2.1 User's Guide.
Issue 17:
Description: CCTK does not take care of the dependencies among the various TPM PPI tokens. Example: It
is possible to change the TPM PPI ACPI token through CCTK even when TPM is not On. However, there is no
negative impact due to this on the BIOS.