Jump to content
LaunchBox Community Forums

cpujunkie

Members
  • Posts

    64
  • Joined

  • Last visited

Posts posted by cpujunkie

  1. does the ps3 read the Linux file system? I'm not sure on Windows how to format and copy files to a Linux formatted drive. Could boot up a live Linux distro. Format and copy over

  2. The only thing I can think of is format the drive in exfat or some kind of fat32 made for large drives. I think the 32GB drive is small enough for a normal fat32 format.

    just a guess

  3. the why on example 1 not having a -rp (rompath) is because the core has generated the ini file with that info in it so I tested it without and it worked.

    The rompath is there for the bios the mame core is looking for. In my neocdz.ini the rom path has a directory listed. You could run once, edit the corresponding ini file to fill in the rompath and not have the whole -rp c:\directory in the command line.

    I believe to be able to generate an ini file the option of mame_write_config has to be enabled and probably also mame_boot_from_cli has to be enabled in the retroarch cfg file of retroarch-core-options.cfg

  4. figured out how to copy the post

    I'm going to post this answer in a few different areas on the forum.

    I have been trying to figure out how to launch retroarch mame for the systems that don't have a stand alone core. I have finally found a mostly elegant solution

    1) Add a New Emulator - I have named mine RetroArch MAME console cores
    Add your retroarch.exe
    Make sure to check "Don't use quotes..."

    01.thumb.jpg.b91feb374b887b1df2cdc6d8f390c7f8.jpg2) Tab over to the Associated Platforms
    Here's the magic sauce
     

    example 1    "neocdz -cdrm \"%romfile%\""
    example 2    "a5200 -rp \"F:\Roms\Atari 5200\" -cart \"%romfile%\""
    example 3    "coleco -rp F:\Roms\ColecoVision\ -cart \"%romfile%\""

    02.thumb.jpg.1299958207f54d061122c0620a28fb70.jpg

    The reason for the "Don't use quotes" and adding this as a new emulator is because of the special thing we have to do to the command line
    using mostly the same arguments has standalone mame/mess you have to have all the arguments in double quotes " but because of how Windows handles long file names with spaces the locations have to be in quotes to. This throws retroarch/the windows commandline off. This is where the \ before the double quote at the beginning and the \ before the closing double quote per directory/location. Also we can use the launchbox variable %romfile% to help make this work.

    3) On top of all that you also have to specify the rompath if the mame core hasn't generated an ini with the rompath. This is needed for the bios of the core you are loading. If all your mame console bios files are in the same dir you could just use that for each entry

    04.thumb.jpg.ae1abefa83d870831a9caf6f23dab6b6.jpg
    The core will generate ini files for each system after first run.

    05.thumb.jpg.5af3fd10a374548df5ce569f80afabde.jpg

    4) I also edited my retroarch core options file. I probably enable boot to bios but I don't at the moment.

    03.thumb.jpg.2ef85689a522233643a9626cd8bf95de.jpgThere is my setup for launching roms through retroarch mame.
    I hope this helps

    • Like 3
    • Thanks 4
  5. figured out how to copy the post

    I'm going to post this answer in a few different areas on the forum.

    I have been trying to figure out how to launch retroarch mame for the systems that don't have a stand alone core. I have finally found a mostly elegant solution

    1) Add a New Emulator - I have named mine RetroArch MAME console cores
    Add your retroarch.exe
    Make sure to check "Don't use quotes..."

    01.thumb.jpg.b91feb374b887b1df2cdc6d8f390c7f8.jpg2) Tab over to the Associated Platforms
    Here's the magic sauce
     

    example 1    "neocdz -cdrm \"%romfile%\""
    example 2    "a5200 -rp \"F:\Roms\Atari 5200\" -cart \"%romfile%\""
    example 3    "coleco -rp F:\Roms\ColecoVision\ -cart \"%romfile%\""

    02.thumb.jpg.1299958207f54d061122c0620a28fb70.jpg

    The reason for the "Don't use quotes" and adding this as a new emulator is because of the special thing we have to do to the command line
    using mostly the same arguments has standalone mame/mess you have to have all the arguments in double quotes " but because of how Windows handles long file names with spaces the locations have to be in quotes to. This throws retroarch/the windows commandline off. This is where the \ before the double quote at the beginning and the \ before the closing double quote per directory/location. Also we can use the launchbox variable %romfile% to help make this work.

    3) On top of all that you also have to specify the rompath if the mame core hasn't generated an ini with the rompath. This is needed for the bios of the core you are loading. If all your mame console bios files are in the same dir you could just use that for each entry

    04.thumb.jpg.ae1abefa83d870831a9caf6f23dab6b6.jpg
    The core will generate ini files for each system after first run.

    05.thumb.jpg.5af3fd10a374548df5ce569f80afabde.jpg

    4) I also edited my retroarch core options file. I probably enable boot to bios but I don't at the moment.

    03.thumb.jpg.2ef85689a522233643a9626cd8bf95de.jpgThere is my setup for launching roms through retroarch mame.
    I hope this helps

    • Like 1
    • Thanks 1
  6. I'm going to post this answer in a few different areas on the forum.

    I have been trying to figure out how to launch retroarch mame for the systems that don't have a stand alone core. I have finally found a mostly elegant solution

    1) Add a New Emulator - I have named mine RetroArch MAME console cores
    Add your retroarch.exe
    Make sure to check "Don't use quotes..."

    01.thumb.jpg.b91feb374b887b1df2cdc6d8f390c7f8.jpg2) Tab over to the Associated Platforms
    Here's the magic sauce
     

    example 1    "neocdz -cdrm \"%romfile%\""
    example 2    "a5200 -rp \"F:\Roms\Atari 5200\" -cart \"%romfile%\""
    example 3    "coleco -rp F:\Roms\ColecoVision\ -cart \"%romfile%\""

    02.thumb.jpg.1299958207f54d061122c0620a28fb70.jpg

    The reason for the "Don't use quotes" and adding this as a new emulator is because of the special thing we have to do to the command line
    using mostly the same arguments has standalone mame/mess you have to have all the arguments in double quotes " but because of how Windows handles long file names with spaces the locations have to be in quotes to. This throws retroarch/the windows commandline off. This is where the \ before the double quote at the beginning and the \ before the closing double quote per directory/location. Also we can use the launchbox variable %romfile% to help make this work.

    3) On top of all that you also have to specify the rompath if the mame core hasn't generated an ini with the rompath. This is needed for the bios of the core you are loading. If all your mame console bios files are in the same dir you could just use that for each entry

    04.thumb.jpg.ae1abefa83d870831a9caf6f23dab6b6.jpg
    The core will generate ini files for each system after first run.

    05.thumb.jpg.5af3fd10a374548df5ce569f80afabde.jpg

    4) I also edited my retroarch core options file. I probably enable boot to bios but I don't at the moment.

    03.thumb.jpg.2ef85689a522233643a9626cd8bf95de.jpgThere is my setup for launching roms through retroarch mame.
    I hope this helps

    • Like 1
    • Thanks 1
  7. I have been working on this issue for awhile and have figured it all out. I am using retroarch mame to load systems that retroarch doesn't have stand alone cores for. When I get back at my computer I'll post the three different ways I have solved this problem.

×
×
  • Create New...