Sorry if I seem to be stating the obvious (and if you understood this stuff before then you were ahead of me, because ***I ***didn't).

Quote - looking at the files it installs on its own, there should be absolutely no reason for the V4 base update whatsoever.  not no reason in general, like changing JCM, but no reason for the S4 install to need it.

I don't take it for granted that the base V4 install is necessary - since the S4 installer writes a new S4 CR2 it seems likely that the only thing required from the V4 base would be the geometry (the OBJ file) - and possibly not even that.  I can't unpack the installer to check whether it's included or not and I'm not going to remove my working copies to find out for sure.  DAZ's installation process evidently has some problems and I'm not really anxious to provoke any :)

Quote - second of all, there's no second cr2 that needs injections....

Well there is actually, if you wanted to use the base "Victoria 4.2" CR2 - editing this, and editing a newly-saved CR2 of the same figure, I can see that the channels don't exist in the installer-written version (but will be created as soon as loaded into Poser) and they do exist in the newly-saved version (because Poser created them based on the readScript operations and saved them into the new CR2).  What the "Morph Injection" poses do is load the DELTAS (the actual morph data) - for almost all of the morphs, this is not done until you take that step, the morph channels are there but they are empty and won't do anything.  The various bone scale operations will work, which may be a little confusing since they aren't always obvious as to which is which (e.g. the Proportions dials for S4 are listed under Morphs, when they're not morphs at all).  I may be misunderstanding quite what you meant here, but this seems completely as I expect it to be.

Quote - instead i left everything in my version 4 runtime, and they installed anyway.  (etc)

Yeah this is Poser's silent search thing going on.  If it was up to me, referencing a relative file location that is not found in your current runtime should at least bring up a warning of some kind - but Poser silently checks through other runtimes and will open what matches a called filename.  Usually.  I don't know what logic Poser uses to track this kind of thing on the first or subsequent load attempts (e.g., does it always search all runtimes? what order? if, after the first load, you then change runtimes and load something that references the same filenames, does it search again or prefer to use what it already found earlier?  maybe Wim knows this stuff offhand, nobody outside the Poser prgramming team could say for sure)  It seems likely to me that if you have these files installed in multiple places, you can get weird results like this.

My Freebies