hello.
I´ve been tracking these posts. Now I got my OVMS Kit CD and try start up the system.
Although I´ve been reading all threads, I got an error, and any tip about it will be welcome.
I´ve used a .ini with some comm as Marc told. The last lines worry me up.
TIA.
VAX simulator V3.8-0
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.
>>>b dua1
(BOOT/R5:0 DUA1
2..
-DUA1
?43 FILESTRUCT, DUA <----------------------that error
HALT instruction, PC: 00000C1A (MOVL (R11),SP)
sim>
In fact, maybe I need to read a little bit.
My machine has an IDE C: drv, a DVD/CD D: drv and a SATA (F: G
I had same problem "vmsfreak" got.
I did try, (following some posts, and searching google), to boot simh as DUA0 TO DUA3. While getting a "DEVOFFLINE" msg I understand that device is off line, or not recognized, but about file struct ???
I am plannig to change my OS base (at momment Win XP), Maybe linux(any flavor), solaris or opensolaris. But, first I´d like get some progress.
Any hint about some reading I´ll apreciate.
My ini file is like that
LOAD -r KA655x.BIN
SET RQ0 RA90
ATTACH RQ0 new_vms.dsk
SET RQ1 RRD40
ATTACH RQ1 vms.iso
SET CPU IDLE=VMS
BOOT CPU
Hi,
As I told, maybe I need some tech reading...
I got my OVMS cd from montagar.
I just thought that following these basic steps I´d get some success starting up the sys. My mistake...
I need to understand how simh see my real devices and get them working properly as a vax. E.g. I boot simh from Crv with OVMS CD (kit from montagar) in Drv. This last one doesnt seems to be recognized.
Problably, it is not that simple.
Where di I find any tech info about these device in simh?
I need to understand how simh see my real devices and get them working properly as a vax. E.g. I boot simh from C: drv with OVMS CD (kit from montagar) in D: drv. This last one doesnt seems to be recognized.
Problably, it is not that simple.
One shortcoming of SIMH on Windows (as opposed to *ix) is that it can't handle physical devices, i.e. all your "VAX disks" have to be container files on the Windows C:, D:, whatever drives. So your INI file ATTACH statements have to have filenames, with the files containing images of the VAX disks or CDs.
As I mentioned in a comment on Hoff's page about SIMH under OS X (sorry, Hoff, for spoiling it with M$ infos), to get your VAX CD's contents into a container file, you can use dd for Windows.
Where do I find any tech info about these device in simh?
The device types (values for the SET RQx type) and size informations for "real" hard disks are in the SIMH source file PDP11/pdp11_rq.c. You can use the RAUSER type, as described in the PDP-11 SIMH doc.
thanks, I´ll try that.
This seems to mean I´ll have some trouble working with files/data.
Any linux distro goes well with simh? Slackware/Ubuntu is good choice?!
Hello, Stephen.
Huh...I didnt understand exactly what you mean...
I ran dd...It seems to generate an .iso file ok, but at end gave an "error reading file = 87 - Incorrect params", although I can see the 665600Kb iso file.
I think it´s time to test it.
I also downloaded some manual´s and other docs...
Hello, Martin, Stephen..
I think I got some success. Even as I reported an error on dd copy, everything seems to be ok. "dd" worked fine, generating the vms.iso, and my .ini file looks like that:
**************
LOAD -r KA655x.BIN
set rq0 rd54
att rq0 new_vms.dsk
set rq1 cdrom
att rq1 vms.iso
b cpu
****************
first boot dua1
standalone backup
issued ---->BACKUP/IMAGE/LOG DUA1:[000000]VMS073.B/SAVE DUA0:
second boot dua0
installed.
There is some line indicating error, but after all it seems to be installed, as shown below:
*******************************************
TIME ZONE SPECIFICATION -- Main Time Zone Menu
1) Australia 11) GMT 21) Mexico 31) Turkey
2) Brazil 12) Greenwich 22) NZ 32) UCT
3) CET 13) Hong Kong 23) NZ-CHAT 33) US
4) Canada 14) Iceland 24) Navajo 34) UTC
5) Chile 15) Iran 25) PRC 35) Universal
6) Cuba 16) Israel 26) Poland 36) W-SU
7) EET 17) Jamaica 27) ROC 37) WET
8) Egypt 18) Japan 28) ROK 38) Zulu
9) Factory 19) Libya 29) Singapore
10) GB-Eire 20) MET 30) SystemV
0) None of the above
Select the number above that best describes your location: 2
You selected Brazil as your time zone.
Is this correct? (Yes/No) [YES]:
Brazil Time Zone Menu
1) Acre 2) DeNoronha 3) East 4) West
0) None of the above
Select the number above that best describes your location: 3
You selected Brazil/East as your time zone.
Is this correct? (Yes/No) [YES]:
Default Time Differential Factor for standard time is -3:00.
Default Time Differential Factor for daylight saving time is -2:00.
The Time Differential Factor (TDF) is the difference between your
system time and Coordinated Universal Time (UTC). UTC is similar
in most repects to Greenwich Mean Time (GMT).
The TDF is expressed as hours and minutes, and should be entered
in the hh:mm format. TDFs for the Americas will be negative
(-3:00, -4:00, etc.); TDFs for Europe, Africa, Asia and Australia
will be positive (1:00, 2:00, etc.).
Running AUTOGEN to compute the new SYSTEM parameters ...
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.
%AUTOGEN-I-NEWFILE, Previous contents of SYS$SYSTEM:CLU$PARAMS.DAT have
been copied to SYS$SYSTEM:CLU$PARAMS.OLD. You may wish to purge
SYS$SYSTEM:CLU$PARAMS.OLD.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GETDATA phase has successfully completed.
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.
You may wish to purge this file.
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]PAGEFILE.SYS;1 extended
%SYSGEN-I-EXTENDED, SYS$SYSROOT:[SYSEXE]SWAPFILE.SYS;1 extended
%SYSGEN-I-CREATED, DUA0:[SYS0.SYSEXE]ERRORLOG.DMP;1 created
******************
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the
information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT
******************
%AUTOGEN-I-REPORT, AUTOGEN has produced some informational messages which
have been stored in the file SYS$SYSTEM:AGEN$PARAMS.REPORT. You may
wish to review the information in that file.
%AUTOGEN-I-END, GENFILES phase has successfully completed.
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.
The system is shutting down to allow the system to boot with the
generated site-specific parameters and installed images.
The system will automatically reboot after the shutdown and the
installation will be complete.
%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
-RMS-E-FNF, file not found
SHUTDOWN message from user SYSTEM at Batch 19:45:32
The system will shut down in 0 minutes; back up SOON. Please log off.
Reboot system with AUTOGENerated parameters
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
HALT instruction, PC: 81211709 (MOVB 400(R1),R0)
sim> B 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.
>>>B 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 V7.3 Major version id = 1 Minor version id = 0
b29;b30;%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
%STDRV-I-STARTUP, OpenVMS startup begun at 14-SEP-2008 19:47:21.88
%RUN-S-PROC_ID, identification of created process is 00000106
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:31.80 %%%%%%%%%%%
Operator _MRXBBS$OPA0: has been enabled, username SYSTEM
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:31.81 %%%%%%%%%%%
Logfile has been initialized by operator _MRXBBS$OPA0:
Logfile is MRXBBS::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:32.05 %%%%%%%%%%%
Message from user AUDIT$SERVER on MRXBBS
%AUDSRV-I-NEWSERVERDB, new audit server database created
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:32.15 %%%%%%%%%%%
Message from user AUDIT$SERVER on MRXBBS
%AUDSRV-I-REMENABLED, resource monitoring enabled for journal SECURITY
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:32.15 %%%%%%%%%%%
Message from user AUDIT$SERVER on MRXBBS
%AUDSRV-I-NEWOBJECTDB, new object database created
%SET-I-NEWAUDSRV, identification of new audit server process is 0000010C
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:32.35 %%%%%%%%%%%
Message from user JOB_CONTROL on MRXBBS
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:32.36 %%%%%%%%%%%
Message from user JOB_CONTROL on MRXBBS
-RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:34.04 %%%%%%%%%%%
Message from user SYSTEM on MRXBBS
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:34.06 %%%%%%%%%%%
Message from user SYSTEM on MRXBBS
%SECSRV-E-NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
%RMS-E-FNF, file not found
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:34.10 %%%%%%%%%%%
Message from user SYSTEM on MRXBBS
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:34.11 %%%%%%%%%%%
Message from user SYSTEM on MRXBBS
%SECSRV-I-SERVERSTARTINGU, security server starting up
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:34.21 %%%%%%%%%%%
Message from user SYSTEM on MRXBBS
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting u
p
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:36.78 %%%%%%%%%%%
Message from user SYSTEM on MRXBBS
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$MRXBBS.LM$JOURNAL)
%RMS-E-FNF, file not found
TP server process waiting
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:37.25 %%%%%%%%%%%
Message from user AUDIT$SERVER on MRXBBS
Security alarm (SECURITY) and security audit (SECURITY) on MRXBBS, system id: 10
25
Auditable event: Audit server starting up
Event time: 14-SEP-2008 19:47:37.19
PID: 00000103
Username: SYSTEM
%STARTUP-I-AUDITCONTINUE, audit server initialization complete
The OpenVMS VAX system is now executing the site-specific startup commands.
%%%%%%%%%%% OPCOM 14-SEP-2008 19:47:37.75 %%%%%%%%%%%
Message from user AUDIT$SERVER on MRXBBS
Security alarm (SECURITY) and security audit (SECURITY) on MRXBBS, system id: 10
25
Auditable event: Identifier added
Event time: 14-SEP-2008 19:47:37.70
PID: 00000103
Process name: STARTUP
Username: SYSTEM
Process owner: [SYSTEM]
Image name: MRXBBS$DUA0:[SYS0.SYSCOMMON.][SYSEXE]AUTHORIZE.EXE
Identifier name: SYS$NODE_MRXBBS
Identifier value: %X80010000
Attributes: none
%UAF-I-RDBADDMSG, identifier SYS$NODE_MRXBBS value %X80010000 added to rights da
tabase
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
SYSTEM job terminated at 14-SEP-2008 19:47:39.11
Accounting information:
Buffered I/O count: 1536 Peak working set size: 1382
Direct I/O count: 599 Peak page file size: 4834
Page faults: 5035 Mounted volumes: 0
Charged CPU time: 0 00:00:13.99 Elapsed time: 0 00:00:19.02
Welcome to OpenVMS (TM) VAX Operating System, Version V7.3
Username: SYSTEM
Password:
u92;[cu92;\u92;Zu92;[0c OpenVMS (TM) VAX Operating System, Version V7.3
%SET-W-NOTSET, error modifying OPA0:
-SET-I-UNKTERM, unknown terminal type
$
Have you any comment to do?
There are some works to do now. I need to add new basic user; start the graphical environment.
I´m following several manual´s/faq´s and doc´s, and hope get this goals reached. Any hint on this?
There is some line indicating error, but after all it seems to be installed, as shown below:
Some error messages are to be expected, as the VMS system starting isn't yet configured, e.g.:
%AUTOGEN-W-REPORT, Warnings were detected by AUTOGEN. Please review the
information given in the file SYS$SYSTEM:AGEN$PARAMS.REPORT
%OPCOM-W-NOOPCOM, the request was not sent, the OPCOM process is not running
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped
%JBC-E-OPENERR, error opening SYS$COMMON:[SYSEXE]QMAN$MASTER.DAT;
%SYSBOOT-W-SYSBOOT Can not map SYSDUMP.DMP on the System Disk
The text following says it all...
OpenVMS VAX V7.3
You have SUCCESSFULLY installed the OpenVMS VAX Operating System.
Congratulations!
Have you any comment to do?
There are some works to do now. I need to add new basic user; start the graphical environment.
I´m following several manual´s/faq´s and doc´s, and hope get this goals reached. Any hint on this?
A graphical environment (i.e. DECwindows) will only work with SIMH when you use the networking variant of SIMH, configure TCP/IP and DECwindows correctly, and - to connect to an X server local to the host machine (to be installed, too, at least for Windows!) - install and configure correctly the OpenVPN TAP-Win32 adapter.
As for administering a VMS (e.g. create a user), there's the System Manager's manual and lots of other resources. But that's not fodder for a discussion forum like this.
cu,
Martin
Oh, and:
Hoff wrote:
And screen management is busted in the default OPA0: console window interface in simh on Microsoft Windows; the MSDOS command environment doesn't provide terminal emulation.
What he's refering to here is that you will not be able to do any editing on the VMS machine (or at least, no screen mode editing as opposed to line mode) when you leave SIMH's VAX console to the DOS box. Better to SET CONSOLE TELNET=12001 in your INI file and connect to the console (on port 12001 in this example) through a terminal emulation program, e.g. PuTTY.
Ok, Martin...
Thanks a lot...
I´ll see what I get...
BTW, about the size of device on vms environment, I noticed that there was a limited space on a "virtual" disk RQ0.
But this I´ll try later.
BTW, about the size of device on vms environment, I noticed that there was a limited space on a "virtual" disk RQ0.
You set RQ0's / DUA0's type to RA90 which means that it's a 1.1 GB drive. Once you fix a disk type, the disk size is limited/fixed, of course. Or am I grossly misunderstanding something here?
All these stuff are documented in user manual ??
If I change "disk type" RQ0 to RA90 means re-install VMS?
If so...well,...ok...
I´ll go ahead and if needed I´ll take ir again from begining.
What is the minimum to run simh and vms? I´m afraid, ´cause I have a lot of info on my machine and dont want lost it all....
...
The disk types: yes. The sizes that go with the disk types: no.
There's a list on NetBSD web pages, or you ahve to dive into the Simh source code.
If I change "disk type" RQ0 to RA90 means re-install VMS?
Yes.
If so...well,...ok...
I´ll go ahead and if needed I´ll take ir again from begining.
You don't have to.
- Create another virtual disk RQ2 with the disk type and any file name you want.
- Boot your VAX from the CD-ROM again, and backup your installed system to the newly created DUA2 disk using
$$$ BACKUP/IMAGE DUA0: DUA2:
- Shutdown and boot again, this time specifying DUA2 as the boot device
What is the minimum to run simh and vms? I´m afraid, ´cause I have a lot of info on my machine and dont want lost it all....
...
If you've really specified a RD54 as DUA0 (it has about 154MB) that's probably a low bound. I've used RA82 frequently (623MB), because this fits onto a CDROM. RA92 (1.5GB) is as big as you can get with the supported disk types. Using RAUSER (described in SIMH's PDP-11 manual), you can get as big as you want.
Hoff wrote:
AFAIK, the driver didn't include a table of names to sizes.
Hoff, setting the disk type is a SIMH thing, nothing to do with VAX. The tables are in PDP11/pdp11_rq.c in the SIMH sources.
What is the minimum to run simh and vms? I´m afraid, ´cause I have a lot of info on my machine and dont want lost it all....
...
Thanks the info, but I did mean what the minimum reqs. (cpu, speed, ram) to run simh with OVMS Vax. This is because I have some others machines, and I´d like to try vms on them too.
Even so, I´ll take a look about the disks.
Looking what you are telling me, maybe I must pick the source and rebuild it with (??) some changes, to fit my purpose.
I´ll dig up and see.
Ok.
tks.
marx
I apologize to all of you. The misunderstandings were not intentional - not enough coffee or something...
but I did mean what the minimum reqs. (cpu, speed, ram) to run simh with OVMS Vax. This is because I have some others machines, and I´d like to try vms on them too.
I have SIMH running on my notebook (nice to always carry a VMS system): 1.5GHz Pentium M, 512 MB RAM, but have used it on slower machines, too. Of course, it's better with more CPU power. The regular emulated VAX runs with 64MB of (emulated) RAM, so this is not the primary concern.
Even so, I´ll take a look about the disks.
Looking what you are telling me, maybe I must pick the source and rebuild it with (??) some changes, to fit my purpose.
Errr... no. Could you elaborate on that, please?
Hoff wrote:
What I've just now found is the -L flag on the RA8USER device, and now if I can figure out how (and if) that works
Looking what you are telling me, maybe I must pick the source and rebuild it with (??) some changes, to fit my purpose.
Errr... no. Could you elaborate on that, please?
Sorry, my english is terrible...
I mean...maybe I need to get the simh source code, take a look on it, make some changes I need, and then recompile/rebuild it and try it again(just wondering...).
But, let´s forget about it. I´ll try some stuff and if success I´ll report.
I took a look at NetBSD web pages, to see about disk types/size, and now it´s a bit clear.
Anyway, you both had gave me a valuable help.
about machines...I have a celeron 300/128 ram - pentium 166/64ram.
I just dont want to drop them out as a junk, however they are. (besides these comes together a 486 100/64ram).
Posts: 33 Location: North Brunswick, NJ Joined: 12.03.08
Posted on September 16 2008 07:22
valdirfranco wrote:
What is the minimum to run simh and vms? I´m afraid, ´cause I have a lot of info on my machine and dont want lost it all....
...
Thanks the info, but I did mean what the minimum reqs. (cpu, speed, ram) to run simh with OVMS Vax. This is because I have some others machines, and I´d like to try vms on them too.
One of the machines I run simh on is a Pentium III running at 600MHz with 128MB RAM. I find the performance acceptable but I'm not doing anything too exotic.
Yes...I need to find this stuff here in brazil... It seems to be like...: who has one doesnt want discard it...
By now I just figure out next step...till get my Vax (even on simh) getting me something useful...
BTW, Hoff (may I call you Hoff)...I got license from DECUS-FIN, I´ve tried register it, and got an error saying invalid user, or something like that. Well, I dont know deeply on this but, when I (will) try the PAK license (other stuff on cd: cobol, fortran, etc) and get same error, what can I do? I did enter some info, at installation, as base license, I got the system installed thinking it is with a valid license, as shown.
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!
rv with OVMS CD (kit from montagar) in D