|
s240779

Registered: 12/07/10
Posts: 12,880
Last seen: 2 months, 9 days
|
Windows' issue with long file addresses
#19406965 - 01/12/14 05:25 AM (10 years, 19 days ago) |
|
|
What I'm talking about is this:
folder1\folder2\folder3\folder4\file
That can't exceed a certain number of characters. Does anyone else have an issue with this? I think it's absolutely absurd. scientific studies, for example, generally have pretty long names, and I'm often forced to shorten the name. And what's hilarious is if I simply moved it to the desktop, Windows wouldn't give me the problem, because that would lessen the number of items in the address.
This has to do with the file system, right (e.g. NTFS and FAT32)? I would imagine there are file systems that are very liberal? what are you preferred file systems?
|
deadwk
00101011


Registered: 06/17/09
Posts: 8,890
Loc: Canada, eh?
|
Re: Windows' issue with long file addresses [Re: s240779]
#19418843 - 01/14/14 06:32 PM (10 years, 16 days ago) |
|
|
I'm confused with what your problem actually is. File names can be ridiculously long in windows, in fact I don't think Windows has a file name limit. You MIGHT be getting errors trying to use restricted characters in your file names.
|
s240779

Registered: 12/07/10
Posts: 12,880
Last seen: 2 months, 9 days
|
Re: Windows' issue with long file addresses [Re: deadwk]
#19418884 - 01/14/14 06:38 PM (10 years, 16 days ago) |
|
|
No, dude. I think I'd know the difference. I was clear of the fact that the total address can't exceed a certain number of characters. So, a study where its title is used as the filename might work on the desktop because everything on the desktop is just desktop/filename but not in deep in folders, because then it's preceded by folder/folder/folder/folder/filename, pushing it over the limit.
|
Ythan
ᕕ( ᐛ )ᕗ


Registered: 08/08/97
Posts: 18,774
Loc: NY/MA/VT Borderlands
Last seen: 9 minutes, 28 seconds
|
Re: Windows' issue with long file addresses [Re: s240779]
#19420357 - 01/14/14 11:29 PM (10 years, 16 days ago) |
|
|
It's just a dumb software limit in Windows, NTFS supports 32k character filenames. You should be able to bypass the 255 character limit for paths in most software by prefixing it like so:
\\?\c:\some\very very very very\long\path\goes\here\and\it\should work because\of the weird double slash\question mark thing\
|
s240779

Registered: 12/07/10
Posts: 12,880
Last seen: 2 months, 9 days
|
Re: Windows' issue with long file addresses [Re: Ythan]
#19421405 - 01/15/14 05:55 AM (10 years, 16 days ago) |
|
|
Interesting. Thanks.
I take it more intelligent file systems are usually employed for open source operating systems?
|
imachavel
I loved and lost but I loved-ftw



Registered: 06/06/07
Posts: 31,375
Loc: You get banned for saying that
Last seen: 12 hours, 9 minutes
|
Re: Windows' issue with long file addresses [Re: Ythan]
#19422311 - 01/15/14 11:02 AM (10 years, 16 days ago) |
|
|
Quote:
Ythan said: It's just a dumb software limit in Windows, NTFS supports 32k character filenames. You should be able to bypass the 255 character limit for paths in most software by prefixing it like so:
\\?\c:\some\very very very very\long\path\goes\here\and\it\should work because\of the weird double slash\question mark thing\
windows at it's finest. It'd be retarded for someone to think that there is some hardware limit restriction that windows is made to run on something that stores the file names and can't go over a certain amount of KILObytes none the less
just a restriction written into the software in some core file and probably looks like this
// character limit # 16
or something or another I don't actually know what c sharp code looks like but something similar
--------------------
I did not say to edit my signature soulidarity! Now forever I will never remember what I said about understanding the secrets of the universe by paying attention to subtleties!
I'm never giving you the password again. Jerk
|
imachavel
I loved and lost but I loved-ftw



Registered: 06/06/07
Posts: 31,375
Loc: You get banned for saying that
Last seen: 12 hours, 9 minutes
|
Re: Windows' issue with long file addresses [Re: s240779]
#19422345 - 01/15/14 11:11 AM (10 years, 16 days ago) |
|
|
Quote:
Da2ra said: Interesting. Thanks.
I take it more intelligent file systems are usually employed for open source operating systems?
just a setting written into the OS somewhere. A more intelligent file system is just written to be accessed simpler/be written with the ease of the programmer in mind/have less updates in the file system where an entire library is updated just to make a few changes to a few basic lines of code with no other specific things re written.
Basically the file system has nothing to do with it. The file system is just an interface for the user to use programs/files with the hardware on a more advanced level. A bios menu could potentially be entire interaction a person has with computer hardware, but an OS allows things to be rewritten and changed and files stored and saved for the user experience. A more liberal file system is more of a way of saying "a file system written to interface with the hardware with less mistakes" really then it is saying "a more advanced file system." As much as I'd rather believe the latter is true, it isn't so, an OS is made to give the user the experience of being glued to the hardware and being able to use and change it whenever it wants. The file system is written with the user in mind, mistakes clearly show inferiority but in a basic sense more reliable file systems like linux etc. aren't written any more efficiently they are just more basic and less changed so the user can get right to the fucking point and more emphasis can be made reliability and integrity instead of just constantly updating an age old kernel to be flashier and occasionally modifying imperative files.
Does that make sense?
--------------------
I did not say to edit my signature soulidarity! Now forever I will never remember what I said about understanding the secrets of the universe by paying attention to subtleties!
I'm never giving you the password again. Jerk
|
deCypher



Registered: 02/10/08
Posts: 56,232
|
Re: Windows' issue with long file addresses [Re: imachavel]
#19428964 - 01/16/14 04:18 PM (10 years, 14 days ago) |
|
|
Just for fun, try making a folder with the name "con" from the GUI in Windows. 
For extra fun, you can make such a folder from the command prompt like so: "mkdir \\.\c:\con", but then you can't delete the folder from the GUI.
-------------------- We are all in the gutter, but some of us are looking at the stars.
 
|
s240779

Registered: 12/07/10
Posts: 12,880
Last seen: 2 months, 9 days
|
Re: Windows' issue with long file addresses [Re: Ythan]
#19589620 - 02/19/14 11:59 AM (9 years, 11 months ago) |
|
|
Quote:
Ythan said: It's just a dumb software limit in Windows, NTFS supports 32k character filenames. You should be able to bypass the 255 character limit for paths in most software by prefixing it like so:
\\?\c:\some\very very very very\long\path\goes\here\and\it\should work because\of the weird double slash\question mark thing\
I've gotten to the point where I definitely need to use this, and came across the same advice when Googling ways to bypass this character limit. But how exactly do I implement this?
By the way, if you guys have any recommended books/videos/etc. on how to switch over to Linux, please share them with me.
|
|