Size of iso build

I am using version 072, and my build size is apparently too small --ISO build size is 34.00 Kb. Am I missing something?

I am using version 072, and my build size is apparently too small --ISO build size is 34.00 Kb. Am I missing something?

By the size of your iso, i would say, you miss everything!
Which project did you try to build?

MedEvil, thanks for responding and so quickly. Please excuse my ignorance. I don't know what a project is. I've tried to create a Vista iso. I selected the downloads I wanted using WinBuilder. Then I tweaked the scripts a little. After the build, I see only one error. In the saved html file, toward the end I see:
" [Info] Creating ISO: [%BaseDir%\ISO\VistaPE.iso] Folder size: 311.80 Mb"
Then a few more lines of code later I see:
"ISO build size is 34.00 Kb"

By the size of your iso, i would say, you miss everything!
Which project did you try to build?

MedEvil, thanks for responding and so quickly. Please excuse my ignorance. I don't know what a project is. I've tried to create a Vista iso. I selected the downloads I wanted using WinBuilder. Then I tweaked the scripts a little. After the build, I see only one error. In the saved html file, toward the end I see:
" [Info] Creating ISO: [%BaseDir%\ISO\VistaPE.iso] Folder size: 311.80 Mb"
Then a few more lines of code later I see:
"ISO build size is 34.00 Kb"

nativeEx, VistaPE, LiveXP... are all projects.
My general advice would be to delete all the folders in your WB folder and download fresh. Then try building Vista without fiddeling with the scripts!
Just set the path to your source and if you have the WAIK installed, set the path to this in the standart-pre(something) script too.

Don't close WB before you checked the newly build iso!
If you still have problems. Go to 'log' press 'save Log'. This will create a html file in the same folder WB is.
Zip this html file and post it here in the forum, so someone can tell you what's going on.

Thanks a lot.

@CharlesP:

Let me join the '34 kB team'. I represent version 074. See here.

I hope when Nuno is back, he will blow up our party by taking this WinBuilder 'feature' away.

Peter

WB v74 has some odd behavior. Do not fiddle with scripts as the project(s) run, it disturbs path settings for some reason.

First the main statement which is repeated later:
So in my opinion this error does not depend on user's input but is rather random and caused WinBuilder internally.

As a 'Big Quiz' for Nuno:

Currently I'm fighting against some Native API / ntdll.dll issues.

Because I'm currently not able to debug the native app itself (maybe somebody tells me how), I insert debug outputs in the app and show them when running the ISO.

That causes a lot of WinBuilder builds.

In my opinion 15 of 100 builds show the 34 kb behaviour. Nothing is changed but only some files inside %Target%. So in my opinion this error does not depend on user's input but is rather random and caused WinBuilder internally.

BTW: After several hours of testing (I estimate about 70 builds) I got errors that the system is out of ressources and out of memory.
After restarting WinBuilder, everything has been ok again.

Peter

BTW: After several hours of testing (I estimate about 70 builds) I got errors that the system is out of ressources and out of memory.
After restarting WinBuilder, everything has been ok again.

Yes, I get that happening intermittently as well.

Commands such as the following

FileCopy,"Folder\*.*","Newfolder"

or

DirCopy,"Folder\*.*","Newfolder"

do not always work correctly in that if the folder contains multiple folders, the last one's name gets truncated from say 'Folder\Lastfolder' to something like 'Newfolder\Lastfol'.

Galapo.

Yes, I get that happening intermittently as well.

Commands such as the following

FileCopy,"Folder\*.*","Newfolder"

or

DirCopy,"Folder\*.*","Newfolder"

do not always work correctly in that if the folder contains multiple folders, the last one's name gets truncated from say 'Folder\Lastfolder' to something like 'Newfolder\Lastfol'.

Galapo.

In my case I did not check the log, I only restarted the 'Build ISO'. But I'm sure that in all these cases in the log there are also the 'truncated lines' I mentioned here.

@Nuno: Try to find out, why sometimes the log lines are truncated. Maybe that brings you to the root of the issue.
Perhaps also the 'running out of ressources and memory' I mentioned some posts above, may be helpful.

Peter

No, I didn't check the log either. What I was referring to was actual commands not being carried out (not lines in the log). 'FileCopy' and 'DirCopy' do not always copy correctly as the last folder within a directory gets its name truncated in the copy.

Regards,
Galapo.

Today I counted:

3 of 23 ISO builds got the 34 kB size.

Peter

Does it make any difference whether 'Boot SDI' or 'Create ISO' scripts are selected? That is, is the issue isolated at all?

Regards,
Galapo.

Does it make any difference whether 'Boot SDI' or 'Create ISO' scripts are selected? That is, is the issue isolated at all?

Regards,
Galapo.

For the nativeEx_BSOR project I use a modified version of 'Create ISO'.
It does some additional target tunings and it extracts the boot sector from the source CD's spcmdcon.sys before building the ISO. But logically it is working like its parent.
No RAM boot of any kind, no FBWF.

Peter

For the nativeEx_BSOR project I use a modified version of 'Create ISO'.
It does some additional target tunings and it extracts the boot sector from the source CD's spcmdcon.sys before building the ISO. But logically it is working like its parent.
No RAM boot of any kind, no FBWF.

Peter

@Galapo:
I think that you should not concentrate on the 'Make ISO'.

I found the famous 'truncated lines' also in different scripts' logs.

But I think, if something goes wrong in an 'unimportant' script, you only have some issues when running the PE, and the usual user does not realie it or thinks 'Maybe I did something wrong'. We rarely get error posts about such an issue.

If on the other hand it happens when creating the ISO, you get a non running ISO. And that is an issue to report.

Peter

Hi Peter,

Yes, I agree that the issue may not really be recognised outside of when it occurs when the image is built.

So all of this is tied together:

- iso image not built correctly due to some input truncation
- truncation of log lines
- truncation of copyiny last directory with 'FileCopy' and 'DirCopy' resulting in incorrect 'copy'

Regards,
Galapo.

Hi Peter,

Yes, I agree that the issue may not really be recognised outside of when it occurs when the image is built.

So all of this is tied together:

- iso image not built correctly due to some input truncation
- truncation of log lines
- truncation of copyiny last directory with 'FileCopy' and 'DirCopy' resulting in incorrect 'copy'

Regards,
Galapo.

@Galapo
I disagree with your conclusion.
My statement is:
If you see anywhere in the log a truncated line (usually not closing an opening '[' with ']'), you can assume that something is wrong with your ISO.

• Maybe the 'Wrong' is in lower levels, like in 'Building the ISO': You see the issue's result at once after starting the ISO.
• Maybe the 'Wrong' is in higher levels: You see the issue's result only after starting certain tasks in the ISO.
  Therefore these issues are rather hidden and therefore rarely reported.

Peter

BTW: I'm sure that your 'Copy' therory depends on your personal special issues, but in general it is not a part of the issue's reason.

Sorry, what I was attempting to suggest was that these separate issues may be related. At least they are all related in some way to truncation. So I also agree with what you wrote and don't think that what I suggested may be incompatible. But maybe it is. I'll have to see if I can reproduce the FileCopy and DirCopy issues more widely.

Regards,
Galapo.

Bump!

Just for Nuno to get knowledge about this 'voodoo'

Peter