[Info-vax] VAX VMS 5.4 on Microvax 2

[Dave Froble]

On 9/1/2021 2:07 PM, Simon Clubley wrote:
> On 2021-09-01, blockhouse007 <ihatecomputers007 at gmail.com> wrote:
>> Ok Ive managed to get an RD53 on an RQDX3 controller fired up on the Microvax 2.
>>
>> The problem I have is I created a STABACKIT on a TK70 from my working MV3800 and a full system backup.sav save set. (VMS 5.4)
>>
>> I can boot the STABACKIT TK70 on my MV2 but on restoring the save set the RD53 becomes 'disk is full'  as it is obviously too small in capacity compared to the RF72 on the MV3800.
>>
>> Do you know what directories are actually required to get a working copy of VMS 5.4 on my MV2, as against me doing a full backup/image? Can I include /exclude or is it unlikely to even fit? I'm sure VMS 5.4 was on my old disk that trashed.
>> Any advice much appreciated.
>
> You need to do a backup/image to get a valid bootable system disk on
> your target system; you cannot just copy over some specific directories.
>
> That means you need to reduce the number of files on the source
> system before creating the saveset.
>
> Ideas to try before creating your saveset (completely untested, use
> at your own risk, etc):
>
> See if you can remove the sys$help and sys$examples contents, after
> making multiple verified backups of them if you need to restore them.
>
> Do a source_disk:[*...]*.*;-1 to check for multiple versions of files.
>
> Did that version of VMS have any uninstall capabilities ?
> If so, try removing any installed layered products with an uninstaller
> and then install them again.
>
> Try a source_disk:[*...]*.*/select=siz=min=1000 and see if you can
> get rid of any of the files that show up.
>
> How big are the swap and paging files on the source disk ?
> They should be marked as nobackup, but they will be recreated on
> the restore and hence take up space on the target disk.
>
> Can you reduce the size of them on the source disk by using autogen ?
>
> Simon.
>

The problems can be from any source.  If the clustersize is large, say 
73, no way the files will fit.  The clustersize on the target should be 
small, I'd use 1, and the files being installed should not be extended 
to a previous clustersize.  Contiguous files on the source will be helpful.

I have faint memories of copying files with truncation.  Something I 
hope to never have to do again.

But that will most likely be required in this case.

On the source disk, truncate all files to their minimum size.
Then make the backup image.
Init the target disk, then when restoring, use the /NOINIT option on the 
BACKUP command.

Not sure if the OP has any method to init the target disk.

Oh, wait, the OP asked for advice.  My advice, scrap the MVII.


-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486