Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 

Atari800XL

Member
  • Content count

    309
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

Atari800XL last won the day on December 28 2014

Atari800XL had the most liked content!

Community Reputation

9 Neutral

About Atari800XL

Profile Information

  • OS
    none specified
  • Country
  1. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    So that's not a flat-out "no" to the idea? What did you use to download the UUPs? The tools are in constant development at the moment... Did you use a fully automatic solution, or did you start the download from a list of URL's (they sometimes time-out after a few minutes already!)
  2. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    I'm really not so sure about asking this, but I just "have to", somehow... I don't know if you've heard about the great new "UUP Dump" project by MKuba50, but it's a very nice set of php scripts that allow you to download Windows UUP files directly from the Microsoft Update servers. I know, I know, you don't want to mess with Insider Previews, but I'll try to restrict this purely to Release versions of Windows 10: Version 1703 (build 15063) is also available as a "UUP" edition. I have done some tests applying these files directly (without going through converting all ESD's to WIM, making ISO, etc.) and it seems to work just fine: (1) There are a bunch of CAB files that need to be converted to ESD (done in a few seconds, best done before hand, I guess). The bulk of the files are already in ESD format, though. (2) After that, all different SKUs are available from the set of ESD files (Pro, Edu, etc.) (3) Apply can be done by adding an extra command line option for the ESD stuff, for example: using DISM: DISM /Apply-Image /ImageFile:Cloud_en-us.esd /Index:3 /ApplyDir:Z: /SWMFile:*.esd using Wimlib-Image-X: wimlib-imagex.exe apply professional_nl-nl.esd 3 c:\ --ref=*.esd Once again: I really don't expect you to jump on this immediately, but I'm sure you understand I was thinking of WinNTSetup as well, when I was experimenting with this. The new 1709 version will probably be out this week, and I expect that the UUP files are available a week (or more) earlier than the ISO/ "normal" full ESD version.
  3. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    Yes, that's it. Best solution, case closed. Thanks again!
  4. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    Yes, I will try all of that (in time). And to perplex you even more: maybe the coolest idea would be for WinNTSetup to modify an existing "autounattend.xml" on the fly with the new name (if desired). That way there would be no misunderstanding on when to apply what. But I'm sure JFX will not bother :-) Thanks again for listening guys, just trying to learn here...
  5. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    JFX, yes, this would normally be done in unattend.xml, just wondering if I could make something to act as a sort of "override" for incidental use. Jaclaz, yes, I asked if WinNTSetup could "manage" it, but *if* that would be the case, I don't know at what particular stage that would happen, like JFX said, it would normally be done by unattend.xml, so I was just wondering if setup would execute that *earlier* or *later* in the process than changing it in the registry myself (=after apply, before first boot). But from your reactions, I can already see that this will not be the new "killer" feature for WinNTSetup 4.0! :-) (meaning: it wasn't such a great idea in the first place. I believe I first got the idea when a buddy of mine was setting up Server 2016 in a VM, which doesn't ask for a computer name, and thinking this would be nice to spare a reboot later. Something like that... This also brought up the question of why a Hyper-V generation 2 VM is so picky when it comes to bootable iso's, but that's a whole 'nother topic). Thanks for listening, anyways.
  6. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    So after WinNTSetup is done with the apply fase (just prior to first reboot), would that be the appropriate time to do the settings for a name change, or is that "too soon"? (ie. is the random name fase still to come, so changing the name this early would have no effect?). Just wondering (before having done any testing yet).
  7. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    Thank you! I will start experimenting...
  8. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    JFX, with all the nice new releases lately, I wonder if I can ask you something: - What would be the best way to name/ rename the computer after apply/ before reset? I know it can be done with autounattend.xml, but it would be great if WinNTSetup could name the PC on its own. At this moment, I'm using this in "PostInstall" to rename the PC, but doing it in WinNTSetup would shave off one reset in some cases. WMIC ComputerSystem where Name="currentname" call Rename Name=newname WMIC isn't normally available in PE, is it? Do you know of any other way to do it in PE (maybe using WinNTSetup -runafter, or maybe a new option?) Thanks for any info...
  9. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    Very interesting... Thanks again for testing. Hope we can find out why your first attempt didn't work (JFX?) At least your test confirms it can work in WinNTSetup, so I can still suggest this solution to others (forced w10 driver updates are a big problem for some, specially on older hardware).
  10. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    Thanks for taking the time to test. (Just put the reg file in a folder and point the "tweaks" button at it). I'm very interested in your results...
  11. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    OK, sorry for giving wrong information. On a test laptop, this does seem to prevent a Synaptic driver from getting updated (and borked), but maybe there are other settings that I forgot to mention. Maybe JFX can help out here... (Maybe it also helps that I use this setting from the earliest stage of setup? Nah, that can't be it).
  12. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    I have been using this, it seems to work for preventing driver updates (added to the WinNTSetup tweaks section): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching] "SearchOrderConfig"=dword:00000000
  13. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    Guimenez, there are other sites that explain how to do that, but even then: I would not advise to make updated iso/wim/esd files anymore. Here are my reasons: (1) For windows 10, there are only 3 updates you need, wether you install from an "old" or a "new/ updated" iso. You only need the latest Cumulative Update, one other update, and maybe Flash update. In the old days, an "old" source file would need more updates than a newer source, but with Cumulative updates, that's a thing of the past. (2) Better wait for next week anyway: There will be a new "Windows 10 1607.1" esd directly from microsoft. So that's version 1607 (july 2016), "with update".
  14. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    belivakov: Thanks for the tip, but I already know how to convert esd to wim or iso. I even know how to "capture" these esd files (using Fiddler etc) and the new UUP files (and convert *them* to single wim or to iso). I just wanted to ask if JFX was playing around with these new UUP files, but I already got a clear answer: He is not :-) On the other hand: Microsoft doesn't even have everything setup correctly with regards to UUP, because even though they were planning some kind of "delta" upgrade system, the last three previews have been "full" downloads, which means all the files were there, so there's no download size/ speed advantage yet. Finally: WinNTSetup is great for testing these previews, as long as you at least have a single ESD file: WinNTSetup can apply straight from esd, but converting to wim might be a bit better, because it allows servicing (changing/ adding/ removing) and setup is a bit quicker that way.
  15. WinNTSetup v3.8.7.4 / 3.8.8 BETA1

    No problem dude...
×