Search options (Page 207 of 213)

your source should not be slipstreamed for bartpe for two reasons

one - pebuilder will not copy any files other than the ones that are on its internal list of files. so slipstreamed drivers will not be copied.
two - drivers that are "upgraded" by slipstreaming my cause issues during the build process.

use a non driver pack modified source and use the base to create a plugin. then make sure the plugin is enabled from the pebuilder plugin screen. the drivers will be added to the destination during the build process. (and yes you have to select BartPE to get a BartPE plugin)

if you have done this correctly you will have a mass storage plugin in PEBuilder that is enabled.
(all the other packs will be greyed out for bartpe because only mass storage is supported so far.)

yeah that is what i expected the two unknown devices are probaly the fixed feature buttons (like the internet explorer button on the laptop) the monitor driver will need to be from the laptop manufacurer same with fingerprint reader and modem. although the modem driver may be in the third party modem driver pack.

the wireless and dlan need to be investigated to see if teh HWID's are in the existing packs

well, there is often a domino effect -
If the chipset driver fails then the nic and vid may also since they are connected to a device that is not working 100%.

useing vista as your workstation for the building of your disk has no known problems, so don't worry about that.

I expect you will be quite susccesful with a standard desktop.

can you give a list of the devices that failed to install properly and your HWID's (i know most of them are in the finisher log already)

thanks

I see the HWID's below what about the list of devices that didn't install correctly?

It's not documented... yet

Ah yes, i guess i was sleep typing.... Nice pickup jt.

Apparently you have not been following the progress of driverpacks and BartPE we do use cabbed drivers and add them to txtsetup.sif.

and it isn't a pain at all. Try it youll like it!

Slipstreaming drivers into the source fails because the new drivers are not on the "list of files to copy" from the source that PEBuilder uses. and wont end up on the destination. that is why we create a plugin.

It does seem the modem is not in the list... it may not be plug and play compatable or may depend on a device that is not installed yet.

the PCI\VEN_1002&DEV_5A62&SUBSYS_13921043 should match the PCI\VEN_1002&DEV_5A62&SUBSYS_13921043&REV_00 device.

ATI Radeon Xpress 200M is the driver that should match the card but i suspect taht this is a laptop and it has a proprietary chipset provided by the distrubuter ( toshiba or dell or whoever it is)

ONE - please verify free space on your disk your useing - with QSC on you may need over 3 gig free
(the temp folder with the extracted drivers is around 1.2 gig the QSC cache folder will be around 500+ meg = 2 gig then add your source files and some room to work)

TWO your slipstream was NOT successful

THREE read this post - READ BEFORE YOU ASK!
http://forum.driverpacks.net/viewtopic.php?pid=4#p4

I have not heard of anyone else with this issue.

Is D: a mapped drive letter? 
(ususally D is a CD ROM but certainly you didn't try to write it to a WORM device)
(try it on a local copy if so and then move it to the server after successful completeion)

Major - you are on the testing team, are you not?  then it seems silly for me to have to ask you for your HWID's doesnt it?

my suggestion would be replace the file (NTFS.sys) that is being reported as damaged with a known good version (possably from a working installation) and try again.

(PS Nlite may be modifying this file so don't run nlite after you replace it)