On Monday 14 February 2005 04:41, Rosemary McGillicuddy wrote: > I bought this modem because internal modem too difficult for me to > configure, even though various articles said it is possible. So have > been trying to ad modem using system configuration, and more latterly > kppp. Thought kppp was going to do it, but got the usual "your system > is not connected" message. I suppose there is a way to do this - but > very disappointed at present.
Rosemary, a potential solution that I sometimes take is to create a symbolic link in your dev filesystem to point to the com port and then try to connect. This assumes that a lot of dialer programs use /dev/modem as a shortcut to the modem. So, to experiment, open a command line, su to root and issue this command ln -s /dev/ttyS0 /dev/modem Then try KPPP again and see if it dials in. If it works, then you know that your modem is on Com1. If it fails, then issue a command ln -s /dev/ttyS1 /dev/modem and then try again. If that works, then your modem is on Com2. One of those should work. If they do, you can actually setup an entry to automatically create the link for you in the startup scripts so that you don't have to do it every time. You can also try opening up KPPP, choose Configure button and go to the Device tab. From there, change the modem device from /dev/modem to /dev/ttyS0 and then click on the Modem tab and click the Query Modem button. That should give you some reponse. Rinse and repeat using the /dev/ttyS1 device as the mdoem device. -- Bryan Phinney
____________________________________________________ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Join the Club : http://www.mandrakeclub.com ____________________________________________________
