Insert the SD card into the Wii 2. Turn you Wii on 3. Now pay close attention. Go to Wi/Data Management/Channels/Wii 5.
![]()
Elf/dol forwarder for custom channels gbatemp.net the independent video game. Wii homebrew browser or wad manager can be used for an easy installation of. Preview geexbox banner small.jpg. Tutorial how to play dvds on the wii. In this part we will install HBC, which is used to run apps from the system menu, using the bannerbomb exploit. Along the way, DVDx will be installed, this allows the lens to recognize burned DVDs (not play backups, just see they are there). In the end we will install Bootmii, which is.
Now in the top bar click on the button that says SD card 6. It should say something like 'install boot.dol?' And click yes Now You can install the Home-brew channel and DVDx Now you should have the Home-brew Channel (It should not show DVDx because it is a hidden channel) By the way if you went into save data or the SD card on the channel screen it will not work. You must go into channels.
Doing some experimenting.I installed DVDx Patchmii mode,then used fsbrowser to extract all the files (tmd,tik,app)I then used the blaze wadpacker to make a.wad file, and it came out to only be 5 kbwhich is nice and small, smaller than the installer'dvdx254.wad'so my question is this, will installing this through wad-manager work as an alternative to the installer?can you create a legitimate working wadfile for a hidden channel? Will the patchmii setting still be intact?I don't know if anyone has gone this route before, and I don't really want to 'discover' a new brick method.
It will probably work. But what's the point? Also, you'll probably piss of bushing and other people who worked on this.I doubt I would piss them off, I'm not distributing anything, and if I was, I was pretty sure it's an open source project.not to mention, the minute size differencewad: smaller, slightly more complex to install (assuming it DOES work, which was my question)installer: little larger, very user-friendly.Actually, I thought this had been done before, so I searched a little bit. Some of the things people said about this.
Click to expand.How is it fair we lose people like Bonemonkey for breaking post rules, yet people like Paul1991 do some shit that could actually hurt users of the site but is allowed to stay? I'm not turning this into a Free-Bonemonkey topic, he made his own bed and layed in it, but this shit with people 'releasing' stuff, especially shit they haven't tested yet, has to stop. When Bushing and Marcan have to drop by a topic to tell you what a huge fucking failure you are, there isn't much to argue about.
Click to expand.I've bolded the part of interest above, I don't believe that means the installer already will install multiple instances (which is what I wish to do, I said that right?), but just that the title.tmd is altered to address whatever IOS you choose (which everyone already knows, unless Im mistaken) upon each installation. A new installation overwrites the previous title.tmd, if there was one, but the title-id is always DVDX, right?also, no I DO NOT NEED THIS TO USE MPLAYERDVD with BACKUP LOADER/LAUNCHER also INSTALLED, because MPLAYERDVD works EXACTLY THE SAME WITH cIOSrev5 as it does with PATCHMIICORE for the tenth freakin time. Whoever started saying that obviously hasn't sat there and tested the same dvds with both cIOS installed.and I don't(.can't.won't.) use either backup program anyway.but thanks for the info above, im just not sure all of it was really applicable to my question. At least you know what multiple instances are.:-). The entire purpose of the DVDX channel installer is that it will modify the title being installed depending on your selection and installed IOS list.I've bolded the part of interest above, I don't believe that means the installer already will install multiple instances (which is what I wish to do, I said that right?), but just that the title.tmd is altered to address whatever IOS you choose (which everyone already knows, unless Im mistaken) upon each installation.
A new installation overwrites the previous title.tmd, if there was one, but the title-id is always DVDX, right?I don't know the details about DVDX, and I probably can't help you with this. I just wanted to let you know that this has been done before and that people were not happy about it.QUOTE(noobwarrior7 @ Oct 6 2008, 04:02 PM). The entire purpose of the DVDX channel installer is that it will modify the title being installed depending on your selection and installed IOS list.I've bolded the part of interest above, I don't believe that means the installer already will install multiple instances (which is what I wish to do, I said that right?), but just that the title.tmd is altered to address whatever IOS you choose (which everyone already knows, unless Im mistaken) upon each installation. A new installation overwrites the previous title.tmd, if there was one, but the title-id is always DVDX, right?I don't know the details about DVDX, and I probably can't help you with this. I just wanted to let you know that this has been done before and that people were not happy about it.QUOTE(noobwarrior7 @ Oct 6 2008, 04:02 PM). Click to expand.yea, I really do mean thanks for the word of warning man, I had no idea before your earlier post that anyone had talked about it before.also, I am not trying to tell you you are wrong. If you tested it and it didnt work than you have to go with what worked for you.
You can only try things with your wii, and only say what worked for you. I am merely saying to all the people who go just off of what they have heard, don't then repeat it to everyone without your own experience.
EVERY DVD I have tried with both has the exact same skips, freezes, code dumps, and 'successes', and there is really no reason they shouldnt, thats all Im saying. Thanks for the info, I get the feeling like you felt my last post was a flame, and I definitely didnt mean it like that, so I apologize.PS: there was one difference for me I neglected to mention, and that was that the initial loading of any dvd seemed to take approx.
6 seconds longer with cIOSrev5. The entire purpose of the DVDX channel installer is that it will modify the title being installed depending on your selection and installed IOS list.I've bolded the part of interest above, I don't believe that means the installer already will install multiple instances (which is what I wish to do, I said that right?), but just that the title.tmd is altered to address whatever IOS you choose (which everyone already knows, unless Im mistaken) upon each installation. A new installation overwrites the previous title.tmd, if there was one, but the title-id is always DVDX, right?I don't know the details about DVDX, and I probably can't help you with this. I just wanted to let you know that this has been done before and that people were not happy about it.QUOTE(noobwarrior7 @ Oct 6 2008, 04:02 PM). Click to expand.yea, I really do mean thanks for the word of warning man, I had no idea before your earlier post that anyone had talked about it before.also, I am not trying to tell you you are wrong. If you tested it and it didnt work than you have to go with what worked for you.
You can only try things with your wii, and only say what worked for you. I am merely saying to all the people who go just off of what they have heard, don't then repeat it to everyone without your own experience. EVERY DVD I have tried with both has the exact same skips, freezes, code dumps, and 'successes', and there is really no reason they shouldnt, thats all Im saying.
Thanks for the info, I get the feeling like you felt my last post was a flame, and I definitely didnt mean it like that, so I apologize. DVDX is installed under a single title ID. To use other title IDs you'd have to edit libdi, recompile it, and then recompile any apps that use it. The installer lets you install a variation of DVDX (one that boots a specific IOS), but you can only have one installed at a time because it's one title.I'm not entirely sure what the need is anyway. Use IOS3x for no-modchip mode, or IOS254/patchmii (or cIOS if you're into that, but that's unsupported) for modchip mode. Libdi will use anything 200 with UnencryptedRead calls, and anything. DVDX is installed under a single title ID.
To use other title IDs you'd have to edit libdi, recompile it, and then recompile any apps that use it. The installer lets you install a variation of DVDX (one that boots a specific IOS), but you can only have one installed at a time because it's one title.I'm not entirely sure what the need is anyway. Use IOS3x for no-modchip mode, or IOS254/patchmii (or cIOS if you're into that, but that's unsupported) for modchip mode.
Libdi will use anything 200 with UnencryptedRead calls, and anything. That is exciting to hear, cant wait for it.
Share a few of the 'new abilities?' Well, what you already see in PatchMii / cIOS, but applied to all IOSes. Also, a bunch of system stuff to maintain these changes as you switch from IOS to IOS.
But adding more stuff will be easy, so anything we can think of that might be useful can be added.QUOTE(Maikel Steneker @ Oct 6 2008, 07:13 PM) I really can't wait for BootMii. On one hand, I wouldn't like installing it because of the risks involved (after all, if you screw something up in boot2 your Wii is basically dead), on the other hand I can't wait for the things that this will make possible, like region free booting via the disc channel.
![]()
Click to expand.BootMiiStub might come soon. That would be the only risky part of the process, and it would also be relatively small, well tested, and the installer will double check everything. It will do nothing itself other than boot some more code from an SD card, if found. That way, only one tiny piece is risky to install, and you will hopefully never have to upgrade it. What it comes down to is:- Do basic initialization- Check for an SD card inserted- If inserted, try to load stuff from it- If no SD card, just boot boot2 normallyThere is very little code to fail there - as long as we can reliably detect a non-inserted SD card, we're at least safe.
If anything, it might be incompatible with some brands of SD cards or with some particular filesystem formattings, but at least it won't brick your Wii (since it won't try to do any of that if there is no SD card). And since all Wiis are the same and all boot2s are the same (almost - newer Wiis require one extra step in the boot2 loader, which we're taking care of - but if we didn't, it would just fail to install, so it would still be safe), and none of this depends on current software installed / NAND / anything, chances are if it doesn't brick one Wii it won't brick any. Of course, we're still going to test it thoroughly with as many Infectus users as we can gather up. Click to expand.BootMiiStub might come soon. That would be the only risky part of the process, and it would also be relatively small, well tested, and the installer will double check everything.
It will do nothing itself other than boot some more code from an SD card, if found. That way, only one tiny piece is risky to install, and you will hopefully never have to upgrade it. What it comes down to is:- Do basic initialization- Check for an SD card inserted- If inserted, try to load stuff from it- If no SD card, just boot boot2 normallyThere is very little code to fail there - as long as we can reliably detect a non-inserted SD card, we're at least safe.
If anything, it might be incompatible with some brands of SD cards or with some particular filesystem formattings, but at least it won't brick your Wii (since it won't try to do any of that if there is no SD card). And since all Wiis are the same and all boot2s are the same (almost - newer Wiis require one extra step in the boot2 loader, which we're taking care of - but if we didn't, it would just fail to install, so it would still be safe), and none of this depends on current software installed / NAND / anything, chances are if it doesn't brick one Wii it won't brick any. Of course, we're still going to test it thoroughly with as many Infectus users as we can gather up.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |