HECnet

hecnet@lists.dfupdate.se

1 participants
15560 discussions

by mcguire＠neurotica.com

On 01/01/2013 09:41 AM, Mark Wickens wrote: On 31 Dec 2012, at 23:41, Dave McGuire <mcguire at neurotica.com> wrote: Happy new year, my DECfetish friends! 20mins left of 2012, here. I am very drunk at the moment, but I don't mind admitting that you all have enriched my life considerably. :) Aw, bless, the hangover almost makes me tearful ;) ;) For me, hacking on PDP-8s, PDP-11s and VAXen can improve even the very worst day. And in this gang, that hacking is taken to its logical extreme. :-) All the best in health and happiness to you all. I promise to get a date for DEC Legacy 2013 sorted shortly! Oh! Umm, what part of the world will this be in? -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 5 months

Funky file formats, et al...

by bqt＠softjar.se

On 2013-01-01 16:55, Johnny Billquist wrote: On 2013-01-01 16:42, Johnny Billquist wrote: On 2013-01-01 16:25, Johnny Billquist wrote: On 2012-12-31 19:36, Bob Armstrong wrote: There s something else going on here. I m not sure who originally analyzed the file to decide that the format was Stream-CR (although given that the analysis was done on RSX, we can probably guess :-) Cool. This is become more weird all the time. WHat I reported was what was shown when doing a directory over DECnet. It's the information VMS presents. RSX is not really involved. What happens if you do a directory showing the attributes over DECnet on a VMS node? I sould say that I don't *think* RSX is involved more than just printing out what it receives from the VMS node, but I might of course be wrong in that. I think we have VMS machines with guest accounts. I'm going to test using one of those. To reduce speculation slightly. From a VMS machine, looking at LEGATO::INFO.TXT;1, it claims that it is Stream_LF, so obviously the "Stream_CR" message must be produced (I assume) in RSX. So it appears that RSX have something wrong in the interpretation of which is which. I'm going to read up more on the file access protocol to understand exactly how it works here, and then I'm ready to declare a bug in NFT on RSX. After that, I guess the next step would be to try and fix it. I wonder it that also implies that the deblocking is done in RSX, which then don't strip the LF out since it thinks it in a Stream_CR. That would be plausible. Bob, please keep your "old" INFO.TXT around. It will be a good test case when I try to fix RSX... Johnny

12 years, 5 months

Funky file formats, et al...

by bqt＠softjar.se

On 2013-01-01 16:42, Johnny Billquist wrote: On 2013-01-01 16:25, Johnny Billquist wrote: On 2012-12-31 19:36, Bob Armstrong wrote: There s something else going on here. I m not sure who originally analyzed the file to decide that the format was Stream-CR (although given that the analysis was done on RSX, we can probably guess :-) Cool. This is become more weird all the time. WHat I reported was what was shown when doing a directory over DECnet. It's the information VMS presents. RSX is not really involved. What happens if you do a directory showing the attributes over DECnet on a VMS node? I sould say that I don't *think* RSX is involved more than just printing out what it receives from the VMS node, but I might of course be wrong in that. I think we have VMS machines with guest accounts. I'm going to test using one of those. To reduce speculation slightly. From a VMS machine, looking at LEGATO::INFO.TXT;1, it claims that it is Stream_LF, so obviously the "Stream_CR" message must be produced (I assume) in RSX. So it appears that RSX have something wrong in the interpretation of which is which. I'm going to read up more on the file access protocol to understand exactly how it works here, and then I'm ready to declare a bug in NFT on RSX. After that, I guess the next step would be to try and fix it. I wonder it that also implies that the deblocking is done in RSX, which then don't strip the LF out since it thinks it in a Stream_CR. That would be plausible. Johnny

12 years, 5 months

Funky file formats, et al...

by bqt＠softjar.se

On 2013-01-01 16:25, Johnny Billquist wrote: On 2012-12-31 19:36, Bob Armstrong wrote: There s something else going on here. I m not sure who originally analyzed the file to decide that the format was Stream-CR (although given that the analysis was done on RSX, we can probably guess :-) Cool. This is become more weird all the time. WHat I reported was what was shown when doing a directory over DECnet. It's the information VMS presents. RSX is not really involved. What happens if you do a directory showing the attributes over DECnet on a VMS node? I sould say that I don't *think* RSX is involved more than just printing out what it receives from the VMS node, but I might of course be wrong in that. I think we have VMS machines with guest accounts. I'm going to test using one of those. Johnny

