When slipstreaming to a BartPE environment, the Mass Storage drivers are greyed out in the driver packs selection. For some reason, I always felt this simply meant that it ALWAYS would slipstream the Mass storage drivers, but I am wrong. I found this out the hard way today when trying to boot a Dell PE T310 and the SAS 6 driver wasn't properly loading, and that was fixed in 11.09 and the last one I had THOUGHT I had slipstreamed was 12.03. If I'm building from a disc, the option is available.

Anything I need to do in order to incorporate the Mass storage drivers into BartPE? (as in perhaps finding another forum article)?

I needed access to a new raid controller on the newest DELL servers. I created a Mass Storage 10.11.1 for my purposes. These are the additions:

ms_1_deviceName="Dell PERC H700 (W2K3)"

The driver set, I can zip up and mail some place, otherwise they can be found at: http://support.dell.com/support/downloa … eid=283231  The download is less than the size of a floppy.

Let me know if you need anything else. Works beautifully. (the driver, that is) As for the controller, I have some real grumbles about the device I'd be happy to share in private.


newest problem: Acer K50IN series, I'm looking at finding this driver. It's an Nvidia G102M chipset:

PCI Devices 
PCI\VEN_10DE&DEV_0873&SUBSYS_19B41043&REV_B1\4&48E82CA&0&0080: NVIDIA GeForce G102M 
PCI\VEN_10DE&DEV_0A83&SUBSYS_CB7910DE&REV_B1\3&267A616A&0&00: PCI standard host CPU bridge
PCI\VEN_10DE&DEV_0A88&SUBSYS_CB7910DE&REV_B1\3&267A616A&0&01: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0A89&SUBSYS_CB7910DE&REV_B1\3&267A616A&0&1B: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0AA0&SUBSYS_1CF71043&REV_B1\3&267A616A&0&80: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0AA2&SUBSYS_1CF71043&REV_B1\3&267A616A&0&1A: NVIDIA nForce PCI System Management
PCI\VEN_10DE&DEV_0AA3&SUBSYS_1CF71043&REV_B1\3&267A616A&0&1D: NVIDIA nForce System Management Controller
PCI\VEN_10DE&DEV_0AA4&SUBSYS_1CF71043&REV_B1\3&267A616A&0&19: PCI standard RAM Controller
PCI\VEN_10DE&DEV_0AA5&SUBSYS_1CF71043&REV_B1\3&267A616A&0&20: Standard OpenHCD USB Host Controller
PCI\VEN_10DE&DEV_0AA6&SUBSYS_1CF71043&REV_B1\3&267A616A&0&21: Standard Enhanced PCI to USB Host Controller
PCI\VEN_10DE&DEV_0AAB&SUBSYS_1CF71043&REV_B1\3&267A616A&0&48: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0AAE&SUBSYS_1CF71043&REV_B3\3&267A616A&0&18: PCI standard ISA bridge
PCI\VEN_10DE&DEV_0AB9&SUBSYS_1CF71043&REV_B1\3&267A616A&0&58: NVIDIA nForce Serial ATA Controller
PCI\VEN_10DE&DEV_0AC0&SUBSYS_16F31043&REV_B1\3&267A616A&0&40: High Definition Audio Controller
PCI\VEN_10DE&DEV_0AC4&SUBSYS_1CF71043&REV_B1\3&267A616A&0&60: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0AC6&SUBSYS_1CF71043&REV_B1\3&267A616A&0&A8: PCI standard PCI-to-PCI bridge
PCI\VEN_10DE&DEV_0AC7&SUBSYS_1CF71043&REV_B1\3&267A616A&0&B0: PCI standard PCI-to-PCI bridge
PCI\VEN_10EC&DEV_8168&SUBSYS_16D51043&REV_01\4&4C866AA&0&00A8: Realtek RTL8168B/8111B Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
PCI\VEN_168C&DEV_002B&SUBSYS_10891A3B&REV_01\4&3AC7AD3&0&00B0: Atheros AR9285 Wireless Network Adapter
19 matching device(s) found.
USB Devices 
USB\ROOT_HUB\4&3468817B&0                                   : USB Root Hub
USB\ROOT_HUB20\4&357D7FD&0                                  : USB Root Hub
USB\VID_04F2&PID_B071\SN0001                                : USB Composite Device
USB\VID_04F2&PID_B071&MI_00\6&32D26C37&0&0000               : USB 2.0 1.3M UVC WebCam
USB\VID_154B&PID_0002\6E570F0002B1                          : USB Mass Storage Device
6 matching device(s) found.
Input Devices 
No matching devices found.
ACPI Devices 
ACPI\ACPI0003\3&267A616A&0                                  : Microsoft AC Adapter
ACPI\ATK0100\1010100                                        : ATK0100 ACPI UTILITY
ACPI\ETD0001\4&44F32A7&0                                    : ELAN PS/2 Port Smart-Pad
ACPI\FIXEDBUTTON\2&DABA3FF&3                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0                : Pentium(R) Dual-Core CPU       T4200  @ 2.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_1                : Pentium(R) Dual-Core CPU       T4200  @ 2.00GHz
ACPI\PNP0000\4&44F32A7&0                                    : Programmable interrupt controller
ACPI\PNP0100\4&44F32A7&0                                    : System timer
ACPI\PNP0103\0                                              : High precision event timer
ACPI\PNP0200\4&44F32A7&0                                    : Direct memory access controller
ACPI\PNP0303\4&44F32A7&0                                    : Keyboard Device Filter
ACPI\PNP0800\4&44F32A7&0                                    : System speaker
ACPI\PNP0A03\0                                              : PCI bus
ACPI\PNP0B00\4&44F32A7&0                                    : System CMOS/real time clock
ACPI\PNP0C01\1                                              : System board
ACPI\PNP0C02\0                                              : Motherboard resources
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\10                                             : Motherboard resources
ACPI\PNP0C02\11                                             : Motherboard resources
ACPI\PNP0C02\5                                              : Motherboard resources
ACPI\PNP0C04\4&44F32A7&0                                    : Numeric data processor
ACPI\PNP0C09\4&44F32A7&0                                    : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\0                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&3                                    : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&3                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&3                                    : ACPI Sleep Button
ACPI\PNP0C14\MXM2                                           : Microsoft Windows Management Interface for ACPI
ACPI\PNP0C14\NVIF                                           : Microsoft Windows Management Interface for ACPI
ACPI\THERMALZONE\THRM                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ACPI_HAL\PNP0C18\0                                          : Microsoft Watchdog Timer
ROOT\ACPI_HAL\0000                                          : ACPI x86-based PC
32 matching device(s) found.
 HDA Audio 
