yeah i ment the wii , it shut down the wii. sorry I was upset when I typed because I had been trying and trying and I wasn't thinking correct.. I dont know but maybe you could tell me the right settings in that app because storage is not an issue really. I have 1TB so I dont think I really have to shrink any games. TIA
Thank you but at the moment I have deleted all games I had using DMToolbox because they just shut down my wii. So what I want now is someone to tell me the correct settings in that app so it won't make my wii shut down all of a sudden when starting the GC games. If someone can be kind enough. I just want it to be correct and done with, so I can play when I will receive my GC controllers.
you dont need to pass isos trough any sort of program nintendont works better with full isos you dont need to use dmtoolbox at all to make full isos work.
considering he said he passed all his isos through dmtoolbox, not a single one will match redump at all.
why do you need gameid? are you using a loader that requires them? nintendont app doesnt need them but im guessing your using something like usbloader gx or wiiflow or cfgloader? tbh i dont know of any app that renames the folders and the isos correctly without chnaging the iso, you can always see the id manualy by just openning the iso on a hex editor and takin a look a the first text.
Yes, I am using usb loader gx I like it better with the covers and all that because nintendont is just plain text. I like the cover because when I see the picture of the game I remember better what it is. And I have my wii games I ripped from my CDs in there too. just better for me.
i use the free one HXD, you just open the iso and the first letters are literely the game tittle and id right off the bat.
whoops i meant HxD not HxH bad typo.Thanks for the heads up. Will have a look at it right now!
I figured it out. I googled it and saw the correct one and understood
Thanks!
It seems a bit slow still for the size of a memory card file but it doesn't freeze anymore.
I just noticed there's an f_expand() function in FatFS but it seems to be disabled in the main branch source. Is there a reason to not use it?
So far, so good here. Time will tell, it was quite random at times...
Card creation seems quite quick on my system.
Appreciate the effort put into this. Will keep testing to be sure.
Sent from my Nexus 5 using Tapatalk
Yes! I am. As a matter of fact, i'm the one who was surprised no one else noticed/cared.I haven't had a card creation fail yet on that build. Rename your old save directory and Fire up a bunch of games and see how it goes if you are one of the ones who had issues.
Sent from my Nexus 5 using Tapatalk
It's been reported here and there, but obviously doesn't affect everyone, or they've long had their cards already setup.
I'm thinking it's some weird interaction with the "simple" caching code and certain storage devices. I didn't notice a problem with my USB HDD, but with my SD card it was hanging for 6-7s before even attempting to start writing the memory card file. The SD card hang is gone with the new cache code.
Not in this PR, but maybe later. (Also an option to skip the IPL.)Any chance of a "skip silent boot" argument? So we can make loaders display nintendont if required? (Assuming the card creation will be hidden again upon release)
Cheers. Much work needed on the loader front to work with ciso?
CISO in the loader is fairly trivial. It just has to read the GameCube header, which is located at 0x8000 in CISO images as opposed to 0 in standard images. The kernel has a CISO map parser, which redirects reads to the appropriate blocks. This is all self-contained in ISO.c, so the rest of the kernel doesn't know the difference between CISO and a 1:1 image.
@
BigOnYa:
