It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use any GPL code, I think.
Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
Unless he writes his own NTFS lib.Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
That is not at all true if you are using your HDD only for a Wii.Unfortunate if true.... NTFS is much better all around, IMO.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
Indeed. I know little/nothing of file systems, but if one works, I don't see why he would bother with another, especially if the only existing library for it is GPL and he wants to keep his app closed source. A lot of effort to write a new library just to support an extra file system.I can't speak for the man, but I honestly don't see why he would bother supporting NTFS when fat32 works perfectly fine. So my speculation is that NTFS support will not happen.
No, there are tools that can convert a filesystem into a different one while retaining the files in it.Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.
Yeah, I guess that would make sense.It is possible that nintendo produces new wiis with different drive types
eg a old one that still reads GC (because the still have much stock or production capacity)
and a new one that does not read GC and is cheaper to produce (but they don't have enough production capacity yet)
Just use a NTFS to FAT32 conversion utility. Not that hard, really?Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
COOL, There's a NTFS to FAT32 utility?Just use a NTFS to FAT32 conversion utility. Not that hard, really?Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
It really isn't that hard.Just use a NTFS to FAT32 conversion utility. Not that hard, really?Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
Well you kinda have to pay for them if your volume size is big...you might prove me wrong, IDK...COOL, There's a NTFS to FAT32 utility?Just use a NTFS to FAT32 conversion utility. Not that hard, really?Unfortunate if true.... NTFS is much better all around, IMO. Plus that would mean that I would have to reformat and spend countless hours moving hundreds of gigabytes of data.It is doubtful devolution will support NTFS as libntfs is GPL and tueidj has said devolution will be closed source and won't use an GPL code, I think.
I'd only heard of FAT32 to NTFS utilities. I'll have to google this.
Yes, apart from being a superior file system, one major reason for using NTFS is that it doesn't require special treatment for files > 4 GB. This means no worrying about splitting up dual layer games, archiving DVD images, etc.... Five years ago I might have recommended FAT32, but not now. IMO, any new Wii development ought to support NTFS.... But, if you like ntfs with your wii, that probably means you have some large files that can not be on fat32, so you can't convert it with those large files.
That's ridiculous given that it's not supported by any official wii software, HBC or exploit loaders. It is far from being a "superior file system", ext2+ has a much better design with the bonus of it not being Microsoft's proprietary invention.IMO, any new Wii development ought to support NTFS.
That's ridiculous given that it's not supported by any official wii software, HBC or exploit loaders. It is far from being a "superior file system", ext2+ has a much better design with the bonus of it not being Microsoft's proprietary invention.
Regardless, my 400 lines of FAT16/32 code do the job just fine and I don't see the need to add anything else.
I completely agree. I keep all my drives as Fat32, for stability and usability on other systems. Linux, android, mac, etc.Security permissions are irrelevant for any drives that can be physically accessed (especially portable drives) - you can just plug the drive into a PC which ignores the permissions.
My western digital 2.5TB drive came formatted as one giant FAT32 partition (as do all WD Elements drives). They even provide a utility to reformat it back to that state: http://support.wdc.c...&sid=34&lang=en
Most devices capable of playing media from USB (BluRay/DVD players) don't support NTFS. PS3s don't support NTFS. Tablet devices (by default for android) don't support NTFS. It is simply not a suitable filesystem for embedded devices to handle.