alright, this is the 6th time this has happened. before, Xolox wouldn't start up because because of " '$' not a vaild integer ". Now it won't start up, because of " '$ENT' not a vaild integer ". I've been really patient. I've posted twice, but no one replies. So, I've just deleted all the gigs of segmented files and started over. But it happens again and again. and i'm really ****ed off now. so someone, please, i beg you tell me what the hell is going on.

Careful fix: Slow but your settings are preserved and few downloads lost.

1) Check for a corrupted resumeinfo.txt
•All JOB tags should have 9 lines of stuff before the first SEGMENT tag.
•All SEGMENT tags should have 4 lines before the next SEGMENT or HOST tag.
•All HOST tags should have 7 lines before the next HOST tag or the end of the file.

If any of these are messed up, delete the last JOB in the file

2) Check for invalid registry entries. Go to Start -> Run -> Regedit and find HKEY_CURRENT_USER\Software\Xolox and compare the following entries:

key ------ my setting ------ valid settings ------ use (when 1 if not otherwise noted)

sockslevel --- "" --- ??? --- I don't use a firewall, if you do, then procede to the semi-drastic solution section.
sockspassword --- "" --- ??? --- ""
socksport --- "" --- ??? --- ""
socksserver --- "" --- ??? --- ""
socksusercode --- "" --- ??? --- ""
autohidebadresults --- "1" --- 0 or 1 --- hides bad results (unused crc funtion?)
autoupdate --- "1" --- 0 or 1 --- enables auto-updating of the software.
clearfinished --- "1" --- 0 or 1 --- clears finished or aborted downloads
completedir --- "C:\Program Files\XoloX\downloads" --- any directory --- place completed downloads here
current dir --- "C:\Program Files\XoloX\" --- location of xolox --- tells xolox where it's installed
dropincorrectsegments --- "1" --- 0 or 1 --- immediately drops segments that don't match the segment being resumed
FF --- "" --- let XoloX handle this --- encrypted family filter password, emty sting means no password, and no filter
firsttime --- "false" --- true or false --- doesn't seem to do anything for me.
incompletedir --- "C:\Program Files\XoloX\temp" --- any directory --- place where xolox puts it's partial downloads
maxuploadspeeditem --- "2" --- any integer --- self explanitory
shareddirs --- "edited out" --- any number of directories seperared by commas (but no more than one from a single directory tree) --- self explanitory
sharedextension --- "ace,asf,avi,bin,exe,gif,htm,html,iso,jpg,mid,mov, mp3,mpeg,mpg,ogg,pcx,pdf,ps,qt,ra,ram,rar,rm,swf,t ga,tiff,txt,wav,wma,zip" --- any number of file extensions seperated by commas (wildcards can't be used... ? * - etc) --- self explainitory
showsharedfiles --- "1" --- 0 or 1 --- shows your shared files on the "files" page
showuploads --- "1" --- 0 or 1 --- shows uploads on the "download" page
speedtype --- "0" --- 0 or 1 --- sets your speed type to broadband
switchtosavemode --- "1" --- 0 or 1 --- switches to save mode if there are lots of badly connecting segments
totd --- "0" --- 0 or 1 --- turns on the tip of the day
usemaxonidle --- "0" --- 0 or 1 --- turns off upload restrictions after 15 minutes of idle time


Semi-drastic fix: may have problems if you have a corrupted resumeinfo.txt file, but fixes any registry problems. All user settings are deleted.

Delete the key: HKEY_CURRENT_USER\Software\Xolox and start up xolox, re-set your settings.


Drastic fix: Fast and easy, it kills all of your cirrent downloads. (back up your /downloads directory first)
Delete your XoloX directory, delete the Xolox registry entry, then re-install XoloX.

Thank you, so much, Seeker.

I'm sure it took quite a long time to figure out how to help me with my problem, just by all the steps and different options. I really appreciate all the trouble you went to. You are truly a god that walks among us.

Seeker Rocks!!!

Copying the keys from the registyry took a little while, but otherwise all I did was list basic trouble shooting and resolutions to whatever problems you might be having. I still don't know what causes XoloX to crash for you, which is why I didn't answer any of your other threads. I'm no god.

Folks:
I had the same problem at Xolox startup: "$ is not a valid integer."
I found that that Utterly Opaque message disappeared when I removed the resumeinfo.txt file.
Since I had deleted and reinstalled Xolox, in an attempt to correct a (possibly related) problem which caused (still causes) my dial-up connection to disconnect, I had collected 2 versions of resumeinfo.
Being somewhat of a Buckaroo, I had edited the two together.
Having done so at an Absurd Hour of the morning, I had accidentally deleted a CR, causing 2 lines to become 1.

I finally located the problem by dicing the file into discrete segments and starting Xolox with each segment as "resumeinfo.txt."

When I finally found the error, it was really quite obvious!
And easy to fix....

Suggestion to the Gurus Behind the Scenes: perhaps the error messages could be couched in more obvious terms...?

Now, why does Win98 SE take to crashing to a complete Reset after Xolox has been installed for several days?
It seems to happen whether Xolox is running or not; I have had things go Boom with BearShare running instead!

I am beginning to suspect that only a complete reinstall of M$Win is indicated, with all the attendant pain of reconnecting all my apps...!

Thanks for a Pretty Good Thing, anyway!!