CAN'T INSTALL BELKIN NIC DRIVERS

Thanks MEB. I really wanted some substance & confirmation that I was doing
the right thing before tackling Belkin. On my post you quoted below, I'm
afraid that what I said was indeed the case, the drivers were listed
correctly as confirmed in Properties for the adapter in Device Manager, as
was the name of the NIC, albeit with a yellow exclamation mark. I apologize
for any ambiguity but I try to be as accurate as possible. I also respect
your comments as to the quality of Belkin NIC's... if the worse happens, then
maybe a Netgear would be better?

I really appreciate the work that you guys on these forums do, giving up
your time presumably freely, to help out us D-I-Y'ers from all over the
world. I think you're stars and need suitable recognition for it. I guess
this is the end of the thread, so with that, many, many thanks.

Best regards,

Sandy.


"MEB" wrote:
> Could very well be, but I'm not sure why it would.. having tried the
> corrections [and you have tried them all apparently] I would go more for a
> bad adapter.
> Searching Google for that particular model [ec] only turns up this
> discussion... winipcfg showing nothing is not good... and the Belkin
> software also unable to find it really is not good. But it doesn't matter,
> if you bought the card, and contacted Belkin concerning it shortly after
> purchase, then you have the material [the contacts] to request a replacement
> from Belkin. Another possibility: If the purchase was recent enough, try to
> return it to the store where purchased.
>
> Uhm, however, let's get this straight, you posted:
> "OK some success. After going through the procedures we spoke about last
> week over the week-end, yes the NIC is now recognized properly, yes the
> drivers finally loaded successfully, but no, Windows says "there is a
> problem
> with my NIC" on restart go & "run the troubleshooter"! As if I didn't do
> that in the first place!"
>
> So in actuality, that wasn't correct, right [sorry we can only work with
> what you present us] the NIC wasn't properly installed/recognized and the
> drivers didn't load properly. Just a correction, as these posts are
> referenced by others.
>
> As you have spent a large amount of time, I would re-contact Belkin and
> tell them you need a new card [you have tried everything, have contacted
> them, and the card does NOT work]. If you have another card around or can
> borrow one, try that to see if it connects. Then you can point this out to
> Belkin as well.
>
> BTW: going through and beyond the first few pages Google shows, does turn up
> some rather poor ratings for that adapter.


