I think the documentation route is better, there seems to be a lot of
little foibles (at the moment) that seem to throw (impatient) people off
course, and no doubt, is the cause of many "bug reports" and forum
When I've been writing stuff on the wiki I've been trying to say the
obvious, because sometimes basic things are not obvious to some people!
At the very least it lets you can get away with "RTFM" ;) ;)
Sometimes I wish I understood ndis so I could help code.
> -----Original Message-----
> From: Adrian Irving-Beer [mailto:wisq-ndis@...]
> Sent: 07 February 2005 13:55
> To: Andrew Martin
> Cc: ndiswrapper-general@...
> Subject: Re: [Ndiswrapper-general] You can't always trust iwconfig
> On Mon, Feb 07, 2005 at 08:00:20AM -0500, Andrew Martin wrote:
> > I rarely see iwconfig change the essid from "on/any" (or at least
> > not before I've brought the card up, which could be why!) but it
> > still works.
> Yes, it seems fairly standard that the reported ESSID doesn't change
> until the card has actually successfully associated with the target.
> The functionality doesn't bug me terribly, but it seems to confuse
> some people.
> I've seen people think that ndiswrapper is somehow inherently broken
> because it won't 'accept' their 'iwconfig essid' (i.e. they don't see
> a result), when really, it's just that something else is incompatible
> and association can't be completed successfully.
> I've seen at least one where someone stated they had to run it '30 to
> 40 times' before it took effect, when I suspect it was just a very
> slow association.
> I don't know enough about the inner workings to know why it
> works this way.
> I'm not sure whether the proper response to this is to put something
> in the installation docs, or to change the code so that it reports
> what the user told us until the Windows driver reports otherwise.