Originally posted by McGenius
I would modify Setup1.vbp to create custom installation process: next is triggered upon successfull completion of the previous or exits otherwise.
That's not a bad idea at all, except that he is using VSI, not P&D. It would be an interesting approach still. Since the P&D's setup.exe just reads the setup.lst file, you could modify it to cycle through all setup.lst files and just use one setup.exe program. Still I do like VSI because it installs MUCH faster than P&D and P&D has a few bugs when registering some dll's and tlb's (easy to overcome, but still a pain!)