We have been using BIT Pro for over two years. I have it configured to autorun with a specific bitconfig file depending on the customer. Recently a customer purchased new HP Probook 6555b laptops. Even though the SSE4a test is not selected in that customers bitconfig, BIT seems to reenable it following the system information collection. This is causing failures and now requires our technicians to stop the test and adjust the preferences for CPU testing before restarting the test.
Has this been patched in a more recent build than the one we are using (V6.0 Pro 1007)?
If not, is there some other way to avoid this?
Thanks,
Scott
Has this been patched in a more recent build than the one we are using (V6.0 Pro 1007)?
If not, is there some other way to avoid this?
Thanks,
Scott
Comment