I wanted to add my Wi-Fi driver but I think it is an application

357mag

Member
Messages
139
Reaction score
5
I was thinking it would be neat if upon getting to the desktop after a custom NTLite install the driver for my Wi-fi would already be installed. I was going to integrate it into the NTLite interface, but upon looking at what I downloaded, it appears to be an application. It's not an .inf file. I downloaded it from the Asus website.

Does this mean it's a no-go for me?
 
Last edited:
The normal methods for extracting driver files from an installer EXE include:

1. Check if the EXE file is readable by 7-Zip or WinZip.
2. Check if the installer has a command-line option to extract driver files to a folder.
3. Install the driver using the normal method, and export the drivers afterwards to folder.

You have the option of installing a licensed copy of NTLite on the target PC, and importing the host's driver list to the image. Or you can export all of the 3rd-party drivers to a folder using:
Code:
pnputil /export-driver * D:\Drivers

Copy the driver files back to the original NTLite host, and import from this folder.
 
What's the ASUS model number? Maybe it's not that bad.
 
I was thinking it would be neat if upon getting to the desktop after a custom NTLite install the driver for my Wi-fi would already be installed. I was going to integrate it into the NTLite interface, but upon looking at what I downloaded, it appears to be an application. It's not an .inf file. I downloaded it from the Asus website.

Does this mean it's a no-go for me?
If it's the same machine from which you're preparing an image and the device is working on the host, and you have an NTLite license, you can import the driver with one button from the Drivers page toolbar - Host import.
I would filter out/remove unnecessary drivers added after that step though.
 
Back
Top