HDAUDIO\FUNC_01&VEN_10EC&DEV_0662&SUBSYS_104316F3&REV_1001\4&221652B5&0&0001: Realtek High Definition Audio
1 matching device(s) found.
RAID Devices 
    Name: NVIDIA nForce Serial ATA Controller
    Hardware ID's:
    Compatible ID's:
1 matching device(s) found.

For the Acer 5515 series that I've been talking about:

PCI Devices 
PCI\VEN_1002&DEV_4383&SUBSYS_028D1025&REV_00\3&2411E6FE&0&A2: High Definition Audio Controller
PCI\VEN_1002&DEV_4384&SUBSYS_00000000&REV_00\3&2411E6FE&0&A4: ATI I/O Communications Processor PCI Bus Controller
PCI\VEN_1002&DEV_4385&SUBSYS_028D1025&REV_3C\3&2411E6FE&0&A0: ATI I/O Communications Processor SMBus Controller
PCI\VEN_1002&DEV_4391&SUBSYS_028D1025&REV_00\3&2411E6FE&0&88: AMD AHCI Compatible RAID Controller
PCI\VEN_1002&DEV_4396&SUBSYS_028D1025&REV_00\3&2411E6FE&0&92: Standard Enhanced PCI to USB Host Controller
PCI\VEN_1002&DEV_4397&SUBSYS_028D1025&REV_00\3&2411E6FE&0&90: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_4398&SUBSYS_028D1025&REV_00\3&2411E6FE&0&91: Standard OpenHCD USB Host Controller
PCI\VEN_1002&DEV_439C&SUBSYS_028D1025&REV_00\3&2411E6FE&0&A1: Standard Dual Channel PCI IDE Controller
PCI\VEN_1002&DEV_439D&SUBSYS_028D1025&REV_00\3&2411E6FE&0&A3: PCI standard ISA bridge
PCI\VEN_1002&DEV_9612&SUBSYS_028D1025&REV_00\4&1E8AA2B1&0&2808: ATI Radeon HD 3200 Graphics  
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&2411E6FE&0&C0: AMD HyperTransport(tm) Configuration
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&2411E6FE&0&C1: AMD Address Map Configuration
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&2411E6FE&0&C2: AMD DRAM and HyperTransport(tm) Trace Mode Configuration
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&2411E6FE&0&C3: AMD Miscellaneous Configuration
PCI\VEN_1022&DEV_9600&SUBSYS_028D1025&REV_00\3&2411E6FE&0&00: PCI standard host CPU bridge
PCI\VEN_1022&DEV_9602&SUBSYS_96021022&REV_00\3&2411E6FE&0&08: PCI standard PCI-to-PCI bridge
PCI\VEN_1022&DEV_9604&SUBSYS_028D1025&REV_00\3&2411E6FE&0&20: PCI standard PCI-to-PCI bridge
PCI\VEN_1022&DEV_9605&SUBSYS_028D1025&REV_00\3&2411E6FE&0&28: PCI standard PCI-to-PCI bridge
PCI\VEN_168C&DEV_002B&SUBSYS_E016105B&REV_01\4&4419318&0&0020: Atheros AR5B95 Wireless Network Adapter
PCI\VEN_1969&DEV_1062&SUBSYS_028D1025&REV_C0\4&364B5521&0&0028: Atheros AR8132 PCI-E Fast Ethernet Controller
20 matching device(s) found.
USB Devices 
USB\ROOT_HUB\4&2B3AF8B0&0                                   : USB Root Hub
USB\ROOT_HUB\4&50F771C&0                                    : USB Root Hub
USB\ROOT_HUB20\4&226161B2&0                                 : USB Root Hub
USB\VID_064E&PID_A103\CN0314-SN30-OV035-VA-R05.00.00        : USB Composite Device
USB\VID_064E&PID_A103&MI_00\6&E51765B&0&0000                : Video WebCam
5 matching device(s) found.
Input Devices 
No matching devices found.
ACPI Devices 
ACPI\ACPI0003\2&DABA3FF&2                                   : Microsoft AC Adapter
ACPI\AUTHENTICAMD_-_X86_FAMILY_15_MODEL_124\_0              : AMD Athlon(tm) Processor TF-20
ACPI\FIXEDBUTTON\2&DABA3FF&2                                : ACPI Fixed Feature Button
ACPI\PNP0000\4&21AFC685&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&21AFC685&0                                   : System timer
ACPI\PNP0200\4&21AFC685&0                                   : Direct memory access controller
ACPI\PNP0303\4&21AFC685&0                                   : Launch Manager
ACPI\PNP0800\4&21AFC685&0                                   : System speaker
ACPI\PNP0A08\1                                              : ATI PCI Express (3GIO) Filter Driver
ACPI\PNP0B00\4&21AFC685&0                                   : System CMOS/real time clock
ACPI\PNP0C01\4&21AFC685&0                                   : System board
ACPI\PNP0C02\3&2411E6FE&0                                   : Motherboard resources
ACPI\PNP0C02\4&21AFC685&0                                   : Motherboard resources
ACPI\PNP0C04\4&21AFC685&0                                   : Numeric data processor
ACPI\PNP0C09\4&21AFC685&0                                   : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&2                                    : ACPI Power Button
ACPI\PNP0C0D\3&2411E6FE&0                                   : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&2                                    : ACPI Sleep Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\SYN1B1D\4&21AFC685&0                                   : Synaptics PS/2 Port TouchPad
ACPI\THERMALZONE\THR1                                       : ACPI Thermal Zone
ACPI\THERMALZONE\THRM                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI x86-based PC
25 matching device(s) found.
 HDA Audio 
