got rid of your dup posts for ya jaak
Did you get this to work Mike?
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
got rid of your dup posts for ya jaak
Did you get this to work Mike?
can you ask a specific question?
when your done with hfslip run base... seems to be the short answer.
adding driverpacks useing DPs_Base.exe is the last step... always.
Welcome to driverpacks.net
Let us know how this works out for you... this is not a supported setup but im intrigued...
that is an issue because we intercept the call to setup.exe and then recall the original in method 2
see \i386\PRESETUP.CMD and i think you will discover your issue...
it is very possable that you dont need all the packs (Wlan is a path monster for example)
and i would hate to think you were pushing an install wireless.
so you amy be able to switch back to method one and make it work if you must have all the packs consider KTD and then you could jsut check device manager for devices that didnt make the txtmodepnp path cut (ktd / gui-pnp does not have this limit which is why m2 is prefered)
We are all working on different pieces that will all come together. The things that get tested and prove effective will be in a final release.
Not all of our test packs make it. most do. We can release (main team members) at any time we wish. We choose not to release garbage and look foolish if we can help it. we don't always win that battle due to shortages of active testers and the broad base of hardware they bring to the table. You can take advantage of the fact that Muiz has pronounced it a final. that implies he is done with his peice of the pie.
Download his test version to see if it is broken by testing it. Once you realize its not broken add your fix and put it up as test pack 71122
and can be the next release. i assure you no ones work will be abandoned if it is needed and effective. I had that happen to me when i signed on here and before it was open source.
I can add your fix right now if i want... lets proceed slowly and with due caution.
We support 2000 XP and 2003 x86 32bit OS's only
check this out it is a detailed explanation of how to integrate drivers to XP
http://unattended.msfn.org/unattended.xp/view/web/36/
We do replace outdated drivers in the I386 folder Jaak has informed you well read the mass storage INF file (in the pack)
please read the other posts in this area then ask more specific questions
Welcome to driverpacks.net
tary this one for sure how do you use driverpacks
Since you havent told us why or where you are failing we are unable to ask inteligent questions.
what is your source OS? can you post your DPs_BASE.log?
how far into the install do you make it?
what software are you useing to prepare your install disk? driverpacks base? anything else?
you didnt tell us what error? specifically (verbatim) and when it shows up in the process.
did you read the info on the page i refered you to? (my guess is no)
Welcome to DriverPacks.net
use the search feature of explorer (advanced) to search the i386 folder for *.inf files that contain your HWID.
also search DRVINDEX.INF and layout.inf for rage
DriverPacks.net
Help file for the DriverPacks Plugin for BartPE
Platform:
Currently supporting; x86 32 bit versions of Microsoft Windows XP and 2003
Mass Storage Only for now - more to follow!
Section One:
Older versions of UBCD4Win previous to 3.05 install directions
Disable or remove any existing Mass Storage Drivers.
UBCD4Win came with many drivers and to avoid conflicts these needed to be disabled.
To disable the included MS drivers...
create a new folder in the UBCD4Win folder called DISABLED then cut and paste
the <UBCD4Win>\drivers\SCSIAdapter folder to the <UBCD4Win>\DISABLED folder.
You can also simply delete this folder if you wish but this would not allow you to use them later if needed.
Newer versions of UBCD4Win Include Bashrat the Sneaky's (Bâshrat the Sneaky) DriverPacks
All versions of BartPE
Extract / install the DriverPacks Base program to a folder that IS NOT in your plugin folder - IE C:\DPsBase\
We will allow the Base program to create our plugin folders because it is critical to proper operation of the MassStorage plugin and also future DriverPacks like LAN and Graphics.
Download the latest Mass Storage DriverPack directly to your DriverPacks folder. IE C:\DPsBase\DriverPacks\
Don't get the other packs right now since they are not (yet) supported and don't need to take up extra space in your plugin.
you dont need to unzip or do anything else to the packs manually.
Run c:\DPsBase\DPs_BASE.exe and select your language on the 'Start' page.
Click the button with the > sign on it (or click on settings) to display the 'Settings' page followed by the 'Location' page
On the location page (see fig1) Select BartPE and "Browse" to your Plugin folder.
note - If you select a valid BartPE Plugin folder the OS: field will change from 'N/A' to 'bartpe'
note - If you do not select a valid location you will not be shown the rest of the settings pages.
Figure 1
Click on DriverPacksâ„¢ in the navigation pane or click on the next button '>' (see fig2)
If the MassStorage DriverPack exists in the C:\DPsBase\DriverPacks folder then MassStorage text mode will automaticaly be selected.
Figure 2
Click on 'Slipstream!'
That's it your done creating your Mass Storage plugin.
------------------------------------------------------------------------------------------------------
Afterwards you will have the following new folder under \plugins... ' \plugin\DriverPacks.net\BASE'
DO NOT CHANGE THE NAME OF THIS FOLDER!!!
"plugin\DriverPacks.net\BASE" is hard-coded into the executable and must not be altered in any way.
Doing so will create problems upgrading to a new MassStorage Pack or adding new packs when they are supported (like LAN)
Run UBCD4WINBUILDER.EXE or PEBuilder.exe and open the "plugins" page.
there should be new plugins (fig3)
"# DriverPacks.net - BASE - Press <CONFIG> to enable drivers or reset DriverPacks plugins"
- this should be set to 'NO' because it is only here to 'configure' plugins it is not part of the build.
"# DriverPacks.net - MassStorage"
- this should be set to yes to enable the MassStorage Plugin and enable the drivers for your build.
Figure 3
If "# DriverPacks.net - MassStorage" is not there or is out of date then select
"# DriverPack - Press <CONFIG> to enable drivers" & press the CONFIG button.
This will setup the base.ini file to your local directory and run the driverpacks base which will generate the mass storage drivers plugin.
You MUST press REFRESH before you will see the new plugin listed in pebuilder.
-------------------------------------------------------------------------------------
Help file updated by
Overflow - 2007-11-17
OverFlow - Jeff Herre, code for mass storage plugin for driverpacks
Many thanks to Bâshrat the Sneaky, hilander, cdob, and the ubcd4win team: i could not have done it without you guys
Hello and welcome to DriverPacks.net.
i think you will find what you are looking for from our freinds at msfn
http://unattended.msfn.org/unattended.xp/view/web/1/
a generic match for this card is in the packs
PCI\VEN_10DE&DEV_042B matches with \D\G\N\1 in the graphics pack.
frequently manufacturers will mod thier chips this is particularly true of laptops in general and large providers like dell.
if you can provide alink to the driver that is correct for your system we will look at it and see if it can be included.
hello and welcome to Driverpacks.net
we at te very least need your HWID's
http://users.pandora.be/jtdoom/sav_HWID.exe here is a tool for that
It is very common for dell to modify their chipsets sometimes it causes issues with reference drivers.
you provided the vehicle... we just did the chinese fire drill.
ask and ye shall recieve
BartPE [beta] help file http://users.pandora.be/jtdoom/basetute … lpFile.htm
that was kind of the point of putting it together...
surprized it took almost a year for our first request for us to provide a help file / tutorial.
guess it is almost self explanitory.
Text mode IS mass storage support for bartPE
and im off most of next week perhaps soon is approaching...
as jaak said dont unzip your packs they are ready to go as is. (that is in the tutorial).
The base is meant to lead you through the steps and is intuitive.
Since you had no mass storage pack available and had the wrong plugin folder specified for location several things would have led you to the finish line. Since the wrong folder was given you would have been immediately take to the UpdateChecker screen which would have indicated you had no local mass storage pack and that a newer version was on the server. (it tried to tell you the pack was not there). If you had the correct folder specified it would have shown mass storage text as greyed out (not available - no really, not available -- hey buddy really it's not here!) When the correct location is given for bartpe the OS= will change from N/A to OS= bartpe (a hint is given in the description box "BartPE: the \plugin directory to which driverpacks will be exported").
if you have the pack available and if you point to the bartpe\plugin\ folder and hit the slipstream button in base
you should then find two new plugins in pebuilder under plugins - base and mass.
Base should be disabled
and Mass should be enabled.
DriverPacks plugin is included with UBCD4win (BartPE on steroids) http://www.ubcd4win.com/downloads.htm
it needs to be configured from <<plugins>> in pebuilder before you build your ISO. that might be easier for you.
we can certaily tell if it can decide correctly from the api log
all things are possable...
we are working on a fix right now in the testing forum, lets see where that goes first.
Jaak tried that already he called them sfx mini packs.
not really the way we would prefer to go.
it is a problem we think we're close to nailing down.
try leaving it in both and let pnp decide see how that shakes out.
sys prepers can deal with a couple of dupes ;-)
Hello hefebia
Welcome to DriverPacks.net
Is the MassStorage plugin enabled when you check the plugins from PEBuilder?
(if only the base is present then you need to hit config button and then the refresh button.)
The plugin comes compressed to save space and needs to be configured from pebuilder to add and enable it.
the HWID you specified should be covered by \D\M\P\7 (location in the pack) ULSATA2.INF
; Copyright (C) 1998-2003 Promise Technology,Inc
[Version]
Signature="$Chicago$"
Class=SCSIAdapter
ClassGuid={4D36E97B-E325-11CE-BFC1-08002BE10318}
Provider=%PROMISE%
CatalogFile=ulsata2.cat
DriverVer=06/30/2005, 1.00.0.33
please also post your base version as well as the pack version when asking about BartPE
and... if the plugin was enabled already
lets see your \plugin\DriverPacks.net\MassStorage.inf
did your build have errors?
did this hwid show up in your txtsetup when you use the plugin?
please wait to declare this a "bug" till we do some checking.
we have yet to find a single bug in the year this has been out.
"Promise SATA300 TX 4302 not recognized in BartPE"
would be better since we report bugs elsewhere.
Welcome to DriverPacks.net
the only stupid question, is the one that is never asked....
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.111 seconds, 6 queries executed ]