Release Notes

a bluescreen may appear. 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.
* For Precision T3400, T5400, T7400, and OptiPlex 755, if only the
system password is set and the setup password is not set, some of
the options do not work. It is recommended that you either remove the
system password or set the setup password too.
* For OptiPlex 960, bootorder output generated using log file may
contain non-alpha-numeric characters. You may ignore such characters.
* Following are the known issues on OptiPlex 740:
- the floppy option does not work.
- the usbemu option does not work.
- asset, minsizeofcontigmem, bioscharacteristics,
and completion code may not work.
* On Precision T3500, CCTK does not report the correct value of the
turbomode option. Though the option is enabled, CCTK reports it
as disabled.
* On Latitude XT2, the busratio option does not set the
argument, max.
* 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.”
You can ignore the message and can proceed with the installation
of other rpms.
* CCTK does not allow you to set or change BIOS passwords to contain
special characters. If your system’s BIOS supports passwords
containing special characters and you want to set or change
a BIOS password to contain special characters, do it using
the BIOS.
* CCTK log file does not capture information related to the
sub options of commands.
* On OptiPlex 760, CCTK may allow to set setup and system passwords
with number of characters lesser than what BIOS mandates.
* On Precision M4400, the bootorder option may not display
the correct number of boot devices.
* On OptiPlex 360, CCTK may not set the wakeonlan option to disable.
* 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.
######################################################################