Overly Chatty Penguins
The Ready Room => Off Topic => Topic started by: Lightning Blue on March 01, 2004, 01:45:23 PM
-
Comprende? :help:
Gotta love MS sometimes. :rolleyes:
-
I am stumped because google does not know
-
is PDPBR a folder name? my assumption says that there are too many subfolders for windows to handle, but thats guessing from the message, since 99% of windows messages are irrelevant, its probably wrong :|
-
http://support.microsoft.com/?kbid=320081 (http://support.microsoft.com/?kbid=320081)
Cause 4 might be related... supposed to be fixing other people's computer right now or I'd check more into it! :blink:
-
Happened while copying from one server over a hard VPN to another server.
PDPBR is a file name. 361 megs to be exact
I do the exact same thing twice a month. It's gone perfectly fine except that once.
Going from F:\Program Files\IHS\CD\Data to \\odessa-dc\ihs\data, so path length isn't the problem either.
:blink:
EDIT: Just zipped the lot and transferred the zip via good ol' HTTP and it went fine. :p
-
Has the box had scandisk/chkdsk and defrag run on it lately? Maybe it's just a really muffed up FAT?
Edit: Or that would work too.
-
I was gonna say go into DOS and do it like a man...
-
NTFS on Windows 2000 Server.
I'll have to try it at the cmd console next time.
-
I was gonna say go into DOS and do it like a man...
^^
-
Nope, DOS freaks out and times out. :rolleyes:
-
path too deep? but win had a 255 char max depth ... gg
yeah, http/ftp == good