on 4/4/01 3:58 AM, Tim Mountford at [EMAIL PROTECTED] wrote:
> As a non-programmer with a dangerous smattering of knowledge about the MacOS
> I always thought that installers looked at the system for Creator codes or
> something equally esoteric. I didn't realise they just looked for apps
> simply by filename! Just shows what I know.
Apparently, only Microsoft's installer does (as well as Adobe's) - plenty of
other apps are able to install despite changes the users made to filenames.
> Again, who'd have thought an installer would stall at a custom icon if the
> sacred filename is okay (assuming it is).
I believe the issue here is less the pasting of a custom icon over existing
icons, but possibly of replacing an icon a custom one using a tool like
Resedit - at least that is the impression I have received from the way it
was described in an earlier message.
I think when people start messing with an app, all bets SHOULD be off.
Nevertheless, since InstallerVISE and Stuffit InstallerMaker, as well as
Apple's installer *ARE* able to handle such instances, and since this update
appears to simply replace entire files, there's probably no real excuse for
such lack of error checking.
At the very least, the documentation should be better at pointing out such
foibles - didn't they test this with users or a beta group before releasing
it? Didn't these errors and problem crop up then?
Harry
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
To search the archives:
<http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
