Re: ProTerm 3.1 Upgrade

[wsquires@lonestar.utsa.edu (William H. Squires)]

In article <mtm4.49.00129652@rsvl.unisys.com> mtm4@rsvl.unisys.com (Mike McCormick) writes:
>Sorry, previous message with this Subject was a premature e-transmission!
>
>As I started to say, I am a little miffed with the way my proterm upgrade
>(from 2.1 to 3.1) went:
>
>1. Manually copying a dozen or so files to the hard drive.  There should
>   be an INSTALLER on the product disk.
>
>2. Error prone install.  I accidentally forgot to create the required
>   empty (!) directory PT3.DIAL during the hand installation.  This leads
>   to mysterious error messages when you try to execute PT3.  The only
>   way to make the diagnostic message go away is a hard reset!
>
>3. Hand rolled windows.  Glad to finally have mouse support, but why not
>   have a ProTerm GS that uses real windows.  The simulated windows are
>   hard to read and slower and monochrome.
>
>4. Unless I missed it, there is no longer a copy buffer in 3.1.  Can this
>   really be true?  I used the copy buffer quite alot as a place to create
>   a message offline in the editor, then upload it to a BBS.
>
>5. Conversion of dialing list and macros from Proterm 2.x.  First, it is
>   hard to figure out how to even get 3.1 to run the PT3.CONVERT macro since
>   it does not appear in the macro list.  Once I figured it out, it worked
>   fairly well.  But I should not have to do a conversion!  PT3 should have
>   an Installer script that automatically detects the presence of PT2 files
>   and converts them for me without me ever knowing about it!
>
>6. Loss of modem init string.  PT3 does not seem to remember my init string,
>   nor did PT3.CONVERT go find it for me in the PT2 files.  Do I really have
>   to try and remember what it was, or what file it lives in, and manually
>   reinsert it in PT3?  I don't remember what it was anymore!
>
>7. Forced reinstallation of modem, printer, and slots.  It is silly at best
>   to have to go through all those dialog boxes again on upgrade.  PT3
>   should use the configuration files that are in place from PT2.
>

  Sorry, but the only Installer is the one that comes with GS/OS (various
versions). Therefore, ProTerm would need to be a GS/OS aware program (i.e.
16-bit), in order to have installer scripts for it.
  Of course this would solve the problem of mono windows, but then how would
I (and others) run the program on //e's?
  I think there should already be a PT3.DIAL folder before you do the install
by hand. Or maybe that was a PT3.DIAL file instead. Sorry, haven't used my
modem in a while... I'm using a VT320 term now... <Yuk!> I have ProTerm 3.0
It has a PT3.DIAL file of some kind. I'll take a look...

                                        wsquires@lonestar.utsa.edu
                                        William H Squires Jr.