Unrar Not Putting Files Into Right Directories In 6.10

[MichaelW_]

I am having some problems with 6.10 in which when an unrar is occuring, the resultant directory structore is not correct. A whole slew of files which should be put into subdirectories are intstead put into the root directory. For example, 100 mp3's which should be in directories 1-10, 11-20, 21-30 etc will randomly drop some of the files into the root of the unrar. It seems to most often happen when the 255 char directory limit is being breached. Where in the previous builds of 6.x, It would warn me that the unrar failed (and stopped, thought it told me that par count should have been a good download). I would rather this be the result, so I could unrar it manually to a different directory rather than having to now manually put the right files into the right folders, which if the mp3 tags aren't there I can't do reliably.

It seems to be also happening when not hitting the 255 char limit as well in some files. Argh.

[Quade]

Yeah, run out of path space and Newsbin will land the files where it can. It suggests you should try unraring to a shallower path or disable some of the options that extend the path Newsbin uses.

[MichaelW_]

Can you put in an option that autounrar works everytime except when you choose download to folder named for subject? Or, if you could just have it name the folder for the subject alone and not subject + filename?

[Quade]

Be easier just to cap the subject length. How much of the subject do you really need?

[MichaelW_]

How about 80 characters.

[Quade]

Yeah, let me look at the code. 80's still pretty big but, I guess that's better than some of the crazy long subjects I've seen.

[apsen]

Could we have option of using 32K long paths?

Have it disabled by default for people who use crippled file managers like explorer if you must...

[Quade]

Been toying with the idea. I have to look at how much code needs to change. The MAX_PATH field is hard coded in a number of places. I'd probably have to switch all pathing to UNC pathing and then cap path length in software to prevent > 255 chars.

[MichaelW_]

Even better, just make it a variable and people can choose on their own. Worst case scenario they make it too long then newsbin just works like it does now. Or, in the 64 bit version at least, can you add support for UNC very long paths? eg \\?\C:\verylongpath. Technically, each path should allow up to 32,000 chars, just that each part of the path cannot be longer than 255. Lets break the shackles of DOS!!! :>

[Quade]

Or, in the 64 bit version at least, can you add support for UNC very long paths? eg \\?\C:\verylongpath. Technically, each path should allow up to 32,000 chars, just that each part of the path cannot be longer than 255. Lets break the shackles of DOS!!! :>

This is what aspen is talking about. What file manager will you use to access these long paths? Explorer, even 64 bit explorer, won't do it. I had long path support in it years ago. So many people couldn't access the files, because explorer can't access them, I removed it.

[apsen]

What file manager will you use to access these long paths?

Personally I use FAR Manager 2.0. There should also be others.

Actually you could even access them in command prompt if you cd close enough and use relative path.

Also you could use short file names unless you have disabled their generation but in that case you should be knowledgeable enough to figure it on your own. With short file names you would be able to access directories up to about 18 levels deep.

[MichaelW_]

Actually, this would work fine for me. It would let newsbin unrar the files as deeply or with folder names as long as it wants, and then I can fix the 1 or 2 files that can't live within the win32 limitations and then move the whole folder structure where I want. Make it an option so that it doesn't bother normal users who don't care.