Hi, Thanks Jeremy.
On Fri, 20 Aug 2021 at 13:03, <perditi...@gmail.com> wrote: > > I was trying to figure out how KITTEN/KITTENC works. Seems to attach > each NLS file with the "KITTENC" signal by the end of the executable. I've > read about making UPX support easier, I guess you UPX before you ATTACH. > > It is written to support either, appending before or after UPX, it > stores the original file size and then when ran uses the compressed > file size computing the difference and adjusting the stored offsets > with this difference. > So if you don't compress or append the languages files after > compressing the difference is 0, but if you do it before compressing > then the difference is your compression savings more or less and > offsets adjusted accordingly. > But if you append after compressing, wouldn't UPX mess the attached stuff? (I mean if it tries to "expand" something that hasn't been compressed). I suppose it is tested to work, but I am curious, I am not very familiar with the technical details of how UPX works. > Why did you need to write an own function to convert string to UL? > > It was from the original kitten - not needed in kittenc since that > part occurs during build, but also no need to change working code; I > like the update from switch statement to strchr for the xlat portion > of the escape conversion > Well I see it used when processing the Esc chars, when a language file is processed. What I was wondering is if the function is smaller, or has some benefits over using the standard strtoul. Aitor
_______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
