So the QWave beta is done. While this may have seemed to be an odd priority we wanted to do this mostly as it was important to find the size baseline. MASM32 programs can be really small; QWave was only 6kB... yet it seems the smallest stub program in VS C++ is about 12kB... and QWave 2.0 is currently 15kB. However QWave 2.0, unlike the current one, actually still works. Not sure what is the issue, probably Unicode is default now and that was never supported. Might look into it at a latter date. In any case the C++ versions will be at least slightly bigger, which is what has been seen so far. iTimeSync for example is about 50% bigger. Do note though that we are not compiling for size; optimised C often has unrolled loops for example. This is OK in reality. Maybe we should ret-con ACAP to be As Compact As Practical? Hmmmm.... Anyway, so what is next? Well there is some other research to do that porting QWave enabled, but probably Egg as it still is quite popular, although the temptation is there to do easy ports like Slam, Volt and Stims. Probably not though. Could be smarter to alternate between a big port and a small one. QWave 2.0 highlighted that it can be done quite fast. In fact more time was spent on re-arranging code for minimum size, writing tests, and rebuilding/testing other programs affected by these changes. Might do some more work on iTimeSync, but there is no intention to finish it for at least a few weeks because, as expected, working on different programs highlighted improvements for all. But some of the missing features like server scanning might be finished. Also, still have not written that tool we wanted.... and this rant is long enough. Back to work!