BITCFG files will only execute from My Documents\Passmark\Burn-in

[mbtester]

I am in proces of upgrading my site license from 4.0 to 5.2 and bought an initial single copy to evaluate before doing so. I installed on my master drive and then copied the new bit.exe application to my test subdirectory path as I had always done in the past. I can use previous test scripts to launch BIT.exe from it's old paths but it will not utilize the .bitcfg files except from documents and settings\......\my documents\passmark\burnin directory. Also when I modify and save a new BITCFG file it will only save to this location. This really causes me issues with all of my test sequences and master test drives. It used to launch or save from where ever it was called. Why was this changed and is there a way around this? Is this by design or an OS bug? I use WinXP Pro SP2a

Thanks

[JamesBulpin]

This worked for me on an upgrade from 5.1 to 5.2: I had to give the full path of the bitcfg file to the -c paramater instead of just the filename and running from the directory containing that file. Without this it compained of not finding its config under My Documents. With the full path I can still run from anywhere.

[mbtester]

Many thanks, I will try this. I have at least 50+ custom script sequences. This could save me alot of work

regards
mbtester

[eDuk]

This worked for me on an upgrade from 5.1 to 5.2: I had to give the full path of the bitcfg file to the -c paramater instead of just the filename and running from the directory containing that file. Without this it compained of not finding its config under My Documents. With the full path I can still run from anywhere.

How do you give the full path of the config file to the c parameter? You'll have to bear with me i think im a little lost.

[JamesBulpin]

e.g:

bit.exe -C c:\any\dir\you\like\bit.bitcfg -R

[Ian (PassMark)]

To specifiythe full path of the config file to the c parameter, from the command line (or bat file...):
bit.exe /c "C:\Program Files\BurnInTest\MyBigTest.bitcfg"

Often this is also specified with /r to start the tests automatically.

If no path is specified then in V5.2 (on W2000 and above, and when not run with a key.dat file) then BurnInTest will attempt to load the config file from the User's personal directory:
eg. bit.exe /c MyBigTest.bitcfg
would load from:
C:\Documents and Settings\<username>\My Documents\PassMark\BurnInTest\MyBigTest.bitcfg

Regards,
Ian (PassMark)

[Terra]

To specifiy the full path is possible if you start the BIT from the harddisk.
But I start it from a USB Stick . Than the device drive is changing at different computers.

[Ian (PassMark)]

We have an item on our candidate feature list to allow for this type of specification. For now, with V5.2 of BurnInTest if you run from a USB drive, using a a key.dat file (see our FAQ) with your license in it, then BurnInTest will check the BurnInTest directory on the USB drive for configuration files. So, in this case, you just need to put your config files in the same directory as BurnInTest.

eg. If bit.exe, MyBigTest.bitcfg and a valid key.dat are on a USB, CD, Firewire etc drive in a directory, say, <drive letter>:/BurnInTest
To specifiy the config file with the c parameter, from the command line (or bat file...) you just need to use:
bit.exe /c "MyBigTest.bitcfg"

Regards,
Ian (PassMark)

[Terra]

That´s what I have already done. But the BIT will always load the bitcfg file of the documents folder even all necessary files are in one separat folder and I start the Bit with "C" parameter. I´m using my key.dat of the BurnIn Test 5.1 version. Do I need a new key for the 5.2 version?

[Ian (PassMark)]

OK. I now see the problem. It is not a problem with your license key. We will add a command line parameter (/p) to to allow the BurnInTest directory to be used rather than the User's personal directory. This will be useful when running BurnInTest from a USB drive for example.

This will be included in the Public release of BurnInTest V5.3, planned for release late next week.

Regards,
Ian (PassMark)

[Mats_Captech]

To specifiy the full path is possible if you start the BIT from the harddisk.
But I start it from a USB Stick . Than the device drive is changing at different computers.
OT: Which OS are you running on your USB stick?

We're investigating the possibility of testing machines that do not have harddrives, so I wonder whether BIT will run on e.g. Windows PE.

~|:^)
// Mats Oscarsson

[Ian (PassMark)]

BurnInTest has been tested and documented with BartPE (Bart Pre-install environment). This will allow testing on a system with no Operating System (some limitations - see documentation). I am not sure if we have tested on a system without a hard disk. You can download our documentation from:
http://www.passmark.com/ftp/bit_bartpe_plugin_v1.pdf

