Hi All:
I dont think freezing issues are Darwin related. At least I havent seen any that were. I highly suspect more reported
issues are script related at this point. M3,M4, and M5 dont work because the scripts arent designed to actually do anything,
at least on my versions.I think youll have to wait for the full release versions for proper scripting, or as users play with various
plugins as they get released youll see scripts being written and tested.
I guess as Darwin is the first plugin to be seen by the masses I think its done pretty well and at least helped to identify some
of the shortcomings of the API which will get corrected as time goes by. M4 doesnt for example tell a plugin if a signal is low active
or high active, it just send a 1 or 0 to the signal. While that may work on some systems, I think its important for the plugin to KNOW
this is an ON condition which happens to be a 0, or a OFF condition that happens to be a high. Im sure such things will change over
time as these shortcomings are found. Ill let Darwin sleep for a short while now while others test and report, and the M4 team get
things more ramped up. Gearotic's new CAM modules are calling me and my laser is getting close to experimenting level, so
forgive me if I disappear for a bit, Ill answer questions and such as they appear but I think Ill leave development of Darwin alone till
it all catches up to me.

Art