[shutfu]

dead0, hurry up with the new batch bro you're killin me!

i just followed your guide for x86 win7 ultimate word for word, changed nothing in any of the files, and I ended up with a 608mb ISO file that errors on install. =(

[dead0]

shutfu, on 08 September 2010 - 09:17 PM, said:

dead0, hurry up with the new batch bro you're killin me!

i just followed your guide for x86 win7 ultimate word for word, changed nothing in any of the files, and I ended up with a 608mb ISO file that errors on install. =(

ive tried attaching the new batch file but i keep getting upload error


try this: http://www.4shared.c...d4XLy/7x86.html

apply wim tweak on clean win 7 x86 ultimate, unmount with changes, apply dism removal (dism7x86.bat) and then unmount with changes, then run vlite (7x86.ini), then apply 7x86.bat in mount folder and then unmount with changes, run vlite again and apply a service tweak (i usually disable dotnet), remember to copy setup.exe from sources to sources folder, create iso and test

ps windows updates are not required

This post has been edited by dead0: 09 September 2010 - 02:36 PM

[Therian]

I see well thanks....I just got back to my house so sorry for the delay. I will let you know how it works out. I had a error a bit ago with gimagex but I finally fixed it.

*edit*
I finally downloaded all the msu packs requested from the Addx64.bat and a small issue arose I am unable to find KB947821-v5.msu (from MS site or my Updater) I can only find KB947821-v7.msu would this effect anything?

*edit*
I am curious ever have imagex make a backup of your windows and not delete it after you committed and unmounted? Some reason it left over and even after changing security to myself it still refuses to delete after reboot. It still requires permission from my own admin account instead of trustedinstaller.

*edit*
Well tried the new batch files with and without removing winsxs but I still get the same error after services install. I am curious has anyone else run into this issue and if so what was your cause for it?

This post has been edited by Therian: 12 September 2010 - 09:01 AM

[Yorn]

I'm not sure if this has been asked before or not, but does any of this work for those of us with Home Premium 64-bit?

[dead0]

final final refresh is up! see first post with new links for the guide dated 13/09/10. the new batches should work for a clean version and with updates applied. applying updates and vlite winsxs removal is optional. if applying updates, there probably is no need to apply kb947821 (which is now upto version 7 so you will need to edit the add batch files if applying). make sure you also check the addx86/64 as some updates aren't included in the download links.

This post has been edited by dead0: 13 September 2010 - 04:02 PM

[dead0]

Yorn, on 13 September 2010 - 03:56 PM, said:

I'm not sure if this has been asked before or not, but does any of this work for those of us with Home Premium 64-bit?

i tried to use my method on HP x64 but i kept getting install errors. for some odd reason when using dism on HP, setup crashes.

ps if you dont use media center, you could try my batches but cant guarantee it will work?

This post has been edited by dead0: 13 September 2010 - 04:06 PM

[Therian]

I found a possible error Dead. KB982519 is in the list of updates folder I downloaded off the new link...but its not in the addx64.bat from the new batch files.
dism /image:c:\s2 /add-package /packagepath:c:\s1\sources\KB982214.msu
dism /image:c:\s2 /add-package /packagepath:c:\s1\sources\KB982664.msu
dism /image:c:\s2 /add-package /packagepath:c:\s1\sources\KB982665.msu

So is it needed or was it not needed and just found its way into the folder? Here is a link to the file description. http://www.microsoft...c6-2046ebd72a3c


*edit*
Well it seems the new batch files work.....actually installed this time lol. ISO size was 825mb. Is this typical size? The only thing I skipped was the winsxs removal and I allowed updates....gonna try doing the removal tomorrow and see what happens.

This post has been edited by Therian: 17 September 2010 - 08:55 PM

[dead0]

Therian, on 16 September 2010 - 06:49 PM, said:

I found a possible error Dead. KB982519 is in the list of updates folder I downloaded off the new link...but its not in the addx64.bat from the new batch files.
dism /image:c:\s2 /add-package /packagepath:c:\s1\sources\KB982214.msu
dism /image:c:\s2 /add-package /packagepath:c:\s1\sources\KB982664.msu
dism /image:c:\s2 /add-package /packagepath:c:\s1\sources\KB982665.msu

So is it needed or was it not needed and just found its way into the folder? Here is a link to the file description. http://www.microsoft...c6-2046ebd72a3c


*edit*
Well it seems the new batch files work.....actually installed this time lol. ISO size was 825mb. Is this typical size? The only thing I skipped was the winsxs removal and I allowed updates....gonna try doing the removal tomorrow and see what happens.

the kb982519 was superceded by another in the batch file. you no longer need to do the winsxs removal in vlite. the batch file will clear the contents of the winsxs folder but still keep folders for windows update purposes

This post has been edited by dead0: 18 September 2010 - 03:43 PM

[Therian]

Oh I see thank you. BTW I noticed a odd issue today on my 40GB test drive. The install size of windows is showing up as 11GB but that seems to big considering a full install is only a little bigger...winsxs folder is 260mb and hibernation/system restore is disabled. Installed it twice with the same results. Could perhaps something else be running that I am not thinking of? Unpacked it shows it as 3.7GB...so not sure where the space being used is.

This post has been edited by Therian: 20 September 2010 - 09:51 AM

[alvinkhorfire]

dead0

Correct me if I am not mistaken. You can add in the following line in the winsxs section of your batch removal file:

del /q amd64_microsoft-windows-font-bitmap-courier_31bf3856ad364e35_6.1.7600.16385_none_5283fef09ca6fa1a.manifest
del /q amd64_microsoft-windows-font-bitmap-fixed_31bf3856ad364e35_6.1.7600.16385_none_db04d3f548508fd9.manifest
del /q amd64_microsoft-windows-font-bitmap-ms_serif_31bf3856ad364e35_6.1.7600.16385_none_2670fbc842c5cd2f.manifest
del /q amd64_microsoft-windows-font-bitmap-oem_31bf3856ad364e35_6.1.7600.16385_none_59590e92c817a4e0.manifest
del /q amd64_microsoft-windows-font-bitmap-small_31bf3856ad364e35_6.1.7600.16385_none_d7839341959a2de0.manifest
del /q amd64_microsoft-windows-font-bitmap-system_31bf3856ad364e35_6.1.7600.16385_none_df4bbe8e10903104.manifest
del /q amd64_microsoft-windows-font-bitmap-terminal_31bf3856ad364e35_6.1.7600.16385_none_70644a8bdb0d9303.manifest
del /q amd64_microsoft-windows-font-bitmap-vgaoem_31bf3856ad364e35_6.1.7600.16385_none_73966d7b932081de.manifest

After all, your batch has already deleted the corresponding folder of these file. It might as well delete the manifest files.


1. Can your batch removal file be modified to delete unnecessary tasks in Task Scheduler?
2. Given any Windows hotfix, how would you decide which updated files can be safely removed?

In my opinion, I much prefer your older delx64 batch file which arranges deleted unused update file accprding to Windows Hotfixes. As such, since I am quite selective on hotfixes I want to integrate, I can easily modify the delx64 batch file according to the hotfixes I have integrated.

Now that your newer delx64 lists all deleted files collectively, I would not be able to correlate the files to their corresponding hotfixes. It is okay, dead0. I am not asking you to change your batch file according to my suggestion. To me, it is much easier to modify the older delx64 file than the newer one.

This post has been edited by alvinkhorfire: 24 September 2010 - 03:33 AM

[dead0]

alvinkhorfire, on 24 September 2010 - 03:07 AM, said:

dead0

Correct me if I am not mistaken. You can add in the following line in the winsxs section of your batch removal file:

del /q amd64_microsoft-windows-font-bitmap-courier_31bf3856ad364e35_6.1.7600.16385_none_5283fef09ca6fa1a.manifest
del /q amd64_microsoft-windows-font-bitmap-fixed_31bf3856ad364e35_6.1.7600.16385_none_db04d3f548508fd9.manifest
del /q amd64_microsoft-windows-font-bitmap-ms_serif_31bf3856ad364e35_6.1.7600.16385_none_2670fbc842c5cd2f.manifest
del /q amd64_microsoft-windows-font-bitmap-oem_31bf3856ad364e35_6.1.7600.16385_none_59590e92c817a4e0.manifest
del /q amd64_microsoft-windows-font-bitmap-small_31bf3856ad364e35_6.1.7600.16385_none_d7839341959a2de0.manifest
del /q amd64_microsoft-windows-font-bitmap-system_31bf3856ad364e35_6.1.7600.16385_none_df4bbe8e10903104.manifest
del /q amd64_microsoft-windows-font-bitmap-terminal_31bf3856ad364e35_6.1.7600.16385_none_70644a8bdb0d9303.manifest
del /q amd64_microsoft-windows-font-bitmap-vgaoem_31bf3856ad364e35_6.1.7600.16385_none_73966d7b932081de.manifest

After all, your batch has already deleted the corresponding folder of these file. It might as well delete the manifest files.


1. Can your batch removal file be modified to delete unnecessary tasks in Task Scheduler?
2. Given any Windows hotfix, how would you decide which updated files can be safely removed?

In my opinion, I much prefer your older delx64 batch file which arranges deleted unused update file accprding to Windows Hotfixes. As such, since I am quite selective on hotfixes I want to integrate, I can easily modify the delx64 batch file according to the hotfixes I have integrated.

Now that your newer delx64 lists all deleted files collectively, I would not be able to correlate the files to their corresponding hotfixes. It is okay, dead0. I am not asking you to change your batch file according to my suggestion. To me, it is much easier to modify the older delx64 file than the newer one.

i've kept those as the folders aren't deleted except for the contents. majority of the manifests are still retained just in case windowsupdates needs them.

1) not sure how to do that?
2) you can open the *.msu files with 7zip and then view the cab file within it for the update contents. i just look at the manifest file inside and compare the corresponding folder in the winsxs directory to the files in the system32 folder or wherever its installed.

