Well I think its a bug - the first time I go to program the chip in a session, I have a message saying that security bits have been set and to confirm that I wanted this. BUT, I didnt set any! After OK'ing that I get the message about clocks bits which is correct as that box is ticked. Programming a second chip in the session does not bring up the security bits message.
I normally load FM by double clicking on a .fms settings file, and the chips are always programmed with the clocks bit set and the security bit NOT set.
Doesn't stop me programming of course, but thought I would mention it...
Ah, should have noted, this happens in version 3.20. Following an upgrade to 3.42 I can confirm it also happens in this version. Have had to go back to version 3.20 anyway. aaaah. :-\
Please email me the .fms file and the .hex file you are using so I can try to reproduce the problem here. Thanks.
Fixed in version 3.43, which will be released later today or tomorrow. Thanks!
Andy