Ken,
To elaborate on OAM's #4
The "additional restrictions and requirements" are basic and clearly spelled out in the Developer Manual (There's not much clearly spelled out in this manual, but these items are). They are not complex... for example you are reqired to list FMI as a copyright holder on a screen (but doesn't specify how large the font must be). If you desire FMI not to unlock the solution at the request (and payment) of a solution user (because you password protected your solution and the user wants to get into it), then you must list some specific terminology on a screen specified by FMI. This screen tells FMI that you, the developer, have limited the user's access to only the password protected privileges that you assigned solution users. Nothing difficult.
After fulfilling these requirements, you have unlimited distribution rights of your "Runtime" without any royalty payments to FMI. As Steve mentioned, these rights come with the Developer edition and are spelled out in the License.
To create a Runtime solution (your solution runs on the user's computer without him having an actual copy of FMP) you utilize a program that comes with Developer, but not with FMP. With this "Binding Program' you create a "Runtime" version of your solution by specifying your solution "File Name", plus whether you want the solution to run in "Kiosk" mode, any custom file extension you want and a couple other choices that you're offered. After making the selections, you tell the program where to place the files, click the "Finish" button and it does it's thing. That's it.
It is not difficult but does require some experimenting to learn how the various selections (that you made during the bind) affect the solution.
Also many, if not most, third party Plug-ins work with the Runtime as well as FMP.
Kiosks present their own set of potential problems. Steve has seen and resolved most of them.
HTH
Gary