> "Sandy" <(E-Mail Removed)> wrote in message
> news:B611B714-3730-437C-B0C5-(E-Mail Removed)...
> | MEB, Gary,
> |
> | Right, I've revisited some of the points made earlier. I actually have
> the
> | modem/router in my property which my son & I setup together, inputting all
> | the MAC addresses of all PC's & security settings - reasonably
> | straightforward on an Netgear and works well. I ran winipcfg and noted my
> | wireless adapter not even listed so there was no point in going any
> further
> | with that one. I checked with Belkin for any firmware revisions but, as
> | suspected, there's no flash 'bios' as such on the card... all done through
> | inf. & sys. files in the installation software.
> |
> | Which brings me onto Gary's point. I've now retried versions 1 through 3
> of
> | the Belkin application software/drivers using the procedures that worked
> in
> | getting the drivers to install, and the same error message appears every
> time
> | on restart that I mentioned in my last post. When opening the "Utility"
> | software I get the consistent message: "Incompatible driver version.
> Unable
> | to load application", then the Belkin utility window opens with "No
> adapters"
> | on the tab. Now, you can't tell me that 3 versions of drivers are all
> | duff... incompatible! To me this is evidence of a duff card and goes back
> to
> | the point I made originally about the ver.no. on the card ending in "ec" &
> | not "uk". If you go to the following link:
> |
> <http://www.belkin.com/uk/support/art...uk&aid=6199&sc
> id=0>
> | you'll notice the picture shows this at the end of the model number
> 'F5D7000'
> | and all the software/drivers also end in 'uk' & not 'ec'. I believe I've
> got
> | a card designed for European use & not UK use. I raised this with Belkin
> but
> | they wouldn't comment. At this point in time I really cannot see the
> problem
> | being anything else than this, after exploring all other issues. Am I
> right?
> |
> | Sandy.
>
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
>
> |
> | "MEB" wrote:
> |
> | >
> | >
> | > "Sandy" <(E-Mail Removed)> wrote in message
> | > news:77C821E5-4A97-4318-BAF0-(E-Mail Removed)...
> | > | Hi MEB, good to hear from you... yes, as far as I'm aware, my TCP/IP
> | > settings
> | > | are right. As far as the BIOS upgrade for the Belkin... I didn't know
> | > there
> | > | was one, I'll check. I haven't gone down the road of pinging or
> running
> | > | winipcfg as I thought the adapter had to be working first??? And
> finally
> | > no,
> | > | I don't use ICS as the other computers belong to my son next door so
> we
> | > have
> | > | no need to share files etc.!
> | > | Cheers, Sandy.
> | > |
> | >
> | > Okay, No ICS entries that might have conflicted.
> | >
> | > Are the other wireless connected computers able to SEE your problem 98
> | > computer {does it appear anywhere in your son's actual network [if he is
> the
> | > one with the wireless base unit]}?
> | >
> | >
> | > What Gary is suggesting is, that the adapter MIGHT be installed, but
> the
> | > adapter in the 98 box is not connecting to the network, which will cause
> a
> | > network error. Errors like you are receiving can also occur [after an
> | > install] because the adapter can not connect to the network, hence it is
> an
> | > error.
> | > What you have posted is that the adapter "apparently" IS installed [or
> at
> | > least shown in the Network configuration].
> | > AS YOU POSTED:
> | > Client for Microsoft Networks
> | > Belkin Wireless 54Mbps Desktop Adapter
> | > Dial-Up Adapter
> | > TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
> | > TCP/IP->Dial-Up Adapter
> | > and...
> | > Primary Network Logon: Windows Logon.
> | >
> | >
> | > I use your "son as" the identifier below, but it refers to whoever has
> the
> | > base transceiver and the actual unit.
> | > Your son MUST add your computer to his network or allow that address in
> the
> | > acceptable range OR you must be using the address range he has allowed
> or is
> | > using as his network. If he setup static addressing then your computer
> must
> | > also use a static address in the range he has allowed. You will also
> need to
> | > use the same compression and security [WEP/WPA-PSK/WPA-2/whatever and
> should
> | > be the same 64/128/etc., SSID{key}, etc. between the two - your adapter
> and
> | > his base transceiver, they MUST be the same. Recheck the
> ENCRYPTION/SECURITY
> | > ISSUES and basic setup sections on my web page for details.
> | >
> | > Have you checked in the wireless base transceiver for what the actual
> | > network configuration is? The 98 computer MUST be using *that* network
> | > addressing range and the transciever address should/would be the gateway
> in
> | > your computer Belkin TCP/IP, hence the reason for running winipcfg, to
> see
> | > if the adapter IS attempting to communicate, and whether *your* IP
> address
> | > is in the *wireless base transceiver* range..
> | >
> | > Any firewall between you and the transceiver MUST allow access/talking
> to
> | > occur. Check your computer firewall, and make sure it has the local
> network
> | > allowance [the wireless network range]. IF you are running
> Norton/Symantec
> | > or McAfee we need to know that specifically, and any other Anti-V,
> | > Anti-SpyWare, etc..
> | >
> | > --
> | > MEB http://peoplescounsel.orgfree.com
> | > --
> | > _________
> | >
> | >
> | > | "MEB" wrote:
> | > |
> | > | > Sorry, slightly distracted. Did you check for proper TCP/IP
> settings, or
> | > did
> | > | > you not get that far?
> | > | >
> | > | > IF the card is shown, but not working properly AND you did check
> the
> | > TCP/IP
> | > | > and it is correct, did you check for an upgrade {BIOS} for the
> device?
> | > | >
> | > | > Winipcfg > Details > {what}?
> | > | >
> | > | > Are you also using ICS in the system {or did you at one time?}?
> | > | >
> | > | > Did you try the ping diagnostics?
> | > | >
> | > | > --
> | > | > MEB http://peoplescounsel.orgfree.com
> | > | > --
> | > | > _________
> | > | >
> | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > news:56494402-ED9E-493F-8FF6-(E-Mail Removed)...
> | > | > | Hello MEB,
> | > | > |
> | > | > | I've had some time to examine your webpage, lots of useful stuff
> on
> | > | > | networking and problems with, but I didn't find much on
> | > troubleshooting
> | > | > | adapter installation. But to answer your last questions about the
> | > EXACT
> | > | > | error message, this happens on boot-up and/or restart: Windows
> | > Networking
> | > | > | window pops up...
> | > | > | "Your network adapter Belkin Wireless 54Mbps Desktop Adapter
> (0001) is
> | > not
> | > | > | working properly. You may need to set it up again. For more
> | > information,
> | > | > | see the Network Troubleshooter in Windows Help".
> | > | > |
> | > | > | You also asked what is listed in Control Panel>Networks:
> | > | > | Client for Microsoft Networks
> | > | > | Belkin Wireless 54Mbps Desktop Adapter
> | > | > | Dial-Up Adapter
> | > | > | TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
> | > | > | TCP/IP->Dial-Up Adapter
> | > | > | and...
> | > | > | Primary Network Logon: Windows Logon.
> | > | > |
> | > | > | There's no problems with the modem/router as 3 other remote
> computers
> | > in
> | > | > my
> | > | > | network connect to it OK. Have we come to the end of the road?
> | > | > |
> | > | > | Cheers, Sandy.
> | > | > |
> | > | > | "MEB" wrote:
> | > | > |
> | > | > | > Sorry, marked this for response and overlooked it. Don't get
> lost in
> | > the
> | > | > | > page and links, it really isn't that difficult. The page is for
> | > general
> | > | > | > diagnostics and information/links to other materials which might
> be
> | > | > | > informative.
> | > | > | >
> | > | > | > Post back with success or if more personal help is needed. Good
> | > luck.
> | > | > | >
> | > | > | > --
> | > | > | > MEB http://peoplescounsel.orgfree.com
> | > | > | > --
> | > | > | > _________
> | > | > | >
> | > | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > | > news:18AC5D03-5CBA-4507-A2DB-(E-Mail Removed)...
> | > | > | > | Hi MEB,
> | > | > | > |
> | > | > | > | Gosh! You've given me a lot to look at & explore. Give me
> some
> | > time
> | > | > to
> | > | > | > | study all this and then I'll come back to you. Thanks.
> | > | > | > |
> | > | > | > | All the best,
> | > | > | > |
> | > | > | > | Sandy.
> | > | > | > |
> | > | > | > | "MEB" wrote:
> | > | > | > |
> | > | > | > | >
> | > | > | > | >
> | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > | > | > news:4D4C8B10-9B4B-4B28-B570-(E-Mail Removed)...
> | > | > | > | > | Good morning MEB and everybody else!
> | > | > | > | > |
> | > | > | > | > | OK some success. After going through the procedures we
> spoke
> | > | > about
> | > | > | > last
> | > | > | > | > | week over the week-end, yes the NIC is now recognized
> | > properly,
> | > | > yes
> | > | > | > the
> | > | > | > | > | drivers finally loaded successfully, but no, Windows says
> | > "there
> | > | > is a
> | > | > | > | > problem
> | > | > | > | > | with my NIC" on restart go & "run the troubleshooter"! As
> if
> | > I
> | > | > didn't

As for whether or not the NIC installed properly and drivers, etc., when it
comes to *wireless* cards, MEB, I don't think you can necessarily call that
"wrong". It may be *another* part of the wireless system that isn't
functioning properly. And, as I said, WINIPCFG, to the best of my knowledge,
doesn't see wireless adapters. But I may be wrong, I've only once worked
with a new wireless adapter in a 98 machine, and the memory is a bit vague.

But I agree, the unit should be returned and a new one tried. Even a
Linksys.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"MEB" <meb@not (E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Sandy" <(E-Mail Removed)> wrote in message
> news:B611B714-3730-437C-B0C5-(E-Mail Removed)...
> | MEB, Gary,
> |
> | Right, I've revisited some of the points made earlier. I actually have
> the
> | modem/router in my property which my son & I setup together, inputting
> all
> | the MAC addresses of all PC's & security settings - reasonably
> | straightforward on an Netgear and works well. I ran winipcfg and noted
> my
> | wireless adapter not even listed so there was no point in going any
> further
> | with that one. I checked with Belkin for any firmware revisions but, as
> | suspected, there's no flash 'bios' as such on the card... all done
> through
> | inf. & sys. files in the installation software.
> |
> | Which brings me onto Gary's point. I've now retried versions 1 through
> 3
> of
> | the Belkin application software/drivers using the procedures that worked
> in
> | getting the drivers to install, and the same error message appears every
> time
> | on restart that I mentioned in my last post. When opening the "Utility"
> | software I get the consistent message: "Incompatible driver version.
> Unable
> | to load application", then the Belkin utility window opens with "No
> adapters"
> | on the tab. Now, you can't tell me that 3 versions of drivers are all
> | duff... incompatible! To me this is evidence of a duff card and goes
> back
> to
> | the point I made originally about the ver.no. on the card ending in "ec"
> &
> | not "uk". If you go to the following link:
> |
> <http://www.belkin.com/uk/support/art...uk&aid=6199&sc
> id=0>
> | you'll notice the picture shows this at the end of the model number
> 'F5D7000'
> | and all the software/drivers also end in 'uk' & not 'ec'. I believe
> I've
> got
> | a card designed for European use & not UK use. I raised this with
> Belkin
> but
> | they wouldn't comment. At this point in time I really cannot see the
> problem
> | being anything else than this, after exploring all other issues. Am I
> right?
> |
> | Sandy.
>
> Could very well be, but I'm not sure why it would.. having tried the
> corrections [and you have tried them all apparently] I would go more for a
> bad adapter.
> Searching Google for that particular model [ec] only turns up this
> discussion... winipcfg showing nothing is not good... and the Belkin
> software also unable to find it really is not good. But it doesn't matter,
> if you bought the card, and contacted Belkin concerning it shortly after
> purchase, then you have the material [the contacts] to request a
> replacement
> from Belkin. Another possibility: If the purchase was recent enough, try
> to
> return it to the store where purchased.
>
> Uhm, however, let's get this straight, you posted:
> "OK some success. After going through the procedures we spoke about last
> week over the week-end, yes the NIC is now recognized properly, yes the
> drivers finally loaded successfully, but no, Windows says "there is a
> problem
> with my NIC" on restart go & "run the troubleshooter"! As if I didn't do
> that in the first place!"
>
> So in actuality, that wasn't correct, right [sorry we can only work with
> what you present us] the NIC wasn't properly installed/recognized and the
> drivers didn't load properly. Just a correction, as these posts are
> referenced by others.
>
> As you have spent a large amount of time, I would re-contact Belkin and
> tell them you need a new card [you have tried everything, have contacted
> them, and the card does NOT work]. If you have another card around or can
> borrow one, try that to see if it connects. Then you can point this out to
> Belkin as well.
>
> BTW: going through and beyond the first few pages Google shows, does turn
> up
> some rather poor ratings for that adapter.
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
>
> |
> | "MEB" wrote:
> |
> | >
> | >
> | > "Sandy" <(E-Mail Removed)> wrote in message
> | > news:77C821E5-4A97-4318-BAF0-(E-Mail Removed)...
> | > | Hi MEB, good to hear from you... yes, as far as I'm aware, my TCP/IP
> | > settings
> | > | are right. As far as the BIOS upgrade for the Belkin... I didn't
> know
> | > there
> | > | was one, I'll check. I haven't gone down the road of pinging or
> running
> | > | winipcfg as I thought the adapter had to be working first??? And
> finally
> | > no,
> | > | I don't use ICS as the other computers belong to my son next door so
> we
> | > have
> | > | no need to share files etc.!
> | > | Cheers, Sandy.
> | > |
> | >
> | > Okay, No ICS entries that might have conflicted.
> | >
> | > Are the other wireless connected computers able to SEE your problem
> 98
> | > computer {does it appear anywhere in your son's actual network [if he
> is
> the
> | > one with the wireless base unit]}?
> | >
> | >
> | > What Gary is suggesting is, that the adapter MIGHT be installed, but
> the
> | > adapter in the 98 box is not connecting to the network, which will
> cause
> a
> | > network error. Errors like you are receiving can also occur [after an
> | > install] because the adapter can not connect to the network, hence it
> is
> an
> | > error.
> | > What you have posted is that the adapter "apparently" IS installed
> [or
> at
> | > least shown in the Network configuration].
> | > AS YOU POSTED:
> | > Client for Microsoft Networks
> | > Belkin Wireless 54Mbps Desktop Adapter
> | > Dial-Up Adapter
> | > TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
> | > TCP/IP->Dial-Up Adapter
> | > and...
> | > Primary Network Logon: Windows Logon.
> | >
> | >
> | > I use your "son as" the identifier below, but it refers to whoever has
> the
> | > base transceiver and the actual unit.
> | > Your son MUST add your computer to his network or allow that address
> in
> the
> | > acceptable range OR you must be using the address range he has allowed
> or is
> | > using as his network. If he setup static addressing then your computer
> must
> | > also use a static address in the range he has allowed. You will also
> need to
> | > use the same compression and security [WEP/WPA-PSK/WPA-2/whatever and
> should
> | > be the same 64/128/etc., SSID{key}, etc. between the two - your
> adapter
> and
> | > his base transceiver, they MUST be the same. Recheck the
> ENCRYPTION/SECURITY
> | > ISSUES and basic setup sections on my web page for details.
> | >
> | > Have you checked in the wireless base transceiver for what the actual
> | > network configuration is? The 98 computer MUST be using *that* network
> | > addressing range and the transciever address should/would be the
> gateway
> in
> | > your computer Belkin TCP/IP, hence the reason for running winipcfg, to
> see
> | > if the adapter IS attempting to communicate, and whether *your* IP
> address
> | > is in the *wireless base transceiver* range..
> | >
> | > Any firewall between you and the transceiver MUST allow
> access/talking
> to
> | > occur. Check your computer firewall, and make sure it has the local
> network
> | > allowance [the wireless network range]. IF you are running
> Norton/Symantec
> | > or McAfee we need to know that specifically, and any other Anti-V,
> | > Anti-SpyWare, etc..
> | >
> | > --
> | > MEB http://peoplescounsel.orgfree.com
> | > --
> | > _________
> | >
> | >
> | > | "MEB" wrote:
> | > |
> | > | > Sorry, slightly distracted. Did you check for proper TCP/IP
> settings, or
> | > did
> | > | > you not get that far?
> | > | >
> | > | > IF the card is shown, but not working properly AND you did check
> the
> | > TCP/IP
> | > | > and it is correct, did you check for an upgrade {BIOS} for the
> device?
> | > | >
> | > | > Winipcfg > Details > {what}?
> | > | >
> | > | > Are you also using ICS in the system {or did you at one time?}?
> | > | >
> | > | > Did you try the ping diagnostics?
> | > | >
> | > | > --
> | > | > MEB http://peoplescounsel.orgfree.com
> | > | > --
> | > | > _________
> | > | >
> | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > news:56494402-ED9E-493F-8FF6-(E-Mail Removed)...
> | > | > | Hello MEB,
> | > | > |
> | > | > | I've had some time to examine your webpage, lots of useful stuff
> on
> | > | > | networking and problems with, but I didn't find much on
> | > troubleshooting
> | > | > | adapter installation. But to answer your last questions about
> the
> | > EXACT
> | > | > | error message, this happens on boot-up and/or restart: Windows
> | > Networking
> | > | > | window pops up...
> | > | > | "Your network adapter Belkin Wireless 54Mbps Desktop Adapter
> (0001) is
> | > not
> | > | > | working properly. You may need to set it up again. For more
> | > information,
> | > | > | see the Network Troubleshooter in Windows Help".
> | > | > |
> | > | > | You also asked what is listed in Control Panel>Networks:
> | > | > | Client for Microsoft Networks
> | > | > | Belkin Wireless 54Mbps Desktop Adapter
> | > | > | Dial-Up Adapter
> | > | > | TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
> | > | > | TCP/IP->Dial-Up Adapter
> | > | > | and...
> | > | > | Primary Network Logon: Windows Logon.
> | > | > |
> | > | > | There's no problems with the modem/router as 3 other remote
> computers
> | > in
> | > | > my
> | > | > | network connect to it OK. Have we come to the end of the road?
> | > | > |
> | > | > | Cheers, Sandy.
> | > | > |
> | > | > | "MEB" wrote:
> | > | > |
> | > | > | > Sorry, marked this for response and overlooked it. Don't get
> lost in
> | > the
> | > | > | > page and links, it really isn't that difficult. The page is
> for
> | > general
> | > | > | > diagnostics and information/links to other materials which
> might
> be
> | > | > | > informative.
> | > | > | >
> | > | > | > Post back with success or if more personal help is needed.
> Good
> | > luck.
> | > | > | >
> | > | > | > --
> | > | > | > MEB http://peoplescounsel.orgfree.com
> | > | > | > --
> | > | > | > _________
> | > | > | >
> | > | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > | > news:18AC5D03-5CBA-4507-A2DB-(E-Mail Removed)...
> | > | > | > | Hi MEB,
> | > | > | > |
> | > | > | > | Gosh! You've given me a lot to look at & explore. Give me
> some
> | > time
> | > | > to
> | > | > | > | study all this and then I'll come back to you. Thanks.
> | > | > | > |
> | > | > | > | All the best,
> | > | > | > |
> | > | > | > | Sandy.
> | > | > | > |
> | > | > | > | "MEB" wrote:
> | > | > | > |
> | > | > | > | >
> | > | > | > | >
> | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > | > | > news:4D4C8B10-9B4B-4B28-B570-(E-Mail Removed)...
> | > | > | > | > | Good morning MEB and everybody else!
> | > | > | > | > |
> | > | > | > | > | OK some success. After going through the procedures we
> spoke
> | > | > about
> | > | > | > last
> | > | > | > | > | week over the week-end, yes the NIC is now recognized
> | > properly,
> | > | > yes
> | > | > | > the
> | > | > | > | > | drivers finally loaded successfully, but no, Windows
> says
> | > "there
> | > | > is a
> | > | > | > | > problem
> | > | > | > | > | with my NIC" on restart go & "run the troubleshooter"!
> As
> if
> | > I
> | > | > didn't
> | > | > | > do
> | > | > | > | > | that in the first place!
> | > | > | > | > |
> | > | > | > | > | I have to say I think that this final message would
> rather
> | > | > indicate a
> | > | > | > | > faulty
> | > | > | > | > | card which may account for all the difficulties. What
> do
> you
> | > | > think?
> | > | > | > | > |
> | > | > | > | > | Regards, Sandy.
> | > | > | > | > |
> | > | > | > | >
> | > | > | > | > What is the EXACT error message and what is now shown in
> | > Control
> | > | > Panel
> | > | > | > >
> | > | > | > | > Network. > {NIC adapter {Belkin 54g wireless}}
> | > | > | > | >
> | > | > | > | > What you're looking for is TCP/IP set for Obtain IP
> | > automatically,
> | > | > no
> | > | > | > | > Gateway, no WINS, and other *INITIALLY*.
> | > | > | > | > HOWEVER, as this is part of a wireless network, the rest
> of
> the
> | > | > network
> | > | > | > | > must be found. RUN * winipcfg * in the Start > RUN box.
> | > | > | > | > What is the address for your base unit/wireless router?
> | > | > | > | >
> | > | > | > | > Here's a general network diagnostic/setup page:
> | > | > | > | >
> | > http://peoplescounsel.orgfree.com/re...NETWORKING.htm
> | > | > | > | >
> | > | > | > | > --
> | > | > | > | > MEB http://peoplescounsel.orgfree.com
> | > | > | > | > --
> | > | > | > | > _________
> | > | > | > | >
> | > | > | > | > | "MEB" wrote:
> | > | > | > | > |
> | > | > | > | > | > Okay, please keep us informed.
> | > | > | > | > | >
> | > | > | > | > | > --
> | > | > | > | > | > MEB http://peoplescounsel.orgfree.com
> | > | > | > | > | > --
> | > | > | > | > | > _________
> | > | > | > | > | >
> | > | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in
> message
> | > | > | > | > | >
> news:5C18927B-2B7E-46DE-BEF7-(E-Mail Removed)...
> | > | > | > | > | > | Gosh... more stuff to think about! Thanks for that
> MEB.
> | > I'll
> | > | > | > have a
> | > | > | > | > go
> | > | > | > | > | > of
> | > | > | > | > | > | your suggestions over the week-end and see what
> happens.
> | > I'll
> | > | > | > come
> | > | > | > | > back
> | > | > | > | > | > to
> | > | > | > | > | > | you next week. See you then.
> | > | > | > | > | > |
> | > | > | > | > | > | Sandy.
> | > | > | > | > | > |
> | > | > | > | > | > | "MEB" wrote:
> | > | > | > | > | > |
> | > | > | > | > | > | >
> | > | > | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in
> | > message
> | > | > | > | > | > | >
> | > news:A58BA0DB-EBEF-42F0-9FE2-(E-Mail Removed)...
> | > | > | > | > | > | > | Morning MEB (it is for me!),
> | > | > | > | > | > | > |
> | > | > | > | > | > | > | Thanks for your reply... lots of stuff for me to
> get
> | > my
> | > | > head
> | > | > | > | > round!
> | > | > | > | > | > | > |
> | > | > | > | > | > | > | The only INF files I removed were the folders
> listed
> | > as
> | > | > Belkin
> | > | > | > &
> | > | > | > | > | > Broadcom,
> | > | > | > | > | > | > | no others.
> | > | > | > | > | > | >
> | > | > | > | > | > | > Okay, that was important, we now can focus on
> other
> | > | > potentials.
> | > | > | > | > | > | >
> | > | > | > | > | > | > |
> | > | > | > | > | > | > | >
> | > http://kbserver.netgear.com/kb_web_files/N100393.asp -
> | > | > was
> | > | > | > the
> | > | > | > | > | > technique
> | > | > | > | > | > | > you
> | > | > | > | > | > | > | > used similar to this?
> | > | > | > | > | > | > |
> | > | > | > | > | > | > | Just printed this off - useful stuff here,
> thanks.
> | > Yes
> | > | > sort
> | > | > | > off
> | > | > | > | > in my
> | > | > | > | > | > | > | fumbling way trying to muddle through. There
> are
> some
> | > | > extra
> | > | > | > steps
> | > | > | > | > I
> | > | > | > | > | > can
> | > | > | > | > | > | > try
> | > | > | > | > | > | > | but what is really useful is I can follow
> through
> in a
> | > | > logical
> | > | > | > | > | > sequence.
> | > | > | > | > | > | > | However, looking at the points between steps 15
> &
> 16
> | > ( I
> | > | > was
> | > | > | > | > having
> | > | > | > | > | > | > another
> | > | > | > | > | > | > | go last night whilst waiting for this post), I
> noticed
> | > the
> | > | > | > card
> | > | > | > | > was
> | > | > | > | > | > not
> | > | > | > | > | > | > | identified. However, I will go through
> Netgears'
> | > sequence
> | > | > now
> | > | > | > | > I've
> | > | > | > | > | > got it
>
>

Might want to check out the thread in Win98.Gen_Discussion from the NetGear
wireless buyer who is having almost exactly the same problems you are.

Windows 98 was never built with wireless networking in mind. There is
nothing native to support it, so all that stuff needs to be installed before
you can actually install the hardware itself. Lots of room for mistakes.
Unfortunately, I can't tell you more without going out any buying a couple
of the devices and playing with them on my own system, so I'd at least know
what *should* happen.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Sandy" <(E-Mail Removed)> wrote in message
news:9062F7A9-F471-4826-A7E0-(E-Mail Removed)...
> Thanks MEB. I really wanted some substance & confirmation that I was
> doing
> the right thing before tackling Belkin. On my post you quoted below, I'm
> afraid that what I said was indeed the case, the drivers were listed
> correctly as confirmed in Properties for the adapter in Device Manager, as
> was the name of the NIC, albeit with a yellow exclamation mark. I
> apologize
> for any ambiguity but I try to be as accurate as possible. I also respect
> your comments as to the quality of Belkin NIC's... if the worse happens,
> then
> maybe a Netgear would be better?
>
> I really appreciate the work that you guys on these forums do, giving up
> your time presumably freely, to help out us D-I-Y'ers from all over the
> world. I think you're stars and need suitable recognition for it. I
> guess
> this is the end of the thread, so with that, many, many thanks.
>
> Best regards,
>
> Sandy.
>
>
> "MEB" wrote:
>> Could very well be, but I'm not sure why it would.. having tried the
>> corrections [and you have tried them all apparently] I would go more for
>> a
>> bad adapter.
>> Searching Google for that particular model [ec] only turns up this
>> discussion... winipcfg showing nothing is not good... and the Belkin
>> software also unable to find it really is not good. But it doesn't
>> matter,
>> if you bought the card, and contacted Belkin concerning it shortly after
>> purchase, then you have the material [the contacts] to request a
>> replacement
>> from Belkin. Another possibility: If the purchase was recent enough, try
>> to
>> return it to the store where purchased.
>>
>> Uhm, however, let's get this straight, you posted:
>> "OK some success. After going through the procedures we spoke about last
>> week over the week-end, yes the NIC is now recognized properly, yes the
>> drivers finally loaded successfully, but no, Windows says "there is a
>> problem
>> with my NIC" on restart go & "run the troubleshooter"! As if I didn't do
>> that in the first place!"
>>
>> So in actuality, that wasn't correct, right [sorry we can only work with
>> what you present us] the NIC wasn't properly installed/recognized and the
>> drivers didn't load properly. Just a correction, as these posts are
>> referenced by others.
>>
>> As you have spent a large amount of time, I would re-contact Belkin and
>> tell them you need a new card [you have tried everything, have contacted
>> them, and the card does NOT work]. If you have another card around or can
>> borrow one, try that to see if it connects. Then you can point this out
>> to
>> Belkin as well.
>>
>> BTW: going through and beyond the first few pages Google shows, does turn
>> up
>> some rather poor ratings for that adapter.
>
>
>> "Sandy" <(E-Mail Removed)> wrote in message
>> news:B611B714-3730-437C-B0C5-(E-Mail Removed)...
>> | MEB, Gary,
>> |
>> | Right, I've revisited some of the points made earlier. I actually have
>> the
>> | modem/router in my property which my son & I setup together, inputting
>> all
>> | the MAC addresses of all PC's & security settings - reasonably
>> | straightforward on an Netgear and works well. I ran winipcfg and noted
>> my
>> | wireless adapter not even listed so there was no point in going any
>> further
>> | with that one. I checked with Belkin for any firmware revisions but,
>> as
>> | suspected, there's no flash 'bios' as such on the card... all done
>> through
>> | inf. & sys. files in the installation software.
>> |
>> | Which brings me onto Gary's point. I've now retried versions 1 through
>> 3
>> of
>> | the Belkin application software/drivers using the procedures that
>> worked
>> in
>> | getting the drivers to install, and the same error message appears
>> every
>> time
>> | on restart that I mentioned in my last post. When opening the
>> "Utility"
>> | software I get the consistent message: "Incompatible driver version.
>> Unable
>> | to load application", then the Belkin utility window opens with "No
>> adapters"
>> | on the tab. Now, you can't tell me that 3 versions of drivers are all
>> | duff... incompatible! To me this is evidence of a duff card and goes
>> back
>> to
>> | the point I made originally about the ver.no. on the card ending in
>> "ec" &
>> | not "uk". If you go to the following link:
>> |
>> <http://www.belkin.com/uk/support/art...uk&aid=6199&sc
>> id=0>
>> | you'll notice the picture shows this at the end of the model number
>> 'F5D7000'
>> | and all the software/drivers also end in 'uk' & not 'ec'. I believe
>> I've
>> got
>> | a card designed for European use & not UK use. I raised this with
>> Belkin
>> but
>> | they wouldn't comment. At this point in time I really cannot see the
>> problem
>> | being anything else than this, after exploring all other issues. Am I
>> right?
>> |
>> | Sandy.
>>
>>
>> --
>> MEB http://peoplescounsel.orgfree.com
>> --
>> _________
>>
>>
>> |
>> | "MEB" wrote:
>> |
>> | >
>> | >
>> | > "Sandy" <(E-Mail Removed)> wrote in message
>> | > news:77C821E5-4A97-4318-BAF0-(E-Mail Removed)...
>> | > | Hi MEB, good to hear from you... yes, as far as I'm aware, my
>> TCP/IP
>> | > settings
>> | > | are right. As far as the BIOS upgrade for the Belkin... I didn't
>> know
>> | > there
>> | > | was one, I'll check. I haven't gone down the road of pinging or
>> running
>> | > | winipcfg as I thought the adapter had to be working first??? And
>> finally
>> | > no,
>> | > | I don't use ICS as the other computers belong to my son next door
>> so
>> we
>> | > have
>> | > | no need to share files etc.!
>> | > | Cheers, Sandy.
>> | > |
>> | >
>> | > Okay, No ICS entries that might have conflicted.
>> | >
>> | > Are the other wireless connected computers able to SEE your problem
>> 98
>> | > computer {does it appear anywhere in your son's actual network [if he
>> is
>> the
>> | > one with the wireless base unit]}?
>> | >
>> | >
>> | > What Gary is suggesting is, that the adapter MIGHT be installed, but
>> the
>> | > adapter in the 98 box is not connecting to the network, which will
>> cause
>> a
>> | > network error. Errors like you are receiving can also occur [after an
>> | > install] because the adapter can not connect to the network, hence it
>> is
>> an
>> | > error.
>> | > What you have posted is that the adapter "apparently" IS installed
>> [or
>> at
>> | > least shown in the Network configuration].
>> | > AS YOU POSTED:
>> | > Client for Microsoft Networks
>> | > Belkin Wireless 54Mbps Desktop Adapter
>> | > Dial-Up Adapter
>> | > TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
>> | > TCP/IP->Dial-Up Adapter
>> | > and...
>> | > Primary Network Logon: Windows Logon.
>> | >
>> | >
>> | > I use your "son as" the identifier below, but it refers to whoever
>> has
>> the
>> | > base transceiver and the actual unit.
>> | > Your son MUST add your computer to his network or allow that address
>> in
>> the
>> | > acceptable range OR you must be using the address range he has
>> allowed
>> or is
>> | > using as his network. If he setup static addressing then your
>> computer
>> must
>> | > also use a static address in the range he has allowed. You will also
>> need to
>> | > use the same compression and security [WEP/WPA-PSK/WPA-2/whatever and
>> should
>> | > be the same 64/128/etc., SSID{key}, etc. between the two - your
>> adapter
>> and
>> | > his base transceiver, they MUST be the same. Recheck the
>> ENCRYPTION/SECURITY
>> | > ISSUES and basic setup sections on my web page for details.
>> | >
>> | > Have you checked in the wireless base transceiver for what the
>> actual
>> | > network configuration is? The 98 computer MUST be using *that*
>> network
>> | > addressing range and the transciever address should/would be the
>> gateway
>> in
>> | > your computer Belkin TCP/IP, hence the reason for running winipcfg,
>> to
>> see
>> | > if the adapter IS attempting to communicate, and whether *your* IP
>> address
>> | > is in the *wireless base transceiver* range..
>> | >
>> | > Any firewall between you and the transceiver MUST allow
>> access/talking
>> to
>> | > occur. Check your computer firewall, and make sure it has the local
>> network
>> | > allowance [the wireless network range]. IF you are running
>> Norton/Symantec
>> | > or McAfee we need to know that specifically, and any other Anti-V,
>> | > Anti-SpyWare, etc..
>> | >
>> | > --
>> | > MEB http://peoplescounsel.orgfree.com
>> | > --
>> | > _________
>> | >
>> | >
>> | > | "MEB" wrote:
>> | > |
>> | > | > Sorry, slightly distracted. Did you check for proper TCP/IP
>> settings, or
>> | > did
>> | > | > you not get that far?
>> | > | >
>> | > | > IF the card is shown, but not working properly AND you did check
>> the
>> | > TCP/IP
>> | > | > and it is correct, did you check for an upgrade {BIOS} for the
>> device?
>> | > | >
>> | > | > Winipcfg > Details > {what}?
>> | > | >
>> | > | > Are you also using ICS in the system {or did you at one time?}?
>> | > | >
>> | > | > Did you try the ping diagnostics?
>> | > | >
>> | > | > --
>> | > | > MEB http://peoplescounsel.orgfree.com
>> | > | > --
>> | > | > _________
>> | > | >
>> | > | > "Sandy" <(E-Mail Removed)> wrote in message
>> | > | > news:56494402-ED9E-493F-8FF6-(E-Mail Removed)...
>> | > | > | Hello MEB,
>> | > | > |
>> | > | > | I've had some time to examine your webpage, lots of useful
>> stuff
>> on
>> | > | > | networking and problems with, but I didn't find much on
>> | > troubleshooting
>> | > | > | adapter installation. But to answer your last questions about
>> the
>> | > EXACT
>> | > | > | error message, this happens on boot-up and/or restart: Windows
>> | > Networking
>> | > | > | window pops up...
>> | > | > | "Your network adapter Belkin Wireless 54Mbps Desktop Adapter
>> (0001) is
>> | > not
>> | > | > | working properly. You may need to set it up again. For more
>> | > information,
>> | > | > | see the Network Troubleshooter in Windows Help".
>> | > | > |
>> | > | > | You also asked what is listed in Control Panel>Networks:
>> | > | > | Client for Microsoft Networks
>> | > | > | Belkin Wireless 54Mbps Desktop Adapter
>> | > | > | Dial-Up Adapter
>> | > | > | TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
>> | > | > | TCP/IP->Dial-Up Adapter
>> | > | > | and...
>> | > | > | Primary Network Logon: Windows Logon.
>> | > | > |
>> | > | > | There's no problems with the modem/router as 3 other remote
>> computers
>> | > in
>> | > | > my
>> | > | > | network connect to it OK. Have we come to the end of the road?
>> | > | > |
>> | > | > | Cheers, Sandy.
>> | > | > |
>> | > | > | "MEB" wrote:
>> | > | > |
>> | > | > | > Sorry, marked this for response and overlooked it. Don't get
>> lost in
>> | > the
>> | > | > | > page and links, it really isn't that difficult. The page is
>> for
>> | > general
>> | > | > | > diagnostics and information/links to other materials which
>> might
>> be
>> | > | > | > informative.
>> | > | > | >
>> | > | > | > Post back with success or if more personal help is needed.
>> Good
>> | > luck.
>> | > | > | >
>> | > | > | > --
>> | > | > | > MEB http://peoplescounsel.orgfree.com
>> | > | > | > --
>> | > | > | > _________
>> | > | > | >
>> | > | > | > "Sandy" <(E-Mail Removed)> wrote in message
>> | > | > | > news:18AC5D03-5CBA-4507-A2DB-(E-Mail Removed)...
>> | > | > | > | Hi MEB,
>> | > | > | > |
>> | > | > | > | Gosh! You've given me a lot to look at & explore. Give me
>> some
>> | > time
>> | > | > to
>> | > | > | > | study all this and then I'll come back to you. Thanks.
>> | > | > | > |
>> | > | > | > | All the best,
>> | > | > | > |
>> | > | > | > | Sandy.
>> | > | > | > |
>> | > | > | > | "MEB" wrote:
>> | > | > | > |
>> | > | > | > | >
>> | > | > | > | >
>> | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in
>> message
>> | > | > | > | >
>> news:4D4C8B10-9B4B-4B28-B570-(E-Mail Removed)...
>> | > | > | > | > | Good morning MEB and everybody else!
>> | > | > | > | > |
>> | > | > | > | > | OK some success. After going through the procedures we
>> spoke
>> | > | > about
>> | > | > | > last
>> | > | > | > | > | week over the week-end, yes the NIC is now recognized
>> | > properly,
>> | > | > yes
>> | > | > | > the
>> | > | > | > | > | drivers finally loaded successfully, but no, Windows
>> says
>> | > "there
>> | > | > is a
>> | > | > | > | > problem
>> | > | > | > | > | with my NIC" on restart go & "run the troubleshooter"!
>> As
>> if
>> | > I
>> | > | > didn't

Well, I think we pretty much agree. I would like to have known if the
adapter was picked up [broadcasting] to the rest of the network, but there
appears to be other issues within Sandy's system. I admit my memory is also
a bit vague [and getting worse every day].
Yeah, you are right, there can be numerous issues with any of these
wireless adapters, particularly in 98, though LinkSys *was* apparently a
more successful pick. And I have to admit, since wireless is so insecure,
that I avoid recommending or installing them, what with all the sniffer/hack
tools readily available [free RADIUS, KARMA, etc.], they just aren't a good
idea. Radio signal broadcasts just aren't secure for anything that might be
considered as a network, unless of course, you're the government/military
and a hack brings substantial prison time..

--
MEB http://peoplescounsel.orgfree.com
--
_________

"Gary S. Terhune" <none> wrote in message
news:(E-Mail Removed)...
| As for whether or not the NIC installed properly and drivers, etc., when
it
| comes to *wireless* cards, MEB, I don't think you can necessarily call
that
| "wrong". It may be *another* part of the wireless system that isn't
| functioning properly. And, as I said, WINIPCFG, to the best of my
knowledge,
| doesn't see wireless adapters. But I may be wrong, I've only once worked
| with a new wireless adapter in a 98 machine, and the memory is a bit
vague.
|
| But I agree, the unit should be returned and a new one tried. Even a
| Linksys.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
| www.grystmill.com
|
| "MEB" <meb@not (E-Mail Removed)> wrote in message
| news:(E-Mail Removed)...
| > "Sandy" <(E-Mail Removed)> wrote in message
| > news:B611B714-3730-437C-B0C5-(E-Mail Removed)...
| > | MEB, Gary,
| > |
| > | Right, I've revisited some of the points made earlier. I actually
have
| > the
| > | modem/router in my property which my son & I setup together, inputting
| > all
| > | the MAC addresses of all PC's & security settings - reasonably
| > | straightforward on an Netgear and works well. I ran winipcfg and
noted
| > my
| > | wireless adapter not even listed so there was no point in going any
| > further
| > | with that one. I checked with Belkin for any firmware revisions but,
as
| > | suspected, there's no flash 'bios' as such on the card... all done
| > through
| > | inf. & sys. files in the installation software.
| > |
| > | Which brings me onto Gary's point. I've now retried versions 1
through
| > 3
| > of
| > | the Belkin application software/drivers using the procedures that
worked
| > in
| > | getting the drivers to install, and the same error message appears
every
| > time
| > | on restart that I mentioned in my last post. When opening the
"Utility"
| > | software I get the consistent message: "Incompatible driver version.
| > Unable
| > | to load application", then the Belkin utility window opens with "No
| > adapters"
| > | on the tab. Now, you can't tell me that 3 versions of drivers are all
| > | duff... incompatible! To me this is evidence of a duff card and goes
| > back
| > to
| > | the point I made originally about the ver.no. on the card ending in
"ec"
| > &
| > | not "uk". If you go to the following link:
| > |
| >
<http://www.belkin.com/uk/support/art...uk&aid=6199&sc
| > id=0>
| > | you'll notice the picture shows this at the end of the model number
| > 'F5D7000'
| > | and all the software/drivers also end in 'uk' & not 'ec'. I believe
| > I've
| > got
| > | a card designed for European use & not UK use. I raised this with
| > Belkin
| > but
| > | they wouldn't comment. At this point in time I really cannot see the
| > problem
| > | being anything else than this, after exploring all other issues. Am I
| > right?
| > |
| > | Sandy.
| >
| > Could very well be, but I'm not sure why it would.. having tried the
| > corrections [and you have tried them all apparently] I would go more for
a
| > bad adapter.
| > Searching Google for that particular model [ec] only turns up this
| > discussion... winipcfg showing nothing is not good... and the Belkin
| > software also unable to find it really is not good. But it doesn't
matter,
| > if you bought the card, and contacted Belkin concerning it shortly after
| > purchase, then you have the material [the contacts] to request a
| > replacement
| > from Belkin. Another possibility: If the purchase was recent enough, try
| > to
| > return it to the store where purchased.
| >
| > Uhm, however, let's get this straight, you posted:
| > "OK some success. After going through the procedures we spoke about
last
| > week over the week-end, yes the NIC is now recognized properly, yes the
| > drivers finally loaded successfully, but no, Windows says "there is a
| > problem
| > with my NIC" on restart go & "run the troubleshooter"! As if I didn't
do
| > that in the first place!"
| >
| > So in actuality, that wasn't correct, right [sorry we can only work with
| > what you present us] the NIC wasn't properly installed/recognized and
the
| > drivers didn't load properly. Just a correction, as these posts are
| > referenced by others.
| >
| > As you have spent a large amount of time, I would re-contact Belkin and
| > tell them you need a new card [you have tried everything, have contacted
| > them, and the card does NOT work]. If you have another card around or
can
| > borrow one, try that to see if it connects. Then you can point this out
to
| > Belkin as well.
| >
| > BTW: going through and beyond the first few pages Google shows, does
turn
| > up
| > some rather poor ratings for that adapter.
| >
| > --
| > MEB http://peoplescounsel.orgfree.com
| > --
| > _________
| >
| >
| > |
| > | "MEB" wrote:
| > |
| > | >
| > | >
| > | > "Sandy" <(E-Mail Removed)> wrote in message
| > | > news:77C821E5-4A97-4318-BAF0-(E-Mail Removed)...
| > | > | Hi MEB, good to hear from you... yes, as far as I'm aware, my
TCP/IP
| > | > settings
| > | > | are right. As far as the BIOS upgrade for the Belkin... I didn't
| > know
| > | > there
| > | > | was one, I'll check. I haven't gone down the road of pinging or
| > running
| > | > | winipcfg as I thought the adapter had to be working first??? And
| > finally
| > | > no,
| > | > | I don't use ICS as the other computers belong to my son next door
so
| > we
| > | > have
| > | > | no need to share files etc.!
| > | > | Cheers, Sandy.
| > | > |
| > | >
| > | > Okay, No ICS entries that might have conflicted.
| > | >
| > | > Are the other wireless connected computers able to SEE your problem
| > 98
| > | > computer {does it appear anywhere in your son's actual network [if
he
| > is
| > the
| > | > one with the wireless base unit]}?
| > | >
| > | >
| > | > What Gary is suggesting is, that the adapter MIGHT be installed,
but
| > the
| > | > adapter in the 98 box is not connecting to the network, which will
| > cause
| > a
| > | > network error. Errors like you are receiving can also occur [after
an
| > | > install] because the adapter can not connect to the network, hence
it
| > is
| > an
| > | > error.
| > | > What you have posted is that the adapter "apparently" IS installed
| > [or
| > at
| > | > least shown in the Network configuration].
| > | > AS YOU POSTED:
| > | > Client for Microsoft Networks
| > | > Belkin Wireless 54Mbps Desktop Adapter
| > | > Dial-Up Adapter
| > | > TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
| > | > TCP/IP->Dial-Up Adapter
| > | > and...
| > | > Primary Network Logon: Windows Logon.
| > | >
| > | >
| > | > I use your "son as" the identifier below, but it refers to whoever
has
| > the
| > | > base transceiver and the actual unit.
| > | > Your son MUST add your computer to his network or allow that
address
| > in
| > the
| > | > acceptable range OR you must be using the address range he has
allowed
| > or is
| > | > using as his network. If he setup static addressing then your
computer
| > must
| > | > also use a static address in the range he has allowed. You will also
| > need to
| > | > use the same compression and security [WEP/WPA-PSK/WPA-2/whatever
and
| > should
| > | > be the same 64/128/etc., SSID{key}, etc. between the two - your
| > adapter
| > and
| > | > his base transceiver, they MUST be the same. Recheck the
| > ENCRYPTION/SECURITY
| > | > ISSUES and basic setup sections on my web page for details.
| > | >
| > | > Have you checked in the wireless base transceiver for what the
actual
| > | > network configuration is? The 98 computer MUST be using *that*
network
| > | > addressing range and the transciever address should/would be the
| > gateway
| > in
| > | > your computer Belkin TCP/IP, hence the reason for running winipcfg,
to
| > see
| > | > if the adapter IS attempting to communicate, and whether *your* IP
| > address
| > | > is in the *wireless base transceiver* range..
| > | >
| > | > Any firewall between you and the transceiver MUST allow
| > access/talking
| > to
| > | > occur. Check your computer firewall, and make sure it has the local
| > network
| > | > allowance [the wireless network range]. IF you are running
| > Norton/Symantec
| > | > or McAfee we need to know that specifically, and any other Anti-V,
| > | > Anti-SpyWare, etc..
| > | >
| > | > --
| > | > MEB http://peoplescounsel.orgfree.com
| > | > --
| > | > _________
| > | >
| > | >
| > | > | "MEB" wrote:
| > | > |
| > | > | > Sorry, slightly distracted. Did you check for proper TCP/IP
| > settings, or
| > | > did
| > | > | > you not get that far?
| > | > | >
| > | > | > IF the card is shown, but not working properly AND you did
check
| > the
| > | > TCP/IP
| > | > | > and it is correct, did you check for an upgrade {BIOS} for the
| > device?
| > | > | >
| > | > | > Winipcfg > Details > {what}?
| > | > | >
| > | > | > Are you also using ICS in the system {or did you at one time?}?
| > | > | >
| > | > | > Did you try the ping diagnostics?
| > | > | >
| > | > | > --
| > | > | > MEB http://peoplescounsel.orgfree.com
| > | > | > --
| > | > | > _________
| > | > | >
| > | > | > "Sandy" <(E-Mail Removed)> wrote in message
| > | > | > news:56494402-ED9E-493F-8FF6-(E-Mail Removed)...
| > | > | > | Hello MEB,
| > | > | > |
| > | > | > | I've had some time to examine your webpage, lots of useful
stuff
| > on
| > | > | > | networking and problems with, but I didn't find much on
| > | > troubleshooting
| > | > | > | adapter installation. But to answer your last questions about
| > the
| > | > EXACT
| > | > | > | error message, this happens on boot-up and/or restart:
Windows
| > | > Networking
| > | > | > | window pops up...
| > | > | > | "Your network adapter Belkin Wireless 54Mbps Desktop Adapter
| > (0001) is
| > | > not
| > | > | > | working properly. You may need to set it up again. For more
| > | > information,
| > | > | > | see the Network Troubleshooter in Windows Help".
| > | > | > |
| > | > | > | You also asked what is listed in Control Panel>Networks:
| > | > | > | Client for Microsoft Networks
| > | > | > | Belkin Wireless 54Mbps Desktop Adapter
| > | > | > | Dial-Up Adapter
| > | > | > | TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
| > | > | > | TCP/IP->Dial-Up Adapter
| > | > | > | and...
| > | > | > | Primary Network Logon: Windows Logon.
| > | > | > |
| > | > | > | There's no problems with the modem/router as 3 other remote
| > computers
| > | > in
| > | > | > my
| > | > | > | network connect to it OK. Have we come to the end of the
road?
| > | > | > |
| > | > | > | Cheers, Sandy.
| > | > | > |
| > | > | > | "MEB" wrote:
| > | > | > |
| > | > | > | > Sorry, marked this for response and overlooked it. Don't get
| > lost in
| > | > the
| > | > | > | > page and links, it really isn't that difficult. The page is
| > for
| > | > general
| > | > | > | > diagnostics and information/links to other materials which
| > might
| > be
| > | > | > | > informative.
| > | > | > | >
| > | > | > | > Post back with success or if more personal help is needed.
| > Good
| > | > luck.
| > | > | > | >
| > | > | > | > --
| > | > | > | > MEB http://peoplescounsel.orgfree.com
| > | > | > | > --
| > | > | > | > _________
| > | > | > | >
| > | > | > | > "Sandy" <(E-Mail Removed)> wrote in message
| > | > | > | > news:18AC5D03-5CBA-4507-A2DB-(E-Mail Removed)...
| > | > | > | > | Hi MEB,
| > | > | > | > |
| > | > | > | > | Gosh! You've given me a lot to look at & explore. Give me
| > some
| > | > time
| > | > | > to
| > | > | > | > | study all this and then I'll come back to you. Thanks.
| > | > | > | > |
| > | > | > | > | All the best,
| > | > | > | > |
| > | > | > | > | Sandy.
| > | > | > | > |
| > | > | > | > | "MEB" wrote:
| > | > | > | > |
| > | > | > | > | >
| > | > | > | > | >
| > | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in
message
| > | > | > | > | >
news:4D4C8B10-9B4B-4B28-B570-(E-Mail Removed)...
| > | > | > | > | > | Good morning MEB and everybody else!
| > | > | > | > | > |
| > | > | > | > | > | OK some success. After going through the procedures
we
| > spoke
| > | > | > about
| > | > | > | > last
| > | > | > | > | > | week over the week-end, yes the NIC is now recognized
| > | > properly,
| > | > | > yes
| > | > | > | > the
| > | > | > | > | > | drivers finally loaded successfully, but no, Windows
| > says
| > | > "there
| > | > | > is a
| > | > | > | > | > problem
| > | > | > | > | > | with my NIC" on restart go & "run the troubleshooter"!
| > As
| > if
| > | > I
| > | > | > didn't
| > | > | > | > do
| > | > | > | > | > | that in the first place!
| > | > | > | > | > |
| > | > | > | > | > | I have to say I think that this final message would
| > rather
| > | > | > indicate a
| > | > | > | > | > faulty
| > | > | > | > | > | card which may account for all the difficulties. What
| > do
| > you
| > | > | > think?
| > | > | > | > | > |
| > | > | > | > | > | Regards, Sandy.
| > | > | > | > | > |
| > | > | > | > | >
| > | > | > | > | > What is the EXACT error message and what is now shown
in
| > | > Control
| > | > | > Panel
| > | > | > | > >
| > | > | > | > | > Network. > {NIC adapter {Belkin 54g wireless}}
| > | > | > | > | >
| > | > | > | > | > What you're looking for is TCP/IP set for Obtain IP
| > | > automatically,
| > | > | > no
| > | > | > | > | > Gateway, no WINS, and other *INITIALLY*.
| > | > | > | > | > HOWEVER, as this is part of a wireless network, the
rest
| > of
| > the
| > | > | > network
| > | > | > | > | > must be found. RUN * winipcfg * in the Start > RUN box.
| > | > | > | > | > What is the address for your base unit/wireless router?
| > | > | > | > | >
| > | > | > | > | > Here's a general network diagnostic/setup page:
| > | > | > | > | >
| > | > http://peoplescounsel.orgfree.com/re...NETWORKING.htm
| > | > | > | > | >
| > | > | > | > | > --
| > | > | > | > | > MEB http://peoplescounsel.orgfree.com
| > | > | > | > | > --
| > | > | > | > | > _________
| > | > | > | > | >
| > | > | > | > | > | "MEB" wrote:
| > | > | > | > | > |
| > | > | > | > | > | > Okay, please keep us informed.
| > | > | > | > | > | >
| > | > | > | > | > | > --
| > | > | > | > | > | > MEB http://peoplescounsel.orgfree.com
| > | > | > | > | > | > --
| > | > | > | > | > | > _________
| > | > | > | > | > | >
| > | > | > | > | > | > "Sandy" <(E-Mail Removed)> wrote in
| > message
| > | > | > | > | > | >
| > news:5C18927B-2B7E-46DE-BEF7-(E-Mail Removed)...
| > | > | > | > | > | > | Gosh... more stuff to think about! Thanks for
that
| > MEB.
| > | > I'll
| > | > | > | > have a
| > | > | > | > | > go
| > | > | > | > | > | > of
| > | > | > | > | > | > | your suggestions over the week-end and see what
| > happens.
| > | > I'll
| > | > | > | > come
| > | > | > | > | > back
| > | > | > | > | > | > to
| > | > | > | > | > | > | you next week. See you then.
| > | > | > | > | > | > |
| > | > | > | > | > | > | Sandy.
| > | > | > | > | > | > |
| > | > | > | > | > | > | "MEB" wrote:
| > | > | > | > | > | > |
| > | > | > | > | > | > | >
| > | > | > | > | > | > | > "Sandy" <(E-Mail Removed)> wrote
in
| > | > message
| > | > | > | > | > | > | >
| > | > news:A58BA0DB-EBEF-42F0-9FE2-(E-Mail Removed)...
| > | > | > | > | > | > | > | Morning MEB (it is for me!),
| > | > | > | > | > | > | > |
| > | > | > | > | > | > | > | Thanks for your reply... lots of stuff for me
to
| > get
| > | > my
| > | > | > head
| > | > | > | > | > round!
| > | > | > | > | > | > | > |
| > | > | > | > | > | > | > | The only INF files I removed were the folders
| > listed
| > | > as
| > | > | > Belkin
| > | > | > | > &
| > | > | > | > | > | > Broadcom,
| > | > | > | > | > | > | > | no others.
| > | > | > | > | > | > | >
| > | > | > | > | > | > | > Okay, that was important, we now can focus on
| > other
| > | > | > potentials.
| > | > | > | > | > | > | >
| > | > | > | > | > | > | > |
| > | > | > | > | > | > | > | >
| > | > http://kbserver.netgear.com/kb_web_files/N100393.asp -
| > | > | > was
| > | > | > | > the
| > | > | > | > | > | > technique
| > | > | > | > | > | > | > you
| > | > | > | > | > | > | > | > used similar to this?
| > | > | > | > | > | > | > |
| > | > | > | > | > | > | > | Just printed this off - useful stuff here,
| > thanks.
| > | > Yes
| > | > | > sort
| > | > | > | > off
| > | > | > | > | > in my
| > | > | > | > | > | > | > | fumbling way trying to muddle through. There
| > are
| > some
| > | > | > extra
| > | > | > | > steps
| > | > | > | > | > I
| > | > | > | > | > | > can
| > | > | > | > | > | > | > try
| > | > | > | > | > | > | > | but what is really useful is I can follow
| > through
| > in a
| > | > | > logical
| > | > | > | > | > | > sequence.
| > | > | > | > | > | > | > | However, looking at the points between steps
15
| > &
| > 16
| > | > ( I
| > | > | > was
| > | > | > | > | > having
| > | > | > | > | > | > | > another
| > | > | > | > | > | > | > | go last night whilst waiting for this post), I
| > noticed
| > | > the
| > | > | > | > card
| > | > | > | > | > was
| > | > | > | > | > | > not
| > | > | > | > | > | > | > | identified. However, I will go through
| > Netgears'
| > | > sequence
| > | > | > now
| > | > | > | > | > I've
| > | > | > | > | > | > got it
| >
| >
|

Hi MEB & Gary,
Just thought you'd like to know that following our thread a while back,
there was sufficient ammo to hit Belkin with, and after some persuasion they
reluctantly agreed to replace the NIC. I received this yesterday and
installed it and, guess what, absolutely no problem! What a merry dance!!
So once again, thanks ever so much to you guys for all your support and
back-up over the months.

All the best,

Sandy.

"MEB" wrote:

> Well, I think we pretty much agree. I would like to have known if the
> adapter was picked up [broadcasting] to the rest of the network, but there
> appears to be other issues within Sandy's system. I admit my memory is also
> a bit vague [and getting worse every day].
> Yeah, you are right, there can be numerous issues with any of these
> wireless adapters, particularly in 98, though LinkSys *was* apparently a
> more successful pick. And I have to admit, since wireless is so insecure,
> that I avoid recommending or installing them, what with all the sniffer/hack
> tools readily available [free RADIUS, KARMA, etc.], they just aren't a good
> idea. Radio signal broadcasts just aren't secure for anything that might be
> considered as a network, unless of course, you're the government/military
> and a hack brings substantial prison time..
>
> --
> MEB http://peoplescounsel.orgfree.com
> --
> _________
>
> "Gary S. Terhune" <none> wrote in message
> news:(E-Mail Removed)...
> | As for whether or not the NIC installed properly and drivers, etc., when
> it
> | comes to *wireless* cards, MEB, I don't think you can necessarily call
> that
> | "wrong". It may be *another* part of the wireless system that isn't
> | functioning properly. And, as I said, WINIPCFG, to the best of my
> knowledge,
> | doesn't see wireless adapters. But I may be wrong, I've only once worked
> | with a new wireless adapter in a 98 machine, and the memory is a bit
> vague.
> |
> | But I agree, the unit should be returned and a new one tried. Even a
> | Linksys.
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> | www.grystmill.com
> |
> | "MEB" <meb@not (E-Mail Removed)> wrote in message
> | news:(E-Mail Removed)...
> | > "Sandy" <(E-Mail Removed)> wrote in message
> | > news:B611B714-3730-437C-B0C5-(E-Mail Removed)...
> | > | MEB, Gary,
> | > |
> | > | Right, I've revisited some of the points made earlier. I actually
> have
> | > the
> | > | modem/router in my property which my son & I setup together, inputting
> | > all
> | > | the MAC addresses of all PC's & security settings - reasonably
> | > | straightforward on an Netgear and works well. I ran winipcfg and
> noted
> | > my
> | > | wireless adapter not even listed so there was no point in going any
> | > further
> | > | with that one. I checked with Belkin for any firmware revisions but,
> as
> | > | suspected, there's no flash 'bios' as such on the card... all done
> | > through
> | > | inf. & sys. files in the installation software.
> | > |
> | > | Which brings me onto Gary's point. I've now retried versions 1
> through
> | > 3
> | > of
> | > | the Belkin application software/drivers using the procedures that
> worked
> | > in
> | > | getting the drivers to install, and the same error message appears
> every
> | > time
> | > | on restart that I mentioned in my last post. When opening the
> "Utility"
> | > | software I get the consistent message: "Incompatible driver version.
> | > Unable
> | > | to load application", then the Belkin utility window opens with "No
> | > adapters"
> | > | on the tab. Now, you can't tell me that 3 versions of drivers are all
> | > | duff... incompatible! To me this is evidence of a duff card and goes
> | > back
> | > to
> | > | the point I made originally about the ver.no. on the card ending in
> "ec"
> | > &
> | > | not "uk". If you go to the following link:
> | > |
> | >
> <http://www.belkin.com/uk/support/art...uk&aid=6199&sc
> | > id=0>
> | > | you'll notice the picture shows this at the end of the model number
> | > 'F5D7000'
> | > | and all the software/drivers also end in 'uk' & not 'ec'. I believe
> | > I've
> | > got
> | > | a card designed for European use & not UK use. I raised this with
> | > Belkin
> | > but
> | > | they wouldn't comment. At this point in time I really cannot see the
> | > problem
> | > | being anything else than this, after exploring all other issues. Am I
> | > right?
> | > |
> | > | Sandy.
> | >
> | > Could very well be, but I'm not sure why it would.. having tried the
> | > corrections [and you have tried them all apparently] I would go more for
> a
> | > bad adapter.
> | > Searching Google for that particular model [ec] only turns up this
> | > discussion... winipcfg showing nothing is not good... and the Belkin
> | > software also unable to find it really is not good. But it doesn't
> matter,
> | > if you bought the card, and contacted Belkin concerning it shortly after
> | > purchase, then you have the material [the contacts] to request a
> | > replacement
> | > from Belkin. Another possibility: If the purchase was recent enough, try
> | > to
> | > return it to the store where purchased.
> | >
> | > Uhm, however, let's get this straight, you posted:
> | > "OK some success. After going through the procedures we spoke about
> last
> | > week over the week-end, yes the NIC is now recognized properly, yes the
> | > drivers finally loaded successfully, but no, Windows says "there is a
> | > problem
> | > with my NIC" on restart go & "run the troubleshooter"! As if I didn't
> do
> | > that in the first place!"
> | >
> | > So in actuality, that wasn't correct, right [sorry we can only work with
> | > what you present us] the NIC wasn't properly installed/recognized and
> the
> | > drivers didn't load properly. Just a correction, as these posts are
> | > referenced by others.
> | >
> | > As you have spent a large amount of time, I would re-contact Belkin and
> | > tell them you need a new card [you have tried everything, have contacted
> | > them, and the card does NOT work]. If you have another card around or
> can
> | > borrow one, try that to see if it connects. Then you can point this out
> to
> | > Belkin as well.
> | >
> | > BTW: going through and beyond the first few pages Google shows, does
> turn
> | > up
> | > some rather poor ratings for that adapter.
> | >
> | > --
> | > MEB http://peoplescounsel.orgfree.com
> | > --
> | > _________
> | >
> | >
> | > |
> | > | "MEB" wrote:
> | > |
> | > | >
> | > | >
> | > | > "Sandy" <(E-Mail Removed)> wrote in message
> | > | > news:77C821E5-4A97-4318-BAF0-(E-Mail Removed)...
> | > | > | Hi MEB, good to hear from you... yes, as far as I'm aware, my
> TCP/IP
> | > | > settings
> | > | > | are right. As far as the BIOS upgrade for the Belkin... I didn't
> | > know
> | > | > there
> | > | > | was one, I'll check. I haven't gone down the road of pinging or
> | > running
> | > | > | winipcfg as I thought the adapter had to be working first??? And
> | > finally
> | > | > no,
> | > | > | I don't use ICS as the other computers belong to my son next door
> so
> | > we
> | > | > have
> | > | > | no need to share files etc.!
> | > | > | Cheers, Sandy.
> | > | > |
> | > | >
> | > | > Okay, No ICS entries that might have conflicted.
> | > | >
> | > | > Are the other wireless connected computers able to SEE your problem
> | > 98
> | > | > computer {does it appear anywhere in your son's actual network [if
> he
> | > is
> | > the
> | > | > one with the wireless base unit]}?
> | > | >
> | > | >
> | > | > What Gary is suggesting is, that the adapter MIGHT be installed,
> but
> | > the
> | > | > adapter in the 98 box is not connecting to the network, which will
> | > cause
> | > a
> | > | > network error. Errors like you are receiving can also occur [after
> an
> | > | > install] because the adapter can not connect to the network, hence
> it
> | > is
> | > an
> | > | > error.
> | > | > What you have posted is that the adapter "apparently" IS installed
> | > [or
> | > at
> | > | > least shown in the Network configuration].
> | > | > AS YOU POSTED:
> | > | > Client for Microsoft Networks
> | > | > Belkin Wireless 54Mbps Desktop Adapter
> | > | > Dial-Up Adapter
> | > | > TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
> | > | > TCP/IP->Dial-Up Adapter
> | > | > and...
> | > | > Primary Network Logon: Windows Logon.
> | > | >
> | > | >
> | > | > I use your "son as" the identifier below, but it refers to whoever
> has
> | > the
> | > | > base transceiver and the actual unit.
> | > | > Your son MUST add your computer to his network or allow that
> address
> | > in
> | > the
> | > | > acceptable range OR you must be using the address range he has
> allowed
> | > or is
> | > | > using as his network. If he setup static addressing then your
> computer
> | > must
> | > | > also use a static address in the range he has allowed. You will also
> | > need to
> | > | > use the same compression and security [WEP/WPA-PSK/WPA-2/whatever
> and
> | > should
> | > | > be the same 64/128/etc., SSID{key}, etc. between the two - your
> | > adapter
> | > and
> | > | > his base transceiver, they MUST be the same. Recheck the
> | > ENCRYPTION/SECURITY
> | > | > ISSUES and basic setup sections on my web page for details.
> | > | >
> | > | > Have you checked in the wireless base transceiver for what the
> actual
> | > | > network configuration is? The 98 computer MUST be using *that*
> network
> | > | > addressing range and the transciever address should/would be the
> | > gateway
> | > in
> | > | > your computer Belkin TCP/IP, hence the reason for running winipcfg,
> to
> | > see
> | > | > if the adapter IS attempting to communicate, and whether *your* IP
> | > address
> | > | > is in the *wireless base transceiver* range..
> | > | >
> | > | > Any firewall between you and the transceiver MUST allow
> | > access/talking
> | > to
> | > | > occur. Check your computer firewall, and make sure it has the local
> | > network
> | > | > allowance [the wireless network range]. IF you are running
> | > Norton/Symantec
> | > | > or McAfee we need to know that specifically, and any other Anti-V,
> | > | > Anti-SpyWare, etc..
> | > | >
> | > | > --
> | > | > MEB http://peoplescounsel.orgfree.com
> | > | > --
> | > | > _________
> | > | >
> | > | >
> | > | > | "MEB" wrote:
> | > | > |
> | > | > | > Sorry, slightly distracted. Did you check for proper TCP/IP
> | > settings, or
> | > | > did
> | > | > | > you not get that far?
> | > | > | >
> | > | > | > IF the card is shown, but not working properly AND you did
> check
> | > the
> | > | > TCP/IP
> | > | > | > and it is correct, did you check for an upgrade {BIOS} for the
> | > device?
> | > | > | >
> | > | > | > Winipcfg > Details > {what}?
> | > | > | >
> | > | > | > Are you also using ICS in the system {or did you at one time?}?
> | > | > | >
> | > | > | > Did you try the ping diagnostics?
> | > | > | >
> | > | > | > --
> | > | > | > MEB http://peoplescounsel.orgfree.com
> | > | > | > --
> | > | > | > _________
> | > | > | >

Good news! Thanks for the update.

--
Gary S. Terhune
MS-MVP Shell/User
www.grystmill.com

"Sandy" <(E-Mail Removed)> wrote in message
news:C00D9FD1-A59D-436B-80FD-(E-Mail Removed)...
> Hi MEB & Gary,
> Just thought you'd like to know that following our thread a while back,
> there was sufficient ammo to hit Belkin with, and after some persuasion
> they
> reluctantly agreed to replace the NIC. I received this yesterday and
> installed it and, guess what, absolutely no problem! What a merry dance!!
> So once again, thanks ever so much to you guys for all your support and
> back-up over the months.
>
> All the best,
>
> Sandy.
>
> "MEB" wrote:
>
>> Well, I think we pretty much agree. I would like to have known if the
>> adapter was picked up [broadcasting] to the rest of the network, but
>> there
>> appears to be other issues within Sandy's system. I admit my memory is
>> also
>> a bit vague [and getting worse every day].
>> Yeah, you are right, there can be numerous issues with any of these
>> wireless adapters, particularly in 98, though LinkSys *was* apparently a
>> more successful pick. And I have to admit, since wireless is so insecure,
>> that I avoid recommending or installing them, what with all the
>> sniffer/hack
>> tools readily available [free RADIUS, KARMA, etc.], they just aren't a
>> good
>> idea. Radio signal broadcasts just aren't secure for anything that might
>> be
>> considered as a network, unless of course, you're the government/military
>> and a hack brings substantial prison time..
>>
>> --
>> MEB http://peoplescounsel.orgfree.com
>> --
>> _________
>>
>> "Gary S. Terhune" <none> wrote in message
>> news:(E-Mail Removed)...
>> | As for whether or not the NIC installed properly and drivers, etc.,
>> when
>> it
>> | comes to *wireless* cards, MEB, I don't think you can necessarily call
>> that
>> | "wrong". It may be *another* part of the wireless system that isn't
>> | functioning properly. And, as I said, WINIPCFG, to the best of my
>> knowledge,
>> | doesn't see wireless adapters. But I may be wrong, I've only once
>> worked
>> | with a new wireless adapter in a 98 machine, and the memory is a bit
>> vague.
>> |
>> | But I agree, the unit should be returned and a new one tried. Even a
>> | Linksys.
>> |
>> | --
>> | Gary S. Terhune
>> | MS-MVP Shell/User
>> | www.grystmill.com
>> |
>> | "MEB" <meb@not (E-Mail Removed)> wrote in message
>> | news:(E-Mail Removed)...
>> | > "Sandy" <(E-Mail Removed)> wrote in message
>> | > news:B611B714-3730-437C-B0C5-(E-Mail Removed)...
>> | > | MEB, Gary,
>> | > |
>> | > | Right, I've revisited some of the points made earlier. I actually
>> have
>> | > the
>> | > | modem/router in my property which my son & I setup together,
>> inputting
>> | > all
>> | > | the MAC addresses of all PC's & security settings - reasonably
>> | > | straightforward on an Netgear and works well. I ran winipcfg and
>> noted
>> | > my
>> | > | wireless adapter not even listed so there was no point in going any
>> | > further
>> | > | with that one. I checked with Belkin for any firmware revisions
>> but,
>> as
>> | > | suspected, there's no flash 'bios' as such on the card... all done
>> | > through
>> | > | inf. & sys. files in the installation software.
>> | > |
>> | > | Which brings me onto Gary's point. I've now retried versions 1
>> through
>> | > 3
>> | > of
>> | > | the Belkin application software/drivers using the procedures that
>> worked
>> | > in
>> | > | getting the drivers to install, and the same error message appears
>> every
>> | > time
>> | > | on restart that I mentioned in my last post. When opening the
>> "Utility"
>> | > | software I get the consistent message: "Incompatible driver
>> version.
>> | > Unable
>> | > | to load application", then the Belkin utility window opens with "No
>> | > adapters"
>> | > | on the tab. Now, you can't tell me that 3 versions of drivers are
>> all
>> | > | duff... incompatible! To me this is evidence of a duff card and
>> goes
>> | > back
>> | > to
>> | > | the point I made originally about the ver.no. on the card ending in
>> "ec"
>> | > &
>> | > | not "uk". If you go to the following link:
>> | > |
>> | >
>> <http://www.belkin.com/uk/support/art...uk&aid=6199&sc
>> | > id=0>
>> | > | you'll notice the picture shows this at the end of the model number
>> | > 'F5D7000'
>> | > | and all the software/drivers also end in 'uk' & not 'ec'. I
>> believe
>> | > I've
>> | > got
>> | > | a card designed for European use & not UK use. I raised this with
>> | > Belkin
>> | > but
>> | > | they wouldn't comment. At this point in time I really cannot see
>> the
>> | > problem
>> | > | being anything else than this, after exploring all other issues.
>> Am I
>> | > right?
>> | > |
>> | > | Sandy.
>> | >
>> | > Could very well be, but I'm not sure why it would.. having tried the
>> | > corrections [and you have tried them all apparently] I would go more
>> for
>> a
>> | > bad adapter.
>> | > Searching Google for that particular model [ec] only turns up this
>> | > discussion... winipcfg showing nothing is not good... and the Belkin
>> | > software also unable to find it really is not good. But it doesn't
>> matter,
>> | > if you bought the card, and contacted Belkin concerning it shortly
>> after
>> | > purchase, then you have the material [the contacts] to request a
>> | > replacement
>> | > from Belkin. Another possibility: If the purchase was recent enough,
>> try
>> | > to
>> | > return it to the store where purchased.
>> | >
>> | > Uhm, however, let's get this straight, you posted:
>> | > "OK some success. After going through the procedures we spoke about
>> last
>> | > week over the week-end, yes the NIC is now recognized properly, yes
>> the
>> | > drivers finally loaded successfully, but no, Windows says "there is a
>> | > problem
>> | > with my NIC" on restart go & "run the troubleshooter"! As if I
>> didn't
>> do
>> | > that in the first place!"
>> | >
>> | > So in actuality, that wasn't correct, right [sorry we can only work
>> with
>> | > what you present us] the NIC wasn't properly installed/recognized and
>> the
>> | > drivers didn't load properly. Just a correction, as these posts are
>> | > referenced by others.
>> | >
>> | > As you have spent a large amount of time, I would re-contact Belkin
>> and
>> | > tell them you need a new card [you have tried everything, have
>> contacted
>> | > them, and the card does NOT work]. If you have another card around or
>> can
>> | > borrow one, try that to see if it connects. Then you can point this
>> out
>> to
>> | > Belkin as well.
>> | >
>> | > BTW: going through and beyond the first few pages Google shows, does
>> turn
>> | > up
>> | > some rather poor ratings for that adapter.
>> | >
>> | > --
>> | > MEB http://peoplescounsel.orgfree.com
>> | > --
>> | > _________
>> | >
>> | >
>> | > |
>> | > | "MEB" wrote:
>> | > |
>> | > | >
>> | > | >
>> | > | > "Sandy" <(E-Mail Removed)> wrote in message
>> | > | > news:77C821E5-4A97-4318-BAF0-(E-Mail Removed)...
>> | > | > | Hi MEB, good to hear from you... yes, as far as I'm aware, my
>> TCP/IP
>> | > | > settings
>> | > | > | are right. As far as the BIOS upgrade for the Belkin... I
>> didn't
>> | > know
>> | > | > there
>> | > | > | was one, I'll check. I haven't gone down the road of pinging
>> or
>> | > running
>> | > | > | winipcfg as I thought the adapter had to be working first???
>> And
>> | > finally
>> | > | > no,
>> | > | > | I don't use ICS as the other computers belong to my son next
>> door
>> so
>> | > we
>> | > | > have
>> | > | > | no need to share files etc.!
>> | > | > | Cheers, Sandy.
>> | > | > |
>> | > | >
>> | > | > Okay, No ICS entries that might have conflicted.
>> | > | >
>> | > | > Are the other wireless connected computers able to SEE your
>> problem
>> | > 98
>> | > | > computer {does it appear anywhere in your son's actual network
>> [if
>> he
>> | > is
>> | > the
>> | > | > one with the wireless base unit]}?
>> | > | >
>> | > | >
>> | > | > What Gary is suggesting is, that the adapter MIGHT be installed,
>> but
>> | > the
>> | > | > adapter in the 98 box is not connecting to the network, which
>> will
>> | > cause
>> | > a
>> | > | > network error. Errors like you are receiving can also occur
>> [after
>> an
>> | > | > install] because the adapter can not connect to the network,
>> hence
>> it
>> | > is
>> | > an
>> | > | > error.
>> | > | > What you have posted is that the adapter "apparently" IS
>> installed
>> | > [or
>> | > at
>> | > | > least shown in the Network configuration].
>> | > | > AS YOU POSTED:
>> | > | > Client for Microsoft Networks
>> | > | > Belkin Wireless 54Mbps Desktop Adapter
>> | > | > Dial-Up Adapter
>> | > | > TCP/IP->Belkin Wireless 54Mbps Desktop Adapter
>> | > | > TCP/IP->Dial-Up Adapter
>> | > | > and...
>> | > | > Primary Network Logon: Windows Logon.
>> | > | >
>> | > | >
>> | > | > I use your "son as" the identifier below, but it refers to
>> whoever
>> has
>> | > the
>> | > | > base transceiver and the actual unit.
>> | > | > Your son MUST add your computer to his network or allow that
>> address
>> | > in
>> | > the
>> | > | > acceptable range OR you must be using the address range he has
>> allowed
>> | > or is
>> | > | > using as his network. If he setup static addressing then your
>> computer
>> | > must
>> | > | > also use a static address in the range he has allowed. You will
>> also
>> | > need to
>> | > | > use the same compression and security [WEP/WPA-PSK/WPA-2/whatever
>> and
>> | > should
>> | > | > be the same 64/128/etc., SSID{key}, etc. between the two - your
>> | > adapter
>> | > and
>> | > | > his base transceiver, they MUST be the same. Recheck the
>> | > ENCRYPTION/SECURITY
>> | > | > ISSUES and basic setup sections on my web page for details.
>> | > | >
>> | > | > Have you checked in the wireless base transceiver for what the
>> actual
>> | > | > network configuration is? The 98 computer MUST be using *that*
>> network
>> | > | > addressing range and the transciever address should/would be the
>> | > gateway
>> | > in
>> | > | > your computer Belkin TCP/IP, hence the reason for running
>> winipcfg,
>> to
>> | > see
>> | > | > if the adapter IS attempting to communicate, and whether *your*
>> IP
>> | > address
>> | > | > is in the *wireless base transceiver* range..
>> | > | >
>> | > | > Any firewall between you and the transceiver MUST allow
>> | > access/talking
>> | > to
>> | > | > occur. Check your computer firewall, and make sure it has the
>> local
>> | > network
>> | > | > allowance [the wireless network range]. IF you are running
>> | > Norton/Symantec
>> | > | > or McAfee we need to know that specifically, and any other
>> Anti-V,
>> | > | > Anti-SpyWare, etc..
>> | > | >
>> | > | > --
>> | > | > MEB http://peoplescounsel.orgfree.com
>> | > | > --
>> | > | > _________
>> | > | >
>> | > | >
>> | > | > | "MEB" wrote:
>> | > | > |
>> | > | > | > Sorry, slightly distracted. Did you check for proper TCP/IP
>> | > settings, or
>> | > | > did
>> | > | > | > you not get that far?
>> | > | > | >
>> | > | > | > IF the card is shown, but not working properly AND you did
>> check
>> | > the
>> | > | > TCP/IP
>> | > | > | > and it is correct, did you check for an upgrade {BIOS} for
>> the
>> | > device?
>> | > | > | >
>> | > | > | > Winipcfg > Details > {what}?
>> | > | > | >
>> | > | > | > Are you also using ICS in the system {or did you at one
>> time?}?
>> | > | > | >
>> | > | > | > Did you try the ping diagnostics?
>> | > | > | >
>> | > | > | > --
>> | > | > | > MEB http://peoplescounsel.orgfree.com
>> | > | > | > --
>> | > | > | > _________
>> | > | > | >