[speedtouch] Multilink PPP works with Speedtouch Drivers
I've recently setup two ADSL lines 'bonded' together using a PC with Linux, PPP with the 'multilink' option, and two Speedtouch modems with the userland drivers and it works brilliantly. It is possible to do this now in the UK with an ISP here called Nildram. I've detailed the whole setup procedure here: http://www.freestuffjunction.co.uk/bondedadsl.shtml May be of interest to UK subscribers of the list or anyone interested in using Speedtouch with a similar setup. Edward Chapman Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: Writing compatibility code for V1.2.beta4
Hi Duncan, > > No it doesn't. Using either ZZZLP2.eni or ZZZLP1 & -2 concatenated > > together with modem_run fails for my 330 rev.2, with an error "Can't > > locate firmware inside ZZZLP.eni". > > That's not what I meant: this shows that modem_run has a problem. > It doesn't show that the firmware is incompatible with the hardware. (I get a slight feeling of deja vu. Did we discuss this before?) I presume the same firmware gets loaded without problems on the rev.4? Then why does modem_run have a problem with the same firmware when used with another revision of the modem? If modem_run can't load the firmware it will be difficult to establish if the firmware is compatible ;) . Somebody should try from another OS. > > Does the two parts of ZZZLP have to be concatenated before use with the > > 330 rev.4? Leonard. -- mount -t life -o ro /dev/dna /genetic/research Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: Writing compatibility code for V1.2.beta4
Hi Leonard, > > Is the firmware backwards compatible? I mean: will new firmware > > work fine on old hardware? > > No it doesn't. Using either ZZZLP2.eni or ZZZLP1 & -2 concatenated > together with modem_run fails for my 330 rev.2, with an error "Can't > locate firmware inside ZZZLP.eni". That's not what I meant: this shows that modem_run has a problem. It doesn't show that the firmware is incompatible with the hardware. > Does the two parts of ZZZLP have to be concatenated before use with the > 330 rev.4? Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: Writing compatibility code for V1.2.beta4
Hello Gilles, > I think it's a bit complicated to ask the user to concatenate the 2 part > under windows. Why would they have to concatenate under windows? $ cat KQDP1.eni KQDP2.eni > KQDP.eni works fine. Why is the use of the first part necessary anyway? Can't you just load the two parts separately? Or does one need to use only one part for certain firmwares? Leonard. -- mount -t life -o ro /dev/dna /genetic/research Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: Writing compatibility code for V1.2.beta4
Hi Duncan, > Is the firmware backwards compatible? I mean: will new firmware > work fine on old hardware? No it doesn't. Using either ZZZLP2.eni or ZZZLP1 & -2 concatenated together with modem_run fails for my 330 rev.2, with an error "Can't locate firmware inside ZZZLP.eni". Does the two parts of ZZZLP have to be concatenated before use with the 330 rev.4? Leonard. -- mount -t life -o ro /dev/dna /genetic/research Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: Writing compatibility code for V1.2.beta4
Is the firmware backwards compatible? I mean: will new firmware work fine on old hardware? Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Writing compatibility code for V1.2.beta4
I am thinking how to write code to support in the same time old user with backup configuration of (mgmt.o|alcaudsl.sys|kqd6p2.eni) ... ... and the way is not very easy. We don't know how firmware/bootloader will be available so at this time the only way we have is to ask user to utilize those from the windows driver. I think it's a bit complicated to ask the user to concatenate the 2 part under windows. I can't write code to concatenate (boot.v123.bin|kqd6p1.eni|zzzlp1.eni) to (mgmt.o|alcaudsl.sys|kqd6p2.eni) because I don't know when it is necessary and don't have a simple way to test during installation. And I don't want to add at every new installation.one more time the boot code from the configuration backup where the firmware is stored. One option is to have a sort of dry-run option in modem_run wich will answer 'boot' or 'firmware' or 'both' and do nothing else. This allow to test what part of (boot|firmware) or both is inside a file and add the boot code when necessary. Second option which is I think the easiest to do is to never concatenate the files, allow loading of two files and use -a -f ( and for all but rev 4.00 use boot.v123.bin) any comment? Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
