>>>It's clearly MS legal language, and I would like to make people think *I* made this and not Microsoft. How can I modify this to be my own?
>>
>>The problem here is that you did include Microsoft products - like the VFP runtime - in your application. That caveat really can't be removed, since you have no way to avoid this. The copyright information provided in the Setup Wizard screen is included in the Help/About box.
>>
>>The MS caveats are built into the Setup component, and aren't alterable.
>>
>>You can use a different tool to create your setup application, but you still
>
>Ah-ha. Well, I guess this is something to add to the wish list for future VFP versions. It would be nice to have some of my text in there...

You can use another installation tool like InstallShield Express and even run a Setup Wizard created install of the runtime from there; you still have to acknowledge MS's copyrights and the restrictions of the EULA on further redistribution of the runtime and components by your end-users.

IOW, the rules you've agreed to don't change because you've switched installers; the user needs to acknowledge the restrictions established not just by you, but by MS as well, on the runtime components. You have a limited licesne to redistribute the VFP runtime - you can distribute it freely because you purchased the VFP development environment, but your end-users don't have that same set of rights - they can't give someone the runtime to use except with the app that you provide to them. They don't have the right to turn around and sell/give away the VFP runtime unless they have the VFP development environment, too, and ship it as a part of an application, at least from what my attorney has told me (since he deals with intellectual property law, I'm fairly certain of his interpretation.)

Caveat - IANAL! Check with your attorney about what the applicable laws are.