Entrance | Main Index | Search | New user | Login | Who's Online | FAQ | Rules

MAMEWorld >> EmuChat
View all threads Index   Threaded Mode Threaded  

Pages: 1

peter ferrie
MAME Fan
Reged: 10/06/10
Posts: 46
Send PM


inidv3cy and initdv2jo broken in 0.149u1?
#312201 - 07/30/13 01:58 AM
Reply to this post Reply


I didn't see any reports in MAMETesters, so maybe no-one else has the problem.
However, at least on my system, the picdata is full of 0xff bytes, so the file to decrypt cannot be found.
Can anyone confirm?



B2K24
MAME @ 15 kHz Sony Trinitron CRT user
Reged: 10/25/10
Posts: 2663
Send PM


Re: inidv3cy and initdv2jo broken in 0.149u1? new [Re: peter ferrie]
#312202 - 07/30/13 02:26 AM
Reply to this post Reply


confirmed here as well


Quote:


C:\MAME64>mame64 -window inidv3cy
317-unk-com.pic NOT FOUND (NO GOOD DUMP KNOWN) (tried in inidv3cy naomi2 inidv3c
y)
WARNING: the game might not run correctly.
Real PIC binary found
0000000000225FD0: 000000000168AAC7 (m6502_device::asl_zpx_partial()+0x0127)
0000000000226090: 0000000002985BB2 (DSP56K::Sbc::disassemble(astring&) const+0
x03c2)
00000000002272F0: 0000000000F84BF9 (delegateoid*)>::delegate(delegate_baseoid*, _noparam, _noparam>::traits::member_func_type, char const*
, suprloco_state*) [clone .constprop.23]+0x0049)
0000000000227470: 0000000002030CE2 (IRQHandler(void*, int)+0x0032)
0000000000227610: 0000000002063CE1 (okim9810_device::sound_stream_update(sound
_stream&, int**, int**, int)+0x0201)
0000000000227970: 000000000206487C (zsg2_device::device_start()+0x003c)
0000000000227B60: 000000000206547D (sp0256_update(device_t*, sound_stream*, vo
id*, int**, int**, int)+0x00bd)
000000000022F360: 0000000001FA69A7 (cpu_disassemble_upd7725(legacy_cpu_device*
, char*, unsigned int, unsigned char const*, unsigned char const*, int)+0x2047)
000000000022F8A0: 000000000211685E (jpeg_idct_11x11+0x032e)
000000000022FE10: 000000000168DAD3 (m6502_device::bvs_rel_full()+0x01a3)
000000000022FE60: 0000000002343F8C (device_t* driver_device_creatortate>(machine_config const&, char const*, device_t*, unsigned int)+0x027c)
000000000022FF20: 00000000004013F0 (__tmainCRTStartup+0x0270)
000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018)
000000000022FF80: 0000000076CB652D (BaseThreadInitThunk+0x000d)
000000000022FFD0: 000000007714C521 (RtlUserThreadStart+0x0021)
GDROM: Could not find the file to decrypt.

C:\MAME64>mame64 -window initdv2jo
gds-0026.chd CHD NEEDS REDUMP
gds-0026.rom NOT FOUND (NO GOOD DUMP KNOWN) (tried in initdv2jo initdv2j naomi2
initdv2jo)
WARNING: the game might not run correctly.
0000000000225FD0: 000000000168AAC7 (m6502_device::asl_zpx_partial()+0x0127)
0000000000226090: 0000000002985BB2 (DSP56K::Sbc::disassemble(astring&) const+0
x03c2)
00000000002272F0: 0000000000F84BF9 (delegateoid*)>::delegate(delegate_baseoid*, _noparam, _noparam>::traits::member_func_type, char const*
, suprloco_state*) [clone .constprop.23]+0x0049)
0000000000227470: 0000000002030CE2 (IRQHandler(void*, int)+0x0032)
0000000000227610: 0000000002063CE1 (okim9810_device::sound_stream_update(sound
_stream&, int**, int**, int)+0x0201)
0000000000227970: 000000000206487C (zsg2_device::device_start()+0x003c)
0000000000227B60: 000000000206547D (sp0256_update(device_t*, sound_stream*, vo
id*, int**, int**, int)+0x00bd)
000000000022F360: 0000000001FA69A7 (cpu_disassemble_upd7725(legacy_cpu_device*
, char*, unsigned int, unsigned char const*, unsigned char const*, int)+0x2047)
000000000022F8A0: 000000000211685E (jpeg_idct_11x11+0x032e)
000000000022FE10: 000000000168DAD3 (m6502_device::bvs_rel_full()+0x01a3)
000000000022FE60: 0000000002343F8C (device_t* driver_device_creatortate>(machine_config const&, char const*, device_t*, unsigned int)+0x027c)
000000000022FF20: 00000000004013F0 (__tmainCRTStartup+0x0270)
000000000022FF50: 00000000004014F8 (mainCRTStartup+0x0018)
000000000022FF80: 0000000076CB652D (BaseThreadInitThunk+0x000d)
000000000022FFD0: 000000007714C521 (RtlUserThreadStart+0x0021)
GDROM: Could not find the file to decrypt.