HDAUDIO\FUNC_01&VEN_10EC&DEV_0272&SUBSYS_1025028D&REV_1000\4&291E4EA0&0&0001: Realtek High Definition Audio
1 matching device(s) found.
RAID Devices 
    Name: AMD AHCI Compatible RAID Controller
    Hardware ID's:
    Compatible ID's:
    Name: Standard Dual Channel PCI IDE Controller
    Hardware ID's:
    Compatible ID's:
    Name: AMD RAID Console
    Hardware ID's:
    Compatible ID's:
3 matching device(s) found.

Thanks. As you can see, the one HWID I posted for the 5517 isn't found in your list and it's the one that's killing any chance of booting with these newer units. I have an HP with a KSOD situation that's doing the same thing and I suspect it has the same controller.

Zeca61's pointer to the driver isn't working any more, but I found another one by googling the driver version.

I have a client's Aspire 5517 that has the same problem. Vista shows the driver name as ahcix86s.sys but using the ahcix86.sys from the 3.1.1540.81 driver set works fine.

In my case, the HWID was a little different : PCI\VEN_1002&DEV_4391&SUBSYS_028D1025&REV_00\3&2411E6FE&0&88
but it works like a champ if I F6 my UBCD and use that driver with this HWID added to the txtsetup.oem file.

