If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
problem with Airlink adapter not always working
Check Device Manager for conflict.
-- I mastered Wordstar graphics! "Martin Murray" wrote: Well, the old router is dead dead dead. Hence the new router. Another interesting point I've found out is this: Prevent the adapter software from starting up by removing it from the Startup folder. Then run the software AFTER BOOT and the adapter seems to work fine. So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. Martin "Mart" wrote in message ... Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. but is is really only the change in router as far as I know. I would suggest substituting the old router and seeing if the problem goes, is probably your best 'proof' of that hypothesis. Mart "Martin Murray" wrote in message ... I think all 4 of the ports are 2.0, but have tried them all with the same results. Really, the more I think about it now the more likely it seems that something is forcing the adapter to restart after boot. I wish I could say something in the system had changed quite a bit to coincide with this issue, but is is really only the change in router as far as I know. "Mart" wrote in message ... Personally? No. BUT - There's plenty of stuff out there. Try Google or the KB for "order of loading drivers" e.g. http://support.microsoft.com/kb/133159 In the meantime, I would be interested in a couple of answers to the questions I previously posed regarding your motherboard and USB options (!.0 or 2.0). Also, how many ports?. Have you tried other ports? I have no solutions but it might help others with ideas. I have a WinMe desktop set up running here with an EDIMAX PCI -Wifi card without any trouble at all - worth considering? http://www.edimax.com/en/produce_det...id=1&pl2_id=44 Mart "Martin Murray" wrote in message ... Definitely an interesting idea about the timing of the initialization. Any ideas how I would change the order or timing of the loading of the drivers? "Mart" wrote in message ... Some 18 months or so ago, the MS Knowledge Base pointed to a dead link concerning USB2.0 - Wifi Adapter issues with WinMe but it finally got pulled before it was ever fixed and I never did manage to find out any details. That said, I had similar issues with a USB 2.0 Wifi stick (Siemens Gigaset USB Adapter 108) on a couple of different laptops which only had single USB1.0 ports. In each case, I fitted completely different unbranded 'generic' 4 port PCMCIA (Cardbus) USB2.0 cards. One always worked correctly and the other displayed similar symptoms to yours. Both cards worked normally with other USB devices but one didn't like the USB2.0 Wifi adapter. I ended up using the USB1.0 port for the Wifi stick as it was more (but not totally) reliable. My guess - and it is only a guess - is that there was a timing issue which occurred whilst WinMe was attempting to enumerate hardware during bootup in readiness to load the two appropriate drivers (PCMCIA followed by the USB Wifi Adapter). Your 'workaround' of disabling/enabling the adapter on a 'hot' pc (i.e. powered-up and actually running WinMe) would add a bit more weight to the theory. Extract form MSN Technet article:- Wireless LAN Support in Windows: Frequently Asked Questions http://www.microsoft.com/technet/net...faq.mspx#E3BAE snip " Q. What wireless support is built into Windows Me, Windows 98, and Windows NT 4.0? A. There is no built-in wireless LAN support in Windows Me, Windows 98, or Windows NT 4.0. Wireless network adapter manufacturers must supply all wireless and authentication functionality for these versions of Windows. To configure a wireless client computer running Windows Me, Windows 98, or Windows NT 4.0, you must use the wireless configuration tool provided by your wireless network adapter manufacturer. Please see the instructions for the wireless configuration tool to configure 802.11 and 802.1X authentication settings. /snip So MS suggest it's not so much a WinMe issue but more likely it could be due to 3rd party drivers. A trawl around Google also suggests that WinMe and USB2.0 Wifi is not an exact science. Try Airlink Tech Support. Just a thought, are your USB ports native to your motherboard and are they USB2.0? If so, they will require separate drivers supplied with your computer. USB2.0 is not supported/supplied with WinMe. You could perhaps substitute a PCI - Wifi card instead of USB if all else fails. Mart "Martin Murray" wrote in message ... Thanks for the reply. I don't think distance is the problem and the USB adapter itself seems ok. I say this because the best workaround I have recently found is to disable then re-enable the adapter. 99% of the time, it comes back on, connects and stays connected after that, until the next reboot. It is really just the startup connection process that seems to have a real problem. That is when the systray icon appears, then disappears. That is new behavior, as I indicated. I have tried power cycling the router but the problem persists. "Corday" wrote in message ... Quickest guess is unit is too far from router. Also other units on the network might be interfearing. Try turning off and restarting router and maybe reentering data including a password change. The router manufacturer and or your ISP Tech might help, but as soon as you mention Windows ME they shy away. Finally, test adapter on another unit. I assume USB is OK for other functions plugged into it. -- I mastered Wordstar graphics! "Martin Murray" wrote: Products: Compaq destktop running Windows Me, Airlink USB wireless LAN adaptor Symptoms: Upon reboot the network adaptor will not always function correctly. The systray icon showing the connection appears, then disappears, then reappears. Connection to the network shows to be working, but no internet connection is functioning. The problem is solved by repeated reboots and/or by unplugging and replugging the adaptor in the USB slot. Then internet functions normally. Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. The network settings are correctly specified in the TCP/IP settings (DHCP, correct DNS Gateway, etc.) and it does function eventually, as indicated above. Could the new router be causing these issues by a newer protocol or something like that? Ideas? Thanks in advance, Martin Murray |
#12
|
|||
|
|||
problem with Airlink adapter not always working
So, what would cause it to start - then stop
- then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. I guess you mean MORE ideas? OK, lets try a different tack - although it does follow-on from a *possible* timing issue I suggested earlier. A messy task but *might* shed some light. It involves the bootlog.txt file and possibly the bootlog.prv files in the root folder. Both files are text files which can be read with a text reader such as notepad etc. Also see "Load Failures Listed in the Bootlog.txt File" for background. http://support.microsoft.com/default...b;en-us;127970 Although you might be able to manage by just using a text reader, you will probably find the (very) old 'Bootlog Analyzer' Freeware utility invaluable. Still available from :- http://dspace.dial.pipex.com/town/terrace/pk29/ NB - It also works with WinMe, in spite of what it says on the page. It may take a bit of interpreting, but you should soon get the hang of it - see also their note. BTW - to call the boot logging switch, press and hold the Ctrl key at each boot to see the boot menu. Select the log option (2) to refresh or update the bootlog.txt file. You are likely to have to undertake several re-boots and hope you eventually get the two conditions where the 'fault' is on and again where the 'fault is off - and therefore a bunch of experimenting. It might also be worth having a play with the Step-by-Step option (4) to see if that gives you any clues. Should keep you busy for a while during these dark winter nights! Good luck. Mart "Martin Murray" wrote in message ... Well, the old router is dead dead dead. Hence the new router. Another interesting point I've found out is this: Prevent the adapter software from starting up by removing it from the Startup folder. Then run the software AFTER BOOT and the adapter seems to work fine. So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. Martin "Mart" wrote in message ... Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. but is is really only the change in router as far as I know. I would suggest substituting the old router and seeing if the problem goes, is probably your best 'proof' of that hypothesis. Mart "Martin Murray" wrote in message ... I think all 4 of the ports are 2.0, but have tried them all with the same results. Really, the more I think about it now the more likely it seems that something is forcing the adapter to restart after boot. I wish I could say something in the system had changed quite a bit to coincide with this issue, but is is really only the change in router as far as I know. "Mart" wrote in message ... Personally? No. BUT - There's plenty of stuff out there. Try Google or the KB for "order of loading drivers" e.g. http://support.microsoft.com/kb/133159 In the meantime, I would be interested in a couple of answers to the questions I previously posed regarding your motherboard and USB options (!.0 or 2.0). Also, how many ports?. Have you tried other ports? I have no solutions but it might help others with ideas. I have a WinMe desktop set up running here with an EDIMAX PCI -Wifi card without any trouble at all - worth considering? http://www.edimax.com/en/produce_det...id=1&pl2_id=44 Mart "Martin Murray" wrote in message ... Definitely an interesting idea about the timing of the initialization. Any ideas how I would change the order or timing of the loading of the drivers? "Mart" wrote in message ... Some 18 months or so ago, the MS Knowledge Base pointed to a dead link concerning USB2.0 - Wifi Adapter issues with WinMe but it finally got pulled before it was ever fixed and I never did manage to find out any details. That said, I had similar issues with a USB 2.0 Wifi stick (Siemens Gigaset USB Adapter 108) on a couple of different laptops which only had single USB1.0 ports. In each case, I fitted completely different unbranded 'generic' 4 port PCMCIA (Cardbus) USB2.0 cards. One always worked correctly and the other displayed similar symptoms to yours. Both cards worked normally with other USB devices but one didn't like the USB2.0 Wifi adapter. I ended up using the USB1.0 port for the Wifi stick as it was more (but not totally) reliable. My guess - and it is only a guess - is that there was a timing issue which occurred whilst WinMe was attempting to enumerate hardware during bootup in readiness to load the two appropriate drivers (PCMCIA followed by the USB Wifi Adapter). Your 'workaround' of disabling/enabling the adapter on a 'hot' pc (i.e. powered-up and actually running WinMe) would add a bit more weight to the theory. Extract form MSN Technet article:- Wireless LAN Support in Windows: Frequently Asked Questions http://www.microsoft.com/technet/net...faq.mspx#E3BAE snip " Q. What wireless support is built into Windows Me, Windows 98, and Windows NT 4.0? A. There is no built-in wireless LAN support in Windows Me, Windows 98, or Windows NT 4.0. Wireless network adapter manufacturers must supply all wireless and authentication functionality for these versions of Windows. To configure a wireless client computer running Windows Me, Windows 98, or Windows NT 4.0, you must use the wireless configuration tool provided by your wireless network adapter manufacturer. Please see the instructions for the wireless configuration tool to configure 802.11 and 802.1X authentication settings. /snip So MS suggest it's not so much a WinMe issue but more likely it could be due to 3rd party drivers. A trawl around Google also suggests that WinMe and USB2.0 Wifi is not an exact science. Try Airlink Tech Support. Just a thought, are your USB ports native to your motherboard and are they USB2.0? If so, they will require separate drivers supplied with your computer. USB2.0 is not supported/supplied with WinMe. You could perhaps substitute a PCI - Wifi card instead of USB if all else fails. Mart "Martin Murray" wrote in message ... Thanks for the reply. I don't think distance is the problem and the USB adapter itself seems ok. I say this because the best workaround I have recently found is to disable then re-enable the adapter. 99% of the time, it comes back on, connects and stays connected after that, until the next reboot. It is really just the startup connection process that seems to have a real problem. That is when the systray icon appears, then disappears. That is new behavior, as I indicated. I have tried power cycling the router but the problem persists. "Corday" wrote in message ... Quickest guess is unit is too far from router. Also other units on the network might be interfearing. Try turning off and restarting router and maybe reentering data including a password change. The router manufacturer and or your ISP Tech might help, but as soon as you mention Windows ME they shy away. Finally, test adapter on another unit. I assume USB is OK for other functions plugged into it. -- I mastered Wordstar graphics! "Martin Murray" wrote: Products: Compaq destktop running Windows Me, Airlink USB wireless LAN adaptor Symptoms: Upon reboot the network adaptor will not always function correctly. The systray icon showing the connection appears, then disappears, then reappears. Connection to the network shows to be working, but no internet connection is functioning. The problem is solved by repeated reboots and/or by unplugging and replugging the adaptor in the USB slot. Then internet functions normally. Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. The network settings are correctly specified in the TCP/IP settings (DHCP, correct DNS Gateway, etc.) and it does function eventually, as indicated above. Could the new router be causing these issues by a newer protocol or something like that? Ideas? Thanks in advance, Martin Murray |
#13
|
|||
|
|||
problem with Airlink adapter not always working
No conflicts, but thanks.
"Corday" wrote in message ... Check Device Manager for conflict. -- I mastered Wordstar graphics! "Martin Murray" wrote: Well, the old router is dead dead dead. Hence the new router. Another interesting point I've found out is this: Prevent the adapter software from starting up by removing it from the Startup folder. Then run the software AFTER BOOT and the adapter seems to work fine. So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. Martin "Mart" wrote in message ... Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. but is is really only the change in router as far as I know. I would suggest substituting the old router and seeing if the problem goes, is probably your best 'proof' of that hypothesis. Mart "Martin Murray" wrote in message ... I think all 4 of the ports are 2.0, but have tried them all with the same results. Really, the more I think about it now the more likely it seems that something is forcing the adapter to restart after boot. I wish I could say something in the system had changed quite a bit to coincide with this issue, but is is really only the change in router as far as I know. "Mart" wrote in message ... Personally? No. BUT - There's plenty of stuff out there. Try or the KB for "order of loading drivers" e.g. http://support.microsoft.com/kb/133159 In the meantime, I would be interested in a couple of answers to the questions I previously posed regarding your motherboard and USB options (!.0 or 2.0). Also, how many ports?. Have you tried other ports? I have no solutions but it might help others with ideas. I have a WinMe desktop set up running here with an EDIMAX PCI -Wifi card without any trouble at all - worth considering? http://www.edimax.com/en/produce_det...id=1&pl2_id=44 Mart "Martin Murray" wrote in message ... Definitely an interesting idea about the timing of the initialization. Any ideas how I would change the order or timing of the loading of the drivers? "Mart" wrote in message ... Some 18 months or so ago, the MS Knowledge Base pointed to a dead link concerning USB2.0 - Wifi Adapter issues with WinMe but it finally got pulled before it was ever fixed and I never did manage to find out any details. That said, I had similar issues with a USB 2.0 Wifi stick (Siemens Gigaset USB Adapter 108) on a couple of different laptops which only had single USB1.0 ports. In each case, I fitted completely different unbranded 'generic' 4 port PCMCIA (Cardbus) USB2.0 cards. One always worked correctly and the other displayed similar symptoms to yours. Both cards worked normally with other USB devices but one didn't like the USB2.0 Wifi adapter. I ended up using the USB1.0 port for the Wifi stick as it was more (but not totally) reliable. My guess - and it is only a guess - is that there was a timing issue which occurred whilst WinMe was attempting to enumerate hardware during bootup in readiness to load the two appropriate drivers (PCMCIA followed by the USB Wifi Adapter). Your 'workaround' of disabling/enabling the adapter on a 'hot' pc (i.e. powered-up and actually running WinMe) would add a bit more weight to the theory. Extract form MSN Technet article:- Wireless LAN Support in Windows: Frequently Asked Questions http://www.microsoft.com/technet/net...faq.mspx#E3BAE snip " Q. What wireless support is built into Windows Me, Windows 98, and Windows NT 4.0? A. There is no built-in wireless LAN support in Windows Me, Windows 98, or Windows NT 4.0. Wireless network adapter manufacturers must supply all wireless and authentication functionality for these versions of Windows. To configure a wireless client computer running Windows Me, Windows 98, or Windows NT 4.0, you must use the wireless configuration tool provided by your wireless network adapter manufacturer. Please see the instructions for the wireless configuration tool to configure 802.11 and 802.1X authentication settings. /snip So MS suggest it's not so much a WinMe issue but more likely it could be due to 3rd party drivers. A trawl around Google also suggests that WinMe and USB2.0 Wifi is not an exact science. Try Airlink Tech Support. Just a thought, are your USB ports native to your motherboard and are they USB2.0? If so, they will require separate drivers supplied with your computer. USB2.0 is not supported/supplied with WinMe. You could perhaps substitute a PCI - Wifi card instead of USB if all else fails. Mart "Martin Murray" wrote in message ... Thanks for the reply. I don't think distance is the problem and the USB adapter itself seems ok. I say this because the best workaround I have recently found is to disable then re-enable the adapter. 99% of the time, it comes back on, connects and stays connected after that, until the next reboot. It is really just the startup connection process that seems to have a real problem. That is when the systray icon appears, then disappears. That is new behavior, as I indicated. I have tried power cycling the router but the problem persists. "Corday" wrote in message ... Quickest guess is unit is too far from router. Also other units on the network might be interfearing. Try turning off and restarting router and maybe reentering data including a password change. The router manufacturer and or your ISP Tech might help, but as soon as you mention Windows ME they shy away. Finally, test adapter on another unit. I assume USB is OK for other functions plugged into it. -- I mastered Wordstar graphics! "Martin Murray" wrote: Products: Compaq destktop running Windows Me, Airlink USB wireless LAN adaptor Symptoms: Upon reboot the network adaptor will not always function correctly. The systray icon showing the connection appears, then disappears, then reappears. Connection to the network shows to be working, but no internet connection is functioning. The problem is solved by repeated reboots and/or by unplugging and replugging the adaptor in the USB slot. Then internet functions normally. Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. The network settings are correctly specified in the TCP/IP settings (DHCP, correct DNS Gateway, etc.) and it does function eventually, as indicated above. Could the new router be causing these issues by a newer protocol or something like that? Ideas? Thanks in advance, Martin Murray |
#14
|
|||
|
|||
problem with Airlink adapter not always working
OK, thanks for the detailed response. I'll look at it.
I guess at this point I'll probably drop the quest. The issue is an irritant, but manageable. Thanks again for all your help. "Mart" wrote in message ... So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. I guess you mean MORE ideas? OK, lets try a different tack - although it does follow-on from a *possible* timing issue I suggested earlier. A messy task but *might* shed some light. It involves the bootlog.txt file and possibly the bootlog.prv files in the root folder. Both files are text files which can be read with a text reader such as notepad etc. Also see "Load Failures Listed in the Bootlog.txt File" for background. http://support.microsoft.com/default...b;en-us;127970 Although you might be able to manage by just using a text reader, you will probably find the (very) old 'Bootlog Analyzer' Freeware utility invaluable. Still available from :- http://dspace.dial.pipex.com/town/terrace/pk29/ NB - It also works with WinMe, in spite of what it says on the page. It may take a bit of interpreting, but you should soon get the hang of it - see also their note. BTW - to call the boot logging switch, press and hold the Ctrl key at each boot to see the boot menu. Select the log option (2) to refresh or update the bootlog.txt file. You are likely to have to undertake several re-boots and hope you eventually get the two conditions where the 'fault' is on and again where the 'fault is off - and therefore a bunch of experimenting. It might also be worth having a play with the Step-by-Step option (4) to see if that gives you any clues. Should keep you busy for a while during these dark winter nights! Good luck. Mart "Martin Murray" wrote in message ... Well, the old router is dead dead dead. Hence the new router. Another interesting point I've found out is this: Prevent the adapter software from starting up by removing it from the Startup folder. Then run the software AFTER BOOT and the adapter seems to work fine. So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. Martin "Mart" wrote in message ... Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. but is is really only the change in router as far as I know. I would suggest substituting the old router and seeing if the problem goes, is probably your best 'proof' of that hypothesis. Mart "Martin Murray" wrote in message ... I think all 4 of the ports are 2.0, but have tried them all with the same results. Really, the more I think about it now the more likely it seems that something is forcing the adapter to restart after boot. I wish I could say something in the system had changed quite a bit to coincide with this issue, but is is really only the change in router as far as I know. "Mart" wrote in message ... Personally? No. BUT - There's plenty of stuff out there. Try Google or the KB for "order of loading drivers" e.g. http://support.microsoft.com/kb/133159 In the meantime, I would be interested in a couple of answers to the questions I previously posed regarding your motherboard and USB options (!.0 or 2.0). Also, how many ports?. Have you tried other ports? I have no solutions but it might help others with ideas. I have a WinMe desktop set up running here with an EDIMAX PCI -Wifi card without any trouble at all - worth considering? http://www.edimax.com/en/produce_det...id=1&pl2_id=44 Mart "Martin Murray" wrote in message ... Definitely an interesting idea about the timing of the initialization. Any ideas how I would change the order or timing of the loading of the drivers? "Mart" wrote in message ... Some 18 months or so ago, the MS Knowledge Base pointed to a dead link concerning USB2.0 - Wifi Adapter issues with WinMe but it finally got pulled before it was ever fixed and I never did manage to find out any details. That said, I had similar issues with a USB 2.0 Wifi stick (Siemens Gigaset USB Adapter 108) on a couple of different laptops which only had single USB1.0 ports. In each case, I fitted completely different unbranded 'generic' 4 port PCMCIA (Cardbus) USB2.0 cards. One always worked correctly and the other displayed similar symptoms to yours. Both cards worked normally with other USB devices but one didn't like the USB2.0 Wifi adapter. I ended up using the USB1.0 port for the Wifi stick as it was more (but not totally) reliable. My guess - and it is only a guess - is that there was a timing issue which occurred whilst WinMe was attempting to enumerate hardware during bootup in readiness to load the two appropriate drivers (PCMCIA followed by the USB Wifi Adapter). Your 'workaround' of disabling/enabling the adapter on a 'hot' pc (i.e. powered-up and actually running WinMe) would add a bit more weight to the theory. Extract form MSN Technet article:- Wireless LAN Support in Windows: Frequently Asked Questions http://www.microsoft.com/technet/net...faq.mspx#E3BAE snip " Q. What wireless support is built into Windows Me, Windows 98, and Windows NT 4.0? A. There is no built-in wireless LAN support in Windows Me, Windows 98, or Windows NT 4.0. Wireless network adapter manufacturers must supply all wireless and authentication functionality for these versions of Windows. To configure a wireless client computer running Windows Me, Windows 98, or Windows NT 4.0, you must use the wireless configuration tool provided by your wireless network adapter manufacturer. Please see the instructions for the wireless configuration tool to configure 802.11 and 802.1X authentication settings. /snip So MS suggest it's not so much a WinMe issue but more likely it could be due to 3rd party drivers. A trawl around Google also suggests that WinMe and USB2.0 Wifi is not an exact science. Try Airlink Tech Support. Just a thought, are your USB ports native to your motherboard and are they USB2.0? If so, they will require separate drivers supplied with your computer. USB2.0 is not supported/supplied with WinMe. You could perhaps substitute a PCI - Wifi card instead of USB if all else fails. Mart "Martin Murray" wrote in message ... Thanks for the reply. I don't think distance is the problem and the USB adapter itself seems ok. I say this because the best workaround I have recently found is to disable then re-enable the adapter. 99% of the time, it comes back on, connects and stays connected after that, until the next reboot. It is really just the startup connection process that seems to have a real problem. That is when the systray icon appears, then disappears. That is new behavior, as I indicated. I have tried power cycling the router but the problem persists. "Corday" wrote in message ... Quickest guess is unit is too far from router. Also other units on the network might be interfearing. Try turning off and restarting router and maybe reentering data including a password change. The router manufacturer and or your ISP Tech might help, but as soon as you mention Windows ME they shy away. Finally, test adapter on another unit. I assume USB is OK for other functions plugged into it. -- I mastered Wordstar graphics! "Martin Murray" wrote: Products: Compaq destktop running Windows Me, Airlink USB wireless LAN adaptor Symptoms: Upon reboot the network adaptor will not always function correctly. The systray icon showing the connection appears, then disappears, then reappears. Connection to the network shows to be working, but no internet connection is functioning. The problem is solved by repeated reboots and/or by unplugging and replugging the adaptor in the USB slot. Then internet functions normally. Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. The network settings are correctly specified in the TCP/IP settings (DHCP, correct DNS Gateway, etc.) and it does function eventually, as indicated above. Could the new router be causing these issues by a newer protocol or something like that? Ideas? Thanks in advance, Martin Murray |
#15
|
|||
|
|||
problem with Airlink adapter not always working
YW
Mart "Martin Murray" wrote in message ... OK, thanks for the detailed response. I'll look at it. I guess at this point I'll probably drop the quest. The issue is an irritant, but manageable. Thanks again for all your help. "Mart" wrote in message ... So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. I guess you mean MORE ideas? OK, lets try a different tack - although it does follow-on from a *possible* timing issue I suggested earlier. A messy task but *might* shed some light. It involves the bootlog.txt file and possibly the bootlog.prv files in the root folder. Both files are text files which can be read with a text reader such as notepad etc. Also see "Load Failures Listed in the Bootlog.txt File" for background. http://support.microsoft.com/default...b;en-us;127970 Although you might be able to manage by just using a text reader, you will probably find the (very) old 'Bootlog Analyzer' Freeware utility invaluable. Still available from :- http://dspace.dial.pipex.com/town/terrace/pk29/ NB - It also works with WinMe, in spite of what it says on the page. It may take a bit of interpreting, but you should soon get the hang of it - see also their note. BTW - to call the boot logging switch, press and hold the Ctrl key at each boot to see the boot menu. Select the log option (2) to refresh or update the bootlog.txt file. You are likely to have to undertake several re-boots and hope you eventually get the two conditions where the 'fault' is on and again where the 'fault is off - and therefore a bunch of experimenting. It might also be worth having a play with the Step-by-Step option (4) to see if that gives you any clues. Should keep you busy for a while during these dark winter nights! Good luck. Mart "Martin Murray" wrote in message ... Well, the old router is dead dead dead. Hence the new router. Another interesting point I've found out is this: Prevent the adapter software from starting up by removing it from the Startup folder. Then run the software AFTER BOOT and the adapter seems to work fine. So, what would cause it to start - then stop - then start and not connect? But when it starts only once in the calmer environment after boot, it works? Would love any ideas! Thanks again. Martin "Mart" wrote in message ... Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. but is is really only the change in router as far as I know. I would suggest substituting the old router and seeing if the problem goes, is probably your best 'proof' of that hypothesis. Mart "Martin Murray" wrote in message ... I think all 4 of the ports are 2.0, but have tried them all with the same results. Really, the more I think about it now the more likely it seems that something is forcing the adapter to restart after boot. I wish I could say something in the system had changed quite a bit to coincide with this issue, but is is really only the change in router as far as I know. "Mart" wrote in message ... Personally? No. BUT - There's plenty of stuff out there. Try Google or the KB for "order of loading drivers" e.g. http://support.microsoft.com/kb/133159 In the meantime, I would be interested in a couple of answers to the questions I previously posed regarding your motherboard and USB options (!.0 or 2.0). Also, how many ports?. Have you tried other ports? I have no solutions but it might help others with ideas. I have a WinMe desktop set up running here with an EDIMAX PCI -Wifi card without any trouble at all - worth considering? http://www.edimax.com/en/produce_det...id=1&pl2_id=44 Mart "Martin Murray" wrote in message ... Definitely an interesting idea about the timing of the initialization. Any ideas how I would change the order or timing of the loading of the drivers? "Mart" wrote in message ... Some 18 months or so ago, the MS Knowledge Base pointed to a dead link concerning USB2.0 - Wifi Adapter issues with WinMe but it finally got pulled before it was ever fixed and I never did manage to find out any details. That said, I had similar issues with a USB 2.0 Wifi stick (Siemens Gigaset USB Adapter 108) on a couple of different laptops which only had single USB1.0 ports. In each case, I fitted completely different unbranded 'generic' 4 port PCMCIA (Cardbus) USB2.0 cards. One always worked correctly and the other displayed similar symptoms to yours. Both cards worked normally with other USB devices but one didn't like the USB2.0 Wifi adapter. I ended up using the USB1.0 port for the Wifi stick as it was more (but not totally) reliable. My guess - and it is only a guess - is that there was a timing issue which occurred whilst WinMe was attempting to enumerate hardware during bootup in readiness to load the two appropriate drivers (PCMCIA followed by the USB Wifi Adapter). Your 'workaround' of disabling/enabling the adapter on a 'hot' pc (i.e. powered-up and actually running WinMe) would add a bit more weight to the theory. Extract form MSN Technet article:- Wireless LAN Support in Windows: Frequently Asked Questions http://www.microsoft.com/technet/net...faq.mspx#E3BAE snip " Q. What wireless support is built into Windows Me, Windows 98, and Windows NT 4.0? A. There is no built-in wireless LAN support in Windows Me, Windows 98, or Windows NT 4.0. Wireless network adapter manufacturers must supply all wireless and authentication functionality for these versions of Windows. To configure a wireless client computer running Windows Me, Windows 98, or Windows NT 4.0, you must use the wireless configuration tool provided by your wireless network adapter manufacturer. Please see the instructions for the wireless configuration tool to configure 802.11 and 802.1X authentication settings. /snip So MS suggest it's not so much a WinMe issue but more likely it could be due to 3rd party drivers. A trawl around Google also suggests that WinMe and USB2.0 Wifi is not an exact science. Try Airlink Tech Support. Just a thought, are your USB ports native to your motherboard and are they USB2.0? If so, they will require separate drivers supplied with your computer. USB2.0 is not supported/supplied with WinMe. You could perhaps substitute a PCI - Wifi card instead of USB if all else fails. Mart "Martin Murray" wrote in message ... Thanks for the reply. I don't think distance is the problem and the USB adapter itself seems ok. I say this because the best workaround I have recently found is to disable then re-enable the adapter. 99% of the time, it comes back on, connects and stays connected after that, until the next reboot. It is really just the startup connection process that seems to have a real problem. That is when the systray icon appears, then disappears. That is new behavior, as I indicated. I have tried power cycling the router but the problem persists. "Corday" wrote in message ... Quickest guess is unit is too far from router. Also other units on the network might be interfearing. Try turning off and restarting router and maybe reentering data including a password change. The router manufacturer and or your ISP Tech might help, but as soon as you mention Windows ME they shy away. Finally, test adapter on another unit. I assume USB is OK for other functions plugged into it. -- I mastered Wordstar graphics! "Martin Murray" wrote: Products: Compaq destktop running Windows Me, Airlink USB wireless LAN adaptor Symptoms: Upon reboot the network adaptor will not always function correctly. The systray icon showing the connection appears, then disappears, then reappears. Connection to the network shows to be working, but no internet connection is functioning. The problem is solved by repeated reboots and/or by unplugging and replugging the adaptor in the USB slot. Then internet functions normally. Facts: The start of the problem seems to have been at the same time a new router was introduced into the network. The network settings are correctly specified in the TCP/IP settings (DHCP, correct DNS Gateway, etc.) and it does function eventually, as indicated above. Could the new router be causing these issues by a newer protocol or something like that? Ideas? Thanks in advance, Martin Murray |
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Linksys wireless adapter stopped working | [email protected] | Internet | 1 | August 13th 08 04:21 AM |
Video Adapter on Dell Inspiron Laptop stopped working | BobT | General | 3 | September 22nd 07 04:32 AM |
3com lan adapter working but connection manager can't see it?? | DR | Networking | 2 | January 4th 05 01:24 AM |
Maxtor dual video adapter not working | Sabo, Eric | General | 6 | December 7th 04 09:01 PM |
Maxtor dual video adapter not working | Sabo, Eric | Setup & Installation | 2 | December 7th 04 09:01 PM |