Path: utzoo!attcan!uunet!snorkelwacker!mit-eddie!uw-beaver!ubc-cs!fs1!fs0.ee.ubc.ca!jmorriso
From: jmorriso@fs0.ee.ubc.ca (John Paul Morrison)
Newsgroups: comp.windows.ms
Subject: Re: Using Win 3.0 on Shared-Use Machines
Keywords: Windows 3.0, File Properties
Message-ID: <1305@fs1.ee.ubc.ca>
Date: 10 Jul 90 01:56:03 GMT
References: <1990Jul6.152405.929@athena.mit.edu> <7768@fy.sei.cmu.edu> <1433@epd74hp.nluug.nl>
Sender: root@fs1.ee.ubc.ca
Reply-To: jmorriso@fs0.ee.ubc.ca (John Paul Morrison)
Organization: Dept. of Electrical Engineering University of B.C.
Lines: 12

Aha..! But you can too have your cake and eat it too! After you set the path
to the start-up directory and choose ok, you get the ivalid path message
blah blah..., but if you then choose the change icons button, you will get
a dialog box with 'filename' containing the start up path you entred. Since
this file doesn't exist, you get a default icon. But you can change this file
name to anything you want, even back to the original file in the right place.
The first (wrong) path specifies the startup, the othe specifies the icon.

This isn't new, and you can get a hold of some PD icons as in icon.dll which has
hords of icons in it.

jp