Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?

• Previous message: Bernd: "Re: [SLE] Locating cause of signal"
• In reply to: Bernd: "Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?"
• Next in thread: Bernd: "Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?"
• Reply: Bernd: "Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: Sat, 27 Sep 2003 01:49:48 +1000
To: SuSE Users Group <suse-linux-e@suse.com>

Bernd wrote:
> On Wednesday, 24 September, 2003 23:58, you wrote:
> <snip>
>
>>I have been busy elsewhere (building a computer for a friend of mine)
>>and haven't been reading the thread and if you have already done what I
>>suggested some time ago then you can send me an abusive e-mail :-).
>>
>>You said above "or it's the modem itself." One of the things I
>>suggested was for you to get hold of another modem and see if you still
>>come up with the same problems. I think in an earlier message you said
>>that you would try and (?)borrow another modem for this purpose but I
>>don't know if you did.
>>
>>The other thing, what exactly is the initialising string(s) that you
>>send to the modem in SuSE?
>
>
> No abuse!!!
>
> I'm not able to return my modem for another one. I've been tryin to fix this
> problem for so long that I passed the timeframe of the distributors "return
> policy". AAARGH!!! I am trying to contact the manufacturer to see if they
> will replace it with an external, or refund me (according to warranty). I am
> still within the warranty period, so...
>
> Unfortunately, I don't have another modem to try at present.
>
> Here's the main init strings that I have used for this modem:
>
> The init string that was default in windoze, plus a few related S Registers
> (Tested successfully in windoze. No difference in SuSE.):

 From where *exactly* did you get the initialising string for Windows?
Did it come from a log file or from the modem "profile" file sitting in
the Drivers sub-directory of the Windows operating system?

> AT&F1E0Q0V1&C1&D2S0=0S6=8S7=60S10=200S19=0S25=20L1M1&M4&K1&H1&R2&I0B0X4

OK, the first thing. The '&F1' above -- is this just a typo on your part
or is this actually in the init string? Should this be '&F' or '&F0' or
is it really '&F1'? Why am I asking? Because....

If it is &F1 then this is re-setting the modem to factory default
settings for Profile1 - which may NOT be the same as the ones in
Profile0. And it is Profile0 that you would normally be working with. In
fact the ATZ mentioned below (and used in wvdial and so on) loads
Profile0 into the active profile - but you have not reset it to factory
defaults because you have used AT&F1 and reset Profile1.

Change the beginning of the above string to AT &F (&F0 which is the same
thing; &F automatically means &F0 in modem language).

Now for the rest.

By issuing AT&F you are resetting Profile0 to factory defaults. If you
look in the manual it will show you what the defaults are for each of
the parameters and the S Registers. It is therefore a waste of time to
issue commands to the modem to set parameters to default values if they
are already set by the AT&F command. For example, (?)all modems now have
&C1 and &D2 as default settings; same as Q0 and V1. However, S0 is
normally set to 1 so issuing 'S0=0' is correct (you don't want the modem
answering the phone should someone call you on the line :-)).

You only ut into the init string the commands which are NOT the defaults
and the ones you really want to use to modify the behaviour of the modem.

Get rid of any unnecessary commands in the above init string if they are
already the defaults (thru the &F command). Apart from being a 'waste'
it is also possible that having too many commands represented by the
number of characters on a line will cause the modem to reject the
commands- there is a finite number of characters you can put on a line
for the modem to recognise. Somewhere in the manual it will tell you
this. From memory this number used to 40 characters but it may have gone
up on the newer modems.

>
> The init string that was default upon using wvdialconf (Same as Yast
> default.):
> AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0

This is the SECOND line of initialising strings when you are setting up
the modem when installing SuSE - and which also appears in kppp and in
wvdial (although I've had to manually type in info into this conrtol
file). The first line is ATZ.

Re the above. Drop the "+FCLASS=0" from the above. The "+FCLASS" is to
do with a FAX setting, and may be causing you a problem.

Now, getting back to the ATZ -- which I said was the FIRST line of the 2
(?or 3) init strings shown when setting up the modem.

ATZ I said will set the ACTIVE profile of the modem (ie the one with
which the modem will dial out and communicate with your ISP) to the
paramaters stored in Profile0. But see what I said earlier above re
whether the &F1 is a typo.

>
> All the init strings that I have used are prefaced with a first init of ATZ.

Oh what a "dangerous" thing to say :-). I hope you mean that, "There are
2 initialising strings issued to the modem and string #1 has ATZ in it
and the following one has ATQ0V1...... in it."

Reason why I am saying this is that if you have something like ATZ Q0 V1
etc then this string will not work: anything after the ATZ is ignored by
the modem (UNLESS you put several "~" after it to create a delay of
several seconds for the modem to digets the ATZ). Oly use ATZ if it is
the only parameter in an intitialising string.

>
> One other thing I just noticed in my windoze log, is that there was a 3rd init
> string: "ATDT;" before the normal dialing start of "ATDT". My understanding
> from the manual is that the " ; " returns the modem to command mode after
> dialing. I have not been using this in SuSE, yet it is used by default in
> windoze. I'm testing it right now. I'll report back if anything new
> happens.

Drop the ";" at the end of the ATDT. ATDT only means that you ware using
Tone Dialling and there is no need for the ";".

What I suggest is that you type the following into the wvdial or kppp or
when you are installing SuSE and configuring the modem:

alter the FIRST line to read-

AT &F E0 &C1 &D2 S0=0

even though &C1 and &D2 are probably default settings anyway'

then either DROP the second line completely, because there is no need
for it, or change it to read ATZ.

And now for the closing comment-

I didn't know that your modem was an INTERNAL modem. I had assumed that
it was an exteranl modem, connected via cOM1 or cOM2 or USB.

Being an internal modem, it's not a Winmodem which requires a special
driver to work correctly in Linux?

( I have an internal modem which uses a Rockwell (now Conexant) chipset
and I have to use the hcf driver put out by Linuxant - and hte modem
works beautifully!)

Cheers.

>
>
> Thanks everyone!!!
>
> Bernd

Pleasure.

-- 
Hire teenagers while they still know everything.
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com

• Previous message: Bernd: "Re: [SLE] Locating cause of signal"
• In reply to: Bernd: "Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?"
• Next in thread: Bernd: "Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?"
• Reply: Bernd: "Re: [SLE] (Revisited) Works in Windoze, NOT in SuSE!?!?!?!?!?!?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]