Yup, I used THNITH:: (a real 11/83 that has Johnny’s RSX TCP) to ftp my original Multinet
zip from Internet and then sent it to FASH:: (my VAXstation) over DECnet. That’s when I
found out about the attribute mangling caveat.
On Feb 22, 2026, at 18:27, Jacob Ritorto
<jacob.ritorto(a)gmail.com> wrote:
Right on, big thx Terri. The transfer is proceeding niiice and slow..
Speaking of Process and vendors still supporting VMS ecosystem, anybody going to Sweden
for this VMS Bootcamp in May? I am so exuberant about my VS 3520 and VMS at the moment
I’m actually considering it. I mean, what if I could quit boring commodity computer work
and work on my beloved DEC stuff for real money! It’s been my dream since I was a teen.
But there are probably no jobs left in the field, right?
One other Q for Terri: what do I do with all these .a .b .c .d files? Googling for
instructions as soon as I hit send…
thx
jake
> On Feb 22, 2026, at 18:03, Terri Kennedy <terri-hecnet(a)glaver.org> wrote:
>
> Well, I certainly blew that, didn't I...
>
>>> On 2026-02-22 17:58, Terri Kennedy wrote:
>> Just to you, for obvious reasons...
>>> On 2026-02-22 17:38, Jacob Ritorto wrote:
>>> Hehe, yup, Multinet‘s exactly what I’m trying to do, here. But the
>>> Multinet ZIP I have has bad attribs from passing thru other systems,
>>> so UNZIP can’t grok it and is telling me I have to set it to stream
>>> using some utility on the freeware cd (which I can’t unzip :). Hence
>>> the ask to copy it on HECnet so the file transfer doesn’t clobber the
>>> attribs and I can actually use it.
>> $ COPY SPCVXA::MULTINET056.* []
>> Should do it for you. Let me know if it doesn't.
>
> Please do not willy-nilly grab this kit - it was intended just for
> Jacob. Process had official distribution channels that should be used,
> and as soon as Jacob tells me he has the kit, I'll be removing it.
> _______________________________________________
> HECnet mailing list -- hecnet(a)lists.dfupdate.se
> To unsubscribe send an email to hecnet-leave(a)lists.dfupdate.se