You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
cdob belives that if the via is in base (non raid) mode that it is supported natively by XP as it emulates IDE.
much the same way as some of the ICH drivers will
and that a textmode driver would not be required unless RAID mode was selected in bios.
thus we could remove references to &CC_0101 from the list of supported via HWIDS in the mass storage INI.
PS we don't technicaly support RIS
so there may not be a "solution" available...
i thought it was your intention to add single dirvers...
IE a drive is moved to a new machine and needs the driver changed...
you are going to go down in flames on many of these drivers if you try to add them together.
you might be having issues with either windos file protection or with a bad download of driverpacks base
well..
your part of of our team now sir - the tutorial is now better
Go.......... Team!!!!
did you use a clean folder - make sure setup.exe does not exist. only setup.ex_
Welcome to DriverPacks alper60!
We are always glad to help people like you who are polite, informed and provide good details.
Stick around and we will make english your second language...
We're glad your here. Thank you for joining!
I am updateing the first post now -
Helmi has made me realize that with DVD's being standard equiptment now that perhaps space is not as much of a concern as time.
well i have had lots of luck with UBCD4win if you wish to start over from scratch i highly recomend it over a vanilla bartpe
there is a donate button in jacks signature... http://driverpacks.net/DriverPacks/donate.php
additionaly donors gain access to the testing forum and get access to the latest test packs and get to read about whats next.
EEguru I have added you to the Donor usergroup you may now view and respond in the testing forum...
base is not a plugin - it is the plugin creator (configure) - and will always be disabled - that is normal
as long as mass is enabled and your build reports no errors then it should be working normaly.
add devcon to your PE disk and make sure the HWID you gave me is correct (you said you pulled it from a different machine)
we have seen cases in the past where different firmware versions reported different HWIDs
thread moved to proper forum.
Jeff
if you enable QSC (with my RC2 version that corrects the /D/D bug) it won't take that long in the future 
then it will only have to cab the "new" pack instead of having to CAB them all...
On my machine I can cab all the primary ten packs (with an empty QSC folder - or QSC off) in about an hour.
Perhaps you should temporarily disable "on access scanning" for your virus scanner.
on access virus scanning would certainly kill your time...
Each file would otherwise be scanned multiple times
Once when it is extracted to the temp folder again whe it is cabbed to QSC and a third time when copied to the $OEM$\$1\D\ folder.
I disable on access scanning for my DriverPacks folders during M1 for just that reason...
so your four hour cabbing was probably more like 1 hour cabbing and three hours virus scanning each file three or more times.
Yes... as long as the fully extracted D\ folder is a subfolder of the DPInst files location
the ONLY reason to use M1 to cab compress them is to save space.
So following through with your idea...
base would not be required at all
just extract them and burn to cd or dvd and it will work just the same.
I did not realize makecab would run faster if i disabled my hyperthreading? (i have a 2.8HT myself)
it makes sense now that i think about it...
that line should read
"If all went well, then build your Windows source into an ISO file
you can use programs like (nLite or RyanVM Integrator) to create your ISO image"
thanks for your hard work, excellent idea, and the quiet / silent switch input.
you can also use dpinst.exe /s comand line switch instead of the xml entry
thanks for the correction helmi i updated both posts with the new info and corrected my link in the other post.
This LSI controler is currently supported by DP_MassStorage_wnt5_x86-32_8021 with the drivers in the \D\M\L1 folder.
that driver contains the HWID PCI\VEN_8086&DEV_27C3&SUBSYS_348F8086
which is a nearly perfect match for that HWID
if you have manually added any drivers to your BartPE build please remove them and try again
R U useing UBCD4win? or just BartPE?
is the #Driverpacks Mass Storage plugin enabled when you check the plugins in PEBuilder?
as far as i can see this should be working...
Perhaps CDOB will drop in here and have yet another moment of brilliance.
I just tested this with an M1 source
1. Create a DPInst.xml file with the following code...
<?xml version="1.0" ?>
<dpinst>
<search>
<subDirectory>D</subDirectory>
</search>
<scanHardware/>
<legacyMode/>
<promptIfDriverIsNotBetter/>
</dpinst>2. Copy the newly created DPInst.xml to the \$OEM$\$1 folder of your m1 source
3. Copy DPInst.exe to the \$OEM$\$1 folder of your m1 source
4. run DPInst.exe
optional
create a .CMD file with the following line
DPInst.exe /c
/c will enable logging in the command window
/s will enable silent mode (no GUI)
list of all command line switches
(obviously you could use - DPInst.exe /c /s > %SystemDrive%\DPInst.log -)
I just updated the "Can a Drivers Only CD be created with DriverPacks?" thread with my un-bloated version. (158k)
Thread--> http://forum.driverpacks.net/viewtopic. … 806#p17806
Files--> DPInst.exe and above XML only--> http://3rdpartydriverpacks.thesneaky.co … /DPInst.7z
i found some of the info here - apparently I assumed correctly
http://msdn2.microsoft.com/en-us/library/ms790308.aspx
http://msdn2.microsoft.com/en-us/library/ms790806.aspx
below is copied from the above link
Windows Driver Kit: Device Installation
Driver Package Installer (DPInst)
Driver Package Installer (DPInst) version 2.1 is a component of Driver Install Frameworks (DIFx) version 2.1 that simplifies and customizes the installation of driver packages for devices that are not yet installed in a computer (commonly known as a software-first installation). DPInst also automatically updates the drivers for any installed devices that are supported by the newly installed driver packages.
By using DPInst, you can:
Enhance the user experience of a driver package by eliminating most of the manual steps that would otherwise be required to install driver packages. When a user runs DPInst, a wizard notifies the user of the installation progress and provides an optional end-user license agreement (EULA) page that gives the user the option to cancel installation. For more information about the wizard pages, see DPInst User Experience and Installing and Uninstalling Driver Packages.
Avoid writing a custom installation program to install driver packages and update the installed drivers for supported devices. You do not have to change your driver packages to use DPInst. You only need to create an installation package that includes DPInst and one or more driver packages. For more information about creating this type of installation package, see Creating a DPInst Installation Package.
it would seem that your program simply extracts the driverpacks and launches the MS program. 700K seems huge for that?
Are we to assume this is to be used after a system was installed without DriverPacks slipstreamed?
If so, does your program automatically install drivers for "unknown devices" in device manager? (I assume so, but it doesn't say)
did you read this post http://forum.driverpacks.net/viewtopic.php?id=2264 ?
the driverpacks cab compressed take up 500MB instead of the 1.5GB they consume when extracted,
or does your program also cab them? if it doesn't perhaps your program can recomend createing a M1 source as an option.
saveing a gig of space makes the difference of being able to fit on a CD or not.
Even if you are useing a dvd or thumb drive who couldn't use the extra space...
Could you update your first post so that it is clear what it does (or doesn't) and that the packs must be in 'Your' programs subfolder?
We have quite a list of LSI drivers in the packs...
http://driverpacks.net/DriverPacks/devices.php?pag=m
we need the specific HWID of the LSI in your machine to be of assistance.
Hello,
Thanks for being here! Have you used the Driverpacks?
You will probably find that you do not have any problems with drivers if you do...
That is the reason we're here.
We support installs slipstreamed with our driverpacks.
We do not provide general installation support. For that type of service you will need to contact the vendor.
[url]http://www.csd.toshiba.com/cgi-bin/tais … p?]Toshiba Tech Support[/url]
Have a great day!
sorry we don't accept drivers that do not come directly from OEM sources
does the sound work?
I would like to reinforce this...
in IM only you benefit.
in forum all benefit...
some of us publish our IM contact info in our profiles feel free to add the ones you find.
http://forum.driverpacks.net/userlist.p … rch=Submit
others may provide thiers if you send a forum email.
it is unlikely that they will put them here if they are not in thier profile info.
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.221 seconds, 5 queries executed ]