INFO.TXT, was Re: [HECnet] UPDATE: HECNET.HLP file for VMS systems

[Brian Schenkenberger, VAXman-]

Johnny Billquist <bqt at softjar.se> writes: 

I think that VMS is lying to itself in this case, and VMS is buying it.
A file with Stream_CR, and not a single CR in the file... What would you
expect the result to be? 

I can't see the file in question as I've not yet gotten my network onto
HECnet.   If you can make a VMS BACKUP of the file and make it available
for download (ftp, sftp, http), I'll determine what's going on with it.



(Or rather, Emacs is lying to VMS, and VMS is buying it.) 

The Emacs for VMS post is ancient (neolithic) history.   Who knows what's
being told to the file system when a file is created, updated and closed.



However, when feeding that file over DECnet, the result looks ugly, so
the FAL in VMS isn't totally falling for the lie. :-) 

FAL will open the file based upon the file attributes of the file and it
will then attempt to digest it with those file attributes to transfer it
over the wire.   Without a corresponding set of file attributes on RSX, it
is possible that it's RSX that is choking.   Try logging into the VMS box
which has this file and dump it:

$ DUMP/RECORD <the-file>/OUTPUT=THE_FILE_RCD.DMP
$ DUMP/BLOCKS <the-file>/OUTPUT=THE_FILE_RAW.DMP

...and then, make it available here so that I can see its layout.   I DO
not believe that VMS RMS "lies"; especially, after four years of work in
it!

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker       VAXman(at)TMESIS(dot)ORG

Well I speak to machines with the voice of humanity.