r> Ah, good. I wasn't sure if you received the file in its entirety, as FD 
r> didn't actually log which file was sent or even *if* it was sent. I knew 
r> which file you *wanted* because it logged the FREQ, at least.

I had to FREQ it twice.  The first time your system decided to
play silly buggers and keep on pausing to give me a timeout.

r> Good point. It's freely distributable, this series anyway. A newer version 
r> written in native MoonRock is being developed, that will be shareware and 
r> possibly a commercial/pro version too. As always I welcome people to use the 
r> earlier freeware versions with absolutely no obligations (and I'll still 
r> support them too).

r> What sort of wording do you suggest I use?

How about...

Copyright Rowan Crowe, all rights reserved.  
You may use this software in both commercial and non-commercial
environments free of charge.  You may distribute copies of this
program, so long as no changes are made to the archive, although
archiving with a different archiver is permitted.  Executables
created with moonrock may be distributed royalty-free.

It's up to you, I don't know what you actually want the 
restrictions to be.  Maybe you don't want people using it
commercially, etc.

r> BTW2, reckon I should also put disclaimers at the top of the sample 
r> programs? Here's what MickeySoft say:

Personally I reckon they are a waste of time, but there is no
actual disadvantage in putting them there.  The disclaimers
that people put there make it look like they were sued by
100 people last year for bugs in their program, even for free
programs, when in reality I've never heard of a single person 
getting sued for that in the world.  I don't bother myself.

BFN.  Paul.
@EOT:

---