Its hardware detection and has to do with CPU timing. Adding a secondary check is a makeshift way of fixing it and its better to just nip it at the source.
This was a response to my post:
One would think that a simple fix for Dlink would be to make a "double boot" part of the boot process itself. A hard boot, ac on, would toggle a switch that identified the completion of the initial hard boot and then the unit would immediately perform a secondary "soft" boot and clear the switch.I would agree that my suggestion is a "makeshift" way of fixing it and your suggestion that "better to nip it at the source" is truly the better solution.
But one truly has to wonder, now weeks later, whether Dlink can "nip this at the source" at all. And whether my proposed makeshift solution wouldn't be an easy fix to implement right now until they figure out a way to address the timing issue once and for all?
