Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Frank da Cr » Fri, 13 Jun 1997 04:00:00



Kermit 95 1.1.12 is now available as a patch to registered users of previous
Kermit 95 releases for Windows 95, Windows NT, and OS/2.  This is a major new
release of Kermit 95, but no, it is not the long-awaited full-GUI release, but
it is a big step on the way.  It replaces version 1.1.11 of 8 February 1997.

The new features of version 1.1.12 include:

 . Microsoft Telephony (TAPI) support
 . Support for 10-digit and other special dialing methods
 . Support for 132 columns and other screen sizes in Windows 95
 . File transfer pipes and filters
 . Web browser interface ("URL hot spots")
 . Greek character-set translation in file transfer and terminal emulation
 . Lots more

The full announcement appears on comp.protocols.kermit.announce.

HOW TO GET IT

Kermit 95 1.1.12 is available as a patch to version 1.1.11 or earlier.
Current registered users of Kermit 95 can download the 1.1.11 upgrade patch
from our BBS or from our Web site:

  http://www.columbia.edu/kermit/k95patch.html

or with ftp:

  ftp://kermit.columbia.edu/kermit/k95/patches/

All the new features are documented in the updated UPDATES.TXT file that
comes in the patch, and in the updated BUGS.TXT file.

Academic site or bulk licensees that have customized their DIALINF.DAT
files will need to send them in so we can convert them to the new format,
since the regular patch will fail (since it only knows what the original
DIALINF.DAT contained, not your customized version).  Contact us by email
about this at:


This is the final major release of Kermit 95 before the conversion to full
GUI is complete later this year.  There might be minor corrective patches
between now and then, but nothing more.  If you have any difficulty with
the patches or the new version, please report them by email to the address
above.

Frank da Cruz & Christine M. Gianone
Managers, The Kermit Project
Columbia University
New York City

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by David Sewe » Fri, 13 Jun 1997 04:00:00




Quote:>Kermit 95 1.1.12 is now available as a patch to registered users of previous
>Kermit 95 releases for Windows 95, Windows NT, and OS/2.  This is a major new
>release of Kermit 95, but no, it is not the long-awaited full-GUI release, but
>it is a big step on the way.  It replaces version 1.1.11 of 8 February 1997.

The OS/2 patch wouldn't replace my .EXE files, so after running it
I'm still getting version 1.1.11.  I'll append the PATCH.ERR file that
was generated.  Any suggestions on how to proceed would be appreciated.
(The program is a registered copy.)

Thanks,
David Sewell, U of Arizona Geosciences
===== ======= = == ======= ===========
[file PATCH.ERR]

ENTRY: cko32i12.dll
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: cko32i20.dll
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: cko32rt.dll
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: k2clip.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: k2dc.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: k2reg.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: p2.dll
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: rlogin.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: setup.exe
warning wpt0015: Old File does not exist

ENTRY: telnet.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: telnetpm.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: k2.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

ENTRY: k2dial.exe
warning wpt0036: Old File not found. However, a file of the same name was
               found. No update done since file contents do not match.

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by d.. » Mon, 16 Jun 1997 04:00:00




: >Kermit 95 1.1.12 is now available as a patch to registered users of
: >Kermit 95 releases for Windows 95, Windows NT, and OS/2.  This is a
: >release of Kermit 95, but no, it is not the long-awaited full-GUI
: >it is a big step on the way.  It replaces version 1.1.11 of 8

: The OS/2 patch wouldn't replace my .EXE files, so after running it
: I'm still getting version 1.1.11.  I'll append the PATCH.ERR file that
: was generated.  Any suggestions on how to proceed would be appreciated.
: (The program is a registered copy.)

Mine didn't install either.
The patch log tells me that several old files do not match, including
K95.exe.
It would be nice if the newly released version were available as a release,
rather than a sequence of patches with unknown dependencies.
When the GUI comes out, please make it a proper release.
--
---

                - Pope Valley & Napa CA.

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Frank da Cr » Tue, 17 Jun 1997 04:00:00




: : >Kermit 95 1.1.12 is now available as a patch to registered users of
: : >Kermit 95 releases for Windows 95, Windows NT, and OS/2.  This is a
: : >release of Kermit 95, but no, it is not the long-awaited full-GUI
: : >it is a big step on the way.  It replaces version 1.1.11 of 8
:

: : The OS/2 patch wouldn't replace my .EXE files, so after running it
: : I'm still getting version 1.1.11.  I'll append the PATCH.ERR file that
: : was generated.  Any suggestions on how to proceed would be appreciated.
: : (The program is a registered copy.)
:
: Mine didn't install either.
: The patch log tells me that several old files do not match, including
: K95.exe.
: It would be nice if the newly released version were available as a release,
: rather than a sequence of patches with unknown dependencies.
: When the GUI comes out, please make it a proper release.
:
If anybody has troubles with the patch process, we are here to help -- like
it said in the announcement.  The fastest way to get help is to send email

- Frank

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by d.. » Tue, 17 Jun 1997 04:00:00



