After 28 installs of 10.2 and LE2005 using more than 10 internal and external modems I got the system to work. I still don't know what the problem is or was but I just installed another modem. It is a Hayes Accura V92. I just plugged it in and turned on the computer. The modem was immediately recognized and when I configured the info such as phone # , logon and pass word the modem connected. Since then I have down loaded 150 megs of updates without any disconnects, stalls or other problems. I still don't know what the problem with the computer is but the Hayes modem seems to be a solution.
Owen
************************************************************************
Derek Jennings wrote:On Thursday 14 July 2005 02:58, Roland Hughes wrote:Mikkel L. Ellertson wrote:Owen wrote:Mikkel, I did the MTU' s o.k. but how do I do the mu's ?As for the initialization strings. I have tried the USER strings for theappropriate modem using strings for software flow control (XON/XOFF) without any changeI would use hardware flow control, instead of software flow control.My theory generated through ignorance.I have tried both versions 10'1 and LE2005 using a variety of external modems with various configurations. The results have always ended thesame. The sad light pulsates with a rhythm from fast to slow this isrepetitive then the rd light starts to blink. Packets are sent in spurts of several seconds. The cs light starts blinking then everything stops for three minutes or so then another spurt of packets. This is repeatedseveral times then all transmission ceases. I don't think it is the software or the modems . This leaves the computer. Being ignorant of the BIOS setup and the motherboard I therefore suspect them via the process of elimination. Any ideas?This doesn't sound like a problem with hardware, and I do not think it is a BIOS problem. It sounds like dropped packets. The way information is transfered over the Internet, information is brocken down in to packets. The sending system will send so may of these before it stops and waits for the recieving machine to respond that it recieved them.The size of these packets is controlled by the MTU and MRU settings. The problem comes in when the packets are larger then the a system along theway can handle. When this happens, the packet is broken down into 2 or more smaller packets. Setting the MRU smaller stops this, because it tells the sending system to send smaller packets. (Max Recive Unit.) That way, the packet does not get broken up, and possible put backtogether wrong. It also means that you generate the proper acknolagmentsfor the packets sent.Normaly, using the default settings works fine - the size is actualy setby your ISP. But sometime the ISP is not sending the correctinformation, so they get set to someting bigger then the ISP can handle.My problem is that I am out of practive on using dialup, and I don't remember exactly how to tweek them. When I was using dialup, I didn'tuse KPPP for it, so that is also a problem for me. This why I am leavingmost of this to peopel actualy using dialup. Mikkel------------------------------------------------------------------------____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________For what it is worth I have always used kppp and until very recently, yeah wireless, have been on dial up. I was never able to get a exteriormodem to work. This is with various modems and hardware. It would alwaysdial correctly, go through the handshake and then just die. I tried various settings but do not remember the details now. I have always had to buy internal real modems. RolyIf I can jump in here.In a previous life I used to design modems so once I used to know more than was healthy about them.Modern high speed modems (V.90) support error detection and correction known as V42. V42 is a packetised protocol between modems invisible to the end user. Packets from the computer are broken down into smaller packets for transmission over the link, and any subpacket lost in transit is retransmitted. At the receiving modem the original packets are reconstructed and the receiving computer is unaware of the process.If the link is poor quality the V42 protocol will be unable to recover and throughput will fall to nothing and flow control will kick in.Incompatibilities between different manufacturers modems might also cause problems but of course should not so long as they conform to the standards.You might like disabling error control with the AT &Mn command to see how the link works without it.This old document from US Robotics is worth reading for anyone sad enough to be interested in modems.ftp://ftp.usr.com/usr/dl07/sp_asci.txt derek------------------------------------------------------------------------ ____________________________________________________Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.comJoin the Club : http://www.mandrivaclub.com ____________________________________________________------------------------------------------------------------------------ ____________________________________________________Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.comJoin the Club : http://www.mandrivaclub.com ____________________________________________________
____________________________________________________ Want to buy your Pack or Services from Mandriva? Go to http://store.mandriva.com Join the Club : http://www.mandrivaclub.com ____________________________________________________
