You can disable SuSE via /etc/rc.config, however this may make the effort of maintaining your system that much harder. Can you basically link out what you did? Maybe we can then find which part of SuSEconfig maybe responsible for overwriting the Winmodem config. Matt On Friday 02 February 2001 02:31 pm, Roy Leembruggen wrote:

After getting the winmodem working I lost it again after running SuSEconfig a few days later. Had to retrace my steps to get it going again! Any ideas how this can be avoided ?

On Fri, 02 Feb 2001, you wrote:

...

Hi all

Well after a lengthy struggle I finally managed to get a dreaded Lucent winmodem working, and here I am.

I have played around with kde2 and found most applications very unstable. has anyone updated kde2 from the Suse FTP server ? Did it make any difference?

I had a look at the FTP site but find it too confusing to attempt a download. What is the correct location to update kde2 and what files are actually needed. If anyone has attempted and succeeded with the update please let me know.

Kind regards

Mark

-- Mark R. Annandale SuSE Linux 7.0 Kmail 1.0.29.2

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just change the line MODEM="/dev/ttyS0" in /etc/rc.config to point to /dev/ttyLT0 instead, and you can keep using suseconfig :-) - -tosi Þann laugardagur 03 febrúar 2001 21:51 skrifaðir þú:

Yes the part that SuSE 'reset' was the modem link - the device set for the Lucent modem was /dev/ttyLT0 whereas the default for SuSE apparently is /dev/ttyS0 or /dev/ttyS1 to which /dev/modem is linked. So when SuSE reset the /dev/modem link to /dev/ttyS1 (in my case) my modem became inop !

On Sat, 03 Feb 2001, you wrote:

...

You can disable SuSE via /etc/rc.config, however this may make the effort of maintaining your system that much harder.

Can you basically link out what you did? Maybe we can then find which part of SuSEconfig maybe responsible for overwriting the Winmodem config.

Matt

On Friday 02 February 2001 02:31 pm, Roy Leembruggen wrote:

...

After getting the winmodem working I lost it again after running SuSEconfig a few days later. Had to retrace my steps to get it going again! Any ideas how this can be avoided ?

On Fri, 02 Feb 2001, you wrote:

...

Hi all

Well after a lengthy struggle I finally managed to get a dreaded Lucent winmodem working, and here I am.

I have played around with kde2 and found most applications very unstable. has anyone updated kde2 from the Suse FTP server ? Did it make any difference?

I had a look at the FTP site but find it too confusing to attempt a download. What is the correct location to update kde2 and what files are actually needed. If anyone has attempted and succeeded with the update please let me know.

Kind regards

Mark

-- Mark R. Annandale SuSE Linux 7.0 Kmail 1.0.29.2

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

- -- ______ /---------------------------------------\ \ | Þór Sigurðsson | Tor Sigurdsson | t | | Netmaður | Network Specialist | o | |-----------------------------------------| s | | tosi@rhi.hi.is | i | \---------------------------------------/_____/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1e-SuSE (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6fJ3u6mRH+PEpr2YRAgPsAJ930Ke97qqj9LcDVWARrW1GBh8pJQCeJ985 N+/89B6sPq/BQspFfF8o3fI= =wmxv -----END PGP SIGNATURE-----