Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: RE: VMS RAM disk
Message-ID: <870214052644.00f@CitHex.Caltech.Edu>
Date: Sat, 14-Feb-87 08:26:50 EST
Article-I.D.: CitHex.870214052644.00f
Posted: Sat Feb 14 08:26:50 1987
Date-Received: Sun, 15-Feb-87 00:40:45 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 15
Approved: info-vax@sri-kl.arpa

>  We will try another application of this nice feature in the future:   Every
>  single-disk  750  user  has  the  problem of waiting at least one hour till
>  standalone BACKUP has started from the TU58s if you want  to  restore  your
>  disk (to remove fragmentation).  It should be possible to build a TK50-like
>  kit on your disk which you can boot in a few seconds and  then  use  it  to
>  overwrite just that disk!

No, you can't build a TK50-like kit on your disk (the TK50 kit  contains  code
to  copy from TAPE to memory, doesn't know anything about disk structure until
VMS is running, etc.  What you really want to do is build a STANDALONE  BACKUP
kit  on  your  disk  that  looks  like regular VMS except that what it runs at
startup time is the VMS kernel with STANDALONE BACKUP (STABACKUP)  instead  of
full  VMS.   This  doesn't  use  RAM  disk,  it uses real disk, then turns off
paging.  (And besides, the disk space it uses  is  a  small  fraction  of  the
storage space required for the TU80/TK50 kits.