Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!husc6!spdcc!ima!think!ephraim From: ephraim@think.COM (ephraim vishniac) Newsgroups: comp.sys.mac Subject: Re: Hard Disk Icon Message-ID: <23723@think.UUCP> Date: 14 Jul 88 13:29:57 GMT References: <10623@oberon.USC.EDU> <698@ttrdf.UUCP> Sender: usenet@think.UUCP Reply-To: ephraim@vidar.think.com.UUCP (ephraim vishniac) Organization: Thinking Machines Corporation, Cambridge, MA Lines: 51 In article <698@ttrdf.UUCP> fjo@ttrdf.UUCP (Frank Owen ) writes: >The hard disk icons are usually hard-coded in the driver for the >particuliar hard disk. The driver is usually located on the low >tracks of the hard disk, not within the normal data area of the disk, >or in any particuliar file. A copy of the driver is also probably in >the resource fork of any Installer/Formatter program provided by the >manufacturer. All true, so far. >The only way to change the icon would be to search for data that >"looks like" the icon either in the DRVR resource in the >Installer/Formatter program or the driver itself on the hard disk, >and change it by alterring the BINARY DATA with something like >MacSnoopy or DiskTools or something like that. (can't use ResEdit >for this folks!). Not so. You can use ResEdit to construct the new icon (actually an ICN# resource), close it, then option-open it to get the hex data. Go to the resource with the old icon, cut out that data, and paste in the data for your new icon. ResEdit's actually very good for this. >Most times the icon is located just after the Pascal-style string >that contains the drive's name, That's backwards. It's immediately *before* the "Where:" string, not after it. >so this makes it a little easier, In the Jasmine driver, it's much easier, because I got tired of Jasmine bugging me about icon changes. To find the icon in your Jasmine formatter, open the SDRV (SCSI Driver) resource, and search for the string 'ICON'. From there to the "Where:" string is the icon data. I suppose I should have put it in a resource and patched the driver at installation time, but that's all hindsight now. >but all in all, it's not an easy task, and can lead to real problems >if you screw up. So true. >I wouldn't try it. I would! Ephraim Vishniac ephraim@think.com Thinking Machines Corporation / 245 First Street / Cambridge, MA 02142-1214 On two occasions I have been asked, "Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?"