[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::excursion

Title:note 3 has pointer to current kit
Notice:note 3 has pointer to current kit
Moderator:PEACHS::GHEFF
Created:Wed May 29 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3301
Total number of notes:14905

3282.0. "Xappl can't work under DECNET using eXcursion v3.0" by HGOVC::ROCKYLAM () Mon May 05 1997 11:18

    It is found that even though one of our major customer using Pathworks
    32 and eXcursion v3, they cannot run Xapplication over DECnet on
    Window NT workstation v4.0. However, if TCP/IP is installed again, the
    Xapplication can immediately be run. ---- This is same result in
    Digital office. 
    
    If there is still problem of eXcursion v3.0 running on DECnet
    (even in Pathworks 32 on Window NT workstation 4.0) ?
    
    Please kindly advise.                                
T.RTitleUserPersonal
Name
DateLines
3282.1PEACHS::GHEFFDo you feel like swimming?Mon May 05 1997 13:156
    Which X application?  Are there any error messages?
    
    eXcursion usually works fine with PATHWORKS 32 DECnet on NT 4.
    
    
    #Gary
3282.2Further Discussion on eXercursion V3.0 ProblemHGOVC::ROCKYLAMTue May 06 1997 10:5415
    Thanks for your feedback.
    The X application is Xclock and Xeyes resided on the local PC. There is
    no response but without any error message when invoking the eXcursion
    v3.0 and these applications on the local PC. The protocol installed is only
    DECNET. 
    
    However, if we install the TCP/IP in the PC again, these application
    can be run properly after invoking eXcursion v3.0.
    
    Thanks for your further advise.
    
    Regards,
    
    Rocky Lam 
    
3282.3JAMIN::OSMANEric Osman, dtn 226-7122Tue May 06 1997 13:1313
    
    Most of our testing and our customers have been dealing with excursion
    running on the local PC but the x apps (such as xclock or xeyes)
    *not* running on the local PC.  Instead, most customers run xclock and
    xeyes (etc) on unix or vms machines, via decnet or tcpip.
    
    If you're really running xclock and xeyes on the local PC, then you're
    dealing with an area we haven't been testing as much.  If you've got
    a case that fails, please carefully document it in a qar.
    
    Thanks.
    
    /Eric