Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!umd5!purdue!decwrl!hplabs!hpl-opus!hpccc!hp-sde!hpfcdc!hpldola!hp-lsd!frisbee!matt
From: matt@frisbee.UUCP (Matt Taylor)
Newsgroups: comp.sys.ibm.pc
Subject: MS-DOS 3.2 XCOPY bug?
Message-ID: <158@frisbee.UUCP>
Date: 25 Apr 88 19:41:27 GMT
Organization: Maximum Storage, Colo Spgs CO.
Lines: 24
Keywords: MS-DOS xcopy


	Has anyone noticed any bugs in the XCOPY program for MS-DOS Version 3.2?
The symptoms I'm seeing range from complete failure with 'Access denied' to
'Internal Stack Failure: System Halted' later on during the copy.  By
changing the config.sys file and loading any drivers in different ways, I can
get the behavior to change (fails earlier or later).  The number of files
and the size of the files being copied also changes the behavior (maybe a
rogue pointer somewhere? :-) ). No TSR's are loaded up.  I can always get it
to fail with PC-NFS or other device drivers such as a WORM or hard disk.

[ Using the Periscope debugger with PC-NFS shows XCOPY not creating the
subdirectories during a recursive copy.  When it tries to create the file in
the nonexistent directory, it fails with 'Access denied' errors. ]  The
typical invocation is 'xcopy e:\ h:\ /s'.

The PC-DOS XCOPY and homebrew XCOPY programs work fine with all of the above
drivers.  Since I never use MS-DOS (we use PC-DOS here), I have no idea if
Microsoft has said anything about this or not.  Do they have a technical
number or uucp address to report problems like this?  Do they care if people
report problems like this (ie. do they do something about it)?

-- 
Matt Taylor @ Maximum Storage, Inc.    
Colorado Springs, CO.  303-531-6888   
{cbosgd,handel,hao,hplabs}!hp-lsd!frisbee!matt