DannyShane Posted January 21, 2019 Share Posted January 21, 2019 (edited) Hello, I used the colecovision roms from mame 204 SL and they work in mame 204. (their extensions are "1" "2" "bin") But that set was missing some good games like "war games" that i used to play all the time, lol. so i grabbed war games from a site where their coleco vision roms are file extension ".col". and mame wont load it, and retroarch wont load it either. i have a few .col roms from another place that wont load either. so im just curious if anyone else happened to use .col roms and if so, what emulator did you use? below is my setting in mame - and this works with my mame SL roms. and below is my setting in retroarch thanks for your time Edited January 21, 2019 by Hayata made the title less broad Quote Link to comment Share on other sites More sharing options...
CDBlue Posted January 21, 2019 Share Posted January 21, 2019 The bluemsx_libretro core should work with those files. But, in order for that core to work properly you need to get the BIOS files installed in the Retroarch/System folder. Instructions on where to get those files are on the Libretro doc site: https://docs.libretro.com/library/bluemsx/ If you do not have those installed properly in Retroarch, then the core won't be able to load .col rom files. I'm not at home right now, so I can't check to see if I also had to enter any command line to get it to work, but I don't believe I had to for the retroarch core, just for stand-alone emulators. Quote Link to comment Share on other sites More sharing options...
harryoke Posted January 21, 2019 Share Posted January 21, 2019 i use mess standalone with .col files so i dont see how mame won't work as it is just mess intergrated coleco cartridge (cart) .rom .col .bin so your commandline is correct Quote Link to comment Share on other sites More sharing options...
DannyShane Posted January 21, 2019 Author Share Posted January 21, 2019 @CDBlue, thanks, i had those folders set up already and i double checked just now to make sure i have the bios, and all was good. @Harryoke, i was under the impression that mame would only run roms from a mame romset? im still learning, but ive tried mame, and just tried again and it will not run any of the roms i have that are 'non-mame' and file extension ".col" sucks because these are the games i used to play. lol and as far as troubleshooting, i downloaded one game from two different sites and they both have .col and neither will play in retroarch or mame. Quote Link to comment Share on other sites More sharing options...
fromlostdays Posted January 21, 2019 Share Posted January 21, 2019 (edited) Newer versions of MAME will indeed run non-mame roms including .col roms. You CAN get this to work in the RA version of MAME as well, but the process is way too involved as I understand it, right down to probably having to rename your roms. I have this working through rocketlauncher, which doesn't require any command lines. The problem is, because I use RL I don't know exactly how to get this working through Launchbox/MAME. But I think I can point you in the right direction. You have to add a command line to the "Associated Platforms" of the Emulator. Under Default Command Line Parameters. However, I've tried a few variations of: coleco -cart with no success, so someone who uses Launchbox/MAME will have to fill in the rest. EDIT: This would be the website where you get the command line info - I'm not sure how exactly to translate it into launchbox: https://pastebin.com/18W3EbD0 Edited January 21, 2019 by fromlostdays 1 Quote Link to comment Share on other sites More sharing options...
spycat Posted January 21, 2019 Share Posted January 21, 2019 I currently use standalone MAME 0.205 (mame64.exe) to emulate ColecoVision (console media not sw list). The system's romset aka bios, coleco.zip should contain the two files colecoa.rom 313 10031-4005 73108a.u2 The Default Command-Line Parameters for LaunchBox are coleco -cart When using MAME to emulate ColecoVision, MAME must know via it's configuration settings (ini file) where coleco.zip is. The actual ColecoVision games can be anywhere, as long as LaunchBox itself is pointed to them. The games can have the normal ColecoVision naming or be renamed to the MAME short naming, and be zipped or not. Example: Miner 2049er Starring Bounty Bob (USA).col can be renamed as mine2049.col both will work with MAME You can also do things such as zipping a Coleco named game and renaming the zip as the MAME short name. Miner 2049er Starring Bounty Bob (USA).col zipped as mine2049.zip 2 Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 21, 2019 Share Posted January 21, 2019 I have Colecovision working using stand alone Mame, I have a separate install of Mame 197 setup specifically for console and computer emulation and I just tested War Games from the No Intro rom set with the .col file extension and it works perfectly fine using the coleco -cart command line parameter. Also tested with the RA MSX core and it works there too. 1 Quote Link to comment Share on other sites More sharing options...
DannyShane Posted January 21, 2019 Author Share Posted January 21, 2019 thanks everyone. Hey LordMonkus, I installed a second mame (197 like you mentioned) and now the .col roms work when I launch them from LB using the mame 197. So thank you very much for that. I am curious why it works in 197 and 205 (as spycat says) but not in 204. that was weird. i figured it could be user error except I have both versions of mame set to use coleco -cart (in Launchbox), and I even copied and pasted the rompath to the new mame197 ini file (from the mame204 ini file). well that was odd, but either way, thanks for helping me out with this you guys. Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 21, 2019 Share Posted January 21, 2019 That is very odd indeed if you are 100% certain that your rompath and bios are correct. The only reason I have 197 is just because it was the last version I bothered to setup and have not bothered upgrading it. Quote Link to comment Share on other sites More sharing options...
DannyShane Posted January 21, 2019 Author Share Posted January 21, 2019 yeah i just copied my rompath from 204 ini to 197 ini. (because i have two rom folders and didn't feel like writing it all out again. lol). and i didnt even move the roms.. in LB, i just right clicked and said "launch in mame197". and it worked. oh well,. yeah after setting all of this up, im not ever upgrading either until.... mame finishes emulating "the grid"... then i have to upgrade because me and my son used to play that in the arcade so i just "NEED" it. LOL Quote Link to comment Share on other sites More sharing options...
fromlostdays Posted January 21, 2019 Share Posted January 21, 2019 Also got this working through launchbox/MAME. Had to update the mame.ini to point to the bios (thanks spycat!). Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 21, 2019 Share Posted January 21, 2019 In my console / computer setup for Mame I just throw all my bios in the \roms folder of the Mame install, that way I don't have to do any rompath editing all. Quote Link to comment Share on other sites More sharing options...
DannyShane Posted January 21, 2019 Author Share Posted January 21, 2019 I had two folders... one was the mame roms, and the other was the mame SL roms. i put all the bios in the main mame rom folder. i was going to put them all in one folder but initially i had read somewhere where the person said not to mix them. but i dont think it woudl matter if i had mixed them. but too late now, im too nervous to start messing with them.,lol Quote Link to comment Share on other sites More sharing options...
CDBlue Posted January 21, 2019 Share Posted January 21, 2019 (edited) FYI, I just got home and tested launching some .col games via retroarch and the bluemsx libretro core... no issues for me there and the games launched just fine for me. Not sure why that would not work for you, unless the bios/machine files are not where the core expects them to be maybe? Glad you got it working via MAME at least. Edited January 21, 2019 by CDBlue Quote Link to comment Share on other sites More sharing options...
DannyShane Posted January 21, 2019 Author Share Posted January 21, 2019 thanks, yeah i probably somehow did something with retroarch. i did paste the blue machines and database folders into retroarch again (even though i had them alreayd) and i did check that the bios was there. i messed aroudn with retroarch so much i migt have messed soething up with the blue msx. Quote Link to comment Share on other sites More sharing options...
spycat Posted January 22, 2019 Share Posted January 22, 2019 MAME arcade roms and software list roms should never be placed in the same folder, as some of these games have identical rom names but completely different internals. A bit out of my depth here, but I do remember that when MESS was independent of MAME, the various software list roms were supposed to go in folders named after the systems. I don't know if this applies to the MAME/MESS all in one we have today as I don't use software lists; the simpler console/computer media approach is just fine for me. 1 Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 22, 2019 Share Posted January 22, 2019 MAME expects the SWL titles in the ROM folder in their own folders but if you edit the ini file to reflect your path you can place them anywhere 1 Quote Link to comment Share on other sites More sharing options...
epicfail Posted January 28, 2019 Share Posted January 28, 2019 On 1/21/2019 at 10:39 AM, CDBlue said: The bluemsx_libretro core should work with those files. But, in order for that core to work properly you need to get the BIOS files installed in the Retroarch/System folder. Instructions on where to get those files are on the Libretro doc site: https://docs.libretro.com/library/bluemsx/ If you do not have those installed properly in Retroarch, then the core won't be able to load .col rom files. I'm not at home right now, so I can't check to see if I also had to enter any command line to get it to work, but I don't believe I had to for the retroarch core, just for stand-alone emulators. Working for my setup, thanks! 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.