Home All Groups Group Topic Archive Search About

bang mark on usb wireless every reboot

Author
14 Feb 2009 12:31 AM
ToddAndMargo
Hi All,

    I have a customer with a wireless calibration device.
It is based on XP.  Buried inside it (you have to disassemble
the unit) is a "Via Network Technologies USB Wireless Lan adapter"

    Problem: the wireless adapter always boots up with a bang
mark on it in the device manager.  If I uninstall it and
scan for new hardware, it comes back perfectly.  That is,
until you shut down and reboot.  Then the bang mark is back.

    Anyone know how to fix this?

Many thanks,
-T

Author
14 Feb 2009 1:08 PM
Malke
ToddAndMargo wrote:

> Hi All,
>
>     I have a customer with a wireless calibration device.
> It is based on XP.  Buried inside it (you have to disassemble
> the unit) is a "Via Network Technologies USB Wireless Lan adapter"
>
>     Problem: the wireless adapter always boots up with a bang
> mark on it in the device manager.  If I uninstall it and
> scan for new hardware, it comes back perfectly.  That is,
> until you shut down and reboot.  Then the bang mark is back.

What do the tech support people for the wireless calibration device say?
That would be my first step to troubleshoot this.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ
Author
14 Feb 2009 7:04 PM
ToddAndMargo
Malke wrote:
Show quoteHide quote
> ToddAndMargo wrote:
>
>> Hi All,
>>
>>     I have a customer with a wireless calibration device.
>> It is based on XP.  Buried inside it (you have to disassemble
>> the unit) is a "Via Network Technologies USB Wireless Lan adapter"
>>
>>     Problem: the wireless adapter always boots up with a bang
>> mark on it in the device manager.  If I uninstall it and
>> scan for new hardware, it comes back perfectly.  That is,
>> until you shut down and reboot.  Then the bang mark is back.
>
> What do the tech support people for the wireless calibration device say?
> That would be my first step to troubleshoot this.
>
> Malke

They said to send it in to them and they'd reflash everything.
In other words, wipe it clean and start over and loose everything
that has been installed on it.

-T
Author
14 Feb 2009 7:41 PM
Malke
ToddAndMargo wrote:

>> What do the tech support people for the wireless calibration device say?
>> That would be my first step to troubleshoot this.
>>
>> Malke
>
> They said to send it in to them and they'd reflash everything.
> In other words, wipe it clean and start over and loose everything
> that has been installed on it.

Then I'm sorry, but that's what I would do.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ
Author
14 Feb 2009 9:36 PM
ToddAndMargo
Malke wrote:
> ToddAndMargo wrote:
>
>>> What do the tech support people for the wireless calibration device say?
>>> That would be my first step to troubleshoot this.
>>>
>>> Malke
>> They said to send it in to them and they'd reflash everything.
>> In other words, wipe it clean and start over and loose everything
>> that has been installed on it.
>
> Then I'm sorry, but that's what I would do.
>
> Malke

I do not give up so easily!  :-)
Author
14 Feb 2009 11:27 PM
Malke
ToddAndMargo wrote:

> I do not give up so easily!  :-)

It isn't a question of giving up. Your customer has a piece of proprietary
hardware that isn't working with the computer's wireless drivers. I don't
know what "reflash everything" means. If it means your customer got the
computer from the proprietary hardware people as part of the proprietary
hardware service, you should let your customer do the sensible thing and
send the whole thing back to the proprietary hardware people.

There's a whole lot of information missing from your posts. For instance, if
this all worked on the same computer before, what has changed between the
time things worked and the time they didn't? If this has never worked on
the customer's (presumably) new computer, then the proprietary hardware
people need to figure out why their device is causing the problem with the
computer's wireless drivers. No one else can do this except them.

Or perhaps there is no computer at all since you say this hardware device is
"based on XP". There is a whole lot of difference between a real computer
running a full version of Windows XP and a proprietary device running some
form of XP, perhaps the embedded version.

You do what you want, but you can't troubleshoot the proprietary device (if
that's what you're trying to do) like you would a regular computer running
XP.

I'm sorry that I was unable to help you.

Malke
--
MS-MVP
Elephant Boy Computers - Don't Panic!
http://www.elephantboycomputers.com/#FAQ
Author
14 Feb 2009 11:43 PM
ToddAndMargo
Malke wrote:
Show quoteHide quote
> ToddAndMargo wrote:

>> I do not give up so easily!  :-)
>
> It isn't a question of giving up. Your customer has a piece of proprietary
> hardware that isn't working with the computer's wireless drivers. I don't
> know what "reflash everything" means. If it means your customer got the
> computer from the proprietary hardware people as part of the proprietary
> hardware service, you should let your customer do the sensible thing and
> send the whole thing back to the proprietary hardware people.
>
> There's a whole lot of information missing from your posts. For instance, if
> this all worked on the same computer before, what has changed between the
> time things worked and the time they didn't? If this has never worked on
> the customer's (presumably) new computer, then the proprietary hardware
> people need to figure out why their device is causing the problem with the
> computer's wireless drivers. No one else can do this except them.
>
> Or perhaps there is no computer at all since you say this hardware device is
> "based on XP". There is a whole lot of difference between a real computer
> running a full version of Windows XP and a proprietary device running some
> form of XP, perhaps the embedded version.
>
> You do what you want, but you can't troubleshoot the proprietary device (if
> that's what you're trying to do) like you would a regular computer running
> XP.
>
> I'm sorry that I was unable to help you.
>
> Malke

Thanks for taking the time to write.  It is appreciated.

-T