H
hls
In all my years, I've never encountered a problem with the XCOPY command
until now. I am wondering if something could provide some input. Is it a
known bug? This is on Windows 2000/PRO updated to the
latest service packs.
First, I thought it was a driver bug with my IOMEGA ZipDrive when I was
trying to xcopy a folder layout to the zip drive.
For example, drive Z: is a Mapped drive and drive I: is my zip drive, via a
DOS window, I type the following commands
i:
cd \builds
xcopy z:\builds\cd cd /E /S
The result is:
Does cd specify a file name
or directory name on the target
(F = file, D = directory)? d
File creation error - Incorrect function.
Unable to create directory - I:\builds\cd
0 File(s) copied
The CD directory was actually created but nothing else.
I checked with IOMEGA support but nothing in their KB or support staff
helped.
Copying the folder via Explorer worked fine so I chalked it off as a
ZipDrive File I/O Driver bug or something, that is until now....
The whole purpose of creating the folders on the zip drive was to sneaker
net to another site with the zipdrive diskette. Since that was a problem, I
figured I'll just use my laptop with XP/Pro instead.
So I created a shared folder called "mywork" on my laptop. From my Windows
2000 machine I mapped the drive q:
net use q: \\mylaptop\mywork
created a builds folder in the mywork folder, then opened a DOS box to
repeat the steps:
q:
cd \builds
xcopy z:\builds\cd cd /E /S
The result is:
Does cd specify a file name
or directory name on the target
(F = file, D = directory)? d
Access denied
Unable to create directory - Q:\builds\cd
0 File(s) copied
This time I see a Access Denied error. So now I am not sure if this some
other issue unrelated to the ZIPDRIVE. The security is full access between
the laptop and my local machine.
Again, using Explorer, the copying of the folder works as well in this
scenario as well.
I explored to see if it was a long file name issue so I checked the source
tree directory and file names. Everything was 8.3 format and the deepest
tree level was 3 folders deep so it can't be some length limit.
Any clue of what could be happening here? XCOPY has been a common and high
usage utility for the longest with never an issue like this.
PS: I Checked MSDN for related issues and I found Q132759, "XCOPY from
LFN-Only Drive to SFN-Only Drive Generates Errors". While it directly
reflect the symptoms, the reasons in the Windows 2000 to Windows XP xcopy
scenario do no apply as both the source and target is NTFS.
Thanks in advance
until now. I am wondering if something could provide some input. Is it a
known bug? This is on Windows 2000/PRO updated to the
latest service packs.
First, I thought it was a driver bug with my IOMEGA ZipDrive when I was
trying to xcopy a folder layout to the zip drive.
For example, drive Z: is a Mapped drive and drive I: is my zip drive, via a
DOS window, I type the following commands
i:
cd \builds
xcopy z:\builds\cd cd /E /S
The result is:
Does cd specify a file name
or directory name on the target
(F = file, D = directory)? d
File creation error - Incorrect function.
Unable to create directory - I:\builds\cd
0 File(s) copied
The CD directory was actually created but nothing else.
I checked with IOMEGA support but nothing in their KB or support staff
helped.
Copying the folder via Explorer worked fine so I chalked it off as a
ZipDrive File I/O Driver bug or something, that is until now....
The whole purpose of creating the folders on the zip drive was to sneaker
net to another site with the zipdrive diskette. Since that was a problem, I
figured I'll just use my laptop with XP/Pro instead.
So I created a shared folder called "mywork" on my laptop. From my Windows
2000 machine I mapped the drive q:
net use q: \\mylaptop\mywork
created a builds folder in the mywork folder, then opened a DOS box to
repeat the steps:
q:
cd \builds
xcopy z:\builds\cd cd /E /S
The result is:
Does cd specify a file name
or directory name on the target
(F = file, D = directory)? d
Access denied
Unable to create directory - Q:\builds\cd
0 File(s) copied
This time I see a Access Denied error. So now I am not sure if this some
other issue unrelated to the ZIPDRIVE. The security is full access between
the laptop and my local machine.
Again, using Explorer, the copying of the folder works as well in this
scenario as well.
I explored to see if it was a long file name issue so I checked the source
tree directory and file names. Everything was 8.3 format and the deepest
tree level was 3 folders deep so it can't be some length limit.
Any clue of what could be happening here? XCOPY has been a common and high
usage utility for the longest with never an issue like this.
PS: I Checked MSDN for related issues and I found Q132759, "XCOPY from
LFN-Only Drive to SFN-Only Drive Generates Errors". While it directly
reflect the symptoms, the reasons in the Windows 2000 to Windows XP xcopy
scenario do no apply as both the source and target is NTFS.
Thanks in advance