Avalaunch's FATX3 is NOT equivalent to implementing NTFS. Enter the Matrix, case and point. Avalaunch's solution is analagous to Win95/98: a temporary one. NTFS is what's used in Win2k and XP. In Avaluanch, the 42-char limit is still there, but hidden from the user. Games with long file names are still a problem. For the last couple of days I've been doing some preliminary research into this very subject: namely, implementing an NTFS system for the XBOX. Maybe someone could enlighten me, since I'm very sketchy in this area: where exactly is the file system implemented. I'm almost certain it's at the operating system level, in the kernel. In XBOX-land this would equate to the dashboard, in which case implementing NTFS is a matter of coding it into a dashboard. I wish Avalaunch or Evox were open-source, so I could have a looksy at their code. This is my first venture into developing software for the XBOX, so in that regard I am a newb. However, removing the twin barriers (the 137 GB limit and the 42-char file name limit) would be a huge step for the scene!!
Mystagogue
PS: should I start a new thread?