Topic: Why some drivers can't be checked?
Why some drivers (Sound, Chipset, CPU, etc.) can't be checked if I choose BartPE? I've downloaded all the latest drivers.
How to add sound drivers as plugin to BartPE?
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Why some drivers can't be checked?
Because BartPE was written WITHOUT support for those DriverPacks.
Why would you want sound in PE? It's a Pre-installation Environment.
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Why some drivers can't be checked?
Thank you, mr_smartepants. 
I want to use BartPE as a LiveCD with multimedia function.
- OverFlow
- DriverPacks Administrator & BASE Developer
- Offline
Re: Why some drivers can't be checked?
PE is an installation and recovery tool not an OS replacement.
mr_smartepants is correct.
BartPE does not have the capacity to support sound drivers...
Multimedia / Sound support requres more than just the device driver.
Since they won't work, they have been disabled as a selection.
DP BartPE Tutorial DP_BASE Tutorial HWID's Tool Read BEFORE you post UserBars!
The DriverPacks, the DP_Base program, and Support Forum are FREE!.
The DriverPacks, the DP_Base program, and Support Forum are FREE!.
Re: Why some drivers can't be checked?
Thank you, OverFlow.
Because I'm writing an article about UBCD4Win. I followed this guide to slipstream drivers.
http://driverpacks.net/docs/Miscellaneo … rtpe-guide
Some readers run UBCD4Win in VMware Player as another OS. They don't care too much the boot time but the multimedia functions.
Now I know more about DriverPacks and UBCD4Win's driver mechanism. Thank you.