On 10-21-1999, Bob Wright wrote to Jonathan de Boyne Pollard about New
DATE and TIME command.

BW>  JdBP> So I don't understand.  What are you trying to say 
BW> by simply cutting and
BW>  JdBP> pasting text that shows IBM's 16-bit CMD behaving in exactly the
way
BW>  JdBP> that I said that it behaves ?
BW> 
BW> Except that that wasn't specified, and I'm not a mind 
BW> reader.  If you go back and re-read Darren's message he 
BW> explicity refers to Warp 3.0, fp 40 and **32** bit CMD.EXE.
BW> 
BW> Since I'm running Connect with FP40, it seems reasonable to 
BW> suppose that cmd.exe had been updated to 32-bit.


Hello Bob;

Here is the method I determined (and assumed) that the CMD.EXE file is
32-bit:

Using my Filestar/2 file management utility program, I selected the
CMD.EXE file in the C:\OS2 directory.

I then pressed the "C:\" button on the Filestar/2 toolbar. (This
allows command line program execution).

This opened a dialog box to execute the file. There is a message on
the top of this box. It read: Executable file - (OS/2 windowable
32-bit)

Thus I assumed the CMD.EXE is an 32-bit OS/2 executable file.

If the file is a batch file, an old OS/2 16-bit executable, DOS or
Windows file, etc., the dialog box reports it as such.

Hope this clarifies things.


Regards,

Darren

Internet e-mail: darrenah@interchange.ubc.ca

 * KWQ/2 1.2i * AMD Athlon: Proof that Intel isn't working hard enough.

--- Maximus/2 3.01
7102/1