Jump to content

Junction Dysfunction by Raymond Chen


Recommended Posts

The article mentioned...


"Windows 2000 settled on Documents and Settings, which provided a reasonably descriptive name for the directory but failed to take other factors into account."

and the MAX_PATH limitation for Win32 path names.


I ran-up against that all too often when backing up, restoring and porting users.  Take a name like...

"C:\Documents and Settings\David.H.Lipman\Documents"

That's 47 characters used up and the data hasn't even been defined yet.


My solution would be to use the SUBTitute command with something like...

SUBST Y: "C:\Documents and Settings\David.H.Lipman\Documents"


Then I could manipulate the data using "Y:" with less chance of bumping up against the MAX_PATH limitation.


C:\users  Certainly fixed that issue.

Link to post
Share on other sites

yeah ... it seems that some of the path names have gotten longer over the years while others have remained on the short side .

i ran into some problems with path/file names that were too long when retrieving files/data from crashed HDs ...

i have no real idea as to why as both systems were 64 bit ... the fast answer was to remove letters (mostly vowels) until the name was "accepted" .


heh , with one drive the data contained stories ... the file name was actually the first "real" sentence in the story with an underscore between words .

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.