Ok answering random questions:
1. Yes any length entry... assuming I didn't bork up the padding code somewhere (that'd be a bug, but it'd be fixable) I think there is a practical limit though, but I haven't reached it yet.
2. Use an uncompressed sound bin (made out of a wav file) and it should work. Also apparently (according to radioshadow) it'll run the original if you use lz77 compression on 0.app when you package it back up.
3. rabapab23: You are going to have to be a little less vague. Is it freezing when you try to run the actual game, or when you click on the channel? If it's the actual launching of the game then this has nothing to do with my utility and it's a rom injector problem. Text-length should no longer be an issue as well, so long as I don't have a bug somewhere. Also please don't use the term "brick" as that's confusing. A brick refers to a lockup that can't be fixed without software/hardware help. What you are getting is a crash. BIG difference.
4. The lz77 questions relate to things that I won't be doing with the brlyt editor. I make different tools for different files and give them command-line options so I can eventually merge them that way.
5. Roms with lz77 compression on them are nothing new.... the c64 roms have this. It appears to me at least that any interchangeable vc file (snapshot, roms ect) with lz77 compression always have "lz77" in the name of the file somewhere and that's how the app knows to decompress it when the game is ran. You can, of course replace this file by recompressing the new one, but by removing the lz77 part of the file name, you should, in theory be able to run uncompressed files. Of course in the case of the roms you need to find the config file/section somewhere in the wad that tells the emulator the name of the rom and change that as well.
5a. I've thought about it and I've decided to make a rom swapper instead of an injector. What's the difference? A rom injector, while simplier to use, merely unpacks the wad and manually edits the bits in the app files to replace the wad. This means that if the rom is larger than the original it can't be injected and if it's smaller you are wasting space by leaving the same size file in there. Also something less important, but in the case of systems that have "loose" roms in their archives, the name of the rom ends up being the same as the original... this can be changed in most cases, making for a cleaner replacement. What I'm going to make is a rom swapper, which properly builds the rom (where applicable, like neogeo) and replaces it and assumes that the wad is already unpacked with the appropriate app file already unpacked as well. It doesn't make a lot of sense to "inject" when we have to open everything up to edit the snapshot/brlyt/save icon/ect anyway.
6. The latest private build of my icon generator can output lz77 compressed files, so yes, I will support it. Barring any major issues with the brlyt editor I will start woking on a new release of the icon generator soon.