Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About hfball

  • Rank
  • Birthday 09/21/1970

Profile Information

  • Gender
  • Location
    Janesville, WI
  1. I pulled source for MameUI from git on May 4th. .221 vanilla was released today, May 19. Has anything changed for MameUI tag-221 in that time?
  2. Bingo. Rolled back to 8.3.0. Working fine now. I'm giving up on updating the mingw environment. 8.3 will do fine until it doesn't. Why does gcc release when it's bugged up like that?
  3. Here's another dump fresh off of the .lay processing. I can't find "host-mingw32.c" in my environment anywhere, so weirdness. Rebuilt environment from scratch. Tried 'master' branch instead of 'tag213.' Same problems. Compressing src/mame/layout/h2hbaskb.lay... Compressing src/mame/layout/escmars.lay... Creating ../../../../mingw-gcc/bin/x64/Release Precompiling src/emu/emu.h... Compiling src/emu/drivers/empty.cpp... internal error in mingw32_gt_pch_use_address, at config/i386/host-mingw32.c:186: MapViewOfFileEx: Attempt to access invalid address. <command-line>: fatal er
  4. Compile error on latest toolchain. Don't know what it means. Might be waiting on the new toolchain for vanilla 213 since it's not released yet. You seem to have fewer problems with the not-bleeding-edge compiler. Version line: gcc version 9.2.0 (Rev1, Built by MSYS2 project) Here's where it barfed: Compiling src/mame/drivers/aci_borisdpl.cpp... internal error in mingw32_gt_pch_use_address, at config/i386/host-mingw32.c:186: MapViewOfFileEx: Attempt to access invalid address. <command-line>: fatal error: had to relocate PCH compilation terminated. make[2]: *** [adc.make:314: .
  5. 203's looking great Robert. Thanks again.
  6. Hey Robert. I just signed in to let you know that everything is going great, and to thank you for maintaining these derivatives of MAME. Awesome work, man!
  7. Hey Robbert. I've been noticing when I come back from a game, the UI will randomly jump to the upper left-hand corner of the screen and resize itself (smaller than what I usually set it at). It's been doing this for a couple of versions now. Not sure when it started. Do I need to do something in the ini to fix it?
  8. Compiled perfectly with the latest devtools. Is there any way to change the order of the picture tabs, or is that hard coded? I thought there was, but now I can't find it.
  9. I recompiled mameui64 from the master branch instead of tag189, and it all works. Go figure. Also, the 64-bit environment doesn't puke on the Saturn device. Only the 32-bit. Go figure. Thought you'd like to know.
  10. That's so weird. I tried both of your 0.189 builds. The one on John IV's page and the one at MESSUI Place. 32-bit works. 64-bit doesn't. I'm running Windows 10 1703 x64, fully patched. Could that be it?
  11. I got these errors when trying to compile 32-bit with the latest tools. It's strange because 64-bit went off without a hitch: In file included from ../../../../../src/devices/cpu/saturn/saturn.cpp:79:0: ../../../../../src/devices/cpu/saturn/satops.hxx: In member function 'void saturn_device::saturn_exchange(int, int, int, int)': ../../../../../src/devices/cpu/saturn/satops.hxx:806:6: error: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Werror=strict-overflow] void saturn_device::saturn_exchange(int left, int begin, int count, int right) ^
  12. Zag from Mameworld here. I d/l mameui 32-bit and the softlists work perfectly along with all the other glitches that mameui64 had. So the softlists problem is a 64-bit specific problem. You should be able to reproduce it on your end. It's not anything in my config files. You probably feel like giving up on the 64-bit version entirely at this point, and I wouldn't blame you. Thanks.
  13. So I signed up, but never got a confirmation email, so now I'm seeing if I can post anyway. Please ignore.
  • Create New...