Johnny> True, and definitely a point for you. I offered them access Johnny> to systems to check it out, but no interest. I suppose that too makes sense -- if you don't know the OS, it's hard to get started on debugging communication to it.

Johnny> On a separate issue, the public domain LAT is equally Johnny> problematic, and should not be used to connect to RSX Johnny> hosts. You'll crash the RSX host eventually. That LAT Johnny> implementation seem to produce some packets that RSX just Johnny> don't deal with, which results in buffer pool getting lost on Johnny> the RSX end. It's definitely not a good behaviour in RSX as Johnny> well, but never the less, it appears as if the PD LAT breaks Johnny> the protocol in some way, and LAT is even worse, since no Johnny> documentation exists outside of DEC (or whereever), so it's Johnny> all reverse engineering (once more of VMS). That's clearly a P1 RSX bug. There's a simple rule: if your system crashes because of a packet it received, that is ALWAYS the fault of the receiving system. Perhaps the sender should not have sent it, but "you shouldn't have sent that" is NEVER an acceptable excuse for crashing.