: If anybody has troubles with the patch process, we are here to help -- like
: it said in the announcement.  The fastest way to get help is to send email

Hey, no need to send email ;-)

My posting, on a Sunday, was answered on Sunday via email from Jeff.

While we bandied about the patch mechanism, I noticed that my previous
patch to 1.11 had apparently failed, leaving the K95.exe at 1.1.8

I applied the 1.1.8-1.1.12 patch successfully.

So, when I CTRL-click on a URL name in a K-95 window, I spawn a copy of my
Web Browser, pointed to that page.
If I click a second URL, it spawns a second copy of a browser.  Would
it be optional to invoke the new page on the existing browser?
--
---

                - Pope Valley & Napa CA.

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Frank da Cr » Tue, 17 Jun 1997 04:00:00


: ...
: So, when I CTRL-click on a URL name in a K-95 window, I spawn a copy of
: my Web Browser, pointed to that page.
: If I click a second URL, it spawns a second copy of a browser.  Would
: it be optional to invoke the new page on the existing browser?
:
Not currently -- that's how we wanted to do it in the first place, but that
would require knowing the API for every release of every browser on every
platform, so for now we just start a new browser.  It's not as dumb an
approach as it might seem, however, since multiple browsers share the same
memory for pure code in Windows 95, Windows NT, and OS/2.  But yes, we do
plan to revisit this question subsequent releases.

- Frank

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Thomas A. Horsl » Tue, 17 Jun 1997 04:00:00


Quote:>Not currently -- that's how we wanted to do it in the first place, but that
>would require knowing the API for every release of every browser on every
>platform, so for now we just start a new browser.  It's not as dumb an
>approach as it might seem, however, since multiple browsers share the same
>memory for pure code in Windows 95, Windows NT, and OS/2.  But yes, we do
>plan to revisit this question subsequent releases.

Not true - a browser independent API is already defined by Microsoft (but
admittedly doesn't work on pre 4.0 versions of NT). For example, this little
program will invoke a browser if it has to or just tell the existing browser
to jump to the given URL, and it don't know 'nuthin about any browser:

#include <stdio.h>
#include <windows.h>
#include <shellapi.h>
int __cdecl
main(int argc, char **argv) {
   if (argc == 2) {
      ShellExecute(0, 0, argv[1], 0, 0, SW_NORMAL);
   } else {
      fputs("Please call with a single argument (a URL)\n", stderr);
      exit(2);
   }
   return 0;

Quote:}

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Kyler Lai » Tue, 17 Jun 1997 04:00:00



Quote:>: If I click a second URL, it spawns a second copy of a browser.  Would
>: it be optional to invoke the new page on the existing browser?
>:
>Not currently -- that's how we wanted to do it in the first place, but that
>would require knowing the API for every release of every browser on every
>platform,

...or simply getting users to write their own interfaces.
All you need to do is write a simple program which either
starts up a new browser with the given URL or directs the
current browser to the given URL.

Then just call that program instead of the browser.  I
did this for a hack of NN which I could trigger from
XMosaic.

--kyler

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Frank da Cr » Wed, 18 Jun 1997 04:00:00




: >: If I click a second URL, it spawns a second copy of a
: >: browser.  Would it be optional to invoke the new page
: >: on the existing browser?
: >:
: >Not currently -- that's how we wanted to do it in the
: >first place, but that would require knowing the API for
: >every release of every browser on every platform,
:
: ...or simply getting users to write their own interfaces.
: All you need to do is write a simple program which either
: starts up a new browser with the given URL or directs the
: current browser to the given URL.
:
: Then just call that program instead of the browser.  I
: did this for a hack of NN which I could trigger from
: XMosaic.
:
A "user exit"?  That would be good if all of our users were
programmers and had programming tools at their disposal.
But it begs the larger question of "Kermit APIs" in general.

Like I said, we'll revisit the browser issue in future
releases.  Yesterday, Tom Horsley suggested a "universal
API" for invoking a browser, but it would take a lot of
testing and verification to see how universal it really
was: Windows 95 original, "B", SR2; Windows NT 3.51 and 4.0
(on Intel, Alpha, and Power PC); OS/2 2.0, 2.1, 3.0, 4.0.
Each of these in combination with every release of every
browser -- nothing is ever that easy.

As for "user exits", DDE, OCX, and so on -- that's another
question that's been on our list for some time.  We can't
do everything at once.

- Frank

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Kyler Lai » Wed, 18 Jun 1997 04:00:00



Quote:>: Then just call that program instead of the browser.  I
>: did this for a hack of NN which I could trigger from
>: XMosaic.
>A "user exit"?  That would be good if all of our users were
>programmers and had programming tools at their disposal.

...or if all users could use some large resource (let's
call it "the Web") to download such tools created by
other users.

Quote:>As for "user exits", DDE, OCX, and so on -- that's another
>question that's been on our list for some time.  We can't
>do everything at once.

Understood.  Someday, when I find a reason to upgrade
from C-Kermit 5A(191), I might poke around in this, too.

--kyler

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Thomas A. Horsl » Wed, 18 Jun 1997 04:00:00


Quote:>Like I said, we'll revisit the browser issue in future
>releases.  Yesterday, Tom Horsley suggested a "universal
>API" for invoking a browser, but it would take a lot of
>testing and verification to see how universal it really
>was: Windows 95 original, "B", SR2; Windows NT 3.51 and 4.0
>(on Intel, Alpha, and Power PC); OS/2 2.0, 2.1, 3.0, 4.0.

The "shell extensions" (which is what the ShellExecute function is part of)
are on all versions of Windows 95 and on NT 4.0 and later. They definitely
didn't exist on NT 3.51. (Wait, you mean you don't trust Microsoft
documentation to match reality? :-).

