How to write (or find) a limited freeware licence for software I wrote?

I’m not sure if this has a GQ answer or it’s in IMHO territory, but I’ll try it here first.

So, I do some programming in my spare time as well as my 8-4 gig, often for somewhat retro mobile devices, and I’ve been thinking of releasing a few utilities that I wrote for the Alphasmart Dana as free software.

As well as the program file itself, and a little manual, I’d like to include a simple license document, spelling out the following requirements…
[ul]
[li]You can run this program on as many devices as you wish.[/li][li]You are not granted the automatic right to view my source code.[/li][li]You may distribute this program on a free basis to other persons or websites, as long as you keep the manual, the license, and my name with it.[/li][li]You do not have the right to charge money for the program.[/li][/ul]
…As well as anything else that sounds like a good idea to cover my butt.

I tried looking around online, but didn’t find anything that seemed like just what I wanted. The BinPress License Generator seemed promising, but it seems designed for specific license agreements between two parties, not a document that I can post for whoever downloads my program.

So, does anybody have a tip for me?

Look at:

https://www.gnu.org/licenses/gpl.html

Thanks… I don’t think GPL or MIT are what I want, but “Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License” may be just the ticket!

Update: Creative Commons does not recommend applying their license to software and suggest using ‘free software’ or ‘open source’ licences instead. Well, I’m sorry, I do NOT want to go free software or open source with this.

(Possibly getting into GD territory here.) Should I use the CC license anyway?

Bumping once for the Monday morning ‘Dope at work’ crowd. :slight_smile:

You could just write out what you put in the OP.

Copyright is going to reserve a whole bundle of rights to you, so all you really need to do is specify which ones you’re no longer claiming. Listing clearly defined things that you’re allowing should do the trick (1. You may install and use this software as specified in the manual without charge. 2. You may distribute this software unmodified as long as the license and manual are included. 3. You may not charge for this software. 4. All other rights reserved).

Most of the various free software licenses are concerned with source code, future modifications, and whether those future modifications are required to be released as well. If you’re not releasing source code, you probably don’t need them.