Mark,
Wrong machine...
"boot -fl 0,1" not "boot/r5:..."
I was in VAXen mode not Alpha... :-)
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Steve Davidson
Sent: Thursday, June 16, 2011 17:44
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] Introduction
Mark,
If you can get to the system console prompt ">>>" then boot into
converstional mode "boot/r5:00000001 <boot_dev>:".
At "SYSBOOT>"
Type "SET STARTUP_P1 "MIN"
Type "CONTINUE"
This should bring the system up without DECwindows. At this point
install your licenses. I would NOT install every license it is a real
pain to delete them all when you have to renew them each year. I
usually wind up "fixing" this on several machines within HECnet. Before
rebooting, execute the following:
$ SET DEFAULT SYS$SYSTEM
$ MCR SYSGEN
SYSTEM> USE CURRENT
SYSGEN> SET STARTUP_P1 ""
SYSGEN> WRITE CURRENT
SYSGEN> EXIT
$
$ REBOOT
-Steve Davidson
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Mark Benson
Sent: Thursday, June 16, 2011 16:15
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Introduction
Well I'm stuck now. I couldn't get my Licenses to validate during
install so I skipped that part and put them in later. I put in the base
license for OPENVMS-ALPHA and rebooted the machine. Now I am presented
with a DECwindows login screen (which is some welcome progress) and I
can't log in because I get the 'LMF license check has failed' error (no
DECwindows license??).
If I could get out to a command-line terminal I can input some more
licenses but, unlike any other CDE/Motif system I've used before the
'Options' menu has no 'Command Line Login' option.
Is there a boot flag from the SRM console or a special keystroke command
I can issue, or any other method to get me to a command line?
Also does anyone know which licenses I will need to enter and operate
the DECwindows 1.6 environment?
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
Mark,
If you can get to the system console prompt ">>>" then boot into
converstional mode "boot/r5:00000001 <boot_dev>:".
At "SYSBOOT>"
Type "SET STARTUP_P1 "MIN"
Type "CONTINUE"
This should bring the system up without DECwindows. At this point
install your licenses. I would NOT install every license it is a real
pain to delete them all when you have to renew them each year. I
usually wind up "fixing" this on several machines within HECnet. Before
rebooting, execute the following:
$ SET DEFAULT SYS$SYSTEM
$ MCR SYSGEN
SYSTEM> USE CURRENT
SYSGEN> SET STARTUP_P1 ""
SYSGEN> WRITE CURRENT
SYSGEN> EXIT
$
$ REBOOT
-Steve Davidson
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Mark Benson
Sent: Thursday, June 16, 2011 16:15
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Introduction
Well I'm stuck now. I couldn't get my Licenses to validate during
install so I skipped that part and put them in later. I put in the base
license for OPENVMS-ALPHA and rebooted the machine. Now I am presented
with a DECwindows login screen (which is some welcome progress) and I
can't log in because I get the 'LMF license check has failed' error (no
DECwindows license??).
If I could get out to a command-line terminal I can input some more
licenses but, unlike any other CDE/Motif system I've used before the
'Options' menu has no 'Command Line Login' option.
Is there a boot flag from the SRM console or a special keystroke command
I can issue, or any other method to get me to a command line?
Also does anyone know which licenses I will need to enter and operate
the DECwindows 1.6 environment?
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
Mark,
There's a way to fire off an interactive boot and then telling the startup not to start decwindows, I don't have the details handy right now, will look it up unless someone else knows it from memory - I'm a relative noob here as well.. :)
As for loading licenses, just load all of them :)
I find the easiest way to get the licenses loaded is to burn a CD with a text file containing all the lines from the hobbyist email starting with a $ sign, calling the file e.g. LOADLIC.COM.
I then mount the CD as follows:
MOUNT/MEDIA=CD-ROM/UNDEFINED=(STREAM_LF:132)/OVER=ID <DEVICE NAME>
Then just run the license file:
@<DEVICENAME>:[000000]LOADLIC.COM
Sampsa
On 16 Jun 2011, at 21:14, Mark Benson wrote:
Well I'm stuck now. I couldn't get my Licenses to validate during install so I skipped that part and put them in later. I put in the base license for OPENVMS-ALPHA and rebooted the machine. Now I am presented with a DECwindows login screen (which is some welcome progress) and I can't log in because I get the 'LMF license check has failed' error (no DECwindows license??).
If I could get out to a command-line terminal I can input some more licenses but, unlike any other CDE/Motif system I've used before the 'Options' menu has no 'Command Line Login' option.
Is there a boot flag from the SRM console or a special keystroke command I can issue, or any other method to get me to a command line?
Also does anyone know which licenses I will need to enter and operate the DECwindows 1.6 environment?
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
Well I'm stuck now. I couldn't get my Licenses to validate during install so I skipped that part and put them in later. I put in the base license for OPENVMS-ALPHA and rebooted the machine. Now I am presented with a DECwindows login screen (which is some welcome progress) and I can't log in because I get the 'LMF license check has failed' error (no DECwindows license??).
If I could get out to a command-line terminal I can input some more licenses but, unlike any other CDE/Motif system I've used before the 'Options' menu has no 'Command Line Login' option.
Is there a boot flag from the SRM console or a special keystroke command I can issue, or any other method to get me to a command line?
Also does anyone know which licenses I will need to enter and operate the DECwindows 1.6 environment?
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
On 2011-06-16 20.53, Johnny Billquist wrote:
On 2011-06-16 20.08, Mark Benson wrote:
On 16 Jun 2011, at 18:55, Mark Wickens wrote:
I've yet to dip my toe properly in the emulated water
There is a sneaky way around the SIMH-can't-talk-to-host limitation:
Stick SIMH in a VM :) That way it can talk to the host running
VMware, just not the IP stack on the VM itself.
Ah, that's clever. Although I'm still thwarted given that atoms don't
have the required VM instructions.
You are correct, Atom CPUs lack the VTx component required for true
Virtualisation. For some confounded reason Intel thought it might not
be needed in a Netbook CPU ;)
In my case I could easily run SIMH on my Mac Pro (I take it it'll
compile on OS X? Maybe need darwin-ports or something like that?) - it
has dual ethernet interfaces and one is redundant t the moment :)
===
So, do I need more than one ethernet card in the Linux machine to run
a DECnet bridge out to HECnet?
I'm not aware if DECnet and TCP/IP will play nicely on the same LAN or
if I need a separate one for DECnet connections?
DECnet and TCP/IP are just two different protocols on ethernet. No
issues or problems with that. In fact, you also have at least ARP also
running on the same ethernet (yet another protocol).
No, you do not need to have two interfaces on a bridge machine, unless
possibly if you want the machine that runs the bridge software itself to
also be participating in the DECnet network as a node itself.
The bridge program should compile just fine on Linux systems. If there
are any issues, just let me know.
There is a makefile, so just typing make in the directory where you have
the files should produce the binary. Then you just need to figure out
where to connect to, setup the config file, and start running.
The separate issue then is set configuration of DECnet itself on
whatever (VMS?) machine you use.
Oh, yeah. I just sent a separate mail to Mark Benson as well. The same as you've all seen in the past. Starting with area, then figuring out node number, nodename, where to connect to, and so on... You all know the drill... :-)
Johnny
On 2011-06-16 20.08, Mark Benson wrote:
On 16 Jun 2011, at 18:55, Mark Wickens wrote:
I've yet to dip my toe properly in the emulated water
There is a sneaky way around the SIMH-can't-talk-to-host limitation: Stick SIMH in a VM :) That way it can talk to the host running VMware, just not the IP stack on the VM itself.
Ah, that's clever. Although I'm still thwarted given that atoms don't have the required VM instructions.
You are correct, Atom CPUs lack the VTx component required for true Virtualisation. For some confounded reason Intel thought it might not be needed in a Netbook CPU ;)
In my case I could easily run SIMH on my Mac Pro (I take it it'll compile on OS X? Maybe need darwin-ports or something like that?) - it has dual ethernet interfaces and one is redundant t the moment :)
===
So, do I need more than one ethernet card in the Linux machine to run a DECnet bridge out to HECnet?
I'm not aware if DECnet and TCP/IP will play nicely on the same LAN or if I need a separate one for DECnet connections?
DECnet and TCP/IP are just two different protocols on ethernet. No issues or problems with that. In fact, you also have at least ARP also running on the same ethernet (yet another protocol).
No, you do not need to have two interfaces on a bridge machine, unless possibly if you want the machine that runs the bridge software itself to also be participating in the DECnet network as a node itself.
The bridge program should compile just fine on Linux systems. If there are any issues, just let me know.
There is a makefile, so just typing make in the directory where you have the files should produce the binary. Then you just need to figure out where to connect to, setup the config file, and start running.
The separate issue then is set configuration of DECnet itself on whatever (VMS?) machine you use.
Johnny
Mark Benson wrote:
Funny, I sent myself an e-mail with the URL of that self-same page only
this morning. Lots a' reading to do. I have a working OpenVMS box now
but not the faintest clue how to operate it. :)
RTFM to the power 20 I think is required!
The "help" command on VMS is your friend. Waaaay better than "man" on UNIX.
Peace... Sridhar
The scsnode and the scssystemid are tightly connected with decnet. The scsnode is the name of the system, 6 alphanum characters in size maximum end is the same as the DECnet nodename. The scssystemid is connected with the decnet address. A decnet address is of the form (area).(hostnr) where area is an integer of 1..63 and hostnr an integer of 1..1023. The syssystemid is computed as 1024*area + hostnr.
Both values may be changed. Google for modparams.dat (the file where those values are stored), sysgen.exe (the utility that modifies the parameters) and autogen.com which is a utility that helps tuning your system.
A lot is covered in a manual I wrote last year that describes the installation of the bridge program and the various system mqnagement tasks tjat are neede on VMS and Windows systems that run DECnet. Johnny Billquist runs DECnet and he has the latest copy of this manual.
Welcome to Hecnet and good luck!
Hans Vlems
Verzonden vanaf mijn draadloze BlackBerry -toestel
-----Original Message-----
From: Mark Benson <md.benson at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Wed, 15 Jun 2011 20:40:05
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: [HECnet] Introduction
Hi!
I'm new to the DEC/OpenVMS platform, but am hoping to join HECnet on recommendation from a friend who is (or at least was) more into this area of computing.
I am not seriously involved with DEC systems to any great extent, or a DEC-using professional, but I'm an avid enthusiast who thrives on investigating different platforms and OSs.
I am currently going through my first install of OpenVMS 8.3 and have hit the part where I need the SCSNODE and SCSSYSTEMID - I guess that's where I need details from HECnet. If I put something random in at the install can I change those post-install?
Also I would like to know details of how to build and run the DECnet bridge on Linux (if that's possible) and if, when using a DECnet, I can still use conventional TCP/IP on the OpenVMS machine.
As I said, I'm very new to this whole thing, so go easy on me :D!
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
Hi!
I'm new to the DEC/OpenVMS platform, but am hoping to join HECnet on recommendation from a friend who is (or at least was) more into this area of computing.
I am not seriously involved with DEC systems to any great extent, or a DEC-using professional, but I'm an avid enthusiast who thrives on investigating different platforms and OSs.
I am currently going through my first install of OpenVMS 8.3 and have hit the part where I need the SCSNODE and SCSSYSTEMID - I guess that's where I need details from HECnet. If I put something random in at the install can I change those post-install?
Also I would like to know details of how to build and run the DECnet bridge on Linux (if that's possible) and if, when using a DECnet, I can still use conventional TCP/IP on the OpenVMS machine.
As I said, I'm very new to this whole thing, so go easy on me :D!
--
Mark Benson
My Blog:
<http://markbenson.org/blog>
Follow me on Twitter:
http://twitter.com/mdbenson
"Never send a human to do a machine's job..."
Chrissie,
Apparently your IP address has changed because you are no longer
connected to GORVAX::. If you wish, you may connect to declab.net (in
the US). This system, gets around the fact that Multinet only supports
static addresses.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Chrissie Caulfield
Sent: Tuesday, March 22, 2011 11:21
To: hecnet at Update.UU.SE
Cc: Sampsa Laine
Subject: Re: [HECnet] Multinet to area 3
OK!
My IP address is 80.2.74.73 (should be in dynDNS as
chrissie.homelinux.net)
Chrissie
On 22/03/11 14:57, Sampsa Laine wrote:
If you want, I can set up a Multinet link for you as well to area 8.
My bridge to area 1 is down at the moment, however.
Sampsa
On 22 Mar 2011, at 14:53, Chrissie Caulfield wrote:
Thanks to Sampsa and DECUServe I now have my router up and running
again, but it doesn't seem to be talking to any of its multinet peers.
It's been a while so I'm not sure who it usually talks to, I think
LEGATO might have been one. The IP addresses are:
64.142.52.93.700& 78.86.123.31
if that helps ;-)
Chrissie
