30 replies to this topic

[patsch]

I have a little problem creating an iso file greater than 1GB
My project now has a size of 6.542.123.196 Bytes
I want to have an iso file for emulating my project in virtual box.

The project stops due to an error

Retrieve - Failed to retrieve the file size from: [%BaseDir%\ISO\Win7PE_x86.ISO] - File does not exist:

this is what I see in the log file

[Success] Retrieve - Sucessfully retrieved the directory size from: [%BaseDir%\Target\Win7PE_SE] to variable: [%sizeFolder%] with result: [-2047811396]
[Success] StrFormat - converted: [-2047811396] to variable: [%sizeFolder%] with result: [-2047811396 Bytes]
[Info] Creating ISO: [%BaseDir%\ISO\Win7PE_x86.ISO] Folder size: -2047811396 Bytes

I think the problem is the negative size of the folder.
Is there an easy way to fix that problem?

Attached Files

•  log_20120310_153300_Win7PE_SE_Support.7z   133.69KB   2 downloads

[pscEx]

There is a glitch in WinBulder up to version 82: It calculates some values with 32-bit integers, where 64-bit integers would be necessary.
This is fixed in the until now not released latest WinBuilder.

My actual WinBuilder developer version (without any guarantee) is included in the multiPE project.

Peter

[patsch]

thanks Peter, that solves the error message
nevertheless the burning size of my Image is about 720MB and not the 6GB (the size of my target folder)
I will post a log later

[patsch]

ok, here is the log

