erik_demon

Hey, welcome to MSFN You need to keep the OEM folder because all driverpacks + other important files are stored there. If you want to save space, I would recommend you to leave-out some driver packs. EDIT and a nice addition from colinbate

@ rimtech Hi, welcome to MSFN This is a known bug in the driverpack. It happend to me two. About 95% of the drivers failed. There are two thing you can do if you want to keep the drivers and use method 2. 1. Use the fix that I discribed in post nr. 400 2. Wait for Bashrat's new BASE pack which should be released soon.

This is a known issue, see this post

@groovie No need for this my friend, always happy to help If you want to preserve the drivers: yes Presetup.cmd is used to extract the driverpacks ( the *.7z files) to the harddisk. Then Presetup will use SetDevicePath.exe to find and save the location of the drivers. If you want to install this way (method 2 of Bashrat's BASE pack) these step are crucial. keep_the_drivers.cmd runs a program called SetupCopyOEMInf.exe I don't really know precisely what this program does, but if I understand it correctly, it copies and registers INF files (and does some other stuff) If you want to preserve the drivers, both steps are crucial. If you are not that familiar with this method, I would advise you to wait until Bashrat releases his new BASE pack (I've seen a few posts back that he implanted this fix) If you want to preserve the drivers: Yes This is possible, but not if you want to preserve the drivers. This can be done, but you can not preserve the drivers this way (unless you keep that one CD in there forever ). If you want to do this, your drivers must be unpacked on your CD. Extract all .7z files to the root of your CD. Now use the following presetup.cmd: SET tagfile=\OEM 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 exist "%%i:%tagfile%" set CDDRIVE=%%i: CD /D %SystemRoot%\system32 %CDDRIVE%\OEM\bin\SetDevicePath.exe %CDDRIVE%\D START %CDDRIVE%\OEM\bin\WatchDriverSigningPolicy.exe SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\999 /V 1 /D "%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemRoot%\Inf" /f EXIT I hope this helps!! Erik

@ groovie Hi It is very important that if you want to keep the drivers, you shouldn't delete the driver folder (in this case the SystemRoot%\BtS_DriverPacks\D folder) You should delete the line! I also noticed a flaw in your RunOnceEx.cmd: REG ADD %KEY%\045 /VE /D "DriverPack" /f REG ADD %KEY%\045 /V 1 /D "%SystemDrive\D\BTS_DPs_Control_Panels.cmd" / REG ADD %KEY%\045 /VE /D "DriverPack" /f REG ADD %KEY%\045 /V 1 /D "%SystemDrive\D\keep_the_drivers.cmd" /f You use two times nr. 45 The second value (keep_the_drivers.cmd) overrides the first value.(BTS_DPs_Control_Panels.cmd) It looks like you are well underway, good job

@CoRoNe I already answered this question see post nr. 525

Hey Mark49 X-Savior and myself have been working on this for quite some time now. We developed a method that is working just fine. You can find it here If you check out post nr. 67 you can find a how-to manual there that explains my approach to this method.

@Vid0 Good find, thnx

@groovie So did you also used the method to keep the driver? If I don't use it all goes fine. @ Bashrat, Because KtD isn't working for method 2 (yet) I would suggest the following (temporary) fix. Use the normal presetup.cmd to install the drivers, so until the problem with SetupCopyOEMInf.exe is solved, we are going to use SetDevicePath again. presetup.cmd: SET tagfile=\OEM 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 exist "%%i:%tagfile%" set CDDRIVE=%%i: CD /D %SystemRoot%\system32 CD /D %SystemDrive% %CDDRIVE%\OEM\bin\7za.exe x -y -aoa %CDDRIVE%\OEM\DriverPack_*.7z -o"%SystemRoot%\BtS_DriverPacks\" %CDDRIVE%\OEM\bin\SetDevicePath.exe %Systemroot%\BtS_DriverPacks\D START %CDDRIVE%\OEM\bin\WatchDriverSigningPolicy.exe SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\999 /V 1 /D "%CDDRIVE%\OEM\bin\SetDevicePath.exe %SystemRoot%\Inf" /f EXIT Then we could have windows keep the drivers by using the SetupCopyOEMInf.exe during GUIRunOnce like this: [GUIRunOnce] command8= "%SystemDrive%\D\BTS_DPs_Control_Panels.cmd" command9= "%SystemDrive%\D\keep_the_drivers.cmd" keep_the_drivers.cmd SET tagfile=\OEM 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 exist "%%i:%tagfile%" set CDDRIVE=%%i: START /WAIT %CDDRIVE%\OEM\bin\SetupCopyOEMInf.exe %SystemRoot%\BtS_DriverPacks\D EXIT

Hi, Welcome to MSFN.ORG I don't really know if I understand your question but I will answer it the best way I can. What is a switch A switch is a bit of information that you hand-out to the installer. The information tells the installer to use (a for that installer specific) command. As an example WISE installers use the /S switch. If you use this switch like for instance adawarese.exe /S the installer is told to do a silent install. What switch should I use? Like I said before, every installer has it's own switches. Most of the time you can recognize it easily (if you open the setup it is sometimes displayed, or you can see it by looking at the icon). Check-out this page for information about the most important installers. If you don't have a clue: you can do the following: - use /? or /help : This provides you with some information of the switches that can be used. adawarese.exe /? - You can also use the Universal Silent Switch Finder. This cool program detects alot of switches. Check-out this topic - Take a look at the Application switches topic I hope this helps! Good luck

Hey The problem has nothing to do with your winnt.sif When during setup does this happen? Is it a T=13? If this is the case, then I guesse you are trying to install Media player 10 from within svcpack.inf If this is the case, you are using the wrong switch. Could you tell me a bit a more? Have you slipstreamed Windows mediaplay 10? (and if so, how)? EDIT: Welcome to MSFN.ORG!!

Hey Isn't the program installed, what exactly do you mean? I use this switch, and it works great daemon.msi /quiet /passive /qn /norestart REBOOT=ReallySuppress

I think that this method should replace the current method 1. Like you said it would save a lot of space on the CD (which is always great). Personaly I like method 2 better, I alway hate to use OemPnPDriversPath because I always make a few mistakes when editing the large line I think that this is a great improvement to method 1

@RogueSpear Thanks for your reply This works, I've done it many times now. Thanks, I will change this! Bashrat changed this in his pack. (This only works if you make the choice to keep the driver (a special option in his batch). Yes, I did this on purpose. I can't delete the %SystemRoot%\BtS_DriverPacks folder because I want to preserve the drivers. I can however delete the %systemdrive%\D folder (which also has the control panels batch inside) I will try to put everything on the %SYSTEMDRIVE%. I don't have any time to test some more today. But I will try it soon. Thanks for all your help

I just tried it, and it didn't work . This is what I tried: winnt.sif [GuiUnattended] DetachedProgram = "%SYSTEMDRIVE%\D\drivers.cmd" presetup.cmd SET tagfile=\WINXP\OEM 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 exist "%%i:%tagfile%" set CDDRIVE=%%i: CD /D %SystemRoot%\system32 CD /D %SystemDrive% %CDDRIVE%\WINXP\OEM\bin\7za.exe x -y -aoa %CDDRIVE%\WINXP\OEM\DriverPack_*.7z -o"%SystemRoot%\BtS_DriverPacks\" EXIT driver.cmd SET tagfile=\WINXP\OEM 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 exist "%%i:%tagfile%" set CDDRIVE=%%i: START /WAIT %CDDRIVE%\WINXP\OEM\bin\SetupCopyOEMInf.exe %SystemRoot%\BtS_DriverPacks\D START %CDDRIVE%\WINXP\OEM\bin\WatchDriverSigningPolicy.exe EXIT The file driver.cmd is in my $OEM$\$1\D folder I never used DetachedProgram before so maybe I made a mistake. In never saw the SetupCopyOEMInf.exe during setup. EDIT: Don't pay attention to the fact that I use WINXP multiple times. I install from a second harddrive, and the folder WINXP can be seen as the root of my CD.

Okay, thanks I will give it a try

Hey guys I did some testing today with the newest BASE pack. I used method 2 (with and without KtD), and I used all latest pack except the MassStorage pack Here are the results: - The problem with FEDIT.exe being on the root of the CD is solved! - The file BTS_DPs_cleanup.cmd isn't copied to the $OEM$\$1\D folder, therefore there is no clean-up - KtD with method 2 is improved, but it still doesn't work completely. Thanks to the START /WAIT command, SetupCopyOEMInf.exe is now executed during presetup. The problem is that SetupCopyOEMInf.exe fails to intergrade the drivers. For more info: Check out this post

Your welcome By the way, this problem is fixed with Bashrat's newest BASE pack ( V 5.04.12 )

Hi I did another test today and this time my presetup.cmd looks like this (Bashrat's DP method 2 with preserving the drivers) : SET tagfile=\OEM 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 exist "%%i:%tagfile%" set CDDRIVE=%%i: CD /D %SystemRoot%\system32 CD /D %SystemDrive% %CDDRIVE%\OEM\bin\7za.exe x -y -aoa %CDDRIVE%\OEM\DriverPack_*.7z -o"%SystemRoot%\BtS_DriverPacks\" START /WAIT %CDDRIVE%\OEM\bin\SetupCopyOEMInf.exe %SystemRoot%\BtS_DriverPacks\D START %CDDRIVE%\OEM\bin\WatchDriverSigningPolicy.exe Because of the START /WAIT command, SetupCopyOEMInf.exe is finally loaded during presetup There however still is a problem When SetupCopyOEMInf.exe start it fails to intergrade the driver : Found C:\Windows\BtS_DriverPacks\D\W\L\blabla.inf Trying to intergrade ... failed I get this with 95% of the drivers. When I run SetupCopyOEMInf.exe in windows again it works flawless What could be the problem?

It's a leftover file, you can delete it.

@Beagz you also have to edit Drvindex.inf, add all the .INF files to the %systemroot%\inf folder and add the necessary lines to txtsetup.sif and dosnet.inf

@X-Savior I tested this method myself and I now know that this method has some advantages and two big disadvantages: advantages: - Windows directly identifies and installs the drivers. With our method, we always needed to tell windows to search for the drivers. With this method this isn’t necessary. (just like you plug in a new USB mouse) - This is a by Microsoft documented method. This method is already used for some devices (scanners mostly ask to install the software first before you plug & play the device.) This method is stable. - This method has no problem with double file names: You might think that our method doesn't have this problem either. I'm not so sure about that. What would happen if their are two device that both use a different version of the file a.sys Then we would have in our Drvindex.inf: [mydriver] a.sys How does windows know which file to use?? In this method this is all taken care off. disadvantages: - It takes a lot of space on the harddrive, my D folder now is 644 MB, when this is in a .CAB file, it is only 193MB - It takes some time to run SetupCopyOEMInf.exe With all Bashrat's DP's this could easily take 15 min. @RogueSpear This would take a lot of time. About 15 min on every boot. Besides with this method this isn't necessary (only you don't have any compression) Yeah, that would be great. I would wish that all driver manufacturers did this. I think that there is one big reason why this doesn't happen. Just think about all the poor souls with their 56K modem This method solves this problem @schalti Would it be possible to let SetupCopyOEMInf.exe scan inside a .CAB or .7z file?

Hi, welcome to MSFN First things first: Please remove your Product-key Now about your question: The winnt.sif looks allright. Are you sure winnt.sif is inside the i386 folder? Also check the filename, sometimes it is saved as winnt.sif.txt

I think you mean this tweak: ;turn off system beeps [HKEY_CURRENT_USER\Control Panel\Sound] "beep"="no"

I that case: let your sfx file extract the files to your %systemroot% folder And use SetupCopyOEMInf.exe %Systemroot%\D I think this should work