A Windows 98 & ME forum. Win98banter

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.

Go Back   Home » Win98banter forum » Windows ME » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

problem with Airlink adapter not always working



 
 
Thread Tools Display Modes
  #1  
Old January 22nd 09, 04:53 AM posted to microsoft.public.windowsme.general
Martin Murray
External Usenet User
 
Posts: 31
Default problem with Airlink adapter not always working

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


  #2  
Old January 22nd 09, 10:06 PM posted to microsoft.public.windowsme.general
Corday[_3_]
External Usenet User
 
Posts: 138
Default problem with Airlink adapter not always working

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



  #3  
Old January 25th 09, 07:33 PM posted to microsoft.public.windowsme.general
Martin Murray
External Usenet User
 
Posts: 31
Default problem with Airlink adapter not always working

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





  #4  
Old January 25th 09, 10:44 PM posted to microsoft.public.windowsme.general
Mart
External Usenet User
 
Posts: 1,190
Default problem with Airlink adapter not always working

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







  #5  
Old January 26th 09, 12:29 AM posted to microsoft.public.windowsme.general
Martin Murray
External Usenet User
 
Posts: 31
Default problem with Airlink adapter not always working

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









  #6  
Old January 26th 09, 01:05 AM posted to microsoft.public.windowsme.general
Mart
External Usenet User
 
Posts: 1,190
Default problem with Airlink adapter not always working

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











  #7  
Old January 26th 09, 01:17 AM posted to microsoft.public.windowsme.general
Corday[_3_]
External Usenet User
 
Posts: 138
Default problem with Airlink adapter not always working

There's a book for $30 or $40 that tells how. I wouldn't recommend tryng
unless you're really technically competent. If so, it's called:
Programming the Microsoft® Windows® Driver Model, Second Edition .
--
I mastered Wordstar graphics!


"Martin Murray" wrote:

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










  #8  
Old January 26th 09, 02:19 AM posted to microsoft.public.windowsme.general
Martin Murray
External Usenet User
 
Posts: 31
Default problem with Airlink adapter not always working

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













  #9  
Old January 26th 09, 10:01 AM posted to microsoft.public.windowsme.general
Mart
External Usenet User
 
Posts: 1,190
Default problem with Airlink adapter not always working

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



  #10  
Old January 28th 09, 05:10 PM posted to microsoft.public.windowsme.general
Martin Murray
External Usenet User
 
Posts: 31
Default problem with Airlink adapter not always working

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

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

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 02:24 AM
Maxtor dual video adapter not working Sabo, Eric General 6 December 7th 04 10:01 PM
Maxtor dual video adapter not working Sabo, Eric Setup & Installation 2 December 7th 04 10:01 PM


All times are GMT +1. The time now is 11:28 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.