Let mkisofs support Chinese file name.

When I testing the Chinese PE, I find a big problem, the mkisofs.exe from NativeEx server does not support Chinese file name.
It cause the "desktop" and "Start Menu" folder in "Documents and settings" folder looks like this:


I check the mkisofs by run "mkisofs.exe -input-charset cp936", and it shows it doesn't support CP936, the Chinese code page.
So I download the new mkisofs.exe that support Chinese file name, this works well with Chinese file name.


@Peter: Do you think we can use this mkfsiso to replace the NativeEx server one?

@Peter: Do you think we can use this mkfsiso to replace the NativeEx server one?

I tested. It is much bigger 700 comparef to 200 MB.
But it works well for me, too.

So a replacement could be done. But it is not on the nativeEx server, but on the LiveXP server.

So it is a job for Galapo to decide and upload.


Peter

I'll update the file on the server after the kids have had a bath and are in bed...

Regards,
Galapo.

...OK, done.

Regards,
Galapo.

, Thanks Peter and Galapo!

@tintinbt
Nice find.
Do you have another URL?
Do you have this mkisofs source code?
Did you created binary file?

Did anybody adjusted mingw32 timestamps?

Given automatic daylight saving enabled, currently not active daylight saving:
Does this mkisofs version create correct timestamps?
Does this result to a valid infcache.1?
Is PNP delayed? Does boot-land community prefer slow pnp?

Did you tried a current official mkisofs? http://cdrecord.berl...e/cdrecord.html
Charsets are not included to binary anymore.
Charsets are read from: /opt/schily/lib/siconv/
Can you add this file as cp936? http://unicode.org/P...NDOWS/CP936.TXT
Does this create correct filenames?

@Peter
There are debug information included. This has been remoded previously.
Use strip to delete this. Filesize reduce 100 kb.
And old file was upx compressed.


Just wondering:
Does NativeEx add "Documents and settings" to ISO image?
Does NativeEx use a RAM disk? Which driver does NativeEx use?

What about:
create a ImgDisk image at build time. Copy "Documents and settings" to image.
Load ImgDisk image at boot time as RAM disk.

Does NativeEx add "Documents and settings" to ISO image?

Yes. The folder is compressed before final ISO creation and unpacked to %temp% at build.

Does NativeEx use a RAM disk? Which driver does NativeEx use?

By default, yes. ImDisk is the default. However, other options, of course, are BootSDI ramdisk or the use of FBWF, which both then allow unpacking of 'Documents and Settings' to the systemdrive.

Regards,
Galapo.

@Peter
What about:
create a ImgDisk image at build time. Copy "Documents and settings" to image.
Load ImgDisk image at boot time as RAM disk.

Interesting idea!

Peter

@tintinbt
Nice find.
Do you have another URL?
Do you have this mkisofs source code?
Did you created binary file?

I don't have the source code, I just download the binary file from a very famous Chinese PE discussion forum.
The author said he used mingw32 to recompile the mkisofs 2.01 for win32 to support not only Chinese.

The original mkisofs supported Charset:
cp10081 cp10079 cp10029 cp10007 cp10006 cp10000 koi8-u koi8-r cp1251 cp1250 cp874 cp869 cp866 cp865 cp864 cp863 cp862 cp861 cp860 cp857 cp855 cp852 cp850 cp775 cp737 cp437 iso8859-15 iso8859-14 iso8859-9 iso8859-8 iso8859-7 iso8859-6 iso8859-5 iso8859-4 iso8859-3 iso8859-2 iso8859-1

And the new mkisofs supported charsets are:
big5 gb2312 euc-kr sjis euc-jp utf8 tis-620 koi8-u koi8-r iso8859-9 iso8859-8 iso8859-7 iso8859-6 iso8859-5 iso8859-4 iso8859-3 iso8859-2 iso8859-15 iso8859-14 iso8859-13 iso8859-1 cp950 cp949 cp936 cp932 cp874 cp869 cp866 cp865 cp864 cp863 cp862 cp861 cp860 cp857 cp855 cp852 cp850 cp775 cp737 cp437 cp1255 cp1251 cp1250

And old file was upx compressed.

@Peter
We can use UPX to compress the new mkisofs.exe, the size would reduce from 954K to 488K

@Peter
We can use UPX to compress the new mkisofs.exe, the size would reduce from 934K to 488K

I suggest a different procedure:
Of course, minimize the size of the exe like CDOB suggested by removing debug and UPXing
Upload to the LiveXP server as mkisofs.ch.exe

In the createiso.script, there is an option 'Chinese support'

And createiso.script uses either mkisofs.exe or mkisofs.ch.exe

@Galapo: a job for you?

Peter

@Galapo: a job for you?

Yes, I can do that. No problem with upxing, but I would need to be provided the file with debug information removed as I do not know how to do that.

Thanks,
Galapo.

Yes, I can do that. No problem with upxing, but I would need to be provided the file with debug information removed as I do not know how to do that.

Thanks,
Galapo.

I Googled a lot.
The 'strip' cdob suggested seems to be a unix app. And I neither have connections to unix nor to linux.
And on the Windows side I only found commercial apps like PE Explorer, where the demo version can do a lot, but unfortunatelly not remove debug info.

@ALL
Can somebody in the forum do this job: Download the current mkisofs.exe from the LiveXP server, 'strip' it and post the result here?

Thanks

Peter

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.

@Peter
In addition ImDisk support NTFS RAM disk resizing. I'm resizing to quarter free RAM:

[Software.AddReg]

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.

Are compressed files unpacked at build or at boot time?
If there is one compressed file at CD: why does chinese chars matter?

Depends on the method. If using ramdisk where 'Documents and Settings' is unpacked at boot, then this wouldn't matter as you say. But if using fbwf with 'Documents and Settings' remaining on CD (which is the method I assume tintinbt is using), then correct Chinese folder names depends on mkisofs.

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?

I'm edgy about this myself, and will likely revert to the former mkisofs unless source can be provided.

Regards,
Galapo.

I'm edgy about this myself, and will likely revert to the former mkisofs unless source can be provided.

Regards,
Galapo.

Agree, I had sent a email to the author for the source code.
Hope can get it soon, or I need to find another method.

For the time being I've now replaced mkisofs.exe with the previous version we had there. Hopefully we are able to source a working and able-to-be distributed version supporting Chinese characters soon.

Regards,
Galapo.