On Mon, 27 Jun 2005 Paul Koning <pkoning at equallogic.com> wrote: Don't have RSTS. :-) True, and definitely a point for you. I offered them access to systems to check it out, but no interest. Myself, I'm not interested in Linux enough for this. I'm doing the TCP/IP for RSX instead. I know... :-/ RSX actually have a different program for each DEC OS that exist, to use instead of the "normal" CTERM program. Unsupported, of course, but working much better... DAP basically failed in three of the four tests I did between Linux and RSX. File transfers in both directions, and directory listings in both directions. The one that did work was directory listings of the RSX system files from RSX to Linux as well, but that was it. Everything else failed, or rather, just hung. On a separate issue, the public domain LAT is equally problematic, and should not be used to connect to RSX hosts. You'll crash the RSX host eventually. That LAT implementation seem to produce some packets that RSX just don't deal with, which results in buffer pool getting lost on the RSX end. It's definitely not a good behaviour in RSX as well, but never the less, it appears as if the PD LAT breaks the protocol in some way, and LAT is even worse, since no documentation exists outside of DEC (or whereever), so it's all reverse engineering (once more of VMS). Maybe one day... Or if I get my hands on the sources to RSX DECnet and LAT, I could do some cleanups in there... But that will not likely happen anytime soon I'm afraid... Ah, and there is also a bug in the DAP code in RSX. I have a patch for both RMSDAP.OLB and DAPRES. The problem is that the file protection word gets messed up when read. Johnny Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at update.uu.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol