Nuitarius Posted September 16 Share Posted September 16 (edited) Hi Launchbox folk, I am first time user of eXoDOS and Launchbox, so please bear with me. I have a clean installed Win 10 Pro 22H2 x64, and have been on a journey to try and get the eXoDOS project to work. At the moment I am stuck at installing Launchbox that is part of eXoDOS v6, which seems to be v13.8. I found from the event viewer that it is due to the Launchbox.exe is not able to find a dll file. I tracked it down, so I know the file exists in this location. Application: LaunchBox.exe CoreCLR Version: 6.0.1623.17311 .NET Version: 6.0.16 Description: The process was terminated due to an unhandled exception. Exception Info: System.IO.FileNotFoundException: Could not load file or assembly 'CefSharp.Core, Version=83.4.20.0, Culture=neutral, PublicKeyToken=40c4b6fc221f4138'. The specified module could not be found. File name: 'CefSharp.Core, Version=83.4.20.0, Culture=neutral, PublicKeyToken=40c4b6fc221f4138' ---> System.IO.FileNotFoundException: Could not load file or assembly 'M:\eXoDOS\ThirdParty\Chromium\CefSharp.Core.dll'. The specified module could not be found. File name: 'M:\eXoDOS\ThirdParty\Chromium\CefSharp.Core.dll' at System.Runtime.Loader.AssemblyLoadContext.LoadFromPath(IntPtr ptrNativeAssemblyLoadContext, String ilPath, String niPath, ObjectHandleOnStack retAssembly) at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath) at System.Reflection.Assembly.LoadFile(String path) at Unbroken.LaunchBox.Windows.Desktop.Program.<>c.ManageFocusParser(Object ) at Unbroken.LaunchBox.Windows.Desktop.Program.<>c.CustomizeDistributedParam(Object sender, ResolveEventArgs e) at System.Runtime.Loader.AssemblyLoadContext.InvokeResolveEvent(ResolveEventHandler eventHandler, RuntimeAssembly assembly, String name) at System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(RuntimeAssembly assembly, String assemblyFullName) at Unbroken.LaunchBox.Windows.Desktop.App..ctor() at Unbroken.LaunchBox.Windows.Desktop.Program.Main(String[] args) First I disabled windows defender and any firewall, and ran the executable as administrator. No cigar... Second I assumed a .NET issue and had the windows fully updated. This did not fix the issue either. My skill-set seems to end here on troubleshooting this issue, and I am hoping a kind soul in here can point me in the right direction. Any help will be appreciated Edited September 16 by Nuitarius Quote Link to comment Share on other sites More sharing options...
sundogak Posted September 16 Share Posted September 16 Something doesn't make sense on your paths. The third party folder is part of Launchbox install. ExoDos files are within the Launchbox directory (see snip below for working setup). Your Third party folder is in a parent folder of "ExoDos". Other than the issue you are having it will potentially cause others both with LB and ExoDOS. You are also using an older version of LB is up at 13.16 so would install LB first then merge in EXO files (he has info on how to do). Quote Link to comment Share on other sites More sharing options...
Nuitarius Posted September 17 Author Share Posted September 17 20 hours ago, sundogak said: Something doesn't make sense on your paths. The third party folder is part of Launchbox install. ExoDos files are within the Launchbox directory (see snip below for working setup). Your Third party folder is in a parent folder of "ExoDos". Other than the issue you are having it will potentially cause others both with LB and ExoDOS. You are also using an older version of LB is up at 13.16 so would install LB first then merge in EXO files (he has info on how to do). Hi sundogak, So the weird path you are referring to I assume is the path that fails during execution of the LaunchBox.exe file? The event viewer entry is what it is, so I do not know what to think about that information. The Launchbox v13.8 I am running is the one that is part of the eXoDOS package, so I would assume that eXoDOS should work with that version. I have downloaded the v13.16 from here and will definitely try and install that and then try that out. The manual says that it should work, so no harm in trying. Thanks for the that, I will get back when I have more information Quote Link to comment Share on other sites More sharing options...
C-Beats Posted September 17 Share Posted September 17 This error almost always means that your virus scanner quarantined a file it shouldn't have. Running the install over your install should put it back in place (assuming it doesn't quarantine it again). When doing make sure you point the installer to your LaunchBox folder and not let it point to \\LaunchBox\LaunchBox\ like it likes to do when selecting the LB folder via it's browse tool. If you don't have the installer for the version you're using you can reach out to support@unbrokensoftware.com and ask them for a download link for it. Quote Link to comment Share on other sites More sharing options...
Nuitarius Posted September 17 Author Share Posted September 17 Ah, I think I know what you meant with the weird path now This is a screendump of the eXoDOS v6 directory after I ran the "Setup eXoDOS.bat" that the manual said I had to run. This path is definitely different from yours @sundogak I cannot find in the manual anything on me having to rearrange the directories, so I assume this is they way they want it? Quote Link to comment Share on other sites More sharing options...
Nuitarius Posted September 17 Author Share Posted September 17 9 minutes ago, C-Beats said: This error almost always means that your virus scanner quarantined a file it shouldn't have. Running the install over your install should put it back in place (assuming it doesn't quarantine it again). When doing make sure you point the installer to your LaunchBox folder and not let it point to \\LaunchBox\LaunchBox\ like it likes to do when selecting the LB folder via it's browse tool. If you don't have the installer for the version you're using you can reach out to support@unbrokensoftware.com and ask them for a download link for it. Hi C-Beats, I am assuming, when you say re-install, that you mean re-install LaunchBox? If so, then I have actually not installed LaunchBox (I see my mistake in my first post). I am just using the one that was a part of the eXoDOS project. So it was already present, just not working. But I will try and install the 13.16 that I can download from here and try and get the eXoDOS to work with that version. Hopefully that will clear up any issue with any dll's. I have disabled all anti virus and firewall for now just in case. I will come back as soon as I have more information. Quote Link to comment Share on other sites More sharing options...
Solution C-Beats Posted September 17 Solution Share Posted September 17 Just now, Nuitarius said: I am assuming, when you say re-install, that you mean re-install LaunchBox? Yeah, that's what was meant 1 minute ago, Nuitarius said: But I will try and install the 13.16 that I can download from here and try and get the eXoDOS to work with that version. Should work flawlessly. Installer doesn't touch data files or the folders eXo collection puts stuff in so you're safe to run the installer over that build. Quote Link to comment Share on other sites More sharing options...
Nuitarius Posted September 24 Author Share Posted September 24 I got the launchbox to work. I installed the newest version. Now everything is up and running except for running games. I can install games, configure games and start the game. DOSbox will run and I can see I get into the game, but there is never anything else than black screen (both window and fullscreen mode). It is clear here that X-COM has entered "GEOSCAPE". Has anyone seen this before? 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.