I'm using Driver base 8.12.5, with Mass storage 9.01. It would be Super if I could get this new HWID added for this driver. I'm assuming from the previous entry, that you HAVE the drivers, so I haven't included them with this post. Let me know if you need them.

I would have posted the DPBASE.log but I can't see that there is anything you really need in there. Assuming you arelady have this in beta, only the HWID needs to be added to the list. FWIW, the ahcix86.sys driver doesn't appear in my list in 9.01, so hopefully it's there with a later release.


These were the other instructions for adding the PNP driver. For Overflow, I'm sure this is "been there, done that". :-)

We now need to make modifications to the setup hive

Go start, run type regedit
Now, select HKEY_LOCAL_MACHINE right click and press File, Load Hive
Select I386/SETUPREG.HIV - name it whatever you want e.g. nvidia
Now open nvidia, CurrentControlSet001, services
Select services right click go create, new, key call it nvgts
Select nvgts right click go create, new, key call it Parameters
Sow select Parameters right click go create, new, key call it PnpInterface
Sow select PnpInterface right click go create, new, DWORD value
Replace New Value #1 with 5, right click 5, press modify and change Value Data to 1
Select nvidia and go file, unload hive - this saves the new SETUPREG.HIV

We now need to make modifications to the installation hive

open i386\HIVESYS.INF in a text editor
HKLM,"SYSTEM\CurrentControlSet\Services\nvgts","Group",0x00000002,"SCSI miniport"
save and exit
Remaining steps involve the $OEM$ folders: Create in the root of your installation source a folder called $OEM$, then inside of that a folder called $1 then inside of that one called Drivers, then another one called NVIDIA inside of Drivers in here place the sataraid and sata_ide folders that were inside the IDE folder of the extracted chipset drivers

Now you'll need to modify or create an WINNT.SIF mine looks as follows:
The important settings being OemPreinstall, UnattendedInstall, DriverSigningPolicy and OemPNPDriversPath



Just a little more info on this missing nforce driver. 9.01 certainly doesn't include this driver. If you're still having problems finding it, look in:


Bad me, I had to return the client's box and I hadn't run the hw_ids script on it, but I used another site which had the info in order to get my PE disk to run. I think there may be a few missing idents from an earlier entry in this thread so you might want to see if the list I have here has any you might not have added.

