I usually use "checking for solutions" yet I hardly ever find that it does offer any solutions worthwhile.
I think that this is just so MS can gleam log reports on their software compatibility.
My connection has been pretty good so far - no disconnections (touch plastic), just have the annoying orange asterix over the network icon.
Hope you manage to sort out your connection.
Digger,
I'm a newbie so apologies for format of response.
This was my message from "Control Panel\System and Security\Action Center\Message Details"
"This is a Windows 7 beta response. If you have feedback about this response, please use the survey at the bottom of the page.
Address a problem with your wireless network card
Your wireless network card isn't working properly because a compatible driver isn't available for this version of Windows.
The model name of your wireless network card is NETGEAR RangeMax Wireless USB 2.0 Adapter WPN111.
Because this device isn't compatible with this version of Windows, and there are no solutions available for this problem, we recommend that you find another device on the Microsoft Compatibility website.
Click to go online to the Windows Hardware Compatibility Center"
However when I look at Device Manager my wireless network adapter (WPN111) the driver is digitally signed as a microsoft windows hardware compatibility publisher (netgear).
Go figure!!!
yea, i am/was/still in the same boat again PiMan. What happens here is, after an uninstall/delete of drivers, then a reboot, let windows install driver, seems to fix everything, no asterix, what seems like good connection and display of. But then do another reboot, and come back to desktop, and i'm back at square one again. Driver reports my usb adapter's usb location, reports the hardware Ids properly now, this didnt happen before when i was installing in comp mode. Even the driver is signed NOW by Microsoft Windows Hardware Compatibility Publisher. Which upon further review of other devices... all but one device, coincidently being the nvidia nforce network controller, is signed "Microsoft Windows Hardware Compatibility Publisher". The nforce is signed by "Microsoft Windows", 7 installed the driver for it as well, havent installed the drivers from nvidia at all yet. This somewhat puzzled me when i found this last night.
work in progress....
I went on Netgear website for latest drivers. Unfortunately the drivers aren't located individually. So I had to download then run whole setup/install for WPN111 adapter.
I then located driver files (mine were in c:\windows\system32\drivers\wpn111vx.sys) I then copied these drivers to folder elsewhere (I have hardware drivers folder in downloads in case of re-install issues).
Then I uninstalled the netgear setup wizard (actually ran setup again and it uninstalled). Then I removed adapter>rebooted then plugged adapter back in and if windows didn't locate driver I browsed towards my copy location (i.e. my hardware driver folders in downloads).
Adapter appears to work but with this stupid icon.
Hope this was useful.
PiMan
there is a way to extract the exe if you like... try this : Universal Extractor | LegRoom.net
Ok, for some testing purposes, is there any way you can put those drivers on a flash drive or something, and not have it connected to the pc after an uninstall/driver delete (everywhere)/reboot ? There's a method to my madness here.I then located driver files (mine were in c:\windows\system32\drivers\wpn111vx.sys) I then copied these drivers to folder elsewhere (I have hardware drivers folder in downloads in case of re-install issues).
Also, if you decide to do this, or even if not, try this -Pay attention to the specific driver for that device, name etc. go to explorer C:\windows\system32\drivers\yourdriver.sys- when you uinstall the adapter driver, either way- thru DM or uinstall programs and the driver is "deleted", tell me if you see it actually being deleted from that folder, in my case, it doesnt delete when i tell it to when uninstalling. This may be a bug i have found, need confirmation.
try opening up the DM before you pop in the adapter, and watch what goes on.
Then I uninstalled the netgear setup wizard (actually ran setup again and it uninstalled). Then I removed adapter>rebooted then plugged adapter back in and if windows didn't locate driver I browsed towards my copy location (i.e. my hardware driver folders in downloads).
Have you not had any D/C issues with that adapter along with the asterix? My situation has varied, no real pattern for me as some others have reported.Adapter appears to work but with this stupid icon.
Hope this was useful.
PiMan
But i think i have found another bug, need confirmation. From above when i ask you to try my little method of madness, try this, as it has worked, but i'm still testing it out to see if this is the problem/solution to just addressing the asterix problem, not actually a driver based problem. After you do the uninstall and totally delete, and during one of the repeated controlled field tests tries, after the driver installs go to your network and connect. Next, go to the properties of your connecting network. Connection Tab. Take out the checkmark for connect to network automatically.
Looking like this
Now, i did this after i D/C'd from the network while connected with the asterix showing still, then i rebooted. Then back to Desktop go to connect to my network (when usually/previously i never had to, since the checkmark. tho in 7000, this was not needed as i always auto connected and still do btw) and voila, manually connected and no asterix. But then i tested again, rebooted WHILE CONNECTED TO NETWORK, at desktop and asterix showing tho also reporting not connected - i manually connect and good stuff, no asterix. Do a double check, and notice that the adapter still pulls the same IP from the network. Therefore it wasnt an issue as the network wasnt allowing the release of the DHCP from the adapter or vice versa, and then if network/router was the problem, the adapter would have pulled a different IP.
so give this a shot, i believe it may cure your asterix woes. The ONLY PROBLEM with doing this is, in my case which i havent yet tested, but remoting into this pc from laptop with the pc on a cold boot, no active user accounts logged in - therefore not allowing the enabling/connecting manually to the network to get a connection. Therefore no RDP conn. So would have to go to the pc manually and fire up an account to have any connection to and from this pc. I also have the options were its used so when logging or switching back and forth between users it wont lose connection, like in XP. Nice feature that is... if only this problem was NOT around.
I don't really have the issues you mention above (don't have network just PC, mobile, router) so I couldn't comment, sorry.Managed to extract driver file without this but thanks.there is a way to extract the exe if you like... try this : Universal Extractor | LegRoom.net
Put driver files on microsd card and did as suggested.Ok, for some testing purposes, is there any way you can put those drivers on a flash drive or something, and not have it connected to the pc after an uninstall/driver delete (everywhere)/reboot ? There's a method to my madness here.
Upon uninsatll my driver file WPN111vx.sys was deleted from C:\windows\system32\drivers\ and network icon went from orange asterix to red X. I had DM open when uninstalling and WPN111 remained visible in DM until I unplugged adapter - as expected. Then rebooted from shutdown not restart.Also, if you decide to do this, or even if not, try this -Pay attention to the specific driver for that device, name etc. go to explorer C:\windows\system32\drivers\yourdriver.sys- when you uinstall the adapter driver, either way- thru DM or uinstall programs and the driver is "deleted", tell me if you see it actually being deleted from that folder, in my case, it doesnt delete when i tell it to when uninstalling. This may be a bug i have found, need confirmation.
Opened DM prior to adapter plug-in. Upon plug-in windows did not auto find driver (on microSD plugged in) and WPN111 appeared as "other device" until I browsed for driver to microSD location. Driver updated OK and WPN111 moved from other device to wireless network adapter - good. Also saw driver repopulate in C:\windows\system32\drivers\ .try opening up the DM before you pop in the adapter, and watch what goes on.
I have had intermittent D/C (if this means disconnections) from network with this adapter but it seems to improve stability with increased number of reboots (or I'm imagining it!). No real pattern before - i.e. heavy network traffic or anyhting.Have you not had any D/C issues with that adapter along with the asterix? My situation has varied, no real pattern for me as some others have reported.
Tried doing what you suggested above but had red X on network icon prior to connection and after connection also. Rebooted then had a orange* prior to connecting and afterwards as well.But i think i have found another bug, need confirmation. From above when i ask you to try my little method of madness, try this, as it has worked, but i'm still testing it out to see if this is the problem/solution to just addressing the asterix problem, not actually a driver based problem. After you do the uninstall and totally delete, and during one of the repeated controlled field tests tries, after the driver installs go to your network and connect. Next, go to the properties of your connecting network. Connection Tab. Take out the checkmark for connect to network automatically.
Not too sure how I check the IP address - do I go into my router settings and view from there or can I do it more easily from desktop?Looking like this
Now, i did this after i D/C'd from the network while connected with the asterix showing still, then i rebooted. Then back to Desktop go to connect to my network (when usually/previously i never had to, since the checkmark. tho in 7000, this was not needed as i always auto connected and still do btw) and voila, manually connected and no asterix. But then i tested again, rebooted WHILE CONNECTED TO NETWORK, at desktop and asterix showing tho also reporting not connected - i manually connect and good stuff, no asterix. Do a double check, and notice that the adapter still pulls the same IP from the network. Therefore it wasnt an issue as the network wasnt allowing the release of the DHCP from the adapter or vice versa, and then if network/router was the problem, the adapter would have pulled a different IP.
.so give this a shot, i believe it may cure your asterix woes. The ONLY PROBLEM with doing this is, in my case which i havent yet tested, but remoting into this pc from laptop with the pc on a cold boot, no active user accounts logged in - therefore not allowing the enabling/connecting manually to the network to get a connection. Therefore no RDP conn. So would have to go to the pc manually and fire up an account to have any connection to and from this pc. I also have the options were its used so when logging or switching back and forth between users it wont lose connection, like in XP. Nice feature that is... if only this problem was NOT around
Thanks for your pointers and if I find a dfinite workaround/fix I'll let you know.
Cheers
PiMan
Sorry Digger last post messy - not understood separating quotes like you did previously. I just hit quote and then typed in between.
no problem.. only thing tho, if you have a router, and a pc, technically you have a "network".... and by your typing if i understand correctly, you have a pc and a laptop, right? thats your network.
but anyhow, did you try to take out the checkmark in the picture i displayed ealier? I guess where it is, is the confusion you may have had. Two ways to get to this, i'll give you another way.
Control panel/ network and sharing center / manage wireless networks/
then highlight your network by left clicking once, the right clilck it, properties, and thats where that window i posted will be, hit the connections tab, take out the checkmark. Reboot, then manually connect to your network and let me know if that clears the asterix.
Quote
