Jump to content
Sign in to follow this  
mandrake_tw

ImgBurn bug in character set!?

Recommended Posts

I use grub4dos as the Bootable CD's boot image.

And I find when when it character set at standard will occur error for me.

First I normaly burn it as standard

post-47538-0-84553800-1349840659_thumb.jpg

then I boot from the cd

post-47538-0-36135300-1349840668_thumb.jpg

it can't find my fontfile unicode.hex.gz & image and I find it in grub environment will be shown as unicode_hex.gz so that it can not be found.

If I change the file name at filesystem and menu.lst as unicode_hex.gz it will all be fine.I

I find the problem because I use command mode instruction binary mkisofs make the same file as iso image and no problem with unicode fontfile and image.

And then I try and find it was about character set standard/DOS/ASCII options

 

I change character set to DOS or ASCII

post-47538-0-54029900-1349840665_thumb.jpg

 

then everything work fine Unicode traditional Chinese and image are there

post-47538-0-49879000-1349840671_thumb.jpg

 

My menu.lst content about this relate are

splashimage=/boot/splash/LRR_640x480.04.gz

font unifont.hex.gz

 

post-47538-0-20879600-1349841673_thumb.jpg

The problem is if I burn it's character set as Standard then in grub4dos commandline will change to

/boot/splash/LRR_640x480_04.gz

unifont_hex.gz

 

But in CD's filesystem it

/boot/splash/LRR_640x480.04.gz

unifont.hex.gz

 

If the filename with more than two dot(.) error will occur.

I don't understand why?and diff about standard/DOS/ASCII and is it bug!?

Edited by mandrake_tw

Share this post


Link to post
Share on other sites

The standard character set doesn't support the 'dot' character for anything other than the separator between the file name and file extension. (XXXXXXXX.YYY)

 

As you have files that require 2 dots, you simply cannot use the 'standard' character set and must change to a less restrictive one (as you've already found out).

Share this post


Link to post
Share on other sites

The standard character set doesn't support the 'dot' character for anything other than the separator between the file name and file extension. (XXXXXXXX.YYY)

 

As you have files that require 2 dots, you simply cannot use the 'standard' character set and must change to a less restrictive one (as you've already found out).

 

Thank you! Now I got more clear about this issue.So that is not ImgBurn's bug.

I also find the mkisofs and use it to check the different.

 

post-47538-0-97095900-1349859015_thumb.jpg

 

Can ImgBurn auto tune the checkbox default status when user switch the radio Standard/DOS/ACII ?

I look at the ISO 9660 Standard and find out this is it's restrictions.

Restrictions

 

File and directory name restrictions

 

The standard has three different levels for interchange, here paraphrased from section 10:

  • Level 1: File names are limited to eight characters with a three-character extension, using upper case letters, numbers and underscore only. The maximum depth of directories is eight.
  • Level 2: File names are not limited to 11 characters (the 8.3 format) but can be up to the maximum allowed by the 1 byte counter in the directory entry and the filename length byte counter. Typically, this is close to 180 characters, depending on how many extended attributes are present.
  • Level 3: Files are allowed to be non-contiguous (i.e., fragmented), principally to allow packet writing or incremental CD recording.

The standard also specifies the following name restrictions:[citation needed]

  • All levels restrict filenames to upper case letters, digits, underscores ("_"), and a dot. Linux by default [3] converts uppercase letters to lower case while mounting ISO filesystems.
  • File names shall not include spaces.
  • File names shall not start or end with the dot character.
  • File names shall not have more than one dot.
  • Directory names shall not use dots at all.

Some CD authoring applications allow the user to use almost any character. While, strictly speaking, this does not conform to the ISO 9660 standard, most operating systems which can read ISO 9660 file systems have no problem with out-of-spec names. However, the names could appear wrong to the user.

Edited by mandrake_tw

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.