On 2014-04-23 20:39, Paul_Koning at Dell.com wrote: On Apr 23, 2014, at 2:28 PM, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote: El 23/04/2014, a les 20.13, Johnny Billquist <bqt at softjar.se> va escriure: Cool. Thanks. TOPS-20 FAL looks semi-sane, and I can talk with it. Tops-10 FAL looks really weird, but at least some kind of communication is possible. RSTS/E FAL is not agreeing with RSX, it would seem. :-( Well, I can get at least a little bit of communication. I can get a DIRECTORY and I can type a remote file, forcing the mode to ASCII (/AS). ...... NFT>ti:=bitxot"[201,2] guestguest"::login.com NFT -- Error in opening output file TT:LOGIN.COM Invalid or Unsupported Record format NFT>ti:=bitxot"[201,2] guestguest"::login.com/as Since RSTS native files are not RMS files, and login.com most likely is such a file, chances are it s coming across as a file of undefined record format. Either that, or stream-crlf. You may want to look at a protocol trace to see what it s doing. That could explain the unsupported record format message. RSTS can certainly talk to other NFTs, but you have to tell it how to map native files to some RMS format, if you re pulling from RSTS. Pretty much: .nft bitxot"201,2 guestguest"::login.com/at Directory BITXOT::_SY:[201,2] 23-APR-14 21:17:47 LOGIN.COM Size: 1./4. Created: 25-APR-14 04:24:00 Owner: [201,2] Revised: 25-APR-14 04:24:00 Expires: <none_specified> File protection: System:RWED, Owner:RWED, Group:, World: File organization: Sequential File attributes: Allocation=0 Record format: Undefined, no maximum defined Record attributes: None Total of 1./4. Blocks in 1. Files .nft bitxot"201,2 guestguest"::login.com/id NFT -- Version V9.0 Local NFARs V8 DAP V7.1 Buffer size= 2064. OS=RSX-11M+ FS=FCS-11 DC=Yes Remote FAL V4.1 DAP V5.6 Buffer size= 636. OS=RSTS/E FS=RMS-11 DC=No Johnny