Subj : Re: Copy In 4NT versus CMD
To   : All
From : Ronald G. Guenther
Date : Mon Feb 25 2002 08:40 am

From: Ronald.G..Guenther@f3.n342.z1.cereal.mv.com (Ronald G. Guenther)
Subject: Re: Copy In 4NT versus CMD

From: "Ronald G. Guenther" <Ronald.G.Guenther@NOAA.GOV>

Thank you Charles.
I thought 4NT was just that, for NT whose command shell just happens to be CMD.

Charles Dye wrote:

> On Tue, 19 Feb 2002 17:02:27 -0600, "Ronald G. Guenther"
> <Ronald.G.Guenther@NOAA.GOV> wrote:
>
> >Greetings!
> >
> >I have run into a problem with 4NT version 4.01A running on WINNT 4.0
> >Service Pack 3.
> >
> >In using alias calls, I have an alias calling another where the
> >parameter is the "nul" file parameter.
> >This part of the logic expands to copy nul %1, i.e., copy nul nul.  4NT
> >does not accept this.
> >
> >e:\4nt401>copy nul nul
> >nul => nul
> >4NT: Can't COPY or MOVE file to itself "nul"
> >     0 files copied
> >
> >Try the same command in CMD and it copies just fine.
> >E:\>copy nul nul
> >        1 file(s) copied.
> >
> >Is there some setting I am missing or is this a difference with which
> >one must live?
>
> That is the way COMMAND.COM behaves:
>
> G:\WINDOWS>copy nul nul
> NUL
> File cannot be copied onto itself
>         0 file(s) copied
>
> G:\WINDOWS>
>
> JP obviously makes a serious effort at keeping a high degree of
> consistency between their own shells.  So I suspect that making
> 4NT's behavior match CMD's would also entail making 4DOS act
> differently than COMMAND.COM.  Blame Microsoft for not keeping
> their own products compatible.
>
> --
> Charles Dye     raster@highfiber.com

--
Ronald G. Guenther
--
|Fidonet:  Ronald G. Guenther 1:342/3
|
| Origin: The Cereal Port BBS (603)899-3335 199.125.78.133 (1:132/152)


---
 # Origin:  (1:132/152.4)
 * Origin: Baddog BBS (1:218/903)

.