Re: Running cp.exe

[Bob Proulx]

Nick

Note that I am not the maintainer but just another hacker on the bug
list.

> OS: Windows NT 4 / Windows 2000 from command line.
> Ive got the 3.16 prebuilt version of cp.exe
[...]
> When I run it from the command line, it messes with the command prompt,
> V:\Aurora\BuildScripts>cp
> v:/aurora/builds~1/cp: missing file arguments
[...]

Hmm...  I would have guessed that somewhere in the code it was doing a
chdir(dir_name) or some such where dir_name was gotten from a pwd()
call that returned the MSDOS 8.3 name instead of the new windows long
names.  But when I scanned the code looking for such a thing I could
not find anything that would have caused your behavior.  However the
version of the code I was scanning was test beta release 4.0.41, a
whole major release later than your version 3.16.

I am wondering if this is somehow related to the compiler used to
compile your cp.exe.  If it was a MSDOS compiler then perhaps the C
runtime startup libraries do not know about the longer windows names.
I do not know and cannot predict.  But perhaps compiling this with a
newer windows aware compiler would solve the problem.

If it were possible for you to update to a newer version of fileutils
it would probably help.  I am pretty much solely a unix programmer and
am at a loss to help when it comes to MS platforms.

Bob