rageking

scree - thank you for your post, your screen shots solved my issue (or made me aware of what the issue is, by giving me something else to try). While everything I have, other than Colecovision stuff works via LB using explicit path names, the Colecovision stuff seems to only work using relative names. It doesn't make sense to me as to why, especially when I can use those same explicit paths to start things from the command-line, but can't argue with the results, and I can replicate and resolve the issue by changing the path format. I previously had all my emulators sitting at the same level as LB, and was using explicit paths for showing where they reside, and where the roms reside. It's a little cleaner than placing the emulators inside of LB (like in your example set-up)....but if not everything works set-up that way, then it needs to change(lol). In addition, I guess that's a better set-up for portability - as then, you just need to grab the LB folder and you get everything needed for everything to work, if you ever decide to relocate it. Many thanks for everyone who took the time to try to help! I'm sure I'll be back starting some additional questions on other topics. Rage

I'd also support this in a BIG way, would be a MAJOR help to have the option for "delete" to actually delete the LB entry but the rom file as well. I'm losing my mind going through and having to manually jump back and forth to delete those I don't want. Would love to see this...I'd be using it like crazy right now, lol.

I do have the BIOS files, as you already concluded. =) As far as MAME version - I've tried a couple. I could use the -now abbreviation as well, but that doesn't change my results. I did try it just to see, as I'm hoping for anything/something to solve this problem. Also, more detail for whatever it's worth. I can also start all of these successfully using MESS from the command line....but through LaunchBox, I get the same failed results.

After much effort and reading, I am unable to get Colecovision ROMs to start using Launchbox. None of them. I can start them without issue via MAME directly. I have things set, such that it should be producing the same start-up request from Launchbox, exactly as I am doing it via the MAME command-line. All fail to start, instead I see MAME fire-up, "loading machine 0%" and it closes right back down. I also see what appears to be a command window appear just before (in a blip) MAME comes up, and it closes the same way when MAME shuts down. It's acting as though it can't find the file, but everything set as it is, it should (and again, does when I perform it on the command line to MAME directly, from any folder location, as I am using full paths for both MAME and the ROM...although I have tried it many different ways). Current Emulator set-up: Emulator Path: P:\Emulators\mame0168\mame.exe (or whichever MAME version, I've tried several, 0169/mame64 included) Default Command Line Parameters: -skip_gameinfo -nowindow coleco -cart P:\LaunchBox\Games\Colecovision\ Options Checked: Don't use quotes for filename; No space before filename Sample shown: mame.exe -skip_gameinfo -nowindow coleco -cart P:\LaunchBox\Games\Colecovision\File Under Game Edit: Emulation is enabled ROM Filename: P:\LaunchBox\Games\Colecovision\filename.zip (where filename is any game filename). I have also tried with the file being a .zip, .col, .rom(which they needed to be for ColEM...which also loaded them successfully from the command line). Any help would be greatly appreciated. I've taken a lot of time to research this, and try different settings, to no avail. I'll feel stupid if it's something simple, but still hoping that it is....lol.