OS/2 I know nothing about...

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Frank da Cr » Thu, 19 Jun 1997 04:00:00




: >Like I said, we'll revisit the browser issue in future
: >releases.  Yesterday, Tom Horsley suggested a "universal
: >API" for invoking a browser, but it would take a lot of
: >testing and verification to see how universal it really
: >was: Windows 95 original, "B", SR2; Windows NT 3.51 and 4.0
: >(on Intel, Alpha, and Power PC); OS/2 2.0, 2.1, 3.0, 4.0.
:
: The "shell extensions" (which is what the ShellExecute
: function is part of) are on all versions of Windows 95 and
: on NT 4.0 and later. They definitely didn't exist on NT
: 3.51. (Wait, you mean you don't trust Microsoft
: documentation to match reality? :-).
:
No comment.

So fine, it's available in Windows 95 and NT 4.0++.  But that
doesn't say anything about the browsers.  How many browsers
exist for these platforms?  (We know about Netscape and IE,
but there are many others, less well known, no?)  How many
different releases of each browser?  Do they all allow
themselves to be invoked in this way?  If somebody has the
answers to these questions, it might save us a lot of work.

- Frank

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Thomas A. Horsl » Thu, 19 Jun 1997 04:00:00


Quote:>How many different releases of each browser?  Do they all allow themselves
>to be invoked in this way?  If somebody has the answers to these questions,
>it might save us a lot of work.

The way the shell extensions really work "under the hood" should mean that
any browser can be successfully invoked. The ShellExecute function really
winds up looking up information in the registry which describes how to
invoke the browser and if it has a DDE interface so it can talk to an
existing copy. Even if some browser doesn't support the DDE or OLE
interfaces to allow an existing browser to be switched to a new URL
remotely, the registry entries can still describe how to invoke a new copy
with an argument passed in, so in the worst case, it would be able to do
what kermit does today, but in the best case, it would use the existing
browser (but it is hard to imagine anyone shipping a browser today that
doesn't support the fancy interface, at least if they expect anyone to
actually be willing to use it).

The whole "shell extensions" stuff really just boils down to a fancier set
of code that still does just about the same thing the original feature that
"associated" a tool with a file extension did, only now it can recognize
more complicated stuff than a simple file extension (like a leading
"http://" instead of a trailing ".doc", etc.).
--
See <URL:http://home.att.net/~Tom.Horsley> for
information on Government by Performance

 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Thomas A. Horsl » Thu, 19 Jun 1997 04:00:00


Quote:>There is no reason why you couldn't take the sample code you posted a
>few days ago and compile it into a program called ShellEx.Exe and then
>    SET BROWSER ShellEx.Exe
>in your K95CUSTOM.INI file to get exactly the functionality that you
>are looking for.

It might be even niftier if you made the ShellEx.Exe file part of the
distribution so folks who don't have a compiler could set it up that way
(its hardly the sort of major software there could be any copyright problems
with - I originally found it in a posting in one of the microsoft news
groups).
 
 
 

Announcing Kermit 95 1.1.12 for Windows 95, Windows NT, and OS/2

Post by Jeffrey Altm » Fri, 20 Jun 1997 04:00:00




: >How many different releases of each browser?  Do they all allow themselves
: >to be invoked in this way?  If somebody has the answers to these questions,
: >it might save us a lot of work.
:

There is no reason why you couldn't take the sample code you posted a
few days ago and compile it into a program called ShellEx.Exe and then
        SET BROWSER ShellEx.Exe
in your K95CUSTOM.INI file to get exactly the functionality that you
are looking for.

One of the benefits of the way that K95 currently works is that the
user can guarantee which application is going to be started.  For
instance, on my system I keep both Internet Explorer and Netscape.
There are some sights that look better in one than in the other.  With
K95, I can SET BROWSER which ever one I want to use depending upon
what I am doing.  That is not the case if we relied exclusively on the
ShellExecute command.

We appreciate your notifying us of the existance of the command and
of explaining how it works.  However, at least for the short term we
will continue to implement the Hot links the way that they are.
Especially given the easy method available for allowing any user to
call ShellExecute on systems that support it.

    Jeffrey Altman * Sr.Software Designer * Kermit-95 for Win32 and OS/2
                 The Kermit Project * Columbia University
       612 West 115th St #716 * New York, NY * 10025 * (212) 854-1344