Hello again! Right after I mailed that, I took another look at my modem command strings and it turned out that the initialization string was wrong! I am now replying from my Linux box. I had changed the initialization string to account for the poor quality of our second phone line: it was making the modem wait a bit for dialtone detection so that the modem would not simply think there was no dialtone. Apparently, that fix does not work any more. Actually, except for the modem difficulties and some fun getting the kernel to compile correctly, the upgrade was not so bad. An old I/O conflict I didn't know enough to resolve properly during my early Linux days reared its ugly head on top of the other problems. As a result, I ended up fixing the I/O conflict and developing a very big aversion to make xconfig. Kernel parameters (e.g., IDE support and PPP support) were getting dropped from the kernel. Once I switched to make menuconfig, the kernel compilations started making sense. So I had to fix an I/O conflict, then find a reliable way to set kernel parameters (I didn't know about make cloneconfig last month.), then account for changes in dialout from 6.1 to 7.1, then fix an initialization string. Sounds bad, but I learned a lot. One side product is that when I get some time, I'll probably finally be able to get my sound card working, too. Were I a Microsoftie, I would have PAID for the upgrade and then probably a new modem, too. It appeals to my Scottish blood! I have a few mionor problems to work out, but I'm back at about 95 % now. Steve
You are totally brave for such a large jump in upgrading! Did you check the permissions for group/user on /dev/modem or /dev/ttyS* (whereever your modem is).
Matt
------------------------------------------------------------ --== Sent via Deja.com ==-- http://www.deja.com/