12 years, 5 months

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

by system＠TMESIS.COM

Johnny Billquist <bqt at softjar.se> writes: On 2012-12-31 19:09, Bob Armstrong wrote: I'm not convinced that a '$ CONVERT/FDL="record; format stream_lf"' would handle that file's contents correctly. I'm pretty sure it will. Bob, could you try? Yes, CONVERT on VMS is perfectly happy to convert the original file. FWIW, that's how I created the "conventional" variable record length version that RSX likes too. Actually, what I had in mind was just changing the attributes of the existing file. A convert actually proves very little. Even less if your file actually was Stream_LF, which it looked like locally. And that would make total sense, considering the contents of the file. So, I wonder why it looks like Stream_CR when looked at from RSX. Does it look "correct" of looking over DECnet from a VMS machine. And the LF is the character that sits in the file. I think we can all agree on that. It, at this point, smells like the FAL listener on VMS is the thing that would get it wrong, but this is just guessing on my part... It's all speculation at this point. Post the output of '$ DUMP/BLOCKS' as well as '$ ANALYZE/RMS/SUMMARY' of the original file that had spawned this discussion. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 5 months

Node DB error for STAR69

by bqt＠softjar.se

On 2012-12-31 22:07, Mark Benson wrote: NODE NODE NODE REGISTER NAME ADDRESS OWNER TIME STAR69 6.1 Mark >>Berryman<< 12-Nov-2011 12:00:00 Spot the deliberate mistake :) Ooops. Fixed. Johnny

12 years, 5 months

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

by bqt＠softjar.se

On 2012-12-31 19:09, Bob Armstrong wrote: I'm not convinced that a '$ CONVERT/FDL="record; format stream_lf"' would handle that file's contents correctly. I'm pretty sure it will. Bob, could you try? Yes, CONVERT on VMS is perfectly happy to convert the original file. FWIW, that's how I created the "conventional" variable record length version that RSX likes too. Actually, what I had in mind was just changing the attributes of the existing file. A convert actually proves very little. Even less if your file actually was Stream_LF, which it looked like locally. And that would make total sense, considering the contents of the file. So, I wonder why it looks like Stream_CR when looked at from RSX. Does it look "correct" of looking over DECnet from a VMS machine. And the LF is the character that sits in the file. I think we can all agree on that. It, at this point, smells like the FAL listener on VMS is the thing that would get it wrong, but this is just guessing on my part... Johnny

12 years, 5 months

Funky file formats, et al...

by bqt＠softjar.se

On 2012-12-31 19:36, Bob Armstrong wrote: There s something else going on here. I m not sure who originally analyzed the file to decide that the format was Stream-CR (although given that the analysis was done on RSX, we can probably guess :-) Cool. This is become more weird all the time. WHat I reported was what was shown when doing a directory over DECnet. It's the information VMS presents. RSX is not really involved. What happens if you do a directory showing the attributes over DECnet on a VMS node? Johnny

12 years, 5 months

happy new year!

by hvlems＠zonnet.nl

A healthy and happy New Year to all of you! Hans -----Oorspronkelijk bericht----- Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens Mark Wickens Verzonden: dinsdag, januari 2013 15:42 Aan: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] happy new year! On 31 Dec 2012, at 23:41, Dave McGuire <mcguire at neurotica.com> wrote: Happy new year, my DECfetish friends! 20mins left of 2012, here. I am very drunk at the moment, but I don't mind admitting that you all have enriched my life considerably. :) -Dave Aw, bless, the hangover almost makes me tearful ;) All the best in health and happiness to you all. I promise to get a date for DEC Legacy 2013 sorted shortly! Regards, Mark.

12 years, 5 months

happy new year!

by mark＠wickensonline.co.uk

On 31 Dec 2012, at 23:41, Dave McGuire <mcguire at neurotica.com> wrote: Happy new year, my DECfetish friends! 20mins left of 2012, here. I am very drunk at the moment, but I don't mind admitting that you all have enriched my life considerably. :) -Dave Aw, bless, the hangover almost makes me tearful ;) All the best in health and happiness to you all. I promise to get a date for DEC Legacy 2013 sorted shortly! Regards, Mark.

12 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet