Just what is XoloX doing?
 

For an enlightening look at how XoloX works, you could run lsof (yay Cygwin!) or similar utility (Taskinfo, Procexplorer) and look at XoloX.

Or perhaps I should say "try" to look at XoloX because the number of files that thing has open will make an attempted listing of these files bring most mortal machines down to their knees.

Gee, why do I see Photoshop listed? My installed Photoshop. And all my installed apps, actually. Which aren't in the shared folder. Which aren't even on the same drive as the shared folder. Indeed, it looks as if XoloX has a file handle open on every single file on my entire system. Hot damn!

Makes sense to index everything inmy shared folder, sure. I was perhaps expecting to see all the DLLs and runtime files and all my shared files, but certainly not thousands and thousands of files all over my system nto at all related to the functioning of XoloX in anyway.

Is this cool? Is this necessary? Hmmm.

-X

same here
 

I checked that out in version 1.12 and noticed the same thing!! What the hell, is Xolox sharing my entire hard disk with the world???

I also tested a theory and did a search on the network for windows system files, rare ones, and files that most likely will not be shared, EVER, and I got over 250 sources for some of them.

What the hell is going on here????

Jesus F***inng Christ!!! I wondered why my DSL activity light was always on -- I thought I was simply doing my part in the indexing process. This is crap.

For those interested, do a search on something simple like photoshp.exe or readme.txt. You'll be amazed and enlightened. Any response from the developer?

umm...
 

Are looking at your shared files index, or a search of the gnutella network? When you first instal XoloX, it gives you a list of directries it thinks you should share. for me, the only directory it reccomends is c:\program files o.O It doesn't check hidden folders at the initial run, so it doens't see my media folders; I have to add them manually into the registry because XoloX doens't let me type in a new shared directory, and the tree it uses doens't list hidden folders either *gasps for breath*

Anyway, a search in XoloX will not show any files YOU are sharing, only files OTHER people are sharing, and a lot of people that use the g'net do stupid things like share entire hard drives. Basic rules of sharing are: don't share entire hard drives unless they are devoted entirely to media alone, Don't share program or system folders, and and don't share temp (incomplete) download directories.

The only things XoloX shares that you don't tell it to are: itself (for sending updates to other clients), currently downloading jobs (to other XoloX users, propogates files faster), and the /downloads folder (Which you should be careful about changing from the default, because if you tell it to place completed downloads in c:\ then your entire C drive will be shared)

(Edit)
PS, to the originator of this thread: I downloaded Taskinfo200, and am watching XoloX. It has the following files open: a few index.dat files related to IE (and not looked at, file pos = 0 usually 3 or 4) SHDOCVW.DLL (loaded) and any currently active segments that are downloading.

My guess is if you see programs listed there it's because you are running them at the time and listing all open files on the system, not just what's open by XoloX. If you see more than a few index.dat files, a DDL, and whatever active downloads open, send a screenshot of whatever it is you're seeing because I can't duplicate it. (For the record, XoloX is also currently using 110 handles, 107 windows, 6 threads, and is averaging < 1% CPU usage when in the tray.)

I can confirm Seekers info about open files, only a few (in normal operation, indexing not in progress). Some open index.dat + SHDOCVW.DLL (IE), one hostslist.txt and one file for each running job, partial or upload. Nothing else.
I'm currently observing memory consumption on different clients... didn't get a clue where all the memory goes to.

> Is this cool? Is this necessary? Hmmm.
Don't share your whole harddrive? (Can't reproduce Xolox opening every file on my system)

> What the hell is going on here????
Some newbies share their whole harddisks, isn't it obvious?

bad sharing restrictions
 

Funny, even though .dll's are not shown in the shared extensions list, ppl seem to be downloading them from left and right, even .txt files that i didn't want shared and made sure it was off the list are still being shared...sucky sucky. You make rules and the darn app doesn't even heed them. Memory violations up the wazoo in 1.12...1.11 didn't have this prob at all...hope 1.13 fixes this?

Screenshots
 

Could you take some screenshots of your preferences (sharing and downloads tabs) and of this activity you are claiming is happening?

I know of no one else with this problem.

The completed download location is shared. If completed downloads go straight into C: then you share your entire system.

> The completed download location is shared. If completed
> downloads go straight into C: then you share your entire system.

That is true! Oops. I think Xolox should not allow to use a root dir for download destination (e.g. C:), because than you would share those subdirectories too... which than means the whole drive.

Good idea for a bugfix - and better let Xolox not share download/temp subdirectories.

CU, Moak

WTF IS THIS

This app does start UPLOADING IN THE BACKGROUND
AT FULL RATE ...and it doesnt even care if a folder is shared
at all. It uploads the COMPLETE DIRLIST of all drives
to a unknown destination as soon as i start it.
My default shared folder contains 1 mp3 file.
After a couple of min i already had like 3 mb upload
traffic visible in my network meter without having a
transfer visible. As soon as i close it the traffic stops.

Also it shows me that i have a network problem in the
startup screen which is bull too..since searching works
and the program itself uploads without my approval.

Ill run a packet monitor on this this is really very
suspicious and im about to think that someone is pulling
a VERY BIG one here.

I dont wanna start flaming right ahead but this CANT be
a accident..no programmer can be such a stupid bunghole.