C:\MAME64>



TafoidAdministrator
I keep on testing.. testing.. testing... into the future!
Reged: 04/19/06
Posts: 3135
Loc: USA
Send PM


Re: inidv3cy and initdv2jo broken in 0.149u1? new [Re: peter ferrie]
#312203 - 07/30/13 03:12 AM
Reply to this post Reply


> I didn't see any reports in MAMETesters, so maybe no-one else has the problem.
> However, at least on my system, the picdata is full of 0xff bytes, so the file to
> decrypt cannot be found.
> Can anyone confirm?

From source:
ROM_REGION( 0x4000, "pic", ROMREGION_ERASEFF)
// PIC/sticker unknown
ROM_LOAD("317-unk-com.pic", 0x00, 0x4000, NO_DUMP )

So you get the message:
"GDROM: Could not find the file to decrypt."

MT bug:
http://mametesters.org/view.php?id=4502

Resolved because it is expected behavior without the PIC dump. So, no bug to report. I've updated the setnames in the report to be accurate to current MAME.



peter ferrie
MAME Fan
Reged: 10/06/10
Posts: 46
Send PM


Re: inidv3cy and initdv2jo broken in 0.149u1? new [Re: Tafoid]
#312239 - 07/30/13 06:03 PM
Reply to this post Reply


The exit is not as clean as I expected, it looks like a crash. That's really why I was asking about it.



R. Belmont
Cuckoo for IGAvania
Reged: 09/21/03
Posts: 9716
Loc: ECV-197 The Orville
Send PM


Re: inidv3cy and initdv2jo broken in 0.149u1? new [Re: peter ferrie]
#312243 - 07/30/13 06:45 PM
Reply to this post Reply


> The exit is not as clean as I expected, it looks like a crash. That's really why I
> was asking about it.

It's intended to crash in that instance (and indeed, it always has). There is nothing more it can do.



peter ferrie
MAME Fan
Reged: 10/06/10
Posts: 46
Send PM


Re: inidv3cy and initdv2jo broken in 0.149u1? new [Re: R. Belmont]
#312284 - 07/31/13 06:52 PM
Reply to this post Reply


game_not_working?
I just wonder why it's allowed to get that far even when it's know that it can't possibly run any further.



R. Belmont
Cuckoo for IGAvania
Reged: 09/21/03
Posts: 9716
Loc: ECV-197 The Orville
Send PM


Re: inidv3cy and initdv2jo broken in 0.149u1? new [Re: peter ferrie]
#312287 - 07/31/13 09:33 PM
Reply to this post Reply


> game_not_working?
> I just wonder why it's allowed to get that far even when it's know that it can't
> possibly run any further.

I just looked at the specific code for that message. It is in fact terminating itself using the standard emu_fatalerror mechanism in the exact spot where it first becomes aware "that it can't possibly run any further". There is nothing *to* fix about what it's doing.


Pages: 1

MAMEWorld >> EmuChat
View all threads Index   Threaded Mode Threaded  

Extra information Permissions
Moderator:  Robbbert, Tafoid 
0 registered and 436 anonymous users are browsing this forum. 		You cannot start new topics
You cannot reply to topics
HTML is enabled
UBBCode is enabled
Thread views: 1799

Browser Test | Delete Cookies atom-guru atom-guru *
UBB.threads™ 6.3.2