MagusBR Posted May 5, 2008 Report Share Posted May 5, 2008 Hi,I having some problems using Junction files; when I add then they work fine (the program do re-check files and start uploading/downloading). But if I stop and start again, an error like "job files not found" raises and I have to re-add the torrent and re-check all again....I think is cause of Junction files "haves two" filesize, 0bytes (the link point) and the real file. So, depending on the GetFileSize function, there is two returns.And for who asking "why junction?" there is the aswer: I love to separate and reorganize my downloaded files, but for that I have to move files to another disk (I usually rename the file names too) and stop seeding... So Junction points is a good solution ;-)See ya, Link to comment Share on other sites More sharing options...
jewelisheaven Posted May 5, 2008 Report Share Posted May 5, 2008 ... If you stop and recheck the files, why not just use set download location? Link to comment Share on other sites More sharing options...
MagusBR Posted May 5, 2008 Author Report Share Posted May 5, 2008 Because the file names doesn't match to the original in .torrent Link to comment Share on other sites More sharing options...
hermanm Posted May 5, 2008 Report Share Posted May 5, 2008 µTorrent 1.8 BETA has a "Relocate" feature which cares of file names not matching. If 1.8 beta is possibility for you, try it out. Link to comment Share on other sites More sharing options...
MagusBR Posted May 5, 2008 Author Report Share Posted May 5, 2008 I already tryed it and worked as the 1.7.7 Link to comment Share on other sites More sharing options...
jewelisheaven Posted May 5, 2008 Report Share Posted May 5, 2008 You use the Files tab, not the right click, advanced menu.Thus in 1.8 you can have a VERY_LARGE_TORRENT on several disks if say you have not enough space on one of them. Link to comment Share on other sites More sharing options...
GTHK Posted May 5, 2008 Report Share Posted May 5, 2008 NTFS junction points? Those are for folders, files get hard links. Link to comment Share on other sites More sharing options...
jewelisheaven Posted May 5, 2008 Report Share Posted May 5, 2008 soft links were in XP, hard links were included in Vista...and technically both are still junctions Link to comment Share on other sites More sharing options...
GTHK Posted May 5, 2008 Report Share Posted May 5, 2008 Usage : fsutil hardlink create <new filename> <existing filename> Eg : fsutil hardlink create c:\foo.txt c:\bar.txt Link to comment Share on other sites More sharing options...
MagusBR Posted May 5, 2008 Author Report Share Posted May 5, 2008 Yeah, but hard links works only for the same disk-partition, isn't it?I'll try old later the new feature, I'm "working" now =DTkz all, Link to comment Share on other sites More sharing options...
jewelisheaven Posted May 5, 2008 Report Share Posted May 5, 2008 Junctions only work on NTFS. I don't think it cares where it is as long as you have the services running (VSC if memory serves) and as long as the VOL_IDs remain valid.http://en.wikipedia.org/wiki/NTFS_junction_point ... apparently the 3.1 upgrade to junctions added cross-volume compatibility. So in Vista, you can do whatever you want except use it on a 3 year old computer. Link to comment Share on other sites More sharing options...
MagusBR Posted May 6, 2008 Author Report Share Posted May 6, 2008 Tkz jewelisheaven, worked as a charm ;-) Link to comment Share on other sites More sharing options...
jewelisheaven Posted May 6, 2008 Report Share Posted May 6, 2008 Awesome. Mind you, I still think some verification of whether or not there IS a problem with the resolution of junctions would be useful as more people (theoretically) migrate to Vista. I personally plan to jump to Server 7 (ca. 2012 unless it slips again) due to the bitter taste... but I urge those who use Vista to try these things. If there's a problem and uT can work around it.. the developers do their utmost to do so. One of the most recent examples is with the (broken) software raid filesystem filter driver on Windows Home Server. All files are apparently junctions and as such don't work well with the "bypass windows cacheing" options, and as such it was addressed- Change: diskio.smart_sparse_hash for broken file systems (like Windows Home Server)... which happens to be a feature FOR sparse files, which don't apply in that specific instance. I'm not sure if it's global... if you could perhaps verify that change also affects junctions it would be useful to know. I've personally never had trouble with junctions on XP. Link to comment Share on other sites More sharing options...
Greg Hazel Posted May 6, 2008 Report Share Posted May 6, 2008 Given a path is there a way to determine 1) if it is a junction and if so 2) where that junction points to? Link to comment Share on other sites More sharing options...
mungustas Posted September 2, 2008 Report Share Posted September 2, 2008 In my situation/scenario I had disks and catalogs d:\Part1 e:\Part2 f:\Part3made a f:\big.pack catalog, made symbolic links inside, made a torrent. But peers could not connect and download those files.With new ideas implemented in newer utorrent version, I was running 1.7.7 at that time, updating to >1.8 solved my problems and I started to seed!thank you very much!as jewelisheaven said: Thus in 1.8 you can have a VERY_LARGE_TORRENT on several disks if say you have not enough space on one of them. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.