Forum Home
Press F1
Thread ID: 112104	2010-08-24 02:20:00	Vista, Presario v6000 & WiFi Adapter Quirk	Perry (4966)	Press F1

Post ID	Timestamp	Content	User
1131199	2010-08-24 02:20:00	Caveat - This is a partner's laptop and it's running Bitsa, about which I have almost no knowledge (apart from "I hate it!") I have purchased, fitted and installed a realtek USB WiFi adapter . Why? The in-built WLAN adapter doesn't work, being a consequence of a mobo component failure that caused the same problem in 1-in-7 of that model (according to the results of a www search) . The adapter was the easy solution . (So I thought!) After yet another www search, later, it seems that Bitsa has problems with USB WiFi adapters actually working . I . e . the laptop can see the Wireless Network, says it's connected, but lies! Or, if not Bitsa, it's that damned HP's Network Assistant . (Can that be disabled, I wonder?) Anyway . . . . I eventually found a www tip that resulted in me assigning an IP address manually, in the alternative configuration window . Bingo! Data flow! So maybe it was connected, as it said, but just wouldn't allow data to move back and forth? Some oddity with server assigning of an IP address? The WAP just feeds through to DHCP, which is enabled enabled on my (own, local) server . My own laptop works fine, here or anywhere else . But I have the nagging thought that maybe if my partner calls in to a cafe that has a WAP on offer, as well as muffins and coffee, she may well find that there will be no WiFi connection made, even though the laptop should try the server-assigned-IP-address option, first, before trying the manually-assigned alternative connection address . After all, if server-assigned IP address didn't work here, why would it, anywhere else? I'll search out a public WAP next week, sometime, to see what happens . But it occurred to me that someone here might have an insider tip on the vagaries of Bitsa's USB Adapter WiFi access, before I get to that . Or HP's Wireless Assistant, if that be the culprit . TCP/IPv6 is disabled, BTW . And there's no connectivity problem for the laptop with the manually assigned IP address, wired, or wireless . Poster's competency: about power user (some days!) . No geek am I .	Perry (4966)
1131200	2010-08-24 02:22:00	The heck is Bitsa?	inphinity (7274)
1131201	2010-08-24 02:27:00	aka Vista	Perry (4966)
1131202	2010-08-24 07:32:00	And the point of this post is?	lakewoodlady (103)
1131203	2010-08-24 08:56:00	And the point of this post is?A guessing game? You wrote it - who's to know? But if you refer to my post, initiating this thread, does this help? After all, if server-assigned IP address didn't work here, why would it, anywhere else? . . . It occurred to me that someone here might have an insider tip on the vagaries of Bitsa's USB Adapter WiFi access, . . . or HP's Wireless Assistant, if that be the culprit .	Perry (4966)
1131204	2010-08-24 09:00:00	Use HP's wireless or Vista's wireless option. Not both. It may help if you turn file sharing and discovery on	Speedy Gonzales (78)
1131205	2010-09-06 04:00:00	After much introspection, I decided that the DHCP in the (mine/internal) web server was at fault. It was, so now (for now?) the problem is fixed. :badpc: Thanks for the patient suggestions, folks. I do appreciate you making the effort. A little knowledge is a dangerous thing. Mea culpa.	Perry (4966)
1