Any suggestions?
Joel
Joel Lidov
jb...@cunyvm.cuny.edu
Classical, Middle Eastern & Asian | Classics
Languages and Cultures | The Graduate School,
Queens College, C.U.N.Y. | City University of New York
> string is the same as before. But when I type AT I don't get "OK" back
> from the modem; I tried ATZ to reset it, but that didn't help. I see that
> win95 with PNP treats the hardware differently: it recognizes a modem
> but not a COM2, though I did find a property sheet which admitted that the
> modem was on COM2.
Joel, try Uninstalling all modems in your Device Manager (in System
Properties). Then reboot and let Win95 detect and reinstall the modem
you're using. Sometimes it takes a purge of that sort to force Win95 to
reassess its assignment of resources and recognize hardware correctly.
> If I try running Kermit from the DOS F8 boot at
> start up, it produces very weird results, and can't find the port at all.
>
Is it an internal modem (card)? Try taking it out and reseating it. It
may be a flaky interface with the motherboard that just needs a little
help. What other serial devices are you running? Is there any conflict?
If there is (whether you realize it or not), reinstalling under Win95
may get wrong assignments cleared out. Good luck!
Dorothy
*****
Dorothy Day
School of Library and Information Science
Indiana University
d...@indiana.edu
*****
"He also surfs who only sits and waits."
On Fri, 17 Apr 1998 23:47:11 EDT, Joel Lidov wrote:
> Do any of you have Kermit 3.15 running under Win95? I would like to
> escape from hyperterminal and go back to Kermit. I had been using
> 3.13, but when I started it as a DOS program under w95 it failed
> with an overflow divide error; I downloaded 3.15, and it appears to
> run. But the modem won't respond. The port, address, IRQ are correct.
> The "sho comm" command reports that the modem is ready (DSR and CTS both
> on).
Dorothy's suggestions are well taken, and may be sufficient.
You may have to turn TAPI off, or install the modem as a non-TAPI
serial device. The TAPI driver (Telephony Applications Programming
Interface) creates a named device from the modem, and COM2 is
thereafter accessible only via the TAPI named device. DOS Kermit, of
course, doesn't know from TAPI and messes up. You can try using the
TAPI device name (it will be listed in your Modems object in the
control panel) instead of COM2 for Kermit, but I don't know whether DOS
Kermit will recognize it.
An alternative to those two solutions (installing as a non-TAPI modem
or using the TAPI device name for Kermit) you may elect to purchase
Kermit 95. It is not free, sadly, but it has an excellent Win95
interface and is much more user friendly than DOS Kermit. It offers
all of the benefits of DOS Kermit, and more, along with a very elegant
front end.
------
Paul J. Bodin <pjb...@sirius.com> http://www.sirius.com/~pjbodin
For PGP public key finger pjb...@sirius.com
or check your favorite keyserver
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.0 (C) 1997 Pretty Good Privacy, Inc
iQB1AwUBNTjU2/goFkdd29RxAQG9PQMAkzbjPAgtRQndRA2DZevb5dSfFYbIP0BJ
Z2hiQr3Y92IFcjgPxNY1GBviTUjCGqQyVxiwt2EbWigsXWpFB4oIidWEH/1IUrgt
M8Q8uq1Am+82Pt2gf42jGplkFWqI/vSc
=RmYT
-----END PGP SIGNATURE-----