Re: Disable DriverPacks in other forum...

there are pictures in the tutorial in my signature
when i wrote the mass storage plugin i also included the tutorial with DriverPacks BASE
and the tutorial is available if you hit the help button in pebuilder.

there are two entrys shown in figure 3

first is DriverPacks BASE the DriverPacks main executable - it is only here to configure plugins it is not a plugin itself so it CANNOT be disabled because it is not 'enable'able (its an exe not an inf and is ignored by the actual build process it is only here for the end user)

Second is the actual mass storage plugin this can be disabled (or enabled)

a simple check of your build log will verify this.... if youre still not convinced just drag the DriverPacks.net folder out of the plugins folder (Then they will both be 'gone'. {even better than disabled} At least until you drag it back)

but i bet a nickle, it ain't the driver wink

PS it seems obvious to me that the best way to disable a 'plug-in' is to 'un-plug' it  wink
PSS The link they sent you to is valid for adding your "Known Good" driver.

For some reason the DriverPacks Finisher did not run... you can just double click on it...

"DPsFnshr.exe"  will finalize all your drivers and remove all those files when it is 'finished' with them. wink

but ... why did it not run... did you do gui run once or runonce exe?

PS mute disables the annoying popup sound when a non signed driver is used wink

Well I had a 15 minute union break and decided to do some code instead of coffee   

Version Release Notes:
Developer: Jeff Herre aka OverFlow
===================================

NEW PLATFORM ADDED

Stand Alone Drivers (S.A.D.)!

Create a Stand Alone Drivers location - Without a source OS
    Use either Method One (M1) or Method Two (M2) for your output
    I am in process of designing a M3 (Raw uncompressed) method
    with DVD as standard equiptment now space is simply not the concern it once was

DP_Install_Tool.CMD had some minor updates wink
     A total rewrite and honestly too many for me to remember... lol
     DriverPacks BASE M2 packs will be in 8.3 format, but, they Do Not need to be!
     This means an M2 S.A.D. folder can be maintained simply by swapping out packs,
     as downloaded, without renaming. Convenient?... yeah we thought so too!

I added DeTard's feature request for an Option to skip driver removal with DriverPacks Finisher
     A new option has been added for use in the DPsFnshr.ini
          DPsRootDel  = "false"
     This switch prevents deleting the /D/ Folder
     This feature was necessary for S.A.D. M1
         - useful to S.A.D. when a M1 source is located and used and (most importantly) NOT deleted... LOL
           IE A ThumbDrive is used for a M1 S.A.D. folder location
               The dpinst tool is run directly off the ThumbDrive \D\ folder. (No copy or extraction)
               normally this folder would then, quite sadly, be deleted by the DriverPacks Finisher. Rats...
               add  DPsRootDel  = "false" to the DPsFnshr.ini and no longer do you have to say... Rats... big_smile