the older delx64 was a bit more time consuming whereas the new one is a bit more easier and quicker to maintain. if you run a dir /b dos command of the winsxs folder when mounted, the list file will show all the updated folders at the bottom so i dont have to search through the whole winsxs to locate the updated folders. you can still use the old one or the new one but if you follow step 2 above, it gets easier to maintain with the new del64 as a baseline has already been set.

[dead0]

Therian, on 19 September 2010 - 05:13 PM, said:

Oh I see thank you. BTW I noticed a odd issue today on my 40GB test drive. The install size of windows is showing up as 11GB but that seems to big considering a full install is only a little bigger...winsxs folder is 260mb and hibernation/system restore is disabled. Installed it twice with the same results. Could perhaps something else be running that I am not thinking of? Unpacked it shows it as 3.7GB...so not sure where the space being used is.

if you only used my lastsessions and haven't edited the batch files, the unpacked size should roughly be just over 2gb?! how big is your pagefile?

[alvinkhorfire]

dead0, on 24 September 2010 - 04:40 PM, said:

i've kept those as the folders aren't deleted except for the contents. majority of the manifests are still retained just in case windowsupdates needs them.

Thanks for tips, dead0 . I was not aware of that effect of removing the manifest files. Should have left the modification of the batch to experts like you instead.

