Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Audiograbber

Audiograbber Community

  1. Home
  2. Audiograbber
  3. MP3 & Co
  4. Audiograbber 1.83, a Player button association - WMP 32-bit vs 64-bit problem

Audiograbber 1.83, a Player button association - WMP 32-bit vs 64-bit problem

Scheduled Pinned Locked Moved MP3 & Co
2 Posts 2 Posters 151 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B
    B
    Brunej
    wrote on last edited by
    #1

    Audiograbber 1.83, a Player button association - WMP 32-bit vs 64-bit problem:

    When I run Audiograbber 1.83 for the first time, I click the Player button to associate it with my default and/or favorite media player software - Windows Media Player v12...

    However, my Operating System is Microsoft Windows 7 Ultimate 64-bit,
    and it has "two" WMPs, the Windows Media Player v12 as a 32-bit version (in "C:\Program Files (x86)\Windows Media Player" folder), and 64-bit version (in "C:\Program Files\Windows Media Player" folder)...

    The problem is that I accidentally associate the Player button via Audiograbber 1.83 to WMP v12 64-bit, instead WMP v12 32-bit version... 😞
    It is important that I set it up this option again to WMP v12 32-bit version and I did not know how to do that...

    Any superficial changes via any file configuration in "C:\Program Files (x86)\Audiograbber" folder will not give any postivie result with this problem, and I was not be able to found the culprit command for this problem in Windows Registry (Regedit) also...


    Answer for the others - How I sucesfully and simply solved my above mentioned problem:

    I just, for the moment, rename to some other name, the "Windows Media Player" folder via ""C:\Program Files" - this is a 64-bit Windows Media Player location...
    Then run Audiograbber 1.83, and push the Player button. Now, he will ask AGAIN that he cannot found default player, bla, bla, bla..., so, reassociate this Player button now with Windows Media Player from "C:\Program Files (x86)" folder - this is a 32-bit Windows Media Player location, which I in fact want...
    Finally, back rename the "Windows Media Player" folder via ""C:\Program Files" - this is a 64-bit Windows Media Player location, to its originate name, and everything runs OK now as I want...

    At last note, If anybody ask, Audiograbber 1.83 runs OK on Microsoft Windows 7 Ultimate 64-bit Operating System... 🙂

    1 Reply Last reply
    0
    • ?
      ?
      Guest
      wrote on last edited by
      #2

      Microsoft Windows 7 Ultimate 32-bit

      1 Reply Last reply
      0

      Hello! It looks like you're interested in this conversation, but you don't have an account yet.

      Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

      With your input, this post could be even better 💗

      Register Login
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      Powered by NodeBB Contributors
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups