Would you do me a favor and report that netinstall failure to email@example.com
? Reference this thread. I've reported it before and gotten shrugged off as a crank, as if I'm the only one in the universe that it has ever happens to. Thanks.
Here is a copy my email:
I am writing to you regarding Netinstall of MikroTik.
ISSUE: Netinstall is NOT a straight forward application when needed to run (using RBwAPG-5HacT2HnD as an example).
REQUEST: MikroTik investigates with a view to making a modified version of Netinstall that is EASIER to run for recovery of MikroTik devices.
IMPLICATIONS: This way, users do not experience, perhaps, frustrations through time wasting via trials and errors when they need to use Netinstall. The combined effects of their experience with ease in recovering MikroTik device/s becomes a sure and safe way of owning MikroTik devices in the first place. Even for less familiar users. FWIW, I hold a certificate of MTCNA (it was acquired more than three years ago).
What happened was I upgraded firmware on the wAP AC (as a CAP) 'without first stopping its link with the CAPsMAN router (RB493G)'. Whether or not this makes it safer to upgrade the CAP, I am not 100 % certain. Its AP function then performs like having a mind of its own. It became unstable at times. Several tries of reset failed to get it back to working properly as prior to firmware updating. In fact, it actually still showed the previous firmware version for some reason!
In the end, I was left with no choice but using Netinstall. This is actually the third time that I use Netinstall to recover an unresponsive MikroTik device over my years of my using MikroTik. I love and learn a lot from using MikroTik. It's why I became a MTCNA.
Let me tell you that the first two occasions of using Netinstall left a bad memory in me in that it was not a quite straighforward process in my experiences. This time around, it takes on a new angle since the Mikrotik wAP AC RBwAPG-5HacT2HnD uses PoE. I actually tried the serial-to-RJ45 port cable at first in a rig, including 2 x PoE cables plus a RJ45 joiner, to effectively deliver PoE to wAP AC, as serial port does not give out power.
But the serial approach did not give result in the WAP AC showing in Netinstall as I expected. I thought it might have been due to my rather convoluted DIY rig. So I went on a search and came across 'whatlanisthis' original post (see link at * below). Hence my realisation that it can be done with a USB adapter.
Still, the wAP AC did not show up on Netinstall screen despite several tries and a few hairs lost later. I followed instructions referred to in the link.
After so many tries, it's really hard to pinpoint with precision which exact sequence of steps that gave me the Eureka moment when the wAP AC finally showed up on Netinstall. But that was only HALF of the battle. You see, I pressed the 'Install' button then I saw Netinstall indicating as if the new firmware being flashed ....but then it quickly stops without really doing it.....Rinse and repeat the process (so to speak).
At one stage, I almost gave up with the thought of acquiring a new replacement.
But my patience and desire got the better of me. Any businessman would regard my time spent as, perhaps, uneconomical if not unwise. For a Mikrotik wAP AC RBwAPG-5HacT2HnD costs some 145 Australian dollars, it took me literally almost a full working day to return it to normal working condition. Netinstall process took a significant amount of it.
In short, I recall doing 'more or less' similar steps that were described by poster 'macsrwe' in the same thread at the link before I succeeded in flashing a new firmware on my wAP AC.
In particular and I quote:
I have found the solution to this is to quit and relaunch Netinstall, choose "previous install" as quickly as possible, then the install button, then you will get the "formatting disk" message and everything will work. I have found that when I am able to use "previous install," the hang almost never occurs, whereas if I have to select different packages, the hang occurs more than half the time; also, the longer it takes me before I hit the install button, the more the chance of the hang increases.
The above background, while rather long winded (sorry), for reading is however much shorter than my time spent on using Netinstall just about every time. I kid you not. Nevertheless, it does give a full picture of my latest experience of Netinstall as a user. I hope that there could be a more DEFINITE guide by MikroTik on using Netinstall, taking into changes in Windows OS, in such a way that users feel comfortable of using MikroTik products. It can be a win-win for both MikroTik and its users.