> No, that's wrong. > I though it is a pretty clear why SAA1099 emulation is in separate package. > 1.) I worked on sound, Allan worked on SimCoupe. New versions came > paralelly. > This is faster. > 2.) My sound emulation isn't concerned into SimCoupe. It is publicly usable > in any SAA1099 interested software. So I publish it in its own package.
So, perhaps it should come with Simcoupe, in a format that can still be used independantly, and with a pointer as to where to get the stand-alone distribution. The installer for Simcoupe could simply take advantage of the fact that the SAA1099 emulator is within the Simcoupe package, without combining the two in some ireversible manner. Perhaps there could also be a legend reading "SA1099 emulator used with permission...". I agree with you wanting to keep your work available as a stand-alone package, but if we want the more general user to investigate SimCoupe, the installation should be as straight-forward as possible. Don't tell me that "Most users have no problems with installing <x> before <y>.", I've spoken to so many people who have trouble understanding concepts like "Root directory" and the difference between free hard-drive space and RAM. Yeah, there are a lot of intelligent PC users, but there are a lot of stupid ones too... -- James R Curry - [EMAIL PROTECTED] "The Balloon Doggies DEMANDED it!"
