how to reduce windows iso dvd folder size

nuhi said:
Have you tried the "Manual Setup" component removal? That entire "ISO" branch of components does the same.
Let me know if you find it has leftovers, also you can remove one Boot Loader that you don't use (BIOS vs EFI).
Click to expand...
yes sir it work flawlessly . but i think there must be a option in NTLite app to add customzed $OEM$ from user side to sources directory without any need to manual copy paste so that final iso be created directly from NTLite containing $OEM$ directory inside sources too.
 
|====| said:
yes sir it work flawlessly . but i think there must be a option in NTLite app to add customzed $OEM$ from user side to sources directory without any need to manual copy paste so that final iso be created directly from NTLite containing $OEM$ directory inside sources too.
Click to expand...
To automate batch script operations on the host machine after update integration, see inside any preset:
Code: 
    <Commands>
        <PostUpdates>
            <!--<Command>example [MOUNTDIR]\Windows parameters</Command>-->
        </PostUpdates>
    </Commands>
You could have a command or a script there to copy $OEM$ automatically, note mountdir is not it - it may need imagedir (non-existent for now) for your scenario, so use a full path instead.
Should be self-explanatory, let me know if you try and it doesn't fire, it's not that known or tested feature - added it during testing as a side-thought.

For outside of image files, $OEM$ and similar, use the above method, also it's so simple for a user to maintain files on their own on the original ISO dir even before copy and load, so it's not worth the investment from the tool's side.

For inside the image, a similar topic, due to file permissions it would be nice to have, but it's not for that many users and it's complicating debugging once more people start messing with the internal files due to ease of use.
 
nuhi said:
To automate batch script operations on the host machine after update integration, see inside any preset:
Code: 
    <Commands>
        <PostUpdates>
            <!--<Command>example [MOUNTDIR]\Windows parameters</Command>-->
        </PostUpdates>
    </Commands>
You could have a command or a script there to copy $OEM$ automatically, note mountdir is not it - it may need imagedir (non-existent for now) for your scenario, so use a full path instead.
Should be self-explanatory, let me know if you try and it doesn't fire, it's not that known or tested feature - added it during testing as a side-thought.

For outside of image files, $OEM$ and similar, use the above method, also it's so simple for a user to maintain files on their own on the original ISO dir even before copy and load, so it's not worth the investment from the tool's side.

For inside the image, a similar topic, due to file permissions it would be nice to have, but it's not for that many users and it's complicating debugging once more people start messing with the internal files due to ease of use.
Click to expand...
Ok sir i understood it :)
 
compact %windir% using Lzx compression for all exe to save 50% of C:\ drive space :

@echo off
cd /d %windir%
COMPACT /C /S /A /I /F /EXE:lzx
Click to expand...
 
are there any performance/resource issues when compacting an OS like the other thingy does? i forget its name, senior moment :oops: :rolleyes:
 
Clanger said:
are there any performance/resource issues when compacting an OS like the other thingy does? i forget its name, senior moment :oops: :rolleyes:
Click to expand...
clanger am using compacted OS only windows directory since 1904x.1741 build from 8th of June means since one week & havent had any issues till date. pl try or else if any issue is seen you can simply uncompact the os via same commandline tool :)
 
Clanger said:
are there any performance/resource issues when compacting an OS like the other thingy does? i forget its name, senior moment :oops: :rolleyes:
Click to expand...
There is for sure performance decrease using compression, it's just not as noticeable nowadays with newer hardware. It's the same as when disabling timestamps used to actually be a big performance boost, but nowadays you just lose more features by disabling that than it's worth.

There's two kinds of compression:
- compact (drives and files): CMD > compact /u /s /a /i /f /q
- compress OS binaries: CMD > compact /CompactOS:never

The single biggest performance boost I ever saw back in the old days, using XP with old hardware was running these commands:
compact /u /s /a /i /f /q C:
compact /u /s /a /i /f /q C:\*.*

Registry keys related to this are:

; Hidden > NTFS File Compression > Disabled
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem]
"NtfsDisableCompression"=dword:00000001

; Hidden > OS File Compression > Disabled
[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WOF]
"ForceNoCompression"=dword:00000001

I just found that last registry key and Google has zero documentation on it. I got that "ForceNoCompression" key by using RegChangesView and comparing registry before and after using the "CompactOS:never" command.

I have a hard time believing that there isn't going to be some performance loss from also using compress os binaries since even in a fully tweaked system you have almost 1 gig of stuff loaded into RAM while idling, so that must all be OS files, so the chances are decent that compression is affecting that a little bit. But that kind of stuff is above my paygrade, so I'll leave it up to smarter people to figure out :p

Either way I find it to be extremely odd how people that are trying to get every single bit of performance out of their systems are then also doing stuff like compressing the drives in various ways to save a few MB, when it's just hurting performance. I mean, if you're hurting *that* bad for storage space, buy another drive. They're stupidly cheap nowadays, it costs as much to buy a high performance SSD as it does to take a family of 4 to McDonalds. When you've got a 1000-2000$ computer and can't bring yourself to spend $50 on some storage then that's on them...
 
Clanger said:
30GB in 1 task alone, think im worried about an os being 2GB less in size?
Click to expand...
Haha, yeah there was lots of times I was crashing my XP because I'd be trying to open 300+ page word files, and 2+ gigabyte GIMP projects, etc. I am excited about being on 64 bit finally just so I don't have to deal with that anymore lol.

Oh to addon to my last as well, I tried the ESD version of Windows Install the other day and it was way slower. That form of compression definitely slows down the install process at least, Windows Setup took much longer than using WIM. Just throwing that info out there for anyone curious. So I imagine the compactos is going to slow down the Setup process at least, even if it doesn't affect the desktop environment.
 
Hellbovine said:
Oh to addon to my last as well, I tried the ESD version of Windows Install the other day and it was way slower. That form of compression definitely slows down the install process at least, Windows Setup took much longer than using WIM. Just throwing that info out there for anyone curious. So I imagine the compactos is going to slow down the Setup process at least, even if it doesn't affect the desktop environment.
Click to expand...

O/T - When installing ESD, switch to a max power plan.
https://www.ntlite.com/community/in...g-power-plan-in-boot-wim-file.2411/post-20292
 
You must log in or register to reply here.
Back
Top