Jump to content

crashfly

Members
  • Content Count

    405
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by crashfly

  1. It was last week when I posted this. This is just a reminder (or bump if you prefer) for Legolash2o.
  2. I do like the idea of updating DISM to the Windows 8 version. Even without the "extra" features inherent to Windows 8, it would be a speed improvement if the newer DISM works as fast as Legolash2o says it does.
  3. I agree with bphlpt. The decision should be with what Legolash2o wants. He is the programmer. He has the singular choice of deciding what to work on or add to WinToolKit. Keep up the great work Legolash2o.
  4. How about a "Seagate Barracuda ST31000524AS 1TB 7200 RPM SATA 6.0Gb/s 3.5" Internal Hard Drive -Bare Drive" from newegg.com (here: http://www.newegg.com/Product/Product.aspx?Item=N82E16822148697) for only $79. A terabyte for cheaper. I would go for more space. One "always" needs more space. Seriously though, looking at your selections, I would also agree that option #3 would be very benefital compared to the others. SATA3 and the cache size are definitely "forward" looking.
  5. I think the last part is what is being considered. Many of us have a SSD. Some of us have a large amount of RAM > 12GB. We are just discussing the balance between how much of a RAM drive is necessary over traditional HDD/SSD space. Note that balance is the key word here.
  6. As Legolash2o mentioned, hell yes. For more direct comparisons, I found a performance test someone did compariing SSD and HDD. I do realize that the hardware they are using are macs, but the same performance increase should hold over on windows hardware. link: http://www.tomshardware.com/reviews/ssd-notebook-portable,1913-5.html
  7. This should be a "relatively" simple request. When downloading updates from the "Update Catalog", would it be possible to sort by the column titles? At a minimum, the name (possibly the KB number even), and the date. If using the date, it would be easier to determine what has been updated most recently, and therefore not have to download the whole update list again. Thank you for this consideration.
  8. I am of the mind of "why re-invent the wheel?" While "doing it" yourself could give speed benefits, I think it would take away from the work on your program done so far. But hey, you *are* the developer.
  9. And that might be an issue if one uses the RAM disk as the temp directory for windows (and it is too small). Since the bulk of DISM space usage will be on the mount point (until changes are written back to the WIM file on unmount), it would seem to be a good suggestion to leave the mount point on the fastest drive (preferrably an SSD with enough space). As previously pointed out, using 16gb of ram for a RAM disk is not possible for the majority of people. So at least the scratch directory to a RAM disk would work with a minimal size of 4gb. (Luckily, I am already there are that one.)
  10. So to get the latest "bug fixes", I need to go back to the latest "non-beta"?
  11. That would be good at least until he does implment the actual file removal of those items.
  12. Ok, so your "resulting" OS is "heavier" than the first? So those pictures are showing what your drive looks like 'after' install? If that is the case, it could be any number of things including updates and what got installed differently. If you are referring to the ISO "image", see bphlpt's post above.
  13. Now see here, I have issues with this forum having issues! (just kidding) Everything seems responsive enough, so great work once again. :prop:
  14. Maybe this needs a 'non-hardcoded' solution? Would it be possible to have a "default" set of prerequisites and supersedes, and a way to change them (maybe saved in a text file or something)? This would help resolve the problem of (if) WinToolKit (ever) stopped being maintained and it would still allow for updates to be properly prepared.
  15. I like the idea of using a RAM disk (just started using one due to the discussion about it), however I think we need to figure out a "baseline" for what the bare minimum needed for integrating. Some have pointed out that one needs a substantial drive to make all of the changes. Likely we also need to have minimum RAM amount specs to even be able to work with a large enough RAM disk.
  16. Is v1.5.0.1 considered beta? If it is, then I would also assume that the "Check for Updates" button is currently wrong saying that I am using the latest version?
  17. Does the file already have "all resolutions"? If not, then the likely answer would be yes. If the file is appropriate for "all resolutions", then I have no idea.
  18. Where has your source file come from? Have you copied this file to a hdd? Do you have antivirus running that might cause WinToolKit to shut down prematurely?
  19. While I might agree with that sentiment, I would rather have the image prepared right the *first* time so that I do not have to go back just to prepare it again. It would save more time in the back end on testing than to just get half way through an install and realize that it will not work period.
  20. You are comparing "apples" to "oranges" there. The one with 45 minutes of waiting has more robust code and actually checks for errors/problems. The one with 15 minutes has few if any checking and therefore could become a problem later.
  21. The best way to "free" up 5gb safely is to get a bigger hdd. While WinSXS can probably be removed (never tried it), the reason for its functionality is OS stability. Secondly, despite what you think, your WinSXS is really not quite that big. What appears to be files in each of the directories are filesystem links back to single files. Because of the way filesystem links work, you only think it is 5gb because each file (even those linking back to a single file) are counted as taking up space. You might research more on why WinSYS is there, instead of just trying to break OS stability first.
  22. While you might understand what you were meaning, the rest of us have very little to go on with your above post. Please include more information as to what you did, what you were installing, *when* it was installing, and other such information that we might be able to help deduce your problem. At this point, I cannot conclude anything from your post and can only suggest that you did something wrong.
  23. And just what is the "latest" version you are trying to run? When you start WinToolKit, the version should be in the main title bar.
  24. crashfly

    Win7 - 4.7GB

    I considered the "Dell OEM" dvd issue. I guess it would depend on if the OEM dvd had more stuff put on it than just the OS. If the "extra" packages are added through DISM, it should be nearly as easy to remove with DISM. However, it Kel is right and it would be likely easier to just use a plain jane Win7 SP1 dvd and then add/inject from there. If I remember correctly, the bios should already have part of the certificate, and he would just need to add the correct key/certificate to the OS.
  25. crashfly

    Win7 - 4.7GB

    There should be an option in WinToolKit that will make sure everything is as small as possible on your wim image. That should help to "reduce" space when removing the 'other' editions. If the above does not help, your only other option is to reduce what is integrated into your image or possibly even removing some components from your image. (That or get a dual layer DVD and/or use a USB stick to install from.)
×
×
  • Create New...