I am very new here on this forum and just briefly, I started learning UNIX ssytems such as Solaris, AIX and etc...
Now, I wish to learn VMS.
Now, A friend of mine, sent me a VMS 7.3 for VAX CD and I had just downloaded the SIMH emulator. BUt, there documentation site is off-line and I wish someone here can guide me on how to boot this CD on this emulator on a Windows XP PC...I would appreciate all the detailed steps if possible on here. I tried googling this stuff, but no luck. I just need to find a way on how to boot this CD using this emulator and I need to know the commands for this.
Once booted, then I guess its downhill from there since the install itself takes at least 30 minutes I have been told by this friend of mine.
Perhaps, its more complicated than installing Solaris....But I got learning its ropes on that a few years ago.
Now, its time to learn some VMS.
ALso, when using this emulator, I need the GUI DEC-Windows installed since Im use to using the GUI on UNIX systems. Im kind of rusty on the VMS commands too.
I would appreciate the kind steps for this using this emulator to get a fell for this before I go ahead and get myself a REAL PC like VAX.
However, I am running Solaris. Will this work under Solaris too?
Now, I had downbloaded the Windows executables under my Windows box and I clicked on the VAX.exe
I just need to find out on how to boot this CD virtually.
VAX simulator V3.8-0
sim> boot dua3
Non-existent device
sim>
Edited by vmsfreak01 on June 19 2008 18:59
I was able to compile and run simh within a Solaris zone with little problem - save the network interface. If you're interested in network you'll probably want to make sure you have access to a (bridged?) ethernet device with a MAC address. If you have access to the global-zone on a box, you should be good to go.
Im almost there....Whats the next command after this prompt?
Remember, I am on WINDOWS not Linux, but I got most of the notes from the LINUX user guide...So what command wil lI have to use for this to backup?
EDIT: I did the following command now and still does not work.
$ BACKUP/IMAGE dua1:vms.iso/save_set dua1
%BACKUP-F-IMGFILSPE, /IMAGE specification must have only device name
If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
VAX simulator V3.8-0
sim> set rq0 rd54
sim> att rq0 new_vms.dsk
sim> set rq0 rd54
Unit already attached
sim> set rq1 cdrom
sim> att rq0 new_vms.dsk
sim> att rq1 vms.iso
sim> boot cpu
Loading boot code from ka655x.bin
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
YSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk
OpenVMS (TM) VAX Version X7G7 Major version id = 1 Minor version id = 0
b29;b30;%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM)
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 24-JUN-2008 11:45
Configuring devices . . .
Now configuring HSC, RF, and MSCP-served devices . . .
Please check the names of the devices which have been configured,
to make sure that ALL remote devices which you intend to use have
been configured.
If any device does not show up, please take action now to make it
available.
Available device DUA0: device type RD54
Available device DUA1: device type RRD40
Available device DUA2: device type RD54
Available device DUA3: device type RX50
Available device DLA0: device type RL01
Available device DLA1: device type RL01
Available device DLA2: device type RL01
Available device DLA3: device type RL01
Available device MSA0: device type MW_TSV05
Available device DYA0: device type RX02
Available device DYA1: device type RX02
Available device MUA0: device type TK50
Available device MUA1: device type TK50
Available device MUA2: device type TK50
Available device MUA3: device type TK50
Enter "YES" when all needed devices are available: y
%BACKUP-I-IDENT, Stand-alone BACKUP T7.2; the date is 24-JUN-2008 11:49:32.80
$
I got it..
The command was this below:
BACKUP/IMAGE/LOG DUA1:[000000]VMS073.B/SAVE DUA0:
Now, another issue, is SPACE...The installation failed because I do not have enought space as shown below. Now, is there any way I can make my virtual disk space big anough to install this?
Please review the installation errors as below. How can I correct this problem?
Space remaining on system disk: 172512 blocks
* Is this correct? (Y/N) y
Restoring OpenVMS library save set ...
%BACKUP-F-OPENIN, error opening DUA0:[000000]VMS073.C; as input
-RMS-E-FNF, file not found
Restoring OpenVMS library save set ...
%BACKUP-F-OPENIN, error opening DUA0:[000000]VMS073.C; as input
-RMS-E-FNF, file not found
A friend sent it to me and first, I extracted the CD contents using Nero Recorder and saved the Image file as VMS.ISO.
So, how do I resize this NEW_VMS.DSK?
Currently, I have new VIRTUAL DSK named vVAXSYS.DSK which has a total size of 777 MB...And I did the same SIMH commands as above and same issues appeared. The VMS.ISO (image) has a sie of 534MB.
So, how would I tell SIMH to use a total DSK size of at least 4GB? Can you please explain briefly? You have been helpful enough.
Actually, by reading the Installation manual, VMS is quite easy to install itself (if the correct requirements are meant)...The actual hard part of this is getting SIMH to install it...Or...even easier....I CAN BUY A VAX workstation on EBAY...Which would be easier than this.
Please explain regarding the creating of a bigger size.
Thx in advance.
Edited by vmsfreak01 on June 24 2008 10:40
Ok...you be the judge...Please review the mistakes below.
VAX simulator V3.8-0
sim> set rq0 rd54
sim> set rq1 cdrom
sim> att rq0 newvms.dsk
RQ: creating new file
sim> att rq1 vms.iso
sim> boot cpu
Loading boot code from ka655x.bin
u92;[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua1
(BOOT/R5:0 DUA1
2..
-DUA1
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
YSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk
OpenVMS (TM) VAX Version X7G7 Major version id = 1 Minor version id = 0
b29;b30;%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 24-JUN-2008 23:57
Configuring devices . . .
Now configuring HSC, RF, and MSCP-served devices . . .
Please check the names of the devices which have been configured,
to make sure that ALL remote devices which you intend to use have
been configured.
If any device does not show up, please take action now to make it
available.
Available device DUA0: device type RD54
Available device DUA1: device type RRD40
Available device DUA2: device type RD54
Available device DUA3: device type RX50
Available device DLA0: device type RL01
Available device DLA1: device type RL01
Available device DLA2: device type RL01
Available device DLA3: device type RL01
Available device MSA0: device type MW_TSV05
Available device DYA0: device type RX02
Available device DYA1: device type RX02
Available device MUA0: device type TK50
Available device MUA1: device type TK50
Available device MUA2: device type TK50
Available device MUA3: device type TK50
BACKUP/IMAGE/LOG DUA1:[000000]VMS073.B/SAVE DUA0:
DONE SCROLLING.....
%BACKUP-I-PROCDONE, operation completed. Processing finished at 25-JUN-2008 00
00:15.09
If you do not want to perform another standalone BACKUP operation,
use the console to halt the system.
If you do want to perform another standalone BACKUP operation,
ensure the standalone application volume is online and ready.
Enter "YES" to continue:
Enter "YES" to continue:
Simulation stopped, PC: 80A6EFB4 (ACBL #1F,#1,R3,80A6EF34)
sim> boot cpu
u92;[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua0
(BOOT/R5:0 DUA0
2..
-DUA0
1..0..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
YSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
OpenVMS (TM) VAX Version BI73-7G7 Major version id = 1 Minor version id = 0
b29;b30;%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
* Please enter the date and time (DD-MMM-YYYY HH:MM) 25-jun-2008 00:02
*********************************************************
%SYSTEM-W-TZGMT, your local timezone has defaulted to GMT
%SYSTEM-I-SETTZ, to set your local timezone use:
$ @SYS$MANAGER:UTC$TIME_SETUP.COM
*********************************************************
On MIN or UPGRADE system startup - CLUE is not run.
%%%%%%%%%%% OPCOM 25-JUN-2008 00:02:02.56 %%%%%%%%%%%
Operator _OPA0: has been enabled, username SYSTEM
%SYSTEM-I-BOOTUPGRADE, security auditing disabled
%LICENSE-F-EMTLDB, license database contains no license records
%%%%%%%%%%% OPCOM 25-JUN-2008 00:02:03.92 %%%%%%%%%%%
Message from user JOB_CONTROL
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 25-JUN-2008 00:02:03.93 %%%%%%%%%%%
Message from user JOB_CONTROL
-RMS-E-FNF, file not found
%SYSTEM-I-BOOTUPGRADE, security server not started
%%%%%%%%%%% OPCOM 25-JUN-2008 00:02:05.57 %%%%%%%%%%%
Message from user SYSTEM
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...
%SET-I-INTSET, login interactive limit = 1, current interactive value = 0
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
* Enter the volume label for this system disk [OVMSVAXSYS]:
* Enter name of drive holding the OpenVMS distribution media: dua0
* Is the OpenVMS media ready to be mounted? [N] y
Select optional software you want to install. You can install one
or more of the following OpenVMS or DECwindows components:
o OpenVMS library - 52200 blocks
o OpenVMS optional - 19000 blocks
o OpenVMS Help Message - 10400 blocks
o OpenVMS Management Station - 20000 blocks
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts - 6200 blocks
o DECnet-Plus networking - 80000 blocks
o DECnet Phase IV networking - 800 blocks
Space remaining on system disk: 224712 blocks
* Do you want to install the OpenVMS library files? (Y/N) y
Space remaining on system disk: 172512 blocks
* Do you want to install the OpenVMS optional files? (Y/N) y
Space remaining on system disk: 153512 blocks
The Help Message utility (MSGHLP) provides online explanations
and user actions for OpenVMS messages in place of the hardcopy
OpenVMS System Messages and Recovery Procedures Reference Manual,
which is now separately orderable.
The MSGHLP database file, MSGHLP$LIBRARY.MSGHLP$DATA,
consumes approximately 10400 blocks and will be
placed by default on your system disk in SYS$COMMON:[SYSHLP]
unless you specify an alternate device when prompted.
* Do you want to install the MSGHLP database? (Y/N) n
The OpenVMS Management Station is a client-server application that
provides OpenVMS system management capabilities through a client
application on a personal computer (PC) running Microsoft Windows.
The server application runs on OpenVMS systems and is automatically
installed as part of the OpenVMS operating system.
This option provides the files used to install the PC client software.
If you want to use the OpenVMS Management Station, you must install
these optional files on at least one OpenVMS system and then use one or
both of them to install the PC client on one or more PCs. There are two
files: TNT030_I.EXE for Intel systems (Windows 95 and Windows NT), and
TNT030_A.EXE for Alpha Windows NT systems.
The OpenVMS Management Station optional files consume approximately 20000
blocks and will be placed on your system disk in SYS$COMMON:[TNT.CLIENT].
* Do you want to install the optional OpenVMS Management Station files? (Y/N)
Space remaining on system disk: 133512 blocks
You can select DECwindows now, or you can use the DECW$TAILOR utility
to provide or remove DECwindows support after the installation.
Some media, TK50s in particular, can be very slow when tailoring on files
You might want to select DECwindows now and tailor off unwanted files lat
NOTE: This kit does NOT contain full DECwindows.
To obtain full DECwindows, you must also install the separate
layered product, DECwindows Motif for OpenVMS VAX.
V1.2-3 is the minimum version of DECwindows Motif for OpenVMS VAX
that can be used with OpenVMS VAX V7.3.
The DECwindows components provided in this kit requires approximately
34400 blocks, broken down as follows:
o DECwindows base support - 4400 blocks
o DECwindows workstation support - 23800 blocks
- 75 dots per inch video fonts - (included)
- 100 dots per inch video fonts (optional) - 6200 blocks
You must select the DECwindows base support option if
- you plan to run DECwindows software, or
- you are installing this kit on
* a workstation or
* an OpenVMS Cluster that contains workstations, or
- you want to provide font files for Xterminals.
If you are installing this kit on a system that includes Xterminals
and you do NOT select DECwindows base support, then you will have to use
the DECW$TAILOR utility to provide font files.
* Do you want the DECwindows base support? (Y/N) n
Beginning with OpenVMS V7.1, the DECnet-Plus kit is provided with
the OpenVMS operating system kit. Compaq strongly recommends that
DECnet users install DECnet-Plus. DECnet Phase IV applications are
supported by DECnet-Plus.
DECnet Phase IV is also provided as an option. Support for DECnet
Phase IV is available through a Prior Version Support Contract.
If you install DECnet-Plus and TCP/IP you can run DECnet
applications over a TCP/IP network. Please see the OpenVMS
Management Guide for information on running DECnet over TCI/IP.
If you plan to install DECnet Phase IV do NOT select DECnet-Plus.
* Do you want to install DECnet-Plus? (Y/N) n
* Do you want to install DECnet Phase IV? (Y/N) n
The following options will be provided:
OpenVMS library
OpenVMS optional
OpenVMS Management Station Software -- PC files
Space remaining on system disk: 133512 blocks
* Is this correct? (Y/N) y
Restoring OpenVMS library save set ...
%BACKUP-F-OPENIN, error opening DUA0:[000000]VMS073.C; as input
-RMS-E-FNF, file not found
Restoring OpenVMS library save set ...
%BACKUP-F-OPENIN, error opening DUA0:[000000]VMS073.C; as input
-RMS-E-FNF, file not found
Im not going to name names, but its from one of those popular VMS hosts which newbies connect to when they want to learn VMS...But he told me that this CD DOES NOT contain any PAK licenses sa I have to get them myself here..That would be illegel if he did.
So, here the output: It seems to be hanging..
%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
YSBOOT-W-SYSBOOT Can not map PAGEFILE.SYS on the System Disk
OpenVMS (TM) VAX Version X7G7 Major version id = 1 Minor version id = 0
b29;b30;%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
%SYSINIT-E, %SYSINIT, error opening system dump file, status = 00000910
%SYSINIT, primary PAGEFILE.SYS not found; system initialization continuing
%SYSINIT, no dump file - error log buffers not saved
%SYSTEM-I-MOUNTVER, DUA1: has been write-locked. Mount verification in progress
.
Hi
It worked...I manged to install...
The issue was....that I had problems MOUNTING from the media without the CD in my tray...
Now....ANother issue....
Im sorry, but I logged out of the SIMH, and restarted by booting the CPU and then BOOTING into DUA0 and dont tell me I have to go through the same installing process as before? after I logout from the SIMH session??
So once I logoff, I have to redo this whole procedure from scratch???
(after logging out from the SIMH session and then trying to boot again to get the USERNAME/PASSWORD prompt...but IT DOESNT)
Heres what it shows:
VAX simulator V3.8-0
sim> boot cpu
Loading boot code from ka655x.bin
u92;[c
KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
>>>boot dua0
(BOOT/R5:0 DUA0
2..
?4D DEVOFFLINE, DUA
HALT instruction, PC: 00000C1A (MOVL (R11),SP)
sim>
Edited by vmsfreak01 on June 25 2008 07:44
Ok, to make it simple....I wrote down the commands so I do not have to do all this process over again like below...So, in the meantime, I will do it manually which does not take that much time anyway with the following commands:And.....It does work!!!!!
Also, instead of SYSTEM account...how do I add myself an own account?? SYSTEM is like ROOT on UNIX...But VMS uses SYSTEM as an ADMIN or SUPERUSER account...I want to create my own username account with password...Can I do this at all or I need to have these PAKs in order to achieve this?
VAX simulator V3.8-0
sim> set rq0 ra90
sim> att rq0 new_vms.dsk
sim> att rq1 vms.iso
sim> boot cpu
You said that you got the installation working, but just in case there is still an issue with that since you may not have yet successfully booted the system, I just wanted to point out what was causing the save-sets to be missing during installation.
You had this part of the installation:
* Enter name of drive holding the OpenVMS distribution media: dua0
Here you should have said dua1: since that's where it'd be copying the VMS073.B and .C savesets from onto DUA0:. They weren't on your virtual hard drive, so that's why the installation had failed.
I know.....THAT was the issue...But I got it working again...
I guess you beat me on my previus post above that I just posted...
Hi,
Ok, to make it simple....I wrote down the commands so I do not have to do all this process over again like below...So, in the meantime, I will do it manually which does not take that much time anyway with the following commands:And.....It does work!!!!!
Also, instead of SYSTEM account...how do I add myself an own account?? SYSTEM is like ROOT on UNIX...But VMS uses SYSTEM as an ADMIN or SUPERUSER account...I want to create my own username account with password...Can I do this at all or I need to have these PAKs in order to achieve this?
VAX simulator V3.8-0
sim> set rq0 ra90
sim> att rq0 new_vms.dsk
sim> att rq1 vms.iso
sim> boot cpu
BOOT DUA0...
Edited by vmsfreak01 on June 25 2008 10:32
Ok, to make it simple....I wrote down the commands so I do not have to do all this process over again like below...So, in the meantime, I will do it manually which does not take that much time anyway with the following commands:And.....It does work!!!!!
Put the commands in a text file, using the text editor of your choice, and save them in a file with the same name as the SIMH VAX executable with the extension .INI . Then they will be executed on SIMH startup.
Also, instead of SYSTEM account...how do I add myself an own account?? SYSTEM is like ROOT on UNIX...But VMS uses SYSTEM as an ADMIN or SUPERUSER account...I want to create my own username account with password...Can I do this at all or I need to have these PAKs in order to achieve this?
Without at least a VAX-VMS PAK, only SYSTEM will be allowed to log in (and only through the console terminal) - to enter PAKs.
An easy way to create accounts is the command procedure SYS$EXAMPLE:ADDUSER.COM.
I did:
Ok, for example: What if I want to create a local account username called MYUSERNAME and then set a password for it?
Please post the commands.
$ SYS$EXAMPLE:ADDUSER.COM
$
%DCL-W-NOLBLS, label ignored - use only within command procedures
\SYS$EXAMPLE:\
%DCL-W-IVVERB, unrecognized command verb - check validity and spelling
\ADDUSER\
Put the commands in a text file, using the text editor of your choice, and save them in a file with the same name as the SIMH VAX executable with the extension .INI . Then they will be executed on SIMH startup
OK, but do I have to put this file into the same folder as the VAX.EXE?
Edited by vmsfreak01 on June 25 2008 11:51
Martin: An .ini file? interesting. That initialization file isn't documented in the simh manuals.
It's documented in the SimH Users' Guide, chapter 1 (search for ".ini" ), but I admit it's easily overlooked:
The simulator interprets the arguments on the command line, if any, as the file name and arguments for a DO command:
% pdp10 {switches} {<startup file> {arg,arg,...}}
If no file is specified on the command line, the simulator looks for a startup file consisting of the simulator name (including its path components) plus the extension .ini. If a startup file is specified, either on the command line or implicitly via the .ini capability, it should contain a series of non-interactive simulator command, one per line. These commands can be used to set up standard parameters, for example, disk sizes.
One caveat: this doesn't work on OpenVMS Alpha and I64, as the version number is not accounted for when splitting an ".exe" extension from the simulator's file name. I have a 3-line patch to correct this (scp.c:652):
strncpy (nbuf + 1, argv[0], PATH_MAX + 1); /* copy sim name */
#ifdef __VMS /* when under OpenVMS... */
if (np = strrchr(nbuf, ';')) *np = 0; /* remove version number */
#endif
if (np = match_ext (nbuf, "EXE")) *np = 0; /* remove .exe */
Thanks to all you here who had supported me inj going through this.
The user command does not work, so you I have to use the UAC commands to do this.
$ @SYS$EXAMPLE:ADDUSER.COM
%DCL-E-OPENIN, error opening SYS$EXAMPLE:[SYSMGR]ADDUSER.COM; as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
For example, I want to create a username called VMSFREAK with a password. Can you please post the commands for this?
Regarding the TXT file that I created:
My text file in Windows Notepad look like this and I renamed the extenstion to INI and and it did not work. It gave me DEVICE DUA0 NOT OFFLINE or something like that: Please review:
Now, when I do this manually in SIMH, it works, it boots directly to VMS.
Please bare with me. I know this is new to me...Esp. coming from a Windows enviroment. I will have to download every Systems manual on VMS which Im doing now.
VAX simulator V3.8-0
sim> set rq0 ra90
sim> att rq0 new_vms.dsk
sim> att rq1 vms.iso
sim> boot cpu
Hi guys...I did a test from the VMS Managers Guide.
Please review on whats going on here....I created a username JONES with a password, then logged on into that account and gave the password and it does not work. Please help.
So why it does not want to login with the correct username and password that I had set for this user JONES??
$ SET PROCESS/PRIVILEGE=SYSPRV
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> ADD JONES/PASSWORD=LPB57WM/UIC=[014,1]
Security alarm (SECURITY) and security audit (SECURITY) on HOBBY, system id: 102
5
Auditable event: Local interactive login failure
Event time: 26-JUN-2008 08:45:21.62
PID: 00000112
Process name: _OPA0:
Username: JONES
Terminal name: OPA0:, _OPA0:
Status: %LOGIN-F-DISUSER, account is disabled
UAF> show jones
Username: JONES Owner:
Account: UIC: [14,1] ([JONES])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[USER]
LGICMD: LOGIN
Flags: DisUser
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 6 Login Fails: 3
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), (none) (non-interactive)
Please bare with me. I know this is new to me...Esp. coming from a Windows enviroment. I will have to download every Systems manual on VMS which Im doing now.
Having said that, a VMS installation clearly isn't your normal everyday user's task.
My text file in Windows Notepad look like this and I renamed the extenstion to INI and and it did not work. It gave me DEVICE DUA0 NOT OFFLINE or something like that:
- "it did not work" isn't a very accurate error description
- "or something like that" isn't either.
Please post exactly what you did and exactly what error messages occured.
The commands you posted look ok. Be sure to specify the same type of disk in the SET RQ0 command every time.
Next time start SIMH in a DOS box and add the "-v" option to the command. Then every SIMH command executed from the INI file will be printed.
$ @SYS$EXAMPLE:ADDUSER.COM
%DCL-E-OPENIN, error opening SYS$EXAMPLE:[SYSMGR]ADDUSER.COM; as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
Sorry, typo on my part: it's SYS$EXAMPLES:ADDUSER.COM
I created a username JONES with a password, then logged on into that account and gave the password and it does not work.
So why it does not want to login with the correct username and password that I had set for this user JONES??
$ SET PROCESS/PRIVILEGE=SYSPRV
$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF> ADD JONES/PASSWORD=LPB57WM/UIC=[014,1]
Security alarm (SECURITY) and security audit (SECURITY) on HOBBY, system id: 102
5
Auditable event: Local interactive login failure
Event time: 26-JUN-2008 08:45:21.62
PID: 00000112
Process name: _OPA0:
Username: JONES
Terminal name: OPA0:, _OPA0:
Status: %LOGIN-F-DISUSER, account is disabled
UAF> show jones
Username: JONES Owner:
Account: UIC: [14,1] ([JONES])
CLI: DCL Tables: DCLTABLES
Default: SYS$SYSDEVICE:[USER]
LGICMD: LOGIN
Flags: DisUser
Primary days: Mon Tue Wed Thu Fri
Secondary days: Sat Sun
No access restrictions
Expiration: (none) Pwdminimum: 6 Login Fails: 3
Pwdlifetime: 90 00:00 Pwdchange: (pre-expired)
Last Login: (none) (interactive), (none) (non-interactive)
Multiple things if you're not taking the ADDUSER.COM route:
- You should set the UAF field for the user's login directory (qualifiers /DEVICE and /DIRECTORY)
- You have to create the user's login directory by hand, e.g.
- All UAF fields not explicitly stated in the ADD command are taken from the DEFAULT account (think template), including the "Flags" field. This one contains "DisUser" for DEFAULT which means the account is disabled. Change by
BTW: Your minimum INI file should probably look like
LOAD -r KA655x.BIN
LOAD -n NVRAM.BIN
SET RQ0 RA90
ATTACH RQ0 new_vms.dsk
SET RQ1 RRD40
ATTACH RQ1 vms.iso
SET CPU IDLE=VMS
BOOT CPU
The first command loads the boot ROM (the file comes with the SIMH distribution in the VAX sub-directory), the second one loads the non-volatile ROM (i.e. any SETtings you have made in the console). As they are written above, i.e. without a path, the files have to be located in the working directory that SIMH executes in.
malmberg August 04 2022 No more VAX hobbyist licenses.
Community licenses for Alpha/IA64/X86_64 VMS Software Inc.
Commercial VMS software licenses for VAX available from HPE.
ozboomer July 20 2022 Just re-visiting.. No more hobbyist licenses? Is that from vmssoftware.com, no 'community' licenses?
valdirfranco July 01 2022 No more hobbyist license...sad
mister_wavey February 12 2022 I recall that the disks failed on the public access VMS systems that included Fafner
parwezw January 03 2022 Anyone know what happened to FAFNER.DYNDS.ORG?
I had a hobbyist account here but can longer access the site.
gtackett October 27 2021 Make that DECdfs _2.1A_ for Vax
gtackett October 27 2021 I'm looking for DECdfs V2.4A kit for VAX.
Asking here just in case anyone is still listening.
MarkRLV September 17 2021 At one time, didn't this web site have a job board? I would love to use my legacy skills one last time in my career.
malmberg January 18 2021 New Hobbyist PAKs for VAX/VMS are no longer available according to reports. Only commercial licenses are reported to be for sale from HPE
dfilip January 16 2021 Can someone please point me to hobbyist license pak? I'm looking for VAX/VMS 7.1, DECnet Phase IV, and UCX/TCPIP ... have the 7.1 media, need the license paks ... thanks!
