Topic: Yes, you've guessed it.
0811h, G4 working OK, G5 not showing grid maps and the IMT is covered in pink squares (tested in Opera and Chrome).
We are now over 6 months from the much-fanfared launch of G5 that was going to be the greatest thing in biological data presentation ever, would eliminate all the performance problems that were evident in G4, and (for all I know) bring everlasting peace and love to the world.
Instead, we have a dreadfully designed, fundamentally unstable mess that I don't believe has functioned properly for any consecutive 5 days since the launch. It is obvious to me and many others that the problem goes right to the fundamental design and structure, and the reason we are in this mess reflects a complete lack of effective testing of the systems during development.
When there is a problem, it seems that someone tweaks something in the hope that it will improve the situation, but without knowing what the real problem is. Matt posted the other day 'it looks like it was caused by a low down feature in Apache which has been disabled for now'. Well, sorry, Matt. That feature may be disabled, but the problem is still there (as it has been on and off since October last year). A while ago, a new problem was created (as Graham posted) by a change intended to correct a different problem. No evidence of testing there either.
I understand why the NBN corporate body is reluctant to admit what is obvious to the rest of us - namely that Gateway 5 is a complete mess which will not be sorted by tinkering around changing and disabling features here and there in the hope that the right feature has been targeted and that there are no unwanted knock-on effects. I think any corporate embarrassment will be short-lived if there is an acceptance that G5 is a disaster, and needs a proper analysis of the whole system, right down at the lowest levels of the software structure and design, to find out what is not working as intended and why. And then sorted.
Murdo