|
MAME 0.261 causes crash in Emu Loader, 0.260 was fine
#397464 - 11/30/23 06:01 AM
|
|
|
Using v8.9.4 of course. And yes I know about the situation with Emu Loader and its developer.
It was working fine with MAME 0.260; updating to 0.261, I got an error. Restarting gives the same error during initialization. I tried making a new instance of Emu Loader and initializing from scratch, but it gets the same error during games loading phase.
In every case, it gets to the "Adding software games to games list." stage and almost immediately gets the following error popup:
Quote:
Code:
date/time : 2023-11-29, 19:35:46, 856ms
computer name : [redacted]
user name : [redacted]
registered owner : Windows User
operating system : Windows 7 x64 Service Pack 1 build 7601
system language : English
system up time : 13 days 19 hours
program up time : 10 seconds
processors : 8x Intel(R) Xeon(R) CPU E3-1240 v3 @ 3.40GHz
physical memory : 4264/32706 MB (free/total)
free disk space : (C:) 62.70 GB (L:) 243.34 GB
display mode : 1920x1080, 32 bit
process id : $3d20
allocated memory : 215.16 MB
largest free block : 1.04 GB
executable : EmuLoader.exe
exec. date/time : 2021-10-27 03:12
version : 8.9.4.0
compiled with : Delphi 7
madExcept version : 5.1.0
callstack crc : $98c3c7e4, $e398671c, $e398671c
exception number : 1
exception class : EConvertError
exception message : 'th' is not a valid integer value.
thread $1b4c:
00463f51 EmuLoader.exe SysUtils ConvertErrorFmt
00464a20 EmuLoader.exe SysUtils StrToInt
00785c67 EmuLoader.exe uMain 23931 +17 TFormMain.GetROMFields
0078b3a0 EmuLoader.exe uMain 26256 +103 TFormMain.AddGames
007ac917 EmuLoader.exe uMain 32748 +0 TFormMain.LoadGames
007ad439 EmuLoader.exe uMain 32748 +0 TFormMain.SetGameType
007a3a1a EmuLoader.exe uMain 32748 +0 TFormMain.FormShow
004de7ad EmuLoader.exe Forms TCustomForm.DoShow
004e1779 EmuLoader.exe Forms TCustomForm.CMShowingChanged
004c6344 EmuLoader.exe Controls 4655 +53 TControl.WndProc
004c928f EmuLoader.exe Controls 6352 +33 TWinControl.WndProc
004b3d51 EmuLoader.exe ComCtrls 18754 +85 TToolBar.WndProc
004c610c EmuLoader.exe Controls 4552 +5 TControl.Perform
004c8de3 EmuLoader.exe Controls 6203 +16 TWinControl.UpdateShowing
004c8e4e EmuLoader.exe Controls 6221 +7 TWinControl.UpdateControlState
004cabde EmuLoader.exe Controls 7315 +3 TWinControl.CMVisibleChanged
004c6344 EmuLoader.exe Controls 4655 +53 TControl.WndProc
004c928f EmuLoader.exe Controls 6352 +33 TWinControl.WndProc
004def39 EmuLoader.exe Forms TCustomForm.WndProc
004c610c EmuLoader.exe Controls 4552 +5 TControl.Perform
004c4e43 EmuLoader.exe Controls 3734 +5 TControl.SetVisible
004dea2e EmuLoader.exe Forms TCustomForm.SetVisible
004e563c EmuLoader.exe Forms TApplication.Run
007eadd3 EmuLoader.exe EmuLoader 138 +52 initialization
75f8344b kernel32.dll BaseThreadInitThunk
thread $82c:
76fc0186 ntdll.dll NtWaitForMultipleObjects
7693176f KERNELBASE.dll WaitForMultipleObjectsEx
75f81a03 kernel32.dll WaitForMultipleObjectsEx
762e087c user32.dll MsgWaitForMultipleObjectsEx
762e0b7c user32.dll MsgWaitForMultipleObjects
0045f129 EmuLoader.exe madExcept CallThreadProcSafe
0045f193 EmuLoader.exe madExcept ThreadExceptFrame
75f8344b kernel32.dll BaseThreadInitThunk
>> created by thread $1b4c at:
73a778c5 gdiplus.dll
thread $3c2c:
76fc1f6f ntdll.dll NtWaitForWorkViaWorkerFactory
75f8344b kernel32.dll BaseThreadInitThunk
thread $1390:
76fc0186 ntdll.dll NtWaitForMultipleObjects
75f8344b kernel32.dll BaseThreadInitThunk
thread $12ac:
76fc1f6f ntdll.dll NtWaitForWorkViaWorkerFactory
75f8344b kernel32.dll BaseThreadInitThunk
thread $8160:
76fc1f6f ntdll.dll NtWaitForWorkViaWorkerFactory
75f8344b kernel32.dll BaseThreadInitThunk
thread $6954:
76fc0186 ntdll.dll NtWaitForMultipleObjects
0045f129 EmuLoader.exe madExcept CallThreadProcSafe
0045f193 EmuLoader.exe madExcept ThreadExceptFrame
75f8344b kernel32.dll BaseThreadInitThunk
>> created by thread $1b4c at:
739fa89c winmm.dll
Seems like maybe MAME is suddenly spitting out something somewhere it shouldn't ("th" is, as it says, certainly not an integer value). Is this ultimately MAME's problem, or Emu Loader's? And is there a workaround, or do I have to just wait for a fix on the MAME end (and make a bug report to help it along)?
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397466 - 11/30/23 03:55 PM
|
|
|
>
> Is this ultimately MAME's problem,
> or Emu Loader's? And is there a workaround, or do
> I have to just wait for a fix on
> the MAME end (and make a bug report to help it along)?
>
Sounds like an issue with emuloader. Guess you'll have to wait for someone to fix it.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397471 - 11/30/23 07:21 PM
|
|
|
EmuLoader works fine for me.
However, in the past, I would have an issue once in awhile.
For me, it turned out to be history.db. Now, I'm not a programmer, but this history.db is located in two different folders: data and history. Keep the folders and delete the two history.db files. Remove history.dat or history.xml from the history folder. Then start up EmuLoader and let the system create new history.db files. Then add your history.dat or history.xml back into the history folder.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: NewMameUser]
#397472 - 11/30/23 07:45 PM
|
|
|
> Sounds like an issue with emuloader. Guess you'll have to wait for someone to fix it.
Seems extremely unlikely anyone's going to be doing anything at all to Emu Loader ever again, given the circumstances… (._.)
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Divemaster]
#397473 - 11/30/23 07:58 PM
|
|
|
> delete the two history.db files
No dice, unfortunately. Same exact error.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397474 - 11/30/23 08:39 PM
|
|
|
> > delete the two history.db files
>
> No dice, unfortunately. Same exact error.
Perhaps you have already tried this, but: you could try to do a new/clean mame and emuloader install, with all the default settings and no additions/modifications from other sources (other than roms and the software lists), and see if that works.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397475 - 11/30/23 08:41 PM
|
|
|
> > Sounds like an issue with emuloader. Guess you'll have to wait for someone to fix
> it.
>
> Seems extremely unlikely anyone's going to be doing anything at all to Emu Loader
> ever again, given the circumstances… (._.)
True. But then again, you knew :
>
> And yes I know about the situation with Emu Loader and its developer.
>
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: mhoes]
#397476 - 11/30/23 08:52 PM
|
|
|
> Perhaps you have already tried this
I hadn't, till you mentioned it. Nope, though. Still the same error at the same stage.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397478 - 11/30/23 09:47 PM
|
|
|
As I said before EmuLoader works just fine. I've been using it for quite a few years. You probably have a corrupted or conflicted file in one of your MAME folders. Now just have to figure which one it is.
When you download a new version of MAME which files do you copy/paste into your main MAME directory?
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Divemaster]
#397479 - 11/30/23 10:45 PM
|
|
|
> As I said before EmuLoader works just fine. I've been using it for quite a few years.
I have too. But have you updated MAME to 0.261 and rescanned in Emu Loader? The new MAME just came out two days ago.
> You probably have a corrupted or conflicted file in one of your MAME folders.
With a clean new installation of MAME giving the same error, I hope not.
> When you download a new version of MAME which files do you copy/paste into your main
> MAME directory?
All of them.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397480 - 11/30/23 10:49 PM
|
|
|
Yes, I updated 2 days ago. I don't have any issues with my MAME cabinet or with my USB external drive I use with my laptop.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Divemaster]
#397481 - 11/30/23 11:24 PM
|
|
|
Hm. Are you running a complete set of ROMs and Software List ROMs? (It's the SL ROMs stage where it errors out.)
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397483 - 12/01/23 12:00 AM
|
|
|
I run arcade only. No mess software list.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397484 - 12/01/23 12:02 AM
|
|
|
> > Sounds like an issue with emuloader. Guess you'll have to wait for someone to fix
> it.
>
> Seems extremely unlikely anyone's going to be doing anything at all to Emu Loader
> ever again, given the circumstances… (._.)
Well, the source code is available. Anyone with a license for Delphi and the additional controls it uses can fork it and pick up development. It does seem somewhat unlikely, though. There doesn’t seem to be a lot of interest in developing front-ends now that MAME’s internal UI is usable enough.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397486 - 12/01/23 12:58 AM
|
|
|
>
> > When you download a new version of MAME which files do you copy/paste into your
> > main MAME directory?
>
> All of them.
That's not exactly what I meant when I said :
>
> Perhaps you have already tried this, but: you could try to do a new/clean mame and
> emuloader install, with all the default settings and no additions/modifications from
> other sources (other than roms and the software lists), and see if that works.
>
Please retry that again as explicitly stated, without the copying/pasting of any files from the old/failing install.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: mhoes]
#397487 - 12/01/23 02:08 AM
|
|
|
> > > When you download a new version of MAME which files do you copy/paste into your
> > > main MAME directory?
> >
> > All of them.
>
> That's not exactly what I meant when I said :
>
> >
> > Perhaps you have already tried this, but: you could try to do a new/clean mame and
> > emuloader install, with all the default settings and no additions/modifications
> from
> > other sources (other than roms and the software lists), and see if that works.
> >
>
> Please retry that again as explicitly stated, without the copying/pasting of any
> files from the old/failing install.
I did. You asked what files I copy when I update. The answer is all of them. When trying a fresh install, that was a different folder, filled from the self-extracting .zip.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397493 - 12/01/23 01:50 PM
|
|
|
> > > > When you download a new version of MAME which files do you copy/paste into your
> > > > main MAME directory?
> > >
> > > All of them.
> >
> > That's not exactly what I meant when I said :
> >
> > >
> > > Perhaps you have already tried this, but: you could try to do a new/clean mame
> and
> > > emuloader install, with all the default settings and no additions/modifications
> > from
> > > other sources (other than roms and the software lists), and see if that works.
> > >
> >
> > Please retry that again as explicitly stated, without the copying/pasting of any
> > files from the old/failing install.
>
> I did. You asked what files I copy when I update. The answer is all of them. When
> trying a fresh install, that was a different folder, filled from the self-extracting
> .zip.
Sorry, my bad.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397494 - 12/01/23 04:35 PM
|
|
|
For what it's worth (which, admittedly, may not be much) but: I downloaded both emuloader v8.9.4 and mame, and got the same results as you : 0260 works, and 0261 gives the error you reported somewhere during setup while parsing xml files. Sorry I cannot be of more help.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: mhoes]
#397495 - 12/01/23 06:40 PM
|
|
|
> got the same results as you
Good to have confirmation, anyway!
Now, I wonder if anyone can track down the source of this "th". I searched around in the listxml 0.261 generates, but couldn't find anything that looked like it could be the problem. It would make it easier to make a bug report with something more concrete…
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397499 - 12/02/23 01:56 AM
|
|
|
> > got the same results as you
>
> Good to have confirmation, anyway!
>
> Now, I wonder if anyone can track down the source of this "th". I searched around in
> the listxml 0.261 generates, but couldn't find anything that looked like it could be
> the problem. It would make it easier to make a bug report with something more
> concrete…
Why are you assuming it’s an issue with MAME? We do extensive validation on every MAME release to ensure the software lists and listxml output are valid. It’s far more likely to be a bug or flawed assumption in Emu Loader.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Vas Crabb]
#397500 - 12/02/23 02:26 AM
|
|
|
If it were in MAME, would not all the other front ends & CLRMAME Pro(and other rom editors) also be running into same said error?
|
Pessimist: Oh, this can't get any worse!
Optimist: Yes, it can!
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Vas Crabb]
#397501 - 12/02/23 06:25 AM
|
|
|
> Why are you assuming it’s an issue with MAME? We do extensive validation on every
> MAME release to ensure the software lists and listxml output are valid. It’s far more
> likely to be a bug or flawed assumption in Emu Loader.
Well, every version of MAME prior to this one has worked fine with Emu Loader. So that's my first thought. But of course that's why I'm wanting to see something that looks like the source of the issue — so we can figure out just what is going on.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397502 - 12/02/23 10:38 AM
|
|
|
> > Why are you assuming it’s an issue with MAME? We do extensive validation on every
> > MAME release to ensure the software lists and listxml output are valid. It’s far
> more
> > likely to be a bug or flawed assumption in Emu Loader.
>
> Well, every version of MAME prior to this one has worked fine with Emu Loader. So
> that's my first thought. But of course that's why I'm wanting to see something that
> looks like the source of the issue — so we can figure out just what is going on.
Since the software lists seem to be the issue, why don't you delete the one with newest date and see if there's any difference? 40 lists were updated during the last cycle, so doing one at a time should eventually reveal which one it is.
After identifying which one, you can restore the ones you deleted, and then have a look at the "faulty" one for anything that seems to be out of place.
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Robbbert]
#397511 - 12/05/23 07:41 AM
|
|
|
> Since the software lists seem to be the issue, why don't you delete the one with
> newest date and see if there's any difference? 40 lists were updated during the last
> cycle, so doing one at a time should eventually reveal which one it is.
>
> After identifying which one, you can restore the ones you deleted, and then have a
> look at the "faulty" one for anything that seems to be out of place.
This sounds like a sensible plan, but daunting. Even so, I set about doing it.
However, after a lot of rigamarole I won't bore everyone with, I ended up trying this:
- Set up a fresh MAME folder without configuring anything at all — no ROMs nor anything else present
- Set up a fresh Emu Loader folder
- Point the fresh Emu Loader at the fresh MAME during welcome setup
- Let scan start
Result: the exact same error in the exact same place.
Then, just for giggles, I did the same thing all over again, but this time with MAME 0.260. No errors; Emu Loader shows everything properly (all with no ROMs present of course).
It looks like the problem is happening prior to any examination of any actual ROMs or other files. So I don't know how I can exclude parts of what Emu Loader is seeing to narrow anything down…?
|
|
|
|
Re: MAME 0.261 causes crash in Emu Loader, 0.260 was fine
[Re: Atario]
#397513 - 12/05/23 10:48 AM
|
|
|
EDIT:
See what Roman said.
Edited by Robbbert (12/05/23 12:05 PM)
|
|
|
|
Solution
[Re: Robbbert]
#397514 - 12/05/23 11:04 AM
|
|
|
Go to MAME's hash folder, open "apple2_flop_clcracked.xml" in a texteditor, search for & #xA; (without the space after the &, can't figure out how this forum allows me to type it) which should be part of the "frclword" and "greetcrd" sets' info elements and remove it in there a couple of times and save the file.
After that, run a clean emuloader instance (could be that it already loaded and cached the softwarelist file somewhere...don't know).
by the way, this is valid xml ....so it's emuloader's xml parser which goes nuts...
Alternatively, you could replace the file with the .260 one...or simply don't scan software list items.
|
|
|
|
Re: Solution
[Re: Roman]
#397515 - 12/05/23 01:00 PM
|
|
|
> 

Interesting. Digging further, there are other fields in various places with other XML entities included, without problems, even LFs — but those were listed with instead, somehow. Changing these 
s to s also fixes it.
> After that, run a clean emuloader instance (could be that it already loaded and
> cached the softwarelist file somewhere...don't know).
Turns out you can delete <Emu Loader folder>\arcade\mame_softwarelist_games\apple2_flop_clcracked.* (should be three files), which removes the offending games from its lists, allowing it to initialize without error and subsequently take user input. From there you can rescan with the modified MAME hash files or whatever else.
> by the way, this is valid xml ....so it's emuloader's xml parser which goes nuts...
Yeah, not sure why it's having such a specific problem. Changing them to 
 doesn't help either; and there are plenty of other hex-encoded entities of both two and three digits that are fine (like ' and ł).
So… on the one hand, looking at the data in these two fields, these particular LFs don't actually serve any sensible formatting purpose and should therefore probably be removed on the MAME side, even if only for neatness' sake with nothing related to Emu Loader. On the other hand, I'm not sure why some LFs are being encoded as and others as 
. And I'm really not sure why Emu Loader has a problem with one and not the other.
|
|
|
|
Re: Solution
[Re: Atario]
#397516 - 12/05/23 01:17 PM
|
|
|
Small followup: it looks like Emu Loader is just straight-up removing the s when it processes the fields into its internal files, but the 
s get turned into real LFs in there, which it apparently does not like one little bit!
|
|
|
Previous 
Index 
Next 
Threaded 
MAME 0.261 causes crash in Emu Loader, 0.260 was fine
Reply
[Re: 
