Search options (Page 21 of 213)

there is a limit to the max path length...

if you exceed it any drivers that are beyond the path limit do not install

please take Erik's advise and shorten your path names to one or two letters.

there is also a memory limit for mass storage drivers if you exceed that then they won't install either.

I have only been able to train a handful of people to be able to edit mass storage correctly.
Took me months to train mr_s, it ain't as easy as it looks.

excellent!

ALWAYS include in your post

- DPs_BASE.log (from the same directory as DPs_BASE.exe)

Dism /image:C:\test\offline /Get-Drivers

http://driverpacks.net/docs/miscellaneo … er-attempt

Index one ... don't touch (think safe mode)

index two ... Install (PE) Add mass only. no chipset.
LAN only if Neccessary. If you have no network access you can't get a virus or trojan .
In this way you can install malware protection before you enable your LAN.
Obviously if you are on a protected network this is a non issue.

The obvious reason from my perspective is i don't install chipset into a PE environment.

It may work on certain platforms but is not good for all systems.
Same reason that Chipset and CPU are not available for BartPE. It causes issues.

PE is not a windows environment. it's a Preinstallation Environment. Mass and LAN only .

Although I do see how chipset would make sense to most people, it is not recomended.

That is why i recomended USB3 for Mass ... that way people don't have a reason to shoot themselves in the foot by installing chipset in the PE stage of setup .

Jeff

you have the cart before the horse.

the ini file entries are carried out based on whether or not the driver is installed, not the other way around. the ini file entries are read and executed by the DriverPacks Finisher as the last stage of the driverpacks install.

IE an Nvidia driver must be installed before the INI entry to call the installer for the Nvidia control panel is run by the DriverPacks Finisher.

So to disable a driver either delete its directory or rename its INF file to another extension (like .BAC)

Hope that helps.

PS finally got the email !

Jeff

I did not get the email to the admin either...

Jeff

Exactly... Same as any other PE

some things do remain the same

Can we use a different sys file for Txtmode like we do with some of the other drivers?

you are not able to add driverpacks to your installation with nLite... that will DEFINATELY fail.

the only way to reliably add the DriverPacks to your install is with DriverPacks BASE. If you could we would not provide the DriverPacks BASE program.

Please read the instructions, this is clearly stated.

http://users.telenet.be/jtdoom/basetute/Eng_tut6b.htm

http://driverpacks.net/docs/beginners-guide-windows-xp

Thanks for reporting your issues with the packs...
however both of your issues are related to User Error. Please read our tutorials and forum and use the DriverPacks the way we recommend and you will have no issues going forward.

Have a great day.

Jeff

the only supported method of adding drivers to PE is to create the plugins with DriverPacks BASE.

If you add our packs using the method recomended then you will find no driver errors.

If you attempt to add drivers as extracted from the packs they will fail... If you could do this we would not have written a program to create the BartPE plugins.

Sound will definatly not work... the issue is not with the drivers the issue is with the HWPnP plugin that is used to support advanced drivers in PE. If a version of HWPnP is ever written to support sound then we will enable BartPE plugin for sound. Until then advanced drivers will fail at PE. This is not an issue with the drivers it is a limitation of the PE environment. PE was never intended to be an OS replacment, it is an installation and repair tool and nothing more. (sound is not needed to repair or install windows )