[Spike]

I'm trying to boot my HP Pavillion dv7 with a BartPE boot disc. BartPE loads for a minute, then as soon as Starting Windows appears, I get a blue screen with various error numbers, the first being 0x0000007B. I found by searches that there are two solutions to this, by going into the BIOS and changing the Hard Disc setting to Lagacy, and alternatively by adding the storage drivers to the BartPE boot disc.

I've searched through every setting in the BIOS, and there's nowhere where I can change any settings for the hard disc except for boot order. The BIOS is InsydeH20 rev. 3.5 .

So I've been trying to get the driver onto the boot disc. It comes down from HP as sp48922.exe . Bart's help file says to create a new folder in the drivers>SCSIAdapter folder which I do, then double click on sp48922.exe and tell it my new folder as the destination. When it's done, there's 12 files in the new folder but I don't think they're the driver, one of them is setup.exe . So I double click on that and it clearly installs the drivers into the computer, but it didn't ask for a destination so my new folder still hasn't got the drivers in it.

If someone can tell me what I'm doing wrong, either with changing the hard drive to Legacy, or getting the new drivers onto the boot disc, I'd be most grateful. Thanks.

[rdsok]

Check HP's website for a driver set usually refered as a floppy set or floppy installation or similar... it must be made for XP... these would be the files to include in the driver folder

The alternate method is to update the driver packs

[Spike]

Thanks for your reply - I'll get working on that.

As a general point, is it best if the BartPE boot disc is created on the computer you're planning to use it on? Does it then automatically collect the drivers it needs to start that particular computer, from the host computer? I was hoping BartPE would be a tool I could use to start any computer, but it doesn't seem to work like that.

I'm not sure what you mean by "The alternate method is to update the driver packs". Ho hum, computers, eh?

[rdsok]

First just a little background...

Don't let the length of this post discourage you... There are three different types of drivers supported so I've got a lot to cover in this post... Mass Storage for the hard drive controllers, LAN for wired networking and WLAN for wireless networking. In addition there are two methods for adding drivers of which you will need to select the one method you are going to use for each type of driver you use, add or update to.


UBCD4Win can use two seperate methods to add drivers to the build. You must choose only one of those methods to avoid ending up with conflicting drivers... ie having the drivers from one method overwriting the other. I will cover both methods and do it in a manner to support both so, if you choose to, you can switch back and forth between them if you wish. If you only want to use one method, that is ok as well, you will, in that case, simply delete the method you are not going to use.


The most basic method is usually refered to as adding text mode drivers. These are probably the easiest to add but they are also the most limited since you can only add a few hundred at best before they start to cause memory errors on boot up. Text mode drivers will contain an INF file along with other files that are needed for the driver. They are not executible or zipped up files that require extracting or installing from within Windows itself like a lot of companies are starting to do because they find them simpler to distrbute them in that form. Typical file extentions seen with the INF files are SYS, CAT, OEM and/or DLL files but others may also be included depending on the hardware driver requirements.

The better method, because it can support a larger number of drivers, is done with a plugin instead. UBCD4Win includes this type already but because new hardware is always coming out... They may need updated from time to time. The drivers we have included are the BTS Driverpacks.net drivers.

First... Create a new folder in your UBCD4Win folder called DISABLED. If you installed UBCD4Win in the default directory... this one would then be C:\UBCD4Win\DISABLED .... This is the folder where you can move the drivers you aren't planning on using during a build which will allow you to switch back and forth if wanted.

Using basic text mode drivers

Next you would create ( if they don't already exist ) two folders in the \UBCD4Win\drivers folder ... make one named Net and one named SCSIAdapter... like...

C:\UBCD4Win\drivers\Net
C:\UBCD4Win\drivers\SCSIAdapter

The Net folder is for network drivers for both LAN and WLAN adapters. The SCSIAdapter folder is for the mass storage drivers needed to access the hard drive controllers. To keep things organised... you would then create folders within these, usually named for the model name of your driver your system needs. Within that folder is where you place your text mode drivers that your device needs. Let's use a Realtek 8139d network card driver as one example just to give you the idea.

Create a new folder called Realtek and then in that, one called 8139d... so the path looks like C:\UBCD4Win\drivers\Net\Realtek\8139d .... then place all of the driver files for the network card into the 8139d folder. Repeat that process for all the other mass storage or network drivers you need.

Now... remember I mentioned that you can't combine both methods and that UBCD4Win already includes the Driverpacks.net drivers. This means you need to disable the Driverpacks.net drivers IF you are going to use the text mode driver method instead. This is simply done by moving the Driverpacks.net folder that is found in the plugins folder into the folder you created earlier... the \UBCD4Win\DISABLED folder. In Windows Explorer navigate to C:\UBCD4Win\plugins... on the right window highlight the Driverpacks.net driver folder, right click your mouse and select Cut from the popup menu. Now navigate to the C:\UBCD4Win\DISABLED folder and on the right window, right click your mouse and select Paste from the popup menu. That, if done properly, moves the Driverpacks.net folder to the DISABLED folder.

You can now rebuild and burn a new disk.

Switching from basic text mode drivers and/or updating the Driverpacks.net drivers

Now lets go in the other direction in case you are wanting to just update the Driverpacks.net drivers so you are using their latest version of drivers ( which support more hardware than when UBCD4Win was released ) or are switching from using text mode drivers as mentioned above back to the Driverpacks.net plugin type of drivers.

First you need to move the text mode drivers, or the older version of Driverpacks.net drivers to the DISABLED folder like mentioned before. To move the text mode drivers found in the drivers folder... simply cut/paste the Net and SCSIAdapter folders from the drivers folder to the DISABLED folder. If you are just updating the Driverpacks.net drivers... cut and paste the current set you have to the DISABLED folder just like I described above.

NOTE... If you don't plan to switch back and forth between the different types of drivers you can choose to simply delete the folders I've mentioned instead of moving them to the DISABLED folder... Doing this isn't as flexible but it doesn't hurt anything either.

Next... to update to the latest Driverpacks.net drivers... follow their instructions found on their website here http://driverpacks.n...se-bartpe-guide ... Please note that those instructions only talk about Mass Storage drivers... They now also support LAN ( wired network drivers ) as well as WLAN ( wireless network drivers ). The WLAN drivers are normally left disabled since they take up a lot of extra space that many don't require since they are usually using the more reliable wired network drivers instead...

After updating or switching to the Driverpacks.net drivers... you can then rebuild and create a new boot disk.