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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

846.0. "Big Endian/Little Endian" by 33836::MCMULLEN () Thu May 25 1989 21:52

    Has anyone noticed a big endian/little endian problem in the
    X protocol when using tcpip transport to other vendors workstations?
    It appears that we can't communicate to machines of different byte
    order than VAX architecture. I've seen it on a vms machine running
    the tcpip transport with the Connection software and been told it
    also occurs under Ultrix.
    
    Thanks in advance,
    Mike McMullen
    

T.RTitleUserPersonal
Name
DateLines
846.120074::dikeFri May 26 1989 09:156
Ultrix servers and clients can talk to any other machine that has correctly
implemented X, regardless of byte order, although some clients have problems
with image bit order.  It would be pretty useless if all we could talk X with
was other Vaxen, or machines with the same byte order as Vaxen.
				Jeff

846.2What about VMS?RTPSWS::MCMULLENFri May 26 1989 16:5411
    True. I agree with every word you say. I didn't see the problem with Ultrix
    and I have had no problem with my own tinkering here at Digital and when
    I was working at NCSU. However I did see the problem on a VMS machine
    talking to another machine using the tcpip transport executable with
    the VMS/Ultrix Connection. Connections to that machine from other types
    of workstations worked fine. I was curious if anyone else had seen a
    problem when using tcp/ip transport from VMS.
    
    Mike
    

846.3Known bug in VMS19458::FISHERBurns Fisher 381-1466, ZKO3-4/W23Tue May 30 1989 13:265
It's a known bug in VMS that the server can't service clients with other
byte orders.  Fixed soon, I hope.

Burns

846.4It's in there.19763::MARRAActs 2:4Tue May 30 1989 15:122
Yeah, it's fixed in V2...  I confirmed the fix last week.

846.5Thanks!RTPSWS::MCMULLENTue May 30 1989 21:222
    

846.6Prophecy? Cynicism!POOL::HALLYBThe Smart Money was on GoliathWed May 31 1989 09:384
    Now all we need is to discover that one layer of the protocol
    byte-swaps the data, unbeknownst to a lower layer that also decides
    it needs to byte-swap the data...