BIT v6.0 v.s BIT v7.1 ?

[Bohan]

Chipset : Haswell ULT
Super I/O : NCT6102
Number of COM : Only one COM
OS : Windows 7 32 bit


When using BIT to verify our system, we encountered COM port issue only on v7.1. We want to know which version is correct and how to explain this difference to our customer ?

[Ian (PassMark)]

>When using BIT to verify our system, we encountered COM port issue only on v7.1.

This error occurs when the number of bytes that were attempted to be sent to the COM port did not match the actual number of bytes sent to the COM port. It would appear that BurnInTest was unable to send 1 block of data (100 bytes) to the COM port. It is unclear why this occurred.
After the error, the COM port is closed and re-opened in software, and it may be that the COM port test continued successfully after that (and hence you only got the one error). Having a level 2 trace log may help understand the problem better.


>We want to know which version is correct and how to explain this difference to our customer ?

I always advise customers to use the latest version and build of BurnInTest as this has the known issues corrected and we are better able to support it.

In saying this, the BurnInTest serial port test in this respect is the same in both BurnInTest 6.0 and 7.1. The main change with the serial port test between V6.0 and V7.1 is a change specifically for when running on WinPE, which you are not.

This error occurs once in over 100 hours, and as such I expect that the problem could have just as well occurred in either version of BurnInTest if you ran the tests long enough or for more iterations.

[ACHU]

Having a level 2 trace log may help understand the problem better.

=> How to get level 2 trace log?

[Ian (PassMark)]

Preferences->Logging, Select Trace file detail level = Activity trace 2 (text).