T.R | Title | User | Personal Name | Date | Lines |
---|
846.1 | | 20074::dike | | Fri May 26 1989 09:15 | 6 |
| 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.2 | What about VMS? | RTPSWS::MCMULLEN | | Fri May 26 1989 16:54 | 11 |
| 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.3 | Known bug in VMS | 19458::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Tue May 30 1989 13:26 | 5 |
| It's a known bug in VMS that the server can't service clients with other
byte orders. Fixed soon, I hope.
Burns
|
846.4 | It's in there. | 19763::MARRA | Acts 2:4 | Tue May 30 1989 15:12 | 2 |
| Yeah, it's fixed in V2... I confirmed the fix last week.
|
846.5 | Thanks! | RTPSWS::MCMULLEN | | Tue May 30 1989 21:22 | 2 |
|
|
846.6 | Prophecy? Cynicism! | POOL::HALLYB | The Smart Money was on Goliath | Wed May 31 1989 09:38 | 4 |
| 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...
|