Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: KatManDEW on January 21, 2009, 01:11:50 AM
-
How do I change to CD icon to the one provided with MagicWB? I installed the CD drive after MagicWB was installed...
-
Hi KatManDEW,
Been a while. I think "deficons" maybe in env prefs?
Chris
-
Have a look in SYS:Prefs/Env-Archive/sys. There should be a load of icons in there. The file you need to change will be called something like def_CD0.info, where CD0 is the name of your CD drive's device. I can't remember now but you may not actually be able to see it from Workbench as icons of type "disk" don't show up. If you do a "dir" from the shell on that directory then the file should be there. Just copy a different icon over the top of it and then it should function as the CD icon. You will need to reboot for it to take effect.
IIRC, this file will be overridden by volumes which have their own disk.info (on the CD).
--
moto
-
Deficons sounds familiar, but I can't find any file like it on my Amiga. I tried the files in SYS:Prefs/Env-Archive/sys to no avail. I have a copy of the icon file in there called def_CD.icon and def_CD-ROM.icon and def_CD0.icon, but I still have a floppy disk icon for my CD drive. :-?
-
@KatManDEW,
As I recall they are hidden and you need to right click and chose "show all".
Chris
-
KatManDEW wrote:
Deficons sounds familiar, but I can't find any file like it on my Amiga. I tried the files in SYS:Prefs/Env-Archive/sys to no avail. I have a copy of the icon file in there called def_CD.icon and def_CD-ROM.icon and def_CD0.icon, but I still have a floppy disk icon for my CD drive. :-?
The fact that you have those def_#?.info files in envarc:sys suggests that you have Deficons installed. The problem is probably that none of the icons match the device name of your CD drive. As I said above, the deficon must match this otherwise it won't be applied. Have a look in sys:devs/dosdrivers and you should see an icon which represents your CD drive. If you can't recognise it, post a list of the contents of the directory. Once you have identified it, copy the icon you want to use in to sys:prefs/env-archive/sys. So, if the mountlist in sys:devs/dosdrivers was called "CD1" then the icon in sys:prefs/env-archive/sys would be called "def_CD1.info"
--
moto
-
QuikSanz wrote:
As I recall they are hidden and you need to right click and chose "show all".
I don't think that will reveal disk icons. They are never displayed unless they are actually being applied to the volume icon of a disk. In all other cases, the only way to see them is to look in the shell (using the "dir" command).
The fact that the OP can see some def_CD#?.info files in envarc:sys just means that they aren't set to disk type icons. I can't remember whether that matters to deficons now.
--
moto
-
motorollin wrote:
The fact that you have those def_#?.info files in envarc:sys suggests that you have Deficons installed. The problem is probably that none of the icons match the device name of your CD drive. As I said above, the deficon must match this otherwise it won't be applied. Have a look in sys:devs/dosdrivers and you should see an icon which represents your CD drive. If you can't recognise it, post a list of the contents of the directory. Once you have identified it, copy the icon you want to use in to sys:prefs/env-archive/sys. So, if the mountlist in sys:devs/dosdrivers was called "CD1" then the icon in sys:prefs/env-archive/sys would be called "def_CD1.info"
--
moto
I have CD0 in devs/dosdrivers. I also have CD0 in Storage/dosdrivers. That second one is the one that I had to hack around and find, and do Icon-Information, to find that it was set to Device=2. My CD is on SCSI device 4, and when I changed it to 4, then my CD drive became available.
-
Is the file in sys:prefs/envarc/sys definitely called def_cd0.icon? Because it should be def_cd0.info. If it has the correct name but still isn't being applied, then either deficons isn't running, or there's something wrong with the icon.
--
moto
-
motorollin wrote:
Is the file in sys:prefs/envarc/sys definitely called def_cd0.icon? Because it should be def_cd0.info. If it has the correct name but still isn't being applied, then either deficons isn't running, or there's something wrong with the icon.
--
moto
I think that was a typo. I had icon on the brain :-o
I'm almost positive I used .info, because all the other files in that drawer were .info, but I'll check when I get home this evening.
This may all be a mute point once i receive OS 3.9 and install it. It might arrive today.
Thanks for the help
-
KatManDEW wrote:
I'm almost positive I used .info, because all the other files in that drawer were .info, but I'll check when I get home this evening.
Try doing a directory listing from the shell rather than opening the drawer through Workbench. If you're using OS3.0 or 3.1 then you need to make sure you've got deficons running, since it's that which applies the icon. Without it, the icon will sit unused. To check, open a shell and type:
ed s:startup-sequence
and then just scan down the file to check for a deficons entry.
KatManDEW wrote:
This may all be a mute point
Maybe, but more likely it will be a moot (http://dictionary.reference.com/browse/moot) point :-P
KatManDEW wrote:
once i receive OS 3.9 and install it. It might arrive today.
OS3.9 has deficons built-in. So all you need to do is change the icon to whatever you want it to be and it should change (after a reboot).
--
moto
-
No Deficons in my Startup-sequence, and I can't find a deficons command anywhere. I used a search tool that I got on Aminet, and I manually searched all over.
That has to be the problem because I checked and I did use the info extension.
Would it be on my Workbench 3.1 install disks?
(http://www.katmandew.com/images/Misc/Amiga%20DOpus.jpg)
-
I did some digging around and found that NewIcons included Deficons, so I went ahead and installed it, and the required ClassAct, and I have a CD icon now!
Now if I could just figure out how to get ClassAct to not display a window when my Miggy boots.
I am probably going to wait until I get a new HD (ASAP), before I install OS 3.9, which will hopefully be here tomorrow, along with some other Miggy goodies :-D
(http://www.katmandew.com/images/Misc/Amiga%20Workbench-2.jpg)
-
And remember you have to get rid of Newicons and Classact when installing 3.9 - they both are built in but different versions (Glowicons, Reaction).
-
zipper wrote:
And remember you have to get rid of Newicons and Classact when installing 3.9 - they both are built in but different versions (Glowicons, Reaction).
Glad you told me that! My new Miggy goodies didn't arrive today anyway :boohoo: I haven't been this excited about new computer goodies since the last time I ordered Miggy stuff!
I will probably wait until I get a new hard drive before I install OS 3.9. AM I gonna have to setup a boot floppy with the CD ROM drivers installed so I can install onto a blank HD from the CD?
-
Installing 3.9, OH no, not again... :lol:
(Sorry, I just had a nightmare installing 3.9 on my 4000T, ....)
Well, KatManDEW, when you click on the 'install' icon for 3.9, the first option is 'create emergency disk', and that's the first thing you should do... Just make sure the 3.9 CD is in your CD drive, and boot the emergency disk. It should boot up, and give access to the 3.9 CD (it's clunky, but it does work ...)
Couple of points; Be sure to test the emergency disk first, make sure you backup any unsaved data, if you have more than one CD drive on your miggy, you may find that only one drive works with the very basic CD-ROM filesystem of the emergency disk, test it first. You probably should get BoingBag 1 + 2 updates, but backup your system first...
You can also search my username for posts, if you want to read about my 'fun time' installing 3.9 ...
:insane:
-
Don't forget to read this:
http://www.gregdonner.org/os39faq/os39faq.html
-
You guys are scaring me!
But thanks for the tips.
-
When my OS 3.9 finally does arrive (unhappy customer here), would I be better off installing to a blank hard drive, or installing OS 3.1 first, and then upgrading to 3.9?