[dead0]

after some thoughts, i think windows 7 professional is the way to go since we're removing most of the ultimate stuff anyway?!

theres not much difference between the two aside from bitlocker & the use of 35 different languages?

This post has been edited by dead0: 16 July 2009 - 12:40 PM

[harusp3x]

dead0, on Jul 16 2009, 01:22 PM, said:

after some thoughts, i think windows 7 professional is the way to go since we're removing most of the ultimate stuff anyway?!

theres not much difference between the two aside from bitlocker & the use of 35 different languages?

I have tried to edit and build only the Professional edition but "No images available" after the installation boots up.

[DomoPlush]

After countless attempts, I still can't get it to work. I always get this error. "Windows could not display the images available for installation."

Am I doing something wrong? Can someone post a detailed guide on what I'm supposed to do?

Thanks.

[dead0]

harusp3x, on Jul 16 2009, 02:14 PM, said:

dead0, on Jul 16 2009, 01:22 PM, said:

after some thoughts, i think windows 7 professional is the way to go since we're removing most of the ultimate stuff anyway?!

theres not much difference between the two aside from bitlocker & the use of 35 different languages?

I have tried to edit and build only the Professional edition but "No images available" after the installation boots up.

looks like the current build only contains ultimate?

[dead0]

harusp3x, on Jul 16 2009, 02:14 PM, said:

dead0, on Jul 16 2009, 01:22 PM, said:

after some thoughts, i think windows 7 professional is the way to go since we're removing most of the ultimate stuff anyway?!

theres not much difference between the two aside from bitlocker & the use of 35 different languages?

I have tried to edit and build only the Professional edition but "No images available" after the installation boots up.

i think i may have found a workaround? if you remove the other editions keeping only professional & then edit the ei.cfg file from ultimate to professional, it should install...testing now

...just finished & it installed correctly will try 2moro to see if vlite works properly on it?

This post has been edited by dead0: 16 July 2009 - 03:20 PM

[dead0]

does anyone know why bitlocker still shows up in win7 pro even though its not supposed to be there?

[liquid0624]

I still think home premium is the way to go to get the smallest install possible. Hey that's just my two cents worth. I am currently getting x86 and x64 build of 7600.16385.090713-1255. I'm going to love this build since it was compiled on my birthday he-he

This post has been edited by liquid0624: 16 July 2009 - 03:13 PM

[dead0]

liquid0624, on Jul 16 2009, 04:12 PM, said:

I still think home premium is the way to go to get the smallest install possible. Hey that's just my two cents worth. I am currently getting x86 and x64 build of 7600.16385.090713-1255. I'm going to love this build since it was compiled on my birthday he-he

i might still take the home premium route once its out!

[zakspeed]

Vlite does not work with build 7600 x64?

* sorry for my english

This post has been edited by zakspeed: 16 July 2009 - 08:18 PM

[SausageHack]

dead0, on Jul 16 2009, 03:18 PM, said:

harusp3x, on Jul 16 2009, 02:14 PM, said:

dead0, on Jul 16 2009, 01:22 PM, said:

after some thoughts, i think windows 7 professional is the way to go since we're removing most of the ultimate stuff anyway?!

theres not much difference between the two aside from bitlocker & the use of 35 different languages?

I have tried to edit and build only the Professional edition but "No images available" after the installation boots up.

i think i may have found a workaround? if you remove the other editions keeping only professional & then edit the ei.cfg file from ultimate to professional, it should install...testing now

...just finished & it installed correctly will try 2moro to see if vlite works properly on it?

I just:
A.) Mounted HOMEPREMIUM with GimageX
B.) install_wim_tweak and DISM etc etc
C.) Open up vLite, select to use HOMEPREMIUM
D.) Do like one tweak and then rebuild one (HOMEPREMIUM)
E.) Actually vLite it using a preset and apply
F.) Delete all files out of /sources EXCEPT boot.wim install.wim and setup.exe

Automatically installs Home Premium Edition! Theorhetically, this would work for Professional. Tell me if it works.

This post has been edited by SausageHack: 16 July 2009 - 07:25 PM

[liquid0624]

SausageHack, on Jul 16 2009, 09:24 PM, said:

dead0, on Jul 16 2009, 03:18 PM, said:

harusp3x, on Jul 16 2009, 02:14 PM, said:

dead0, on Jul 16 2009, 01:22 PM, said:

after some thoughts, i think windows 7 professional is the way to go since we're removing most of the ultimate stuff anyway?!

theres not much difference between the two aside from bitlocker & the use of 35 different languages?

I have tried to edit and build only the Professional edition but "No images available" after the installation boots up.

i think i may have found a workaround? if you remove the other editions keeping only professional & then edit the ei.cfg file from ultimate to professional, it should install...testing now

...just finished & it installed correctly will try 2moro to see if vlite works properly on it?

