MAMEWorld Forums - EmuChat - NEOGEO/File manager bugs, has anyone the same problem?

This has been bugging me for a while, many older NEOGEO MVS games like KOF97 and older crash on start up.

C:\Emus\MAME>mame64.exe kof97

-----------------------------------------------------
Exception at EIP=00000000021B50B0 (float128_rem(float128, float128)+0x0480): ACCESS VIOLATION
While attempting to read memory at 000000002C5CA530
-----------------------------------------------------
RAX=00000000007E007E RBX=FFFFFFFFFC5F75F0 RCX=0000000014BC8D08 RDX=000000002C5CA528
RSI=0000000013BC80B7 RDI=0000000005BC308E RBP=00000000067B7F70 RSP=00000000002268A0
 R8=0000000014BEF0F0  R9=000000000E000029 R10=0000000014BEF130 R11=00000000021B5090
R12=00000000000003E7 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000
-----------------------------------------------------
Stack crawl:
  00000000002268D0: 00000000021B50B0 (float128_rem(float128, float128)+0x0480)
  00000000002269C0: 00000000021B986C (fyl2xp1(floatx80, floatx80)+0x076c)
  0000000000226B30: 00000000021E6F44 (read_metadata_vorbiscomment_+0x003f)
  0000000000226C30: 00000000021E7AAC (skip_id3v2_tag_+0x0087)
  0000000000226DF0: 00000000021E93F9 (read_subframe_fixed_+0x0284)
  0000000000227190: 00000000021EAFAB (safe_malloc_mul2add_+0x002b)
  00000000002274C0: 00000000021EBA65 (init_stream_internal_+0x0188)
  0000000000227600: 00000000021EBE99 (init_stream_internal_+0x05bc)
  0000000000227960: 00000000020D6CB7 (get_ea_mode_str(unsigned int, unsigned int)+0x0c17)
  0000000000227B50: 00000000020D76FD (d68020_tst_pcix_16()+0x006d)
  000000000022F360: 000000000201C166 (ui_draw_text_full(render_container*, char const*, float, float, float, int, int, int, unsigned int, unsigned int, float*, float*)+0x0276)
  000000000022F8A0: 000000000218739E (chd_cd_flac_compressor::~chd_cd_flac_compressor()+0x008e)
  000000000022FE10: 00000000016D1A13 (t11_device::bic_ded_ix(unsigned short)+0x00e3)
  000000000022FE60: 00000000023E270C (device_t* driver_device_creator(machine_config const&, char const*, device_t*, unsigned int)+0x023c)
  000000000022FF20: 00000000004013F0 (__tmainCRTStartup+0x0270)
  000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018)
  000000000022FF80: 00000000772A652D (BaseThreadInitThunk+0x000d)
  000000000022FFD0: 00000000773DC541 (RtlUserThreadStart+0x0021)

And this has been happening me since at least two official MAME releases. The MESS AES versions work fine.

There's this other problem with the File Manager on MESS menu. Probably unnoticed because many use front-ends.

- Lets take a MESS driver, neocdz for example.
- Load a CHD via the File Manager then exit the emulator.
- Rename or delete the path where the CHD was previously stored.
- Try to load a CHD again via the File Manager.

Evething dissapears ("empty slot", "software list", drives, dirs, files) except the "Return to Previous Menu" option.

After that you can't load a CHD again unless you force your way with the -cdrom parameter AND you load a CHD via the File Manager. If you don't, the problem repeats the next time you load the driver without the cdrom parameter. Everything gets back to normal once the emulator can locate the previous deleted path too.