It may not be a piece of cake, kuroyume.  DAZ has complete control over what happens to files after they have been read into DAZ|Studio.  I can't say the same thing about them and Poser.  When Poser reads in the V4.1 CR2, all of the readScript() calls in the file are replaced in memory with the actual morph channels that those readScripts are calling out to.  This means, in effect, from Poser's point of view once the model is loaded, the readScripts don't exist anymore.  Thus when you save V4.1 back out to the library, those readScript calls aren't written out b/c they don't exist (the loaded morph channels do instead).  I don't think there is actually any way for them to update V4.1's that have already been loaded into Poser's memory and saved back out.  I'd blame that as much on DAZ for choosing such a hacktastic way of using an old undocumented Poser command as Poser for it's own handling of said command.

¤~Giolon~¤

¤~ RadiantCG ~¤~ My Renderosity Gallery ~¤