hoehle@cs.uni-sb.de ("Joerg-Cyril Hoehle TAG-Gruppe") (06/10/90)
In c.s.a.t, bdo8650@cec2.wustl.edu (Bryan Dennis O'Connor) writes: > I just set up a remote DUMB terminal through the AUX: device >and I am looking for ideas for using it most effectively. Having a remote terminal on the serial port often helps when a program freezes the screen and/or the mouse, or when a dumb program uses the whole display and blocks Intuition on my very multitasking machine. Although Xoper opens a window, there are other tools (dis,...) that work in the CLI window, and they allow you to debug your application. However, without mouse and screens and editor, you will soon want to reboot. When a program GURUS, you can hit the DEL key to access a debugger that is in ROM (look in the Exec manual for further information). I'm also looking for an editor that works from a terminal, Without one, the terminal is of small use, except for testing, as above. Compiling from the terminal is fun! You can control your program from there if you need the whole screen, and don't want to switch between yours and the WB one. I've not been able to test DNET yet, due to the lack of another adapted computer. Curiously Cshell 4.01a GURUs when started through the terminal. Using a terminal also shows you how system-friendly some software is (ex Cshell?) To feed the games vs. multitasking discussion: Connect a terminal to your serial port and you will see that many (-), err, the few I have) of the games that may be launched from WB and seem to turn down multitasking, multitask well. (Even a friend of mine wanted his game to open a screen without using intuition, guess what happened when I used Amiga-N). Yet another hint for multitasking still alive: listen to your clicking drives. The programs have only the strange habbit of requiring the entire screen.resource (tm) and throwing out the Intuition event handler. ----------------------------------------------------------- Joerg Hoehle hoehle@hpki.cs.uni-sb.de student @ Universitaet des Saarlandes