Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
Incroyable HULK

"Optimize" ISO limitation

Recommended Posts

Hello Multi-everyone,

I want to know if you had some limitation with the optimize feature of your multi-boot CD/DVD? The reason I'm asking is because I ran into a computer that didn't want to boot my CD and if I burn the same CD without an optimised ISO it worked fine. :o

Perhaps my problem is from EasyBoot, the software I use to generate my ISO (same engine as UltraISO).

Share this post


Link to post
Share on other sites

not sure, i dont use easyboot, i use cdimagegui & cdshell 2 make my multiboot dvd, no probs so far :D

Share this post


Link to post
Share on other sites

EasyBoot is perfectly fine. But don't use it to generate your ISOs - I like to use a utility for what it is originally designed. :)

And I use CDimage.exe thru the cdimageGUI interface - its the best way to create an optimized ISO.

Well now, what *ARE* the limitations you might have run into?

1. EasyBoot and UltraISO aren't good to use for optimized ISOs (they corrupt files!).

2. If you use FAT32 partitions, then you can't create any file of size more than 2 GB (and any optimizing tool will first create a file as big as non-optimized size, so move to NTFS).

3. cdimage.exe cannot (properly) make an ISO of files totalling upto more than 4 GB.

Check all the above, and do post back about what the problem was, and how you fixed it.

Share this post


Link to post
Share on other sites

@prathapml

I've been using EasyBoot and UltraISO for a long time now and I never had any issues with them.

The trouble I had was with a not so old (PIII 600Mhz I think) computer wich refused to boot from my CD. I decided to do further testing and I discovered that if I didn't use the "optimize" function, my Multi-Boot CD would work on this machine.

So I wanted to know if other people had similar issues with the Optimisation feature.

Next time I run into a computer doing this, I will burn my ISO optimised by CDIMAGE so I can diagnostic better.

I don't have any issues in the process of creating an optimised ISO.

What are people using to do an optimised ISO when they have a source over 4GB?

Is there any REAL difference between CDIMAGE cmd line utility and the GUI version or the output will be the exact same?

Share this post


Link to post
Share on other sites

honestly, I think CDIMAGE has a limitation of 4 gigs or something. Everytime I built an ISO with the -o option on a multiboot DVD, the XP install would quit on me.

When I tried UltraISO to do the optomize, I found that instead of doing a hash or whatever to determine if the files where teh same, it based it on file size and date I believe. Maybe they fixed it since the version I tried....dunno.

I've been using mkisofs with the dfl option. I haven't tried making a multiboot yet (on my things to do), so I don't know how it'll work.

Share this post


Link to post
Share on other sites

I am going to dig into CDIMAGE but I want some expertise on the matter. What I really wants is MAXIMUM COMPATIBILITY.

On MSFN, the proper command line is the following:

Removing any possible attributes set on D:\AIODVD and its subfolders...

attrib -R -H D:\AIODVD /S /D

CDIMAGE.EXE -lWXPFPP_EN -t12/31/2002,12:00:00 -h -j1 -m -bxpboot.img D:\AIODVD D:\WXPFPP_EN.ISO

On flyakite they suggest:
CDIMAGE.EXE -lWXPFPP_EN -t08/23/2001,09:00:00 -b\AIODVD\BOOT\loader.bin -h -n -o -m \AIODVD D:\WXPFPP_EN.ISO

Ok, now what I don't like about the MSFN command is that first they remove the file attribute and they don't optimise. They also use the j1 option but is this better?

Keep in mind that I seek maximum compatibility. Should I use the -j1 switche with flyakite command?

Here are the options available for CDIMAGE

CDIMAGE 2.47 CD-ROM and DVD-ROM Premastering Utility

Copyright © Microsoft, 1993-2000.  All rights reserved.

For Microsoft internal use only.