I just:
A.) Mounted HOMEPREMIUM with GimageX
B.) install_wim_tweak and DISM etc etc
C.) Open up vLite, select to use HOMEPREMIUM
D.) Do like one tweak and then rebuild one (HOMEPREMIUM)
E.) Actually vLite it using a preset and apply
F.) Delete all files out of /sources EXCEPT boot.wim install.wim and setup.exe

Automatically installs Home Premium Edition! Theorhetically, this would work for Professional. Tell me if it works.

It should work by theory but this step

F.) Delete all files out of /sources EXCEPT boot.wim install.wim and setup.exe

I can't get that one to work i always have to copy the sources original directory into the ISO i created or it gives me missing driver errors when i try to install it

[liquid0624]

Going to test this theory now preparing for first install of 16385 x64 wish me luck

[liquid0624]

SausageHack you were right All i need is INSTALL.WIM and BOOT.WIM and SETUP.EXE from sources directory for Windows 7 Clean Boot Install

[Jeronimo]

install_wim_tweak works for me again with build 7600 x64. Now trying to see if I can slim it down a bit more. Should be able to get the image below 1GB. I have removed a lot more from the image, also from winsxs-folder. just need to check remaining disabled Windows-features and files in program folder, see if I can remove those from winsxs as well. Probably somewhere during the weekend, I will post my results and files.

I will remove Windows features IE8 (IE-Troubleshooting, InternetExplorer-Optioonal), Gadgets, DVD-Maker, Windows Gadgets, XPS-service, Internet Games and those redundant language files. Then I commit the image (*). Then run vLite removal-only, check with dism what components remain. Then I put the wim-file back (the 1 I had here: *), remove the components that were remaining, see if I can still select all components in vLite, perform removal once more, cleanup/delete files from image, run vLite dummy-removal to slim down image again.

Somewhere along the way I would like to integrate my language pack, but unfortuantely, this is not available yet as far as I know.

[gendouhydeist]

@Jeronimo
any updates to your batch??? i really would like using an updated one..

[valeri]

W-7, b7100
With guard these files

windows\system32\wer.dll
windows\system32\msdrm.dll
windows\system32\browcli.dll
windows\system32\msoert2.dll
windows\system32\winipsec.dll
windows\system32\werconcpl.dll
windows\system32\Magnification.dll
windows\system32\srvcli.dll

P. S.
Not delete Japanese, otherwise Word 2003, during the complete setting, at his opening, opened time-lagged to 7 seconds

This post has been edited by valeri: 17 July 2009 - 03:46 PM

[valeri]

valeri, on Jul 17 2009, 04:44 PM, said:

W-7, b7100
With guard these files

windows\system32\wer.dll
windows\system32\msdrm.dll
windows\system32\browcli.dll
windows\system32\msoert2.dll
windows\system32\winipsec.dll
windows\system32\werconcpl.dll
windows\system32\Magnification.dll
windows\system32\srvcli.dll

P. S.
Not delete Japanese, otherwise Word 2003, during the complete setting, at his opening, opened time-lagged to 7 seconds

Attached File(s)

•  1_3W_7.jpg (95.77K)
  Number of downloads: 82

[Jeronimo]

I am nearly finished with the dism removal-part. Just need to test 1 or 2 installations (1 without IE removed and if all goes well 1 with IE removed). After that I am going to check the cleanup-part. Probably somewhere tomorrow I will know more. On a side note: still working on x64 7600.16384, but I saw 7600.16385 also is available.

This post has been edited by Jeronimo: 17 July 2009 - 03:50 PM

[Skauneboy]

Thanks for the excellent batch-file Jeronimo! So much easier for me to service my WIM-files now compared to when I did it manually. One question regarding your approach to package and component removal: I've noticed that you choose not to remove some packages with DISM which component's you check for removal in Vlite. Am I correct in assuming that this is done so that Vlite can "see" these packages and remove the files associated with them? I.E. Depending on the package it's preferable to use only DISM, only Vlite and in some cases both DISM and Vlite?

[Jeronimo]

Skauneboy, on Jul 18 2009, 12:39 AM, said:

<br>Thanks for the excellent batch-file Jeronimo! So much easier for me to service my WIM-files now compared to when I did it manually. One question regarding your approach to package and component removal: I've noticed that you choose not to remove some packages with DISM which component's you check for removal in Vlite. Am I correct in assuming that this is done so that Vlite can "see" these packages and remove the files associated with them? I.E. Depending on the package it's preferable to use only DISM, only Vlite and in some cases both DISM and Vlite?<br>

I guess something like that, trying to find a best of both worlds. It seems dism does not remove everything (winsxs) )and therefore I prefer vLite. I checked after removing all components with vLite, which packages remain present and those are the ones I try to remove with dism. Sometimes removing a package also removes a component in vLite and then I do not remove the package. I know that drivers are not fully removed with vLite, but that is why I have my own clean-up afterwards. I need to check 2 driver-packages that failed in the past, after that the dism/vlite part is done and I can move on to testing the clean-up process.