Xolox still incompatible with Zone Alarm...
 

I always had trouble with XoloX because of some unknown incompatibility with ZoneAlarm. When ZA is running, XoloX freezes on startup. When I diasble ZA and restart the computer, XoloX runs well. I have ZA version 2.6.362, security level set at Medium, all permissions granted to ZA.

I wrote to Zone Labs about this and, incredibly, they replied, but only to tell me to set security level at Medium, something I had already tried.

I had this problem with XoloX 1.12 and now with 1.19

ZA doen't seem to cause problems with other P2P apps, such as winMX and Gnotella.

Any other people out there with this problem? Any fix?

My computer is a P III 550 with 128 MB, Asus board, Soundblaster 128, ATI 16 MB video Win 98 SE ...nothing unusual

Thanks

Hmm...

I am running w2k without any problems...

I will test it with 98se!

Morgwen

same here. i have zone alarm and xolox wont even connect even when i allow it to connect to the net.

I am the Unregistered who started this thread. Would like to know from the last Unregistered if he just can't connect or if XoloX also freezes on startup.

Waiting for news from others

Freezer

Did you give the permission to act as a server? If not try it again...

Morgwen

Yes I gave it permission to act as a server. It is more complicated than that. If no one else has this problem, then it has to do with something particular to my system. On the other hand, if many people have this problem, then the problem could be related to XoloX itself.

Freezer

I am running Win XP with ZoneAlarm and I find that I have to shut down the firewall when using xolox. With ZoneAlarm running I can connect to the network, and search but I cannot d/l anything. When I shut it down it works okay.

Do you have ZA Pro? I run ZA Pro 3.0.118 on Win98se since 1.18 and it does fine, although it does take it a little longer to connect to the network.

Xolox 1.20 (build 177) is running fine for me on a Win XP Pro system behind both a hardware firewall (Linksys DSL Router) and a software firewall (Zone Alarm Pro, ver. 3.0.118).

"Xolox 1.20 (build 177) is running fine for me on a Win XP Pro system behind both a hardware firewall (Linksys DSL Router) and a software firewall (Zone Alarm Pro, ver. 3.0.118)."

Same here, never a problem. For many months with any version of ZAPro.

when I use Zonealarm normal with xolox 1.12, I notice the red lines go beserk. It seems to be using the network connections for itself. Sends things to itself a lot. I run an AMD K6 500 and it can be a lot of problems in win98. However, in win2k it runs with no probs.

Sometimes my system will completely hang for a minute and return back to normal. Is this fixed in the latest xolox?

I am using zonealarm 2.6.362

thanx

I am running Zone Alarm 2.6.362 and CA's EZ AntiVirus under
Win2KPro.

No experiencing the problem with either version 1.18beta or 1.20.

Have you disabled the "Tip of the Day"?

I did that, and the program would hang on launch. Followed the
directions in the FAQ to remove the registry entry, reinstalled and
was back in business...

Re: ZoneAlarm
 

I'm using zonealarm 2.6.231, also set at med. and have no problems with this program downloading. Also using crashguard 2.0 and norton auto protect. When I tried winmx and imesh neither one of them would run right. It sounds more like a program problem not a problem with incompatible to za. Try removing xolox and download it again, It may be just a bad download.

Try Sygate personal firewall 5.0, build 1117.

Is there a fix for this?
 

Hi, I'm running a Win98SE P3-500mhz w/256mb RAM
and ZA ver. 2.6.362

Xolox ver. 1.18

It really didn't seem to matter if ZA was left on or not on my sys.
(these same things I listed below happened anyway with ZA on or off, didn't matter.)

When I first installed it it seemed to work fine, but then the
probs started happening.

1. I would get 75% done with a dled and then it would always stop! (never could get the rest of the file(s) either)

2. then about 15 minutes into a downloading session with Xolox
my 'Resorce monitor' started going haywire! Xolox would SUCK all my Resorses down to 0! and then back up again, then back down , then back up etc etc for about 3 minutes or so, this also didn't go away, every 15 minutes or so there after xolox would do it all over again. Is there a fix for this?

3. now for some reason after a week or 2 worth of download stuff off xolox, I get any connections to dled a thing!

any help would be great! thanks, Kryaxx

Try to upload 1.20 and see if that works.

I had a similar situation. Xolox hangs from time to time and after a while all of the ressources are down to zero and I have to close some applications. Mouse reacts slowly.
But there was only one solution: shutdown zone alarm. I had also problems with Bearshare (when shutting down) and Morpheus (reacting slow, hanging) due to Zonealarm. Logical conclusion: blame it on ZA.

Giving Up
 

I started this thread and I want to say that I have given up on XoloX for now. I tried upgrading to DirectX 8.1 and to the latest driver for my video card. Even if I have cable, I tried installing XoloX with a modem configuration to reduce bandwidth. Nothing helps. XoloX freezes and freezes my system. So I give up. I will try it again when a new version comes with the news that the incompatibility with Zone Alarm has been fixed.

Also, XoloX has to fix the enormous upload bandwidth consumption. When I get it to work (ZA disabled) XoloX burns upload bandwidth at the rate of 1 MB a minute, when uploading no file...This is excessive for someone whose ISP limits total monthly upload to 1 GB. I would not be surprised if this behavior had something to do with the freezing problem

Freezer

I have the same problem, with xolox and zone alrm, my machine
slows down. so much that i just give up and reboot. So your not alone. Resources seem to be sucked dry. All permissions are set up, wish it was that simple. Got tired of fussing with it, so i just turn zonealarm off before i start xolox. Their just not compatible on certain machines with certain software or set ups.sorry for not having the answer, at least i just didn't say it works fine for me.

Use a normal firewall rather than ZA and simply allow port 6346 TCP, in and out.