Load Control Info – Allows the specified Burn-in
configuration file to be loaded. Enter the full path, drive
and directory location, as well as the filename.
Save Control Info – Allows the specified Burn-in
configuration file to be saved. Enter the full path, drive
and directory location, as well as the filename. The configuration
filename must be BURNIN.INI and must be in the same directory
as the Burn-in executable file.
Set Program Defaults – Sets the configuration
options to a default setting.
Test Time Hours – Allows setting of the diagnostic
run time in hours (maximum of 99). In order for Burn-in to
use the run time, the Program Loop Count must be set to 0
(zero).
Test Time Minutes – Allows setting the diagnostic
run time in minutes (maximum 99). In order for Burn-in to
use the run time, the Program Loop Count must be set to 0
(zero).
Use DMI Serial Number – Burn-in normally saves
the report with the name BURNIN.RPT, however the report filename
can use the last 8 digits of the serial number found in the
DMI. So the report filename would then be 12345678.RPT.
BURNIN.SLT File Location – Set the drive and
directory location of the Burn-in configuration file. Burn-in
will load the test selection file from the specified path.
SEND.TXT File Location – Set the drive and directory
location of the serial / model number file. Burn-in will load
the serial / model number file from the specified path.
Report File Location – Set the drive and directory
location of the Burn-in test results report. Burn-in will
save the report file to the specified path.
Compare File Location – Set the drive and directory
location of the system comparison file (CTEST.BIN). Burn-in
will load the comparison file from the specified path.
Append Report File? – By default, Burn-in will
always create a new file for the report (BURNIN.RPT). However,
Burn-in can append the report to the end of an existing report
file.
Exit On Completion? – By default, Burn-in will
not exit the diagnostics upon completion. The program will
continue to display the testing results on the screen and
the user will need to either power off the system or press
<CTRL><ALT><DEL> to reset the system. However,
it maybe beneficial to have the diagnostics end and return
to the calling batch file. Burn-in will exit and pass to the
calling batch file a 1(one) signifying a failure or a 0 (zero)
for all testing passed.
Create Database File? – Enable Burn-in to create
a coma-delimited database file of the report. The filename
for the database is BURNmmdd.DB. Where mm is the month and
dd is the date from the CMOS.
Program Loop Count – Set the number of loops
the diagnostics should perform (maximum 999). If this value
is set to a value other than 0 (zero), Burn-in will run the
selected tests for the specified number of loops. When the
value is set to 0, Burn-in will run for the time set in the
Run Time Hours and Run Time Minutes.
Abort On Error? – Exit the diagnostics on the
first error detected. Normally, Burn-in logs up to the first
16 errors detected. However, if you prefer to exit the diagnostics
as soon as an error has been detected, set this value to Yes.
Flash CMOS From File? – Flash the CMOS with data
contained in the RTCDATA.TXT file.
Allow HD Write Tests? – Configure Burn-in so
NO destructive tests can be accidentally performed on the
installed hard disk drives. To ensure no write testing is
performed on the hard disk drives, set this value to No.
Use Last Test Info? – Configure Burn-in to utilize
the last test feature which gives the program the ability
to restore the complete test data if power is lost then reapplied
to a system
Use Power Cycle Time? – Use Power Cycle time
configuration instead of loop counts. Burn-in has the ability
to cycle the power off and back on with certain systems. The
power cycle testing can be configured to cycle the power off/on
per loop counts or per time.
Display Report? – Display the report on the screen
at the completion of the diagnostics.
Eject CD? – Eject all CD trays at the completion
of the diagnostics. This helps to prevent the test CDs from
being left in the systems after testing.
