?

Log in

No account? Create an account
Today's first random discovery is that xcopy apparently has a 254… - 'Twas brillig, and the slithy toves did gyre and gimble in the wabe [entries|archive|friends|userinfo]
Thomas

[ website | Beware the Jabberwock... ]
[ deviantArt | the-boggyb ]
[ FanFiction | Torkell ]
[ Tumblr | torkellr ]

Links
[Random links| BBC news | Vulture Central | Slashdot | Dangerous Prototypes | LWN | Raspberry Pi]
[Fellow blogs| a Half Empty Glass | the Broken Cube | The Music Jungle | Please remove your feet | A letter from home]
[Other haunts| Un4seen Developments | Jazz 2 Online | EmuTalk.net | Feng's shui]

[Saturday 10th May 2008 at 10:51 pm]
Thomas

boggyb
Today's first random discovery is that xcopy apparently has a 254 character limit for fully qualified filenames. For added fun, the "continue copying on errors" switch doesn't work for this.

Next time I'll just image the laptop's disk.
Link | Previous Entry | Share | Next Entry[ 3 pennies | Penny for your thoughts? ]

Comments:
[User Picture]From: link077
Saturday 10th May 2008 at 10:14 pm (UTC)
Doesn't Windows have a 254 character limit? Or is that normally excluding the path?
(Reply) (Thread)
[User Picture]From: boggyb
Sunday 11th May 2008 at 12:00 am (UTC)
Sort of - usually the limit is whatever MAX_PATH is defined as (I think 260), but there's a special way of calling CreateFile and friends that has a limit of 30,000 or so bytes for the full pathname. I don't think the filesystem enforces any length limits on the path.
(Reply) (Parent) (Thread)
[User Picture]From: pakennedy
Sunday 11th May 2008 at 8:00 am (UTC)
Try robocopy. I think it walks the tree and avoids that problem.
(Reply) (Thread)