I try to make someone to convert to Linux, and so installed a SuSe 9.0 system on his machine.
The problem is that he has a Lucent winmodem and I cannot make it work:

SuSe 9.0 auto-detected the modem, auto-installed its driver (/dev/ttyLT0), but anytime I try to dial in, the system becomes and stays irresponsive (no more response to keys pressed on the keyboard or mouse moving or clicks), meanwhile I see endless HDD activity.

I saw that the modem uses com3 in windows, so I tried to change it to /dev/ttyLT2 under linux. No panic this time, but I got an immediate error message saying that no response from modem.

Could you help me what to do?

Huh, it looks like I was impatient:

It begins to dial 20 MINUTES after I click on the kinternet icon.

Looks like the Lucent linmodem driver is a heavy stuff for a Celeron 533.

But how to use the internet when your modem dials 20 minutes after clicking on kinternet (meanwhile your system is irresponsive to any user interaction)?

Wow, when I use wvdial directly to dial in, dialing starts in not more than 5 minutes.
Besides, only the first dialing takes so long to start, any following dialing is started immediately. It is a good thing.

Now I think this problem may have something to do with the modem init string.

However, I do not know why this modem works only if it is setup as device /dev/ttyLT0, whilst it uses COM3 in windows?
I think it should use ttyLT2, instead, but I do not have such device.
Should I create it? How?