You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 203 of 213)
Topics by OverFlow User defined search
Posts found [ 5,051 to 5,075 of 5,307 ]
he copied all of http://dlsvr03.asus.com/pub/ASUS/mb/soc … Q1Camr.zip
to \D\S\SM\A\3\
and added something like
[SM-A-3]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 1
exc_1_tagFile1 = "%SystemRoot%\system32\drivers\smwdm.sys"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\S\SM\A\3\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = ""%DPSROOT%\D\S\SM\A\3\Setup.exe" /s /f1"%DPSROOT%\D\S\SM\A\3\Setup.iss""
this adds 24 meg to the driverpack BTW
for starters stop hijacking this thread
Thanks for asking and have a great day.
dolivas wrote:@overflow are you sure this line is correct? should the quote be there after the Setup.exe" I have tried two loads now and both have failed with a DPFinsher error. Here is that last bit of information I am seeing in the DPFinsher log before it fails. Let me know what you think and I will try another load.
exc_1_command1 = "%DPSROOT%\D\S\S\U\Setup.exe" /s /f1"%DPSROOT%\D\S\S\U\Setup.iss"
hmmm try
exc_1_command1 = ""%DPSROOT%\D\S\S\U\Setup.exe" /s /f1"%DPSROOT%\D\S\S\U\Setup.iss""
or
exc_1_command1 = ""%DPSROOT%\D\S\S\U\Setup.exe" /s /f1%DPSROOT%\D\S\S\U\Setup.iss"
or
exc_1_command1 = ""%DPSROOT%\D\S\S\U\Setup.exe" /s"
edit--------------------------------------------------------------------------------------------------------------------------
Doh!!!!!!!
i posted the wrong path drat..... :-( sorry guess i was tired....
see below
""%DPSROOT%\D\S\SM\A\3\Setup.exe" /s /f1"%DPSROOT%\D\S\SM\A\3\Setup.iss""
realhyg wrote:For example?ECS 845GV-M2 ALC655 with HWID “PCI\VEN_8086&DEV_24C5&SUBSYS_18881019†will install zhe driver of SoundMAX Integrated Digital Audio.
We have done the same job and improve it's not the best way, So we change to use a tool (base on EVEREST) to distinguish the Manufacturer of device and decompression the right driver pack
In this example the tool will decompression the driver pack named realtek.7z, The driver pack soundmax.7z will keep in compressed, So windows will automatically install the right driver of realtek.
integrateing an external program is a long term task... and this is not the proper forum for that.
well look into your suggestion.
lets just fix D for right now.
Thanks again.
how much free space is on your disks? you will need 3 GB or more
method one source 300 mb
method one QSC 600 mb
temp file for extracted driverpacks 1.2 gb
Total 2.1 gb
destination folder 600 mb
Grand Total 2.7 gb
Is U: a mapped network drive?
@Gray88
Welcome to DriverPacks!
this is a technique we use every day
Nice job! excellent work... thanks for shareing!
would you like to be on the testing team? were always looking...
jeff
Welcome to DriverPacks!
We all use nLite - and we all use base too. (Remember to always run base as the last step in your process)
No. You will not get the expected result integrateing with nLite plus your installation will grow from 300 meg (7-zipped) of drivers to 1.2 gig.
control panels and anything else installed by a setup program would not be executed by nLite but would be by the driverpacks "finisher".
If nLite did this as well then we wouldn't be here... tee hee...
Your right there are a plethora of valid reasons to use DriverPacks Base
and the other three programs we can't live without.
-RyanVM for windows update slipstreaming
-Nlite for automating and tweaking
-Driverpacks for drivers
-WPI (Windows Post Installer) for installing enduser software and registry tweaks.
-Nlite for createing / burning the ISO
Installed in that order is important too
MSFN is a great source of general info check it out http://unattended.msfn.org/unattended.xp/
We are glad to help you anytime! Thanks for being here
the contents of the bin folder and the contents of teh 7zip file must be in %systemdrive%\
and they are seemingly not according to your script results - make sure everything from DPsFnshr.7z is in %SystemRoot%
post your DPsFnshr.ini and DPsFnshr.log (i:\windows\DPsFnshr.log?)
Looking at it now - short answer is - you probably need most or all of them - we'll look at the inf file.
put them all in there for a quick test to see if it even works.
@realhyg - No it will not cause a series of problems because we leave the generic hwid in one of the drivers
if it really is a generic it wont matter and
if its not then the extended HWID will install the correct driver
IE if it really is a generic card any driver that contained the generic HWID will be functional. but we would pick a signed driver to keep the generic HWID. Grooming HWIDS is a tested and proven method. BTW making sweeping statements without any specific details helps no one, start your own thread [duplicate posts are not neccessary], post hwids of the conflicts, show us logs, give specifics; which pack, which base, (do you even use driverpacks base?) We like feed back and appreceate input - thank you - but your post was vague and nonspecific. Furthermore we are already aware how windows compares, chooses and installs drivers. please see the post earlier in this thread http://forum.driverpacks.net/viewtopic. … 342#p15342
If you are aware of a specific senario where this happens just let us know and we'll be more than happy to fix it.
@dolivas
just add the setup.exe and the setup.iss to S/SM/A/3
additionaly if you use the name setup.iss and setup.iss exists in the same folder as setup.exe the { /f1"%DPSROOT%\D\S\S\U\Setup.iss" } parameter is not technicaly required (but let's specify it anyway)
how it works
the driver is installed by normal driverpacks operation (so don't delete anything)
when the finisher runs it will look for "%SystemRoot%\system32\drivers\smwdm.sys IF IT EXISTS it will run setup /s
more
If you deleted the driver files then "%SystemRoot%\system32\drivers\smwdm.sys would not get installed and therefore not exist
since smwdm.sys is not a native windows file the setup /s would not run unless driverpacks installed it first.
turn on quick stream cache (QSC) and retry (it was off when you ran this)
Welcome to driverpacks.net - thanks for posting
"I am thinking if I could slipstream the DriverPacks with my Winxp cd, burn the result into a cd and then build the BartPE disc with this new cd."
no pebuilder will only copy files that are in its internal list of files, so any added drivers would be ignored.
LAN and the other packs will be comeing out this winter as i have the time.
Method two merely saves space on the install disk (around 300MB) and avoids an oempnpdriverspath limitation of 4096 characters. I think our curent folder structure is around 6000 so a few hundred of the drivers would not be available to setup.
we rename setup.exe and use a dummy one we wrote. It extracts the driverpacks, adds them to the PNP search path, then calls the original setup file which we rename.
It will not break ANY existing funtionality of windows setup
Welcome to Driverpacks.net - were glad your here!
lets see your DPs_BASE.ini
make sure QSC is on
we cross posted reread my last please
dolivas wrote:Debugger wrote:OverFlow, SoundMax Control Panel is different to install by ini file. It hasn't cpl file. It installs by InstallShield, and to create .iss file (to make silent install), panel installer must to setup at motherboard with that soundmax chip, else the panel installer show an error message.
Ok thanks Debugger maybe this is not worth the trouble the reason I wanted to try and install the control panel with the driver is because when the driver is installed with the DP I get this error when running the DirectX Diagnostic Tool (DirectSound test results: Failure at step 10 (Secondary buffer): HRESULT = 0x80004005 (Generic failure) I decided to remove the drivers that the DP installed and installed the drivers that Asus provides they were the same as what is in the DP I checked the file hashes and they matched. Once the drivers where installed with the setup program which also installs the SoundMAX Control Panel I retested the system again with the dxdiag tool and this time all test pass? Any thoughts on the error? the sound seems to work fine and like I said the correct driver is installed with the DP.
Thanks,
dolivas
debugger has given you the answer
create the .iss file on a machine with this sound card (you have to do it for us).
you can look up how to create a .iss file by google. http://helpnet.installshield.com/robo/p … seFile.htm
then we launch the setup from the ini entries (like i showed above) useing the .iss file you provide to automate the soundcards setup program when we run the finisher.
no problem.
[SM-A-3]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 1
exc_1_tagFile1 = "%SystemRoot%\system32\drivers\smwdm.sys"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\S\SM\A\3\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\S\S\U\Setup.exe" /s /f1"%DPSROOT%\D\S\S\U\Setup.iss"
it would be an arduous task
base doesnt seem to be broken the copy is executed from textsetup.sif and the entries in textsetup.sif appear to be correct. although a space before the "=" is normal i dont think its mandatory.
this seems to be a windows issue we now have a workaround for.
-ps RIS and NIS are not currently supported by the base and even if it were how can i force them to mount their folders properly from base???...
since we know that i386 needs to be in the root either map it that way or use that old dos command "SUBST" if you must bury the folder structure.
SUBST drive_letter: path
@tiger he is talking about the destination not the source
Tiger is right you are doing this the hard way you need to create a new installation source (or use base to update your old source) to create a new image. trying to update an existing system image would be a VERY tough job.
Check out this post http://forum.driverpacks.net/viewtopic.php?id=2115
That is a good point - we are always covering sysprep - and a guide does seem needed
sysprep yech...
Which driver was it that worked ?
26th of May 2006 driver, version 5.10.5067.0 of what? can you give us the folder name and the driverpack version of the one that did work? and can you test a driverpack if we add the HWID to it?
add your control panel file and create an entry in the INI - you can use the existing entries as a guide
add YourControlPanelFileName.cpl to D\S\SM\A\3\
something like the code below needs added to the sound INI file
[SM-A-3]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 1
exc_1_tagFile1 = "%SystemRoot%\system32\drivers\smwdm.sys"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\S\SM\A\3\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "cmd.exe /c copy /y %DPSROOT%\D\S\S\U\YourControlPanelFileName.cpl %SystemRoot%\system32"
the control panel can be installed with driverpacks.
it simply requires an entry added to the sound B INI to install the control panel.
the finisher will copy files or even run a setup program when specified in the DriverPack_Sound_B_wnt5_x86-32.ini file
If i read this thread correctly you are getting the sound driver installed from d\s\sm\a\3\ ?
There is no control panel file in that folder so it would also have to be included there first.
It is also interesting to note that this drivers signing is broken
nice work guys .... way to work together.
is there a reason you are not useing the latest version of base and the newer finisher?
Posts found [ 5,051 to 5,075 of 5,307 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.112 seconds, 5 queries executed ]