<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I did this once. The other thing to do is just temporarily to create another data disk with that label and attach it to SIMH until you can fix your startup file. You could do this by installing VMS again into a new virtual machine, you could probably just make the label of the new VMS system disk be DATA2.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Regards<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rob<o:p></o:p></span></p><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></a></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> simh-bounces@trailing-edge.com [mailto:simh-bounces@trailing-edge.com] <b>On Behalf Of </b>Markus Ruggiero<br><b>Sent:</b> 12 October 2010 07:03<br><b>To:</b> simh@trailing-edge.com<br><b>Subject:</b> Re: [Simh] Oh, my<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On 10.10.2010, at 16:23, Nathan Cutler wrote:<o:p></o:p></p></div><p class=MsoNormal><br><br><o:p></o:p></p><div><p class=MsoNormal>I seem to have gotten myself into a bind. (SimH/VAX OpenVMS 7.3)<br><br>I used the Standalone backup functionality to make a backup of my system disk (to a larger container - thanks to Tim for help on this). The BACKUP/IMAGE/VERIFY appeared to go well.<br><br>Then, instead of just booting the new system disk, I stupidly decided go to one data disk (I had been using two). Stupidly, I deleted the second data disk (labeled DATA2) but forgot to edit the system startup procedures to reflect this.<br><br>The SYSTARTUP_VMS.COM script contains "MOUNT/SYSTEM DUA2: DATA2" and when the startup process hits this command, the system chokes on it, demanding (repeatedly) that I mount DATA2. However, I can't mount it because it has been destroyed. This forces me to "power off" the "machine" (CTRL-E to the sim> prompt and then exit).<br><br>To fix this, I did a conversational boot. This does get me to a $ prompt but a whole bunch of files seem to be missing. Critically, SYSTARTUP_VMS.COM is not where it's supposed to be:<br><br>$ dir sys$manager<br>dir sys$manager<br>%DIRECT-E-OPENIN, error opening LIVVAX$DUA0:[SYS$STARTUP]SYS$MANAGER.*;* as input<br>-RMS-E-DNF, directory not found<br>-SYSTEM-W-NOSUCHFILE, no such file<br>$ type sys$manager:systartup_vms.com<br>type sys$manager:systartup_vms.com<br>%TYPE-W-SEARCHFAIL, error searching for SYS$MANAGER:[SYS$STARTUP]SYSTARTUP_VMS.COM;<br>-RMS-F-DEV, error in device name or inappropriate device type for operation<br>$<br><br>Suggestions, anyone?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>My VMS know-how is a bit rusty but I think in a conversational boot you do not have logicals available at that point. So navigate to your files using the real disk and dir names. You should be able to edit SYSTARTUP_VMS.COM and remove the offending mount or at least rename it or move it away.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>---markus---<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></body></html>