Sorry, they are unrelated questions/observations. But, if block mode was
still easy to use under UX, why couldn't we use it? That's what prompted the
query about how it was killed...
jp
----- Original Message -----
From: "Tom Brandt" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, August 15, 2003 2:01 AM
Subject: Re: [HP3000-L] QCTERM, BLOCK-LINE MODE


> At 11:32 AM 8/13/2003 -0500, Peter Smithson wrote:
> >  In article <[log in to unmask]>, [log in to unmask]
> >says...
> > > Wirt,
> > >
> > > How did hp kill Block Mode in UX?
> > > Due to the large amount of code we have, probably our only option
(apart
> > > from COMPLETE rewrite) is to go to eloquence...that's the thinking so
far.
> > > Trying to get enough gear set up to evaluate it asap.
> >
> >I'm learning about MPE.  Could someone explain what this means and why
> >going to eloquence is related?  Isn't Block Mode a function of a
> >terminal and Eloquence a version of IMAGE on UNIX?
> >
> >Is UX short for UNIX?
>
> You are right, block mode is a host-terminal data transfer, while
Eloquence
> is an IMAGE clone on UNIX. The one has nothing to do with the other.
>
> HP-UX is HP's version of UNIX.
>
> --
> Tom Brandt
> Northtech Systems, Inc.
> 130 S. 1st Street, Suite 220
> Ann Arbor, MI 48104-1343
> http://www.northtech.com/
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *