readme.now

增强的pterm01b.zip 终端仿真程序(63KB)<END>

                                  P T E R M

                         Paragon Terminal Application

                                for Windows NT

                                 Version 0.1b

                                18, June 1993




   What's Going on Here?
   =====================

      This is a beta of Paragon Terminal Application for Windows NT. What's
      so great about PTERM? Not much yet, but here is a list of features
      available so far:

         o  Fully threaded (6 so far), native Win32 application

         o  Auto Zmodem download/upload

         o  Fast ANSI (including color!) terminal emulation

         o  Console based for speed

      The other valuable feature of PTERM is that as far as I know it is
      the only Zmodem capable native, multi-threaded Win32 terminal
      application available. It won't be for long, but for now...

      Some glaring omissions:

         o  No Dialer!?!?!

         o  No user interface driven configuration

         o  No annoying "register me now, or die" messages and
            [purposefully] broken features.

         o  Many other things which you will likely go insane without (but
            hang in there, it is my intention to evolve PTERM).


   Why Would You Do Such a Thing?
   ==============================

      Some months back, I was asked to beta test a C++ based,
      multi-platform communications library from a company called Lookout
      Mountain Software (William Herrera, owner/author, BBS 719-545-8572).

      The best method I could think of for testing this package was to use
      it as the core of a terminal application -- and PTERM was born.

      William has been extremely sensitive to the problems I found and
      enhancements I suggested, and should be commended for authoring such
      a stable and comprehensive communications library, which is available
      for DOS, Windows, OS/2 and Windows NT. All of the file transfer
      protocol code (Zmodem/Ymodem/Xmodem) is Williams, and he has done an
      excellent job implementing them (sealink and telink are also included
      in the communications library, but not in PTERM -- Xmodem and Ymodem
      will be available in the next release of PTERM).


   I Didn't Do It, I Swear!
   ========================

      Every precaution has been taken to ensure the safe operation of PTERM
      in your Windows NT system. But, come'on, not only is this copy of
      PTERM in beta, but so is the current (March '93) build of NT, so
      obviously I cannot be held responsible for any damage done to your
      system (or psyche) by PTERM or any interaction involving PTERM. So
      all I can say is "I didn't do it!", so don't blame me!


   What Do I Need To Use Pterm?
   ============================

      You need an Intel based (Intel Inside sticker optional) PC running
      Windows NT (March '93 build or later), with at least one serial port
      and a modem attached to that port.

      If someone would like to send me a MIPS R4400 or DEC Alpha AXP, I
      will be glad to get PTERM up on those platforms as well <grin>.


   Alright, What Do You Want For This?
   ===================================

      The list of things I want would be much too large to include in this
      document, so you will have to settle for what I need.

      What I need, from you, is the following:

         o  Bug reports (there should be plenty)
         o  Suggestions (again, no shortage expected here either)

      So, please, please inundate me with this information, I promise I
      will consider anything submitted (but nothing not submitted).

      I can be reached via internet mail at:

         [e-mail]

      FIDOnet people, try netmail to UUCP at 1:1/31, first line of the
      message body:

         To: [e-mail]

      I plan on finding a reliable FIDOnet system here in town, and when I
      do I will post my FIDOnet address for netmail.

      For slowest response, choose snail-mail:

         Ron Cox
         Paragon Consulting Group
         4212 West Cactus STE 1110-229
         Phoenix, AZ  85029
         ATTN: PTERM


      If you are a Windows NT developer, and would like to contribute code
      to PTERM let me know! Currently I have no plans to charge real money
      for PTERM, so you will get the same thing I do as far as that goes,
      nothing but recognition (we'll be lucky to get that!). Any code you
      contribute will become public domain, and may be distributed in the
      future (in source or object form) or used in other projects without
      restriction.


   Free? Something Must Be Broken!
   ================================

      Actually, yes. I am releasing this with a several known bugs, and I'm
      sure many more unknown bugs. I am of the belief that the bugs I know
      about will not significantly affect the operation. Some require bug
      fixes in NT or the SDK, others just require me to figure out what's
      going on. Here is a list of the bugs I know about:

         o  The first time (during a given run) an upload starts and the
            file selection dialog pops up, it does so behind the console
            window PTERM is running in. After the first time, and during the
            same run, the file selection dialog will pop up above the PTERM
            window as expected. I am working on getting this fixed.

         o  After each file of a Zmodem upload, there is a 15-20 second
            period where a sync with the host is attempted. During this
            period, there are usually several (3-5) timeout messages. The
            sync finally takes place, and the host usually accepts the
            transfer. This is irritating, and throws off the CPS rating,
            but seems to cause no other problems. I am working on getting
            this problem solved more than any other.

         o  Occasionally, when exiting PTERM, just before the console
            window goes away, you may see a brief message mentioning some
            runtime error. I have no idea what is causing this, but am
            investigating it. I tend to believe it is a problem in the
            current build of the NT runtime libraries. It does not seem to
            have any adverse side effects.

         o  As mentioned, PTERM supports ANSI terminal emulation.
            However, I was unable to find any definitive document on
            ANSI, so I am sure some sequences are not supported, and
            its possible ones I do support operate incorrectly. I have
            little or no problems with the BBS's I call (including a UNIX
            shell account with ansi emulation) around town. I believe that
            ANSI is a superset of VT-100/102, so PTERM may work with
            these emulations as well. If anyone has a detailed document on
            ANSI/VT-100/VT-102, please, please send it to me. It needs
            to be real detailed and complete (I already have various bits
            and pieces). Also, the emulation in PTERM is tuned for 9600 baud
            and higher, so you guys with the old 1200 and 2400 baud modems
            will notice that PTERM spits out blocks of characters, giving
            the output a somewhat jerky appearance. This can be minimized by
            having PTERM use the actual baud rate you expect to connect at
            (see configuration below).

         o  When PTERM is run in a console window without a scroll bar,
            characters in the last column do not always scroll. I believe
            this to be a bug in NT, but am investigating. In any case, the
            solution is simple, use the system menu/buffer size to change
            the lines in the buffer to be larger than the size of the
            window PTERM is running in, which adds a scrollbar to the
            window. Actually, this is convenient as it gives you a scroll
            back buffer. I typically run PTERM in a window whose buffer is
            1024 lines (although the window size is 80x25), giving me that
            much scroll back.

      Well, them's the major ones I have found so far. Please report others
      to me as necessary.


      Some 'features' to watch out for:

         o  Once PTERM quits, it closes the serial port, and if the modem on
            this serial port is currently connected to somewhere, that
            connection will be lost (since closing the serial port drops
            DTR). You may be able to prevent this by setting your modem to
            always hold DTR high, but this will have the side effect of
            preventing ALT-H from hanging up the connection.

         o  If there exists, in your download path, a file with the same
            name as one you are attempting to download, the transfer will be
            aborted. I apologize for this, and I will have a reasonable
            automatic rename mechanism available in the next release.

         o  PTERM has a lot of trouble with the ANSI codes coming from
            Maximus BBS software. I am working on getting this straight. It
            seems Maximus uses some strange (although probably completely
            legal) derivation of the cursor position command. I will get
            this fixed as soon as I can get a detailed document on ANSI
            emulation (and even better document on what the hell Maximus
            sends out for various sequences).


   I'm Getting Sleeeepy...