I get this error. Anyone know how to fix it?
I am running win xp pro



HMODULE: 4194304
Unhandled exception EHandleOsError
Exception message:Exception happened in Xotella.Timer1Timer
Exception: EAccessViolation
Message: Access violation at address 004052C0 in module 'xolox.exe'. Read of address 00000045
Prev call stack: [004052C0]


Call stack:
[0050B92A]
[0043DED6]
[00421BA2]
[00528201]

I get the same thing, with the same OS and Xolox build as you. I even deleted all my .txt files before installing this build after using many beta versions. I have to restart Xolox many times a day. Any suggestions besides deleting txt files again?

Got this error:

HMODULE: 4194304
Unhandled exception EHandleOsError
Exception message:Exception happened in Xotella.Timer1Timer
Exception: EAccessViolation
Message: Access violation at address 004052C0 in module 'XOLOX.EXE'. Read of address 31333118
Prev call stack: [004052C0]


Call stack:
[0050789A]
[0043DEB2]
[00421B7E]

Using Win98SE, Zone Alarm 3.1.395

I got the same error occuring under Windows 2000 Pro SP3. I have to restart Xolox 1.4 multiple times during the day.

It's ironic that the last two beta builds threw no errors on the system, and now the shipped release of 1.4 does.

Also, I never notice anyone actually uploading files from my system anymore. There's no log of files actually uploaded by other Gnutella users, so I don't know if I have a problem or not.

OK, this new EHandleOsError in 1.4 is becoming EXTREMELY annoying. It seems to only occur when a file is downloading, which happens many times during the day.

Unless a solution is posted soon I'm going back to using beta build 474.

Three times now I have notice the EHandleOsError
error occuring under the following situation:

1. A file download is in progress.
2. The downloading file's progress indicator reaches 98%.
3. A message appears in the status window indicating something about a mismatch in expected data of the file (if these status messages were logged to a file I could give you the exact text).
4. The download progress of the file drops to 50%.
5. The EHandleOsError occurs.

This error may have something to do with the fact that a single file can be downloaded from multiple locations, and in certain situations the last few bytes of the file doesn't match. In the last few days I had one file that went fron 57% to 98% and back down again over a dozen times. It's possble that the EHandleOsError was occurring each time.

I'm turing off "Perform hash verify after download completes" on the Downloads tab of the Preferences box to see if this "fixes" the problem. I'll let you know.

Disabling hash verify didn't fix the error, but installing Xolox 1.4 build 502 did. Thanks.

Darth, GREAT to hear.

thanks for the feedback and everyone else's.

the coders think they have it now isolated to wXP. ** and a solution for it

they are hard at work and everyone's patience and feedback is much appreciated

Now build 502 is throwing this error too, but much less often than 490:

Version: '1.4 build 502'
Error message: 'HMODULE: 4194304 Unhandled exception EHandleOsError Exception message:Exception happened in Xotella.Timer1Timer Exception: EAccessViolation Message: Access violation at address 00404EB8 in module ''xolox.exe''. Read of address 39353918 Prev call stack: [00404EB8] Call stack: [00507ADE] [0043DEB2] [00421B7E] [00528239]'