-
Posts
1,403 -
Joined
-
Last visited
-
Days Won
64
Content Type
Profiles
Forums
Events
Everything posted by bphlpt
-
So, you've tried using Win Toolkit + RT7Lite, and now you're using Win Toolkit + WinReducer + VLite? Admittedly Win Toolkit does not do as well as some other tools in slimming Windows 7, but slimming is not it's major purpose or focus, and the need for slimming is not as necessary with the current speed and size of today's CPU, memory, disks and SSDs. I also agree with the suggestion of minimizing the use of multiple tools, as Thiersee stated. I hope that Win Toolkit will continue to evolve so that it could be the one tool that anyone would ever need or want, but it's not there yet. If you're dead set on slimming Windows 7, instead of RT7Lite, Win Reducer or vLite, you might want to look at a more modern tool such as NTLite, either with or without Win Toolkit. Cheers and Regards
-
RT7Lite - This program might not have installed correctly
bphlpt replied to mmigasmike's topic in Microsoft Windows 7
I don't think you'll find many folks here that can help you that still use RT7Lite. it hasn't been updated in many, many years. It's main feature, of being able to slim Win7, hasn't been as necessary anymore either, due to the current sizes of disks and the speed of today's CPU and memory. It's annoying I know for Win7 and later OS to be as bloated as they are, but they're usually "good enough". But if you want to slim Win7 and later, you might check out a more current tool such as NTLite. It works on Win7 and later, can slim as good or better than NT7Lite, can work on live and offline OS, etc, etc. Cheers and Regards -
That's not a bad idea, but the rates that Lego is proposing are already very low, so I don't think the period idea is necessary in this case. I currently gladly pay for a text editor app - Edit Pad Pro - that has what I think is a reasonable payment policy: Free trial and a free version Pro version for $ with extra capabilities "Minor" updates - ver 7.0 -> 7.x are free Major updates - ver 7.x -> 8.x - are half price for prior subscribers Past history of this app, ( I think I have owned this app for 8 or 9 years ), shows that major upgrades only happen every 3 or 4 years. So that's yet another possible modification to your payment idea. Cheers and Regards
-
HOW to USE WimSplitter...?.. please is Important..!
bphlpt replied to latino's topic in WinToolkit Bugs
I'm not sure, but it might make a difference as to which OS and architecture you are trying to build, whether or not you are trying to use UEFI, whether you need to split the WIM because you are also trying to add a lot of addons, and other factors. You'll have to wait until someone who knows more than I to respond, but in the meantime, the more info you can provide might help clarify the situation. Cheers and Regards -
Welcome to WinCert! Cheers and Regards
-
Hopefully, abbodi1406 will respond and confirm whether I interpreted his instructions correctly. Cheers and Regards
-
So, to use a modified version of Thiersee's example above, for an x86 AIO install source the steps would be: 1) In the normal AIO choose the lowest version 8, ie STARTER) and delete ALL other (HomeBasic, HomePremium, Professional, Ultimate) 2) Integrate all updates you need 3) When finished close WTK, go into the folder where your .WIM is located 4) Run the following code: imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomeBasicimagex /commit /append c:\mount HomeBasicimagex /unmount c:\mountimagex /flags "HomeBasic" /info install.wim 2 "HomeBasic" "HomeBasic"imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomePremiumimagex /commit /append c:\mount HomePremiumimagex /unmount c:\mountimagex /flags "HomePremium" /info install.wim 3 "HomePremium" "HomePremium"imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:Professionalimagex /commit /append c:\mount Professionalimagex /unmount c:\mountimagex /flags "Professional" /info install.wim 4 "Professional" "Professional"imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:Ultimateimagex /commit /append c:\mount Ultimateimagex /unmount c:\mountimagex /flags "Ultimate" /info install.wim 5 "Ultimate" "Ultimate"9) Rebuild the install.wim 11) Done! Correct? Do you need to mount, unmount, mount, etc, or can you only mount and unmount once like this?: [s]imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomeBasicimagex /commit /append c:\mount HomeBasicDISM /Image:c:\mount /Set-Edition:HomePremiumimagex /commit /append c:\mount HomePremiumDISM /Image:c:\mount /Set-Edition:Professionalimagex /commit /append c:\mount ProfessionalDISM /Image:c:\mount /Set-Edition:Ultimateimagex /commit /append c:\mount Ultimateimagex /unmount c:\mountimagex /flags "HomeBasic" /info install.wim 2 "HomeBasic" "HomeBasic"imagex /flags "HomePremium" /info install.wim 3 "HomePremium" "HomePremium"imagex /flags "Professional" /info install.wim 4 "Professional" "Professional"imagex /flags "Ultimate" /info install.wim 5 "Ultimate" "Ultimate"[/s]Cheers and Regards
-
Do I really have to integrate updates to all images? (Win Toolkit + Win 7)
bphlpt replied to Psy-Virus's topic in Win Toolkit
Yep, he did! See here - http://www.wincert.net/forum/topic/13036-making-an-aio-and-integrating-all-updates-possible/?p=114840 Cheers and Regards- 11 replies
-
- all images
- integrate
- (and 8 more)
-
Thanks, Thiersee! Cheers and Regards
-
Well, there is a way to integrate them once for each architecture of each platform and then promote each image to all the editions you need, and then merge all the install.wim files. I'm afraid I can't describe it better than that since I haven't actually done it yet myself, but see here for a very brief explanation. It is supposed to be a coming feature in Win Toolkit v2. In the meantime, if you are able to work out the manual process successfully, then give back to the community by sharing the details of the process so others can do it too. Good luck! Cheers and Regards
-
One way would be to use a tool such as WPI to do the app installations. The mechanism to call WPI could be added to each image, but then there would only be one set of apps, which would be located outside the install.wim, and AFAIK WPI could be set to install the x86 and x64 versions as appropriate. I think that the apps could then either be included on the AIO disk or on a separate medium, which might be more convenient to maintain. Just a thought. Cheers and Regards
-
Since this issue has been reported by many people, both here and on other sites, I would assume that this is not anything that anyone is doing wrong, except MS. So I'd suggest only doing a deep clean before adding these troublesome updates, and not afterwards, at least this month. Hopefully, MS will straighten this mess out by next patch Tuesday, if not before. It seems that either the updates, and/or the deep cleaner app, needs an update. Just my opinion. Cheers and Regards
-
μTorrent v3.4.3.40097 [RePacked by Ruben Alamina]
bphlpt replied to niTe_RiDeR_Pr0's topic in Installer Repacks
I also have heard that uTorrent has made many of their loyal users abandon uTorrent because of their recent practices - https://forum.utorrent.com/topic/95041-warning-epicscale-riskware-installed-with-latest-utorrent/. It seems that qBittorent has become the alternative torrent client of choice. Cheers and Regards -
You might want to check this out - atmzzrSystemCheck v2.6 [Check installed runtimes versions] - I don't think it's currently compatible with Win10, but you might could work with automizzer to make the two apps be in sync. As an off-the-wall thought, you might also think about making a companion "Runtime Removal" app, as a way to help clean up problem installations before running your installation app. Just an idea. I would also urge you to work with the other app makers here to help you make your AIO app smaller. I was surprised to see it is as large as it currently is. For those wanting/needing a smaller solution, they are able to put one together themselves using existing repacks available elsewhere here on the board. There are conveniences to having an AIO, but many would rather have a smaller solution. As a final observation, with the combination of runtimes in this app, and since each of them are updated frequently on a non-coordinated schedule, you are most likely going to be pestered constantly to keep this AIO up to date. Cheers and Regards
-
Well, I know there are users who only add the minimal versions of .NET that they absolutely have to have - none if they can get away with it. But for users that are likely to use an AIO pack like this one, I would think that they are more likely to install all runtimes they can find so they will be ready for any app or file they run across. So yes I think it's probably appropriate to include all the versions of .NET that are appropriate for the OS involved. At least that's my opinion. I hope others will post if they feel differently. If so, then you might consider either multiple versions, or making it an option. Cheers and Regards
-
AFAIK, 4.5 does not work on XP either. I think that 4.0 is the last one that works in XP [ OT ] Please do not bold everything you post. It's impolite board posting. [ /OT ] Cheers and Regards
-
AFAIK, this should be: - Microsoft DirectX End-User Runtimes (June 2010) including DirectX for Managed Code Support For Windows Xp & above This is inside the "What is included spoiler". Cheers and Regards
-
AFAIK, this should be: - Microsoft DirectX End-User Runtimes (June 2010) including DirectX for Managed Code Support For Windows Xp & above Cheers and Regards
-
No problem. I've never tried Windows 8.x+, and have never known anyone who has run DXCB on Windows 8.x+, so I'm glad you were able to get it to work for you. Cheers and Regards
-
I have seen a very few situations where either permissions or certain anti-virus or firewalls or sand-box apps have caused issues with DXCB. but I have not found a consistent solution. But then I haven't done much work with this in quite awhile. Fortunately, there haven't been any changes to the older DirectX code in almost 5 years, and once you are able to make a successful addon or installer they seem to work on all appropriate systems. In other words, the occasional issues I have heard of only effect running DXCB itself. I have never gotten any report of any failure or problem of any kind with the addons or switchless installers that DXCB produces. Cheers and Regards
-
Glad to help. You are welcome to use this in your pack however you like. Cheers and Regards
-
It seems MS has changed the structure of the download page, so neither of the included downloaders currently work. But, no problem. Go here - http://go.microsoft.com/fwlink/?LinkID=56511&clcid=0x409 - and manually download the latest DirectX End-User Runtimes (June 2010). The file should be "directx_Jun2010_redist.exe". Place the file in the same folder where "DXCB.cmd" is located. I just ran it that way myself, so it should work for you, too. If you don't enter any options, when you then run "DXCB.cmd" it should produce these files as output, which will include DirectX for managed code, and should be located in the same folder as "DXCB.cmd": ---------------------------------- DirectXRuntimes-201006-AddOn-32.7z -- (13,676,451 bytes) -- 32-bit addon DirectXRuntimes-201006-AddOn-64.7z -- (29,363,280 bytes) -- 64-bit addon which includes the 32-bit addon as well DirectXRuntimes-201006-Switchless-32.exe -- (13,676,076 bytes) -- 32-bit switchless installer -\ DirectXRuntimes-201006-Switchless-64.exe -- (15,686,796 bytes) -- 64-bit switchless installer --\ for 64-bit use you need to use both 32-bit and 64-bit DXUnInst.cmd -- (15,803 bytes) -- Uninstaller which should uninstall DirectX completely from any Windows OS no matter how it was installed ---------------------------------- So since directx_Jun2010_redist.exe is (100,271,992 bytes), you can see how much smaller any of these options are, and yet they will install the same files as the original redist. Cheers and Regards
-
Works now. Cheers and Regards
- 17 replies
-
- 2.0.5641.41562
- 2.0.5642.1187
-
(and 79 more)
Tagged with:
- 2.0.5641.41562
- 2.0.5642.1187
- Request
- K-Lite
- Codec
- silent install
- Repak
- Windows 7
- image burner
- cd
- integrate
- updates
- Windows 7 KB3021952
- introduction
- Windows 8.1
- Windows 7
- Batch
- CMD
- Administrador
- Win Toolkit
- minitool
- power data recovery
- 1.5.3.9
- silent install switches
- wintoolkit
- request
- repack list
- full list
- index
- Integrator
- monting
- WIM Manager
- updates
- update downloader
- [solved]
- Crash Stop Error
- Legolash2o
- magiciso
- maker
- magiciso maker
- 5.5
- 2.7
- repack
- .net
- framework
- slim
- madbarz
- invite
- code
- Investigation
- automatic
- driver
- install
- xp
- v1.5.x
- OSCDIMG
- v2.0.0.22
- Fixed in v2.0.0.23
- Mutilple os in a wim updates
- v2.0.0.19
- v2.0.0.19
- Fixed in v2.0.0.21
- universal
- chipset
- driver
- pack
- download
- windows
- 8.1
- xp
- usb
- v2.0.0.12
- Fixed in v2.0.0.14
- Registry file right click
- help
- KB2919355
- win 8.1 x64 help integration
- windows 8 themes
- themes
- xp themes
- themes for windows 7
-
Sorry but it's still messed up. Total size only 6KB. Seems to only be "en-us.xaml". Cheers and Regards
- 17 replies
-
- 2.0.5641.41562
- 2.0.5642.1187
-
(and 79 more)
Tagged with:
- 2.0.5641.41562
- 2.0.5642.1187
- Request
- K-Lite
- Codec
- silent install
- Repak
- Windows 7
- image burner
- cd
- integrate
- updates
- Windows 7 KB3021952
- introduction
- Windows 8.1
- Windows 7
- Batch
- CMD
- Administrador
- Win Toolkit
- minitool
- power data recovery
- 1.5.3.9
- silent install switches
- wintoolkit
- request
- repack list
- full list
- index
- Integrator
- monting
- WIM Manager
- updates
- update downloader
- [solved]
- Crash Stop Error
- Legolash2o
- magiciso
- maker
- magiciso maker
- 5.5
- 2.7
- repack
- .net
- framework
- slim
- madbarz
- invite
- code
- Investigation
- automatic
- driver
- install
- xp
- v1.5.x
- OSCDIMG
- v2.0.0.22
- Fixed in v2.0.0.23
- Mutilple os in a wim updates
- v2.0.0.19
- v2.0.0.19
- Fixed in v2.0.0.21
- universal
- chipset
- driver
- pack
- download
- windows
- 8.1
- xp
- usb
- v2.0.0.12
- Fixed in v2.0.0.14
- Registry file right click
- help
- KB2919355
- win 8.1 x64 help integration
- windows 8 themes
- themes
- xp themes
- themes for windows 7
-
And without any spaces in the path name. Cheers and Regards
- 5 replies
-
- 2.0.5641.41562
- 2.0.5642.1187
-
(and 79 more)
Tagged with:
- 2.0.5641.41562
- 2.0.5642.1187
- Request
- K-Lite
- Codec
- silent install
- Repak
- Windows 7
- image burner
- cd
- integrate
- updates
- Windows 7 KB3021952
- introduction
- Windows 8.1
- Windows 7
- Batch
- CMD
- Administrador
- Win Toolkit
- minitool
- power data recovery
- 1.5.3.9
- silent install switches
- wintoolkit
- request
- repack list
- full list
- index
- Integrator
- monting
- WIM Manager
- updates
- update downloader
- [solved]
- Crash Stop Error
- Legolash2o
- magiciso
- maker
- magiciso maker
- 5.5
- 2.7
- repack
- .net
- framework
- slim
- madbarz
- invite
- code
- Investigation
- automatic
- driver
- install
- xp
- v1.5.x
- OSCDIMG
- v2.0.0.22
- Fixed in v2.0.0.23
- Mutilple os in a wim updates
- v2.0.0.19
- v2.0.0.19
- Fixed in v2.0.0.21
- universal
- chipset
- driver
- pack
- download
- windows
- 8.1
- xp
- usb
- v2.0.0.12
- Fixed in v2.0.0.14
- Registry file right click
- help
- KB2919355
- win 8.1 x64 help integration
- windows 8 themes
- themes
- xp themes
- themes for windows 7