Status update on 0.4

["Marius Milner" <mariusm@xxxxxxxxxxx>]

Yes, I found and fixed the bug that you have all been complaining about.
If you have all of the following... 

- An ORiNOCO card 
- NetStumbler version 0.3.30 
- "Auto Reconfigure" switched on 

... then the following sequence of events is likely to occur: 

1. You eventually associate with an access point while you're scanning. 
2. You go out of range, or in better range of a different AP. 
3. "Auto reconfigure" kicks in to disassociate you (otherwise "get AP
names" won't work) 
4. In reconfiguring the card, it inadvertently puts it into a state
where it will not discover any access points at all. 

This has been fixed in version 0.4 (coming soon!) 



Marius