You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 36 of 213)
Topics by OverFlow User defined search
Posts found [ 876 to 900 of 5,307 ]
I would like to restate that we are in agreement here. (and thanks BP for pointing out that DS went to Devcon)
If you are doing Clean installs from Disc or USB Slipstreaming is best.
If you are changing hardware (like a MB) or useing universal imaging, or RIS, then Software first installers are better.
I also agree that DPINST never was the tool it was intended to be... and is frought with bugs. Although the bugs are rare, less than 1% of drivers have issues, when you have hundreds of thousands of drivers that is a signifigant factor. If Driverpack Solution has gotten a Devcon Based installer working then there is no question that it will be the superior app. (At least for an after the installation solution, slipstreaming is still best for new installs)
Always nice to see you around SamLab! Keep the feedback coming our way!
yup that would be the main cause... there is another, that is very rare
Thanks Echo_Platoon!
It's Really nice to see you updating a pack. You are one of the original masters!
Jeff
Hello vehf263.
vehf263 wrote:Hi everybody!
1. if I need a widest range of newest drivers with NO EXCLUSION presented in this forum to have my personal initial repository of drivers how can I download it at once?
You can't. You must download the all of the main DriverPacks, and any 3rd party DriverPack you wish to use.
http://driverpacks.net/downloads
vehf263 wrote:2. I use Russian "DriverPack Solution" and "Drivers Installer Assistant" but is there a better alternative to those ones?
The best thing to do is to use our app "DriverPacks BASE" to add the DriverPacks to your source. There is no better option. If you do that then the drivers will be installed during windows setup... this is by FAR the best way to go.
"DriverPack Solution" http://forum.driverpacks.net/viewtopic.php?id=4927
and "Drivers Installer Assistant" http://forum.driverpacks.net/viewtopic.php?id=4206
are both friends of the DriverPacks . However Both of these are what microsoft calls "software first installers". That means that the application is run after windows is finished installing (and potentially after you have installed and updated your software). DriverPacks also has a Software first installer that can be used. DriverPacks BASE has an option called SAD (Stand Alone Drivers) which is a simple script that will update drivers after your install, not as fancy with all the bells and whistles like the other two but it is simple and effective with no GUI or any options for the user (or you) to be confused by 
.
So both of the apps you mention are fine and so is our SAD solution... But installing drivers after the install will never work as well as intalling them during windows setup. Slipstreaming the DriverPacks with DriverPacks BASE is absolutely the best way to update the drivers in your systems. (please note that if you do slipstream the packs to a source with BASE that source will automatically include the SAD script. So any DriverPacks slipstreamed source can also be used for a software first soluton too.)
vehf263 wrote:3. are driverpacks cumulative so if will download from "Get the latest" I will have all I need?
Yes!
I agree with Ricktendo64... the only thing DriverPacks does during the PE stage of setup is extract the drivers, and there is a progress bar for that step. This takes about 4~6 minutes on a decent machine. Somthing else is causing your issue (something that perhaps is conflicting with DriverPacks). Have you made any changes after adding DriverPacks?
Also here is way to do it after the fact... Thanks to Ricktendo64 for pointing it out.
http://forum.driverpacks.net/viewtopic. … 678#p41678
obviously adding them to your source FIRST is a better method... but since it seems you have already blown way past that point you could use pnputil to update your already completed source, and then use the WIM method above the next time you start clean 
On the contrary, you must install windows before you do anything else... Yes?
Windows is installed from a Wim file... Yes?
That makes these instructions "Step 0"
IE the very first thing you do.
Once you add the drivers to windows... you are done... Let me be even more clear... These instructions don't just add the drivers during the install... They permenently add the drivers to windows.
Again what you want and keep asking for is right under your nose ... well if you scroll up.
The instructions are above... 
That is to say you asked "what the best way to do add drivers" at the end of the thread that describes in great detail the best way to do it...
Obviously you have been banging your head against the wall too long . (skip that step and read the above thread)
real1elmo wrote:If DISM is the way to go can you make a script that adds all the driverpack subfolders for mass storage, and existing ones in winpe just in case.
http://driverpacks.net/docs/miscellaneo … er-attempt
already did
if you selected mass storage text mode then it should be supported for text mode...
In other words RIS is text mode
usb nic support with native windows ... "not"
method 2 .. M1 has been considered retired for years
finisher .. your choice
KTD off
QSC on
tutorial on how to add driverpack in my signature...
presetup is added when you use DriverPacks BASE to slipstream DriverPacks into your source
Take a look at Autoimage by roguespear. his app works with DriverPacks BASE to create RIS images.
another option is to make sure to add the full set of DriverPacks is copied and installed with your pxe image.
see here for an idea http://forum.driverpacks.net/viewtopic.php?id=4808
you just need to make sure the OEM folder is copied to $win_nt$.~ls (it should be automagically copied)
Why are you useing M1? is there a particular reason? if not M2 is a better option
Just substtute your NT6 drivers for the windows NT5 drivers in your SAD folder
Bam! SAD for windows 7.
Dpinst.exe (the core component) is win7 compatable.
the ROI is just terrible with sysprep... I hope you can prove me wrong. Good luck!
you can't use mass 10.x.x with BASE 8.12.x or any other older versions of DriverPacks BASE.
Major changes with DriverPacks BASE and mass Storage took place in version 10.
You can't use 10x DriverPacks BASE with old mass.
You can't use 10x Mass Storage with old DriverPacks BASE.
It looks like there might be a stray " mark in the Mass INI file. We'll take a look.
Edit...
Hmmm... There is a huge hole in your txtsetup.sif file - all the entries after [D] and up to [H]... many lines are missing. Did you verify the MD5 of your Mass 10.10? Did you make changes after DriverPacks BASE was run? Did you have a bad burn on your disc?
http://forum.driverpacks.net/viewtopic. … 325#p30325
copy setupreg.hiv setupreg.hiv.%random%.sav
reg.exe unload HKLM\loaded_SYSTEM
reg.exe load HKLM\loaded_SYSTEM setupreg.hiv
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts5\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts6\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe add "HKLM\loaded_SYSTEM\ControlSet001\Services\nvgts7\Parameters\PnpInterface" /f /t REG_DWORD /v "5" /d 1
reg.exe unload HKLM\loaded_SYSTEM
I did not say to put $OEM$ at the root of the drive i said put OEM at the root. (M2)
OEMfilesPath won't work either... for the same reason M1 does not work. We exceeded the 4096 character path limit about five years ago. you cant use M1 for what you are doing. Since you said Presetup.cmd failed i assumed you were useing M2 since M1 does not use Presetup.cmd.
Use M2 move "OEM" to the root of the thumb... or follow the directions in the thread i linked above. (forget all about M1, it's dead)
ricky.martin4545 wrote:gotaker wrote:no, no antivirus
also that exe is also not in the bin folder.....wher eis it picking the file from
?????
stumped
I guess We'll have to be patient a little longer.
You just responded to a thread that has not had a post in over four years... Either you are a lot more patient than me, or you are really stupid. I have a vote for the latter.
those files are replacements.... IE they are renamed by BASE to KR10N.ORG etc...
We have updated drivers included in our mass storage pack.
Copying them to KR10N.sys won't work... since it is actually looking for KR10N.sy_ ;P
Renameing them will definately blow you up.
This has never been an issue before so i am not sure why you are haveing a problem now.
The DriverPacks are included with UBCD4Win... so why are you adding them?
Jeff
CDOB R U out there?
I do this myself...
Put the OEM folder at the root of your thumb drive... one simple solution
here is another http://forum.driverpacks.net/viewtopic.php?id=4808
Posts found [ 876 to 900 of 5,307 ]
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.116 seconds, 5 queries executed ]