Hacking suggestions to SD/USB Loader

  • Thread starter Thread starter JimmyZ
  • Start date Start date
  • Views Views 8,159
  • Replies Replies 47
nothing to be so harsh. try to be a little more gentle or nobody will hear what you are aking for. you are asking for a favor and shout at the ones which could do it for you. i read the original post more than a week ago buddy. you might read my last post. i even posted in the original thread you linked to and in the libwbfs+ thread over at wiinewz.

i support your idea but i can understand if the coder don't want to implement a closed fileystem which has at least as much downsides as wbfs has. ext2 with wbfs containers would be the best way to go in my eyes. the reason it won't happen is the overhead a filesystem with container files causes on the softwareside.
 
Screemer said:
with wbfs containers on fat32 you would have the filesize issue again. i a game is bigger than 4gb even if it's in a wbfs container you had to split the file.

There is also the exFAT (or FAT64 if you prefer). No more size issue and it will be the next fat standard on SDXC (next level of SD Card), it's already compatible with Windows XP and Vista, and the driver for linux is on way.

I also read somewhere that "fs" file system aren't great for flash memory because it doesn't need any indexing stuff etc.

But about wbfs, why haven't Waninkoko integrate something more used like ntfs or even ext3/hfs. Create another kind of partition is simply force user to use any device only for wii "hack".
 
other than the issues with multiple partitions, there is nothing wrong with WBFS. It works, we can use Windows and such with GUI's, and as someone stated earlier, maybe someone will actually code a native driver for the filesystem, but if they don't that's OK. If someone didn't have the skills to make a new filesystem and wanted to use NTFS/ext2, they would have, but they have worked it out, and unless you can do a better job (I know I can't), accept the skills and gifts that you get.

Thanks for all the work, guys.
 
i just love the wbfs like it is.
we're all using it because that's the best solution for now.
if you really want us to use ntfs or whatever, then code a lib that we can use in our loaders and you'll see them pop out from everywhere in no time.
 
Screemer, sorry for being rude, but no regret, stupid is stupid, I'm thankful but this do not make me think someone's always absolutely right.

I said times and times again that the main benefit of using FAT is that Wii System Menu/Other homebrew can share the same partition.

Any file system other than FAT do not qualify this advantage.

I'll try to implement that about two month later, when I have some spare time, well, if no one did it before that.
 
drmarvin said:
... someone didn't have the skills to make a new filesystem ...

you need to make that clear that making a new (file) system do not need too much skills, though it feels so.

making a great (file) system do.

but it's clear that the only meaning of the existence of most file systems on this little planet is that they are different and not compatible.
 
JimmyZ said:
Screemer, sorry for being rude, but no regret, stupid is stupid, I'm thankful but this do not make me think someone's always absolutely right.

I said times and times again that the main benefit of using FAT is that Wii System Menu/Other homebrew can share the same partition.

Any file system other than FAT do not qualify this advantage.
i think i have to quote myself because i think you don't get me.
QUOTE(Screemer @ Apr 14 2009, 12:39 PM) have you read my edited post? should i buy a portable drive for every application i'm going to use? every other damn homebrew app uses fat to access external drives and sd cards. every damn os can access/read/write a fat formated portable drive. nearly no homebrew can read/access other partitions besides the main partition. even if i create 2 partitions it's not going to work. usb loader needs the primary partition to be wbfs, every other hb needs it to be fat or it could not be accessed. that's why i am moaning for fat with splitted isos. i am not for ntfs, ext, reiser, or what ever. i want to use my hard drive as it was intended to be. and its purpose is to be a portable drive.
i completely support your idea! damn it. why do you insult somebody who fully agrees with you.
 
The reason WBFS was created, is how small the code is to read a image, the code required to read an image is in IOS.

The code in libwbfslite/libwfbs.c, is the code included in the custom IOS, it's under 110 lines of code. code to read off a fat filesystem with split images will likely be larger than that, ntfs will be way larger than that. And the extra processing slows down loading and playability.

Yes having everything would be nice, but this is pretty good.
 

Site & Scene News

Popular threads in this forum