Nevertheless, thank you very much for your batch files. Previously, I had to manually delete the fonts one by one. Just imagine all the agony of getting through User Account Control and taking file ownership in deleting the fonts. Silly, wasn't it? Now, with dead0's batch files, I need not suffer such agony ever again.

This post has been edited by alvinkhorfire: 25 September 2010 - 04:25 AM

[shutfu]

dead0, on 13 September 2010 - 03:58 PM, said:

final final refresh is up! see first post with new links for the guide dated 13/09/10. the new batches should work for a clean version and with updates applied. applying updates and vlite winsxs removal is optional. if applying updates, there probably is no need to apply kb947821 (which is now upto version 7 so you will need to edit the add batch files if applying). make sure you also check the addx86/64 as some updates aren't included in the download links.

you the champ, thanks boss

[MikeRussia]

Hello all, I've got 2 Questions:
1st: What is the difference between this method and the one, using vLite only?
2nd: http://img237.images...32/97573768.png where is the tweaks.ini?

This post has been edited by MikeRussia: 27 September 2010 - 08:37 AM

[dead0]

MikeRussia, on 27 September 2010 - 08:28 AM, said:

Hello all, I've got 2 Questions:
1st: What is the difference between this method and the one, using vLite only?
2nd: http://img237.images...32/97573768.png where is the tweaks.ini?

