[erol]

The whole thing is imo the usual NTL mess.

We simply do not know what the dialer sw does at the moment (when it works that is)

I suspect the intial motivation from NTL was to be able to automaticaly move people from one dial up number to another, based on loads being experienced and so on. However I also suspect that any other number of 'good ideas' were then tacked onto this and no consideration was given for the downsides.

There are reports that even when using the same numbers that the dialer sw does connections can still not be obtained using 'standard' (dun in win for example) meathods and this implies dome form of 'proprietary' authentication that only the dialer is capable off.

There are reports of it installing spyware.

There are reports of it blocking some standard windows features such as ICS.

There are reports of it simply not working

There are reports of it working but the dial up number it forces not working.

From some reports it would seem that it is quite an extensive and expansive install, adding / changing dlls, registry entries and the like.

All in all the usual from NTL imo. Badly thought out. Little or no warning to users. Little or no 'real' information. Genral attitude of 'we impose and you accpet - or go elsewhere'.