redneck649 / wiiflow

Automatically exported from code.google.com/p/wiiflow
0 stars 0 forks source link

ISO forwarders dont work on versions above 304 #518

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Use Wad2Iso from 
"http://gbatemp.net/t207530-wiiware-vc-iso-forwarders-made-easy" to generate 
some ISOs for VC/WiiWare loading on Emulated NAND.
2. Copy the Loader.dol file to Fat32 USB HDD like explained on that topic
3. Try to load them in any version of WiiFlow above 304.

What is the expected output? What do you see instead?
In 304, using cios249[56]d2xv7a5 as default, it works, the loader.dol is found 
and the game is launched.

Any newer version gets me either a black screen or a "Can't find Loader.dol" 
error (which sounds like access to the HD was denied).

Tried all the ios releases available, none works.
It works in other USB loaders, though, using Hermes 222/3 

What version of the product are you using? On what operating system?
4.1U, cios 249[56]d2xv7a5.

Please provide any additional information below.
No ideia why ver304 would load these ISOs fine with d2xv7a5, while newer 
versions won't neither with same cios or any other... Other loaders can do the 
job too.

Original issue reported on code.google.com by nicklessguy@gmail.com on 9 Sep 2011 at 9:05

GoogleCodeExporter commented 8 years ago
I'm not sure if ISO forwarders will be necessary considering w/rev 411+. Now 
that Wiiflow has a Homebrew channels option you should be able to run the app 
that points to the rom. Untested yet but I'll try on my Wii tonight.

Original comment by MassiveR...@gmail.com on 12 Sep 2011 at 4:00

GoogleCodeExporter commented 8 years ago
Problem is that the app that points to the rom is only one single dol. Which 
rom is called and with which settings are sent by the ISO.

Also, they are the only way for the games to blend nicely along with the 
others, sonted by categories (as system names) and fast, since there is no need 
to read from emulated nand at all.

Calling them from wiiflow's nand emulation, with 300+ games, takes ages to load 
game list, and the favorites/categories are limited and don't blend with normal 
isos.

Original comment by nicklessguy@gmail.com on 13 Sep 2011 at 5:38

GoogleCodeExporter commented 8 years ago
Nand emulation uses the same cache game view does.  This will not recieve any 
attention.

Original comment by Miigotu on 27 Sep 2011 at 2:53

GoogleCodeExporter commented 8 years ago
Wiiflows takes 4 to 5 times the initial load times that 304 does for me in the 
same hd.
If it's not nand reading, im clueless about the reason for such load times 
difference.

Anyway, this isnt the main issue. We can't organize/categorize/rename the nand 
emu the same way we can with isos, and all the main tools for ISO 
dol/forwarders for homebrew and games won't work with wiiflow.

Wad2ISO, CustomizeMii, Universal Forwarder Creator, ISO Studio, none of these 
works in recent wiiflow thanks to the absense of IOS Selector Reload Block 
on/off switch (they need it set to OFF, Auto won't work).

Some VC (especially neo geo and n64) and WiiWare needs options (AppLoader, 
different IOS, and such) that wiiflow doesnt have, but ISO Forwarders does.

CFG and GX Loaders supports all these and works perfectly for everything, i 
don't get why wiiflow can't, just to have a settings window 2 or 3 lines 
cleaner...

Original comment by nicklessguy@gmail.com on 25 Oct 2011 at 4:00

GoogleCodeExporter commented 8 years ago
Also misinformation.  NAND emu can be sorted, named, categorized, etc even MORE 
than iso forwarders.  And the fact that ISO forwarders need Reload Block off is 
only because of bad coding in the iso forwarders, change the ios the iso 
forwarder requests in it's TMD to the right ios and it works fine.  This is a 
bug in the programs that make the forwarders, since all they seem to understand 
is how to replace a main.dol with outdated emulator code and sign the iso.  
Apploader method is a misnomer, all apploaders of all ww/vc is embedded inside 
the main .app (usually the last .app in the wad), this "Apploader Method" was a 
cheap workaround in triiforce to make some games work which didnt because the 
contents of their TMD was out of order, so using TMD->Contents[boot_index] 
fails.  Instead of the correct way of looping through contents and finding 
which TMD->Contents[i].index == boot_index (which ALWAYS brings the right 
main.app).

There are no need for ANY of these options, they were workarounds to errors in 
pseudo-emulation of the wii which are corrected inside wiiflow.

Dont post about shit that's removed, it was removed for a reason and decided 
upon after much deliberation and input from many people who know ALOT more 
about these things.

Original comment by Miigotu on 26 Oct 2011 at 12:10

GoogleCodeExporter commented 8 years ago
Ok, if you know so much more and got all the solutions, then please, tell me 
how can i play Zelda Majora's Mask, KoF 96/97, Ogrebattle, Bomberman Hero, and 
other VC games that needs an older cIOS to run, since no d2x version work for 
them till now?
They only goes as far as the "N" logo, unless you use rev17.

If i dont have iOS selector, tell me how i can play these games from wiiflow, 
please.

Original comment by nicklessguy@gmail.com on 7 Nov 2011 at 4:21

GoogleCodeExporter commented 8 years ago
Hi nicklessguy, What I have done is install all the vc games that don't support 
d2x on my wii's real nands, And used the backup nands for all the rest. It dose 
mean I have to press the B button on the channel icon, But it work great. If 
only we could get the real nands and backup nands on the same page. But this 
will work for now.

Original comment by pounds...@yahoo.com on 10 Nov 2011 at 8:07

GoogleCodeExporter commented 8 years ago
Thanks for the input, but there are 10 N64 games that run on these new models 
of VC emulator (the ones released since Kirby 64) and about 6 or 7 neo geo ones 
too. 

The real nand isnt enough to hold all of them, just a few.
That's why i think ios selection is still important, at least until d2x reaches 
100% compatibility, which didnt happen yet...

Original comment by nicklessguy@gmail.com on 11 Nov 2011 at 5:11