


Since you have tested the installation of SP4 by so many different methods, both with and without external tools, I have a hard time believing that the fault with WinNTSetup is with either SP4 or an external tool. He also believes that the problem lies either in the update packs themselves and/or the tools used to integrate them such as nLite or RVMi. JFX believes that WinNTSetup is fine, and he has no current plans to modify it to resolve the conflict since XP is EOS. It seems that SP4 and some of the other XP update packs sometimes have an issue when you try to use WinNTSetup, which is a very respected tool and is able to be used to do installs for XP, Win7, Win8, etc. You seem to have done a very thorough job in testing all the various installation methods including CD, DVD, USB, live install, integrate then install, reinstallation after uninstallation, etc, so I would very much appreciate your comments about a matter that Atari800xl has brought up.

Harkaz, you have absolutely done an amazing job on this project.
