Please ensure Javascript is enabled for purposes of website accessibility Jump to content

michaelgqld

Members
  • Posts

    7
  • Joined

  • Last visited

michaelgqld's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Conversation Starter Rare
  • One Month Later
  • Week One Done

Recent Badges

3

Reputation

  1. What I have found is the config file only supports Windows 10. The other laptop I tried is Windows 7. Manually editing the config file on that system to include Windows 7 in the 500X part of the hardware section allowed the Windows 7 laptop to to detect the 500X in License manager and in Monkey. I would use Line 6 central if you need to update your firmware however. So if you have Windows 10, I think it should work.
  2. Trying this on a different laptop has not worked, so you may still have an issue. I will continue to look into it.
  3. I had an issue with license manager where it would not detect my hardware and I was unable to activate anything. I managed to solve this. I must also give credit to hurghanico for giving me an insight into what the issue was. Get the default.cfg file from this post. Place this file in C:\Users\yourusername\AppData\Roaming\Line 6\MonkeyCore\ Attached image of folder with file example. Doing this enabled me to activate my 500X, additional software packs and install them onto it.
  4. I HAVE SOLVED IT! I put the default.cfg file from the Monkey workaround post in the MonkeyCore folder mentioned above and the 500X is now detected by license manager and I was then able to authorise it. After restarting License Manager, the packs appeared in the add-ons list. I then had the option to install the packs and after several minutes of programming the hardware, it said I needed to power cycle the 500X, which I did. THE PACKS ARE NOW INSTALLED! They show up under the model packs menu on the 500X and I am able to use them. I have told support how I did it also. Thanks hurghanico for giving me idea on what the issue is. Link to the post with the file Put the default.cfg file from this post at C:\Users\username\AppData\Roaming\Line 6\MonkeyCore\default.cfg
  5. Thanks for the replies. Cruisinon2. I understand your point and I agree that they may not be devoting a lot of resources to older products, however they are still selling the add on packs and they need to support those at least. I do think the fact that are still supporting older units in at least some manner is great and I think that other companies probably wouldn't, so I do appreciate Line 6 for that. Support has also been more responsive since I made the original post. Silverhead. I will look into that again but I think it was for a short amount of time. Something like 10 days, I may be wrong though. Support has assured me that I will be able to get a refund if the packs are not able to be activated and I also ordered using PayPal who have their buyer protection thing until late January. hurghanico. I have that same issue with monkey, only on a laptop that had monkey installed at an earlier date when I was looking at the edit software, will it detect the 500X, but it isn't able to check if updates are available. Other computers that I install the software fresh on, will not detect the 500X and won't let me select anything other than a POD XT or something. I did try using line 6 central and it works. It detects the 500X and reports that I have the latest firmware versions of both the 500X and usb (2.62 and 1.04.) The fact that License Manager works for you is interesting. I am guessing it is working for you because it already has the config files on your computer? From the log, it seems to run into the issue when it needs to download the config file for the 500X. That or maybe because it's already activated previously. Does your License Manager log mention if it is trying to download config files? Mine says it looks at C:\Users\username\AppData\Roaming\Line 6\MonkeyCore\default.cfg and C:\Users\username\AppData\Local\Temp\default.cfg before it tries downloading the config file. I have looked and those files do not exist on my pc, so I am guessing it only tries to download the files if those are not present. I'm now wondering if I had the 500X config file(s) in the relevant place, if it would work... I will mention this to support.
  6. I opened a ticket when it first happened, I have not had much in the way of help so far, other than what I considered to be fairly generic responses. (eg. it's a server issue, IT are working on it) I've worked as a tech in IT, and server issues don't normally run into several days, let alone weeks. At the time of the original post, I had received no reply for over 2 weeks and was very frustrated that I was not getting any replies when I had made further enquires on the ticket. After I posted here I went back to the support ticket, posted another comment, and after that I received a reply fairly quickly about a possible monkey workaround, the "Making Line 6 Monkey Work" post. This workaround has done nothing for my issue, or monkey, as still neither detect my 500X. I'm not really concerned with Monkey though. It seems the issue is with license manager, however they may be related because after looking in the Monkey log, it has basically the same errors and licence manager mentions Monkey device. In that reply I was told that licence manager would come "later." I have asked if there is any estimated time frame but I am yet to receive a reply back from that. I am trying to be patient about this but when you buy something and are unable to even activate it for several weeks, it wears rather thin.
  7. I am unable to activate the HD fully loaded bundle on my POD HD500X. License manager will not find it and only has my PC in the list. Relevant things I can see in the log file: Detecting devices... Downloading config file: http://line6.com etc. Created Monkey Device: POD HD500X Device not supported Redirecting to https://line6.com etc Loading server XML, XML Load failed! Error:80001019 And "Sockets: Socket operation on non-socket." This has been happening for over three weeks now. Is anyone else having/had a similar issue?
×
×
  • Create New...