Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 263,988 of 264,096    |
|    =?UTF-8?Q?Arne_Vajh=C3=B8j?= to flexmcmurphy    |
|    Re: SIMH + OpenVMS 5.5-2H4 standalone BA    |
|    17 Dec 25 19:53:24    |
      From: arne@vajhoej.dk              On 12/17/2025 5:52 PM, flexmcmurphy wrote:       > Setup (simplified):       > - SIMH VAX (have tried MicroVAX 3900 and VAX 8600)       > - OpenVMS VAX 5.5-2H4 ISO attached as an RQ device (read-only)       > - Booting directly from the ISO into standalone BACKUP       >       > In standalone BACKUP, the installation media always appears as DJAx       > (device type RA60), not as DUAx, for example:       >       > Available device DJA3: device type RA60       >       > As a result, restoring the saveset only works using:       >       > BACKUP DJA3:VMS2H4055.B/SAVE_SET DUA0:       >       > However, I have seen multiple reports (e.g. WinWorldPC forum, blog tutorials)       > where users claim to restore from the *same* OpenVMS 5.5-2H4 ISO using:       >       > BACKUP DUAx:VMS2H4055.B/SAVE_SET DUA0:              > 1) Under standalone BACKUP 5.5-2H4, what determines whether the boot       > device is assigned DUAx vs DJAx?       > 2) Is this affected by the VAX model (MicroVAX vs 8600/8650), SIMH MSCP       > configuration, or whether BACKUP was booted from that device?       > 3) Is DJAx actually the expected and correct name for RA60-based ISO       > media in this environment?       > 4) Using my setup is it at all possible for me to restore the save_set with       a command such as:       > $ backup dua3:VMS2H4055.b/save_set dua0:       > instead of       > $ backup dja3:VMS2H4055.b/save_set dua0:       >       > Any clarification would be greatly appreciated.              Traditional VMS disk device naming is:              D = disk       X = controller type, U=Unibus, I=DSSI, K=SCSI       Y = controller number, A=first, B=second, C=third ...       N = unit on controller, either 0=first, 1=second, 2=third ... or       0=first, 100=second, 200=third              RA81's and RA82's become DU disks.              Google indicate that RA60's become DJ disk. Not sure why. I am not old       enough to know RA60's. Maybe someone else can elaborate on why RA60's       are DJ and not DU.              Arne              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca