Tracy writes:

> My experience is once you have a Reflection session loaded, any second
>  window just pops right up, even when using different config files.
>
>  Say opposed to Minisoft/WS92 or QCTerm, both will happily pause at their
>  welcome displays before running the second instance.

In the category of more than you might want to know, there are two ways of
generating a second "instance" of a program in Windows. The first is generally
marked Cntl+N, "Open a New Window." The second is to simply run the program
again.

In the first, the program is already fully loaded and all that is being done
is space is being assigned to the new instance's variables. Otherwise, the
loaded executable is being shared. In the second, the program becomes a fully
independent program.

The advantage of the first method is that the second instance comes up quite
quickly. The disadvantage is that if anything should happen to cause the
primary (and sometimes any of its children) to fail, they all fail simultaneously.

You have exactly the same choice when running MSIE, and it's for this reason
that I learned some time ago never to run additional browsers as child windows
of a first launch. If one website screws up one instance, you will likely
lose all of your instances simultaneously.

I considered this enough of a disadvantage that we opted to support only the
independent instance method, where every instance has to be launched
independently, but which would not fail if some other instance of QCTerm failed.

Wirt Atmar

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