I dunno about that. Remember, 4.2 has 2 interface engines, one for P4, the other for P5. Odds are that one deactivates the other, to avoid conflicts. Probably the easiest way to deal with the issue for P45 dual installers is to use the P4 code section, which seems more stable, and then copy the runtime files for P5 into the P4 runtime, leaving out all of the dynamic stuff, of course. Did this test, and the only things it imported of the P5 part of the test were the things I'd copied into the P4 runtime.