The BurnInTest BartPE plugin can be downloaded from:
http://www.passmark.com/ftp/bit_bartpe_plugin.zip

While we have not tested with Windows PE, we understand some of our customers are using BurnInTest with Windows PE.

Regards,
Ian (PassMark)

[FSC]

OK. I now see the problem. It is not a problem with your license key. We will add a command line parameter (/p) to to allow the BurnInTest directory to be used rather than the User's personal directory. This will be useful when running BurnInTest from a USB drive for example.

This will be included in the Public release of BurnInTest V5.3, planned for release late next week.

Regards,
Ian (PassMark)

im running bit from usb-stick, too. since switch from 5.1 to 5.2 the config files wont be found in personal folders.

please inlcude getting bitcfgs from same folder bit is situated on stick.

its urgend.

rgs
fsc

[Ian (PassMark)]

OK. If it's urgent, then please email us (help [at] passmark [dot] com) and we will send you a pre-release shortly.

Regards (Ian)

[CJ]

When/where can we download BurnIn test 5.3? :)

We use a USB key / CD and would like the config file to run from the burnin test folder, plus have Vista compatibility.

[Ian (PassMark)]

It is not yet available for general release. Currently planned for general release around 23 March 2007. If it's urgent, then please email us (help [at] passmark [dot] com) and we will send you a pre-release shortly.

Regards
Ian (PassMark)

[CJ]

There's no rush, I can wait a week.

Could you possible add another option to the command line to mute the main volume in Windows? (In Vista specifically)

i.e. "bit.exe /mute"

[Jito463]

I am so glad I found this post. I've been having this problem with the x64 version, where it would ALWAYS search the personal user directories for the bitcfg, but would never use the one in the current directory until I stopped the test and then loaded the correct config. This finally fixed it. I must have overlooked this in the manual last time I perused it.

[malte]

I have a similar problem, I run bit.exe with the /p parameter.
By the way instead of using full path you can use ".\config.bitcfg"

.\ is normally interpreted as full path of current directory.

We're currently using BurnIn v5.3 pro Build 1004, but no matter what option I set, it always creates a "\Passmark\BurnIn" folder in the "my documents" folder an places a lastused.bitcfg when using the key.dat version I expect it doesn't create anything on the unit I test.

I have tried to update to v5.3 Build 1011, but in that Build I can not use a pre-test application like ".\runthis.cmd" on Build 1004 this is working.

[Ian (PassMark)]

We have found a problem with the translation of "./" in filenames and will correct this in the next release of BurnInTest (date TBD).

We could not find a reason why the LastUsed.bitcfg file would be created in the "My Documents\PassMark\BurnInTest" folder when the "-p" command line parameter is specified. Can you send your configuration file and information about the mechanism you use to start BurnInTest (exact command line, or batch file, shortcut infromation including working directory etc). You can email this to help [at] passmark [dot] com

Thanks.
Ian

[malte]

You've got mail :) a copy of it, here. (w/o attachments)

Hello Ian,

Find attached all my configuration files.
The last time I tried with stresstest.bitcfg

I can not post the whole Batch file, but I think one of the parts that starts BIT should be OK.


~~~/snip/~~~~
:burnin
if exist %_sn%.log del %_sn%.log
echo SETLOG "%_sn%.log" >> tmp-script.txt
echo SETMACHINETYPE "%_model%" >> tmp-script.txt
echo SETSERIAL "%_sn%" >> tmp-script.txt
echo SETNOTES "Assembly order: %_fa% Tester ID: %_test%" >> tmp-script.txt
type tmp-script.txt >> bit-script-input.txt
start /wait bit -p -c .\stresstest.bitcfg -r
~~~~~\snap\~~~~

Than within the BIT I use the copy_tmp.cmd that only contains one line:

type tmp-script.txt >> bit-script-input.txt

It's included with .\copy_tmp.cmd in the configuration as a "start and wait until finished" application. As bit-script-input.txt is always deleted after one time of use, this way I make sure it's existing on every start of BIT and all my information are passed to the logfile.

My path I work on is c:\SYSPREP\rodabit\

All Batch files and configuration files are in the same directory like BIT.exe