nvgts.sys = 100,,,,,,3_,4,1,,,1,4
nvrd32.sys = 100,,,,,,3_,4,1,,,1,4

PCI\VEN_10DE&DEV_0036 = "nvgts"
PCI\VEN_10DE&DEV_003E = "nvgts"
PCI\VEN_10DE&DEV_0054 = "nvgts"
PCI\VEN_10DE&DEV_0055 = "nvgts"
PCI\VEN_10DE&DEV_0266 = "nvgts"
PCI\VEN_10DE&DEV_0267 = "nvgts"
PCI\VEN_10DE&DEV_037E = "nvgts"
PCI\VEN_10DE&DEV_037F = "nvgts"
PCI\VEN_10DE&DEV_036F = "nvgts"
PCI\VEN_10DE&DEV_03F6 = "nvgts"
PCI\VEN_10DE&DEV_03F7 = "nvgts"
PCI\VEN_10DE&DEV_03E7 = "nvgts"
PCI\VEN_10DE&DEV_044C = "nvgts"
PCI\VEN_10DE&DEV_0558 = "nvgts"
PCI\VEN_10DE&DEV_0559 = "nvgts"
PCI\VEN_10DE&DEV_055A = "nvgts"
PCI\VEN_10DE&DEV_07F8 = "nvgts"
PCI\VEN_10DE&DEV_07F9 = "nvgts"
PCI\VEN_10DE&DEV_07FA = "nvgts"
PCI\VEN_10DE&DEV_07FB = "nvgts"
PCI\VEN_10DE&DEV_0AD9 = "nvgts"
PCI\VEN_10DE&DEV_0AD8 = "nvgts"
PCI\VEN_10DE&DEV_0ABD = "nvgts"
PCI\VEN_10DE&DEV_0ABC = "nvgts"
PCI\VEN_10DE&DEV_0BC4 = "nvgts"
PCI\VEN_10DE&DEV_0BC5 = "nvgts"
SCSI\NVIDIA__Raid_Disk________ = "nvrd32"
SCSI\__NVIDIA_______Raid_Disk = "nvrd32"
SCSI\NVIDIA__Raid_Disk_20_____ = "nvrd32"
SCSI\__NVIDIA____Raid_Disk_20 = "nvrd32"
*_NVRAIDBUS = "nvrd32"
*NVRAIDBUS = "nvrd32"
*NVRAID20 = "nvrd32"

nvgts = nvgts.sys,4
nvrd32 = nvrd32.sys,4

nvgts = "NVIDIA nForce Storage Controller"
nvrd32 = "NVIDIA RAID Driver"



(9 replies, posted in Software)

Is there a place to add a missing driver? I had a problem with a gateway using the NVidia 630/7100 combination this week and the current driverpacks didn't include the driver (nor did Vista SP1!)  I have the driver and the sif info. I just wanted to submit it so others can get the additions too.
Just let me know where to send them.


hot plug usb mouse and kbd would be nice with BartPE. I figured out (as did others) for hot plug USB mass storage device.

What about WZconfig to make dp WLAN drivers work? Is there a trick there?

I looked at your tutorials before I made a reply to you in this thread.

I've (personally) ALWAYS had a 'production grade' disk as well as a "beta" version. And since I don't RUN any of MY computers on these disks anyway, I can assure you that I wouldn't run some nightly on anyone else's PC. Let me be perfectly clear--my time is precious, and since I work on other folks computers all day, I rarely have time to do anything on MY computers. Of utmost importance is the ability to access a problem computer's hard drive using a another boot disk and as that stands right now, the UBCD/Driverpacks.Net (aka Bâshrat the Sneaky driverpacks:-)) the current disk I hav pretty much hits the mark. So, why, you might ask, would I be interested in testing?

I used to write code for a living and I know the value of a GOOD testing group. There are always folks who want to get an "alpha copy" of the code, just to check it out, but then provide no useful feedback. My feedback might be limited too. The way I see it, I used to have a REALLY NICE repair disk but was growing tired of updating the drivers on it, especially for those pesky INTEL storage matrix drivers, so I cracked open my build config and tried all the new code. And guess what, it works, but only sometimes.

