There is no way to have a single process connected to 2 cli windows simulaneously under Win32. You could create a gui style window with either native calls or one of the gui toolkits.

It is possible to have multiple screen buffers associated with a single cli window. You can do this with Win32::Console. You then only need arrange for some key sequence to be recognised and trigger switching between the 2 or more screen buffers.

You could take this a stage further and package it up using a tied filehandle to represent the "alternate console" so that you could use Perl's standard IO to write to the multiple consoles.

If you don't like the idea of having to use a keysequence to allow you to view the various screens, you could take that a step further. Size the window to 160 x 48 and draw the different 'screens' in different portions of the one real screen. In fact, I frequently use an 8 point font in my console sessions which gives me a 250 x 120 screen, which could hold 15 80x24 sessions concurrently.

Presuming you mean "X11" when you ask about *NIX, the answer is probably "yes but not as simply". See man xterm for information on the -S option which allows you to open a pty and have xterm grab the other end. Any output you write to the pty will be displayed in the xterm (and theoretically one could also read input from it).

Update: Oh yeah: IO::Pty may be of assistance getting a pty for this.

Update: And while not exact code, see opening and writing to another xterm for the steps to take.

echo "Hello!" >/dev/tty2
[download]

open(TERMINAL,'>/dev/tty2');
. . .
[download]

The easiest way I may think of is to redirect the output of your script to some file, and monitor its content with tail:

term1% myscript.pl > /tmp/logfile

term2% tail -f /tmp/logfile
[download]

Even better, you can both have the output into the first windows and in the log file, with tee:

term1% myscript.pl | tee /tmp/logfile
[download]

IIRC there is a "CON:" device existing in windows, but I don't know what it is and what it's used for.

Actually CON: is the "console device" for MS-DOS and Windows. Maybe some windows guru may learn us more about what tricks can be achieved with it....
See some fun tricks using CON here :user input

#!/usr/bin/perl

system 'mknod thepipe p' unless -p 'thepipe';

if ( fork ) {
        system q(xterm -e 'exec < thepipe; cat');
} else {
        open F, '>thepipe';
        select F;
        $|++;
        for (1..30) {
                print "and a $_ woot!\n";
                sleep 1;
        }
}
unlink 'thepipe';
[download]

depending upon your OS (Linux, Solaris, IRIX ...), you may use mkfifo instead of mknod ... p.
Keep in mind that fifos may lock, or exit quite easily (the reader can't read anymore after the writer stops). however it'll save some disk space :)
BTW, would it be possible to create an anonymous pipe (on the IO::File model perhaps?)