also @ TechSpot: Check your bill: AT&T adds new 'administrative fee' to wireless bills

Problem with USB device

Discussion in 'Audio and Video' started by rduff, Apr 25, 2009.

  1. rduff Newcomer, in training Posts: 32

    OK...files uploaded as before but to another Humyo account
    Email richardduff@fastmail.fm
    Password techspot

    I think the C:Windows\inf search resulted in the same setupapi.dev.log as before. Also attached is a screen print of the search results for ks.inf, but not sure if I did what you wanted.

    You are convinced this is something to do with the firmware, whereas I believe it is related to the Realtek upgrade and the fact that one seems to corrupt the other. The firmware was installed about 6 months before the upgrade but the naming issue only became apparent afterwards. Interestingly I have tried reinstalling the original Realtek driver from my PC's system restore facility (currently v 2.21, before 1.69) yet once connected Micronas is still shown, so whatever has changed would appear to be irreversible.

    Perhaps the easiest solution is simply to buy a new headset!!
  2. LookinAround TechSpot Chancellor Posts: 7,679   +39

    LOL i agree wrt to getting a new headset :haha: BUT

    wrt firmware vs. Realtek Upgrade
    • You're thinking of your first firmware upgrade! Look again at the timeline. You ran a second firmware upgrade just minutes before Realtek upgrade
    • The device ID at moment / beginning of 2nd firmware upgrade is still the OLD device ID (of course) but once firmware upgrade is finished we frankly don't know if it changes after the 2nd firmware or your Realtek upgrade you started shortly after. (but, again, i can't imagine Realtek modifying any vendor's hardware device ID OTHER THEN their own Realtek hardware IDs
    • It's quite possible (even likely!) that even if ID chang was result of the 2nd firmware upgrade the actual change in the headset's device ID wouldn't take affect until the next time you had actually removed then reinserted your headset plug (vs. when the firmware upgrade s/w finishes)
    • I don't know.. but am guessing and curious... Did you download the firmware from Sennheiser again when you ran that second firmware upgrade just prior to Realtek
    • /* EDIT */ Added fact to know: Those device IDs aren't the result of corruption. The IDs your computer sees are whatever IDs have been programmed into the devices themselves! So while it's not impossible i just can't imagine Realtek applying a firmware change to your Sennheiser headset!
    Your search for Micronas text
    • Are you saying that the setupapi.dev.log file is the ONLY file match?
    • Did you following my directions in the .pdf?
    • Because that C:\Windows\inf\oem6.inf should also still exist in the directory AND we know it also contain Micronas text SO it should also have appeared if the text search if done right
    Last but certainly not least
    I think have the Vista registry edit solution! (And might be just for a minor tweak now for your USB headset name change but good to know how to circumvent Vista registry permission issues in the future!)
    1. Run regedit (I'm assuming your userid has Admin rights)
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_074D&PID_3554&MI_0 0
    3. Rt click on the key 7&84b63cc&7&0000 and select Permissions
    4. THEN click the Advanced Button, then the Owner tab
    5. Select your userid under Change owner to: then click OK
    6. Click to highlight OWNER RIGHTS, check Full Control then OK
    7. You should finally be able to edit FriendlyName!
    You'll note i renamed my friend's Maxtor drive! (and i did it remotely btw :D)
    [IMG]
  3. rduff Newcomer, in training Posts: 32

    Hi again
    Sorry for the delay in responding but I had visitors staying for the last few days and it was difficult to leave them in order to edit the registry!!
    The good news is that I was able to amend the friendly name to Sennheiser USB Headset in Device Manager. The bad news is that the change does not seem to have had any impact on the Realtek driver so when clicking on the little loudspeaker icon in the system tray, Micronas USB Headset still appears under playback devices.
    With regards to the report you would like me to run, can you please specify exactly what you want me to do as I've got a bit confused with the various requests.
    Regards
  4. LookinAround TechSpot Chancellor Posts: 7,679   +39

    Stop. Reset. OH! :D

    All this time i've been thinking you' were referring to the name appearing in Device Manager! That's where i focused (sorry if i misunderstood).

    Tho all not lost as at least (for me) have learned the trick to Vista registry permissions and a bit more about its drivers.

    But back to the business of name change! I'm not surprised to learn that the notification icon name may stored independent of the registry entry we edited. As that section of the registry is used for Windows services/drivers (e.g. for a USB enumerated device) (vs. its iconic user interface)

    I'll take a look at Vista icon names. (tho just in case, have you rebooted?) just in case the name is copied at reboot for icons vs. we can see the name change is immediately applied in the case of Device Manager
  5. rduff Newcomer, in training Posts: 32

    Yes I've rebooted but to no avail, and also unplugged & reconnected the headset. The Micronas name was shown in two places....in Device Manager, which is now rectified, but also in playback devices accessed by right clicking the small loudspeaker icon in the system tray. I would think this is a function of the Realtek sound card driver rather than a Vista icon as such, and brings me back to my original view that somehow the Sennheiser firmware and updated Realtek driver are somehow incompatible.
  6. LookinAround TechSpot Chancellor Posts: 7,679   +39

    Looking at things as I’ve had the time…. Here’s an update

    Notification Icon Text
    >> The icons you see in lower right along your Windows task bar are called “Notification Icons
    >> I’ve found the information (and text) for the notification icons for the current logged in user are stored in
    Code:
    [B]HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\TrayNotify[/B]
    >> But do not try to edit this key!
    Unlike the “FriendlyName”, trying to edit/change TrayNotify might result in a system crash (The TrayNotify format isn't publicly documented. And windows could change anytime they want. While we might guess its format, we could be wrong and/or it simply change which might cause registry corruption and a crash!)

    Then how change text for this case? Either
    • Programmatically. Means figuring out Vista's script/program interface which allows one to set icon "properties" including its text label
      >> might turn into to a lot (i.e. too much) work. But will explore it a bit to see
    • By reference. Whichever script/program runs normally now when you start Vista is assigning the text label “Micronas USB Headset” it is finding somewhere – if only we could find where that “somewhere” is to change it!
    For option b), here's step-by-step to look for Micronas text in the C:\Windows\inf directory

    1. Unhide Files
    Control Panel->Folder Options-View.
    >> Check Show hidden files and folders
    >> Uncheck Hide extensions for known file types
    >> Uncheck Hide protected operating file systems

    2. Validate Micronas search result when you do the search
    I think a valid search should result should include these 2 files in the result
    Code:
    C:\Windows\inf\oem6.inf
    C:\Windows\inf\setupapi.dev.log
    You can open/check the 2 files to find Micronas text to prove so (and prove you did the search correctly)

    3. How to search for Micronas in folder C:\Windows\inf

    >> Note the special “Windows” key in lower left of your keyboard
    >> Hold down Windows and ‘f’ key at the same time to get Vista search
    >> Click on Advanced search (should be in upper right)
    1. Check the box Include non-indexed, hidden, and system files
    2. Click the pull down arrow for Locations. Select Choose search locations. Then click on the arrows to expand and select Computer->C:->Windows
    3. Click on the folder named inf (you should then see the folder and its subfolders and files automatically all get checks in their check boxes!). Click OK
    4. In the search box (the rectangle in upper right) enter Micronas
    5. By default windows looks for folder names so it will say “No item matches” BUT click where it says Search in File Contents

    What are the files it then lists?
     
  7. rduff Newcomer, in training Posts: 32

    Hello again & thanks for the update. I ran the search as directed but there was only one file
    - setupapi.dev.log - which you've already seen. What do you suggest now?

    Forgot to tell you that Skype also recognises the headset as Micronas, so changing the friendly name made no difference.

    Regards
  8. LookinAround TechSpot Chancellor Posts: 7,679   +39

    Hi!

    Sorry for taking such a long time to reply... (Lots of distractions here.. including just being summer! Hope you're enjoying a good summer as well - assuming you're in the same hemisphere as i am!)

    Here's a bit more info if only for the "what it's worth" department as i'll admit i'm ready to resign to defeat to this Windows mystery for your specific case.

    As for FriendlyNames
    >> FriendlyName should reflect the name that appears in DeviceManager display (Click to look back at post #42 as you can see I renamed one of the disk drives listed in Device Manager to a “Maxtor Full-of-Baloney drive!

    As for the text displayed when you hover the mouse above notification icons
    >> I believe notification icon text for all the icons are stored in
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\TrayNotify\IconStreams
    >> But advise do NOT try changing this particular registry entry by hand
    >> An icon’s text can be changed programmatically by setting the text property of the Notify Icon (see http://msdn.microsoft.com/en-us/library/system.windows.forms.notifyicon.text.aspx)

    But i'm not going to try going any further down that path... Hope you have less grief when you buy your next Sennheiser USB headset!
  9. rduff Newcomer, in training Posts: 32

    Thanks for the update. Sorry we haven't been able to resolve this query but it's been an interesting journey.
    All the best.