You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 5 of 159)
DriverPacks.net Forum » Posts by mr_smartepants
TechDud wrote:Do you like the changelog, mr_smartepants?
Now it goes back to "First Release!"
LOL, sure.
The release changelogs are cumulative and show all the final changes from all the test builds.
Testing build changelogs should show what each build changed from the previous testing build (added/changed/deleted/regression)
cdob wrote:I've no idea, if a Windows 7 dism works at Vista files or at Windows 2008 (not R2) files.
May work or fail, it's not supported.
Yes it does. Each newer version of DISM is backwards compatible and IS supported by M$.
I have an HP Z420 sitting on my desk at work. What a beast!
I didn't have the same problem you did because I used the $WinPEDriver$ folder method.
http://support.microsoft.com/kb/2686316
As long as the accompanying DPsFnshr.ini is written properly, the NT5 DriverPacks Finisher will execute it with the current SAD.
Floppy wrote:Was my DtcInstall.log ok?
I don't know, I don't use SysPrep. Something happened during the "generalize" process.
Floppy wrote:I have this in my
SETUPCOMPLETE.cmd
REG ADD %KEY%\070 /VE /D "Driver Oppdatering" /f
REG ADD %KEY%\070 /V 1 /D "%systemdrive%\D\SAD2\DP_Install_Tool.cmd /s
Looks like you're missing an end-quote from your second REG line.
Change to read:
REG ADD %KEY%\070 /V 1 /D "%systemdrive%\D\SAD2\DP_Install_Tool.cmd /s"
Yes, the /S switch is used to make SAD silent.
Ken@fri wrote:I also add this switch (overwrite mode)
to 7Zip extraction commands of sections :Lets_GO, :Method2 & :Begin
Nice! I'll add that into my working copy.
http://forum.driverpacks.net/viewtopic. … 641#p51641
ChiefZeke wrote:Intel RST 12.6.0.1003 released
Beat you to it Chief! 
Strange, I don't have that problem.
Here's a sample batch to illustrate:
@Echo off
ECHO Line 1!
ECHO Line 2
ECHO Line 3!
ECHO Line 4
results in:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
I:\test>test12.bat
Line 1!
Line 2
Line 3!
Line 4
I:\test>
It's possible there's something wacky going on in the French localization of the code.
I'll remove the exclamation points just to be safe.
I'll also look into the log-delete errors.
Thanks for reporting.
Thanks! I was reading this yesterday.
http://msdn.microsoft.com/en-us/library … S.85).aspx
At least M$ has a sense of humor!
Well, doing some research into WMIC I found the following tidbit works to identify notebooks.
WMIC SystemEnclosure GET ChassisTypes /value
On a notebook the output would be "ChassisTypes={10}" but on anything else the value would be blank. Once the target machine is identified as a notebook, further filtering can be applied.
Ref: http://technet.microsoft.com/en-us/libr … 80825.aspx
Microsoft wrote:This property when set to the value of 10 is equivalent to "notebook." However, not all computers provide this property.
Hmm, I wonder if we could do something similar by polling WMIC on the target system.
<goes off to play in the sandbox...>
TechDud wrote:Would a touchpad mfg possibly be listed in acpi, for instance?
Well, most touchpads are on the ACPI bus anyway. Sometimes their mfg can be divined from the HWID but not always.
%*sny9001.DeviceDesc%= MouFilter_Inst9001,*SNY9001,ACPI\SNY9001 ;Alps Pointing-device
The above touchpad is declared as an "Alps" but the HWID contains "SNY" which indicates "Sony".
There are other indicators; "IBM" or "LEN" for Lenovo, "DLL" for Dell, etc.
ikbeneenlul wrote:If I use SP0, SP2 or SP3 then guiSetup crashes on my Pentium1 90Mhz 
I haven't even SEEN a Pentium 1 in over 10 years! Get some new(er) hardware! 
2013-05-11 21:39:41 : <PREP> Replaced original setup: method 2 was used previously.
2013-05-11 21:39:42 : <PREP> Verified method 2 references don't exist in txtsetup.sif or dosnet.inf.
Yup, source is suspect if DriverPacks BASE is already detecting a prior (broken) method-2 integration.
vlotho wrote:and for 64 bits ?
We don't support Windows XP x64
http://forum.driverpacks.net/viewtopic.php?id=2651
Ra wrote:The DP_Touchpad_Mouse does not include the Microsoft Mice and Keyboard drivers does it ?
Correct, they do not.
Thanks cdob! I had forgotten about that.
Here's the latest version: v130507
http://www.mediafire.com/file/2dqtuw948 … -130507.7z
:: Changelog:
:: v130507 v3.0 (Erik Hansen)
:: Fixed bug where KTD option was not set when /CR switch is used.
:: Changed folder delete code to incorporate array processing.
:: Cleaned up user choice code, standardized variable names to X_CamelCase method.
:: Examples: C_Blah (user Choice variable), D_Blah (Directory variable), F_Blah (Function variable), O_Blah (Object variable), T_Blah (Temp/disposable variable)
To-Do: Increase data output to log.
I really need to find the time to update the first post...
Change your "for %%i" line to read as follows and it WILL work:
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF /I EXIST %%i:\sources\install.wim SET "CDROM=%%i:"
The main difference is the inclusion of "IF /I", the /I makes the query case-insensitive meaning that "BlAh" is the same as "blah". Also get in the habit of enclosing your SET variables in quotes to eliminate stray spaces.
I know this works because I use the exact same line in my .cmd.
I always use IF /I EXIST unless I'm looking for a very specific case-spelling.
Yeah, but again that would be "hard-coding" SAD with those known problems. What if they're solved in future DriverPacks? We'd be removing valid drivers from a working pack when we don't have to. Having the .txt file within each DriverPacks allows for greater flexibility, dontcha think?
Well, adding the text file to the DriverPacks and adding code to support that function was just a proof of concept. It still needs further testing before we re-release new DriverPacks with the "known-problems*" file (not all DriverPacks will need it).
This current version of SAD will work fine if those files are not present (IF EXIST...).
I'm glad it worked for you! Whew!
Ken@fri wrote:Any idea why only this file remains in system?
Well, probably because I haven't uploaded the modified HID Third Party DriverPacks. 
Here's the modified NT5 HID Third Party DriverPack.
http://www.mediafire.com/file/e626s4ft3 … _1209b1.7z
Here's the modified 32-bit NT6 Third Party DriverPack.
http://www.mediafire.com/file/cg1itmmai … _1203b1.7z
Here's the modified 64-bit NT6 Third Party DriverPack.
http://www.mediafire.com/file/5vi7mirxl … _1203b1.7z
If you don't want to wait for my HID testpack uploads, you can make your own by creating a text file inside the \D\ folder (NT5) or in the root of the .7z archive (NT6) using the following format:
Known-problems-{name_of_dps}.txt
; The following drivers are known to cause problems during automatic integration.
; If your device is not installed during automatic installation, you can try these folders manually.
x64\All\3\Touchpad_Mouse\Alps\2\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Alps\3\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Alps\4\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Alps\5\Apfiltr.inf
x64\All\3\Touchpad_Mouse\Elantech\1\ETD.inf
x64\All\3\Touchpad_Mouse\Elantech\2\ETD.inf
x64\All\3\Touchpad_Mouse\Elantech\3\ETD.inf
x64\All\3\Touchpad_Mouse\Cypress\1\cykbfltr.inf
x64\All\3\Touchpad_Mouse\Cypress\1\cymfltr.inf
Posts found [ 101 to 125 of 3,962 ]
DriverPacks.net Forum » Posts by mr_smartepants
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.100 seconds, 5 queries executed ]