DriverPacks.net Forum - Why some drivers can't be checked?

Re: Why some drivers can't be checked?

null@example.com (pclover) — Fri, 22 Oct 2010 01:29:31 +0000

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.

Re: Why some drivers can't be checked?

null@example.com (OverFlow) — Thu, 21 Oct 2010 05:52:44 +0000

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.

Re: Why some drivers can't be checked?

null@example.com (pclover) — Wed, 20 Oct 2010 17:10:54 +0000

Thank you, mr_smartepants.

I want to use BartPE as a LiveCD with multimedia function.

Re: Why some drivers can't be checked?

null@example.com (mr_smartepants) — Wed, 20 Oct 2010 17:05:40 +0000

Because BartPE was written WITHOUT support for those DriverPacks.
Why would you want sound in PE? It's a Pre-installation Environment.

Why some drivers can't be checked?

null@example.com (pclover) — Wed, 20 Oct 2010 16:36:27 +0000

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?