POSTER
Article 221 of comp.binaries.amiga:
Path: estinc!mcdphx!asuvax!ncar!mailrus!ames!sun-barr!newstop!sun!swap!page
From: page%swap@Sun.COM (Bob Page)
Newsgroups: comp.binaries.amiga
Subject: v89i144: vd0 - recoverable ram disk
Message-ID: <122693@sun.Eng.Sun.COM>
Date: 21 Aug 89 06:30:28 GMT
Sender: news@sun.Eng.Sun.COM
Lines: 474
Approved: page@sun.com
Submitted-by: kim@uts.amdahl.com (Kim E. DeVaughn)
Posting-number: Volume 89, Issue 144
Archive-name: dos/fs/vd0.uu1
This is the latest version (July 14, 1989) of the ASDG recoverable ramdisk.
New features:
* Up to 8 Meg VD0:
* Rewritten in assembly
- faster
- 1/3 the size
POSTER2
Article 12121 of comp.sys.amiga:
Path: estinc!mcdphx!asuvax!ncar!mailrus!tut.cis.ohio-state.edu!unmvax!gatech!ncsuvx!ccvr1.ncsu.edu!garvin
From: garvin@ccvr1.ncsu.edu (Michael A. Garvin)
Newsgroups: comp.sys.amiga
Subject: New ASDG VD0: library error fix
Message-ID: <3680@ncsuvx.ncsu.edu>
Date: 16 Aug 89 18:06:47 GMT
Sender: news@ncsuvx.ncsu.edu
Reply-To: garvin@ccvr1.ncsu.edu (Michael A. Garvin)
Organization: Bill 'n Opus Campaign HQ
Lines: 140
[Posting this due to popular demand and the small size...]
I got the following off of GEnie (as I recall). It's the fix for the
"Could Not Open ASDG.VDisk.Device" error given by CleanRamDisk and
DeleteRamDisk. I've stuck the readme on here, followed by the UUENCODED
Zoo archive with the programs. Enjoy.
Michael Garvin
garvin@ccvr1.ncsu.edu
NCSU Computing Center, Raleigh, NC
---------------------------------------------------------------------------
These are versions of the CleanRamDisk and DeleteRamDisk programs for use
with ASDG-RAM (vd0:) in which the "Could Not Open ASDG.VDisk.Device" error
has been fixed.
This is for use with the latest version of asdg.vdisk.device as of July 14,
1989. This asdg.vdisk.device file should be 2724 bytes.
---------------------------------------------------------------------------
Readme
This is the ASDG recoverable ramdisk (also known as VD0:)
This is the latest version as of July 14, 1989.
New features are:
* Upto 8Meg VD0:
* ReWritten in Assembly (faster)
* 1/3 the size (Used to be 6604
To use it read in instructions in the file 'mountlist' and
edit that file you reflect MAXIMUM size recoverable ramdisk
you want. VD0: does NOT use all the ram you specfiy. That
size specification just tells VD0: the most memory it is
allowed to use. It is better to fill up VD0: then to run out
of memory.
To install VD0: you must add this 'mountlist' to the
'mountlist' in your devs: directory. You can do this by going
to the CLI, setting the currect directory (CDing) to the
directory with the ASDG-VD0: files in it and typing.
join devs:mountlist mountlist as RAM:mountlist
copy ram:mountlist devs:mountlist
Then you must add the line
mount VD0:
to your startup-sequence. Mounting VD0: won't actually start
it up until you try to access VD0: so I usually put these two
lines in my startup-sequence
mount VD0:
cd VD0:
You also need to copy the file 'asdg.vdisk.device' to your
devs: directory.
copy asdg.vdisk.device devs:
That should be all. Just reboot.
Some tips:
VD0: will work with RAD: (just mount RAD: first) The
advantage to this is that IF you are using 1.3 KickStart you
can create a small RAD: (just large enough to hold what you
need to re-boot your system.) And then you use VD0: for the
rest of your recoverable ram disk. VD0: only uses the memory
it needs to unlike RAD: which uses all the memory you specify.
This means you will have more memory free with this
arrangement then with just using RAD: and you will still be
able to BOOT from RAD:
You can make VD0: "act as RAM:" by puting the following lines in your
startup-sequence
mount VD0:
cd VD0:
Relabel VD0: RAM
DiskChange VD0:
This way, all your programs that access RAM: will actually
access VD0:
Other Files include in the ZOO are
SysMon - Show you system performance information.
DeleteRamDisk - After running this you will lose all the
information in VD0: next time you reboot.
(Similar to RemRad for RAD:)
CleanRamDisk - Tells VD0: to freeup any memory it is
no longer using. (This happens
automatically every so often.)
FastMem - Allocates all your systems Fast Memory.
Run it again and it will release it.
(Used for very old programs that have a
problem with fast memory)
Readme2
These are versions of the CleanRamDisk and DeleteRamDisk programs for use
with ASDG-RAM (vd0:) in which the "Could Not Open ASDG.VDisk.Device" error
has been fixed.
This is for use with the latest version of asdg.vdisk.device as of July 14,
1989. This asdg.vdisk.device file should be 2724 bytes.
