Hi!...

I made my own Windows with nLite, but... for some reason when windows starts, the info balloon show me that there are networks detected, but when i open the Wireless Network manager doesnt show anything.

The router works fine, because i just installed an original Windows without mod, and works.

What services, or tweaks should i have to make the wireless work?....

- Wireless Zero Conf, works
- Wi-Fi Card Works
- Router works

Thanks!... (Sry for my english)

This post has been edited by Cain Mx: May 14 2008, 01:11 AM

Same thing here!

I'm using Windows XP pro SP3 Spanish with nLite 1.4.5 Final

That's a strange behabiour. I use nlite's tool for not autoremoving components (I select DHCP/Wireless) but this won't solve the problem.

I can't see any wireless network, all remaining services are autostarted (services.msc)

I attach my config file wishing It can help someway...

Thank you a lot!

Same issue here with an XP SP3 disc, using the exact same removed components as my SP2 disc that worked with nLite, is there a bug here?

I guess my solution for now is using a different app for managing wifi connections as for me anyway it is only the built in Windows app for managing wireless connections that tells me all access points are out of range

This post has been edited by iNFEKT: May 15 2008, 02:47 AM

Hi there!...

As i know, is that about Windows Services... I just disable some services in a XP SP2, and i had the same problem. So, i've restored the system and works again.

Now, i'm gonna disable again the services but i will take note about them. I'll see if a services is doing the problem.

EDIT:

Well, the error in XP SP2 was in EventLog Service, when i disable it, the Networks didn't show. And when i enable it, all works fine. But, in SP3 doesn't work.

I give up. Anyone can help us, please?...

Thanks!... (Sry for my english)

This post has been edited by Cain Mx: May 16 2008, 01:51 PM

Having the same problem

i have the same problem since last week; the list for "available wireless networks in range" kept being empty; after 3-4 nlites i ended up with a working and a non-working configurations; posting both of the configurations and the difference;


Non-Working:
 Last_Session__2008.05.19_00.04.30_.ini ( 30.96K ) Number of downloads: 8


Working:
 Last_Session__2008.05.19_01.31.34_.ini ( 29.15K ) Number of downloads: 13



Difference(removed components in the Non-Working config):

;# Network #
Client for Netware Networks
Communication tools
Comtrol Test Terminal Program
Connection Manager
FrontPage Extensions
H323 MSP
Internet Connection Wizard
Internet Information Services (IIS)
IP Conferencing
MSN Explorer
Netmeeting
Network Diagnostic
NWLink IPX/SPX/NetBIOS Protocol
Peer-to-Peer
Share Creation Wizard
Synchronization Manager
Vector Graphics Rendering (VML)
Web Folders
Windows Messenger
;# Services #
Alerter
Application Layer Gateway
Beep Driver
Distributed Link Tracking Client
Error Reporting
Extensible Authentication Protocol Service
Fax Service
Health Key and Certificate Management Service
IMAPI CD-Burning COM Service
Indexing Service
Messenger
Network Access Protection (NAP)
Network DDE
QoS RSVP
Quality of Service (QoS)
Remote Registry
Removable Storage
Route Listening Service
RPC Locator
Service Advertising Protocol
Simple TCP/IP Services
System Restore Service
Task Scheduler
Telnet
Uninterruptible Power Supply
Volume Shadow Copy
Windows Time
Wired AutoConfig


ONE or more of the above components/services is responsible(there is a dependency); hope someone can pin-point the cause(me just cant invest the time); my guess is, its one of the top components in "Network" section;

note: this is an SP3 issue(i read that in SP3 the wireless subsystem has been completely/partialy redone); never had this issue in SP2

This post has been edited by sarkash: May 18 2008, 08:07 PM

sarkash,

I bet it's the bottom one.

In order of suspiciousness:

Wired AutoConfig
Extensible Authentication Protocol Service
Health Key and Certificate Management Service
Network Access Protection (NAP)
Application Layer Gateway (if Windows Firewall is involved)
Route Listening Service (if router is involved; but very unlikely)

Nothing in # Network #.

But, knowing Microsoft, there might be a hidden dependency...

GL

Had this problem with wifi - everything seemed to be fine but can't see anything in network list and as a result can't connect.

hope this gets fixed soon

http://www.msfn.org/board/nLite-145-Final-...667#entry764667

Thanks Kirby, works like a charm

Actually that didn't solve anything, it stops on its own and is definitely dependant on more services than just those two. I put those services along with wireless zero on automatic startup and its still not working. Only way I can get it working in windows is put ALL services on automatic startup, and thats just excessive. I'm thinking about possibly just removing all the wireless services and using wifi hopper like everyone else?

This post has been edited by iNFEKT: May 24 2008, 01:41 AM

I use Wireless Network Ignition. Very simple and effective. It doesn't rely on Windows wireless component, it has its own protocol. So if you like researching you can even take default wifi protocol and a few files out of your disk too

I would suggest keeping service such as system event viewer and similar, as from the get-go you boot windows up until login till you have logged in windows gets updated on whats where. Also posting last session.ini's where 99% is removed, isnt helpful, it would be nice if people could remove all languages and keyboard information from them as its regardless not the culprit. I would check into Network diagnostic service, most because im curious of it, but seems new to me? im not sp3 however. not xp 32bit even.

http://support.microsoft.com/kb/949127

it contains a fixed file for sp3, too.
available via thehotfixshare

Oleg_II, thank you for posting this software. For a long time, I was searching for a wifi connection client that did not rely on existing Windows components.
Eventually, I found Wifi Hopper, a lightweight client that provides functionality far beyond the rather terribly built-in Windows XP client.

http://wifihopper.com/

Cheers,
James
x

Hi,

I am having the same problem. However, after installation, my wireless adapter could detect my network and connect without any problems. Recently, it just can't find any networks.

I tried using Belkin's utility to connect but it also fails to find any networks. I'm going to try the wifi-hopper mentioned here a bit later as well.

I think that the problem is not due to the Wired AutoConfig because I have it enabled... Is a reinstall the only other solution??

Hi!...

No fix yet?...

Take care!...