If so, any idea what this error message says (I'm guessing it's something about a missing I/O cartridge):
If so, any idea what this error message says (I'm guessing it's something about a missing I/O cartridge):
Please lord, tell me that is from Mario No Photopie (J) [!].
Increase the size of your wang - PM crusher the words "poo poo" for extra length now!
Beware Coward!
Originally Posted by Ton
Hmm, a bomb, could be a matter of many things. Maybe it's corrupted Save file?
I completed the internetz
Anyone who can put the characters into babelfish even maybe?
I know you get programs that try to remove text from an image (so you can copy-paste or edit it) if theres a program like that that works for japanese, use that and paste into babelfish. You might get something mildly legible.
(\__/)_/)
(O.o ).^)
(> < ) <)
Now we know how viral bunny signatures really spread.
Yep it is heheOriginally Posted by Hangman
http://www.emutalk.net/showthread.php?t=23565
Just wondering what that message means really - put it here as I don't need help with an emulator, just a message translating.
Thanks for the suggestions though, I may give 'babelfishing' it a go, if I can be arsed
Hmmm.... I can sorta read it, but my Japanese is kinda bad since I have a horrible Japanese teacher. From what I can read, it ways:
"smart media is ?????? please redo the electricity"
So, from what it says, which pretty much states that you have to replug something, I don't think you can really fix it.
PSX - Crash Bash [NTSC]
PSX - Vagrant Story [NTSC&PAL]
PSX - Crash Bandicoot 3 Warped [NTSC]
PSX - Azure Dreams [NTSC]
PSX - Hydro Thunder [NTSC]
:::[DOWNLOAD PSX ISOS FROM OMNIROM.TK]:::
It could have somthing to do with the 64 DD as well. Did anyone ever dump those disks?Originally Posted by omni_rom
Nice one, that's about all I need to knowOriginally Posted by omni_rom
As some may think this wasn't a 64DD game (there was another one that was) this one did come with hookups on the cartridge though for AV input AFAIK. I'm guessing that's what it needs.
And Ultimate X, in this case there wasn't a need for me to state when it happened, as all I wanted to know was what the error message said - not how to resolve it.