Where I can help is documenting what works (or should) and what doesn't.

And, with the new config, I suspect I will spend the next month or two trimming down and merging in the plugins that I want/need and those that I could care less about. I certainly don't need four different defraggers.  And during that time, I will end up making a LOT of builds, and each one of those could be built with beta/nightly code if you are interested in my feedback.

In the "early days" the whole BartPE project seemed almost "cult-ish" in that only serious techies could understand how to make it work, or could really appreciate the usefulness of the end result. At some point, the project had some decent documentation written for it that made it understandable to the above-average-noob and that's when the "UBCD-like" copies exploded on the net. It seemed the project had hit the critical mass and the general public could all benefit from it. But it didn't really happen. Not sure why. I was almost expecting the better software companies to begin building the plugin inf code for their product and including a BartPE installer as part of their InstallShield installer config. How simple was that? But it never happened. Sometimes I think the original developers (perhaps not Bart himself) didn't want that level of success. I really don't know. But what I do think is that this turned into another one of those projects that starts out with a great idea but lands one step shy of mass acceptance and use. And it won't be the last project to do this, nor is it the first. I used to work in Digital/Compaq corporate research and I know all too well what happens with projects like this.

So where I'm going with this diatribe, is just that I really don't want this project to stall, get boring, or only be used by techies. Sometimes, all it takes is a little polish or some guide that paves the way to increased adoption of a project. And the more folks who can make use of this project, the better off they will be. Anyway, my offer to test is there.

So well put. Bâshrat the Sneaky. Gotta love it. Lol.

Wim, you are my hero as well.

On a different note, perhaps someone could create an "RC" thread and peg it to the top of the list so more of us willing to help test could find it.

And on a yet another note, I was so joyful the other day when I booted a UCBD4Win variant, with Mass Storage, WLAN and LAN driver packs, from a USB stick, on my server and it worked beautfilly. Made my week.


I finally had a chance to dig deeper into this so I could completely understand your reply. For anyone reading this thread, I hope you will finally understand it as I do now.

You see, I started with BartPE and loved the idea behind the whole project. And UBCD came out and was the leader in the drivers "collection" plugin because it was stupid for the odd one of us to add "dell wireless", or "HP-servers" or what have you. The UBCD_drivers_full was the bomb. It just didn't get updated after a while. It also required Autobuild, which was cool in-and-of-itself, but I believe was part of the reason why I was confused on how to use the current DriverPacks with a stock BartPE build.

So what was confusing me, was how DriverPacks.Net and UBCD were connected.

UBCD4Win clearly took off. They weren't just going to stop at drivers and they wanted to add everything into their "disk" including the kitchen sink. This, for some is way-cool, but for us Tech Repair folks, just having a customizable builder, with EVERY MASS STORAGE driver, and possibly every wireless and LAN driver is a small step short of heaven.

What I found, is roughly the same that the UBCD4Win folks found, and that's some nasty interactions between either the BartPE builder and the MS drivers, or something that's way over my head. And that is, adding EVERY driverpacks.net driver pack to your BartPE build, whether using a "clean 3.10a" or the 3.22 UBCD4Win build, you just can't get it to fully work properly. My issue is I can't get the mouse to load, and sometimes the shell won't load either. The UBCD4Win folks suggest using only the MassStorage driverpack, but I've found good success using the WLAN and LAN driver packs too. So, I know the problem is somewhere in the Video, CPU or Chipset driverpacks. The Video one is obvious on what it can bring to the experience, the other two less so.

But, if you're reading this thread. My suggestion is to start with a clean 3.22 build of UBCD4Win and then add additional driverpacks.net drivers incrementally. The way you do that is by copying the .7z file into the same directory (the UBCD4Win\plugin) where the BASE driverpack is located, and then re-run the BASE plugin using CONFIG Plugin. Then, to customize your bootdisk, just add/remove plugins that are there from the UBCD4Win installation.

