Ok, some snippage and I have combined some responses here, sorry if that proves to be annoying, but I wanted to get my thoughts all on one track. Oh, this is long & winding and some of it is OT. Very sorry. Please humor me. Thamk you all for your help.
> > It's an external hardware modem on ttyS0. And I am connecting, > > otherwise you wouldn't be seeing this email. I'm just not staying > > connected. > > > > It's so simple then ... Ok, I'm going for you. You are here for the action. It's like geek reality TV. Well, reality mailing list at least..... > 1. start your inet connection > 2. kill the program which communicates with modem (kill -9 something) Ok, kill -9 1771 (which is wvdial) > 3. start "minicom -o" (without initialization of modem) Got it. Actually I have used the DOS version of this program. Back in "the day". > 4. command at&v will show u actual modem setup Now the problems start. First I saw nothing on the screen at all. I turned on local echo, so now I can see the command when I type "at&v", then I hit enter & nothing. Does this mean something isn't working? Or does this mean I don't know what I'm doing? PPPD is still active, it's shows in 'top'. > U can save actual setup using at&w command. > U can restore saved setup by atz command. > Command at&f restores setup to factory predefined. > > So if u compare saved outputs of at&v (after step 3.) > and after at&f, u will find the right init string. > > Yes I know, it's simple to do on any linux or unix system, > but how to run steps 1-3 on M$hit, is a double dutch > for me, but maybe u know it :-). > > noro Well, I found out how to get some info from Winblows. It seems that wincrap keeps a log of the last modem session. Below is the modem log file from Win98: begin log----------------------- 01-15-2004 21:30:11.33 - Standard Modem in use. 01-15-2004 21:30:11.33 - Modem type: Standard Modem 01-15-2004 21:30:11.33 - Modem inf path: MDMGEN.INF 01-15-2004 21:30:11.33 - Modem inf section: Gen 01-15-2004 21:30:11.60 - 57600,N,8,1 01-15-2004 21:30:11.60 - 57600,N,8,1 01-15-2004 21:30:11.60 - Initializing modem. 01-15-2004 21:30:11.60 - Send: AT<cr> 01-15-2004 21:30:11.60 - Recv: AT<cr> 01-15-2004 21:30:11.70 - Recv: <cr><lf>OK<cr><lf> 01-15-2004 21:30:11.70 - Interpreted response: Ok 01-15-2004 21:30:11.70 - Send: ATE0V1<cr> 01-15-2004 21:30:11.70 - Recv: ATE0V1<cr> 01-15-2004 21:30:11.80 - Recv: <cr><lf>OK<cr><lf> 01-15-2004 21:30:11.80 - Interpreted response: Ok 01-15-2004 21:30:11.80 - Send: ATX4<cr> 01-15-2004 21:30:11.90 - Recv: <cr><lf>OK<cr><lf> 01-15-2004 21:30:11.90 - Interpreted response: Ok 01-15-2004 21:30:11.92 - Dialing. 01-15-2004 21:30:11.92 - Send: ATDT*##,,,#######<cr> 01-15-2004 21:30:45.07 - Recv: <cr> 01-15-2004 21:30:45.07 - Interpreted response: Informative 01-15-2004 21:30:45.07 - Recv: <lf> 01-15-2004 21:30:45.07 - Interpreted response: Informative 01-15-2004 21:30:45.07 - Recv: CONNECT 01-15-2004 21:30:45.07 - Interpreted response: Connect 01-15-2004 21:30:45.07 - Connection established at 57600bps. 01-15-2004 21:30:45.07 - Error-control off or unknown. 01-15-2004 21:30:45.07 - Data compression off or unknown. 01-15-2004 23:07:23.07 - Hanging up the modem. 01-15-2004 23:07:23.07 - Hardware hangup by lowering DTR. 01-15-2004 23:07:23.46 - Recv: <cr><lf>OK<cr><lf> 01-15-2004 23:07:23.46 - Interpreted response: Ok 01-15-2004 23:07:23.46 - Send: ATH<cr> 01-15-2004 23:07:23.59 - Recv: <cr><lf>OK<cr><lf> 01-15-2004 23:07:23.59 - Interpreted response: Ok 01-15-2004 23:07:23.59 - 57600,N,8,1 01-15-2004 23:07:23.59 - Session Statistics: 01-15-2004 23:07:23.59 - Reads : 2821953 bytes 01-15-2004 23:07:23.59 - Writes: 451460 bytes 01-15-2004 23:07:23.59 - Standard Modem closed. end log -------------------------------------------- now, here is my orginal wvdial.config which was created by wvdialconfig (unsername & password replaced) begin file----------------------------------[Dialer Defaults] Modem = /dev/ttyS0 Baud = 115200 Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ISDN = 0 Modem Type = Analog Modem Phone = *70,,,2122222 Username = username Password = password end file------------------------------------- And here is the wvdial config file I came up with based on the Windoze log. begin file------------------------------------ [Dialer Defaults] Modem = /dev/ttyS0 Baud = 115200 Init1 = AT Init2 = ATE0V1 Init3 = ATX4 ISDN = 0 Modem Type = Analog Modem Phone = *70,,,2122222 Username = username Password = password end file------------------------------------- I get the same results with each config file. So, comments? Ideas? Observations? Would it be better if I simply used the first init string (ATZ) and skip all the others? I don't think this would help the problem, as under KPPP I was only using ATZ, no other stings, yet have the same problem there. But would this be better for the modem I mean? On the subject of config files, doesn anyone see anything wrong with my /etc/ppp/options. At the begining you will see the settings that were originally there and after that you will see the settings I currently have which were suggested by someone eles. begin file---------------------------- # original settings # lock # noauth # noipdefault # usepeerdns # end original settings # /etc/ppp/options lock debug crtscts noauth defaultroute lcp-max-configure 45 ipcp-accept-local ipcp-accept-remote idle 600 # eof end file--------------------------- next letter ------------------------------------------- > Um, I worked for years for a isp-which-shall-remain-nameless dealing > with hardware issues. Most connectivity problems are due to poor setup > of the comm program or bad phone lines which create signal noise on > the line which interferes with the signal you are trying to send. > Since any interference will tend to cause you to disconnect, that is > probably the culprit in this case. Could be. In fact I am an electronic tech and I have worked with telecom. While I certainly see validity in all your observations . . . > What kind of modem do you have? What's the connection speed if you do > get connected? How do you have the hardware hooked up? Any splitters, > long phone cords, cheap/ratty phone cords or other reasons why the > signal may be attenuating? Replace the phone cord with as short a > length as possible, with NO splitters on the line, make sure that > there is nothing that could provide interference to the signal and try > again. If you have a separate line/number, try that line with the > modem. Do not use the over the ac power line phone converters or > wireless phone setups, they are inherently noisy or prone to > interference. Modem: external fax modem, the documentation doesn't list a manufacturor, the modem has the number V1456VQE on the face plate. connection speed? in reality? 28000 if I'm lucky. more on this later. Hardware hookup: Ok, you will love this. Starting from the wall plug -- Isotec surge protector -- to modem in second computer -- to the modem in question -- to telephone. Long phone cords? Of course. You don't think the wall plug is on the same side of the room as the computer?? How silly would that be? =) I have, at this very moment a brand new line between the modem & the wall, all other devices removed. I will see how that goes. While I know this is a lot of stuff to have, my excuse is "it works with windows" and "it worked on my old computer/modem under linux". But I'm open to anything here. I know that sometimes the answer is the one thing you think it isn't..... No second line to try this with. > (True story, lady called up one day complaining that she lost her > connection every time the refrigerator turned on. She had run the > phone cord behind the thing, it was an ancient model and apparently, > the motor wasn't shielded that well. We were on the same line and when > it cranked on, you could hear the hum on the phone line.) Oh yea... I can totally see that. > Unhook the phone cord from the modem and hook it to a regular phone. > Call someone and tell them you are just checking the phone for noise > and could they put it down for a minute in a pillow or something. > LISTEN! If you hear anything, try the same experiment from a different > phone jack in the house on the same line. If you still hear noise, > call the phone company (from the noisiest phone you own), on that > line. (Some phones are just plain noisy.) Complain sweetly, asking > them to fix the noise, please, it's driving you buggy. DO NOT SAY the > words "computer","modem","Linux" or"connection" when you talk to the > nice person on the phone.( Otherwise they will tell you that they > don't support modem or fax connections, and they don't, but they will > take steps to kill the noise for you.) They will run a remote check on > the wiring, if they find something, they will send someone out to fix > it.(You can also check it with the procedure outlined below, but the > program they use checks for noise outside the range most of us can > hear.) The phone at the end of this string of wire is the one I use the most often. No noise problems, even thru all this mess. I never say those four words to the phone company. Ya know, maybe I should call them anyhow and complain about noise anyway. Can't really hurt.... > If they don't find an external problem with the line, it may be > between the box on the outside of the building and your phone. Locate > the box and check for physical damage. (I had one that was cracked, > and it leaked water if it rained from the north and the wind was > blowing fairly hard. That one about drove me crazy trying to figure > out. I made the connection only because the back door opened to the > north and I had to walk the dog in the rain one day and the rain > driving into the house and the inability to get a connection minutes > earlier just clicked.) If you have your own house, it won't be hard to > find, if you live in an apartment, check with the landlord. If you can > get to the physical location of the box, all the ones I've seen have a > phone jack that you can plug your test phone into to check the > connection. Plug it in and see if you hear noise when you call out, if > not, it's an interior wiring problem, and your life now officially > sucks. (If you live in an apartment, your life sucks even more, > because the phone company most likely is NOT going to fix the line > between that box and your phone jack.) If you live in a house, you are > going to pay the phone company to fix the line unless you have been > paying the monthly fee for phone repair. Now, remember that max connect speed of 28000 I mentioned? I do live in an apartemnt and our box is disgusting. How do I know? Because half the time it hangs open to the weather. Hmmm... I just did a "ping". I had a 2% packet loss. Does that mean anything useful in this context? I just went outside to check the box. It's closed (amazing) and actually, it looks like a different box. I say that because it isn't broken. Wonders will never cease. But I'm totally aware that the phone company don't care. If it's in my wiring I'm screwed.. Blah blah blah. Actually tho, as I said I have telecom experience. I can run my own wiring to the box. I'm sure that is not "legal" but I do know how to do it. > If you only have one line, and you determine that it's a problem > between the phone jack and the box on the outside, you are going to > make an appointment for the phone guy to come over and check the > lines, or to add a new line just for the computer. (if you do that, > check the phone company for the best deal, sometimes they do something > called a "teen line" where the installation and monthly charge a bit > cheaper.) > > You want to BE THERE WHEN PHONE GUY IS THERE! You want him to be > predisposed to help you. You want to be as nice as you can, but don't > try to impress him with your knowledge, this is the time to try out > those social engineering skills you heard about. Let him explain how > the phone thing works to you, most folks take pride in their work, use > ego *hahahahaha* Oh gawd, how right you are. Actually, once long ago when I had a second line put in for the computer (anther apartment) I told the phone guy I was an elec-tech and he let me help him, showed my how his line computer worked and everything. But yea, most of the time it's best to act stupid. Of course, the book shelf covered in electronics books might give me away.... > and "pride in work" to your advantage. When the guy is in the house, > explain to him the dilemma of the noise interfering with the > connection, and ask him to do the best he can to fix it. How you word > this is going to depend on your impression of the guy. You don't want > to be the last customer of the day, you don't want him to be delaying > his lunch break because of you, etc. Heck, make the appoint for first > thing in the morning, take the day off or call in sick, run out for a > dozen fresh donuts and make coffee. "hey, I know you probably aren't > supposed to take stuff from customers, but I got these donuts if you > want some. Oh yeah, I'm fixing to make some coffee, you want a cup?" > Explain your problem, find out what his solution is, make adjustments > as necessary then get out of his way! =) Right on. I know that when I repair things for people this stuff works on me. I always fixed the phones of people that had coffee and food first. > Tell the phone guy that you want the best connection you can get for > your computer. I have yet to have one give me a hard time about it, > unlike the folks on the phone you call with a complaint. This is > backed with plenty of testimony from clients I spoke with at my isp > gig, btw. > > I did have one phone repair guy put in a phone jack for me when I > wanted a separate line for computer, so I wouldn't have to run a long > phone cord in the house, that cost me $50. I would recommend it, > because then it's all new wiring. When you set up the appointment, > tell the phoneco that's what you may want and find out what it costs > in your area. Actually the phone guy I mentioned above... He installed a new jack for me for free. He wrote up on his bill that it was already there. You can't find a person more decent than that. > > It's so simple then ... > > 1. start your inet connection > > 2. kill the program which communicates with modem (kill -9 > > something) 3. start "minicom -o" (without initialization of modem) > > 4. command at&v will show u actual modem setup > > Modems talk in ALL CAPS btw. AT&V. You can also check the > manufacturer's manual, if you received one. Check their website, if > necessary and download it. The "manual" is useless (how to set it up in Winblows) and I can't believe I threw away the box. What a dummy.... Wait, sales receipt... Score. It's listed as a Phoebe 56K External v.92 Modem. I'm gonna go google for a spec sheet..... Well, no data sheet, but: http://www.phoebemicro.com/Support/Driver_Download/56K_External_Driver/56k_external_driver.html The CM1456VQE-C is the one that I have. Ok, I just sent them an e-mail asking for a data sheet. Will see what happens. > > U can save actual setup using at&w command. > > you can also save it to one of up to [ number of profiles set by > manufacturer ]. It's in the manual. AT&W1, AT&W2, etc. > > > U can restore saved setup by atz command. > > ATZ > > That should reset the modem to the default. It's a good idea to issue > that particular command before you close your com program, btw. > > > Command at&f restores setup to factory predefined. > > > > Unless you have changed it, which is possible with the AT&W command. > Use AT&W1 to save whatever you want, and load that with AT&F1. > > Years ago, I burnt out a modems eprom by making it write the commands > every time I initialized it. duh. Really? I never heard of such a thing. Great, one more thing to worry about. *haha* Ok, the new phone cord hasn't helped. I've disconnected several times already, so my long string of wire & devices is not the problem. > > So if u compare saved outputs of at&v (after step 3.) > > and after at&f, u will find the right init string. > > > > Also your isp may have an example of what it uses, make your init > string match theirs. Ummm... good idea. I will check into that for sure. For those interested, data on my ISP can be found at www.colostate.edu/acns/modems/ As I have mentioned previously, they totaly refuse to associate with Linux users. next letter ------------------------------------------ > >>It's so simple then ... > >>1. start your inet connection > >>2. kill the program which communicates with modem (kill -9 > >something)>3. start "minicom -o" (without initialization of modem) > >>4. command at&v will show u actual modem setup > > > > > > Modems talk in ALL CAPS btw. AT&V. You can also check the > > manufacturer's manual, if you received one. Check their website, if > > necessary and download it. > > > > I don't know which modems did u use, but all modems I know > are happy with lower case commands as well, but it's > true they answer in CAPS. > > > > >>U can save actual setup using at&w command. > > > > > > you can also save it to one of up to [ number of profiles set by > > manufacturer ]. It's in the manual. AT&W1, AT&W2, etc. > > > > Right, I had a modem with 6 user profiles, but I never needed > more then factory one, since my init string always starts with at&f. > > In case, when the guy just need to catch init string used > by M$hit, the simplest is the best way, so to use profiles > numbers is really not necessary. > > > > >>U can restore saved setup by atz command. > > > > > > ATZ > > > > That should reset the modem to the default. It's a good idea to > > issue that particular command before you close your com program, > > btw. > > > > U are wrong, profile "0" will be loaded. (atz = atz0) > > > > >>Command at&f restores setup to factory predefined. > >> > > > > Unless you have changed it, which is possible with the AT&W command. > > Use AT&W1 to save whatever you want, and load that with AT&F1. > > > U are wrong again, u can't change default factory profile by at&w. > (It can be changed in other ways.) > > So u exchanged the meaning of at&f and atz, please rtfm if in doubt. > > 99% of modems has only one factory profile, which is accessible > by at&f, and two user profiles (write access at&w0 or 1, > list access at&v0 or 1, restore setup from profile atz0 or 1) > > noro Well, I don't know enough to come down on either side of this debate, so I will just keep open options for now & try RTFM myself. Is there a man page which covers modem strings? I'm sure I can find something on the inet also. I'll google on that later. Ok.. I don't think I'm gonna work on this for a few days. It's consuming my life & I have other things I have to do. I'm sure I will be back soon however. Again, thanks for all the help & suggestions. Adrian -- On The Fly Photography http://204EastSouth.com -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GAT d-@ s: a C++ UL++ L++(+++) P E- W++ !N o? K- w--- M+ PS+++ PE+++ Y+ PGP t++@ 5+++ X++ R+@ tv-- b++ DI++++ D+ G e+ h+ r y++ ------END GEEK CODE BLOCK------ -- [EMAIL PROTECTED] mailing list
