ah - I got it under unusual conditions I finally got this MFC42 error - when I left Gnucleus running after the internet connection dropped with 12 files rotating requesting to refusing hosts overnight. (lots of fast destination unreachable returns - DCC running keeps TCP/IP stack alive but nothing reachable)
WI*** OSR w/DUN 1.3/winsock 2 upgrades, TCP/IP, NetBEUI only, MFC42.DLL v. 6.0.000
Seems that after thousands of cycles of sockets opening & closing in one windoze session a possible slight memory leak ?? (just guessing)
When trying nodes who are refusing - running down the list in the cache, opening & closing alot of sockets (most nodes connect but drop right away or give a shot of hosts then drop) I sometimes get an out of memory error -small box message from Gnucleus not windoze (not a system error) I can click on it & it'll disappear, Gnucleus keeps working (athough the HD thrashes a bit virtual swapfile activity 8.MB physical RAM)
When searching for a stable node connection if I pause it every min or two this never happens, both errors seem to relate to opening & closing alot of sockets quickly, the MFC error in my case rare & unusual (I fell asleep & let the internet connect drop & left Gnucleus re-trying a dozen IP's)
Limiting/pausing/slowing down opening too many sockets totally prevents either error, I can run Gnucleus all night with no error by doing so
(v.1.3.5 - 1.4.x is bigger so I haven't installed it yet)
so it's an on-going bug not something that slipped in recently. It's workable (preventable) and Gnucleus works great - you'd be shocked how well it runs on a 386 !
That means something in my book |