SystemDrive X Size

Is there a setting in Gena that controls the size of X? I had a 200mb build and my X drive was a good size and I could run my AntiVirus. Decided to make a smaller build (88MB) and now my Antivirus will not run because drive X is too small. I have looked the scripts over and I know how to increase ram size but how do I increase the systemdrive X?

The option is on all of the 'Create Image' scripts:







Regards,
Galapo.

The option is on all of the 'Create Image' scripts:

Thanks. To be honest, didn't look there. Seems like a weird place for that option  I am using the wim boot option so should I play with the compression setting? How does this effect the size of the X drive?

Each different different script has to do things a bit differently, so in that way it makes sense to set the option there. If you make a default build, that is build without any writeable system drive. To take such things into account we'd have to make another script for this under 'Basic'. Personally, I'm not sure that that is needed. When someone changes to a different 'Create Image' script, they are selecting an entirely different build option, and they should adjust the script settings to those that are needed.

Yes, on WimBoot, writeable size by default is 160mb. But remember that this is dependent upon the actual RAM available in the machine once booted.

I provided an image of all three 'Create Image' scripts to show the option to set. You didn't specify which one you were using (and I don't have telepathy or such) and so gave all three to cover the bases.

Regards,
Galapo.

You can read about overlay cache data compression a bit here: http://msdn.microsoft.com/en-us/library/ee832773.aspx

Regards,
Galapo.

I provided an image of all three 'Create Image' scripts to show the option to set. You didn't specify which one you were using (and I don't have telepathy or such) and so gave all three to cover the bases.

  So use to using Wim boot option, just figured  everyone should know I use it  Sorry, I will try to be more specific in the future. Thanks for your replies, Galapo.

Is there a guide on Wimboot settings?

Not that I know of. WimBoot script has been developed by Nikzzzz. I don't know exactly what all the options do exactly. Trial and error and testing is needed.

Nikzzzz is like me: developing something is fun, but writing documentation is very boring and hard to get around to.

Regards,
Galapo.

Not that I know of. WimBoot script has been developed by Nikzzzz. I don't know exactly what all the options do exactly. Trial and error and testing is needed.

Nikzzzz is like me: developing something is fun, but writing documentation is very boring and hard to get around to.

Regards,
Galapo.

I understand that. 160 compress gives me the most X drive but still small than my bigger build. Must work on a percentage, the smaller the build, the smaller the X drive? Just a guess. 

I don't think WimBoot works on a percentage.

Have much free space is on the system drive when you boot?

Regards,
Galapo.

I don't think WimBoot works on a percentage.

Have much free space is on the system drive when you boot?

Regards,
Galapo.

Actually, just traced down the root of my problem. PENetwork was coping drivers out of the wrong driver pack folder and it was 60mb on a 153 mb drive. The properties of the X are not accurate. Shows 153 mb with only 2.37mb used and 149 free. This is not correct.  Opera 12 is 31 mb plus the other stuff so no wonder my Antivirus ran out of space. Not sure why the system properties of X show the wrong info on space left? 

The free space is the size of the overlay filter driver. This is the free space after the WIM image has been loaded to RAM.

Also, remember that if you have compression enabled, then usage on the drive will be increased with respect to the files size being copied to it.

Regards,
Galapo.

The free space is the size of the overlay filter driver. This is the free space after the WIM image has been loaded to RAM.

Also, remember that if you have compression enabled, then usage on the drive will be increased with respect to the files size being copied to it.

Regards,
Galapo.

I always build with compression at 160. I am going to try one with that option unchecked. Curious to see what the difference is

The properties of the X are not accurate.

This is common for filter drivers (especially with compression), besides not too bad accurate, only 2-3 mb tolerance, which is OK ;)

I believe You get something wrong, the free space is not relevant to what is inside (what you add) .wim, it is about what you "add after",
with other words:
Adding Opera, Antivirus etc. available inside .wim during build does not effect available size.
ex:
240 MB .wim size, 160 MB available free space on X:

with other words:
filter driver works after boot, whatever x: size, it "Add" free writable space to x:


I suspect,
you use a routine
http://theoven.org/index.php?topic=370
to copy files after boot , to x:

If that is the case, use B: , like Zanaffer

I understand the drive is bigger and after Opera and things, that the final size would be the 153mb but after Penetwork copies 45mb worth of drivers and nod32 installs, it's 45mb also. These two things run after the system has booted and no matter what I install to X, the free space never moves off of 153mb?   

to copy files after boot , to x:

See, Lacelot, I don't ignore you!  I reconfigured my Nod32 to install to the B drive instead of the X drive. I have plenty of room now. Now I created another problem. I strip my build down from 200mb to 86mb and not sure what I unchecked that effect this but I cant open cmd files anymore or run them. When I try, window pops up and ask me what program would I like to use to open cmd files. Didn't do this on my larger build so I will need to weed through the Winbuild scripts to see what I have done.    Thanks for all you guys replies!

See, Lacelot, I don't ignore you!

Good and Funny indeed, you give me biiig smile of today 

I reconfigured my Nod32 to install to the B drive instead of the X drive.

Very well 
Keep in mind, when you use imdisk as ramdisk, imdisk has a feature to hot increase size of ramdisk 

So here is another advice, which you will thank me a looooot in long term:
reconfigure Nod32 to install %temp% 

%temp%\Nod32 , whatever ;)

With a chance of none of us around here after some years, This way, your preparations will work on any PE (+increase some more flexibility) 


*
Enable
Gena\Finals\1 Optimizations\"BackupRestore Optimizations" on your builds,
will help you like reverting back a good condition where cmd etc. work (ghost ;)) ,
so when you get in very bad trouble with green buttons, you can revert back to a good known condition,
than continue playing with greens again....
faster than rebuilding all again (and again ;))
 

*
some last words about filter driver(s) on X:

As seen on pictures





I copied 2 files (~ 60 MB) and free space shown drop from 159 to 99

Still, don't trust numbers much, it is known filter driver does not work as they report,
ex: here I can not copy single 130 MB file ;) to X:
theorically 1GB option exists on this driver, but no way 

We already know driver not work very properly after some size (and wrong reports),
besides having writable x: is always valuable for many reasons,
nobody complains with having option of a better running ramdisk for bigger tasks.

Shortly: 160 MB limit setting on WimBoot decided by Nikzzzz after various tests



See you around

Mine never goes down. I am not complaining at all. Love this new to me PE stuff. I have not problem installing programs to B to keep X free. 

Mine never goes down.

probably because of me testing with a default build  (+lots of added files....)
besides as you notice, my "used space" on 2nd picture did not increase 
well, filter driver of X: , everything normal as long as it works 

btw, the joke about "funny" is, you go right path not ignoring me, but write my name wrong
 

ps: reminding to use %Temp%... in future

I hope you share all these nice portable stuff after you conclude they are ready 

See you

Sorry. Using my smartphone and it has this auto correct crap. Will type when I get home.