home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!cel.cummins.com!philip
- From: philip@cel.cummins.com (Philip D. Pokorny)
- Newsgroups: comp.sys.apollo
- Subject: Re: strange program behavior
- Message-ID: <9209151905.AA04572@cel.cummins.com>
- Date: 15 Sep 92 19:05:15 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Organization: The Internet
- Lines: 18
-
- Thanks for all those that responded with suggestions on how a program might
- write to the pad after a vt100 emulator was started on-top of it.
-
- The vendor selling the software found the problem. It seems that they were
- dup() ing the stdout stream and then latter calling tgetent (a termio
- initialization routine) It appears that tgetent tests to see whether stdout
- is a DM PAD and if so, starts a vt100 window on the pad and then REPLACES
- stdout with a connection to the vt100 pty. Because the product dup'd stdout
- and was writing to the old stream, the output was going to the pad and not
- the vt100 emulator. Moving the tgetent call before the dup solves the problem
- as does not dup'ing stdout at all.
-
- Thanks again for the input.
-
- Sincerely,
- Philip D. Pokorny
- philip@cel.cummins.com
- :)
-