Usage: CDIMAGE [options]sourceroot targetfile

       -l  volume label, no spaces (e.g. -lMYLABEL)

       -t  time stamp for all files and directories, no spaces, any delimiter

             (e.g. -t12/31/2000,15:01:00)

       -g  encode GMT time for files rather than local time

       -h  include hidden files and directories

       -n  allow long filenames (longer than DOS 8.3 names)

       -nt allow long filenames, restricted to NT 3.51 compatibility

             (-nt and -d cannot be used together)

       -d  don't force lowercase filenames to uppercase

       -c  use ANSI filenames versus OEM filenames from source

       -j1 encode Joliet Unicode filenames AND generate DOS-compatible 8.3

             filenames in the ISO-9660 name space (can be read by either

             Joliet systems or conventional ISO-9660 systems, but some of the

             filenames in the ISO-9660 name space might be changed to comply

             with DOS 8.3 and/or ISO-9660 naming restrictions)

       -j2 encode Joliet Unicode filenames without standard ISO-9660 names

             (requires a Joliet operating system to read files from the CD)

           When using the -j1 or -j2 options, the -n, -nt, and -d options

             do not apply and cannot be used.

       -js non-Joliet "readme.txt" file for images encoded with -j2 option

             (e.g. -jsc:\location\readme.txt). This file will be visible as

             the only file in the root directory of the disc on systems that

             do not support the Joliet format (Windows 3.1, NT 3.x, etc).

       -u1 encode "UDF-Bridge" media

       -u2 encode "UDF" file system without a mirror ISO-9660 file system

             (requires a UDF capable operating system to read the files)

       -ur non-UDF "readme.txt" file for images encoded with -u2 option

             (e.g. -usc:\location\readme.txt). This file will be visible as

             the only file in the root directory of the disc on systems that

             do not support the UDF format.

       -us sparse UDF files

       -ue embed file data in UDF extent entry

       -uf embed UDF FID entries

       -uv UDF Video Zone compatibility enforced

       -b  "El Torito" boot sector file, no spaces

             (e.g. -bc:\location\cdboot.bin)

       -p  Platform ID for the "El Torito" boot catalog

       -e  Do not set floppy emulation mode in El Torito boot catalog

       -s  sign image file with digital signature (no spaces, provide RPC

             server and endpoint name like -sServerName:EndPointName)

       -x  compute and encode "AutoCRC" values in image

       -o  optimize storage by encoding duplicate files only once

       -oc slower duplicate file detection using binary comparisons rather

             than MD5 hash values

       -oi ignore diamond compression timestamps when comparing files

       -os show duplicate files while creating image

           (-o options can be combined like -ocis)

       -w  warning level followed by number (e.g. -w4)

           1  report non-ISO or non-Joliet compliant filenames or depth

           2  report non-DOS compliant filenames

           3  report zero-length files

           4  report each file name copied to image

       -y  test option followed by number (e.g. -y1), used to generate

             non-standard variations of ISO-9660 for testing purposes:

           1 encode trailing version number ';1' on filenames (7.5.1)

           2 round directory sizes to multiples of 2K (6.8.1.3)

           5 write \i386 directory files first, in reverse sort order

           6 allow directory records to be exactly aligned at ends of sectors

               (ISO-9660 6.8.1.1 conformant but breaks MSCDEX)

           7 warn about generated shortnames for 16-bit apps under NT 4.0

           b blocksize 512 bytes rather than 2048 bytes

           d suppress warning for non-identical files with same initial 64K

           l UDF - long ads used in file entries instead of short ads

           r UDF - number of ad's is random

           w open source files with write sharing

           t load segment in hex for El Torito boot image (e.g. -yt7C0)

           f use a faster way to generate short names

       -k  (keep) create image even if fail to open some of the source files

       -m  ignore maximum image size of 681,984,000 bytes

       -a  allocation summary shows file and directory sizes

       -q  scan source files only, don't create an image file

       NOTE: Many of these options allow you to create CD images

             that are NOT compliant with ISO-9660 and may also

             NOT be compatibile with one or more operating systems.

             If you want strict ISO and DOS compliance, use the -w2

             warning level and correct any discrepencies reported.

             YOU are responsible for insuring that any generated CDs

             are compatible with all appropriate operating systems.

             Also note that Microsoft company information is placed

             in the image volume header, so don't use this program

             to generate CDs for companies other than Microsoft.

Share this post


Link to post
Share on other sites

Well, see the switches I use:

cdimage.exe -l"WXP_AIO" -h -j1 -b"C:\wxpsp2\easyboot\loader.bin" -o -w1 -m "C:\wxpsp2" "h:\xpsp2.iso"

And you don't need to use the switch to remove file attributes - that is there only for a few special cases where some ppl had problems. And the msfn guide did not tell you to optimise, simply because optimised ISO was not the objective of the guide. And I say *ALWAYS* use the "-j1" option bcos its better.

