Hi,

I'm on Fedora 27. Winbox starts with delay and CPU goes to 100% for about 5 sec then everything is normal. I think it happens because of discovery. Does anybody get the same thing? How can I start it without discovery? (when I start it with an IP address and password in arguments the discovery doesn't skipped )

best regards, Gabor

Wine isn't exactly a little app, it takes some resources to start up. Is 5 seconds of high CPU load really causing a problem? I could understand if it hits 100% while in use, but just 5 seconds on startup doesn't seem like anything to worry about.

My notebook (Mac) is quad-core, and I get all 4 cores at 25% for about 2 seconds on startup of WinBox in Wine. So 100% on a single core would be understandable. But still, I don't think this is a problem, and certainly not a winbox problem. It also runs just fine on my little Atom with 2 cores running Win7.

Some of my best work on mikrotik is done with wine....... Carménère Reserve from Chile that is. badda bing!

I'm also using Winbox 3.13 on Fedora 27 in Wine. I don't really get the 100% CPU issue, but sometimes it does have a slight delay on startup to find my device. But other than that, it seems to work pretty well.

Wine takes some effort to start the first time after a clean reboot of your PC. I suppose it loads all that stuff it needs to run (dlls, libraries etc).

Winbox starts where you left it. If it was last on the "Managed" tab, next time you start it again, it will start on "Managed", so no discovery. If it was last on the "Neighbors" tab, it will start next time by discovering. Hope this is clear enough.

On my PC, a six-core (AMD FX-6100) cpu system, running Opensuse 43.1 and wine-2.0.1, it takes about 2 seconds @ 20% cpu use, from a cold start.
On my ancient netbook, 2-cores atom, it is the same cpu usage, but for about 5 seconds.

I think your system consumes time and effort normally, but if you think this is not correct, why not ask in wine forums? If any comes out, it would be a benefit for all of our community.

Hi,

I got "Windows Wine Loader is not responding" on each start, but after about 5sec is responding. I would take a try on a fresh Fedora 28.
Anyway:
creating Window Class routeros_null
creating Window Class routeros_connect
creating Window Class routeros_dbl_canvas
discovery started
rescaning
connecting to 127.255.255.255
connecting to 192.168.68.255
connecting to 192.168.122.255
*****it stops here*****
Strange that I have only 192.168.68.x and 127.0.0.1 interfaces...

best regards, Gabor

Well, this looks like a normal output to me.
This is my output: and when discovery starts: Network 10.160.0.255 is correct.

127.255.255.255 is localhost
Why don't you check your /etc/hosts file?

Hi,

thank you for the answers!
I installed a fresh Fedora 28 then the problem disappears