Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!ukecc!agollum
From: agollum@engr.uky.edu (Kenneth Herron)
Newsgroups: comp.sys.amiga
Subject: Re: Relabelling RAM: (the disk icon)
Message-ID: <2779@ukecc.engr.uky.edu>
Date: 29 Jan 89 16:21:00 GMT
References: <34939@bbn.COM> <549@jc3b21.UUCP> <674@cord.UUCP>
Reply-To: agollum@engr.uky.edu (Kenneth Herron)
Followup-To: comp.sys.amiga
Organization: Way down south in the land of Basketball
Lines: 17

In episode <674@cord.UUCP>, we
heard nsw@cord.UUCP (Neil Weinstock) say:
>For those who are unaware, you can also change the icon image of RAM: so you
>don't get that generic picture of a disk.  Normally, when RAM: is created,
>(or does loadwb do it?) the system looks in it for disk.info, which contains 
>the icon info.  Not finding one, it creates a generic one.  You can get 
>around this by editing the RAM: icon (using iconed or whatever) and then 
>copying RAM:disk.info to somewhere on your boot disk.  

I fooled with this while setting up a "boot to ram:" disk a while back.
As near as I could tell, the exact behavior is:  When LoadWB starts up,
if RAM: has no disk.info, then SYS:disk.info is copied to RAM:disk.info.
So whatever icon your boot disk has, your ram: disk will have the same
(though the window position is reset). To avoid this, have a disk.info
file in RAM: when you run LoadWB.

Kenneth Herron