Jump to content
|Topic||Stats||Last action by|
|Microsoft now rolling out Windows Phone 8.1 Update 1 for Lumia 930||
|printer madness with OS X clients in multi-OS environment||
|iPhone 6 reputedly bending when stored in front pockets||
|Anyone buying a PS TV when it becomes available in their region?||
|Valve rolls out major Steam redesign||
Posted 03 August 2013 - 12:57
Posted 03 August 2013 - 13:12
Posted 04 August 2013 - 08:21
Posted 04 August 2013 - 11:45
Posted 04 August 2013 - 12:11
Posted 04 August 2013 - 12:17
Posted 04 August 2013 - 12:51
Posted 04 August 2013 - 13:10
Posted 04 August 2013 - 19:01
Posted 04 August 2013 - 19:24
Posted 04 August 2013 - 20:04
It will be stuck in ad-hoc mode at driver level to let it talk to the DS. Change it back or reinstall the driver - which ever you prefer.
Posted 04 August 2013 - 20:12
Posted 04 August 2013 - 20:21
I would imagine that he's likely seeing the existing home network wireless connection but I have seen devices that will show both ad-hoc and infrastructure connections despite only being able to connect to ad-hoc connections.
I've only ever used one before for the original DSLite - it placed the USB device into 802.11b / ad-hoc then allows you to "pair" it with a DS to get the DS onto the Nintendo network. To my knowledge you can just restore the driver settings to get it back to normal or reinstall the driver.
Posted 04 August 2013 - 20:27
Are you certain you are configuring the right network adapter? From the window in your first shot, can you post a pic of the "Change Adapter Setttings" window?