On 2012-08-23 23:21, Mark Benson wrote:
Hi,
Johnny can you add:
6.4 TOOCHI
to the node list.
It's a REALY VAX(station) :D
Done. :-)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Hi,
Johnny can you add:
6.4 TOOCHI
to the node list.
It's a REALY VAX(station) :D
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
Hi,
I don't suppose anyone has a 5/25" CD-ROM Storage Building Block (with or without CD ROM drive) for a BA36x storage array? They are the one that mounts across 3 bays and occupies 1 or 2 IDS on the bus.
I am looking for one that will work in a BA365 (late top-gun blue coloured) array. Colour matching isn't a concern as long as it works.
Thanks.
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
HECnet: STAR69::MARK
Online Resource & Mailing List for DEC Enthusiasts.
There were hundreds of them and I wasn't able to capture them, as I was on a VGA screen + actual keyboard.
It was some weird file formatting error with how the CD was burned.
Sampsa
On 20 Aug 2012, at 17:26, Paul_Koning at Dell.com wrote:
So what are the messages? What does the file look like in an editor, or with the TYPE command?
paul
On Aug 20, 2012, at 12:24 PM, Sampsa Laine wrote:
Tried that, and STREAM_CR - the files were created on OS X which is Unix-y.
Oh well, got it going in the end - won't let the damn things expire again so that reloading them is easier.
BTW, does someone have a license database pruner that'll kill expired licenses?
Sampsa
On 20 Aug 2012, at 17:22, Peter Coghlan wrote:
So I'm trying to load some licenses onto CHIMPY and am about to throw the
box out of the window.
Basically, I burnt the licenses as .COM files onto a CDROM, and mounted them
on the VMS box as follows:
MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM_LF:132)
When I try to run the COM file, I get loads of weird DCL errors, it's clearly not parsing the file right.
This should not be this difficult.
If the files were created on windows which tends to like CRLF delimited files,
maybe something like:
$ MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM:132)
would work better?
If this is not the case, more information about the way the files were created
and what the weird DCL errors were would be helpful.
Regards,
Peter Coghlan.
So what are the messages? What does the file look like in an editor, or with the TYPE command?
paul
On Aug 20, 2012, at 12:24 PM, Sampsa Laine wrote:
Tried that, and STREAM_CR - the files were created on OS X which is Unix-y.
Oh well, got it going in the end - won't let the damn things expire again so that reloading them is easier.
BTW, does someone have a license database pruner that'll kill expired licenses?
Sampsa
On 20 Aug 2012, at 17:22, Peter Coghlan wrote:
So I'm trying to load some licenses onto CHIMPY and am about to throw the
box out of the window.
Basically, I burnt the licenses as .COM files onto a CDROM, and mounted them
on the VMS box as follows:
MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM_LF:132)
When I try to run the COM file, I get loads of weird DCL errors, it's clearly not parsing the file right.
This should not be this difficult.
If the files were created on windows which tends to like CRLF delimited files,
maybe something like:
$ MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM:132)
would work better?
If this is not the case, more information about the way the files were created
and what the weird DCL errors were would be helpful.
Regards,
Peter Coghlan.
Tried that, and STREAM_CR - the files were created on OS X which is Unix-y.
Oh well, got it going in the end - won't let the damn things expire again so that reloading them is easier.
BTW, does someone have a license database pruner that'll kill expired licenses?
Sampsa
On 20 Aug 2012, at 17:22, Peter Coghlan wrote:
So I'm trying to load some licenses onto CHIMPY and am about to throw the
box out of the window.
Basically, I burnt the licenses as .COM files onto a CDROM, and mounted them
on the VMS box as follows:
MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM_LF:132)
When I try to run the COM file, I get loads of weird DCL errors, it's clearly not parsing the file right.
This should not be this difficult.
If the files were created on windows which tends to like CRLF delimited files,
maybe something like:
$ MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM:132)
would work better?
If this is not the case, more information about the way the files were created
and what the weird DCL errors were would be helpful.
Regards,
Peter Coghlan.
So I'm trying to load some licenses onto CHIMPY and am about to throw the
box out of the window.
Basically, I burnt the licenses as .COM files onto a CDROM, and mounted them
on the VMS box as follows:
MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM_LF:132)
When I try to run the COM file, I get loads of weird DCL errors, it's clearly not parsing the file right.
This should not be this difficult.
If the files were created on windows which tends to like CRLF delimited files,
maybe something like:
$ MOUNT DQB1: /MEDIA=CDROM/OVER=ID/UNDEF=(STREAM:132)
would work better?
If this is not the case, more information about the way the files were created
and what the weird DCL errors were would be helpful.
Regards,
Peter Coghlan.
Well, after all that, I'm happy to announce that RHESUS and CHIMPY are back online.
RHESUS has a fairly large file library available, including a whole bunch of SPDs..
Sampsa
On 20 Aug 2012, at 15:01, Sampsa Laine wrote:
Thanks, will do that next time :)
I manually typed in enough licenses to get DECNET going and pasted in the file via CTERM :)
Sampsa
On 20 Aug 2012, at 14:54, hvlems at zonnet.nl wrote:
The license utiility can build com files for you:
$ license/issue/proc/out=imf.com *
Omit the /procedure qualifier and all you get is the data as printed on the PAK.
Thanks, will do that next time :)
I manually typed in enough licenses to get DECNET going and pasted in the file via CTERM :)
Sampsa
On 20 Aug 2012, at 14:54, hvlems at zonnet.nl wrote:
The license utiility can build com files for you:
$ license/issue/proc/out=imf.com *
Omit the /procedure qualifier and all you get is the data as printed on the PAK.
The license utiility can build com files for you:
$ license/issue/proc/out=imf.com *
Omit the /procedure qualifier and all you get is the data as printed on the PAK.
