>> > >Nice.  While we're at it, how about changing the type & creator codes
>> > >of changesets, so they'll be less likely to be corrupted by file
>> > >transfers?

>> > If you get the 3.0 sea file, then they have the right file type.  (STch)

>> I'm afraid you misunderstand.  I don't mean the changes file, I mean
>> changesets, as in file-outs.  I transfer them between systems a heck
>> of alot more often than I do changes files.

>Not a bad idea, if it's not too hard to do.  Probably the same STch file type would be good for these?  At least, I think the same icon (the mouse inside the document) would be appropriate.  Also, .st fileouts should probably have the same file type as well.

Another solution would be to compress them, which we request anyway for anyone posting changeSets.  Saves 4x in space and doesn't get munged by the mailers.  FileIn just needs to be apprised of the possibility.

	- Dan