Squeeth

SUCCESS! Once I got out of my "stupid me" bubble, the issue then came up for the vcruntime140.dll. Got an AIO package I found on github for all the proper runtime packages, installed, ran the .bat and it started extracting. Once the first successful extract was completed I did a test with Xemu and it does in fact work! I'll consider this forum post issue closed, but will continue to monitor from time to time to help anyone else out if needed. Thanks again for the help @darreldearth!

Okay, disregard my last two posts...I'm obviously a little challenged at using GitHub for this and just realized I didn't have the actual utility downloaded lol Let me grab the .exe from the latest release and I'll report back.

I have screenshots attached that should help better explain the structure and placement. The first one shows the .bat file contents. The second shows the error when running the self-made .bat file. The third shows the extract-xiso.c file in the root folder of my Microsoft Xbox folder containing all the folder formatted games. Thanks again in advance.

I ended up finding a source that was compressed folder format games, so I just finished extracting those and replacing all the spaces with dashes so it's all one word. Granted they're over 8 characters long total but that shouldn't be the cause of what I got now. I have the extract-xiso.c file in the root folder of all the folder format games, created the batch file using the first code you posted. It is throwing me an error saying "'extract-xiso' is not recognized as an internal or external command, operable program or batch file." I'm wondering if the tool needs to be compiled/built or if the .c extention on the end of it needs to be removed and turned to a .bat? Thanks in advance

I did try both of those, but they seemingly hiccup when I try to do any sort of batch processing. I think what's bugging me the most is I know I had it all working a few months ago before I rebuilt my library, and now it's not working and I can't figure out why lol

Unfortunately there was no luck after double checking those things. Additionally I see on the 2nd response to that tutorial it says "Some iso's don't work in Xemu. For example from Redump." I think if I can't get the batch extract to work I may just have to find another source for them that isn't Redump

As far as I remembered, they did too...but according to their site they no longer do. I posted screenshots of what I read. It's kind of confusing to me since I swear I used to have redump ISO files. I had it setup in the past but have since rebuilt/reconfigured my library from the ground up. I'll get around to testing the command line parameters and following the guide posted tomorrow as well just to test and see what happens. Thanks for the reply, I'll update with my findings on those things tomorrow.

Hey everyone, this might be a noobish question but I figured I'd ask it anyways just to see if anyone might have any insight into this. I'm trying to use Xemu to emulate my collection of Xbox Redump ISO's and I'm getting the dreaded "Please insert disc" error. Reading up on this I found that they don't support regular ISO files and require XISO files. After searching the web I found numerous tools that can do this, but most of them are single file only. One I found was XDVDMulleter but it was not doing the job given my library is located on a mapped network drive. I found the extract-xiso utility (found here https://github.com/XboxDev/extract-xiso) and it seems to work for single files, but I was curious how I might go about doing a batch extract? I found a topic on this, however the commands discussed weren't working for me. I have my collection located at X:\Microsoft Xbox and it's all raw .iso files. Would I drop the extract-xiso.c file into this folder, shift right click and run a certain command that modifies it to run until it's processed all the files? If anyone could help, I'd greatly appreciate it. Let me know if there's any more info that's need, and thanks in advance!

Really hate to necro an older thread, but I'm still too new to fully understand using the .xml to import the media for the eShop. Do I copy and paste the .xml contents to the Metadata .xml file in my Launchbox folder? Thanks in advance for any help

Correct. After your guys input here I think I'm going to be hosting the ROMS and ISO's remotely on my network and the emulators locally. The only thing I'd host remotely as far as software goes is going to be the Launchbox folder itself to allow the portable deployment to systems local disks if they want to use Launchbox at my house. Copy the fully configured Launchbox folder to their system that I'll put on the network once I'm completely done configuring it, and then hopefully have it working like that. Edit: And ensure they have the correct network share mapped properly Awesome, thanks so much for sharing your knowledge and verifying that I'm not thinking crazy Glad to know that even though I'm a total noob to all of this, I've read and understood enough to come up with a seemingly workable solution for my crazy ideas ?