1) this one removes a little bit more than vlite. these batch files are in addition to vlite removal as they need to work together
2) the tweaks were a vlite preset for the services. these are no longer required if you are using the latest batch files and guide in the last section of my first post.

[dead0]

alvinkhorfire, on 25 September 2010 - 04:24 AM, said:

dead0, on 24 September 2010 - 04:40 PM, said:

i've kept those as the folders aren't deleted except for the contents. majority of the manifests are still retained just in case windowsupdates needs them.

Thanks for tips, dead0 . I was not aware of that effect of removing the manifest files. Should have left the modification of the batch to experts like you instead.

Nevertheless, thank you very much for your batch files. Previously, I had to manually delete the fonts one by one. Just imagine all the agony of getting through User Account Control and taking file ownership in deleting the fonts. Silly, wasn't it? Now, with dead0's batch files, I need not suffer such agony ever again.

more stuff can be removed using vlite and by editing the batch files but finding out what each file does and/or dependencies is too time consuming.

[MikeRussia]

Quote

1) this one removes a little bit more than vlite. these batch files are in addition to vlite removal as they need to work together

How much, to be exact?

[dead0]

MikeRussia, on 27 September 2010 - 10:44 AM, said:

Quote

1) this one removes a little bit more than vlite. these batch files are in addition to vlite removal as they need to work together

How much, to be exact?

average install size for x86, under 1.5gb; x64 around 2gb
iso size x86 550mb, x64 around 950mb

This post has been edited by dead0: 27 September 2010 - 02:07 PM

[Therian]

dead0, on 24 September 2010 - 04:45 PM, said:

Therian, on 19 September 2010 - 05:13 PM, said:

Oh I see thank you. BTW I noticed a odd issue today on my 40GB test drive. The install size of windows is showing up as 11GB but that seems to big considering a full install is only a little bigger...winsxs folder is 260mb and hibernation/system restore is disabled. Installed it twice with the same results. Could perhaps something else be running that I am not thinking of? Unpacked it shows it as 3.7GB...so not sure where the space being used is.

if you only used my lastsessions and haven't edited the batch files, the unpacked size should roughly be just over 2gb?! how big is your pagefile?

Yeah followed your session to a T and unpacked with gimage its 3.7GB unpacked and my pagefile is set to 4GB by default (max ram). Total install size on my final install was 9GB so not really sure what happened to make it smaller as I didn't change anything and did a full format on the drive each time I reinstalled the OS. ISO size is 825mb.

The OS however is stable and working...just not sure where this extra space is coming from yet.


*Edit*
Also I am curious do you have a list of everything you removed on your batch files etc or perhaps you know a good source guide so I could manually track everything down so I can add/remove on the batch files based off personal preference if I wanted to add something?

This post has been edited by Therian: 27 September 2010 - 04:24 PM