Clangers Minimum Fonts List [en-US/en-GB only]

Some of the language fonts have moved to on-demand downloads, if they're not native to your Windows edition. They can be integrated from the Optional Features on Demand ISO to an image.

Segoe UI fonts are actually display icons for the Windows UI. Removing them gets you square boxes in the place of missing symbols.
 
there can be some pretty substantial savings to be had from removing uneeded keyboard and languages(and related components), combined with fonts and uneeded drivers.
 
Clanger said:
there can be some pretty substantial savings to be had from removing uneeded keyboard and languages(and related components), combined with fonts and uneeded drivers.
Click to expand...
Is there a list of what specific drivers do? I'm removing a good amount (like a pos barcode scanner driver??) but it would help to know what the other less clear ones are. I've just been googling back and forth and I'd like to not have arthritis in my hands at 40 ;)
 
ive never seen a list, i just play it by ear, you know what you use and dont use.
whoever invented the pc mouse did not have arthritis in their hands.

you can go either of 2 ways with drivers, completely customise for a specific machine or the one size fits all - what i do here is remove all 3rd party published drivers - example amd_sata.sys/inf and not ms driver for amd_sata.sys/inf, geddit?
 
Last edited:
domainofthegods said:
Is there a list of what specific drivers do? I'm removing a good amount (like a pos barcode scanner driver??) but it would help to know what the other less clear ones are. I've just been googling back and forth and I'd like to not have arthritis in my hands at 40 ;)
Click to expand...
Every PC is different, but here's my list of drivers that "normal" home users don't need. Copy/paste the lines into your preset.

There's a ton of network drivers still present in the image. I wouldn't remove them all, unless you're ready to import your required set of drivers immediately back from the Drivers screen.
 

Attachments

garlin, stick a link on post no1 or move your comment to top of page no1 so it can be easily seen because people looking for driver info wont be looking inside a Fonts thread :)

like i suggested to hellcow you really need your own little Repository thread because your stuff wont get found if its all over the shop.
 
and thats why i recommend removing the 3rd party published drivers only for a good(good is relative) all round image.
garlin knows his onions.
 
Last edited:
garlin said:
Every PC is different, but here's my list of drivers that "normal" home users don't need. Copy/paste the lines into your preset.

There's a ton of network drivers still present in the image. I wouldn't remove them all, unless you're ready to import your required set of drivers immediately back from the Drivers screen.
Click to expand...
I wanna just chime in. I know this doesn't necessarily pertain to "home users" but I remembering getting wild with driver removal. Doing MANY trial and errors. I definitely ran into 2 issues that were harder than others to track down. I needed an HP (non-microsoft) printer driver to install the driver for the HP printer was using at the time. I wonder if this is still an issue, if all non-microsoft drivers are removed? The one that took me the absolute longest to identify was a Modem driver which was necessary to create a virtual COM port during the "rooting" process for the Amazon Fire TV 2. (wish I could remember which one. I had it posted here on NTLite prior to the forums being created)
This was on Windows 7 Professional x64 when I was doing that particular trial. A good 6 months on my quest to perfect Win7! It was fun. I'm doing Win10 now....
 
Jim said:
I wanna just chime in. I know this doesn't necessarily pertain to "home users" but I remembering getting wild with driver removal. Doing MANY trial and errors. I definitely ran into 2 issues that were harder than others to track down. I needed an HP (non-microsoft) printer driver to install the driver for the HP printer was using at the time. I wonder if this is still an issue, if all non-microsoft drivers are removed?
Click to expand...
The answer depends on how your printer is connected: USB, Ethernet, Wi-Fi or even Bluetooth. There's a HP driver which only understands the printer's specific features, but an unrelated driver might be required for Windows to communicate with the printer.

Jim said:
The one that took me the absolute longest to identify was a Modem driver which was necessary to create a virtual COM port during the "rooting" process for the Amazon Fire TV 2. (wish I could remember which one. I had it posted here on NTLite prior to the forums being created)
This was on Windows 7 Professional x64 when I was doing that particular trial. A good 6 months on my quest to perfect Win7! It was fun. I'm doing Win10 now....
Click to expand...
Physical serial ports have mostly disappeared after USB replaced them for connecting non-PC devices. A lot of "console" apps are based on the legacy serial protocol support that's part of the modem libraries. Why a modem? Back in the old days, everyone used external modems for dial-up before they were replaced by on-board Win modem chips. For backwards compatibility, Windows emulated a serial console interface so you could dial using the well-supported ATDT command set.

Either a driver is entirely self-contained, or a dev cheats and borrows another device driver to handle the dirty work.
 
garlin said:
The answer depends on how your printer is connected: USB, Ethernet, Wi-Fi or even Bluetooth. There's a HP driver which only understands the printer's specific features, but an unrelated driver might be required for Windows to communicate with the printer.


Physical serial ports have mostly disappeared after USB replaced them for connecting non-PC devices. A lot of "console" apps are based on the legacy serial protocol support that's part of the modem libraries. Why a modem? Back in the old days, everyone used external modems for dial-up before they were replaced by on-board Win modem chips. For backwards compatibility, Windows emulated a serial console interface so you could dial using the well-supported ATDT command set.

Either a driver is entirely self-contained, or a dev cheats and borrows another device driver to handle the dirty work.
Click to expand...
It was connected via USB. I'm all networked these days. And I found that modem driver I was speaking of...ya'll addressed it in another topic...

garlin said:
This thread was missing key details, which I found in your MSFN post USB serial interface driver problem, error message; can't find file

By reading Uniden's driver INF, it requires copying this device driver (mdmcpq). You can use the hard-to-see search box on the top of Components tab to find which driver class it belongs. The driver certificate is dated 2014, but looks valid. I don't have the signing tool to check its validity.

Look for a folder named Windows\system32\DriverStore\FileRepository\mdmcpq.inf_amd64_neutral_3f60a6f21f7bb0d9 on your machine.

View attachment 5073

Remote Assistance & RDC are red herrings. They work on the UDP & TCP network layer, and don't care about drivers except for display acceleration.
Click to expand...
 
You must log in or register to reply here.
Back
Top