Playing roms directly from archive-which systems work?

Do you have a link? I’m not sure if this is the right site since I can’t find it http://www.mamedev.org/index.php

Yeah, just go to their latest release downloads section and grab the 32 or 64bit binary package. You can open the .exe with 7zip and extract chdman.exe from there. Or just run the package’s .exe to extract everything and grab chdman out of wherever you extract it to.

1 Like

Can I change it to the following for cdi files? Would they work with lakka for dreamcast?

for /r %%i in (*.cue, *.cdi) do chdman createcd -i “%%i” -o "%%~ni.chd

Im not sure if cdi work for that. I remeber converting 100’s of my DC games and i now have cdi and chd games.

1 Like

You can try it, but I’m not sure it will work. CDI versions are crappy dumps generally though. Many had FMV or music quality downgraded or completely ripped out of the games to fit GDROM games on CDROMs. Redump GDI images are what you want.

1 Like

Awesome info Awakened. Do you know if it works with those silly redump games with multiple bins? Been a pain converting them to single bin cue with cdmage one at a time… guess i could just try! heh

Edit: Seems to have worked on one that i tried. Will have to test the game works when i have more time.

Yeah, chdman converts multi bin dumps no problem.

1 Like

Do GDI dumps have a really small gdi file with multiple raw and bin files? I only started looking at GDI roms and I’m not sure if I’ve found the correct files. I tried testing the bat with one I found and it wouldn’t run.

Yeah, the GDI files function just like CUEs from what I’ve read. I guess I converted my GDI’s to CHD one by one from the command prompt before I found the batch script, so I didn’t test those with it. I don’t see why they wouldn’t work with it though. If you know how to use the command prompt, the syntax is:

chdman createcd -i "filename.gdi" -o "filename.chd"

Even if it doesn’t work, you might get some error output that can help troubleshoot.

Great :slight_smile: . Now only if i could figure out why they dont launch in LaunchBox :confused:

I was an idiot, I forgot to put chdman.exe in the same directory.

Which core specifically for the different sega systems and the psx? I’m using RC5 from http://static.kivutar.me/ and I can’t find the core

In the updater they are called:

Playstation (Beetle PSX)
Sega MS/GG/MD/CD (Genesis Plus GX)

I think the HW variant of Beetle supports it too. I use Windows nightlies, so I’m not sure how getting the latest cores in Lakka works.

Is there a core that can play chd dreamcast roms?

Both Reicast and Redream support CHD. But only Redream supports the newer CHD format the latest chdman outputs. I’m not sure what version of chdman you’d have to use to get Reicast compatible CHDs. But Redream is probably going to replace Reicast and hopefully even Demul as it improves over time.

Hello, everyone. I would like some information about the archive (zip) files that retroarch can use. I realised 2 things in particular: the first is that if the zip file contains a folder inside which there are files, retroarch does not see the folder the second is that if there is a large number of files inside the zip file, retroarch sees nothing. Well my questions are: is it possible to make retroarch see subdirectories in zip files? is it possible to make retroarch see a large number of files in the zip file? thank you

Hi blunayelf

I don’t have an answer for your question but curious as to which systems/roms use folders within a zip? Is this how they have been downloaded? In my experience, I have used zips in the past but due to having plenty of storage now, have gone back to individual files (a26, lnx, jag, etc). The only cores I use zips with are for arcade (fbneo and mame). Multiple files (ps1, ps2, dreamcast, etc) can be merged into one file using chdman.

How are you scanning these files? Automatic using a database (in my case, can be problematic) or manually, by selecting each option.

:slight_smile:

ciao Graham thank u for your reply i’m using rom of snes, genesis, gameboy and so on. yes i donwloaded entire collection of rom divided for system, and i founded them like this.

I see. For roms such as Snes, Genesis and Gameboy, they can either be in zip format (one file inside, such as *.smc, *.gen and *.gmb) or individually like game.smc, game.gen and game.gmb. Game being the name of a particular game. For storing (management) of roms, I have chosen the format below:-

roms
--->Atari
------>2600
---------> Store 2600 roms here
--->Nintendo
------>Gameboy
---------> Store Gameboy roms here

You will also need the BIOS for particular systems. These need to be placed in the “System” folder. The other thing you need to be aware of are the naming of roms (for boxart, screenshots, etc). For reference, match against this https://thumbnails.libretro.com/. If placing your roms inside zips, make sure the actual rom name matches.

:slight_smile:

@blunayelf

To more directly answer your question, it’s not an issue of RA being able to read multiple files or a folder in a zip, it’s an issue of that structure not being correct for emulation.

RA cannot tell which file, among multiple files, that you want to load… and there is no need for a folder.

You will have to restructure your files.

Generally speaking, the file extension will give RA the information it needs to make the correct cores visible in the core selection dialog, so it is to your advantage to have the roms not in zip format.

The exception is arcade roms, which can have multiple files inside i.e.

1943.zip/
         bm.7k
         bm04.5h
         bm05.4k
         bm06.10a
         bm07.11a
         bm08.12a
         bm09.14a
         bm1.12a
         bm10.10c
         bm10.7l
         bm11.11c
         bm11.12l
         bm12.12c
         bm12.12m
         bm13.14c
         bm14.5f
         bm15.10f
         bm16.11f
         bm17.12f
         bm18.14f
         bm19.10j
         bm2.13a
         bm20.11j
         bm21.12j
         bm22.14j
         bm23.8k
         bm24.14k
         bm25.14l
         bm3.14a
         bm4.12c
         bm5.7f
         bm6.4b
         bm7.7c
         bm8.8c
         bm9.6l
         bme01.12d
         bme02.13d
         bme03.14d
2 Likes