NDIS 6.0 test -- 2c_oidndisrequest.wsf script terminates abnormally

Discussion in 'Windows Vista Drivers' started by abrahamlincolng, Mar 6, 2008.

  1. I am performing NDIS 6.0 test on LAN device. During
    "2c_oidsndisrequest"
    test, script terminates abnormally.It gave the message "Invalid
    procedure call or argument:
    'Left' ".

    When analysing the failure carefully observed that one of the argument
    i.e "Version" will be Empty after this function call,
    bDriverInfoFound =
    oNDTSupp.DriverInfo(DriverName,Size,TimeStamp,Version,Checked)

    So after the above function call, when this statement executed ,
    HighWord = Left(Version, FirstPos-1)), the Left () function called
    with Version as Empty causes the script terminated.

    Any idea how to fix this problem !!!!!!

    Below is the code where the script terminated. Also the NDIS test logs
    provided.

    2c_oidsndisrequest.wsf code;

    HighWord = Left(Version, FirstPos-1) /* Here the script terminates*/
    Temp1 = Left(Version, SecondPos-1)

    NDIS Logs :

    Variation #48 Checking if OID must be queried
    Querying/Comparing return values
    NdisRequest
    - OpenId = 0x01010001
    - OID = OID_GEN_VENDOR_DRIVER_VERSION
    Vendor Driver Version Number = 65536
    NdisRequest
    - OpenId = 0x01010001
    - OID = OID_GEN_VENDOR_DRIVER_VERSION
    Vendor Driver Version Number = 65536

    Variation #49 Testing OID_GEN_VENDOR_DRIVER_VERSION
    [624940]NdtSupp: DriverInfo: GetFileVersionInfoSize return 0 for
    C:\Windows\system32\DRIVERS\usbiad.sys.
    NdisClose
    - OpenId = 0x01010001
    NdisClose
    - OpenId = 0x01010002
    NdisClose
    - OpenId = 0x02010001

    Variation #50 Verifing script completed successfully...
    FAILED: [0] Script was terminated abnormally!

    THIS COULD BE THE RESULT OF AN INTERNAL ERROR,
    DELIBERATE TERMINATION OF THE WSCRIPT PROCESS OR
    STOPPING THE SCRIPT WITH THE UI!

    Also If i see the logs at Variation #48 it is getting the Vendor
    Driver
    Version Number as 65536, but fails to get at variation #49.

    Please provide help immediately as I am going bald due to this
    problem.

    Rgds,
    RK
     
    abrahamlincolng, Mar 6, 2008
    #1
    1. Advertisements

  2. abrahamlincolng

    PCAUSA Guest

    Variation #49 seems to be looking at the driver file's version
    information; See the MSDN description of GetFileVersionInfo and
    friends. Do you have a version resource compiled into your driver?

    Thomas F. Divine
     
    PCAUSA, Mar 6, 2008
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.