Emule Won't Share Relative Path Incoming Folder
#1
Posted 07 February 2016 - 03:47 PM
Only thing that's bugging me is the "Incoming" folder sharing. And no matter what I do, eMule 050a (I've also tried eMule 0.50b BETA1) detects the presence of files in the Incoming folder, rahashes them and yet total number of Shared Files remains at 0. And if I click Reload button again, it just rehashes all the files again and again ends up with zero shared files. What's going on?
I've even tried manually adding a shared folder and then by hand changing the path in shareddir.dat to ".\Incoming" to signify a relative path and still the same behavior.
Which is odd because toolbar skins folder can be set using relative path and works just fine, but files inside Incoming folder just refuse to be shared. How can I bypass/fix this?
Stulle @ Dec 7 2005, 06:16 PM
#2
Posted 07 February 2016 - 05:51 PM
2) Download binaries from sourceforge.net
3) Options extended, choose the last option (store everything in program directory), click ok, restart 2-3 times and set it.
come ottenere aiuto italian guides - guide della sezione italiana
italian support - sezione italiana scaricare la lista server
ottenere id alto impostare le porte nel router
recuperare file corrotti i filtri ip
Sembra talco ma non č serve a darti l'allegrIa! Se lo lanci e poi lo respiri ti dā subito l'allegrIa!
#3
Posted 07 February 2016 - 06:12 PM
Stulle @ Dec 7 2005, 06:16 PM
#4
Posted 07 February 2016 - 07:28 PM
I see them in the incoming folder, but the squares near them aren't ticked.
I have to select them all.
A beautiful dream for leechers: it's not a dream anymore, since years, it seems (click.
epsilon2, on 20 February 2010 - 08:34 PM, said:
Maybe this should be considered a bug. There could at least be some error message.
The beta file, re-created/re-shared on emule startup, isn't re-shared.
The verbose log shows only these strange lines on startup:
Quote
File shared twice, might have been a single shared file before - C:\Program Files (x86)\eMule\incoming\yyyyy.222
File shared twice, might have been a single shared file before - C:\Program Files (x86)\eMule\incoming\zzzzz.333
I agree it should be considered a bug.
come ottenere aiuto italian guides - guide della sezione italiana
italian support - sezione italiana scaricare la lista server
ottenere id alto impostare le porte nel router
recuperare file corrotti i filtri ip
Sembra talco ma non č serve a darti l'allegrIa! Se lo lanci e poi lo respiri ti dā subito l'allegrIa!
#5
Posted 07 February 2016 - 07:50 PM
While I was waiting for the answer, I've already written an app (a portable launcher) that reads its own location, corrects the preferences.ini entries relative to its own location and then fires up emule.exe
This way I can move around eMule folder as much as I want and it'll always point to correct Incoming and Temp folders while still sharing files.
I really hope this nonsense will be fixed within eMule 0.50b, so eMule could work as portable without a launcher. But considering no one cared about this rather significant bug for this long, I don't have much hope for seeing it fixed now...
Stulle @ Dec 7 2005, 06:16 PM
#6
Posted 07 February 2016 - 08:00 PM
Users that are using relative paths are not the majority.
I didn't even know them (rel.paths).
come ottenere aiuto italian guides - guide della sezione italiana
italian support - sezione italiana scaricare la lista server
ottenere id alto impostare le porte nel router
recuperare file corrotti i filtri ip
Sembra talco ma non č serve a darti l'allegrIa! Se lo lanci e poi lo respiri ti dā subito l'allegrIa!
#7
Posted 07 February 2016 - 08:48 PM
It just annoys me that I have to fiddle with "UsePublicUserDirectories" registry entry if I want to have it portable without modifying the binary. Which means it'll override settings for those who use eMule with settings stored in user profile and not app folder. Which is a bit annoying.
Stulle @ Dec 7 2005, 06:16 PM
#8
Posted 27 February 2016 - 12:29 PM
RejZoR, on 07 February 2016 - 11:48 PM, said:
The trouble with relative paths in general is that you must know exactly the origin.
That is, relative to what node in directory tree?
There are several ways do define the starting point.
For exmaple, it could be relative to:
- the root of the installation drive
- eMule's installation directory
- user home directory (which is already relative).
#9
Posted 27 February 2016 - 09:15 PM
Stulle @ Dec 7 2005, 06:16 PM
#10
Posted 27 February 2016 - 10:00 PM
RejZoR, on 28 February 2016 - 12:15 AM, said:
That might be good enough up to XP for a single user and one drive, but hardly otherwise.
The default installation paths (see Docs, Shared Usage) might be like
..\..\Users\<Username>\Downloads\eMule\Temp.
The case with different drives and multiple directories would be even worse.