Path: utzoo!mnetor!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!uwmcsd1!csd4.milw.wisc.edu!devilbis
From: devilbis@csd4.milw.wisc.edu (Vilbiss Warren C De)
Newsgroups: comp.sys.amiga
Subject: Re: Help! RAM: Device (Simple Query)
Message-ID: <5253@uwmcsd1.UUCP>
Date: 18 Mar 88 13:06:39 GMT
References: <848@umbc3.UMD.EDU> <17873@oliveb.olivetti.com> <624@ncs-med.UUCP> <5527@swan.ulowell.edu>
Sender: daemon@uwmcsd1.UUCP
Reply-To: devilbis@csd4.milw.wisc.edu (Mike Shawaluk)
Distribution: na
Organization: University of Wisconsin-Milwaukee
Lines: 25

In article <5527@swan.ulowell.edu> page@swan.ulowell.edu (Bob Page) writes:
>
>Essentially, you have to somehow touch ram: to load the ram-handler
>and make a WB disk icon available.  You could do something else like
>	assign t: ram:
>or
>	copy file to ram:
>you get the idea.
>
>..Bob

Actually, *I* usually prefer the following means of "touching" RAM:
	copy sys:ramicon to ram:Disk.info

This does the dual duty of loading the ram-handler AND giving the RAM: drive
a nicer looking icon than the plain-Jane one that AmigaDOS normally gives it.
Note that sys:ramicon is actually a copy of Disk.info, saved on my floppy under
a different file name, so AmigaDOS won't erroneously think that it's an icon
file.  Also, please note that in order for a different icon to be assigned to 
RAM: in this manner, you MUST copy the Disk.info file there as the first 
operation on RAM:, since AmigaDOS does not reload the Disk.info imagery again
unless the specified disk is ejected and reinserted, which you obviously can;t
do to RAM:

  - Mike Shawaluk