sl@0: The .bat and .txt files in directories Batchfiles and CommandFiles has
sl@0: been automatically generated by the Perl script
sl@0: DABS_test_data.pl. That script uses a files called test_data.txt to
sl@0: read which batch files copies over test data from the MMC card to the
sl@0: C:-drive and delete the data from the C:-drive when test has
sl@0: finished. 
sl@0: 
sl@0: test_data.txt was generated by executing "grep -i -l copy *.bat
sl@0: >test_data.txt" in a Cygwin bash shell. The grep utility found on
sl@0: \\londata21\tools works just as well. 
sl@0: 
sl@0: The .txt files contain the command autoexec.bat will execute on HW to
sl@0: copy over the data. Eg MMFSbcUnitTests_del_data.txt contains the line:
sl@0: 
sl@0: call e:\MMFSbcUnitTests_del_data.bat
sl@0: 
sl@0: The .bat files contains the actual copy and delete commands.
sl@0: 
sl@0: These files are necessary because the DABS system uses one file to
sl@0: build up the autoexec.bat file. A line in that file can look like:
sl@0: 
sl@0: testframework, logs\testresults\mm\TSU_MMF_SBCCODEC.htm, ,
sl@0: \TSU_MMF_SBCCODEC.script, 600, UREL,
sl@0: MMFSbcUnitTests_copy_test_data.txt,
sl@0: MMFSbcUnitTests_del_test_data.txt 
sl@0: 
sl@0: where the two last arguments is the pretest and posttest command
sl@0: files. Unfortunately the command file can only contain one line as
sl@0: the DABS system only reads the first line in that file. Bonkers
sl@0: but there you go.
sl@0: 
sl@0: The above test line will produce an autoexec.bat looking like this:
sl@0: 
sl@0: call e:\MMFSbcUnitTests_copy_test_data.bat
sl@0: RUNTESTS testframeworkTSU_MMF_SBCCODEC.script.txt -t 10
sl@0: call e:\MMFSbcUnitTests_del_test_data.bat