Search options (Page 5 of 10)

The onboard IDE controller is part of chipset and use a fast connection to north bridge
The SATA is connected to PCI bus. PCI Bus transfer speed does limit SATA card.
The IDE adapter may result faster transfer speed as a PCI SATA card.

I doubt hard disk as true speed limit.

Link goes to a non public Testing Team section.

Thanks for reminding, OverFlow.

Added to LAN ini file

[I2]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "Dell2_OEM"
ms_1_sysfile 	= "e1000325.sys"
ms_1_exc_skipIfOS="wxp,w2k3"

[I3]
; BartPE Code
ms_count	 	= 1
ms_1_tag 	= "Dell3_OEM"
ms_1_sysfile 	= "e1k5132.sys"
ms_1_exc_skipIfOS="wxp,w2k3"

Good find.

Compare INF Manufacturer Section
http://msdn.microsoft.com/en-us/library … S.85).aspx

Which Wndows do you use? Do you use XP or 2003 files?

In addition, inf editing is required sometimes. Compare http://forum.driverpacks.net/viewtopic.php?id=4530

A new approach: create a batch plugin\DriverPacks.net\EditInf.cmd

@echo off
setlocal EnableExtensions
cd /d %~dp0

rem PE mode: edit *.inf files: 
rem comment lines with CopyFiles, DelFiles, UpdateInis, DelDirs, RenFiles, Reboot
rem
rem created by cdob
rem approach based on 911cd experience http://www.911cd.net/

rem sed.exe http://sourceforge.net/projects/unxutils/

for %%a in (LAN\w2k3\*.inf LAN\wnt5\*.inf LAN\wxp\*.inf WLAN\w2k3\*.inf WLAN\wnt5\*.inf WLAN\wxp\*.inf) do (
    echo %%a
    type "%%a" | sed -e "s/^CopyFiles/;CpyFiles/" | sed -e "s/^DelFiles/;DlFiles/" | sed -e "s/^UpdateInis/;UdateInis/" | sed -e "s/^DelDirs/;DlDirs/" | sed -e "s/^RenFiles/;RnFiles/" | sed -e "s/^DelFiles/;DlFiles/" | sed -e "s/^Reboot/;Rboot/" > "%%a.new"

    if exist "%%a.new" (
      if exist "%%~na.bak" del "%%~na.bak" 
      ren "%%a" "%%~na.bak" 
      ren "%%a.new" "%%~nxa" 
    )
)

Add sed.exe and run the batch.

That's the SATA board BIOS. Card itself is bootable.

However this is a PCI 2.2 card. Does you system provide PCI 2.2 slots?

Does system BIOS list a SCSI boot option?
This should run SATA card. Try this SCSI boot.

Use InfCacheBuild http://forum.driverpacks.net/viewtopic.php?id=4530

Congratulations, clever approach.

Just wondering: if driver signing policy is disabled and RIS driver is newer than normal drivers:
which driver does PNP load?

Yes, I think so.
ef creates BartPE using 2003 server files.
Hence finally RIS drivers and regular driver are included.

Thanks, I like this. Should work.
@ef please verify this at real hardware.

There is RIS driver included: b06nd.inf, B06ND51X.SY_

And a 2003 driver bxvbd.inf.

Both driver refers a PCI\VEN_14E4&DEV_164C.
This may cause a conflict.

Try edit lan.inf

[SourceDisksFiles.3790]
;w2k3\BXDIAG.INF=20,,1
;w2k3\BXDIAGX.SYS=4,,1
;w2k3\BXND.INF=20,,1
;w2k3\BXND50X.SYS=4,,1
;w2k3\BXND52X.SYS=4,,1
;w2k3\BXNDCOX.DLL=2,,1
;w2k3\BXOIS.INF=20,,1
;w2k3\BXOIS.SYS=4,,1
;w2k3\BXVBD.INF=20,,1
;w2k3\BXVBDX.SYS=4,,1
;w2k3\EVBD.INF=20,,1
;w2k3\EVBDX.SYS=4,,1
;w2k3\WDFCOINSTALLER01007.DLL=2,,1
;w2k3\BNXCDX.SYS=4,,1
;w2k3\VBDINSTALLER.DLL=2,,1

Short simple answer: create a ISO image always.

This is possible, but does require some work.
A prebuild solution is simplier to find: a linux live cd.

No, sound won't work. Plain BartPE dosn't support sound requirements.
Adding a sound driver alone won't enable sound playback.

As for a starter:
As indicated some keywords already http://www.911cd.net/forums//index.php? … p;p=163592
Add a PNP plugin, e.g. part of XPE plugin.
Add a sound plugin, e.g. part of XPE plugin.
Add HWPNP too.
Add HDAudio bus driver, realtek sound driver and vga drivers too.
And process InfCacheBuild at build time to adjust *.inf files.
Boot BartPE. Run HWPNP to load sound, vga drivers.

Add media player classic. Play a sound file locally.

Next add Youtube requirements.

Above are keywords to search.
If there are specific questions search at 911cd.net or ask at 911cd.net.

Use post processing autobuild routine to sort menu items. And to edit *.inf files, this avoid prompt to insert the Windows XP CD.
Read let Builder create a ISO image. You may configure autobuild plugin not to create ISO file itself.

Hundreds of posts are false. Plain BartPE is compatible with a plain XP SP3.

There is a small static list. However most files are defined at layout.inf.
Required files/drivers are read from layout.inf. E.g. PEBuilder does add a file xpsp3res.dll.

In that case slipstreaming drivers didn't update layout.inf.
Yes, PEBuilder dosn't process txtsetup.sif.
Layout.inf file list dosn't match txtsetup.sif file list. The source files are kind of corrupt.
Broken input gives a broken output. This result to a corrupted BartPE. 

Slipstreaming a SP if fine.

@Doman
Try PNPInterface
http://forum.driverpacks.net/viewtopic. … 325#p30325

@msturtz
Does your BartPE contain files e1k5132.inf and

You don't need a driver for a hard disk.
Windows provides driver for the hard disk, this includes the SP2504.

Contrary you may need a driver for the MassStorage controller.

http://h10025.www1.hp.com/ewfrf/wc/docu … =c00864946
That's a ICH7-R MassStorage controller.

There may be a driver conflict: remove KR10N, mraid35x, megasr and MegaINTL.