Retrieve - Sucessfully retrieved the directory size from: [%BaseDir%\Target\Win7PE_SE] to variable: [%sizeFolder%] with result: [6517908869]
StrFormat - converted: [6517908869] to variable: [%sizeFolder%] with result: [6,07 Gb]
Creating ISO: [%BaseDir%\ISO\Win7PE_x86.ISO] Folder size: 6,07 Gb
[//]
IF - [true] is equal to: [true] evaluated string: [If,%pCheckBox1%,Equal,true,Set,%Show_mkiso%,Open]
SetVar - Sucessfuly changed the value of [%Show_mkiso%] to: [Open]
IF - [boot/grldr] is not equal to: [boot/etfsboot.com] evaluated string: [If,%BootSect%,Equal,Boot/etfsboot.com,Run,%ScriptFile%,NormalCD]
IF - [boot/grldr] is not equal to: [boot/etfsboot.com] evaluated string: [If,Not,%BootSect%,Equal,Boot/etfsboot.com,Run,%ScriptFile%,CompatibleCD]
Run - Processing section: [CompatibleCD] From file: [%BaseDir%\Projects\Win7PE_SE\Finals\4-iso.script]
IF - [grub4dos] is not equal to: [isolinux] evaluated string: [If,Not,%BootSector%,Equal,IsoLinux,ShellExecute,%Show_mkiso%,"%Tools%\mkisofs.exe","-v -iso-level 4 -l -J -joliet-long -R -volid "%Volume_Name%" -A "GRLDR/MKISOFS" -sysid "Win32" -b "%BootSect%" -no-emul-boot -boot-load-size 4 -hide boot.catalog -duplicates-once -o "%ISOfileVar%" "%targetdir%""]
ShellExecute: [Open] using: [%BaseDir%\Projects\Tools\Win7PE_SE\mkisofs.exe] with parameters: [-v -iso-level 4 -l -J -joliet-long -R -volid "Win7PE" -A "GRLDR/MKISOFS" -sysid "Win32" -b "Boot/grldr" -no-emul-boot -boot-load-size 4 -hide boot.catalog -duplicates-once -o "%BaseDir%\ISO\Win7PE_x86.ISO" "%BaseDir%\Target\Win7PE_SE"]
ELSE - [ShellExecute,%Show_mkiso%,#$q%Tools%\mkisofs.exe#$q,"-v -iso-level 4 -l -J -joliet-long -R -volid #$q%Volume_Name%#$q -A #$qGRLDR/MKISOFS#$q -sysid #$qWin32#$q -b #$q%BootSect%#$q -no-emul-boot -boot-load-size 4 -c isolinux/boot.cat -boot-info-table -duplicates-once -o #$q%ISOfileVar%#$q #$q%targetdir%#$q"]
Run - Processed section [CompatibleCD] in file: [%BaseDir%\Projects\Win7PE_SE\Finals\4-iso.script]
[//]
Retrieve - Sucessfully retrieved the file size from: [%BaseDir%\ISO\Win7PE_x86.ISO] to variable: [%sizeISO%] with result: [721309696]
StrFormat - converted: [721309696] to variable: [%sizeISO%] with result: [687,89 Mb]
ISO build size is 687,89 Mb

Attached Files

•  log.7z   199.18KB   3 downloads

[pscEx]

Ununderstandable!

What shows a compare of the %target% and ISO tree?

What about "Duplicates Once"? But I cannot imagine that there are so many duplicates in %Target%

Peter

[Wonko the Sane]

Why not posting a:

DIR /S <whatever>TargetWin7PE_SE >C:mytarget.dir

and a DIR /S of the built .iso?


Wonko

[patsch]

here are the 2 files ... and the log file

Attached Files

•  myisodir.7z   305bytes   4 downloads
•  mytargetdir.7z   11.7KB   8 downloads
•  log.7z   183.07KB   2 downloads

[pscEx]

A misunderstanding about the ISO Tree:

Open the ISO with e.g 7z, expand anywhere and tell us the expanded tree.

Peter

[patsch]

sorry for misunderstanding ... here the result of the extracted iso

Attached Files

•  extracteddir.7z   11.45KB   5 downloads

[pscEx]

In your explored target dir I do not find any piece of the missing 5 GB. (ISO 720 MB, Target dir (as you wrote above) 6 GB)

Do You?

Peter

[patsch]

I do not get it ...
Explorer, TC and DirStat-Tools tell me that the ISO has a size of 720MB
If I mount that ISO with Daemon-Tools, I get the right size of the content (ergo the size of the target dir), but I have no access to the files, I cannot copy files from that mounted iso to my hard drive (tried with the 0 Byte files like menu.lst (see extracted content)).

[MedEvil]

If I mount that ISO with Daemon-Tools, I get the right size of the content

Which tool do you use, to get the size, after mounting the iso with daemon tools?

[ChrisR]

Which tool do you use, to get the size, after mounting the iso with daemon tools?

a DIR /S of the built .iso?

in your extracteddir.dir there are several files whose size is at 0 eg: TargetWin7PE_SEimages folder
win7sp1x64ger.iso : 0 B in extracteddir - 3 GB in TargetDir
win7sp1x86ger.iso : 235 MB in extracteddir - 2.33 GB in TargetDir.
Here we have the 5 GB.

What do you do with the 2 isos win7sp1x64(x86)ger.iso Inside the new built iso ?

[patsch]

that are my isos that I use for installation
http://www.rmprepusb...ials/firawiniso

[ChrisR]

OK, but there should be an issue with mkISOfs when building the new Iso, try to recreate the iso

[patsch]

i have tried it several times, I also updated mkisofs to a newer version

what I have done yet: I played around with MBAM (Multiboot ISO Maker, http://reboot.pro/96...dpost__p__83397 )
and the result with these parameters look good, I will try it out a bit more this evening

mkisofs.exe -b grldr -A -allow-multidot -boot-load-size 4 -debug -iso-level 4 -J -joliet-long -l -no-emul-boot -R -udf -V Win7PE_SE -o C:\temp\test.iso D:\workspace\wb\Target\Win7PE_SE

[ChrisR]

I also tried by adding an Iso of 3 GB in TargetDir and with the current version of mkisofs, the creation of the iso fails with the message:

mkisofs: Implementation botch: FS should end at 4294611741 but ends at 188260

By replacing mkisofs (in %tools% folder) by the version of of mbim_alpha_07_R01 , there is no more problem (with the iso script).
In the multiple versions of mkisofs, where can I find the best or latest version ?

[cdob]

win7sp1x64ger.iso : 0 B in extracteddir - 3 GB in TargetDir
win7sp1x86ger.iso : 235 MB in extracteddir - 2.33 GB in TargetDir.

That's files greater 2gb. Does Win7PE_SE uses a non official, historic mkisofs version from 2004 still?
What about a update or another application?

I also updated mkisofs to a newer version

That's a good idea.

[ChrisR]

That's files greater 2gb. Does Win7PE_SE uses a non official, historic mkisofs version from 2004 still?
What about a update or another application?

Yep, I believe that it is indeed the 2GB, a link about an update, official version or a good replacement ?

[cdob]

a link about an update, official version

That's a source code only release http://cdrecord.berlios.de/

Jörg links to Thomas win32 binary http://www.student.t...t/thomas.plank/

or a good replacement ?

That's a difficult question.

There are different approaches arround.
A summary http://code.google.com/p/mkisofs-md5/

I'm used to http://cdob.boot-lan...uplicates_once/

[ChrisR]

Thank you, I'll watch later

[patsch]

By replacing mkisofs (in %tools% folder) by the version of of mbim_alpha_07_R01 , there is no more problem (with the iso script).

that is very strange because an mkisofs.exe -version shows that from version number these two should be the same, namely "mkisofs 2.01-bootcd.ru (i686-pc-mingw32)"
But for sure they have a different size

My try is to use the "mkisofs 3.01a06 (i686-pc-cygwin)", but then I have to add 3 dlls (cygiconv-2.dll, cygintl-8.dll, cygwin1.dll), I'll test it later if I have time to

[pscEx]

try the mkisofs of multiPE!

Peter

[patsch]

thx Peter, but your version gives the same error like the mkisofs 3.01a06 from Link above (but you have another cygwin1.dll)

Run - Processed section [CompatibleCD] in file: [%BaseDir%ProjectsWin7PE_SEFinals4-iso.script]
[//]
[Failed] Cannot open file "%BaseDir%ISOWin7PE_x86.ISO". Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird: [Retrieve,FileSize,%ISOfileVar%,%sizeISO%]
[Failed] StrFormat - Failed to convert [Bytes] because [] value is not valid:
[Info] ISO build size is
Run - Processed section [Process] in file: [%BaseDir%ProjectsWin7PE_SEFinals4-iso.script]

[cdob]

that is very strange because an mkisofs.exe -version shows that from version number these two should be the same, namely "mkisofs 2.01-bootcd.ru (i686-pc-mingw32)"

Yes, version string was not updated.
Versions seems to be http://fy.chalmers.s...RW/tools/win32/

That's another historic version and adds files up to 4 GB.
Default windows installation ISO files are below 4 GB.
A nice replacement for current Win7PE_SE.

A current mkisofs adds files up tp 8 TB.

Hint deleted

I like

mkisofs 3.01a07-bootcd.ru (i686-pc-cygwin)

Edited by cdob, 28 March 2012 - 06:34 PM.