KGC2ROMS v1.1 - The Konami's Game Collection ROMs extractor

Página 1/3
| 2 | 3

Por Louthrax

Prophet (2436)

imagem de Louthrax

05-01-2015, 02:15

Here's the updated version of this tool that extracts ROMs from Konami's Game Collection disk images:

Download it here: kgc2roms1.1.zip

It works on MSX-DOS and Win32, and can create both SCC+ and SCC versions of the ROMs.

v1.1 changelog:

  • Fixed boot-code bug (was causing issues on openMSX).
  • Support for original 64KB SD Snatcher cartridge.
  • New SCC detection pattern added (pause in TwinBee now mutes the sound).
  • Added padding option. 128KB makes all ROMs work fine in openMSX and blueMSX.
  • Changed the "patching-letters" indicators.

Here's the help file for more details:

                                 KGC2ROMS 1.1
                                 ============

                      coded by Louthrax in January 2015
                 

KGC2ROMS is a tool to extract ROM images from Konami's Game Collection  disks.
Created ROMs can be either SCC or SCC+.

Sources are  provided under  the Creative  Commons Attribution-ShareAlike  4.0
International license (<a href="https://creativecommons.org/licenses/by-sa/4.0/" title="https://creativecommons.org/licenses/by-sa/4.0/">https://creativecommons.org/licenses/by-sa/4.0/</a>).

Compared to the existing ROM conversions:

    * All  26 ROMs  are dumped,  in both  SCC and  SCC+ mode  (some games were
      previously not available in SCC mode).
      
    * No more  random crashes in   Knightmare or TwinBee  (these crashes  were
      happening only on non-Turbo machines, it now works on all MSXs).

    * Correct set-up of SCC or SCC+ mode at boot time (no more need to specify
      it in your ROM loader).

    * Unified and more compact loader.
    
    * Support for  original 64KB SD  Snatcher cartridge. Gradius  and Twin Bee
      can't be converted in this mode.

MSX-DOS  2 and  Win32 versions  of the  tool are  provided (KGC2ROMS.COM   and
KGC2ROMS.EXE  respectively).  Just type  KGC2ROMS  at the  command  prompt and
select the SCC mode to start extraction. You can also select a padding for the
SCC ROMs size. 128KB will make your ROMs more compatible with emulators.

You  must  have the  following  disk images  files  in the  same  directory as
KGC2ROMS:

* KGC1.DSK
    CRC32:      113fe20c
    TOSEC name: "Konami Game Collection - Volume 1 (1988)(Konami)(Disk 1 of 2)[SCC]"

* KGC2.DSK
    CRC32:      b5a0f2b3
    TOSEC name: "Konami Game Collection - Volume 2 (1988)(Konami)(JP)[SCC]"

* KGC3.DSK
    CRC32:      6575f8da
    TOSEC name: "Konami Game Collection - Volume 3 (1988)(Konami)(JP)[SCC]"

* KGC4.DSK
    CRC32:      a3f9a236
    TOSEC name: "Konami Game Collection - Volume 4 (1988)(Konami)(JP)[SCC]"

* KGCS.DSK
    CRC32:      faacf3a6
    TOSEC name: "Konami Game Collection Special (1989)(Konami)(JP)[SCC]"
 

The following ROM files will be created:
 
    kmare.rom.rom   Knightmare
    aadventu.rom    Antarctic Adventure
    yieark1.rom     Yie Ar Kung-Fu
    yieark2.rom     Yie Ar Kung-Fu 2

    boxing.rom      Konami's Boxing
    tennis.rom      Konami's Tennis (non-SCC)
    vhustler.rom    Video Hustler
    holymp1.rom     Hyper Olympic 1 (non-SCC)
    hsports2.rom    Hyper Sports 2

    twinbee.rom     Twin Bee
    scobra.rom      Super Cobra
    sjaguar.rom     Sky Jaguar
    tpilot.rom      Time Pilot (non-SCC)
    gradius.rom     Gradius

    soccer.rom      Konami's Soccer
    pingpong.rom    Konami's Ping Pong
    golf.rom        Konami's Golf (non-SCC)
    holymp2.rom     Hyper Olympic 2 (non-SCC)
    hsports3.rom    Hyper Sports 3

    pippols.rom     Pippols
    hrally.rom      Hyper Rally
    rfighter.rom    Road Fighter
    tsururin.rom    Tsururin Kun
    hsomen.rom      Hyper Somen
    tawase.rom      Title Awase
    goboard.rom     Go Board

Warning: The new ROMs might not be recognized correctly yet in emulators using
CRC checks. You might have to specify the ROM type manually.

The letters  displayed during  the extraction  process are  indicating what is
patched. You should get the following output if everything goes well:

SCC+ mode:
    Opening kgc1.dsk...
    Creating kmare.rom... AAAAAAAAAAAAABAJJJ
    Creating aadventu.rom... AAAAAAAAABAABAJJJ
    Creating yieark1.rom... AAAAAAAAABAAAAABAJJJ
    Creating yieark2.rom... AAAAAAAAAAAAABAJJJ
    Opening kgc2.dsk...
    Creating boxing.rom... AAAAAAAAJJJ
    Creating vhustler.rom... AAAAAAAAAAAAABAJJJ
    Creating hsports2.rom... AAAAAAAAAAAAABAJJJ
    Creating tennis.rom...
    Creating holymp1.rom...
    Opening kgc3.dsk...
    Creating twinbee.rom... AAAAAAAAAAAAABAJJJJJJJ
    Creating scobra.rom... AAAAAAAAABAJJJJJJ
    Creating sjaguar.rom... AAAAAAAAAAAJJJJJJ
    Creating tpilot.rom...
    Creating gradius.rom... JJJ
    Opening kgc4.dsk...
    Creating pingpong.rom... AAAAAAABJJJ
    Creating soccer.rom... AAAAAAAAAAAAABAJJJ
    Creating hsports3.rom... AAAAAAAAAAAAABAJJJ
    Creating holymp2.rom...
    Creating golf.rom...
    Opening kgcs.dsk...
    Creating hrally.rom... AAAAABJJJ
    Creating pippols.rom... AAAAAAABJJJ
    Creating rfighter.rom... AAAAABJJJ
    Creating goboard.rom... AAAAAAAAAAAAJ
    Creating tawase.rom... AAAAAAAAAAAAJ
    Creating tsururin.rom... AAAAAAAAAAAAJ
    Creating hsomen.rom... AAAAAAAAABAJ
    Done!

SCC mode:
    Opening kgc1.dsk...
    Creating kmare.rom... AAAAAAAAAAAAABAIFJGGGGGGGGHHFCCJFJ
    Creating aadventu.rom... AAAAAAAAABAABAIFJGGGGGGGGHHFCCJFJ
    Creating yieark1.rom... AAAAAAAAABAAAAABAIFJGGGGGGGGHHFCCJFJ
    Creating yieark2.rom... AAAAAAAAAAAAABAIFJGGGGGGGGHHFCCJFJ
    Opening kgc2.dsk...
    Creating boxing.rom... AAAAAAAAIFJGGGGGGGGHHFCCJFJ
    Creating vhustler.rom... AAAAAAAAAAAAABAIFJGGGGGGGGHHFCCJFJ
    Creating hsports2.rom... AAAAAAAAAAAAABAIFJGGGGGGGGHHFCCJFJ
    Creating tennis.rom...
    Creating holymp1.rom...
    Opening kgc3.dsk...
    Creating twinbee.rom... AAAAAAAAAAAAABAJJFCJFCEEEEJIFJGGGGGGGGHHFCCJFJ
    Creating scobra.rom... AAAAAAAAABAIFJGGGGGGGGHHFCCJFJIFJGGGGGGGGHHFCCJFJ
    Creating sjaguar.rom... AAAAAAAAAAAIFJGGGGGGGGHHFCCJFJIFJGGGGGGGGHHFCCJFJ
    Creating tpilot.rom...
    Creating gradius.rom... DDDFCCEEEEDDDDDDFCCEEEEIFJGGGGGGGGHHFCCJFJ
    Opening kgc4.dsk...
    Creating pingpong.rom... AAAAAAABIFJGGGGGGGGHHFCCJFJ
    Creating soccer.rom... AAAAAAAAAAAAABAIFJGGGGGGGGHHFCCJFJ
    Creating hsports3.rom... AAAAAAAAAAAAABAIFJGGGGGGGGHHFCCJFJ
    Creating holymp2.rom...
    Creating golf.rom...
    Opening kgcs.dsk...
    Creating hrally.rom... AAAAABIFJGGGGGGGGHHFCCJFJ
    Creating pippols.rom... AAAAAAABIFJGGGGGGGGHHFCCJFJ
    Creating rfighter.rom... AAAAABIFJGGGGGGGGHHFCCJFJ
    Creating goboard.rom... AAAAAAAAAAAAIFGGGGGGGGHHFFDFJ
    Creating tawase.rom... AAAAAAAAAAAAIFGGGGGGGGHHFFDFJ
    Creating tsururin.rom... AAAAAAAAAAAAIFGGGGGGGGHHFFDFJHIH
    Creating hsomen.rom... AAAAAAAAABAIFGGGGGGGGHHFFDFJ
    Done!

Have fun !

Louthrax


v1.1 changelog:
    * Fixed boot-code bug (was causing issues on openMSX).
    * Support for original 64KB SD Snatcher cartridge.
    * New SCC detection pattern added (pause in TwinBee now mutes the sound).
    * Added  padding option.  128KB makes  all ROMs  work fine  in openMSX and
      blueMSX.
    * Changed the "patching-letters" indicators.
Entrar ou registrar-se para comentar

Por Louthrax

Prophet (2436)

imagem de Louthrax

05-01-2015, 02:31

Some technical details :

  • Patching the ROMs to 128KB make them run correctly on both blueMSX and openMSX (result with smaller values may vary, you'll need to add checksums in your emulator database).
  • The "Patch for 64KB SD Snatcher" generates special ROMs that will only run on 64KB SD Snatcher cartridges. You can launch them with SCROM or ROMLOAD. Thanks to gdx for the idea of this option !
  • SCC versions will also work on SCC+ cartridges. I'd be cursious to see if there's a game where SCC+ really makes an audible difference.
  • I have no 128KB expanded SD Snatcher or Snatcher cartridges (well, I have both original ones, but I don't want to damage them !). So I have not been able to test Gradius or Twin Bee on real Konami hardware. Please let me know if someone can do that. I'd be curious to see if the "normal" dump works on a 128KB SD Snatcher ? (if pages 0-7 are filled with added RAM, it should).

Por gdx

Enlighted (6103)

imagem de gdx

05-01-2015, 10:53

You are a chief!

Is it possible to prevent the starting of game by pressing a key at launch? Smile

I found following loaders for the Konami Sound cartridge:
- SCCLOAD by Manuel Pazos (Supports only an SCC+ cartridge extended to 128KB)
- SCROM by Sean Young
- LOADROM by Trunk

I've probably forgotten one.

Por Louthrax

Prophet (2436)

imagem de Louthrax

05-01-2015, 12:30

gdx wrote:

You are a chief!
Is it possible to prevent the starting of game by pressing a key at launch? Smile

I found following loaders for the Konami Sound cartridge:
- SCCLOAD by Manuel Pazos (Supports only an SCC+ cartridge extended to 128KB)
- SCROM by Sean Young
- LOADROM by Trunk

I'm using ROMLOAD by TNI. If offers a /H option to add an hotkey to disable boot, but I prefer to use the /P:0,0000,00, this just erases the "AB" header and the ROM will never restart. I was surprised by the time needed for the Snatcher and SD Snatcher cartridges to completely erase, you need to wait something like 20 or 30s to be sure that the game does not restart !

ROMLOAD offers lots of options and is really cool, there just seems to be a problem if your SCC cartridge is located in a subslot (MSX freezes and game does not start).

Por gdx

Enlighted (6103)

imagem de gdx

05-01-2015, 12:58

Yes, we need to wait more than 10 seconds for completely erase the Sound cartridge. SC-LOAD (a other loader) has also a option to erase the "AB" code but it is not useful when the game is already running.

I have not yet tried the /H option to add an hotkey to disable boot.

Por AxelF

Champion (395)

imagem de AxelF

06-01-2015, 16:31

All works perfectly now... thanks Louthrax Smile

Por Wild_Penguin

Hero (644)

imagem de Wild_Penguin

20-10-2015, 16:03

Hi,

I don't get any SCC sound in ROMs converted into SCC+ mode in OpenMSX, if I load them directly (as if they were a cartridge). ROMs I've dumped into SCC mode do work in OpenMSX with SCC sound, however.

It does not matter if I have chosen to load an SCC(-I) extension; I've tried the SCC+, SCC, Snatcher and SD Snatcher sound carts. But if I load them into, say, a virtual MegaFlashRom SCC+, they do work (didn't try others).

Is this intentional / expected? I mean, I just can't pop a SCC+-enabled ROM with the SCC+ in another slot and play? Should I use the plain SCC versions with emulators (as there, probably, is no audible difference)?

Thanks for your work in any case, Louthrax!

Por mars2000you

Enlighted (6430)

imagem de mars2000you

20-10-2015, 16:32

It's an intentional limitation in openMSX that does not have direct support for SCC+ roms, contrary to blueMSX.

However, you can use the following workaround :

* Create a DSK file with the following files : MSXDOS.SYS - COMMAND.COM - ROMLOAD.COM - the SCC+ game rom - AUTOEXEC.BAT

* The AUTOEXEC.BAT file needs to contain this command (for the game named as gamesccp) :

romload /5 /s gamesccp.rom

* Insert this disk in drive A and a SCC-I cartridge in a slot before launching the emulated machine in openMSX

Btw, this workaround should be added to the openMSX manual !!! Wink

P.S. In blueMSX, the SCC+ roms can be played directly, you just need to insert manually the rom and select the SCC+ mapper (because the roms generated by Louthrax tool are not in the database).

Por Wild_Penguin

Hero (644)

imagem de Wild_Penguin

20-10-2015, 16:47

Hi

Thanks mars2000you! Ah, I never though that the SCC+ extensions actually have RAM in them to load games into =). Making a disk image is trivial, but just a little bit more work (also - just because I'm curious, I might do some automated audio dumps with SCC and SCC-I to see if there is or indeed is not any difference, as postulated bu Louthrax above - if I have the time).

Por Manuel

Ascended (19298)

imagem de Manuel

20-10-2015, 20:25

mars2000you: it's not a workaround, it's how it works on the real machine...

Por mars2000you

Enlighted (6430)

imagem de mars2000you

20-10-2015, 21:12

It can viewed as a workaround because the openMSX developers don't want to add direct SCC+ support. Just like for CAS files : the Nyyrikki script is also a way to bypass the absence of direct support in openMSX for CAS files.

Página 1/3
| 2 | 3