- Status
You all know that everything there is displayed in a game when you are pressing the home-button is programmed into that specific game, not the system menu, right?
That means you would have to reprogram every single game to achieve what you are proposing. I would say it's highly impractical.
That means you would have to reprogram every single game to achieve what you are proposing. I would say it's highly impractical.
Forsaekn said:
I think if you can allow an open option for us to specify the version number, will accomplish 2 things if i get that right (in theory)
1- we change it to 0 to get an official update
1- we change it to the latest official menu version, so wiiconnect42 and wii shop will be accessible ?!
For Forsaekn's sake...give the man the space to release the version he already has without DEMANDING all your potential revisions!!
Plz Forsaekn release what you have so others can help you if you wish. YOU are the man, but I feel your taking alot of burden on this. If wii's are blasted by people not following the instructions so be it. It's not you fault.
Waiting for bootmii to come out will not stop ppl from bricking their wii and if so then they can then get the bootmii fix when released...so be it....everything has a risk element...just like when the PSP hack was going out when it was only 1.50 hack! Shoot happens! But it's upto individuals to evaluate the risk? ;o)
Plz Forsaekn release what you have so others can help you if you wish. YOU are the man, but I feel your taking alot of burden on this. If wii's are blasted by people not following the instructions so be it. It's not you fault.
Waiting for bootmii to come out will not stop ppl from bricking their wii and if so then they can then get the bootmii fix when released...so be it....everything has a risk element...just like when the PSP hack was going out when it was only 1.50 hack! Shoot happens! But it's upto individuals to evaluate the risk? ;o)
it's easier just to wait than it is to create a textbook of what not to do for inexperienced users, especially with all the forseen and unforseen potential complications.
not to mention:
-one textbook wouldn't be enough, cuz everyone would just not read it, and you'd end up needing 2 or 3 tutorials on all the big forums,
it would be impossible to tell the bugs from the idiots.
not to mention:
-one textbook wouldn't be enough, cuz everyone would just not read it, and you'd end up needing 2 or 3 tutorials on all the big forums,
it would be impossible to tell the bugs from the idiots.
i agree wait for the man to release the first version and see how that works before you go suggesting all kinds of changes.amzo said:
amzo said:
It doesn't matter how nicely you try to dress it up, you're being impatient by asking for an early release. What exactly do you want him to release right now? The code that he just bricked his Wii with? I think if the software reaches a point where a public beta is a good idea, the software author will probably realize that. I think coders are even more eager to release their code than users are to try it out, but for the benefit of all the users they wait until it's the right time.
As for the dashboard, Forsaekn, is there any potential downside to the first option? Would you have to overwrite the whole thing every time there is an update to dashboard or not anymore than you'd have to with the second option?
Well Dashboard is coming along well while i wait for my wii's to come home. It does act just like a loader stub, and boots directly to the system menu as if it wasnt there, unless you hold 'X' on the GC Pad or tap Reset (if you dont have a GC controller) which will bring up the dashboard where you are able to:
- continue booting the system menu (and apply select patches that are different than the default set)
- boot any title on the wii (say, the homebrew channel)
- run a dol/elf from frontsd (boot.elf or boot.dol in root, just like tphack...i figured if you had a bunch of dol's to run you would just boot HBC because that's what its for)
- load a dol/elf through network
Also I'd like to mention, The System menu rescue mode is on by default when dashboard loads it...this means when your wii turns on, you can either hold 'X' to go to dashboard, or 'Y' to enter rescue mode (where you can directly boot games from, i know many people liked skipping the menu altogether).
I really like how dashboard is coming together, once installed you're brickproof provided you don't ever screw with 0000000100000002, or do a nintendo update (it wont brick you, it will just overwrite dash). Its a great companion to BootMii.
EDIT: This is in no way defeating the purpose of BootMii. Dashboard does have more functionality than BootMii (at the moment, but there are little details on what BootMii will actually do once released), but it is not as invulnerable to nintendo as BootMii is. Dashboard also changes how the system menu is launched, whereas BootMii does not. I will personally be using BootMii and Dash together once its out, as I recommend everyone should.
@noir any update to dashboard will be just as dangerous as the second option...which is why I plan on making sure dashboard is complete and does not ever need an update (so that it remains a one-time install). Also in my opinion the 1st option doesnt have a downside at all, and is what i believe im going to go with. Oh and thanks for the donation bud, i appreciate it.
- continue booting the system menu (and apply select patches that are different than the default set)
- boot any title on the wii (say, the homebrew channel)
- run a dol/elf from frontsd (boot.elf or boot.dol in root, just like tphack...i figured if you had a bunch of dol's to run you would just boot HBC because that's what its for)
- load a dol/elf through network
Also I'd like to mention, The System menu rescue mode is on by default when dashboard loads it...this means when your wii turns on, you can either hold 'X' to go to dashboard, or 'Y' to enter rescue mode (where you can directly boot games from, i know many people liked skipping the menu altogether).
I really like how dashboard is coming together, once installed you're brickproof provided you don't ever screw with 0000000100000002, or do a nintendo update (it wont brick you, it will just overwrite dash). Its a great companion to BootMii.
EDIT: This is in no way defeating the purpose of BootMii. Dashboard does have more functionality than BootMii (at the moment, but there are little details on what BootMii will actually do once released), but it is not as invulnerable to nintendo as BootMii is. Dashboard also changes how the system menu is launched, whereas BootMii does not. I will personally be using BootMii and Dash together once its out, as I recommend everyone should.
@noir any update to dashboard will be just as dangerous as the second option...which is why I plan on making sure dashboard is complete and does not ever need an update (so that it remains a one-time install). Also in my opinion the 1st option doesnt have a downside at all, and is what i believe im going to go with. Oh and thanks for the donation bud, i appreciate it.
The chances of Nintendo figuring out the works of CSM before Bootmii comes out is slim to none. They are slow in responses to hacks. I mean I doubt anything will happen if you released Dashboard (is that CSM's new name now) and everyone had it. It'd atleast take a month.
Dashboard is a separate homebrew altogether that will be utilized by cSM.Phratt said:
As far as I understand though as long as there is a means of running homebrew on a wii, Nintendo can't do anything easily about dash. Its not as simple as preventing the copying of a savefile or checking for it upon boot. These example checks from Nintendo are done via the System Menu, and Dashboard is executed before that point, and in most cases will run an unofficial system menu anyways. Since Dash modifies the system menu title itself, it would be rather complicated for Nintendo to prevent its installation.
I don't want any wacky features... I DEFINITELY do NOT want a totally different look than Ninty's setup. Faster SD reading speeds like in 3.4, the ability to transfer files however I like, loading of my backups from the disc channel and the ability to use WiiConnect24 with blocks on Nintendo updates and that's all I need.
I also think blocks on Nintendo Updates, but still allowing WiiConnect24 would be great. Animal Crossing is less fun w/o the auction house, and I hate not getting my Wii Mail until halfway through a Brawl match.
Also, what do you think about adding a function sort of like what SDExplorer does? like you can move, copy, rename, delete and etc. any file on the SD Card, and view it as a set of folders?
I think that that would be nice.
EDIT: Gamecube backups would also be an epic win. I know it's complicated, you have to patch the MIOS and all that, but it would rock.
Also, what do you think about adding a function sort of like what SDExplorer does? like you can move, copy, rename, delete and etc. any file on the SD Card, and view it as a set of folders?
I think that that would be nice.
EDIT: Gamecube backups would also be an epic win. I know it's complicated, you have to patch the MIOS and all that, but it would rock.
Id like to see a cheat code manager and save state support .
Also a cheat engine and memory modifier would be a great addition .
ANother idea is a way to tunnel games to get them to work online for those that dont have online support .
A game speed modifier as well would be pretty useful .
Also a cheat engine and memory modifier would be a great addition .
ANother idea is a way to tunnel games to get them to work online for those that dont have online support .
A game speed modifier as well would be pretty useful .
3.2 with starfall is safer , and if you follow my installer you can have both 3.3uv1 and 3.2u with starfall , then you can enjoy the best of both worlds.kakis said:
Forsaekn said:...Also in my opinion the 1st option doesnt have a downside at all, and is what i believe im going to go with. Oh and thanks for the donation bud, i appreciate it.
Hi Forsaekn,
I think you have missed my suggestion so I post it here again :
What about a simple "boot strap" on NAND that load your cSM from SD, if cannot be found it would load normal SM. It would be risk free to test new cSM and no storage problem
Idealy it would be great if cIOSes could be put on SDCard too, maybe hacking IOS_Reload() to read them from SD. It would prevent Nintendo to overwrite them, and enable the use of many cIOS.
This realy looks like it will be EPIC!!!! Dashboard..OMG...do you have a Mac or why do you call it Dashboard
? Anyways, looks awesome!!!
But just to be shure I will wait 1-2 Months after the release, to look if Nintendo will try to stop this, and If Forsaekn will be able to fight back
....look how future-proof this will be
(Look at the New 002 Error, etc...)
But just to be shure I will wait 1-2 Months after the release, to look if Nintendo will try to stop this, and If Forsaekn will be able to fight back
(Look at the New 002 Error, etc...)
- Status
Similar threads
