JdBP>> So I don't understand. What are you trying to say by simply
JdBP>> cutting and pasting text that shows IBM's 16-bit CMD behaving in
JdBP>> exactly the way that I said that it behaves ?
BW> Except that that wasn't specified, and I'm not a mind reader. If you
BW> go back and re-read Darren's message he explicity refers to Warp 3.0,
BW> fp 40 and **32** bit CMD.EXE.
BW>
BW> Since I'm running Connect with FP40, it seems reasonable to suppose
BW> that cmd.exe had been updated to 32-bit.
I'm afraid that it *was* specified. Darren didn't state that the 32-bit CMD
was part of OS/2 Warp 4. He *asked* whether it was. Here's the very text
what he posted:
DH> Is the 32-bit command interpreter specific to OS/2 v4.0?
I then replied to him by saying that it wasn't, saying :
JdBP>> If you crank up IBM's 16-bit CMD, and run the TIME command
JdBP>> with the /? option, you will notice that it documents a
JdBP>> /N option.
and:
JdBP>> But documenting it in the help message is as far as IBM's
JdBP>> 16-bit CMD goes. It doesn't actually *implement* it, [...]
You joined the thread after that message. As you can see, far from it being
"not specified", it was made clear *every single time* that it was mentioned
in *every single post* that IBM's CMD was a 16-bit program. It was *always*
referred to as "IBM's 16-bit CMD". That's about as unequivocal on the subject
as anyone can get. So you didn't have to be a mind reader. You only had to
follow the thread.
JdBP>> Are you saying that you want the 32-bit CMD ? (-:
BW> Putting words in my mouth won't wash, either.
I'm asking you what you are saying, not telling you. That's twice that you've
mistaken a question for a statement. Once with Darren asking me whether OS/2
Warp 4 has a 32-bit CMD, which you mis-read as Darren stating that it had, and
once with the above question, which you've mis-read as me saying that you want
the 32-bit CMD.
In both cases there was a question mark at the end of the questions, and the
verbs and subjects were in the usual reversed order that English speakers use
for questions. So I'm not sure that there's anything further that I, or
indeed anyone, can do to make it more clear to you when something is a
question not a statement. So all I can do is to exhort you:
*Please* read messages more carefully.
¯ JdeBP ®
--- FleetStreet 1.22 NR
633/260
2501/209
* Origin: JdeBP's point, using Squish (2:257/609.3)
|