|
MAME 0.162 and softlists
#340567 - 05/27/15 11:41 PM
|
|
|
Hi,
How are you supposed to launch a game from a softlist now? Before 0.162 I'd do e.g: mess genesis sonic
But that doesn't seem to work anymore.
Code:
mame genesis sonic
"sonic" approximately matches the following
supported software items (best match first):
EDIT: It does work, but you need the hash folder, silly me.
Edited by Calamity (05/27/15 11:54 PM)
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: Calamity]
#340570 - 05/28/15 12:22 AM
|
|
|
Yup it still works 
|
|
|
|
Re: MAME 0.162 and softlists
[Re: Calamity]
#340594 - 05/28/15 06:44 AM
|
|
|
> Hi,
>
> How are you supposed to launch a game from a softlist now? Before 0.162 I'd do e.g:
> mess genesis sonic
>
> But that doesn't seem to work anymore.
>
>
> mame genesis sonic
>
> "sonic" approximately matches the following
> supported software items (best match first):
>
>
> EDIT: It does work, but you need the hash folder, silly me.
it had always needed the hash folder, otherwise the emulator cannot foresee what "sonic" is 
also, while we absolutely encourage to use the shortcut "mame system game" to launch emulation with simple systems, you shall be aware that such usage limits you in some situations, and you might want to keep in mind that there also exists the more complete command line "mame genesis -cart sonic"
In particular, you shall be aware that
1. the former syntax does not allow you to lock multiple games through a passthru cart (e.g. Sonic & Knuckles + Sonic or the Game Genie), while the latter syntax gives you such a possibility (with "mame genesis -cart sk -cart2 sonic")
2. with computer games spanning on multiple disks, the emulator will try to load as many disks as possible in the floppy drive because this is the most convenient solution with many systems (so e.g. a 8-disk game in a system with 2 drives will have its first 2 disks mounted), but in some cases the game might expect you to only mount the first disk in drive 1 and then wait for more precise instructions... in this case you can overcome the wrong assumption by using "mame system -flop1 game"
3. the media switch allows you to play also games which are not in the softlist, like homebrew games and translated games, by launching "mame genesis -cart C:/mygamepath/myTranslatedGame.bin"
that said, have fun
|
|
|
|
Re: MAME 0.162 and softlists
[Re: etabeta]
#340606 - 05/28/15 02:34 PM
|
|
|
Taking advantage of the question I do have an advanced one. Since unlike floppys and cartridges, cdroms are not supported to be switched on the fly because it crashes the emulator when you hit the "[software list]" option, with any of these commands you can load Lunar 2:
Code:
mame64.exe psj lunar2et
mame64.exe psj -cdrom lunar2et
mame64.exe psj -cdrom1 lunar2et
Question is some software list games do have more than one disc, how do you load anything other than disc 1 without setting the full path?
Code:
mame64.exe psj -cdrom "F:\MAME\softlist\psx\lunar2et\lunar 2 - eternal blue (japan) (disc 3) [slps-02083].chd"
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3135
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340613 - 05/28/15 03:02 PM
|
|
|
> Taking advantage of the question I do have an advanced one. Since unlike floppys and
> cartridges, cdroms are not supported to be switched on the fly because it crashes the
> emulator when you hit the "[software list]" option, with any of these commands you
> can load Lunar 2:
> mame64.exe psj lunar2et
> mame64.exe psj -cdrom lunar2et
> mame64.exe psj -cdrom1 lunar2et
>
> Question is some software list games do have more than one disc, how do you load
> anything other than disc 1 without setting the full path?
>
> mame64.exe psj -cdrom "F:\MAME\softlist\psx\lunar2et\lunar 2 - eternal blue (japan)
> (disc 3) [slps-02083].chd"
In those cases, I believe, you need to use the internal UI and 'replace' the disc with another image just as you'd take out the former disc out of the console and put in a new one and close the cover. I'm not sure if there is a method of pre-loading all the discs at once.
|
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340624 - 05/28/15 05:30 PM
|
|
|
> Since unlike floppys and
> cartridges, cdroms are not supported to be switched on the fly because it crashes the
> emulator when you hit the "[software list]" option,
they should be changed like floppies and carts.
if the emulator crashes, then there is a bug but it's the first time I see it reported (BK2K4 was able to finish Lunar 2, so I had always assumed it was working, but maybe he was not launching the game from softlist)
I'll look into it ASAP
|
|
|
| R. Belmont |
|
Cuckoo for IGAvania
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 9716
|
|
Loc: ECV-197 The Orville
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340625 - 05/28/15 05:31 PM
|
|
|
> Taking advantage of the question I do have an advanced one. Since unlike floppys and
> cartridges, cdroms are not supported to be switched on the fly because it crashes the
> emulator when you hit the "[software list]" option, with any of these commands you
> can load Lunar 2:
It shouldn't crash the emulator (and AFAIK it doesn't currently).
|
|
|
|
Re: MAME 0.162 and softlists
[Re: etabeta]
#340627 - 05/28/15 06:26 PM
|
|
|
It's been like that since forever at least for me. If I do for example a "mame64.exe psj" and then load lunar2et via the softlist, the emulator crashes like this.
Code:
C:\Emus\MAME>mame64.exe psj
-----------------------------------------------------
Exception at EIP=00000000025205CE (open_disk_image(emu_options&, game_driver con
st*, rom_entry const*, chd_file&, char const*)+0x005e): ACCESS VIOLATION
While attempting to read memory at 0000000000000010
-----------------------------------------------------
RAX=0000000000000000 RBX=000000000A76B470 RCX=00000000003CA750 RDX=0000000013BE2
180
RSI=00000000002286C0 RDI=00000000139CA160 RBP=0000000000228150 RSP=0000000000228
0D0
R8=0000000012A4B900 R9=0000000013BF5A90 R10=0000000000000014 R11=8101010101010
100
R12=0000000000228450 R13=0000000000228260 R14=000000000A76B4D0 R15=00000000139CA
160
-----------------------------------------------------
Stack crawl:
0000000000228300: 00000000025205CE (open_disk_image(emu_options&, game_driver
const*, rom_entry const*, chd_file&, char const*)+0x005e)
00000000002285A0: 0000000002590847 (media_auditor::audit_one_disk(rom_entry co
nst*, char const*)+0x00f7)
0000000000228660: 0000000002590CC3 (media_auditor::audit_software(char const*,
software_info*, char const*)+0x0243)
00000000002287A0: 00000000025706DE (ui_menu_control_device_image::load_softwar
e_part()+0x014e)
0000000000228850: 0000000002571053 (ui_menu_control_device_image::handle()+0x0
6f3)
00000000002288A0: 000000000254D1D9 (ui_menu::ui_handler(running_machine&, rend
er_container*, unsigned int)+0x0039)
0000000000228950: 000000000251A4F8 (ui_manager::update_and_render(render_conta
iner*)+0x00a8)
00000000002289D0: 000000000256FBFE (video_manager::frame_update(bool)+0x004e)
0000000000228A30: 000000000247F65E (screen_device::vblank_begin()+0x02de)
0000000000228AA0: 000000000247F915 (screen_device::device_timer(emu_timer&, un
signed int, int, void*)+0x0265)
0000000000228B40: 00000000024A03B9 (device_scheduler::timeslice()+0x0179)
0000000000228BA0: 00000000024AD4F8 (running_machine::run(bool)+0x0188)
000000000022F690: 00000000024A1C4B (machine_manager::execute()+0x024b)
000000000022F840: 00000000025474EB (cli_frontend::execute(int, char**)+0x0d9b)
000000000022FDF0: 00000000014CDBE4 (utf8_main(int, char**)+0x0174)
000000000022FE50: 00000000028ECCFE (wmain+0x007e)
000000000022FF20: 00000000004013CA (__tmainCRTStartup+0x024a)
000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018)
000000000022FF80: 0000000076CD59CD (BaseThreadInitThunk+0x000d)
000000000022FFD0: 0000000076F0B981 (RtlUserThreadStart+0x0021)
If I do the same with segacd and load say the first lunar I get this:
Code:
C:\Emus\MAME>mame64.exe segacd
halt slave
clear reset slave
resume slave
-----------------------------------------------------
Exception at EIP=00000000025205CE (open_disk_image(emu_options&, game_driver con
st*, rom_entry const*, chd_file&, char const*)+0x005e): ACCESS VIOLATION
While attempting to read memory at 0000000000000010
-----------------------------------------------------
RAX=0000000000000000 RBX=000000000A652E40 RCX=000000000032A750 RDX=000000001431A
790
RSI=00000000002286C0 RDI=00000000142E7E10 RBP=0000000000228150 RSP=0000000000228
0D0
R8=0000000014099C70 R9=000000001D22ADC0 R10=0000000000000014 R11=8101010101010
100
R12=0000000000228450 R13=0000000000228260 R14=000000000A652EA0 R15=00000000142E7
E10
-----------------------------------------------------
Stack crawl:
0000000000228300: 00000000025205CE (open_disk_image(emu_options&, game_driver
const*, rom_entry const*, chd_file&, char const*)+0x005e)
00000000002285A0: 0000000002590847 (media_auditor::audit_one_disk(rom_entry co
nst*, char const*)+0x00f7)
0000000000228660: 0000000002590CC3 (media_auditor::audit_software(char const*,
software_info*, char const*)+0x0243)
00000000002287A0: 00000000025706DE (ui_menu_control_device_image::load_softwar
e_part()+0x014e)
0000000000228850: 0000000002571222 (ui_menu_control_device_image::handle()+0x0
8c2)
00000000002288A0: 000000000254D1D9 (ui_menu::ui_handler(running_machine&, rend
er_container*, unsigned int)+0x0039)
0000000000228950: 000000000251A4F8 (ui_manager::update_and_render(render_conta
iner*)+0x00a8)
00000000002289D0: 000000000256FBFE (video_manager::frame_update(bool)+0x004e)
0000000000228A30: 000000000247F65E (screen_device::vblank_begin()+0x02de)
0000000000228AA0: 000000000247F915 (screen_device::device_timer(emu_timer&, un
signed int, int, void*)+0x0265)
0000000000228B40: 00000000024A03B9 (device_scheduler::timeslice()+0x0179)
0000000000228BA0: 00000000024AD4F8 (running_machine::run(bool)+0x0188)
000000000022F690: 00000000024A1C4B (machine_manager::execute()+0x024b)
000000000022F840: 00000000025474EB (cli_frontend::execute(int, char**)+0x0d9b)
000000000022FDF0: 00000000014CDBE4 (utf8_main(int, char**)+0x0174)
000000000022FE50: 00000000028ECCFE (wmain+0x007e)
000000000022FF20: 00000000004013CA (__tmainCRTStartup+0x024a)
000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018)
000000000022FF80: 0000000076CD59CD (BaseThreadInitThunk+0x000d)
000000000022FFD0: 0000000076F0B981 (RtlUserThreadStart+0x0021)
My rompath in mame.ini is like this:
Code:
rompath F:\MAME\romset;F:\MAME\chd;F:\MAME\softlist;roms
Never reported it because I though it was known.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340630 - 05/28/15 08:10 PM
|
|
|
I can confirm using the [software list] selector causes a crash with stack crawl.
You can easily avoid this problem though by not using that option in the internal UI and instead using the drive letters to point to the exact image file to get a successful load of the game.
|
|
|
|
Re: MAME 0.162 and softlists
[Re: B2K24]
#340634 - 05/28/15 09:29 PM
|
|
|
Thank you. I don't want to sound as if I'm requesting anything, but now I feel like I should mention this and ask if is it a normal behavior with floppies.
Taking for example x68000, when I load a disk via the softlist menu it loads right away. However, when I load a disk using the file manager it prompts me to select the access mode. I take it the softlist menu sets the disk as read only in automatic and if I ever want a disk to be writable or diffed I must extract the zip/7z content and load it via the file manager menu. Is that right?
I'm sorry for the bother.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340638 - 05/28/15 11:00 PM
|
|
|
> Thank you. I don't want to sound as if I'm requesting anything, but now I feel like I
> should mention this and ask if is it a normal behavior with floppies.
>
> Taking for example x68000, when I load a disk via the softlist menu it loads right
> away. However, when I load a disk using the file manager it prompts me to select the
> access mode. I take it the softlist menu sets the disk as read only in automatic and
> if I ever want a disk to be writable or diffed I must extract the zip/7z content and
> load it via the file manager menu. Is that right?
>
> I'm sorry for the bother.
No bother at all
I'm happy to answer and try to help where I can and know how.
Regarding your question that behavior sounds correct, but I'm not 100% exactly sure.
Hopefully a Dev or a more knowledgeable expert can give you the answer to that.
I'm guessing that behavior seems correct AFAICT
I know with some cart systems when I was full path loading, it wouldn't work when I pointed it to a zip. I had to extract the archive.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: etabeta]
#340640 - 05/28/15 11:04 PM
|
|
|
> (BK2K4 was able to finish Lunar 2, so I had always assumed it was working,
> but maybe he was not launching the game from softlist)
> I'll look into it ASAP
This is correct I don't tend to use the softlist when it comes to psx and psu because the list seems very preliminary and I can't read Japanese
Before the merge I used this syntax and then when the game expected the disc change it's easily done in the internal UI with no problems.
Quote:
mess64 -rompath "J:\MESS\roms" -hashpath "J:\MESS\hash" psu -mc1 "J:\MESS\software\psu\card1.mc" -cdrom "J:\Lunar 2 - Eternal Blue Complete (USA) (Disc 1).cue"
|
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340666 - 05/29/15 11:45 AM
|
|
|
> Thank you. I don't want to sound as if I'm requesting anything, but now I feel like I
> should mention this and ask if is it a normal behavior with floppies.
>
> Taking for example x68000, when I load a disk via the softlist menu it loads right
> away. However, when I load a disk using the file manager it prompts me to select the
> access mode. I take it the softlist menu sets the disk as read only in automatic and
> if I ever want a disk to be writable or diffed I must extract the zip/7z content and
> load it via the file manager menu. Is that right?
yeah for the moment disks from softlist are read-only because MESS does not yet support addressing write-to-diff for floppy disks (and you don't want to write to the good dumps available in the softlist, or the checksums would be messed up )
as soon as we get to supporting write-to-diff you will have that option too
|
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340946 - 06/02/15 02:39 PM
|
|
|
> Never reported it because I though it was known.
well, known issues are the ones logged at MT, and I have never seen this specific problem being mentioned... so no, it was not known
however, thanks to your report we have discovered it now and not in 2020
in conclusion, I have added a temporary workaround to the crash when auditing the CHD during emulation and current git tree does not crash anymore. it's not the final solution, but for average users it's all that is needed while I search for a better fix
|
|
|
|
Re: MAME 0.162 and softlists
[Re: etabeta]
#340960 - 06/02/15 05:13 PM
|
|
|
I admit I don't check mametesters. I rarely would report anything and its front-page it's a big turn off: "We'll evaluate first if you are worth our time so meanwhile go bug Mame Chat".
These bugs not being mentioned before tells so much about how often users make use of softlists which is a shame. Now that both projects are merged this will change though. The cdrom crash exists even before I asked about why MESS didn't prompt for a cartridge just like MAME empty driver does.
I hope I'm not sounding ungrateful or anything, it's a relief I could be of some help. I appreciate the response and it's a good thing mere questions never intended as requests will be fixed next release. At least for me this will turn into a more enjoyable MAME experience.
|
|
|
| B2K24 |
|
MAME @ 15 kHz Sony Trinitron CRT user
|
|
|
|
|
|
Reged: 10/25/10
|
|
Posts: 2663
|
|
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340964 - 06/02/15 05:55 PM
|
|
|
> These bugs not being mentioned before tells so much about how often users make use of
> softlists which is a shame.
I'm not sure that this is necessarily true.
In your example about lunar2et and most other machines in the softlist, if you execute *mame64 psj lunar2et* it loads the game without any kind of crash and the same goes for other CD related machines as well when softlist loading.
Although the more crash cases that are caught, reported and fixed are always a good thing. Thanks for your efforts.
|
|
|
| Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3135
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: MAME 0.162 and softlists
[Re: BIOS-D]
#340967 - 06/02/15 06:21 PM
|
|
|
> I admit I don't check mametesters. I rarely would report anything and its front-page
> it's a big turn off: "We'll evaluate first if you are worth our time so meanwhile go
> bug Mame Chat".
The main page writeup is simply fact and not meant to be mean sprited or a turn-off. In fact, it was hoped that people would respect the effort being made to keep everything clean that they would understand the initial delay. I'll admit the solution is not the most elegant and the whole process could be explained better, I'm sure. The initial delay only comes when you first signup to the site and generally it is 24 hours or less before an Administrator (I am the only regular one at the moment) can take the time to make sure is the user is known, fake and/or purposely using a proxy or otherwise. The suggestion to use EmuChat is for those who haven't the patience to wait out the process and are compelled to report their bug immediately. You can sign up there and post here - no biggie and when you are authorized to Tester that is it, free reign. I would hope you would consider signing up sometime anyway.
The reason it is this way was that some time ago we had a rash of users (might have been just a couple) who would purposely post junk report, leave nonsense notes and push dozens of reports for no reason and otherwise damage the database causing a lot of confusion and cleanup work by everyone involved. After adding the initial delay MameTesters has turned into a much saner place where we generally have much better reports in place because of it. Anyway, everything is subject to change and the stance might be reevaluated sooner or later.
|
|
|
Index 
Threaded 
MAME 0.162 and softlists
Reply
[Re: 
