When we try to run Netinstall on Wine, we get bind bootp failed: (10013).
Ok, this happens because it tries to bind to some low port that only root can bind. But, hey, if all I want/need is to install RouterOS on a local USB drive or local memory card, I don’t think we need bootp protocol.
So, can you make Netinstall work even if it can’t bind to such port? I don’t want to run wine as root, and we shouldn’t need to.
If I use sudo, it says: wine: /home/denilson/.wine is not owned by you
I really don’t want to mess with wine under root, so I will assume Netinstall won’t work under wine until this issue with binding to low ports is fixed.
And it should be easy to fix. If it can’t bind to the port, inform the user about that and continue anyway. That error should not be a fatal error. The application can (or should) work even if that error happens.
how should it work if it can’t bind to necessary ports? how can a apache-webserver work if it can’t bind itself to port 80? so get yourself comfortable with sudo (which is tricky sometimes) and resolve the permission problems with chmod (which is ugly but works), if you have no possibility to really log in as root and build a new wine-config.
Don’t act that redicilously, so a mobilephone shouldn’t start if it can’t get mobile network connection?
Netinstall should not require any network ports to write ROS to a USB flash-drive.
I also had this bind bootp failed: (10013) error with wine on my Macbook running IOS. To get around this and use winbox and Netinstall on my mac, I ended up just installing Virtual Box with a copy of Windows XP installed. Just modified the network adapter to be bridged to my MacBook ethernet port.