Search options (Page 59 of 213)

@zee - Demerit awarded

per our "Posting Guidelines"
If you create a post that says "I am looking for a driver for" then you will be awarded a demerit .

Welcome to DriverPacks (please read the rules)

@jinkazama - You rock!

I am not sure about sysprep proceedure with OLSP... I defer to the crazy sysprepers of our forum

But regarding the driver installation...

1) You simply call sysprep.inf with dp_inst_tool.cmd being called under 'runonce'.
    SAD M2 is better than extracting and running devpath on C:\D because the drivers remain archived.
    This saves you around 1 gig on your image

    Notes: Your other method would work as long as you don't EVER use KTD.
    Simply running devpath on the c:\d\ folder was all that was needed.
    KTD was killing you. As previously stated do not run makepnf...
    KTD uses makepnf... Therefore you failed . (Because you inadvertently used makepnf)

or

2) You could combine devpath and dp install tool methods together.
    Create a SAD M1 folder
     -  Be sure to enable QSC so you won't have to cab compress a pack more than once.
        QSC (Quick Stream Cache) keeps a copy of the cabbed drivers for M1 slipstreams.
           (The first run is slow because they are cabbed with makecab.exe, after the first run they are simply copied.) 
    Copy everything from the driverpacks.net M1 folder to c:\
    Run devpath on C:\D
    Call dp_inst_tool.cmd under 'runonce'

this Hybrid method both makes the drivers available to minisetup and runs the dpinst.exe and the DriverPacks Finisher. Effectively making two passes on the machine to ensure drivers are fully installed. Some drivers require two passes. IE you cant install a HDA device unless the HDA bus driver is installed first. chipset drivers have to be installed before drivers that rely on chipset etc...

In many cases dpinst.exe works fine but some failures have been reported in the forum.

Please note that even though M1 will take a long time to run on your first time it will save you a huge amount of space over simply extracting them.

Definately use the mass storage pack! (as long as you don't use makepnf or KTD it will not crash!)

I hope that helps

Isn't it on the side of your PC?

UBCD4Win IS BartPE...

They have just done all the work for you already

IE DriverPacks is included, required plugins included, AV programs included, disk tools included, etc...

It is the whole package already assembled waiting for you to supply a copy of XP .

http://driverpacks.net/

check the news on the home page

and this mass pack DriverPack MassStorage 10.01.25

please read "Read BEFORE you post" linked in my signature, it details how to request help .

Please post your DPs_BASE.log and we will see what went wrong .

I think he is a spammer the link he posted redirected through a third party website .

if a driver has the same name as another then tag it (similar to mass )... yes a select few

well if you put them both in hp1 then the skip command will skip the entire folder... not the result we need
the ris drivers will need their own folder

Well you're really beating yourself up trying to do this manually...

DriverPacks BASE will build a proper plugin for you!

read the DriverPacks BASE BartPE tutorial in my signature... (after re-reading your post i get the impression you did)

Do NOT try to use the drivers folder!
Do NOT extract anything!
Move your drivers folder out of your pe folder entirely (or delete it if you like).

Follow the Tutorial to build a proper PE plugin... (that is why i wrote the code into DriverPacks BASE to build plugins form the packs )

you should end up with \plugin\DriverPacks.net\*.*

at the time i wrote the tutorial LAN was not supported... now it is... Simply allow DriverPacks BASE to build your LAN plugin . that should solve your Mass and LAN issues entirely (again after a re-read that seemed to be method 2 you refered to)

Let me know how that works! PS I added code tags to your very detailed post (Excellent job!)

I Would like to work on method 2 since that not only fixes it for you but everyone else with your same hardware

Try method 2 on a clean sp2 source and post your DPs_BASE.log and if your pebuilder log shows build errors let's see those.

Jeff

PS the LAN pack includes the "joshua" plugin drivers (or it used to) So if you play with adding the josua plugin you're duplicateing them

PSS RAID issue? read this thread, re load order and the mass storage INI file http://forum.driverpacks.net/viewtopic.php?id=3907
your fix may be to move the RAID driver section around in the Mass Storage INI

Well he did post in the "hardware" forum

I tend to agree with both of your points BigBrit...

The Antec true power 550 will deliver 550 watts continuous (100% duty rating) and is the same PS I use in this machine a p4 2.8 HT w/ a 6800GT this machine pulls about 300W and it is a good match... Why strain your PS by running it at 100% duty . Give yourself some elbow room . Besides what if you upgrade again?

This is not a noob freindly site... OT questions and help with basics is greatly frowned upon...
This forum is for hardware questions as they relate to drivers. (now you know)

demerit awarded !

Re duplicate names in separate folders...

I wrote this code last year for bartpe...

when two drivers have the same name the last one processed by BASE wins...
by assinging a unique name for the "tag" value this issue is resolved
REMEMBER the tag name must be unique not only to ALL of the packs used for BartPE but also to existing windows files too .

Try this please...

LAN 10.02 RC3