Still confusing to me is the "Bâshrat the Sneaky DriverPacks". I still really don't know what they are, but I'm assuming they are the Driverpacks.net drivers, only with an old name. The Bâshrat the Sneaky driverpacks are what the UBCD4Win folks refer to and they don't really mention the Driverpacks.net plugin unless you do a log of digging.

As for the 809RC1, I never found much success in that one because I was trying to include the whole set of driverpacks (other than sound) and ran into the missing mouse problem. I think I've since tracked it down to a USB mouse problem, while PS/2 may work. As for an 8110RC1 image, I would be happy to try that. It's just important for testers to understand the best/intended way to use it. If you start with the UBCD4Win collection and then just add driverpacks, you probably aren't testing much of the 8.x slipstreaming features, if any. Since I practically owe my business to driverpacks, I am more than happy to test what you have available in order to keep this effort alive.


Now I'm feeling MUCH better!

Last question, since I bet anyone reading this thread (now or later) would want to know...

"If we are mostly interested in BartPE building, should we use the UBCD4win Mass Storage plugin, or just use UBCD4Win if we're already using UBCD4Win for all the other driver packs?"

And yes, of course, I'd be happy to test your RC. I need to find the pointer to that download so I can help join the effort.


So, forgive me for asking, but I guess the general answer is for the BartPE world, you can use DriverPacks for MassStorage (which, mind you, if you do what I do for a living, is  a HUGE win to have others helping out with this!) and then, for the other stuff, use UBCD4Win and their driverpacks (not to be confused with driverpacks.net, I gather), therefore NOT enabling the mass storage driver packs from UBCD4Win during the BartPE plugin controls.

That sound about right?

Time to check out the UBCD4Win group again, as I was under the impression that they weren't updating their driver packs any more.

And, if you're up to it, if UBCD IS updating their mass storage pack, why wouldn't you guys want to somehow work together so you could use a single .7z file and repurpose some of your efforts? It's almost sounding like if UBCD4Win is still updating, I might as well just use UBCD or is there still some added value with the the driverpacks.net driver packages?

I have to believe I'm missing something. Perhaps you don't work completely with BartPE (yet) but how else would you use the driver packs now, if you wanted to use them? Is there really life after BartPE (or PE Builder) :-)?


Hello there. I'm new to your forums--I just found your site. Not sure why it took so long!

I've been using BartPE for ages and also the UBCD plugins. I believe I saw something else in the forums about UBCD and driverpacks, but not within the context of BartPE. Hence, I've posted this reply. Please move this if in the wrong place.

The "Administrator's" tutorials were helpful, but still leave a few unanswered questions. Perhaps these questions are similar to what others might ask:

1) I use BartPE and UBCD plugins to provide driver support for many varieties of hardware. I would really like to understand how to "cleanup" my plugins configuration so I am using a consistent method to load all the drivers I can. Right now, I run all of the UBCD and I even have a "raid" plug-in, but it's not active. I don't think it ever worked. Likewise, I think I have other "driver" plugins in order to add things like Dell wireless drivers, etc. How should I configure PEBuilder to use your drivers and should I continue with the UBCD plugins?

2) I ran the Base program and chose the BartPE configuration as described in your tutorial. It takes the mass storage drivers as indicated, but it doesn't do anything with the other driver packs. For these, is the proper method to slipstream them into my XP/2003 distribution instead of having them get "loaded on the fly" as the UBCD drivers do?

3) Is there any chance I could just stick an updated DriverPacks 7Z file and place it into the UBCD plugin folder and it would pick up the new drivers?

Thanks in advance for your help on these. I would be very happy to contribute to your effort as well as I spend a fair amount of time updating the 7z UBCD files to include the latest Intel drivers. We are mostly a Dell shop but have clients who rent a lot of various other brands and we spend too much time trying to keep it all up to date. Having a single, coherent driver loading system with PEBbuilder would be a dream come true.

If there is an easy way I could post my plug-in configuration to make it easier to explain my environment, I would be happy to do so.