Drivers Which method is the best?
Posted 08 October 2005 - 02:24 PM
The AutoIT method: http://www.msfn.org/...showtopic=51406
And Pyron's method: http://www.msfn.org/...showtopic=12566
Have you guys tried either of these? Which one do you recommend? Or is there a better way with HFSLIP?
Posted 08 October 2005 - 04:01 PM
only because it seems easier, but I haven't tried it, so YMMV.
My $.02. When doing his 3 steps, create your OEM subfolders alongside your SOURCE\i386 folder. Once all 3 steps are complete, run HFSLIP and you're good to go.
Posted 08 October 2005 - 08:44 PM
I'm not saying that methods are not working at all. Maybe the reason was on my side
And it would be cool to have DRIVERS folder integrating drivers too
Or have a small sub-script just for this purpose - uncab/cab/include in drivers.cab (and get some out
PS Now I'm just using an old official method of winnt.sif and OEM folders structure. The obsolete folders with drivers are deleted during the first startup by cleanup.cmd that is usefull anyway because it also deletes some more crap from just installed system.
This post has been edited by Oleg_II: 08 October 2005 - 09:05 PM
Posted 09 October 2005 - 03:27 AM
Thanks also go out to Pyron for making SetupCopyOEMInf.exe, which is used in this method.
Nethertheless, i highly recommend using autoit method by hp38guser because you don't need to use the special setup.exe by Pyron and presetup.cmd. AutoIT method don't need to swap original MSFT files with special ones.
Posted 09 October 2005 - 06:56 AM
Posted 09 October 2005 - 07:11 AM
Sorry for misunderstanding, I meant you introduced this method to me
And I was wrong - there is no modified setup.exe. But anyway, I tried it and it didn't work for me. Maybe because it is only for Windows XP? Is it really possible to modify it somehow so that it works with Windows 2000?
Posted 09 October 2005 - 11:12 AM
Actually the au3 script don't parse any file searching for some path. It only runs two commands, the first is WatchDriverSigningPolicy.exe which stays in memory, then launch SetupCopyOEMInf.exe which scan the specified folder and add all infs to Windows inf folder and when job is finished, WatchDriverSigningPolicy is removed from memory (like using taskill to kill the process).
The path to use is first searched from WINNT.SIF with the Detached command which parse $WINNT$.INF to find dospath value.
What value want you to get from prodspec.ini?
You may ask confirmation to hp38guser but his method works with all flavour of modern OS (Win2K, WinXP and Win2003).
The SetupCopyOEMInf function copies a specified .inf file into the %windir%\Inf directory. SetupCopyOEMInf does not recopy the file if it finds that a binary image of the specified .inf file already exists in the Inf directory with the same name or a name of the form OEM*.inf. When SetupCopyOEMInf copies a file, it renames the copied file to OEM*.inf. Name provided is unique and cannot be predicted.
SetupCopyOEMInf uses the following procedure to determine if the .inf file already exists in the Inf directory:
All .inf files with names of the form OEM*.inf are enumerated and any files that have the same file size as the specified .inf file are binary compared.
The Inf directory is searched for the source filename of the .inf file. If an .inf file of the same name exists and is the same size as that of the specified .inf file, the two files are binary compared to determine if they are identical.
If the specified .inf file already exists a further check is performed to determine if the specified .inf file contains a CatalogFile= entry in its [Version]section. If it does, the .inf files's %windir%\Inf primary filename with a ".cat" extension is used to determine if the catalog is already installed. If there is a catalog installed, but it is not the same as the catalog associated with the source .inf, this is not considered to be a match and enumerations continue. It is possible to have multiple identical .inf files with unique catalogs contained in %windir%\Inf directory. If an existing match is not found, the .inf and .cat files are installed under a new and unique name.
OEM .inf files that do not specify a CatalogFile= entry are considered invalid with respect to digital signature verification.
In cases where the .inf file must be copied to the %windir%\Inf directory, any digital signature verification failures are reported.
If the .inf and .cat files already exist, these existing filenames are used and the file replacement behavior is based on the specified CopyStyle flags. Replacement behavior refers only to the source media information stored in the .pnf. Existing .inf, .pnf, and .cat files are not modified.
If all drivers are digitally signed (have a .cat file), we can avoid using WatchDriverSigningPolicy.exe. I have already launched an install without it (all my drivers are digitally signed) and having no issues.
This post has been edited by Bilou_Gateux: 09 October 2005 - 11:19 AM
Posted 12 October 2005 - 10:24 AM
Besides that, now i am confused Does this method work with Windows 2000 or not?
Posted 13 October 2005 - 01:04 AM
During unattended I run appz.cmd (place it in HFSVPK which installs all my programs from installation disk and does simple tasks like this:
xcopy "%CDDRIVE%\tweak\clean.cmd" "%UserProfile%\Start Menu\Programs\Startup\" /Y
This line copies CLEAN.CMD from my installation disk to Default User Profile. During the first logon my profile is created from and inherits all files and shortcuts from Default User Profile. As you know all files or shortcuts placed in Startup will run automatically on startup.
So, windows starts the first time and runs CLEAN.CMD where I specify:
RD /Q /S %SystemDrive%\drivers
This line deletes DRIVERS folder and all its content including sub-folders from the system disk. There are some more stuff I delete in CLEAN.CMD.
The batch has a command to delete itself at the end so it won't disturb you any more.
fdv also suggested a method with WELLCOME.EXE. I haven't tried it yet but it has potential
PS Send me PM and I'll include the content of my CLEAN.CMD and other stuff you need in reply
This post has been edited by Oleg_II: 13 October 2005 - 01:42 AM
Posted 13 October 2005 - 07:31 AM
I tried again AutoIt method yesterday but wasn't lucky again. But I probably found where is my mistake: I have not commented OemFilesPath=\$OEM$ and OemPnPDriversPath="drivers\0;drivers\1;drivers\2" - that's maybe my problem.
Let's see if I have some time today to try on my other computer.
By the way there is a good script to compress drivers found here _http://www.msfn.org/board/index.php?showtopic=35869
Posted 14 October 2005 - 01:37 AM
I will PM you my email. Thanks. I'd love to take a look at the script.