Yesterday, after having searched the web, Usenet, and here and finding no mention of the new TrendNet TEW-424UB V2 or its SiS163u.sys driver/chipset, I posted a note in Hardware reporting my experience that it bluescreens an otherwise solid WinXP system after working well with NetStumbler for a few minutes.
I would like to understand why this post was dumped to the Newbie Bin. I don't believe it was abusive, or repetitive (other TrendNet adapters, and the SiS 162 series were mentioned, but there was _nothing_ about the 424UB V2 nor the SiS 163). It clearly relates to NetStumbler use and not general connection. I did throw in a probably superfluous and newbie sounding question, but I've never experienced NetStumbler use leading to a bluescreen - typically it just "doesn't work" if an adapter is unsupported.
I've read all the "stickies", and didn't see anything prohibiting reporting one's experience with particular hardware, other than the request to keep it in a single thread. Since there was no thread about my new adapter or the SiS 163, I thought creating a new thread was appropriate. Where did I go wrong?
Oh, to answer streaker69's question:
"You do realize that NS is not designed to be used while connected to a network don't you? I mean, it is written in the documentation that I'm sure you read when you read about if your card was compatible or not."
Mine used to work perfectly whether connected via XP ZeroConfig or not. After an update to the Buffalo WLI-CB-G54A driver it now locks the reported signal strength to the value at the time of connection, and won't update it until I disconnect - whether I'm using the Buffalo card, the built-in Broadcom adapter, or the new TrendNet USB device. So yes, I always run NetStumbler with the network disconnected.
And to answer the implied question, I didn't choose the 424 for compatibility with NS - I chose it for another purpose because it was cheap. I just fired up NS to see how its performance compared to other cards, before passing it on to its real home.