Used the Wii to Dump game-- Launched Dolphin 3.5 and ISO does not launch. (RESOLVED)

[dumar]

Before I begin, allow me to say I tried to search all over various
websites (here and homebrew) for assistance for a similar issue
occurring to someone else but to no avail. (Now my back is against a
wall and i felt it was necessary to create a thread.)

0) ****This
is the first time I'm trying to play/launch a Wii game on Dolphin--
figured I'd start with my real library of games! =)
[If
configuration on Dolphin EMU is necessary before launching a Wii Title,
then that's likely where my issue lies since I haven't touched anything
in the Wii config or tabs.]

NOTE: Used Dolphin 3.0 & 3.5 stable revisions only.

1) I dumped my Wii game, Metroid Other M: on my Wii 3.3U firmware, using latest homebrew and latest APP (CleanRip)

2) I used a 4GB SDHC card for destination of dump (this took roughly 28minutes to complete... perhaps slightly longer.)
- Parameters on CleanRip I used:
- Dual layer (No)
- Chunk Size MAX
(The Dump finishes with no errors.)

3) ISO is 3.9GB's (displays 3.7GB in Dolphin.)
- I refreshed ISO library in Dolphin 3.5 EMU, and it's detected (looks the same as 3.0 Dolphin.) as:

Wii --> No banner--> Metroid Other M--> 3.7GB's
Wii --> No Banner--> Zelda Twilight Princess--> 3.7GB's

NOTE: I also dumped My Twilight Princess Wii, the same way... and same issue (Blackscreen, freezes.)

4) I launch the game(s) [both Twilight Princess Wii & Metroid Other M), and black-screen. Nothing happens.

Dolphin 3.0(stable)/ 3.5 (stable)
Settings are:

* DX9 Backend
- 1920x1080
- force 16:9
-Vsync Yes/ Full-Screen Yes
- 1x Native + 9xSSAA
- Scaled EFB Copy + Per Pixel Lighting + Force Texture Filtering

*Hacks*
- Ignore Format Changes/ Yes
-EFB Copies RAM / Enable Cache/ Yes
- Texture Accuracy (slider all the way to Right-- > FAST)
- External Frame Buffer / Disabled
- OpenMP Texture Decoder / Yes

*Audio Tab*
- DSP LLE Recompiler / Yes
- DSP LLE on Thread/ Yes

*Wii Tab*
- Use EuRGB60 Mode (PAL60)

5) What have I done wrong here?
- Is my process dumping the issue? Setting file-chunk 'MAX' perhaps?

(NOTE:
I tried DSP HLE AUDIO & LLE (I have the bin files dumped from my
Wii already-- my gamecube games work just fine with either HLE or LLE)

Thanks
for reading guys, any advice or suggestions are greatly appreciated.
(Also, I hope I haven't broke any forum-rules going into too-much detail
=\

***EDIT: I had imagines directly linked and nothing but code
displayed all over the thread... a complete mess (I typed out settings.)

[delroth]

Your SD card is likely too small. Wii games are usually 4.8GB. Try dumping to an SDHC 8GB card instead, or to a >= 8GB USB device.

Note that you might also get issues with FAT32 4GB per file limit. Not sure how cleanrip handles that, maybe someone who uses that app could answer you.

[dumar]

(01-01-2013, 08:14 AM)delroth Wrote: Your SD card is likely too small. Wii games are usually 4.8GB. Try dumping to an SDHC 8GB card instead, or to a >= 8GB USB device.

Note that you might also get issues with FAT32 4GB per file limit. Not sure how cleanrip handles that, maybe someone who uses that app could answer you.

Thanks.

Yea, perhaps that's it.

1) I have a spare 16GB SDHC card that I use for my 3DS-- I'll try that and see what happens.

2) Alternatively, perhaps I should fragment by 2GB each? And keep re-inserting and copying off the 2GB Chunks from Wii to PC using small 4GB card... I don't think the Wii will know the difference.

[dumar]

(01-01-2013, 08:14 AM)delroth Wrote: Your SD card is likely too small. Wii games are usually 4.8GB. Try dumping to an SDHC 8GB card instead, or to a >= 8GB USB device.

Note that you might also get issues with FAT32 4GB per file limit. Not sure how cleanrip handles that, maybe someone who uses that app could answer you.

It WORKS!!! Delroth, you're the MAN!!!

Thanks man!

You were right.

Using MAX Chunk setting on a 4GB Card was the issue because average size of Wii game is indeed single-layer @ 4.7GB's.

Gah, you know, if the damn APP would have produced any sort of error, or warning that I ran-out of space, this would have been identified so much sooner. (Instead the software mysteriously closes after its progress bar completes, with no confirmation, or error.)

A) I used my 2nd alternative to copy... I copied off (1) 3GB chunk, then I copied the remaining 1.44GB with the same 4GB card, (transferring the chunks onto my machine per chunk.)