I'm not sure if this thread belongs more to the Support or Game Discussion forum. When I try to run NHL 2K9 NTSC I get a "Warning - eieio not implemented" error. I tried turning off panic handlers but the game wouldn't run anyway - the farthest I got was the safety screen after which the screen turned black. It seems like it's a missing function of the emulator, the message shows no matter how I configure Dolphin and which revision I use. It is not that much of a big deal as I can play the game on my Wii at any time but maybe someone could look into it when building future revisions
My system specs: Windows 7 RC1 32bit (same thing happened on XP SP3), AMD Athlon X2 3600+, Geforce 8600GTS 256, 2GB RAM.
Sounds like some Wii IPC part not implemented, though I have no idea what a "eieio" is
.
(08-17-2009, 05:07 AM)omegadox Wrote: [ -> ]Sounds like some Wii IPC part not implemented, though I have no idea what a "eieio" is .
Well me neither
just for record, here's the screenshot of the message:
http://images48.fotosik.pl/182/90e192766016c005.jpg
In this case I use the JitIL revision but the same thing happens on IL-less one. After clicking "Yes" emu crashes and when I click "No" it just quits. If this helps in any way, a person reported exactly the same error on emuforums but with game "We Love Golf PAL". So it seems that it is not just a NHL2K9 problem. Cheers!
It's a part of the load/store instructions of the Interpreter. Dolphin can't interpret that instruction yet as there's no code in place to do so, most likely because no-one knows or understands what it does yet. So it doesn't do what it's supposed to do on the emulated hardware, so whatever that is looking for some information from that function, or another function that "eieio" calls, is not getting anything it expects and craps out, causing the emu to stop and/or crash. So unless someone figures out what "eieio" is supposed to do and implements the code... there is no fix for this.
found the name kinda funny though... haha all i could think of is "Old McDonald had a farm... E I E I O!" haha..
If it is an opcode, then it will be doc'd on IBM's website. Ector probably did not implement as many games didn't seem to use it, note when ector wrote most of the interpreter and JIT, he only implemented the opcodes that were important.
Couldn't resist myself to post the obvious
link
well... as I said, it wasn't implemented, for one reason or another... so until it is... this won't work.
Apparently this opcode is not important, it does a certain memory check that dolphin would not need to perform.
Is the Interpreter mode crashing only because the instruction wasn't implemented? How about trying to ignore it and see what effects it has? Or is it already doing that?
I do not know, but maybe you can replace the opcode with a nop opcode while running the debugger.