MicroScope Burn-in Version 2005 Manual
About Burn-in:
The testing routines in the Burn-in diagnostics are based on the
best-selling MicroScope software that has been the industry leader
since its introduction in 1990. Whereas MicroScope is designed to
troubleshoot individual systems either onsite or in a repair depot,
Burn-in provides an interface to use the same proven tests in batch
mode in a factory setting, to run a specified number of passes or
for a set amount of elapsed time, without active supervision.
Machines can be evaluated in bulk with a pre-determined selection
of tests, and can even be tested prior to the installation of keyboards
and monitors. There is a great deal of flexibility in setting the
test configuration and control parameters, and in choosing reporting
functions. As in MicroScope, Burn-in comes with our own proprietary
bootable operating system that allows access to the hardware at
a very fundamental level, without intervention of an operating system
not written for diagnostic purposes. This gives the most accurate
possible assessment of the CPU and peripherals. However, Burn-in
can also be run under DOS and higher level operating systems to
allow testing with software drivers in place, and for network reporting
capability.
Setup Burn-in:
Burn-in’s setup program is SetupBI. This program can be executed
from the Burn-in bootable disk’s main menu or from a DOS command
prompt. The setup program contains two main configuration areas.
The first is "Program Control", which is used to configure
how the Burn-in diagnostics run. The items in this menu are listed
below:
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.
The second main configuration menu for the Burn-in Setup program
is "Test Selection". The test selection is accomplished
through the setting of the test sequence numbers. Highlight the
item and press the <SpaceBar> to select the next test sequence
number. Press the <+> and <-> keys to increment and
decrement the sequence number. The items in this menu are list below:
Load Batch Tests - Allows the specified Burn-in test
selection file to be loaded. Enter the full path, drive and
directory location, as well as the filename.
Save Batch Tests - Allows the specified Burn-in test
selection file to be saved. Enter the full path, the drive and
directory location, as well as the filename.
Clear Batch Tests – Resets all the test selection
sequence number to 0 (zero).
Select All Tests – Selects all tests and numbers
the tests sequentially, even the destructive floppy and fixed
disk tests are selected. Once this option is selected, the tests
can manually be deselected or re-sequenced.
Display Settings – Displays the selected tests
in sequence order.
SystemBoard Tests – Selects the system board suite
of tests.
Memory Tests…
Base Memory – Selects the Base Memory (below
640K) suite of tests.
Cache Memory...
Pattern Test – Selects the Patterns suite
of tests.
Pseudo-Random – Selects the Pseudo Random
Test algorithm.
Xor'ed Address – Selects the Xor Address
Test algorithm.
Short Bit Test – Selects the short version
of the Bit Test algorithm.
Short Grid Test – Selects the short version
of the Grid Test algorithm.
Full Bit Test – Selects the complete version
of the Bit Test algorithm.
Full Grid Test – Selects the complete version
of the Grid Test algorithm.
Extended Memory...
512Mb Maximum Memory – Set the maximum
amount of Extended Memory to test.
Pattern Test – Selects the Pattern Tests
listed below:
Walking 1's – Select the Walking 1’s
Test algorithm.
Inv. Walking 1's – Selects the Inverse
Walking 1’s Test algorithm.
Checkerboard – Selects the Checkerboard
Test algorithm.
Pseudo-Random – Selects the Pseudo Random
Test algorithm.
Xor'ed Address – Selects the Xor Address
Test algorithm.
Short Bit Test – Selects the short version
of the Bit Test algorithm.
Short Grid Test – Selects the short version
of the Grid Test algorithm.
Full Bit Test – Selects the complete version
of the Bit Test algorithm.
Full Grid Test – Selects the complete version
of the Grid Test algorithm.
Quick Test – Selects the quick version
of the Pattern Test algorithms.
Floppy Disk Tests…
Read Test... – Selects the Floppy Read Test
for all the installed floppy drives in the system.
Tracks – Enter the number of tracks to
test on the floppy drives. Enter a 0 (zero) to select
all.
Increment – Enter the track increment number.
This number allows the selection of testing every track
or every second track, every third track, etc.
Seek Test... – Selects the Floppy Seek Test
for all the installed floppy drives in the system. The Track
and Increment values are entered for the test too, has described
in the Floppy Read test above.
Write Test... – Selects the Floppy Write Test
for all the installed floppy drives in the system. The Track
and Increment values are entered for the test too, has described
in the Floppy Read test above.
Safe Write... – Selects the Floppy Disk Safe
Write Test for all the installed floppy drives in the system.
The Track and Increment values are entered for the test
too, has described in the Floppy Read test above.
Fixed Disk Tests…
Read Test... – Selects the Fixed Disk Read
Test for all the installed fixed disks in the system.
Cylinders – Enter the number of cylinders
to test on the fixed disk drives. Enter a 0 (zero) to
select all.
Increment – Enter the cylinder increment
number. This number allows the selection of testing
every cylinder or every second cylinder, every third
cylinder, etc.
Seek Test... – Selects the Fixed Disk Seek
Test for all the installed fixed disks in the system. The
Cylinder and Increment values are entered for the test too,
has described in the Fixed Disk Read test above.
Write Test... – Selects the Fixed Disk Write
Test for all the installed fixed disks in the system. The
Cylinder and Increment values are entered for the test too,
has described in the Fixed Disk Read test above.
Safe Write... – Selects the Fixed Disk Safe
Write Test for all the installed fixed disks in the system.
The Cylinder and Increment values are entered for the test
too, has described in the Fixed Disk Read test above.
Format Test... – Selects the Fixed Disk Format
Test for all the installed fixed disks in the system. The
Cylinder and Increment values are entered for the test too,
has described in the Fixed Disk Read test above.
IDE/SATA Tests…
Seek Test... – Selects the IDE/SATA Disk Seek
Test for all the installed IDE/SATA disks in the system.
Sectors – Enter the number of sectors to
test on the drives. Enter a 0 (zero) to select all.
Increment – Enter the sector increment
number. This number allows the selection of testing
every sector or every second sector, every third sector,
etc.
Read Test... – Selects the IDE/SATA Disk Read
Test for all the installed IDE/SATA disks in the system.
Sectors – Enter the number of sectors to
test on the drives. Enter a 0 (zero) to select all.
Increment – Enter the sector increment
number. This number allows the selection of testing
every sector or every second sector, every third sector,
etc.
per Access – Enter the number of sectors
to access with each Read. Depending on the size of each
sector (in bytes) the maximum sectors per access will
be adjusted automatically.
Write Test... – Selects the IDE/SATA Disk Write
Test for all the installed IDE/SATA disks in the system.
The Sector Increment and Per Access values are entered for
the test too, has described in the IDE/SATA Read test above.
SCSI Tests… - Aspi drivers are required to access
all SCSI devices other than the first two installed fixed disk
drives.
Seek Test... – Selects the SCSI Disk Seek Test
for all the installed SCSI disks in the system.
Sectors – Enter the number of sectors to
test on the SCSI disk drives. Enter a 0 (zero) to select
all.
Increment – Enter the sector increment
number. This number allows the selection of testing
every sector or every second sector, every third sector,
etc.
Read Test... – Selects the SCSI Disk Read Test
for all the installed SCSI disks in the system.
Sectors – Enter the number of sectors to
test on the SCSI disk drives. Enter a 0 (zero) to select
all.
Increment – Enter the sector increment
number. This number allows the selection of testing
every sector or every second sector, every third sector,
etc.
per Access – Enter the number of sectors
to access with each Read. Depending on the size of each
sector (in bytes) the maximum sectors per access will
be adjusted automatically.
Write Test... – Selects the SCSI Disk Write
Test for all the installed SCSI disks in the system. The
Sector Increment and Per Access values are entered for the
test too, has described in the Aspi Read test above.
CDROM Drive Tests…
Read Test... – Selects the CDROM Read Test
for all the installed CDROM drives in the system.
Sectors – Enter the number of sectors to
test on the CDROM drives. Enter a 0 (zero) to select
all.
Increment – Enter the sector increment
number. This number allows the selection of testing
every sector or every second sector, every third sector,
etc.
per Access – Enter the number of sectors
to access with each Read. Depending on the size of each
sector (in bytes) the maximum sectors per access will
be adjusted automatically.
Seek Test... – Selects the CDROM Seek Test
for all the installed CDROM drives in the system.
Sectors – Enter the number of sectors to
test on the CDROM drives. Enter a 0 (zero) to select
all.
Increment – Enter the sector increment
number. This number allows the selection of testing
every sector or every second sector, every third sector,
etc.
Serial Port Tests…
Internal Port 0 Test – Selects the Internal
loopback connections for testing Port 0.
Internal Port 1 Test – Selects the Internal
loopback connections for testing Port 1.
Internal Port 2 Test – Selects the Internal
loopback connections for testing Port 2.
Internal Port 3 Test – Selects the Internal
loopback connections for testing Port 3.
External Port 0 Test – Selects the External
loopback connections for testing Port 0.
External Port 1 Test – Selects the External
loopback connections for testing Port 1.
External Port 2 Test – Selects the External
loopback connections for testing Port 2.
External Port 3 Test – Selects the External
loopback connections for testing Port 3.
Parallel Port Tests…
Internal Port 0 Test – Selects the Internal
loopback connections for testing Port 0.
Internal Port 1 Test – Selects the Internal
loopback connections for testing Port 1.
Internal Port 2 Test – Selects the Internal
loopback connections for testing Port 2.
External Port 0 Test – Selects the External
loopback connections for testing Port 0.
External Port 1 Test – Selects the External
loopback connections for testing Port 1.
External Port 1 Test – Selects the External
loopback connections for testing Port 2.
Video Memory Tests…
Page Memory Test – Selects the Video Page
Memory tests. This tests the video memory using Interrupt
10h, which accesses the memory in blocks or pages.
Linear Memory Test – Selects the Video Linear
Memory tests. This tests the video memory in one Linear
block of Protected Mode memory.
DAC Test – Selects the Digital to Analog Converter
tests.
Other Tests…
Sound Card Test – Selects the Sound Card tests
for SoundBlaster and Adlib compatible sounds cards as well
as AC’97 sound cards.
NIC Card Test – Selects the Network Interface
Cards tests for the supported NIC cards.
USB Controller Test – Selects the USB Controller
test.
Flash CMOS – Flashes the CMOS with the data
contained in the RTCDATA.TXT file.
Compare System – Compares the system components
with the components listed in the CTEST.BIN file.
APM Power Cycling... – Selects the Power Cycling
which can turn the system power off then back on in the
intervals listed below.
Test every XX Loops – Selects the number
of loop counts for the power cycling event.
Turn ON in XX Minutes – Set the amount
of time before the system turns itself back on.
Once the Burn-in configuration files have been created, the diskette
is ready for testing.
Using the Serial / Model Number entry
The Serial/Model Number usage was originally a request from one
of our Burn-in OEM Customers. Their production line consisted of
a roller conveyor belt where the systems were bar code scanned at
the beginning of the line. The scanned in serial number and model
number were formatted into a file on the network named SEND.TXT.
This file consisted of two columns of numbers. The first column
contains the Serial Number and the second is the Model Number. The
two numbers are separated with a space.
As the systems continue to get scanned, the serial and model numbers
are added to the send.txt file. The first line of numbers is for
the first system scanned. The second line of numbers is for the
second system and so on. The systems are then setup for testing,
including installing all the loopback connectors. This customer
would utilize a parallel port network interface to connect to the
network through its own DOS drivers.
The Burn-in diagnostic diskettes were pre-configured with the appropriate
autoexec.bat and config.sys files to connect to the network and
map network drives. The first system scanned was at test station
number 1 with Burn-in diagnostic diskette number 1. The second system
was at test station number 2 with Burn-in diagnostic diskette number
2 and so on.
When the autoexec.bat file executes Burn-in, a number is passed
into the program via the command line options for the program. The
autoexec.bat line to execute Burn-in would look like this:
burnin.exe 1
The command line option number tells Burn-in which line in the
send.txt file contains the serial and model numbers for the system
being tested. While Burn-in is determining the system components,
the serial and model numbers are loaded from the send.txt according
to the value passed into Burn-in on the command line. The serial
and model numbers are included in the report that Burn-in generates.
Also, the first 11 digits of the serial number are used for the
Burn-in report name. This allows all of the Burn-in reports to be
saved to a network directory.
Using the Comparison feature
The Comparison Feature gives the ability to verify the correct
components are installed in the systems being tested. Using MicroScope,
the Comparison file is created (CTEST.BIN) for the specific model
of system to be tested. This compare file saves information about
the motherboard, CPU and NPU, amount of memory installed, floppy
drive numbers and sizes, fixed disk drive sizes and speeds, video
card information, number of serial and parallel ports, network cards,
sound card and keyboard interface type. This information is then
used as a comparison for the entire line for that specific model
number.
The comparison file can be edited, using a standard text file editor,
to include additional options for the comparison. If a "!!"
(double exclamation point) is added to the beginning of a line,
then when that item is compared, the test ignores the results. This
is useful if a model number build may include one of two hard drives
that have a different cylinder, head and sector count but the same
physical size. This would normally create a failure because the
drives do not match exactly, but this may be acceptable for this
build. The other option is a "||" (double pipe). This
option added to a line indicates "or". This is useful
if for this model number the processor is no longer available in
a specific speed, so the next processor is used. Then the comparison
would look at that component and if the processor speed is one or
the other then the component is all right.
A quick look at the Burn-in Report file
The Burn-in report is broken down into a few different sections.
The first section consists of a header with Burn-in program name
and version number of the program. The date and time when the report
was generated is included with the header too. If the serial number
and model number is loaded from the SEND.TXT file then those numbers
are also included.
The next section of the report contains all the system specific
information. Information on the motherboard, processor, memory,
video, floppy, fixed disk, Atapi and Aspi devices, CD-ROMs, serial
and parallel ports, network cards, sound cards and other miscellaneous
information is all included in this section.
The third section is a listing of the Burn-in test selections,
from the burnin.slt file. All the test sequence numbers and additional
parameters being used for the current set of tests is displayed.
The next section contains all the information from the burnin.ini
file. This is the information about how Burn-in is configured, where
some of the files are located and for how long the tests will run.
The next section is a summary of the Burn-in diagnostics. This
includes the test results, either passed or failed, the number of
loops the diagnostics performed, the average time for a single loop,
start and end times and the total test time. This is followed by
a list of all the tests performed in the order that they were performed.
This also includes if the individual tests passed or failed and
the average time required for each test. The last section is a list
of all the failures the diagnostics found and recorded, if any.
Using the last test feature
The Last Test feature will restore all the testing parameters,
errors and test time if power is turned off then back on during
testing. This is useful if the system being testing is in a temperature
chamber and the system is controlled by an external power source.
When running a system in a temperature chamber the system will be
powered for a given period of time and off for a given period of
time. This on/off cycle will continue for a set time. The Last Test
feature is designed to function in this environment. As each test
is completed, the diagnostic results, test time and testing data
is all stored in a file. Then, if power is lost to the system, the
next time Burn-in is executed, the diagnostics continue right where
it left off. The time is updated and the testing continues.
Call
us now on +44 (0)1342 301 001
|
