The folder is compressed before final ISO creation and unpacked to %temp% at build.
Are compressed files unpacked at build or at boot time?
If there is one compressed file at CD: why does chinese chars matter?
I guess, there is another option to include "Documents and settings" to CD.
Language specific chars does matter that way. However that's not a reliable solution.
According to ISO9660:1999 draft there is no hint about used charset inside ISO image.
Originator and recipient has to aggree to one charset, char confusion is possible.
In addition ImDisk support NTFS RAM disk resizing. I'm resizing to quarter free RAM:
0x1,"Microsoft\Windows\CurrentVersion\RunOnceEx\100","000","||xpeinit.exe -f -m ""Resize ImDisk RAM disk"" imdisk.exe -e -s 25%% -m %RamDrv%"
I don't have the source code, I just download the binary file from a very famous Chinese PE discussion forum.
That's sad. I like to learn this charset handling.
Please ask the author about the source code.
Mkisofs has been released under the terms of GPL so far.
Which famous Chinese PE discussion forum do you use?
I'm wondering: what's boot-land opinion about:
distributing a modified GPL application, but not provide source code?
Isn't this considered GPL violation? Did I misunderstood GPL?
Can somebody in the forum do this job: Download the current mkisofs.exe from the LiveXP server, 'strip' it and post the result here?
Well, I could do this.
However I dislike to violate GPL knowingly. I'm not sure enough at this point.
Can anybody clarify requirements?
As for myself I'm currently at
$ ./mkisofs -version
mkisofs 2.01.01a41-bootcd.ru (i686-pc-cygwin) Copyright © 1993-1997 Eric Youngdale © 1997-2008 Jörg Schilling
I like Alex's -duplicates-once, correct timestamps and files greater 4GB.
However I implemented ISO9660:1999 8bit chars only. Sorry I can't read, write or test a 16bit char language.