There is a file in sys$startup: called DECW$mumble-private-setup.com
Look at the output od SHOW LOGI/SYS DECW* for a llogical name that has refreshrate in it. Or SHO LOG/EXEC DECW*
In the private setup file enter the line
DEFINE/SYSTEM <logicalname> 60
(Or /EXEC, depending on which table holds the DECW logical names)
Hans
Verzonden vanaf mijn draadloze BlackBerry -toestel
-----Original Message-----
From: Mark Benson <md.benson at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 17 Jun 2011 13:56:16
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Introduction
I will have to learn how the darned system works before I look further into this I think.
Tonight's task, now I beat DECwindows into working, is to work out how to change at least the refresh rate of the X server as my LCD is not liking 70Hz (shuts the signal off after 5mins). I have the docs for DW to hand but they aren't awfully clear. Time to learn EVE and delve into some config files!
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
Mark,
Always go with the DVNETRTG version for DECnet. This will allow you to become a router if you ever need to be. I would ignore the DVNETEND license entirely.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Kari Uusim ki
Sent: Friday, June 17, 2011 00:32
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Introduction
Hi Mark,
The base set of licenses you'll need for using a VMS machine like a workstation consists of:
OPENVMS-ALPHA
DW-MOTIF (DECwindows)
UCX (TCP/IP)
DVNETEND (DECnet)
Then if you need more features, you can load more licenses.
When you want to disable DECwindows to start when you boot the machine, just edit the SYS$MANAGER:SYSTARTUP_VMS.COM and remove the comment (!) from the line $ DEFINE DECW$IGNORE_DECWINDOWS TRUE
like above.
One thing which is usually helpful when you get in some kind of trouble is to keep the console functions tied to the serial port (SET CONSOLE SERIAL at the console prompt [>>>]). That way you'll always have a way to log into the machine and use a command line session. The additional benefit is to follow what happens during the early self tests of the machine and the whole startup of VMS. That doesn't affect the DECwindows usage on the graphics port.
Regards,
Kari
On 16.6.2011 23: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?
I will have to learn how the darned system works before I look further into this I think.
Tonight's task, now I beat DECwindows into working, is to work out how to change at least the refresh rate of the X server as my LCD is not liking 70Hz (shuts the signal off after 5mins). I have the docs for DW to hand but they aren't awfully clear. Time to learn EVE and delve into some config files!
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
You can run the license file as a DCL procedure to register the new licenses every year. Unfortunately the license database is cumulative and if you don't delete expired licenses, you'll soon have several hundred of them. Therefore the procedure which registers the new licenses and deletes the old ones are most useful.
It is also easier to handle the license database if you don't register unnecessary licenses.
Regards,
Kari
On 17.6.2011 13:55, Mark Benson wrote:
Even if you don't recreate the license database every year, as far as I can see the license file is just a (DCL?) script that runs 'LICENSE REGISTER' for each License you are granted. 5 mins and a decent editor and you could easily create one to rip out each license by name too, right? Can LICENSE do that? I think it can IIRC.
LMF can remove licenses, provided that they are not loaded. The remove (or delete, can't remember) command needs the product name. The situation gets complex if more than one PAK for a product exists. There's no wilcard option, you must specify the authorization code to single out a PAK.
It may be done in DCL. The License/Issue command accepts wildcards and unloads the license. It can even issue a DCL script (license/issue/command/out=file.name *Y
Next modify that output file in DCL and replace register with delete (or even better. with the batch editor of course)
A lot of work! It's a lot easier to remove sys$system:*.ldb.1 ...
Hans
Verzonden vanaf mijn draadloze BlackBerry -toestel
-----Original Message-----
From: Mark Benson <md.benson at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 17 Jun 2011 11:55:07
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Introduction
Even if you don't recreate the license database every year, as far as I can see the license file is just a (DCL?) script that runs 'LICENSE REGISTER' for each License you are granted. 5 mins and a decent editor and you could easily create one to rip out each license by name too, right? Can LICENSE do that? I think it can IIRC.
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 17 Jun 2011, at 10:53, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
On 17.6.2011 12:48, Rok Vidmar wrote:
... it is a real pain to delete them all when you have to renew them each year.
No pain at all if you create License Database anew each year.
--
Regards, Rok
.
Or then you can create a DCL procedure which does the job. :)
Regards,
Kari
On 17/06/11 11:55, Mark Benson wrote:
Even if you don't recreate the license database every year, as far as I can see the license file is just a (DCL?) script that runs 'LICENSE REGISTER' for each License you are granted. 5 mins and a decent editor and you could easily create one to rip out each license by name too, right? Can LICENSE do that? I think it can IIRC.
IIRC the issue is when you start getting multiple licenses for the same product name, as you then have to differentiate them by application date/expired status.
There was a DCL procedure on either comp.os.vms or VMS Hobbyist site which you could run against any database and it would remove all expired licenses. That's the lazy approach. I like it ;)
Mark.
Even if you don't recreate the license database every year, as far as I can see the license file is just a (DCL?) script that runs 'LICENSE REGISTER' for each License you are granted. 5 mins and a decent editor and you could easily create one to rip out each license by name too, right? Can LICENSE do that? I think it can IIRC.
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 17 Jun 2011, at 10:53, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
On 17.6.2011 12:48, Rok Vidmar wrote:
... it is a real pain to delete them all when you have to renew them each year.
No pain at all if you create License Database anew each year.
--
Regards, Rok
.
Or then you can create a DCL procedure which does the job. :)
Regards,
Kari
On 17.6.2011 12:48, Rok Vidmar wrote:
... it is a real pain to delete them all when you have to renew them each year.
No pain at all if you create License Database anew each year.
--
Regards, Rok
.
Or then you can create a DCL procedure which does the job. :)
Regards,
Kari
... it is a real pain to delete them all when you have to renew them each year.
No pain at all if you create License Database anew each year.
--
Regards, Rok
Hi Mark,
The base set of licenses you'll need for using a VMS machine like a workstation consists of:
OPENVMS-ALPHA
DW-MOTIF (DECwindows)
UCX (TCP/IP)
DVNETEND (DECnet)
Then if you need more features, you can load more licenses.
When you want to disable DECwindows to start when you boot the machine, just edit the SYS$MANAGER:SYSTARTUP_VMS.COM and remove the comment (!) from the line
$ DEFINE DECW$IGNORE_DECWINDOWS TRUE
like above.
One thing which is usually helpful when you get in some kind of trouble is to keep the console functions tied to the serial port (SET CONSOLE SERIAL at the console prompt [>>>]). That way you'll always have a way to log into the machine and use a command line session. The additional benefit is to follow what happens during the early self tests of the machine and the whole startup of VMS. That doesn't affect the DECwindows usage on the graphics port.
Regards,
Kari
On 16.6.2011 23: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?
