Jump to content
LaunchBox Community Forums

MadK9

Members
  • Posts

    540
  • Joined

  • Days Won

    13

Posts posted by MadK9

  1. 1 hour ago, spycat said:

    dfkbl.zip is still supported in MAME 0.240
    akatana.zip and sdoj.zip are no longer supported.

     

    dfblk.zip with the crc i gave is the original way of loading the hacked rom as it was not available in mame.

    sdoj.zip has never been a file in mame

     

    This post got me curious as the original Knuckles (DoDonPachi Saidaioujou) rom hack you had to replace the dfkbl.zip for it to work and as such the file failed crc checks, but could still be run, then mame in 0.239 added ddpsdoj.zip as the official rom file, but the rom file was never released, Then in December the correct crc u2 file was posted to the net but was removed after a few hours and didn't apear anywhere else. But with a bit of hunting it can be found fairly easy with the correct crc. This version ddpsdoj.zip can be dropped in mame 0.239 and can run with no crc errors and plays as normal (I do recommend using arcade64 and using the overclock feature) 

     

    Adding this for completeness

    Name: ddpsdoj.zip
    Size: 72650161 bytes (69 MiB)
    CRC32: E087EB9E
    CRC64: CDB83BA3C815765F
    SHA256: f8c5f8f31d42f57b545982ad25e71cf6bdc7fd8ca5dc319c6395c1b1ef732a18
    SHA1: ed1c3668d4453b88b191d53399cf80e866c985e0
    MD2: 77b8bb7cfc0a69e6ac3a1a88ea20ae24
    MD4: 2f2d007fad40f98f24222d04ff111381
    MD5: c6b5b49f5da5304a465594f29176cbbd
    SHA384: d32c2ad49065ac3853ffe3ba8fbce21560f1a2ed214c0559f87a87c3204ed10eea7618a6d43836605e1f7d5cb32df596
    SHA512: 0452190daa4ca5cb969205f3164f30844f1e28c5c22bf6b68a55118473bbfa94bef774455fb4fb60a2cd824fec8372a4c676e13645d82550d14d732949247f16
    

    image.thumb.png.2238e135dc8048516b2e69df09ff3a38.png

    • Like 1
  2. As some of you may know, Mame recently removed Akai Katana and DoDonPachi Saidaioujou after a request by the licence holder. With that they left the option open for it to be re-enabled for self builds, with that in mind i will NOT be posting a version with them re-enabled on here. I recommend adding a second mame emulator to your build, running and older 0239 no-nag and place the two rom files 

    Name: akatana.zip
    Size: 75082428 bytes (71 MiB)
    CRC32: DF6ABD9A
    CRC64: 40C8ED449674F17F
    SHA256: C0B1D5A2E43C220A579420498E19E7551FFBB8AE94B039AC56BF6CE6FE43A0FE
    SHA1: 702355C99BCCB087DDDBFCA2925C18CAC0E383F1
    
    Name: dfkbl.zip
    Size: 69877891 bytes (66 MiB)
    CRC32: ED20E790
    CRC64: 43394584527B8870
    SHA256: 0DBC704453AE5081749A19E67D06F215FA3051B523764E286E48E36D43860ABC
    SHA1: A3FAC1D53567EFA28E0A7A7C356AE00DACAE3DF6

    in that extra/old version of mame, and in LB add the games as normal but set the emulator to the additional emu and point the roms to the correct path. This will allow you to update mame and roms as normal and these two games will be left alone and work as normal.

    • Like 1
    • Thanks 1
  3. 13 hours ago, Jason Carr said:

    Unfortunately there's always going to be tradeoffs, unless we have servers all over the world, which would be prohibitively expensive. 5 minutes to download a 250MB update might seem like a long time, but users in the US were sometimes seeing updates take a half hour for that same 250MB file because the servers were in the Netherlands, which was borderline unacceptable. Those deep-sea cables can only transfer so well, apparently, though I would have hoped for better speeds. The speeds may improve in the future, but unfortunately we can only do what we can do.

    Yeah no worries Jason, it does seem to be a lot better today, i just had visions of it going back to the way it was with downloads going at like 30kb/s. So its all good.

    • Like 1
  4. @Jason Carr Well things just got worse for me here in the UK, gone backwards close to how it was before the move to the Netherlands hosting.  Seeing very slow speeds, 5mins to get the newest beta, and the update meta was slow as well, not quite as slow as it was a few years ago, but very noticable. I get why stuff needs to change, but it wasn't an enjoyable time back then, and im hoping it doesn't fall back to the same levels. 

    Im on a gigabit fibre, with no issues, tested files from around the world just to make sure, and speeds were all very reasonble. 

     

  5. Mame No-Nag Updated Monthly, Current Version:

    View File

    NOTE: There are changes to UI navigation, Pause and Save/Load savestates have changes made in 0.263

    please read the whatsnew.txt to see the extent of the change and what they mean in regards to what you emulate.

    whatsnew.txt

    **This removes the nag screen that informs you if a rom doesn't work correctly, or if at all, if you use this no nag, then please do NOT go to the mame support site with issues with games, please only use if you understand that there will be no help from anyone at mamedev as you are using a modified version of mame.

     

    Contents: mame.exe - Normal Mame with Nags removed. (Note mame no longer carries the 64 in its exe name changed by Devs in 0.229)

    It's advisable to download the full mame official pack and install it, then just overwrite the exe with the replacement, this covers any changes the mame devs may have made to the support files.

    After you have done this, make sure you copy the folders artwork, ctrlr, cheat, hlsl, ini, folders and the ini files from the root of your original mame folder, and move/copy them to the new install.  

    If you are using your own installed/setup of mame then make sure you also set in the mame.ini  'Skip_gameinfo  1'

    If you got Launchbox to setup mame for you when asked, you only need to replace the exe and play.

     

    As some are not sure about  False Positives, and report a virus was detected, As goes for all versions i upload, they are all ran through virustotal before i upload, and if by any chance something did end up with an issue it would be noticed very quickly after upload and would be removed/restricted.

     

    0.263 - https://www.virustotal.com/gui/file/7a7f544e444450865109ea61748c57eaeb1c3618e0259889760411cf6140d115?nocache=1

     

    All NEW versions of the No-Nag will be posted in this download thread only, if you wish to get the new releases every month, either follow myself or the thread, As the download section will not show any new releases.


     

    • Like 4
    • Thanks 3
  6. Mame 0.238 No-Nag

    View File

    NOTE: This does NOT interfere with the Leader boards at all.

    **This removes the nag screen that informs you if a rom doesn't work correctly, or if at all, if you use this no nag, then please do NOT go to the mame support site with issues with games, please only use if you understand that there will be no help from anyone at mamedev as you are using a modified version of mame.

    mame.exe - Normal Mame with Nags removed. For Version 0.238 (Note mame no longer carries the 64 in its exe name changed by Devs in 0.229)

    It's advisable to download the full 0.238 official pack and install it, then just overwrite the exe with the replacement, this covers any changes the mame devs may have made to the support files.

    After you have done this, make sure you copy the folders artwork, ctrlr, cheat, hlsl, ini, folders and the ini files from the root of your original mame folder, and move/copy them to the new install.  

    make sure in the mame.ini file you have  the following set.

    Skip_gameinfo  1


     

    • Like 1
    • Thanks 2
  7. @pofo14 them guides are out out of date, there is instructions on mamedev on how to compile, you just need to make sure you know what to change, check for mkchamp diffs, and just use a text editor to change the files, these will nearly always be released about 2 weeks after the main release,  using actual diffs can be a pain in the ass to use and get right.

    https://www.mamedev.org/tools/

    http://forum.arcadecontrols.com/index.php?topic=64298.0

     

    None of it is really difficuly to do, the only time it could be difficult is, if there are major changes to the files that need editing.

     

    The diff files are just text, you can read the contents in any text editor, and the information is easy to read.

    for example

    +++ src/frontend/mame/ui/mainmenu.cpp	2021-10-29 22:43:02.508332401 +1100
    @@ -167,6 +167,9 @@
     
     	item_append(menu_item_type::SEPARATOR);
     
    +	// DISABLE SELECT NEW MACHINE & FAVORITES
    +	if (!machine().options().skip_gameinfo())
    +	{
     	if (!mame_machine_manager::instance()->favorite().is_favorite(machine()))
     		item_append(_("Add To Favorites"), 0, (void *)ADD_FAVORITE);
     	else

    The above shows the file mainmenu.cpp needs to be edited, the @@ denotes the line where change are going to occur, then line directly under this is what you are looking for, and you edit will be UNDER this line, the next part shows 3 lines all with a + sign this is code that you need to add placing it after the previous line you found (do not add the + sign). The next two lines show what should follow after you added the edits.

    Go through the whole diff, its only 2 files that will need editing, and very small changes, then using the current mame msys64-2020-11-03 setup (make it easy for yourself and install to your root of your C drive so you end up with the mysys folder in the root of C, you do not need to update the mysys tool set, so now make your src folder in the root of the mysys folder then just unpack the mame src code to that folder, 

    then make a batch/cmd file and in that file, add the folowing. and place this file in the src folder where you unpacked the mame source too.

    set CONFIG_ARCHITECTURE=x64
    call ..\win32\env.bat
    make -j5 PTR64=1 TOOLS=0 STRIP_SYMBOLS=1

    NOTE:  -j5 is how many jobs to run concurrently,  i personally set mine between 10-12 but only do this if you have a very good multi core CPU, don't go above 5 if you only have a quadcore or less.

    Addition:

    Ignore any errors you may see when building, these are normal, if you have made a mistake in your edits, you will know when the cmd window just closes and you end up with no mame.exe

    If your make fails for any reason then delete all the files from the src folder and unpack and re-edit again.

     

  8. Check you have the correct bios files for picodrive in retroarch's system folder.

    https://docs.libretro.com/library/picodrive/

    thats all there is to picodrive, its should just work after that, if you are still having issues with it, it could be bad game dumps.

     

    just to add to the info the correct checksums for the bios files are as follows. 

    Name: bios_CD_E.BIN
    Size: 131072 bytes (128 KiB)
    CRC32: D344F125
    CRC64: E42EAAFC5F5DFBC7
    SHA256: 11619BF93C86A67E63A6D543B9337C0E325B9426E638A07D0D7F259A979A9A72
    SHA1: 523B3125FB0AC094E16AA072BC6CCDCA22E520E5
    BLAKE2sp: E697CA515C987DB92F411B1D6D76166D2FCCED9547A8ACF3B3E554B13A037AEB
    
    
    Name: bios_CD_J.bin
    Size: 131072 bytes (128 KiB)
    CRC32: 9D2DA8F2
    CRC64: 0F30C52B95F0DFFE
    SHA256: 923EB9DA740F98AB1572085E3D351E2C0982DF0906B0B99EFB68A9997C94CF8F
    SHA1: 4846F448160059A7DA0215A5DF12CA160F26DD69
    BLAKE2sp: 2BEB663E4EC50C026C7EC67787413416450F17B21AF552971C22C915319FCB27
    
    
    Name: bios_CD_U.bin
    Size: 131072 bytes (128 KiB)
    CRC32: 9F6F6276
    CRC64: 99A406BFD5196F20
    SHA256: B1C2036B79467514EAAA69C76E5BA83801621E821059CAA53CB921A0B21E3AF4
    SHA1: 5ADB6C3AF218C60868E6B723EC47E36BBDF5E6F0
    BLAKE2sp: DDE0BD70363327ACF5582A579C5054B6B3DBB2E2149D030C60CC1D465C206FB0

     

  9. Mame 0.237 No-Nag

    View File

    NOTE: This does NOT interfere with the Leader boards at all.

    **This removes the nag screen that informs you if a rom doesn't work correctly, or if at all, if you use this no nag, then please do NOT go to the mame support site with issues with games, please only use if you understand that there will be no help from anyone at mamedev as you are using a modified version of mame.

    mame.exe - Normal Mame with Nags removed. For Version 0.237 (Note mame no longer carries the 64 in its exe name changed by Devs in 0.229)

    It's advisable to download the full 0.237 official pack and install it, then just overwrite the exe with the replacement, this covers any changes the mame devs may have made to the support files.

    After you have done this, make sure you copy the folders artwork, ctrlr, cheat, hlsl, ini, folders and the ini files from the root of your original mame folder, and move/copy them to the new install.  

    make sure in the mame.ini file you have  the following set.

    Skip_gameinfo  1


     

  10. 3 hours ago, JoeViking245 said:

    But I don't know if AHK can "detect" a button press from a Wiimote.  I know it can from an Xbox 360 controller (and of course, a keyboard).

    Wii Motes on the PC are acting as a mouse, so should be able to use mouse functions.

    There was an app called somthing like wiihotkey, it should still be on the autohotkey forums somewhere, that enabled a lot of functions to be mapped to the wiimote, not sure if its still about, but that may work if you can find it, and would be easy to run from an ahk before the emu is run.. (don't quote me on it, its been a long time since i used that app, and may not do exactly as you want.)

  11. 7 hours ago, C-Beats said:
    12 hours ago, faeran said:

    Fixed: Drag and dropping images to Add/Edit Game window, when you don't have any images already, is working again (introduced in 12.0 beta 1)

    @MadK9 @Rlad Can I get one of you to confirm this is fixed for you?

    @C-Beats Did a quick test and seems to be back to normal, also checked the right click in notes and that also seemed to fine.

    Thanks again.

×
×
  • Create New...