One of the USB... has malfunctioned

[LookinAround]

• Nothing is absolutely certain in the wonderful world of computers, but I think there’s a good shot that uninstalling/reinstalling devices will fix the root problem. (Some manual cleanup to remove oem files, etc. might still be needed. But manual cleanup is ok if done after Windows does it’s work (not all uninstallers, etc. clean up after themselves correctly. But you always give them first chance becasue if you try manual change/hack/removal first, find it doesn’t work, and THEN try Windows uninstalls… the uninstalls may now fail because they find things missing. And then you’re stuck in a state where manual is you’re only option so best hope you can manually do a full cleanup
• I wouldn’t worry about removing oem files along the approach in my point above. It’s done all the time this way (i.e. doing uninstalls). Even so, nothing with computers is absolute. So the first step is always doing a full backup using a tool that can do file level recovery AND, should it be needed, it can recover your disk’s image (i.e. a snapshot of your disk as it was layed out at the time of the backup). My personal choice is Acronis True Image, $49.99 and can be ordered and downloaded from online with a 15day free trial before you need pay anything. (And if you go this route, be sure and create and burn an Acronis recovery CD as one of the first things you do – so you don’t find yourself sometime with a crashed machine and then thinking how to get to your backup data!?)
• By the way, it’s not clear for me just where the fault lies. Magellan is almost certainly running Windows Embedded and the Windows TFAT file system on the disk. So seeing Microsoft’s vendor id does make sense. In fact……I curious to know and found a nav system from Becker which also provides Microsoft’s vendor id to the USB bus. I’m not yet sure about the product id. ffff is actually a “wildcard” and would cause a match for any of Microsoft’s product ids that appear on that USB bus. Also note, it’s not the product id that distinguishes bluetooth from Mass Storage et. al. It’s the additional information contained in the USB descriptor which is passed along as part of the message on the bus which state things like Class = Bluetooth or Mass Storage. I don’t know, but the problem may not be Magellan at all but instead are in the WayTech USBFilters. I don’t know a lot about them but will guess from some of the info I see in their oem files, the Filters are intended to affect Bluetooth devices and traffic on a shared USB bus. But they may have bugs in the causing them to affect things outside of those bounds as well.
• An uninstall bluetooth process can involve more then just uninstalling the Widcomm driver. In the ways of windows, there are always “hidden” things you must know how to “unhide” before you can check to assure DeviceManager, as one example, has all bluetooth entries removed.
• So, take whatever path seems best for you so long as you promise to post back and reveal the ultimate source of your problem when found (now I’m just damn curious)

 

[MartyXB]

My initial thought why some of the blame is on Magellan was because of the output from USBDeview. I don't know where and how it gets the Device Name, but what it displays is omnious.

Device Name = Generic Mass Storage (PROTOTYPE--Remember to change idVendor)

 

[LookinAround]

Oh, i'm certainly not ruling out Magellan either. As you note, there's still plenty to raise suspicion about Magellan (i'll show you more below). But, i've also found the WayTech filters don't appear to have a perfect track record either. (When you talk to Magellan i wouldn't mention WayTech as sometimes tech support loves nothing easier then pointing the finger at someone else.)

And as far as those messages you see in USBDeview, here's what i stumbled across on MSDN (Microsoft Developer's Network) under Windows Embedded Development Center when discussing USB drivers and registry settings.
(below, where it says Copy Code, that's actually the label on a button somone can click to easily copy the code fragment MSDN provides)

The following registry keys show the default USB function mass storage client driver registry settings.

[B]Copy Code[/B] 

[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers]
   "DefaultClientDriver"=- ; erase previous default
[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers]
   "DefaultClientDriver"="Mass_Storage_Class"

[HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Mass_Storage_Class]
   "Dll"="usbmsfn.dll"
   "InterfaceSubClass"=dword:06 
   "InterfaceProtocol"=dword:50 
   "DeviceName"="DSK1:" 
   "FriendlyName"="Mass Storage"
   "idVendor"=dword:045E
   "Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change idVendor)"
   "idProduct"=dword:FFFF
   "Product"="Generic Mass Storage (PROTOTYPE--Remember to change idVendor)"
   "bcdDevice"=dword:0

So, yea, quite possible some developer at Magellan copied the sample code fragment from MSDN and then never bothered to update all the fields before the product was launched.

 

[LookinAround]

If you want to try, i'm thinking there may be a fairly easy method to try “another way to skin this cat”. I think will be good enough to disable the WayTech filter (and i have a tool that will make that task easy for you). You can use the tool to easily re-enable it as well if need be

• Download Serviwin
• It has 2 different views. One of your Windows services running and the other all your drivers. Click View -> Drivers for the drivers view.
• Look for the WayTech filter (I’m guessing it will display n558 under Name) .
• Look at its startup type. I’m guessing it’s either Manual or Automatic? (in either case remember the current value)
• Click Actions -> Change Startup Type -> Disabled

·
I think this should be sufficient so as not to be considered next time Windows installs for the Magellan USB. Reboot and try it out.

if it's still being used might have to remove waytech's oem files as am not certain, off hand see what setuapi generates and what happens when testing it.

If you still have problems with some usb ports not others it might be the modified oem files if u still have the originals? Or can get them regenerated..