Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

nuhi

Developer
  • Content Count

    4,453
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

10 Good

1 Follower

About nuhi

  • Rank
    nLite & NTLite human.dll

Contact Methods

  • Website URL
    http://www.ntlite.com

Profile Information

  • OS
    none specified

Recent Profile Visitors

7,463 profile views
  1. Your choice if you want to update boot.wim environment. It's being used only during Windows install, first portion when booting. If using at home, I don't think there can be any tricky situation. If capturing WIM images from that boot, then at least update servicing stack (since 2009 latest ones it means cumulative update as well). Driver integration is another story, make sure to add them to boot as well, if Storage or USB drivers. Rufus and Win7 boot requirements belong on Rufus forum - but first make sure the correct drivers are integrated, that link you provided has plenty
  2. Hi Wolfe, thanks for the feedback. It is true that Win7 as a host does not allow HyperV feature configuration, it requires a missing API from it. Containers uses HyperV so thus the error. Will also lock that, only locked HyperV in the UI when Win7+Win10 is detected. Let me know if I missed anything, it should work with the HyperV (and thus dependent Containers) feature state intact.
  3. OK, but I'm a bit confused, do you have any issues with this tool? All I read is that you saw a few people reporting other problems with their scripts so you didn't even try yours. Or if you did try, then please let me know how to confirm if that script worked or not. In my reply above is how to integrate it. Thanks.
  4. Hi, the link is incorrect (seems to have been pasted as the short version). Either way for scripts, they go to the Post-setup page. On the Support page you can see two links for that topic.
  5. Hi, when it comes to virtual machines, they usually randomize the network adapter MAC address, so make sure to set that at static. Best is to reuse the same VM, just reformat it when needed. Let me know if you have any issues, best is to contact me over the email about this topic. Thanks.
  6. nuhi

    edit

    jaclaz, the point was that open-sourceness allows for outside contributions and thus fragmenting the vision, pulling to the side if you get a nice contribution of code that works. Even if that hypothetical dream team's branch of code ignores all else and continues working on its own; still, to the public, there would be fragmentation. For example what influenced me was the Media Player Classic HC and BE editions. Always used HC, then after it began branching BE, I liked some added features in it, but HC was more stable at the timespan I tried both so I was forced to wish for BE and continu
  7. nuhi

    edit

    muck, I do appreciate the feedback, but I don't see the solution for that amount of paranoia and idealism, it's simply not practical. Since I have extra energy and this topic is interesting, let me dig myself in a hole (from your perspective) some more So as far as I have gathered, correct me if I'm wrong: you use only open source software that you review (or wait enough time for others to review) and compile yourself on each update? And we concluded that even open source is not safe. Not to mention that majority of Windows users will use pre-compiled binaries, even there anything c
  8. nuhi

    edit

    muck, that argument, as flawed as it is, can be said for the majority of commercial software available. You can always compare what this tool does to the system by looking at the image files and registry before and after the modifications. There are tools for that. Also there is sfc /scannow to confirm that kept files are in their original form. Let's compare it to some popular closed-source commercial application, let's say an antivirus which constantly scans all you do, how is that so trusted by millions of people every day? And regarding opensource having any guarantee, do you rem
  9. Please next time try 1.2 final next week and let me know how it goes, I didn't experience such issues. Thanks.
  10. Cloves, ok, let me know if such confusion happens again, to find out why. Can't wait to add ISO reading support so users don't have to copy the content manually.
  11. Simply loading does not change it. You can also unload it and don't tick save changes, nothing will be done to the image. I mentioned unloading because when the image is loaded it is also mounted, that is just an NTFS virtual representation of the image content inside a mount directory. To release the hold on the loaded image you need to unload it fully, not just close the tool. When you normally apply some action and keep ticked save changes in the toolbar, the unloading with unmounting + saving changes is done automatically. Some fun fact: You can load the image, integrate drive
  12. Hi Cloves, here is well explained driver integration, main key is to integrate USB3 drivers to the boot.wim (2nd image, with the "setup" in the title) itself, not just install.wim. Both is necessary, install.wim is in effect after setup. You can check if the driver is there in Components - search box in the toolbar. Original ISO, as it the one that you loaded and integrated driver into? There is no read-only, copy to temporary dir and edit option, it actually edits what you load on the Source page. Let me know if you need more info or I misunderstood you, thanks.
  13. Hi Tseng, ok, will look, but to reduce guessing I have a few short questions: - which Windows version? - in case it was Win10, did you remove just Firewall or including its service as well? - online (C:\Windows) or offline (from image) removal? - Preset attached or sent on email would be best Thanks.
  14. Oh, thank you, appreciated.
  15. Hi Tseng, as it was always stated on the Shop page (below the list), and discussed on this forum when the tool was being launched, the license has in it a year of new features since the first activation. The point was to allow premium fixes and upgrades to continue, not doing the subscription-only updates. The difference in this model is that you can keep on using the latest versions always. The renewal price is 50% of the license price for another year. I did extend that initial year somewhat, mainly due to the fact it was just a beta for some time, so that initial users are rewarde
×
×
  • Create New...