# Selecting Test Preferences |

Test Preference Windows The Test Preference Windows allow the detailed configuration of each test type, such as the CPU and disk tests, to be set. The test configuration Windows are described in the Test preference sections shown below:
• | 2D Graphics and video memory tests
• | 3D Graphics test
• | CPU test
• | Disk test
• | Error handling
• | Logging
• | Management Console
• | Network, Bluetooth and Advanced network tests
• | Optical Drive test
• | Plug-in test
• | Parallel port test
• | Post-test actions
• | Pre-test actions
• | Printer test
• | RAM test
• | Serial port test
• | Sound test
• | Tape test
• | Temperature and Battery monitoring
• | USB test
• | Video playback test
Preferences editor The test preference Windows allow the configuration for the current system or similar systems. In general it does not provide the option to configure the testing of hardware that does not exist on the system being used and it will validate the user settings (e.g. that input test files exist). Some users need to create test configuration files for a large variety of systems including for hardware that does not exist on the system being used. BurnInTest can be started in a special 'Preferences editor' mode to allow the creation of BurnInTest configuration files for hardware that does not exist on the current system (e.g. configure a hard disk to be tested that is not on the system being used). Specifically, when specifying the command line parameter "-Y":
• | CPU instructions not supported on the current system can be selected for testing;
• | All HDD drive letters [A..Z] and physical disk numbers [0..50] are displayed and can be configured for testing;
• | All optical drive letters [A..Z] are displayed in Preferences->Optical drives and can be configured for testing;
• | Files are not validated for existence: Plugin test files, sound test files, log files, video playback files and pre/ post test files.
When BurnInTest is run in the Preferences editor mode, tests configurations can be created and different configuration files saved as required. BurnInTest tests may not be run when BurnInTest is run in this mode. Scripting preferences Many of the test preferences can also be configured using BurnInTest scripting commands.