serial port driver test,why creatfile cann't work? - Software-Testing

This is a discussion on serial port driver test,why creatfile cann't work? - Software-Testing ; I use COM1 to receive test info data when I am running test. I use the software Accessport.exe. So I think my COM port is all right.But yht log shows error55 means ERROR_DEV_NOT_EXIT.I use the default command line tux –o ...

+ Reply to Thread
Results 1 to 3 of 3

serial port driver test,why creatfile cann't work?

  1. Default serial port driver test,why creatfile cann't work?

    I use COM1 to receive test info data when I am running test. I use the
    software Accessport.exe. So I think my COM port is all right.But yht log
    shows error55 means ERROR_DEV_NOT_EXIT.I use the default command line tux –o
    –d serdrvbvt .
    *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    ShellProc(SPM_BEGIN_TEST, ...) called
    BEGIN TEST: "Send bytes at all supported bauds, data-bits, parity and
    stop-bits", Threads=0, Seed=29897
    Send bytes at all supported bauds, data-bits, parity and stop-bits on
    COM1
    FAIL in c:\mlqa\private\test\drivers\serial\bvt\serdrvbvt\testproc.cpp
    at line 113: Util_OpenCommPort(); error 55
    ShellProc(SPM_END_TEST, ...) called
    END TEST: "Send bytes at all supported bauds, data-bits, parity and
    stop-bits", FAILED, Time=0.021
    *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    That is to say the specified network resource or device is no longer
    available.
    Any body could help me?why?
    Regards
    Mary

  2. Default Re: serial port driver test,why creatfile cann't work?

    Is the accessport.exe running when you execute this test . Try using command
    lone -pCOM1:
    and observe what happens.

    Can you give more information about your platform, OS version and Post the
    complete logs .

    Thanks
    Shiv


    "Mary" <guangjuan.wang@ge.com> wrote in message
    news:EA0BB0EB-B654-48ED-B057-4C2742EF2C68@microsoft.com...
    >I use COM1 to receive test info data when I am running test. I use the
    > software Accessport.exe. So I think my COM port is all right.But yht log
    > shows error55 means ERROR_DEV_NOT_EXIT.I use the default command line
    > tux -o
    > -d serdrvbvt .
    > *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    > ShellProc(SPM_BEGIN_TEST, ...) called
    > BEGIN TEST: "Send bytes at all supported bauds, data-bits, parity and
    > stop-bits", Threads=0, Seed=29897
    > Send bytes at all supported bauds, data-bits, parity and stop-bits on
    > COM1
    > FAIL in
    > c:\mlqa\private\test\drivers\serial\bvt\serdrvbvt\testproc.cpp
    > at line 113: Util_OpenCommPort(); error 55
    > ShellProc(SPM_END_TEST, ...) called
    > END TEST: "Send bytes at all supported bauds, data-bits, parity and
    > stop-bits", FAILED, Time=0.021
    > *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > That is to say the specified network resource or device is no longer
    > available.
    > Any body could help me?why?
    > Regards
    > Mary




  3. Default Re: serial port driver test,why creatfile cann't work?

    Thanks ShivShankar
    I adjust the parameter in platform.reg, then the test works.
    Regards
    Mary

    "ShivShankar" wrote:

    > Is the accessport.exe running when you execute this test . Try using command
    > lone -pCOM1:
    > and observe what happens.
    >
    > Can you give more information about your platform, OS version and Post the
    > complete logs .
    >
    > Thanks
    > Shiv
    >
    >
    > "Mary" <guangjuan.wang@ge.com> wrote in message
    > news:EA0BB0EB-B654-48ED-B057-4C2742EF2C68@microsoft.com...
    > >I use COM1 to receive test info data when I am running test. I use the
    > > software Accessport.exe. So I think my COM port is all right.But yht log
    > > shows error55 means ERROR_DEV_NOT_EXIT.I use the default command line
    > > tux -o
    > > -d serdrvbvt .
    > > *** vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
    > > ShellProc(SPM_BEGIN_TEST, ...) called
    > > BEGIN TEST: "Send bytes at all supported bauds, data-bits, parity and
    > > stop-bits", Threads=0, Seed=29897
    > > Send bytes at all supported bauds, data-bits, parity and stop-bits on
    > > COM1
    > > FAIL in
    > > c:\mlqa\private\test\drivers\serial\bvt\serdrvbvt\testproc.cpp
    > > at line 113: Util_OpenCommPort(); error 55
    > > ShellProc(SPM_END_TEST, ...) called
    > > END TEST: "Send bytes at all supported bauds, data-bits, parity and
    > > stop-bits", FAILED, Time=0.021
    > > *** ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    > > That is to say the specified network resource or device is no longer
    > > available.
    > > Any body could help me?why?
    > > Regards
    > > Mary

    >
    >
    >


+ Reply to Thread

Similar Threads

  1. run Serial Communication test against USB Serial Port
    By Application Development in forum Software-Testing
    Replies: 2
    Last Post: 09-13-2007, 01:14 PM
  2. Subject: The serial port driver test of CETK can't be finished
    By Application Development in forum Software-Testing
    Replies: 0
    Last Post: 04-28-2007, 04:46 AM
  3. Running serial port test on my custom driver
    By Application Development in forum Software-Testing
    Replies: 0
    Last Post: 04-06-2006, 10:14 AM
  4. Serial Port Driver Test CETK 5.0 command line usage
    By Application Development in forum Software-Testing
    Replies: 1
    Last Post: 03-14-2005, 08:02 PM
  5. Serial Port Driver Test Problem!!??
    By Application Development in forum Software-Testing
    Replies: 1
    Last Post: 11-16-2004, 12:29 AM