Conference jamin::pathworks32

107.0. "SDK on EFT2C: dloopst.exe strange behavior." by DELNI::BARBER_MINGO (Let me DANCE for you) Fri Jan 31 1997 20:01

    EFT2C: PWSDK : DLOOPST.EXE
    
    Hi,
    	I downloaded and installed Pathworks on an Intel and Alpha
    system today.  I found that the DLOOPST.EXE program only appears
    to function with my OLD VMS machines.  My new ones are getting
    protocol not supported messages.  
        Am I supposed to have a particular version of Decnet on my
    VMS systems to run loopback?
    
        Terminal emulation(CTERM) worked for both systems.
    
    	In addition, the Pathworks event logger logged 3 NML messages
    whenever I tried to test loopback from my newer systems.  It
    seems like pathworks acknowledges that a message came in, but
    it isn't passing the message back through the application.
    
    	How do I run traces within the PAthworks modules to see
    how far the packets got?
    
    Thanks,
    Cindi
    

    Thanks for reporting this.  I have seen some problems relating to newer
    versions of VMS and loopback.  We are looking into this.  
    As another test, try running 'ncp mirror' on the pathworks32 machine and 
    running ncp loop to it from vms.  On my pw32 machine ncp mirror works 
    correctly, but the winsock2 sample mirrors produce an error on the VMS ncp:
    %NCP-W-INVPVA, invalid parameter value, Loop length
    Maximum data length = 2048
    %NIN-E-MIRBFOVF, morror buffer exceeded
    
    Ken R. 11-feb-97
      

    The newer versions of VMS use a loop message length of 4096.  If you
    experiance problems looping to or from your pc, try changing the pipe
    quotas in PATHWORKS 32.  
    For example type: 
    ncp define exec recv pipe quota 15
    ncp define exec transmit pipe quota 15
    and then reboot.
    This fixed my problems.
    
    Ken Robinson
    PATHWORKS 32
    Winsock2 DECnet