I just noticed 1 more thing from the current release:
I have in my startup-sequence:
Run >NIL: C:AddNetInterface QUIET DEVS:NetInterfaces/~(#?.info)
And have user-startup with:
run >NIL: Work:TuneNet/TuneNet -stream
http://82.149.227.170:8000In earlier release Tunenet would keep trying to connect -- in 86.66 seems like it is not. Basically, with using the "run" for addnetinterface" it allows WB to bootup faster but its IP is not ready completely when TuneNet starts. Tunenet was okay with this before but the behavior has changed now