I was just wondering where wads install to? I use Multi Mod Manager to batch install stuff like cIOS on my SD but where does the installed stuff go to? Is there such a thing like running out of space for that?
It installs to the wii internal nand flash chip. That one has a capacity of 512MB.
Gamesaves and wiiware are also stored on that location.
Yes, it can run out of space, but cios are not the largest things to install there.
Gamesaves and wiiware are also stored on that location.
Yes, it can run out of space, but cios are not the largest things to install there.
It installs to the internal memory of the Wii known as NAND. yes you can run out of room on the n and. it's a very small memory chip that was initially meant for the wii software and game saves only but when wiiware/VC was introduced in later versions of the system menu it was evident that the 500 some mb chip was far too small for games so they had to include a way to transfer installed channels to an external storage device. The ability to transfer the channel to an SD card was a standard feature in system menu after that point. In short yes memory is a problem with the wii. hence the reason that SNEEK/UNEEK was such a breakthrough. It grants us the space of a hard drive or SD card instead of using the internal memory on the wii. Oh and no install cIOS and other ISO's is very unlikely to run you out of space. an IOS takes up at most a couple blocks of the memory. they are very small. as said the only real worry is the installing of wiiware. It will take up alot of space.
Oh... Guess I'll figure out how to use that Sneek/uneek thing next week... 512mb does seem really small for VC and Wiiware and save files.
And the transferring games to the SD sounds like you arent able to play those games on the SD until it is transferred back... Am i right?
And the transferring games to the SD sounds like you arent able to play those games on the SD until it is transferred back... Am i right?
The SD card menu allows for an easy quick transfer of the file but yeah it'll were your nand out recopying files to it constantly. but if you are looking for a channel solution only you can always use Mighty channels. It works like UNEEK however it's not the whole package it just does VC titles
You can't 'wear out' your NAND, it's solid state memory so there's no way you can physically wear it out.
tueidj said:
I'm quite well aware of that though it still decreases the life span of the chip. Not severly but still.
SNEEK/UNEEK and or Mighty channels is just a much better solution all around. For wiiware users... I personally very rarely play Wiiware titles.
The nand is a flash chip and those have a limited number of write / erase cycles.
I am sure if you would have a routine that continously writes to the chip, you will get a bad block very fast.
You need to look at the chip datasheet to see the number of guaranteed write / erase cycles. Some are 10000, others 100000
Some bad blocks will simply decrease the size of the flash disk a little, it's not like the whole chip becomes bad.
So, with installing / erasing gamesaves or wiiware, you don't need to worry. (Who would erase something 10000 times?)
I am sure if you would have a routine that continously writes to the chip, you will get a bad block very fast.
You need to look at the chip datasheet to see the number of guaranteed write / erase cycles. Some are 10000, others 100000
Some bad blocks will simply decrease the size of the flash disk a little, it's not like the whole chip becomes bad.
So, with installing / erasing gamesaves or wiiware, you don't need to worry. (Who would erase something 10000 times?)
You wouldn't, because it has automatic wear-levelling. So even if your routine ran 10000 times, those 10000 writes would be spread all over the chip.obcd said:
Anyway, forget the NAND. The SEEPROM is going to wear out quicker.
Code:
You wouldn't, because it has automatic wear-levellingWouldn't those blocks be relocated to some unused area so that you don't notice them? (The same way harddisks don't have bad sectors anymore these days.) I still remember you had to add the list of defective sectors in the early days....
It's not important anyhow.
Yes, and that software (IOS) is what is used to write to the NAND 99% of the time (the exception being RestoreMii, which is smart enough to only restore modified block). A regular app wouldn't have an issue. However if that app was written to do nothing but reload IOS constantly... storing a random seed in a static SEEPROM location wasn't ninty's best idea. At least when it wears out it won't cause any harm.obcd said:
raylgo said:After reading about how Sneek/Uneek sometimes messes with cIOS, I decided to live with the 512 mb for VC and Wiiware. Thank you for the replies everyone
you have it wrong, nand emulation is safer
Similar threads
- Question
-
AncientBoi
-
Sicklyboy
-
BakerMan
The snack that smiles back, Ballsack!
-
-
-
-
@
SylverReZ:
It was easy to bypass some of the restrictions, as one of the admins left a registry key in the administrative shares drive, which allowed me to get around the blocking of some sites. -
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
