Author Topic: SC 7.5 DOS - Auto run several tests with an end report,  (Read 4490 times)

Offline regraham

  • Newbie
  • *
  • Posts: 2
    Hi Everyone,

    We are currently testing SC 7.5 for our notebook repair operation, what we are looking to get out of this software is the following,

    A non invasive (independent of the OS) series of tests and stress tests on core hardware with an end report, with as little user interaction as possible.

    I understand that we will need to run this from DOS and will need to create PDOs,

    I have some knowledge of editing batch files but simply have no idea where to start with these tests,

    Firstly is it possible to have SC 7.5 do the following (i've displayed as a list so its easier to say can/can't do for each.


    boot and automatically run,
    Maximum System Load
    then
    All quick tests,
    then
    Normal Hard Drive Tests
    then
    CPU/Memory Tests
    then
    Motherboard/Video Tests
    then
    Normal Hard Drive Tests
    then
    Internal Speaker
    then
    Mouse
    then
    Keyboard
    then Stereo Speaker
    then
    Create a custom report with our logo and
    save to the USB dongle,[/li]

if any of this is possible could someone point me in the direction for instructions to start looking into this?

Thanks everyone
« Last Edit: November 23, 2010, 08:10:57 am by regraham »

Offline fwilson

  • Hero Member
  • *****
  • Posts: 779
regraham,

It is relatively straight forward to do this but it does require a fair amount of DOS knowledge.

Running PC-Doctor command line to run a specific Overlay in a PDO file:
For example the following command line will run test overlay #1, disabling all prompting and log the results into a:\testlog.log.
pcdr /ba:01 /pr:a:\testlog /np

Running PC-Doctor command line to run a specific test:
For example the following command line will run the CPU test, disabling all prompting and log the results into a:\testlog.log.
pcdr /RT:CPU&1 /pr:a:\testlog /np


Running PC-Doctor from a control Batch File and parsing log results:
You can parse a text file from within a DOS batch file using the findstr command.  You could then exit the Batch file if the string FAILED is found in the logfile stopping any further execution.  You can use either overlays or specific tests in this scenario. Here is something I cobbled together to do such a thing with overlays:

@echo off
echo Running Overlay 1
pcdr /ba:01 /pr:c:\testlog.txt /np
findstr /m "FAILED" c:\testlog.txt
if %errorlevel%==0 goto FAIL
echo Running Overlay 2
pcdr /ba:02 /pr:c:\testlog2.txt /np
findstr /m "FAILED" c:\testlog2.txt
if %errorlevel%==0 goto FAIL
echo Running Overlay 3
pcdr /ba:03 /pr:c:\testlog3.txt /np
findstr /m "FAILED" c:\testlog3.txt
if %errorlevel%==0 goto FAIL
echo All Passed
goto END
:FAIL
echo TEST FAILED
:end

This batch file will stop execution if FAILED is found in the referenced text file.

Look at the advanced users guide on the CD for specific switch options.  Have fun!

-Fred
« Last Edit: November 23, 2010, 12:59:06 pm by fwilson »
“Integrity is doing the right thing, even if nobody is watching.”  ~ J.C. Watts

Offline regraham

  • Newbie
  • *
  • Posts: 2
Thanks fwilson,

How do I get PC Dr to boot straight to DOS mode looking at the root location which contains our batch file? at least then I can simply type "go" etc and run the batch,


and, would you mind, so that I have the best relative reference, indicate what each string in this batch is doing? at least then I know what pieces to pick and play with?

@echo off
echo Running Overlay 1
pcdr /ba:01 /pr:c:\testlog.txt /np
findstr /m "FAILED" c:\testlog.txt
if %errorlevel%==0 goto FAIL
echo Running Overlay 2
pcdr /ba:02 /pr:c:\testlog2.txt /np
findstr /m "FAILED" c:\testlog2.txt
if %errorlevel%==0 goto FAIL
echo Running Overlay 3
pcdr /ba:03 /pr:c:\testlog3.txt /np
findstr /m "FAILED" c:\testlog3.txt
if %errorlevel%==0 goto FAIL
echo All Passed
goto END
:FAIL
echo TEST FAILED
:end


Offline fwilson

  • Hero Member
  • *****
  • Posts: 779
regraham,

You can boot DOS directly from the USB key or the CD. 

You will need to modify the files on the USB key or create a custom CD with a good CD authoring software. Explore the key and you will see how it is set up.  The autoexec.bat file can be modified and the custom PDO can be added to the PCDR zip file contained on the key.

To do this on the CD you will need to save the boot tracks to an image file, modify the image to your specifications and create a new bootable CD with the modified files.  Instructions to do this using various software products are available on the web.

As far as the statements in the batch file I posted here is what they do:

pcdr /ba:01 /pr:c:\testlog.txt /np
This runs PCDR after loading the Ovelay 01(ba/:01).Writes a log file to c:\test.txt (pr:c:\test.log and disables prompting (/np

findstr /m "FAILED" c:\testlog.txt
Is a pure DOS command that looks for the string "FAILED" in the c:\testlog.txt file. if it is found it will set the environment errorlevel to 1 so that %errorlevel% will be 1 and the statement if %errorlevel%==0 goto FAIL will be triggered and skip the rest of the batch file.

To do a custom setup will require you to do a fair amount of learning the product as well as the DOS environment.  Please read the documentation on the use of the DOS product, it is on your distribution CD.

Step by step customizations and setups are beyond the scope of this board, if you need us to create a custom build, environment or factory type setup for you please contact sales and we will get you a quote.

-Fred
« Last Edit: November 24, 2010, 11:54:25 am by fwilson »
“Integrity is doing the right thing, even if nobody is watching.”  ~ J.C. Watts