PDA

View Full Version : filestream error


View Full Version : filestream error


capt java
May 6th, 2002, 08:32 PM
When I start up xolox, I can search for and find a variety of files, which is fine. However, ANYtime I attrempt to download anything, I get a message at the bottom which says "filestream error--> 1" what is this and does anyone have any ideas on how to correct this. I have a cable connection and have no other connectivity type problems.

MusicMan
May 6th, 2002, 08:43 PM
Just thought I'd move this into the Gnutella section for ya, more topic specific.

Rickio
May 9th, 2002, 07:02 PM
try deleting the registry entry and re-installing.
I also had problems till I figure to look at the registry and it seems you can easily mess it up by deletling your downloads to fast. You know when you decide to give up on a file and you cancel it, well if you cancel a few fairly quickly it just mangles something. That's all I know and re-install will fix ya up but not unless you clear it's registry entry, as I re-installed 3 or 4 times and it would not fix till I figured it out.

markyrwol
May 20th, 2002, 11:19 PM
The Quick fix: Reselect the temp and completed download folders.


The detailed fix: Over and over I hear of people complaining that they are getting a filestream error------->1 despite there being numerous posts about it. However, the fix that is being given while working in many cases does not tell the full story.

Due to multi-segmented downloads (where one file in downloaded by taking different parts of it from more than one person who has the file then reassembling the file once all parts are through) XoloX needs a folder to be specified in which it can download these individual parts. It also needs to be told where to put the file that has been complete and assembled.

filestream error------->1 is where XoloX has not been told where it is to put these files. Xolox cannot run if it does not know what to do-you’re telling it what to take, where to take it from but not where to take it to.

To sort this you must tell XoloX where to take the files. This is easy. You have two options:

Option 1 is the most common solution to the problem. Create a “downloads” and a “temp” folder in the XoloX directory. If you have not told XoloX something else in the past then this will work as the XoloX default is for these folders which I assume are not created because of option 2 which is what I think the original developers intended.

Option 2 is where you create any folders anywhere on a hard drive and tell XoloX to put files there. You do not even have to create new folders - just tell XoloX to put all files into the XoloX directory but please note that I do not recommend this. What I do recommend is that you create a folder in which XoloX can put the temporary files separately. This can be anywhere and be called anything. Mine is called incomplete for example. The advantage of having these files kept in a folder on their own is that there is never any need to go into it and the files inside will never be deleted by mistake.
You also need to tell XoloX where to put the finalized files. This is also completely flexible. XoloX will put them anywhere that you ask on your hard drive and you can name the folder what you want - be it downloads/new/music/films - you name it, you can have it.

OK... Now that you have created these folders you need to tell XoloX where they are and what they are called. This is easy.
Open up XoloX
go to tools
go to preferences
go to downloads
click on the "..." button to the right of the move downloads to this directory when complete
choose the folder in which u want your complete files to be put
click on the "..." button to the right of the save incomplete files in this temporary directory
choose the folder in which you want the parts of files to b stored.

After this you should no longer receive the filestream error--------->1 and you can also have your downloads put wherever you want. You must remember that if you move your folders for downloads then you must tell XoloX otherwise you will get this error again.

I hope that this helps not only to explain how to fix the error but that it also allows everyone to understand why it happens in the first place.



Xolox_girl wrote this I just spell checked it and copied it here. www.geocities.com/xolox_girl