CompuServe Messages

>> What is also strange is the fact that it loads BMP's successfully! I saw some IExxxx.DLL files in the SYSTEM directory. They appear to be DLL's used for the different file types (i.e. xxx is PCX, BMP, GIF, TIF…). << yes. >> I am currently, as I am writing this, reinstalling Animator Studio on the computer. I went through and deleted the ANIMATOR directory and have tried tracing down the files it installs in the WINDOWS and SYSTEM directories and deleted them also. << i have had several people ask me if there is a guide to _all_ files installed by AStudio for this same type of analysis… it is a common challenge for users when they install an application to know "what's been added" to the system. about 1.5 years ago, we wrote a Windows application which would memorize the WINDOWS and WINDOWS\SYSTEM contents before an install and then report any additional files which had appeared in those directories after an install. a later version also reported files which had existed which had been altered (INI files for example). still an easy way though is to ZIP up the entire WINDOWS and subdirectory contents to a safety file (provided there's enough HD space) and then wipe the whole thing if problems start and restore (leaving ZIP instact for later unzipping) completely (using -d parameter of PKUNZIP) until problems are resolved. i mean, <laughing> how many people can honestly go into their WINDOWS and SYSTEM directories and explain what every file does in there? <ggg> some applications are kind enough to provide de-installers to clean out these system directories…. those that don't… well… all users know is that the WINDOWS directory keeps getting "bigger". <gg> >> So it seems that what I was suspecting was the problem. Reinstalling WITHOUT deleting the Animator files was not sufficient. I had to go through and delete as many of the Animator files as I could find before reinstalling. This did fix the problem. Sure was a pain. Can't wait until we are able to use the Uninstall capabilities of NT and Windows 95. << me too. maybe we'll get some level of functionality like this in the 3.1 and WFWG 3.11 versions too. imho, every Windows app ought to have a de-installer, or at least a guide to ALL files being installed and their locations and the modifications made to any existing files. imho. -dave