[Info-vax] how to extract and install content from vms073lp.zip

[Paul Sture]

On Sat, 31 Mar 2012 18:36:28 +0000, Simon Clubley wrote:

> On 2012-03-31, Qunying <zhu.qunying at gmail.com> wrote:
>> The [...] thing, it helps me! I did not know it. backup VMS073LP.BCK
>> /save dua2:[lp...] But then I got this error:
>> %BACKUP-E-OPENOUT, error opening
>> DUA2:[LP.PATHWORKS_60D.KIT]PWRKV60D060.C;1 as output -RMS-F-FUL, device
>> full (insufficient space for allocation) %BACKUP-E-OPENOUT, error
>> opening
>>
>> It looks strange to me as my host system has quite a lots of space: I
>> am running it under Slackware64 13.37, my home directory is in the same
>> partition as root so I still have 100G of space.
>>
>>   Filesystem     1K-blocks     Used Available Use% Mounted on
>> /dev/root      169372672 43240576 117652592  27% /	/
>>
>>
> This doesn't matter. It's the size of the emulated disk which does
> matter and those sizes are fixed.
> 
> Do a
> 
> 	show dev dua2: /full
> 
> and look at the number of free blocks. The value should be pretty close
> to zero.

Simon is correct here. The disks seen by VMS inside SimH are just 
container files on your host system.
 
> 
>> ; Define disk drive types. RA92 is largest-supported VAX drive set rq0
>> ra92
>> set rq1 ra92
>> set rq2 ra92
>> set rq3 cdrom
>>
>> ; Attach defined drives to local files attach rq0
>> /home/qunying/vms/data/d0.dsk attach rq1 /home/qunying/vms/data/d1.dsk
>> attach rq2 /home/qunying/vms/data/d2.dsk
>>
>>
> The only part of your host filesystem which is used is the part used to
> store these files and unless SimH has acquired some form of dynamic disk
> resizing (it's been a few years since I last used SimH so I am just
> covering all possibilities :-)), the size must be consistant with the
> emulated device.
> 

See the section "The Variable-sized RAUSER device" at:

http://labs.hoffmanlabs.com/node/922

"The following creates a generic RA-series disk with 20,000 512-byte 
block capacity:

set -L rq0 rauser=20000

RAUSER is specified in 512-byte disk blocks (with the -L option) (and in 
units of mebibytes (MiB) without), and can range up to 2 gibibytes (2 GiB) 
when simh is compiled and running with 32-bit addressing, and up to one 
tebibyte (1 TiB) when simh is compiled and running with 64-bit 
addressing. The backing file must be of at least sufficient capacity for 
the specified RAUSER size."



-- 
Paul Sture