SUMMARY: PC-NFS/Pro(2.0), Win95, and PPP

From: Ron Madurski (rmadursk@galaxy.galstar.com)
Date: Tue Aug 20 1996 - 11:03:56 CDT


The question...

:>
:>Hi,
:>
:>I have a TI 570CDT notebook computer that I need to get PPP working on
:>as well as a network connection via a PCMCIA card (That part works OK
:>already, I just need to figure out how to swap configurations easily).
:>
:>Anyway, I have a modem installed (New Media Netsurfer or USR Sportster,
:>both are Fax/Modems). The modem is working just fine, I can use
:>Hyperterm to dial out and the system answers OK. I have gone through
:>the Express config as well as manually configuring the PC via the
:>Configuration screen. I have set up PPP on several other machines with
:>no problems, this is the first Win95 install I have done.
:>
:>When I get into the Remote Link Manager and try to do a connect I get a
:>timeout error waiting for the OK back from the modem. This makes sense
:>(to a point) because when I try to use the manual dial option I can type
:>in at and I get no response. I try ate1v1 and I still get no response.
:>I can however do an atdt(somenumber) and it will dial out and the system
:>answers. Since I am getting no response from the modem that is all I
:>can do. I have tried several different modem setups, deleted all of the
:>modem init string, Written my own dialup.scr, as well as a plethora of
:>other things too numerous to mention...
:>
:>So does anyone have any experience with getting this to work and why is
:>it being such a pain?
:>
:>
:>Thanks.
:>

The answer...

>From Dave Burwell:
:
: Because PC-NFS Pro doen't support com3 or com4 correctly. Sun knows this,
:and they really don't care. Your PCMCIA modems are set to use com3 or com4
:(you didn't say, but I bet $5). If you could change them to com1 or com2, it
:would work, but I have never been able to figure out how to to that under W95.
: What I have done is attach an external modem to the com2 port on the
:laptop, and proved it would work. But the external modem is a pain to carry.
:

OK, here is what I think I did to make this work. I disabled COM2 from
the Device Manager in Win95 by unchecking the box in Device usage for
that com port. At the same time I removed my modem from the Modems
panel in Control Panel. I also turned off the Serial interface in
NFS/Pro Configuration. So basically the modem is gone (I removed it
physivally as well), the COM Port is disabled, and NFS has no interface
to deal with on boot up. I think that last point is the most critical.
Since the Remote Link Manager (RLM) starts before Windows has a chance
to finish its "analysis" of the machines hardware, the com port is in use
before it is being checked. Somehow this "messes it up". After booting
check to make sure that there is an X in the com port on the Device
Manager page. Put the modem back in and restart the system again to
install the modem drivers. This time the modem should show up on COM2
since it is available. If it doesn't try again. When the modem is on
COM2 and works in that confugration then you can go back and enable the
serial interface in your configuration again. It lies to you, you do
not have to reboot the machine to get the new interface to work when you
switch from the Lan to Serial interface. You do need to restart when
going the other way to get the ethernet card initialized.

Any questions?

-- 
Ron Madurski      
rmadursk@galaxy.galstar.com



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:08 CDT