tony bible said in [SuSE Linux] suse, wvdial and modems at 06/Mar/1999 (Sat) 23:20:05. > > just wondering if anyone would know why wvdial says that modem will not > respond. i edited the file wvdial reads from and inserted ATZ as modem init > and ATDT as dialing prefix. it will respond in minicom but slowly and kppp > wont work either. i am not good with configuring text files and chatscripts > so wanted to try wvdial to connect to isp using pap. > > thanks > tony Well - this should depend on which modem you are using. modems are usually produced with their own specififc init strings to optimise performance. hmm. Nothing to stop you writing you own or tweaking the original, though. Maybe a good idea to try the Web site of you modem manufacturer and see if they have their own scripts to download. Try you ISP support too. Or for example - http://www.visi.com/support/modems/ http://www.netins.net/dialup/modems/init/ http://curlew.davlin.net/modemhelp.html Otherwise configuring wvdial seems pretty easy - edit /etc/wvdial.conf - inserting your ISP phone number, ISP user name, ISP password, modem baud rate. I may be wrong here but; Keep init1 to ATZ, or ATZ1, as this command resets the modem hardware. im no expert. init2; insert the script from your modem manufactureretc that handles the dialling etc. best to get hold of a modem command reference if you want to hack some scripts yourself. i found the most important command is M0 - this turns off the modem sound chip!!! good luck - To get out of this list, please send email to [EMAIL PROTECTED] with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