And more things to keep in mind - many ppl did not have problems, but I *REPEAT* that ultraiso/easyboot is *NOT* good for optimised ISOs. (remember I support these tools for all other purposes, but not for this one)

I always use cdimage.exe for my optimised ISO and haven't had a problem even once with it, because my files total up to 3560 MB (therefore below 4 GB).

So that's that.... *MAXIMUM COMPATIBILITY* above.

The command-line and GUI versions of CDimage are both the same - they'll give you the same result. Only difference is the GUI version is easy to use. :P Hmm.... So what else?

Hoping this helps....

Share this post


Link to post
Share on other sites

@prathapml

Yes! it sure helps... I like clear answers and explanation. Thanks

Can you give me more details about this -j1 options? Is it going to truncate my file names, is it going to capitalize every name?

-j1 encode Joliet Unicode filenames AND generate DOS-compatible 8.3
filenames in the ISO-9660 name space (can be read by either
Joliet systems or conventional ISO-9660 systems, but some of the
filenames in the ISO-9660 name space might be changed to comply
with DOS 8.3 and/or ISO-9660 naming restrictions)

Share this post


Link to post
Share on other sites
Can you give me more details about this -j1 options?
Well, cdimage gave you the long/complex description. To put it in a short way, you can just say "-j1" keeps your file-names exactly as how it was on your HDD. (No unnecessary capitalizing, no truncated file-names, just direct-as-it-is, if you get what I mean :) ).

Okay, there's a few more things to keep in mind, while using cdimage though:

1. If you want your CD to be bootable, ensure that "-y1" is *NOT* used.

2. I think there's some sort of limitation in cdimage.exe about file-names (should not be more than 256 characters) - but that's no problem since I don't like to give such big names to files. :lol:

3. It will warn you if directory depth is more than 8-levels (i.e., 8 directories one-below-the-other anywhere in your CD) - that warning means that if you try to go to access the 9-th level directory in DOS, you can't access it. In windows mode it will still work perfectly well. This is a limitation of the ISO9660 format, and is not a fault of cdimage. (so if you want to be able to install XP after booting into DOS, ensure that your entire files in I386 are properly within 8-levels limit) The I386 files will be read properly in XP-setup (text-mode, i.e., blue screens) and in WinPE even if you break that limit.

Everytime I built an ISO with the -o option on a multiboot DVD, the XP install would quit on me.
Maybe the solution has something to do with point 3 of this post? Anyways, if its working fine for you now, all's good and ignore this comment. :)

Share this post


Link to post
Share on other sites

So if I understant correctly, it will work even if I exceed the 8 level limit in the Windows Installation setup

For Example my $OEM$ folder is the longest:

AIO-DVD\SYSTEME\XPSP2FR\$OEM$\$1\drivers\ATI\Driver\2KXP_INF\B_17656

Also, what is your solution for a DVD over 4GB of source file?

BTW thanks for all theses informations! Maybe you should add them to your Sticky about Multi-Boot :thumbup

Share this post


Link to post
Share on other sites
So if I understand correctly, it will work even if I exceed the 8 level limit in the Windows Installation setup.
Yes, that's correct.

Ha ha... don't worry about the path-names of your drivers in $OEM$ being long. Mine is longer than that, with all the graphics chipsets I need to support. ;)

what is your solution for a DVD over 4GB of source file?
In such a case, there is no need for optimising, isn't it? The DVD gives a nice amount of space (4.3 GB, or 8.5 GB with newer disks) to fit all your files into. The only reason why you need to create an ISO before burning to CD is to optimize (or to test in VMware). So if I'm burning to DVD and source files is more than 4 GB, I just directly use Nero! If I need to create an ISO (without optimization) of more than 4 GB I use Nero's Image Recorder. :D

Time stamp?

Use it if you want.... It makes no problems whether you use it or not. It will work perfectly with/without. Its just for your own satisfaction about CD/DVD release date.

Share this post


Link to post
Share on other sites

Cool! I just finished the compilation with your CDIMAGE parameter... I will test soon.

the 4GB barrier will be a problem to me because my next step is a full packed Multi-Boot DVD and I NEED the optimise feature for sure. I always prefer to create an ISO before burning so I can test and also easily duplicate...

Share this post


Link to post
Share on other sites
the 4GB barrier will be a problem to me

Well, I heard about that 4GB barrier from one of Alanoll's posts. So I'm not so sure about it (as far as first-hand information goes). Just try your luck and please post whether there actually is such a barrier. :P

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...