Is it crazy to re-integrate the same image file over and over?

G

garlin

Moderator
Staff member
Messages
8,251
Reaction score
4,006
If someone is really careful, is there a practical limit to mounting one image, applying changes to it, reloading the results and repeating this step over and over?

When building my Win7 image, I'm required to pre-integrate 3 RDP patches to get around annoying manifest issues. This works out well. Second pass is where I apply the normal updates, drivers, and post-setup commands. Third pass is because currently you cannot block the EOS notification component from integration, only remove it afterwards.

Tell me if this a safe strategy. Obviously you shouldn't keep patching a patched image endlessly, but in this case it should be OK?
 
It depends on whether the changes you made in a previous iteration can affect the changes that you're making in the current. But it's not inherently crazy.

For example, I start by taking an untouched iso and slipstreaming updates into it.

Then I save it and make a copy of it.

Then I work on the copy to remove Fonts, Language & Keyboard. I might add drivers for RAID (which, in my case, requires that I remove all other hd drivers).

I save that and make a copy.

Then I load the copy and start component removals.

If I take too much out, I can make a new copy of the previous wim with the F,L,K removed and do removals again, without having to start from the beginning.

I usually stop there and install the wim.

But of course, once you have installed a wim that has removals, you might be able to remove more items from using a Live NTLite.

So again, your work flow is not inherently wrong.
 
After making over 20 different test runs, I'm comfortable with it.

I like saving preset files from each iteration, to keep my changes consistent when reworking a build. Whenever you tweak an earlier step, check the later presets to clear out any "junk" that doesn't belong downstream. I've had to catch myself a few times :confused:.
 
It gets more interesting when you try to use a working preset in a newer version of NTLite.

Sometimes nuhi's Engine changes and the Presets don't import the same. (Which perhaps could be a Feature Request: A way to alert users when an item in the preset.xml is not longer 100% compatible with a newer version of NTLite? Like, when a removal changed to a finer graduation (with perhaps two removals now), etc.)
 
Somewhere in our discussions, you suggested that I try Win8.1 on my new (used) Dell i3-8100. I was noodling around in the BIOS today as I installed my new M.2 drive. The BIOS says that this Dell will NOT boot Win7 or 8.1.
 
I swear it wasn't me!! The only time I touched Win8 was on the Surface tablet (ARM) they gave us for personal use.
lol
 
pmikep oems locking a system down to 10 is well known, i dont know if there is a work around for it or not. you can install 7 on retail boards, it is officially supported on H310C(r2.0) boards, can be installed on B360 and other 8/9 gen boards because someone has kludged the drivers for it and biostar supports 7 on some B365 boards and has a tool for that. 8.1 installs on 8/9th gen because the usb3 drivers are now native ms and already inside iso's :) M2 drive, WD?
 
Oops. My message above was meant to be a PM to Clanger. (It was 2 in the morning and I had been wrestling with Win10 (and Intel) to recognize my 1 TB HD in SATA slot 0 after installing the M.2.)
 
hahaha :p Leave it here, info for others in that installing 7 or 8.1 instead isnt always an option, its w10 or linux only.
 
You must log in or register to reply here.
Back
Top