Reply to Re: Lil Dinky - A kind of DFARC replacement project
If you don't have an account, just leave the password field blank.
OH!! Right!
I knew I was forgetting one important thing! I don't have any "pack dmod" option ahaha! I dunno how no one even mentioned that before!
Basically, since it detects a dmod folder, it just needs to .tar and then .bzip2 the dmod folder you select and that's it.
I do have one question though... The original DMOD format is kind of... broken. In the sense that it does not respect proper .tar format. The .tar-ed data needs to be a multiple of 512 bytes, so the file needs to be padded with 0x00s. Additionally the last two 512 byte blocks in the .tar file are supposed to be filled with 0x00, so that's 1024 more 0x00 padding bytes. Dmods do not respect this, so some dearchiving programs give you a warning that the archive is badly formatted or something when you manually extract it.
Now the question is, when generating a dmod file, and creating the .tar, should I respect the standard .tar format and pad the file with 0x00 at the end? Or should I just use the "borken" format that dmods use where all the extra 0x00s at the end get discarded?...
I imagine DFArc 3 can interpret both valid and incompelte .tar formats, but I dunno about older versions?...
I knew I was forgetting one important thing! I don't have any "pack dmod" option ahaha! I dunno how no one even mentioned that before!
Basically, since it detects a dmod folder, it just needs to .tar and then .bzip2 the dmod folder you select and that's it.
I do have one question though... The original DMOD format is kind of... broken. In the sense that it does not respect proper .tar format. The .tar-ed data needs to be a multiple of 512 bytes, so the file needs to be padded with 0x00s. Additionally the last two 512 byte blocks in the .tar file are supposed to be filled with 0x00, so that's 1024 more 0x00 padding bytes. Dmods do not respect this, so some dearchiving programs give you a warning that the archive is badly formatted or something when you manually extract it.
Now the question is, when generating a dmod file, and creating the .tar, should I respect the standard .tar format and pad the file with 0x00 at the end? Or should I just use the "borken" format that dmods use where all the extra 0x00s at the end get discarded?...
I imagine DFArc 3 can interpret both valid and incompelte .tar formats, but I dunno about older versions?...
