The new portal for frozen@mid80 is at mid80.net. The .zip for download is there, too. If you would like to download that in the MSDOS batch file format, the following text box would help, though.
Legal Speak. Mid80.com, AND OTHER FILES/CONTENT AT THIS SITE, IS/ARE PROVIDED AS IS, WITHOUT ANY GUARANTEES. IT IS THE USER'S RESPONSIBILITY/CHOICE TO MAKE SURE, TO ENSURE CORRECT OPERATION (TO HIS/HER/THEIR SATISFACTION LEVEL), ON THE SET OF PROBLEMS HE/SHE/IT ENCOUNTERS. IN JURISDICTIONS, OR CONDITIONS, WHERE SUCH NOTICES LIKE THIS, WOULD STILL
LEAVE THE SOFTWARE/AUTHOR LIABLE FOR ANY DAMAGES, OR IN ANY WAY, WOULD LET LITIGATION TO EXIST,
PERMISSION FOR USE IS NOT GIVEN.
In the following text box, there is the
batch file for producing mid80.com. (See how to, if you need more info.)
historical download list, & the stepwise philosophy
This software is NOT complete, yet. In the spirit of flight & fight, I publish incrementally.
- mid80.com 1.0 was for monitoring the Nutt net, in Fig.2 of NN73.
- frozen@mid80 1.1 demo, was for monitoring new few, & closing to NN73 macros.
- frozen@mid80 1.1.1 demo, was with NN73 macro transitions -- NN73/VD78 subnets.
- frozen@mid80 1.2 demo, was with NN73 macro locations, & modifiable, too.
- frozen@mid80 1.2.1 demo, was with a few bugs
- frozen@mid80 1.3, was again buggy [less than 1.2.1]. Working, too!
- frozen@mid80 1.3.1, was reporting [sub]macro liveness & properness.
- This time, frozen@mid80 1.4, has the five-row "videoRAM", x1..x5 -- flexible in the frag menu.
- For a full SARA system, I may (or, may not?) need further documentation.
- For more of a repository (esp. VD78), the representing is not enough, yet. (Not verifying.)
- ... people new to formal-nets, may find pages like macro vs. makruh informative (& helpful).
- frozen@mid80, although simple enough for most people, is not with a full set of intuitive tools, yet.
the yogurt strategy?
I may find a few uses for buggy software-process
- For example, in the future, as historical examples of bugginess
- For flight & fight, this strategy of not fully-working, is optimal. Any stupid copycat may verbatim copy a perfectly-working algorithm, but if the buggy software is copied (& with the same fault-list), they get caught as thieves [& associated with other offenses]. ((If intel ("only paranoids survive"), & Microsoft (as Ray Ozzie told "I think [Microsoft has] a culture of always being a little bit paranoid, always looking out there and adapting.") find value in (well-thought) suspiciousness, well, I may have the makings of a successful enterprise, inshaellah. :-)) Seriously, as I'm fighting against plagiarist people who committed such things in broad daylight (grabbing from well-known prior art), then caution is in need of heeding.))
Thus, bugs (if) hiding in the software, may resemble the good bacteria, such as yogurt-bacteria naturally are. When good bacteria assert themselves, the evil ones have less chance to infest.
To explore what is working, and what is not, may have thrilling aspects, too. I think, w.r.t. days of unexpected electricity-outages, this test process is one-step higher, for a half-conrollable kind of experimenting.
If to continue from the state of the design that causes a software-crash, keep in mind to freeze that with the '-' (hyphen) to mid80.frz (& may rename that for archiving), before monitoring that.