Jump to content

Legolash2o

Contributors
  • Joined

  • Last visited

Everything posted by Legolash2o

  1. 1. Integrate the 3 msu files. 2. Nope, it's not safe. However the WinSXS\\Backup is safe to delete though.
  2. System32 folder if I remember correctly.
  3. Not sure, never experienced that issue. Probably for backup reasons :/
  4. DISM probably had a whole team of people to create it, i suppose I could monitor an integration and see how it works fully.
  5. There's probably lots of junk in the WinSXS folder. For example, you could remove the some update files but you wont be able uninstall old updates.
  6. 1. Sort of, it does replace files but Windows does keep the old files in case you want to uninstall it. 2. They shouldn't be installed after Windows installation, for me they are completely removed. I think Windows 8 DISM does have a feature to actually remove old/superseded files. 3. I'm planning on adding more to the 'vLite' list which actually removes the files.
  7. I manage to use 6GB RAM Drive ok, but for some reason it won't create a RAM Drive in Windows 8 x64 SSD would be a great upgrade for a PC, it's like having a new computer. I could add an option for the user to be able to select: Win Toolkit Temp Mount Temp ScratchDir Temp People also forget their anti-virus will slow down the update process a lot. The best and only way to make it way faster is if I removed DISM and made Win Toolkit handle everything manually.
  8. If you don't provide a scratchdir command it uses windows default temp directory. Apparently you can use also the scratchdir switch when mounting too. I wonder if that is also moved to RAMDrive speed will be increased?
  9. The C:\WinToolkit_Temp will most likely just be for the mounting.
  10. I think I may have sorted it EDIT: Fixed in v1.4.1.10
  11. I will have a look at it now
  12. I haven't really done any experimenting with component removal on Windows 8 yet.
  13. v1.5.0.1 is beta.
  14. Nah, DISM will detect it's already there and skip it.
  15. Yep 1.4.1.9, please test
  16. I think i may have fixed this
  17. The apps folder needed to location on the root of the drive. i.e. D:\Apps\.
  18. Win Toolkit doesn't have a database, it's hardcoded Prerequisite's need to be intalled before certain other updates for example Internet Explorer 10 before an update for Internet Explorer 10.
  19. Ignore anything about a beta, the current 1.4.1.x release is newer.
  20. Some user has already reported the reg file issue. I'm just waiting for a response.
  21. Legolash2o posted a post in a topic in Win Toolkit
    Many users are starting to use RAMDrive's, we need to get together and brain storm for ideas of how integration can be faster or any ideas relating to speed. At the moment i'm added the '/ScratchDir' switch to DISM so that in the next release it will use your RAMDrive, if WinToolkit is told to used that anyway.
  22. I have noticed that even when you set the temp folder to a RAM drive, DISM will still use the main C:\ partition which sucks. I will be adding code which adds the /scratchdir syntax for dism so it will use the same temp as Win Toolkit i.e. your RAM drive.
  23. I never do those updates. But there's no harm in integrating into both images.
  24. Legolash2o replied to ccl0's post in a topic in Win Toolkit
    It will keep compressing the image until it is under 250kb so it shouldn't try and compress it. If it does, then it won't do any harm
  25. Legolash2o replied to Falo's post in a topic in Win Toolkit
    The 'Old' folder can be deleted. If an update is removed the from the server, it will get moved to the old folder.