petersja@debussy.cs.colostate.edu (james peterson) (04/23/91)
I have the thankless job of "supporting" a 386 ATT PC running MS Windows 3.0 and PCNFS. We have had some difficulties getting a terminal session (NCSA telnet) to run in a window over PCNFS without frequently causing unrecoverable errors (this was not surprising to anyone). The purported "solution" was to upgrade to PCNFS 3.5 which worked "much better with Windows," or so I was told. And while I was at it, Sun resold Reflections telnet software as "Advanced Telnet" which was to allow a Windows user to create up to three terminal sessions each in its own window -- the answer to our prayers. So we ordered the update of PCNFS to 3.5 plus Advanced Telnet. The Advanced Telnet came first so I installed it under the old version of PCNFS (3.0.1); aside from bad documentation (what else is new), it installed and worked basically as advertised ( though it set aside just enough memory so that Word would no longer run). Things went along fine for a couple of weeks until the update of PCNFS arrived. After installing the new PCNFS, the Advanced Telnet began to behave very flakey. About half the time, when opening a terminal session in a window the window would close up shortly after logging on to the remote host, and the PC screen would go completely blank. Rebooting the system is the only way to escape. The session on the host was uninterrupted by this (causing its own problems). This situation is much worse than the one we purchased the software to fix. This is frustrating. Can anyone suggest what is going on, and why updating software might make things *worse*? Thanks in advance. -- james lee peterson petersja@CS.ColoState.edu dept. of computer science colorado state university "Some ignorance is invincible." ft. collins, colorado (voice:303/491-7137; fax:303/491-2293)