New rip WITHOUT NTLite detecting OS drivers?

Saaglem

Active Member
Nuhi. How are you mate? Tell me, please! How do you rip a clean OS without NTLite detecting the drivers on the host machine you are ripping from? I want to rip a Windows 8.1 for my Lenovo but NTLite keeps on telling the architecture version is wrong and then it doesn't import all the drivers I want to import to the image I want to create. Yes the settings for host is not marked. This is the reason I never want to import the drivers and the reason I posted last week why the chipset drivers keeps on getting imported without the request to do so. I tells me that the OS that is been created is not updated drivers free and this create a problem if the driver set is "TOO NEW" on the machine that is been installed on because then you cannot remove it or update them on the other machine! The NTLite version I us is an older version of NTLite, I know but the old one works great for me. I tried the newest one and I need to do everything over, that I did, but my OS's kept on failing so I've loaded the older one and now everything works fine. Maybe in the newer version this driver thingy is fixed?!

PS: I came right with the SATA preinstall drivers, but not from that site because it was confusing, it kept on removing the Windows PE set and not all the page is included in the explanation. I used another, https://www.rickygao.com.au/blog/use-ntlite-to-add-oem-drivers-into-windows-installation-usb-disk.

Thanx.

Cheers.
 
Last edited:
Hi Saaglem,

In your screenshot I don't see host import, I see preset load.
Do you know that the tool auto-loads last session by default on load? You can disable that in File - Settings before loading.

Also in any case if those wrong architecture messages are incorrect, please send me the link to that driver that was used and name the exact 2-3 INF files that you think of which architecture was wrongly detected.

Thanks.
 
Wrong architecture message is shown when x86 drivers are loaded for x64 or vice versa.

Are you running an architecture and want to integrate its drivers into an image with another architecture or just added a folder drivers with both architectures?
 
Ok. I normally only use 64bit drivers. Yet it still import the 32bit along with 64bit, it actually added win xp drivers along with them. But, that is only half the issue. I already fixed with manual driver load, the same ones I used in this rip. I do not use host import at all, definitely not on that rip because this is a desktop and that is a Lenovo laptop, different architecture. When I take a blank, NO Driver installed windows and run NTLite from it then the Intel drivers are not amended since it's only the default windows Intel driver that's loaded. But once I install the intel chipset driver on the host machine and I do a rip then the machine I install that rip on tells me that the driver, when I install that machine's intel chipset driver, is older than currently on that machine, and then if I select yes install older version, well then the fun starts.

I will do two rips for you, one with default no drivers installed and one with the chipset drivers installed. However, there is one snag; you cannot tell from the output xml file that the driver is loaded as part of the OS rip. This driver is pulled from the host or source machine and added or included into the rip OS. Their should be an output log that can be checked if available? You have something like that Nuhi?
 
Nuhi. Do you think NTLite perhaps reset the driver info or reset the OS to think that the drivers are newer.....just a question? I'm trying to figure out how and why this is happening.
 
Answers to your screenshot:
- driver checklist, if you don't use it, it's easy to ignore, that would be empty space if turned off. You can pick any machine, like VMware or exported manually.
- INFs even if under some other architecture subfolder name, can still have needed driver version listed inside it.
I'll pick the Realtek driver and see manually if x86 folder should have been filtered out.
It's not actually a bug that it allows adding more than needed onto the list, second line of defense is actual integration which will deny unfitting ones.
And then third line of defense is the PNP detection, where Windows chooses what to pick, so worst case scenario you lose some extra space if you don't filter out the list manually.

That said I do want it to filter better so will check the ones from the screenshot.

As for the rest, I'll need more info if I missed some point, like that resetting of driver info, don't get it.

Thanks!
 
Back
Top