Re: Re clip will not work on new Windows 98 installation

["Robert Holmgren" holmgren@xxxxxxxx]

** Reply to message from Harry Binswanger  on Sun, 05 Sep 2004
22:47:19 -0400


> I didn't understand correctly what /c does. I thought it
> referenced COMMAND.COM, but your use indicates it means there are arguments
> coming.

No. The "/C" switch has been in place for 25 years -- in COMMAND.COM, and
later in CMD.EXE etc. It means, & has always meant, "carry out the command
specified by string and then terminate" (to quote from "CMD /?"). The "/K"
switch does the opposite -- the command processor persists after the command is
executed. /K is the default (implicit in COMMAND.COM). Zero relationship to
arguments.

> I haven't used DO since the 80s, and I thought it couldn't take
> arguments.

DO _only_ takes arguments! By itself it does nothing (incurs an error). You
have to "DO" something!

> ci ^dos/nv/x/z /c^do/nv/x/z kmd.exe /c^

Yikes! This is a situation-by-situation thing. I wouldn't do that. You'll
slow it down to a tortoise, all those unnecessary KMD.EXEs -- ridiculous.
Besides, use COMMAND.COM, not KMD.EXE -- as I wrote in my followup.

> Okay, the results are in: U2 still runs
> after global change of DOS/nv (etc.) to DO/nv (etc.)
> But CLIPW doesn't work...
> clearly all that is needed is a DO/nv/x/z CLIP.EXE somewhere

Don't tinker with that frame. The commands are where they must be. Just do
what I prescribed, for the "three instances" of DOS/NV.

Enough. Back into my hole. So long

-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------