Now I'm sure I could probably find the answer with a quick Google search but with one of the posts I read in the forums here regarding emulating from a network drive, people were saying that loading ROMS from network is fine but loading Launchbox is not. I kind of assumed that's because Launchbox has numerous files to access during operation where the ROM itself is essentially "loaded" and "read" once and then good from there. So I guess I'm curious if the ROM file is continuously accessed during play or if it gets loaded into the emulator, and then that's about it? If that's the case the case then I might end up migrating the emulators to the local Launchbox folder and point Launchbox into that, as now that I've read these replies I'm starting to kind of have the "ohhhh duhhh" moment of realizing that the emulators themselves are probably continuously accessed during emulation.

Didn't even think about the latency with the VPN...very good point to consider! I guess I'll just have to wait until everything is fully setup to test it out. Thanks for the reply! :)

Hey everyone, somewhat new to Launchbox here (have used and tinkered a little on a friends setup) and I'm hoping that the question I'm about to ask isn't too "noobish" lol ? So I recently setup a "hybrid" install of Launchbox on my home desktop, and was looking to see if my ideology on making this work on my laptop makes sense. What I mean by "hybrid" install is that I have Launchbox itself installed on a local disk in my desktop (C:) and then have all of my ROMS and emulators living on a mapped network drive (X:) that lives on my Unraid server at home. I do have everything setup on my home firewall to VPN in from my laptop and have my network drives mapped on my laptop so if I'm way from home, my network share drives are accessible from my laptop. I've done some reading around and I have seen an overwhelming amount of people say that installing all emulators and ROMS to the Launchbox folder is best practice since it essentially makes it 100% portable, as Launchbox has everything contained in its own folder and it knows where to go for everything needed. So my question is that (in theory) I should be able to copy my Launchbox folder from my home desktop C drive to my laptop C drive, ensure that the X drive where all my emulators and ROMS reside is mapped and accessible as X on my laptop, and everything should work as it does on my desktop, without needing to reconfigure much...if anything? Additionally another thought I had was that once I get everything configured properly... could I copy my locally configured Launchbox folder to my mapped drive so someone who comes over may copy that Launchbox folder to their laptop or PC, and essentially have it be "plug n' play"? Thank you in advance for any help that can be given! ? I'll answer a few questions now just in case they may get asked in replies, just to save a bit of everyone's time Q: Why not put everything in the Launchbox folder locally? A: I am planning on backing up a lot of my XBOX, PS2, PS3, XBOX 360, etc. games and those will take up a lot of space that I don't have available on my desktop locally. I also just wanted a mapped drive dedicated to my library (500GB+ and counting) to keep everything organized with parity protection. I also read a bit before setting it up this way that said mapped network drives weren't an issue for ROMS, so I'm just looking to get a definite answer to my specific config/intentions to make sure I'm not thinking crazy lol. Additionally I figured with this config, it'd make it possible to provide anyone who comes over with the ability to just essentially "plug in and play", which I thought would be neat Q: How do you currently have it configured in Launchbox, and is it completely setup? A: Nothing was moved after installing Launchbox and all of the ROMS and emulators were in place on my mapped drive before touching Launchbox, just to ensure that Launchbox would have no confusion. As for being completely setup, no. I have it up and running testing Project64 and confirmed working very well, but have not yet tested my NES, SNES, Genesis, GB, GBC, or GBA emulation. I do think though in theory that once I do the initial config of each emulator though, that everything should run as well as Project64...*fingers crossed* Q: Are you trying to move it now? A: No, and don't plan to until I have everything properly setup and configured on my desktop. Once I have my library completely copied to the network share and have Launchbox running everything properly on my desktop, that is when I plan to copy the Launchbox folder to my laptop. Any other questions, please ask! I'm having a TON of fun setting this up and learning how it all does (or maybe doesn't) work, so any knowledge or insight to my configuration is greatly appreciated. Thanks again!