wr_uk Posted December 22, 2024 Share Posted December 22, 2024 Hi, Is anybody else getting this error when enabling LEDBlinky? For some reason I have Ive been getting for about 3 weeks now when trying to enable and I have no idea how to resolve it or where exactly the problem lies. Im on the very latest update. Please any help is very much appreciated Thanks Quote Link to comment Share on other sites More sharing options...
Marine50 Posted January 1 Share Posted January 1 I'm having the same issue wish we could find out the issue Quote Link to comment Share on other sites More sharing options...
wr_uk Posted January 1 Author Share Posted January 1 (edited) yeah... very frustrating! its been nearly 1 month now Ive had no response at all from anybody at launchbox even after submitting a support ticket. An acknowledgement from their support even if its just to say we are looking into the problem and hope to have it resolved soon would be great. We cant be the only 2 people experiencing this problem Edited January 1 by wr_uk Quote Link to comment Share on other sites More sharing options...
dragon57 Posted January 1 Share Posted January 1 Although I don't have Ledblinky installed, there are a couple of things that might help diagnose things. The error in your pictures says it can't find D:\Launchbox\Games. I assume this directory exists? Have you tried installing an older release to see if the error exists? The older installers should be in your ...\Launchbox\Updates directory. Quote Link to comment Share on other sites More sharing options...
wr_uk Posted January 1 Author Share Posted January 1 Hi, there is no games folder in the directory in my set up which has always been the case and it was working up until about a month ago. Also the fact that I need point Launchbox to where LEDBlinky is yet it still cant find it I find a bit odd. Quote Link to comment Share on other sites More sharing options...
wr_uk Posted January 1 Author Share Posted January 1 I only have LaunchBox-13.18 and beta versions of this in the updates folder Where can I grab an earlier version? Quote Link to comment Share on other sites More sharing options...
dragon57 Posted January 1 Share Posted January 1 1 hour ago, wr_uk said: I only have LaunchBox-13.18 and beta versions of this in the updates folder Where can I grab an earlier version? I think you can email support@unbrokensoftware.com and request a link to one. 1 Quote Link to comment Share on other sites More sharing options...
dragon57 Posted January 2 Share Posted January 2 Also, you could try sending a PM to arzoo here on the forums since he is the author of the LEDBlinky software. He may have seen this error before. Quote Link to comment Share on other sites More sharing options...
Marine50 Posted January 2 Share Posted January 2 I have emailed arzoo about it and unfortunately he doesn't know about launchbox issues Quote Link to comment Share on other sites More sharing options...
Solution C-Beats Posted January 2 Solution Share Posted January 2 The error you're seeing isn't related to LEDBlinky at all, one of the options pages is having problems with it's save event and is throwing an issue for it. It appears to be looking to add the folders used in automated import feature and is failing to do because the folder in question doesn't exist (or can't be read by the app). If you disable this feature via it's option page and press OK I'd have to assume it'd work and the LED Blinky options would save then for you. 1 Quote Link to comment Share on other sites More sharing options...
Marine50 Posted January 4 Share Posted January 4 My error seems to be different and it looks like I'm running launchbox13.16 not 13.18 Quote Link to comment Share on other sites More sharing options...
wr_uk Posted January 5 Author Share Posted January 5 I had a response back from both Launchbox support and LEDBlinky support. Launchbox support LEDBlinky implementation hasn't been touched for about 2 years when a fix was put in to reduce some kind of slowdowns. Nothing has been touched since then, but there's always a possibility that LEDBlinky, or some other program it relies on changed, which could have caused our integration to stop working. We haven't heard of anything like that, and there's enough users that utilize the LEDBlinky integration that if we did break something for everyone, we would have definitely heard it LEDBlinky support I wonder if this has something to do with file permissions on the LEDBlinky folder? Maybe somehow the LaunchBox config app is unable to read the files in the \LEDBlinky folder? Or maybe something is going on with your virus protection software? I’m really just guessing here. But regardless, when you configure LaunchBox and select the LEDBlinky executable, absolutely nothing happens on the LEDBlinky side, so whatever the issue is, there’s nothing LEDBlinky is doing to cause that error. I see the response from the LB support guy but it seems like he doesn’t understand that this error is occurring from the LB configuration app, not when running LEDBlinky. Sorry I don’t have an answer. Maybe the LB forum can help? I was going to drop roll back on a version or two of launchbox but if your getting a similar error then I dont think rolling back will make any difference. Im going to check LEDBlinky suggestions and then roll back LEDBlinky version to see if that makes a difference. If none of these work then Im stumped. Just out of interest what version of LEDBlinky are your using? Quote Link to comment Share on other sites More sharing options...
Marine50 Posted January 8 Share Posted January 8 It looks like I'm running 13.16 and I think the current is 13.18 still have gotten any help yet arzoo did say it seems like LB is throwing an error that won't let me enable ledblinky but can't find the issue yet Quote Link to comment Share on other sites More sharing options...
C-Beats Posted January 8 Share Posted January 8 On 1/4/2025 at 6:23 PM, Marine50 said: My error seems to be different and it looks like I'm running launchbox13.16 not 13.18 No the error is the same one. Something in the Automated Import page is failing to save correctly which is stopping other changes from being saved that you made in that window. This error has absolutely nothing to do with LEDBlinky from what I can gather from your stack trace. Quote Link to comment Share on other sites More sharing options...
faeran Posted January 8 Share Posted January 8 Has anyone with the error tried to do this yet? Quote Link to comment Share on other sites More sharing options...
wr_uk Posted January 8 Author Share Posted January 8 exactly what feature is it referring to? Can you post a screen shot? Quote Link to comment Share on other sites More sharing options...
C-Beats Posted January 9 Share Posted January 9 17 hours ago, wr_uk said: exactly what feature is it referring to? Can you post a screen shot? Automated imports page, it's the feature that allows LB to automatically scan your drive for new roms and auto-import them. 1 Quote Link to comment Share on other sites More sharing options...
wr_uk Posted January 9 Author Share Posted January 9 On 1/2/2025 at 4:17 AM, C-Beats said: The error you're seeing isn't related to LEDBlinky at all, one of the options pages is having problems with it's save event and is throwing an issue for it. It appears to be looking to add the folders used in automated import feature and is failing to do because the folder in question doesn't exist (or can't be read by the app). If you disable this feature via it's option page and press OK I'd have to assume it'd work and the LED Blinky options would save then for you. Actually is was the opposite. It's was disabled. When I enabled, clicked OK and then launched bigbox. LEDBlinky started straight away! Thankyou everybody, I appreciate it! Quote Link to comment Share on other sites More sharing options...
skizzosjt Posted January 9 Share Posted January 9 38 minutes ago, wr_uk said: Actually is was the opposite. It's was disabled. When I enabled, clicked OK and then launched bigbox. LEDBlinky started straight away! Thankyou everybody, I appreciate it! What happens when you re-enable it? Does stuff still work or does a new or the same error return? Just because you use LEDBlinky doesn't mean you should be forced to enable auto imports. They shouldn't be dependent on one another like what has been described by your most recent post. Just seems off either way. auto imports should work for you when enabled and not throw an error. and LEDBlinky should work regardless of auto imports being enabled or not. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.