[QUOTE]Originally posted by Unregistered
[B]


Problem seems to be related with ports and or an rouge Peer sending some corrupt data also... the strange thing is only win2k+ is having this problem...




I have noticed two crashes with with Win98(Gateway OEM) since the update to 1.4.2 a few days ago. They seem to have occured after running for an extended period. I had not noticed any problems with the previous version.

Tom

Hi,

'GNUCLEUS caused an invalid page fault in
module MFC42.DLL at 0177:6c40049e.
Registers:
EAX=00000000 CS=0177 EIP=6c40049e EFLGS=00010246
EBX=00000000 SS=017f ESP=006cfa8c EBP=006cfaa0
ECX=004a3484 DS=017f ESI=00000000 FS=1927
EDX=00000000 ES=017f EDI=00000050 GS=11f7
Bytes at CS:EIP:
89 7e 04 e8 16 6a f8 ff 53 56 ff 76 04 e8 a8 6a
Stack dump:
ffffffff 00000000 004a3454 00800de0 004a34bc 00000001 6c389ef6 00000050 00000002 00000002 6c389e71 007f8f80 006cfb40 6c389e88 6c371ed5 00000050 .'

That's the error info. that I get when I use the current Gnucleus. I never used to have this problem. I have tried downloading an older version of the software, yet the problem persists. I didn't particularly want the latest version as 'evolve' works funnily. Why is mfc42.dll necessary? It's in the windows/system folder anyway for any app. to use, surely.

Yours,
'Gazza'.

Hi,

I've fixed my problem with mfc42.dll. It's not ideal as it stands, though, but it works perfectly (for me, anyway). I simply switched off my firewall protection (Zone Alarm). Hope this helps others or points them in the right direction.

Yours,
'Gazza'.

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

First , I have to say I ' m sad ... I can't use nucleus more than 1 hour .After this period , you know : MFC42.dll blabla !
When swabby gave us URL www.gnucleus.net , I download the clone Oasis.And...Incredible !!! No MFC42.dll crash during 2 days (Never happend before with gnucleus) .And so less freeze !!
Those who can't use another client like me , try it ! It ' s an ersatz .True.But a good one !
PS:Oasis 1.0.0b use same MFC42.dll on my PC.