-=> Quoting Robert Bull to Leonard Erickson <=-

 RB> Hello, Leonard;

 RB> 02 Jun 03 18:27, Leonard Erickson wrote to Robert Bull:
 
 LE> Take command (and 4NT) are running console sessions, so they are still
 LE> subject to the limits placed by the OS. And rightfully so.
 
 LE> Basically, Windows NT/2k/XP (and OS/2) are not using "strong-arm
 LE> tactics". They are acting *properly* to prevent programs on a
 LE> multitasking system from trashing other tasks.
 
 LE> Windows 1.x/2.x/3.x/95/98/ME are *broken* because they *don't*
 LE> restrict programs to the alloted RAM and HW access.
 
 LE> Direct hardware access and multitasking don't mix at all well.

 RB> Hmmm, OK.  Starting from scratch, I will probably have to move from
 RB> 95/98  to XP at work.  When I do, I still want to be able to take
 RB> Procomm Plus  along.  That's partly because it's rock-solid reliable
 RB> and I don't want to  change anything, or even recompile scripts for the
 RB> Windows version of  Procomm if I can help it.  The other part is that I
 RB> simply don't like the  look and feel of GUIs and much prefer a
 RB> console-mode interface because I  find the screens much easier and
 RB> clearer to read. 
 RB> So, do I take it that Take Command will allow a DOS terminal program
 RB> to run  as expected, while still behaving correctly under Windows?

Again, you've got two different things confused. the "command
processor" and the OS.

Take Command sets up a character mode console session. 4NT replaces
CMD.EXE, they both give you a "character mode" *interface* to Windows. 

But either way, hardware access will be controlled by *Windows*, not by
them. Especially under XP. 

Basicly, if you can't run the program from Windows *without* the JP
software product, you aren't likely to get any better results *with*
the JP Software product.


--- FMailX 1.60