Yes, the crash is fixed. Now, I get a popup saying that whatever type of share I am trying to mount, is an "unknown mount type". I reply to that popup, and it proceeds to, happily, mount what I requested. There is no evfsgui.err file now. If I try the mount from the New resource tab, I don't get the popup.
Ok, I see what happens, not sure why, but I will fix that, can't be too hard.
It seem that NMBD.EXE is starting before the DHCP stuff gets set up
Ok, I never tried that, however I this likely to fail. Eventually code could be added to smb.cmd to wait until DHCP has completed - however, don't expect to see that soon.
DMB
All you describe here is normal Samba behaviour. The DMB should always be present, in case it vanishes, it might take several minutes for another machine to take over, meanwhile requests will go to limbo - expect loooooong delays in such a situation. There are ways to make sure only a certein machine becomes DMB, this is a matter of RTFM ;-) (look for "os level" setting).
However while I thought over that all, it came to my mind that there's chance to see 2 DMB in the network neighbourhood with current EVFSGUI 2.5 - which is wrong, there is always only one DMB for one domain at a given time - if that changes while EVFSGUI still builds the network neighbourhood, and EVFSGUI already processed the earlier one and later on the new one 2 DMBs will be displayed - I need to think over how to fix that (which wont be trivial).
Just as a side note: Network neighbourhood (called ressource browser) in IBM Peer always was flaky and could easily block the WPS forever....