Randalf

I will let you know how the new beta works, I am getting back to another 5.8 version installed elsewheres to try it. Yeah, nothing with VLC in Launchbox.xml file that I could find, I didn't check my One Drive copy

Wonderful, I was about to state I can not find anything to do with VLC in my xml file, I even installed to my C drive and did a search for VLC and nothing returned, but I have a VLC folder

I cna do that, give me a few minutes to fire it up and install it. I will let you know what I find

I bet it is, I just launched it off from my One Drive (a backup source for anything that happens) with my 64 Bit, Windows 10, Home system, no issues with the beta Execute it with the 32 bit system right off one drive, does the same thing as if I run it off my D drive

I will work on a video, I will walk through the beta install as well, maybe something in there I didn't pick up on that might have also been key and I will take a look at what Windows has to say on it and see if that has any answers I run Windows 10 Home...32 bit

Jason, I just sent mine in to you. I will also add, the error scree just posted is what I get on my system as well, same status, etc

Sure can, should I put it back to the beta version or will that matter with the xml file?

Are there any logs or details that can be pulled? Once I allow it to upgrade to beta 9 is when I no longer have access to even the interface of the program. I can go as far as even recording a video of the upgrade to the relaunch when it decides to stop working if that will help with anything even. I have no problem in duplicating for these purposes, I don't have many games loaded to begin with so restoring everything is not going to be an "end of the world" scenario for me.

I moved back to 5.8- 5.9 beta 9 is where everything stopped working for me. Everything else including other beta versions I had no problems with. I will give it a try again on a newer update, just glad I got everything backed up!

Something is a miss it seems, I went to the extreme of removing Launchbox, reinstalled 5.8. Imported, navigated, etc, no problems. Got beta installed, right back to the same place it crashes right on the settings message. I guess I will go back to 5.8 or another version and wait, I am logged into my PC as an admin. For some reason, beta does not like me.

Not sure what else I can look at and hope someone might have an idea. Got new Beta, typically launchbox and all emulators and games run off my D drive (secondary drive), everything worked good up to this point but when the update took place, the program crashed "Launchbox has stopped working" everytime the status changed to "populating settings" Rebooted the PC and got the same issue, so I run a copy I had out of the One Drive, and after the update completed, relaunched and got the same results But it appeared I didn't really get the update, because I went to a different PC, launched from my one drive and it updated again, but it was now successful. I went back to my other PC that I have hooked to my TV that I normally use, launched from One Drive, crashed in same place and same status. They both are Windows 10 computers, the only difference in respect to the OS is the primary PC is a 32 bit, and the computer I got it working well off from is a 64 bit. Curious if anyone might have any input on what could have happened. Thanks!

If you are still looking for submitters, moderators, etc (and no I will not stick around and blow in everyone's NES cartridges) I can contribute, most of my days, for now, are going to be, staring at screens playing games until I go back to work! If you are all set, great, I will go back to figuring out which game I should play next!

Thanks for the suggestion, no harm in trying, but luck is not on my side. Oh well, I am not going to worry about it too much, this is more testing for me as I am eventually going to put the MAME side of things on another PC and setup a cabinet. Just wanted to get an idea of how things are going to work to build up that arcade experience.

It is sound, I could in reality move on, but it gets annoying for me, but I did not realize about changing for just those three games (I thought I would have to change an entire platform or have some logical mess at hand) but that made it easier, sound is good, everything looks good and honestly, it is not really noticeable that a separate emulator is being used. I think I will stick with Retroarch where I can and if needed I can just switch it for that game only.

Thanks! I will check that out

Hello all, I have been trying to chase down an audio issue with (so far in my small collection) just 3 roms that produce crackling/white noise while playing. Those are Burger Time, JT-104 and Mario Bros. All arcade games use the latest Retroarch. All the other games I have work with no audio issues. I tried some other suggestions I have seen on other platforms like moving the audio up to 128, toggling sync, lowering frame rate (all within retroarch) to no avail. If I play these games out of MAME directly however, I have no issues. I am trying to avoid a mix and match of emulators if I can with the arcade games and hoping maybe there is something I have overlooked, or if for now I should use MAME for those games that don't present any issues. Everything is on a PC hooked up via HDMI to my Samsung TV. Thanks in advance.

@DOS76 the games in full screen are in color, but a weak color (best I can explain it, reminds me of an old tube tv starting to burn out) In window mode, color is great. Sound is there, sometimes choppy, I will look into the doc file and the command line, I don't know command language, (DOS commands if that counts for anything) I suppose it couldn't be too hard to figure out, but sometimes I need a simple reading to figure things out quicker. My background has been more on the Hardware side of things, more than software or language programming.

I never heard of x-padder until now, found it, got it, looks like I mapped it out right to the gamepad and minus the sound and color (which seems to be what I can expect here) but to technically say there is emulation is a success!

Thanks again for the information, I tried -s1=3 and the joystick is not responding with the emulator, I looked into the help file on making a default config file but I believe I am just over reading it not knowing what to put to map out what is up, down, and how the gamepad is detected by the emulator.

Thank you for the replies. I found my errors, had an old version apparently as I had no BIOS folders, I found a better version, found the BIOS folder, everything is working. My only challenge is determining if my logitech gamepad will work instead of using the keyboard, I read the files on the config file, for some reason figuring out how to add one is not clicking in my head here.

Is O2EM good for Odyssey 2 games? I downloaded it, and pointed to the path in launchbox where the app is, I am not sure if I am pointing to the right file or missing a command, it seems if I launch a game, the command prompt screen opens and then closes, and I get nothing no errors, no game. Any advice would be greatly appreciated. Thanks!