I added DeTards's feature request to process the QSC without Slip-streaming as a by product of the above request...
     I am actually 'cheating a little' on this one
     Use the S.A.D. platform and choose M1
       (CAUTION - base deletes target folder if it exists - Use a dummy folder if needed big_smile

===================================

I added Helmi's Feature Request for the Nvidia control panel feature
     [REQ] Option to select between Old, New or Both for the NV CP design
     Base writes the registry file entries to a file called nvidia.ins
     base will set the correct settings in that file based on the users GUI selection
     the required DriverPack Graphics A INI entry is being added and exists in the current nightlies
     the DriverPacks Finisher will run regedit /s %systemdrive%\nvidia.ins When an appropriate nvidia device is detected
     This feature works in a similar manner as the ATI CCC or CCP function you are all familiar with
     the primary difference is this just creates some registry entries instead of calling an installer.

I added JSe's feature request for folder searching in presetup.cmd 
    [REQ] PreSetup.cmd - add on success/exit to drive letter search loop
   

I added yiuc1's feature request for a date stamp for the LOG file 
     ChiefZeke also gave excellent input on this Feature Request
     [REQ]  Backup of log files
     Added a dated log in a sub-folder
      IE \[DPs_folder]\LogFiles\DPs_BASE_08-09-02_01-48.log 
     The log file now also contains the DPs_BASE.ini settings that were used
     We also create the  \[DPs_folder]\DPs_BASE.log too because legacy support is required, dolivas reporting
     Neat feature...


I added Copy the current DPs_BASE.ini settings to end of the DPs_BASE.log

I fixed reported bug with language files on overview page - helmi reporting

I added start /wait /separate /realtime call to un7zip to the presetup and S.A.D. disk calls
And maxximum asked his friend STK, (who coded the current version of un7zip that we use), to optimize it for speed.
STK did optimize his code and un7zip is Much faster now! Kudos Guys!
     The combination of these two together, Well... It's faster wink

I fixed a quirk where the Version checker offers older based versions as "upgrades" to newer beta versions - mr_smartepants reporting

I updated alignments in the GUI and increased the description box's size
I updated master language file to include new, old and both for use in base translations
  Created a translation for BartPE since it is necessary for the hot key function. (good eye Helmi)
  Wrote a description for the DriverPack Graphics A options page

I added Nvidia and ATI control panel settings to OverView page

I Updated Hot Key functions 

I corrected spelling error for DriverPacks Finisher - mr_smartepants reporting
forfilled -> fulfilled

I created a Workaround for a bug mr_smartepants found in the MS dpinst.exe tool
     DPInst.exe fails when it is run from the root folder of a drive.
       It appends an extra \ after the search-path if it is run from a root folder, 
     IE c:\\D\,  and then 'minisetup' (DPInst) fails to install any drivers.
     dp_install_tool.cmd and DriverPacks BASE code were both updated to compensate for the path issue with dpinst.

I added command line parameters to DP_Install_Tool.cmd...
    you may choose ONE of the three following choices...
      V=Verbose not case sensitive and list a few extra items that normally output to null
      Q=Quiet not case sensitive and skips the beeps and pause at the end (skip the attended output stuff)
      "Your_Path\Filename.here"=Log to "Filename.here"

         IE  "Your_Path\DP_Install_Tool.cmd" "C:\Documents and Settings\All Users\Desktop\DP_Install_Tool.log"
         OR  "Your_Path\DP_Install_Tool.cmd" Q


I added language updates that were submitted by:
English       Jeff Herre ~ OverFlow
German       Helmi
french       Maxximum
Italian        jinkazama
Portuguese  Sandrion
Spanish       ricktendo64

Main testers (in alphabetical order) reporting on base 809 alpha:
BigBrit, dolivas, Echo_Platoon, Helmi, mr_smartepants, and Sm0k3r

My Special thanks and great appreciation to our translators and testing team for making this RC possible!
I can't say enough nice things about the DriverPacks team here...
'We' make DriverPacks possible only through working together towards a common goal.
Each of you is the most important member of the Team...

    - Report any good or poor results please ! ( it's always nice to read... 'no problems found' )
    - Reporters are members of the team too... wink


HERE YOU GO --->> http://dev.driverpacks.thesneaky.com/dr … 809rc1.exe


Main Packs - progress and release notes:

Mid summer is always a rough time at DriverPacks because Intel releases their new chipsets and drivers. There is always a few months of turmoil that result for us. Please know that we're working feverishly to release updates to the major DriverPacks (DriverPack Sound A, DriverPack Graphics A, LAN, ect...). Our primary goal has always been to support all hardware, and our secondary goal is providing the most stable drivers available. You may already be aware that newer drivers sometimes have bugs wink. I would like to quote Orson Welles, from the old Paul Masson Commercial,  "We will release no driver before it's time!"  wink  big_smile  LOL...

The team has several of the main packs in the final stages of testing and it will be very soon. (are we there yet?)

last and most important, my thanks and respect to Wim Leers for bringing all of us DriverPacks.net.
It is our intention to continue successfully down the path he blazed.   
When the people around you make you want to be better than you were yesterday, then you're in the right group  wink
thanks

- Jeff

Well i can't send money... so how does an upgrade to your membership sound...

Nice Job. Giving back to the community is an awesome thing to do and a rare and honorable quality.
Your efforts have been recognized by the team and myself.

Welcome to the testing team Kickarse!

Thank you for that VooDoo that you do! big_smile

jeff

PS you will find that the testing team forum is now visible to you... wink

I can leave it open, if it is OK with you?

Perhaps you can provide a link to the post in the other forum? Please.

This issue may present itself in the future
  and you may help someone else who finds themselfs in your situation... big_smile

Thanks for stopping by and asking,
I am just quite certain the crew at UBCD4Win will know exactly what happened...
I'm just a PE noob compared to those guys... and therefore i would be guessing  wink 

You need a specialist... big_smile 

jeff

It is a feature that is not well documented... i apologize

I totaly rewrote it last year but recieved no feedback on it...

If you would like, it would be an awsome contribution to document it.
I think it is easier for someone with a different perspective than mine to outline it.
could get a sticky from helmi too... wink big_smile

that is to say; it already makes sense to me wink

jeff

3,432

(1 replies, posted in DriverPack Chipset)

read before you post in my signature please...

details man! we need details!    like what are your HWID's?

welcome to the forum GnEE...

Obviously your HDD was detected properly or you would not have access to the drive at all...
Logicaly you should have relized this is not a DriverPacks issue since the HDD was accessable.
put another way, file system access is OS related not driver related
you need to do a search on UBCD4Win for fat32 support, and post there for support...
UBCD4Win does support fat32 so you must have an issue with your build...

so not only did you post this in the wrong forum at DriverPacks (mass storage instead of UBCD4Win)
you also posted it on the wrong website... wink

have a great day and good luck

moved to UBCD4Win forum

3,434

(88 replies, posted in DriverPack LAN)

I am a little confused here since the DriverPacks bartpe plugin doesnt use the inf.

the info for the build is taken from the mass storage ini...

what am i missing here...?


Ooops were talkin lan not mass NM...

Jaak wrote:

Question to Jeff
Could the "="=" have nulled that entire driver?

I belive so, yes.  It probably tried to match the = sign as a HWID. lol

which means that it picked up on another hwid from another section...?

Well you assume incorrectly one job i had, working for the phone company
(you might have heard of the phone company... Ma BELL?). I had 50 techs working for me...
and we managed 5000 desktops daily... I started in computers in 1968...

So yes i have more than a little experience... in fact i have more experience than anyone you ever met...
i got my degree in programming and have been a PC hardware tech since before you were born...
you may be a big dog with your friends - Here you are just a snot nosed kid, with bad manners.
Most of the team have similar responsibilities in their jobs... this ain't the noob forum.

This is the first and last time i am going to tell you to show some respect... Failure is unacceptable.

all DriverPacks files must be at root of drive

base supports multi boot it is a gui option...

3,438

(10 replies, posted in Other)

This line is the 'unattended from a script' method you were asking about  wink

DPs_BASE.exe /settings:[MyBase.INI]

if MyBase.INI exists in the same folder as DriverPacks BASE...

Copy (or export from DriverPacks BASE) your DPs_BASE.ini settings file to  MyBase.INI
Then you will need to set the line GUI=yes to GUI=no in the MyBase.INI file.
(remember to reset GUI=yes if you use the default DPs_BASE.ini name or you will never get back to the GUI. wink)

mind you this is not api mode (quiet), the main base 'logging' screen pops up and runs visibly...
it just doesn't stop for any user input and runs unattendedly... what i belive you wanted big_smile


I am certain this has been a feature since at least early last year (base 7.xx.xx or later)
My apologies for the lack of documentation on this...

Jeff

the fix for the card reader hang was fixed in the base version 8.08.28 alpha (last month)
you can look forward to your issue being resolved in the next release

you can take a peek at it now if you like...
just remember it is for testing only and is a beta version... wink
(my betas are usually rock solid wink)   

 http://dev.driverpacks.thesneaky.com/driverpacks_nightlies/DPs_BASE_80915b.exe

i belive if you try that version you will find that the card readers will no longer hang you up...

if they do still Hang after useing the above version or if you know the boot order in the bios is incorrectly assigning drive letters to your removable media (card readers) before the HDD. IE the SystemDrive will not be C:  It will be G: - or whatever letter is next after assigning each of the removable drives a letter. If it's true, that the HDD can not be assigned as the primary boot device 'C:' from the machines bios, then i can tell you how to customize your setup so you can address the machines BIOS problem. wink

The drive letter / bios problem normaly shows up when a card reader is added to a desktop and the MB bios is not able to correctly deal with the removable drives - since you indicated this was a laptop i don't expect you will have this happening to you...

I think you should take a deeper look at UBCD4Win / BartPE...

the focus is quite certainly on being a recovery / admin tool...
And GREAT care is taken not to write to the HDD just for the reason of recovery.
and the recovery tools are the best available...

I agree there are a few rogue plugins out there, but you dont have to download or install them either...
and there are very few of them...
I remember one particular guy did attempt to write a sound driver plugin for PE...
Ben (Developer of UBCD4Win) rebuked him severely for loosing focus of the purpose of the tool... wink
Which brings me to this point - you can't watch movies on BartPE, not with no sound drivers wink
Or to put it another way yo would have to work really hard at a BartPE build to get sound and then subsequently movies... wink neither messengers nor media players are included nor is sound support...

so I can only assume you know absolutely nothing about bartPE...

There IS 30 different antivirus, spyware, malware tools and a few dozen hdd recovery tools. all i assure you better than the MS counterparts. offline sysprep... full network support with browsers, support for Ghost, Norton AV and other licenced products (if you have the licence)...

So before you trash talk you should know what your talking about... and you obviously don't...
You also don't realize that we all (the team) manage more computers in a day than you have seen in your lifetime...
(i personally do / have  managed networks in the 500~70,000 client PC range)

The last i heard ERD (Winternals and MS versions) are quite unstable and limited...
and had issues with adding drivers and it doesn't support changing resolutions wink
the only feature that ERD has that is yet to be added to BartPE is the system restore function.
And that is a hit or miss proposition in itself...
half the time system restore is unable to restore a previously saved 'restore' point.

and i guess i have explained why bartpe is popular and erd is not...

note: I personaly spend the money for an OS licence, rather than use ERD for free! wink

Jeff

PS irritating the guy who would code your 'proposal' into DriverPacks BASE is not the best way to get a feature added... wink tongue big_smile

RogueSpears AutoImage uses DriverPacks to achieve RIS support...

perhaps you could look at what RS's AI does and see if it will work with your scenario

Sounds to me like this guy is putting ISO's up on torrents mad

Thanks for the missing pieces of the puzzle...

since we get about 32,000 downloads a day and this is the second request for this in more than three years i don't expect that there will be much activity on this... But I could be wrong...

We all use bartpe or ubcd4win... wink

have a great day and thanks for your input and details / links. It is always nice to have options.

welcome to the forum

kickarse wrote:

I just wish I had some feedback on how it's working for everyone.

Thanks for the compliments! big_smile

welcome to my world... wink   thank goodness for bigbrit... big_smile

3,445

(210 replies, posted in Software)

the second quote is in the wrong spot

REG ADD %KEY%\065 /V 1 /D "c:\drivers\DPInstaller_WSED.exe" /unth /f

my script is also for attended installation...

you seem dead set on useing the attended scripts for doing an unnatended install

from your other post

"It calls DPInstaller_WSED.exe in the RunOceEx.cmd  from C-disk for UA(xp)."


that indicates that you are doing an unattended install

WHY!!!   
             are you trying to use the attended methods to do an Unattended install...


the base slipstraeams drivers for unattended install... that is what you want...
so use it as presented or at least tell us why you refuse to do so...

did you try useing search feature of the forum... grrr...

obviously not... please at least attempt to find things on your own
this is not your moms house...

http://forum.driverpacks.net/viewtopic.php?pid=23108
http://forum.driverpacks.net/viewtopic.php?id=435

it is ironic that you are trying to force his add-on to do what the DriverPacks do right out of the box...

by useing DriverPacks BASE (useing the DriverPacks as provided / supported)
you will get the result you are asking WS for...

IDK waht your familiarity is with DriverPacks (because you have not told us any details) but it seems like youre making it harder than it needs to be.

WarmSnows application is for attended install because DriverPacks BASE doesnt support attended installs

however DriverPacks BASE is for unattended installs and is why warm snows app doesn't (directly) support it

so since you are attemptind an unattended install you should be useing DriverPacks with DriverPacks BASE

JakeLD wrote:

So how your suppose to read the drivers network share if you have no network driver installed in 1st place ?

I normally face the machine in the direction of the server, and point with my finger... wink

its worse than that chipset and other drivers will interupt the network connection too...
there is no way around haveing the drivers available localy... period...

PS the entire basic DriverPacks are around 300meg which is still less than the OS wink
pss a 300MB copy at 100Mb or better is quite fast... wink (less than 30 seconds)

all structures are built on foundations...
the foundation of a PC is the chipset... wink