SPARTAN117N01 Posted August 2, 2021 Author Share Posted August 2, 2021 It is read only but it keeps re-setting itself to read only. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 2, 2021 Share Posted August 2, 2021 What do you mean by its resetting itself? Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 2, 2021 Author Share Posted August 2, 2021 I mean this... After I hit apply and reopen the folders properties to double check and it's back to "read only". I edit a lot of ini files and have set "read only" dozens of times and this is the first time I've ever seen this behavior. Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 2, 2021 Author Share Posted August 2, 2021 I mean this... After I hit apply and reopen the folders properties to double check and it's back to "read only". I edit a lot of ini files and have set "read only" dozens of times and this is the first time I've ever seen this behavior. I turned on Debug Logging. Here is that file... not sure if it will help. Debug 2021-08-02 04-38-19 PM.log Quote Link to comment Share on other sites More sharing options...
Lobopr Posted August 4, 2021 Share Posted August 4, 2021 bump Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 Hey @SPARTAN-117B01 can you give me the full path to theme folder of the theme in question. Your path looks pretty long in that screenshot and I'm curious if you aren't running into an issue where the file path length is too long. Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 F:\Emulators & Games\Back & Front-Ends\LaunchBox (Front-End) = Root Folder F:\Emulators & Games\Back & Front-Ends\LaunchBox (Front-End)\LBThemes = Themes Folder Question: How Long is too long? Quote Link to comment Share on other sites More sharing options...
Inquisitor Posted August 4, 2021 Share Posted August 4, 2021 2 minutes ago, SPARTAN-117B01 said: F:\Emulators & Games\Back & Front-Ends\LaunchBox (Front-End) = Root Folder F:\Emulators & Games\Back & Front-Ends\LaunchBox (Front-End)\LBThemes = Themes Folder Question: How Long is too long? Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 I should be good then. I don't understand why I'm getting this error... I've installed LaunchBox dozens of times on multiple systems and have had it on this system in the past. I did a clean install of Windows 10 a few weeks back (again I've done this a dozen times over) and after installing the necessary software I added LaunchBox and here we are with this issue. I can give a list of the software I have installed but I don't think this too be the issue as I've used this software in the past with other LaunchBox installs. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 Yeah, other than the fact your directories permissions are changing after you manually set them I haven't seen anything in your reports that makes it sound like it's related to another software. When you have your LaunchBox open can you navigate to \\LaunchBox\Core\LBThemes\Neon Deluxe Arcade LB\Images\ via the symlink and make sure you can navigate to that folder inside of File Explorer and see the background images that are supposed to be in that folder. Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 See image for installed software. As for the folder see 2nd image; and just to cross it off the list, I've uploaded a 3rd image that shows my account on this system is Administrator. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 Removed your top image, no need to dox yourself for the cause. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 Can you try something else for me. Can you close LaunchBox/Big Box and then remove the LBThemes folder/symlink from \\LaunchBox\Core\ (if it exists) and then copy the LBThemes folder from \\LaunchBox\ TO \\LaunchBox\Core\ and then manually set the folder to readonly and start Launchbox and tell me if you still get the error. Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 That brings in an interesting question... could it be my security software? Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 3 minutes ago, C-Beats said: Can you try something else for me. Can you close LaunchBox/Big Box and then remove the LBThemes folder/symlink from \\LaunchBox\Core\ (if it exists) and then copy the LBThemes folder from \\LaunchBox\ TO \\LaunchBox\Core\ and then manually set the folder to readonly and start Launchbox and tell me if you still get the error. The symlink folders (all of them) disappear when LB is closed but I did copy the LBThemes folder to the core folder (it was already marked as read only). The errors still pop up... Something to note is that after setting it back to default and closing LB the "LBThemes" folder remains in the core directory but it's empty. Ideas? Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 Just so we are clear when I say "Set to readonly" that checkbox needs to be a check, not a square. A square means that some files in the folder are set to readonly but not all, a check would mean ALL are readonly so deleting the contents of that folder wouldn't even be possible if the flag was set the way I was referring to. Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 Well, I made sure it was a check mark and not a box... the contents of the folder a keeping even when LB is closed but the errors still pop up. I'm going to add an exception to my security for LB and see what happens on that front. Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 Does the checkbox stick? I know you were saying before unchecking that box wasn't. If that box doesn't stick or files are missing despite that being checked you may have something system side going on because that shouldn't be possible. We'd receive a IOException trying to delete anything in that folder marked read-only. Quote Link to comment Share on other sites More sharing options...
SPARTAN117N01 Posted August 4, 2021 Author Share Posted August 4, 2021 Can you clarify" We'd receive a IOException trying to delete anything in that folder marked read-only."? Quote Link to comment Share on other sites More sharing options...
C-Beats Posted August 4, 2021 Share Posted August 4, 2021 5 minutes ago, SPARTAN-117B01 said: Can you clarify" We'd receive a IOException trying to delete anything in that folder marked read-only."? Windows would stop our application from deleting the file. We'd get an exception or error that would appear in the logs or show in the error popup window of LaunchBox. 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.