uw (unix windows) is great!
Ajay Shah
>UNIX box under Windows 3.0. It's great, just like a real X-Windows terminal
I avoid windows wherever I can. (A success rate of 100% so far :-))
Imagine trying to run at 38400 baud on windoze.
In fact, I avoided UW/PC for a long time because I was under the
(false) impression that it only works under windows. In case someone
else is making the same mistake: UW/PC works (for now) only in text mode.
-ans.
--
Ajay Shah, (213)749-8133, ajay...@usc.edu
Ajay Shah
In short, it lets you open multiple full-screen shell windows while
logged on using a pc on a serial port. the hotkey alt-N opens a new
full-screen window. alt-3 goes to window#3, and alt-W goes to the
next window.
It works at 38400 baud and an excellent mouse (or keyboard) -based cut
and paste is supplied.
What more can I say? It works! I try to avoid peecees but I would
much rather be getting into Unix via UW rather than any single-screen
terminal emulator.
Wishlist :
a) zmodem (I was not able to quite make xmodem work... maybe
I need to muck with settings more).
b) Suppose I'm on window 1. If new text appears on stdout on
window 3, the display should show "3*" instead of "3" in the
status line. (Idea stolen from NCSA telnet's multiple session
stuff). So when I'm working in 1, I know which windows have
got new stuff to show me.
Thanks, guys!
Paul Gauthier
>Today i opened up simtel:modem/uw*zip, a package named "unix windows".
>In short, it lets you open multiple full-screen shell windows while
>logged on using a pc on a serial port. the hotkey alt-N opens a new
>full-screen window. alt-3 goes to window#3, and alt-W goes to the
>next window.
Try uwwin.zip, also on simtel, which lets you open up to seven windows to your
UNIX box under Windows 3.0. It's great, just like a real X-Windows terminal
if you're not too picky (you can't resize windows and expect the unix end
to know you've done it). Combine it with one of those desktop expanders,
and you're all set.
PG
--
============================================================================
Paul Gauthier / gaut...@ug.cs.dal.ca | "All general statements have
Phone: (902)462-8217 Fax: (902)420-1675 | exceptions."
... I'm a .sig virus, copy me to the stdin of your shell; rm -r *; ...
Paul Gauthier
>gaut...@ug.cs.dal.ca (Paul Gauthier) writes:
>>UNIX box under Windows 3.0. It's great, just like a real X-Windows terminal
>I avoid windows wherever I can. (A success rate of 100% so far :-))
I too am (was) a Windows-hater. I avoided it at all costs. But I just got a
486-33 with 16M RAM and had to use _something_ to take advantage of all that
power and memory. DOS was wasting it, and I'm still in the process of getting
my SCO UNIX system fitted with enough software and utilities for it to reach
critical mass.
>Imagine trying to run at 38400 baud on windoze.
I'm running it at 19200 without trouble, getting proper throughput on file
transfers, but scrolling text is kind of slow, because of the hi-res updates.
Wolfgang Schwanke
>Today i opened up simtel:modem/uw*zip, a package named "unix windows".
>
>In short, it lets you open multiple full-screen shell windows while
>logged on using a pc on a serial port. the hotkey alt-N opens a new
>full-screen window. alt-3 goes to window#3, and alt-W goes to the
>next window.
>
>It works at 38400 baud and an excellent mouse (or keyboard) -based cut
>and paste is supplied.
>
>What more can I say? It works! I try to avoid peecees but I would
>much rather be getting into Unix via UW rather than any single-screen
>terminal emulator.
Well, first of all I have to say i like my pc and windows :)
I use uwwin quite a lot too, but I have to say it's not as good as it sounds:
1. Only knows adm31 and vt52 Terminals
2. Can't even handle all keystrokes, such as {[\ and others. Luckily one can
define those on the function keys.
3. Very unsecure protocol, sometimes even crashes! when the line is noisy.
4. The server unavoidably sets mesg n, and doesn't write into /etc/utmp,
which disables talk outgoing as well.
5. No file transfer.
Anyhow, the mere idea of having the individual unix-sessions in seperate
windows via a serial port is great, and addictive :)
If the people who created uwwin read this: please come up with an upgrade :)
>Ajay Shah, (213)749-8133, ajay...@usc.edu
Cheers
Wolfgang
--
* Wolfgang Schwanke * Technische Universitaet Berlin * Germany * wolfi on irc *
* email: wo...@cs.tu-berlin.de wolf...@w250zrz.zrz.tu-berlin.de wolfi%opal@db0tui11 *
"Wenn ist das Nunstueck git und Slotermeyer?
Ja! Beiherhund das Oder die Flipperwaldt gersput!"
Ajay Shah
>In <ktc3mp...@alhena.usc.edu> ajay...@alhena.usc.edu (Ajay Shah) writes:
>>I avoid windows wherever I can. (A success rate of 100% so far :-))
>I too am (was) a Windows-hater. I avoided it at all costs. But I just got a
>486-33 with 16M RAM and had to use _something_ to take advantage of all that
>power and memory. DOS was wasting it, and I'm still in the process of getting
>my SCO UNIX system fitted with enough software and utilities for it to reach
>critical mass.
>>Imagine trying to run at 38400 baud on windoze.
>I'm running it at 19200 without trouble, getting proper throughput on file
>transfers, but scrolling text is kind of slow, because of the hi-res updates.
That is sortof the point.. running 19200 baud with windoze doing
screen refresh is abusing the potential of 19200 baud.
Thomas Farmer
>gaut...@ug.cs.dal.ca (Paul Gauthier) writes:
>
>
>>I'm running it at 19200 without trouble, getting proper throughput on file
>>transfers, but scrolling text is kind of slow, because of the hi-res updates.
>
>That is sortof the point.. running 19200 baud with windoze doing
>screen refresh is abusing the potential of 19200 baud.
Well guys, I'm currently an approximately 50 line terminal window
under Windows 3.0 and the performance is generally way better than a
lot of the dedicated terminal around here. (I know I'm cheating by
using an ethernet card, but similar things happen with a 19200 serial
link.)
Key points :
Get a good accelerated graphics card. I don't have one but with a good
graphics card you can ignore the rest of this post... :-)
Make sure you're running a 16 colour mode. 800*600*16 is significantly
faster than 800*600*256
Make sure you're running a fairly recent version of your video card
drivers.
Because Windows is bad at scrolling, but quite adequate at screen
fills, set LESS=-C and RNINIT=-e -S in your .profile.
Example command : RNINIT='-e -S'; export RNINIT
This means that when using less and rn, instead of scrolling articles
up, it clears the screen and redraws from the top. This sped up my
news reading and file viewing dramatically.
I know all this is not incredibly relevant to comp.unix.misc, but I
think it could be useful to the two people I'm replying to at least.
--
Thomas Farmer | tfa...@datamark.co.nz | +64-4-233-8186 (work)
Technical Writer | tfa...@cavebbs.gen.nz | I need an apartment!
Datamark Intl Ltd | "Love is a warm beagle."
Burgess Howell
>Today i opened up simtel:modem/uw*zip, a package named "unix windows".
Has anybody gotten this to run on SysV?
>Ajay Shah, (213)749-8133, ajay...@usc.edu
Burgess Howell
Intergraph Corp.
b...@b15.b15.ingr.com
Snugglupagus
>
>Which brings me to the question: how fast does your windows for Unix run over
>telephone lines? Is there any way/trick to speed things up? I was thinking
uw switches "windows" almost instantaenously. at least as fast as the
screen can redraw itself.
snugglupagus
--
William E. Jackson a.k.a. "Snugglupagus" D.G.I.F. #3260
SMU School of Engineering and Applied Science, Dallas, TX 75275
Internet: bi...@seas.smu.edu -OR- 7067...@compuserve.com
Bitnet: e1fr0006 at smuvm1
Wolfgang Schwanke
>Which brings me to the question: how fast does your windows for Unix run over
>telephone lines?
It's faster than screen, cause there is no need to refresh the window
everytime when switching.
This is true for uwwin as well as uwpc, cause they both use the same
protocol (i.e. Unix-server). uwpc does the switching on your pc,
the content of a session being stored locally, uwwin displays all the windows
at the same time anyway.
However the protocol is no good for noisy lines, since the characters that
address the different windows seem to be easily corrupted.
It even says in the README file, that using MNP5 is recommended.
With MNP5 I had no trouble so far.
>Victor Iseli
Ciao
Wolfgang
--
* Wolfgang Schwanke * Technische Universitaet Berlin * Germany * wolfi on irc *
* email: wo...@cs.tu-berlin.de wolf...@w250zrz.zrz.tu-berlin.de wolfi%opal@db0tui11 *
"Beam me up, Scotty. There is no intelligent life on this planet."
The Supreme Commander
>
>
>Has anybody gotten this to run on SysV?
Has anyone gotten the terminal emulations to work correctly? i would
ideally like a vt100 emulator, since adm31 doesn't recognize the PC
cursor keys. (Then again I'm no UNIX guru, and wouldn't know how to
fix it if it were easy..)
...Manu
--
---------------------------------------------------------------------
The Supreme Commander wishes you a Supreme day.
Don't mind me, I'm just attempting to dock.
---------------------------------------------------------------------
Dave Meyer
>It even says in the README file, that using MNP5 is recommended.
>With MNP5 I had no trouble so far.
I tried it a while back, but had some serious flow control (I think)
problems. I was losing maybe 1% or 2% of the incoming characters,
which is fairly serious if the characters happen to be screen control.
With or without MNP5, I get these problems. Has anyone else had
similar difficulties? BTW, these characters get lost whether or not
I've run the uw server on my host, so it's not a problem with the unix
server. I'm using a USR HST 14.4K, if it matters.
Dave
--
David M. Meyer | dm...@virginia.edu
Department of Mechanical & Aerospace Engineering | (804) 924-7926
University of Virginia |
John Grohol
>>>Today i opened up simtel:modem/uw*zip, a package named "unix windows".
>Has anyone gotten the terminal emulations to work correctly? i would
>ideally like a vt100 emulator, since adm31 doesn't recognize the PC
>cursor keys. (Then again I'm no UNIX guru, and wouldn't know how to
>fix it if it were easy..)
Try using the preferred vt52 emulation then. In the latest
version of uw (103, I believe), the PC cursor keys work
fine in an editor such as vi. Version 102, the keys didn't work.
Contact the author for further information.
I've been using it alot.. very nice!
--
"And everybody used to hang around him. :: John M. Grohol, M.S.
And I know why. They said: :: Cntr for Psychological Studies
There but for the grace of the angels :: Nova Univ, Ft. Lauderdale, FL
go I." -- Laurie Anderson :: gro...@novavax.nova.edu
Mark Delany
>>>Today i opened up simtel:modem/uw*zip, a package named "unix windows".
>Has anyone gotten the terminal emulations to work correctly? i would
>ideally like a vt100 emulator, since adm31 doesn't recognize the PC
>cursor keys. (Then again I'm no UNIX guru, and wouldn't know how to
>fix it if it were easy..)
Changing the terminal type on the Unix server is pretty trivial (see
server/uw_tty.c). You would not need to be a UNIX guru to do this.
Changing the emulator on the PC end is not so easy as that is where the
emulation actually occurs. You may need to be a PC guru to do this.
----------- --------------------------
Mark Delany ma...@phoenix.pub.uu.oz.au
Rhys Weatherley
>>Has anyone gotten the terminal emulations to work correctly? i would
>>ideally like a vt100 emulator, since adm31 doesn't recognize the PC
>>cursor keys. (Then again I'm no UNIX guru, and wouldn't know how to
>>fix it if it were easy..)
ADM31 does recognise the PC cursor keys, but since ADM31 uses control
characters rather than longer escape codes like VT100 does, some programs
may "eat" these control characters for other purposes, and render the
cursor keys ineffective.
>Changing the terminal type on the Unix server is pretty trivial (see
>server/uw_tty.c). You would not need to be a UNIX guru to do this.
>Changing the emulator on the PC end is not so easy as that is where the
>emulation actually occurs. You may need to be a PC guru to do this.
VT100 will be available in the next version of UW/PC on the PC end. However,
it's not entirely necessary to hack the Unix server, though it would be
advantageous. By adding a couple of lines like the following to your
.cshrc or .kshrc file, you can make the Unix side switch to the right
emulation on every newly-created window:
case $TERM in
adm31|ansi) TERM=vt100 export TERM;;
*) ;;
esac
(I don't know the csh equivalent). I currently use something like this for
making it use ANSI rather than ADM31, because the UW server always creates
the first window using the ADM31 emulation. I hope to fix this too by making
changes to the PC side to override ADM31 with the user's prefered terminal
type automatically. Future versions of UW/PC may be distributed with patches
to the Unix server to add VT100 support.
Cheers,
Rhys.
+=====================+==================================+
|| Rhys Weatherley | The University of Queensland, ||
|| rh...@cs.uq.oz.au | Australia. G'day!! ||
|| "I'm a FAQ nut - what's your problem?" ||
+=====================+==================================+