Bilou_Gateux

@codejunkie Since you have switched from a lite version to a full pack version, i no longer use your pack for a single reason. I want to keep my UA install clean and generic. i add more customizations and non MSFT branded binary files from cmdlines.txt. EDIT: mergecabs.cmd works as expected and TXTSETUP.SIF is edited if we don't forget to add RyanVM drivercabfix.exe in the same folder.

try my batch file here Q: how is your "ATI Radeon Mobility 9000" Display adapter detected by windows? A1: Standard VGA Graphics Adapter A2: Video Controller A3: other, please use Siginet Get_HWIDs.exe before installing PnP Devices drivers and post the result.

Here a small batch i use to install the devices unknown from Windows at the end of install. May be someone will find it of some interest... Required tools: Pyron's SetupCopyOEMInf.exe Microsoft's Devcon.exe @ECHO OFF SETLOCAL set DriverPack=%SystemDrive%\PnPDrvrs ::// Define which class to install/update set class=Unknown ::// Path to Pyron's SetupCopyOEMInf.exe tool set SetupCopyOEMInf=.\bin\CopyINFs.exe ::// Path to Device Console tool set DevCon=.\bin\devcon.exe %SetupCopyOEMInf% %DriverPack% ::// goto :%class% :Unknown set command=remove ::// Find all Devices, with specified setup %class% name, and start %command% subroutine for each one FOR /F "tokens=1* delims=: " %%A IN ('%DevCon% FindAll ^=%class% ^| FIND ":"') DO (SET ID="%%A")&(SET DEVICE=%%B)&(SET HWID=%ID:~0,22%")&(CALL :%command%) ::// run single %command% set command=rescan goto :%command% :remove ::// Remove devices that match the specific hardware or instance ID echo Device: %device% %DevCon% %command% %HWID% :rescan ::// Tell plug&play to scan for new hardware %DevCon% %command% to help understanding the batch script, see output for a Video Controller: command: output: %%a : %%b set variables: Remove device that match the specific hardware or instance ID: Tell plug&play to scan for new hardware: I don't install unknown devices during UA install using methods described in this forum for one reason. I use the same Hard Drive with the installed Windows in two box with different hardware. Solution 7: Create a new Hardware Profile before shutdown Windows. Question: does anybody know how to create a new Hardware Profile with a command line? standard GUI method:How To Create Hardware Profiles on Windows-Based Mobile Computers

Why not try to use an AutoIT script: Copy with progress dialog... by ezzetabi call the function with these parameters: _CopyDirWithProgress("X:\AI\SOURCE\I386\", "C:\I386\")

I have not checked the encryption / password protection feature yet. That's why i have made some tests by changing to alternate shell by injecting some files / modifying some hives keys in the ISO before burning it. The Copy Muppy don't works as expected to be used in your project. When we select \AI\SOURCE\I386 as source and C:\I386 as destination, the files are copied to destination C:\I386\AI\SOURCE\I386 and the "listing" used in command line use hardcoded paths with drive letter. Good new if in the next version you are going to use the infs from the original WinPE and read/modify to your needs during the build process. I will wait patiently for next release.

about the copy source: Maybe can we use this Copy Muppy freeware (use VB6run60sp6.exe and comdlg32.ocx / tabctl32.ocx / mscomctl.ocx) under WinPE.

@Justin I would recommend you not to use your predefined CONFIG.INF and WINPESYS.INF when building the hives. It would help to build a new AICD with all available versions of WinPE (using the <OPK_CD>\WINPE\*.infs) without leaving some new features introduced in later versions of WinPE. I'm intending to build an AICD not launching your shell as default. Using a different shell let me choose between your AI.EXE or another tool GHOST32.EXE or loading Network first...

@hp38guser: Thanks for cleaning the code and post again. Just finished my UA install (on real box) and just discover it. Too late to check this time with 2K3. i will report on my next install... @a06lp: Maybe can you add some credits on 1st post to shalti for the original idea of setupcopyoeminf.exe coded by Pyron. and then ask BtS stickying this post instead of Unlimited number of drivers + keeping the drivers., Exception: MassStorage drivers. by schalti SOLVED: drivers from CD, possible even without winnt.sif! by Pyron Just a suggestion...

Thanks Siginet for your compiled AutoIt scripts. I'm using a little different script from the BTS original. @ECHO OFF :: Initialize variables SET TmpFile="%Temp:"=%.\_DevCon.dat" :: Remove old temporay file IF EXIST %TmpFile% DEL %TmpFile% :: Store DEVCON info in a temporary file to speed up processing DEVCON Find PCI\VEN_* | FIND ":"> %TmpFile% 2>NUL DEVCON Find USB\VID_* | FIND ":">> %TmpFile% 2>NUL TYPE %TmpFile% I use the _DevCon.dat output in batch script. the output is more clean because only valuables infos are stored inside. the output from BTS contains not valuable infos (devices using Windows OS built-in drivers) and sections headers. Could you enhance the GUI of your tool with a selection (drop down list?): PCI Devices: PCI\VEN_ USB Devices: USB\VID_ All Devices: PCI\VEN_ + USB\VID_

@hp38guser Thanks! change done successfull. Another question. My unattended install is based on "Windows Server 2003, Web Edition Setup" The autoIT script don't delete the 3 files in @SystemDir. I have tried to change strings WinWaitActive("Windows Server 2003, Web Edition Setup", "") and WinSetTrans("Windows Server 2003, Web Edition Setup", "",170) with no success. how can i check the string to use? @all When installing only digitally signed drivers (with a cat file), the WatchDriverSigningPolicy.exe is not necessary. I have edited the drivers.au3 autoit script and add a semicolon in front of both lines with WatchDriverSigningPolicy.exe process and successfully unattended install (on a real box, not on a VirtualMachine) Digitally Signed Drivers.

I have a request because i don't know how to change the drivers.au3 AutoIt code. I always install Windows from a Network share or from an i386 source folder located on the hard drive (WINNT32.EXE /s:<source_path>) booting first the box with WinPE/BartPE. My Drivers folder is located on %SystemDrive%\Drivers. Could you post a modified AutoIt script that search \win51ip.SP2 on local HDD instead of CD. I just need a new subroutine to set $instDrv to another letter than CD letter. Optional (i can edit the original au3 to replace with my IDTag): Can you set the IDTag win51ip.SP2 in a variable for use with others Windows versions.

Slow NIC detection with all brands or only with a specific model? I use BartPE with HP w/ Broadcom onboard, FSC w/ Intel 1000 onboard and NEC w/ VIA Rhine II onboard and don't have encountered slow detection... Do you use original WinPE factory.exe or "Bartpe network support plugin" for NIC detection?

@Justin for the next major release, i have one suggestion: Adding a line in AIUI X Initialize Setup Engine X Partition Hard Drive X Format Hard Drive X Copy Source Files to HDD X Install Windows X Restart and Finalize Settings It takes a long time to copy source files from CD to HDD and it would be fine to know what happens during this laps

Original post #719 by tommyp in HOTFIXES: Win2000 SP4 – WinXP SP1 – WinXP SP2 topic by Incroyable HULK

reg add "HKLM\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{03D9F3F2-B0E3-11D2-B081-006008039BF0}" /v "Compatibility Flags" /t REG_DWORD /d 1024 /f I always add the /f switch, just in case... Approuved , c'est du franglais or it's frenchglish?

Myself user of 2K3 Server SP1 Web Edition as OS (turned to workstation ). If you can share your method after figured / solved possible issues, please post in this thread. Currently, i have already build my install source with all updates integrated (using a little modified method based on RyanVM pack). Will post a new topic when i have full documented process.

Should we continue to use XPCREATE ? Today GreenMachine [url="http://xpcreate.com"]http://xpcreate.com[/url] is down...

@RyanVM your batch includes a reference to DRIVERCABFIX but the exe is not included in the downloaded attachment?

Download Windows Server 2003 Service Pack 1 32-bit Deployment Tools Open "Microsoft Windows Preinstallation Reference" Help File (ref.chm) Go to Unattend.txt > WindowsFirewall Settings are documented in this section of the help file:

Microsoft TechNet: Microsoft Windows Server 2003 TechCenter Post-Setup Security Updates

[url="http://support.microsoft.com/kb/891861/en-us"][b]Update Rollup 1 for Windows 2000 SP4[/b][/url] was released [b][color="red"]June 28, 2005[/color][/b]. This update rollup contains a list of security-related updates produced for Windows 2000 between the release of Windows 2000 SP4 and April 30, 2005. SVCPACK.INF (integrate method) [checked install on real box with 2K Server] XPCREATE Freeware version [code][Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=0 BuildNumber=2195 [SetupData] CatalogSubDir="\i386\svcpack" [SetupHotfixesToRun] IE6SP1.EXE /Q:A /R:N IE6START.EXE /Q:A /R:N SP5.EXE /Q /U /O /N /Z >>> Rollup Update Package for Windows 2000 SP4 890046.EXE /Q /U /O /N /Z >>> Security Update for Windows 2000 893066.EXE /Q /U /O /N /Z >>> Security Update for Windows 2000 894320.EXE /Q /U /O /N /Z >>> Security Update for Windows 2000 896358.EXE /Q /U /O /N /Z >>> Security Update for Windows 2000 896422.EXE /Q /U /O /N /Z >>> Security Update for Windows 2000 [ProductCatalogsToInstall] KB890046.CAT KB893066.CAT KB894320.CAT KB896358.CAT KB896422.CAT MDAC.CAT SP5.CAT[/code] Updates for individual Windows components not included with a clean slipstream install of Windows 2000 SP4 are not added to this sample. [b]Critical Updates and Service Packs[/b] to add reported by www.windowsupdate.com / "Automatic Updates" notification: [b][color="blue"]Cumulative Security Update for Outlook Express 6 Service Pack 1 (KB897715)[/color][/b] WU/AU [b][color="blue"]Cumulative Security Update for Internet Explorer 6 Service Pack 1 (KB883939)[/color][/b] WU/AU [b][color="blue"]Microsoft Windows Installer 3.1[/color][/b] WU/AU [b][color="blue"]Microsoft GDI+ Detection Tool (KB873374)[/color][/b] WU [b][color="blue"]Security Update for Windows 2000 (KB841356)[/color][/b] AU only report [b][color="blue"]Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 (KB842773)[/color][/b] WU/AU [b][color="blue"]Security Update for Microsoft Data Access Components (KB832483)[/color][/b] WU/AU [b][color="blue"]814078: Security Update (Microsoft Jscript version 5.6, Windows 2000, Windows XP)[/color][/b] WU/AU [b]Windows 2000 Updates[/b] [color="blue"][b]DirectX 9.0c End-User Runtime[/b][/color] [b][color="blue"]Microsoft .NET Framework version 1.1[/color][/b] [color="yellow"](1)[/color] [color="blue"][b]Root Certificates Update[/b][/color] [color="blue"][b]Windows Media Player 9 Series[/b][/color] [color="yellow"](2)[/color] After adding updates, need to add fixes to updates... [color="yellow"](1)[/color][b][color="blue"]Microsoft .NET Framework version 1.1 Service Pack 1[/color][/b] [color="yellow"](2)[/color][b][color="blue"]Critical Update for Windows Media Player Script Commands (KB828026)[/color][/b] Note:[list] [*]Windows Media Services 4.1 fixes for Windows 2000 Server are included in rollup (WMS subfolder). XPCREATE don't integrate well the binary files in I386. I have to manually compress the 4 files in WMS subfolder to I386 and edit DOSNET.INF [/list][code]@echo off :: Updating dosnet.inf FINDSTR /V /B /I /C:"d1,WMS\nscm.exe" CDROOT\I386\DOSNET.INF>>DOSNET.INF MOVE /Y DOSNET.INF CDROOT\I386\DOSNET.INF > NUL FINDSTR /V /B /I /C:"d1,WMS\nsiislog.dll" CDROOT\I386\DOSNET.INF>>DOSNET.INF MOVE /Y DOSNET.INF CDROOT\I386\DOSNET.INF > NUL FINDSTR /V /B /I /C:"d1,WMS\nsisapi.exe" CDROOT\I386\DOSNET.INF>>DOSNET.INF MOVE /Y DOSNET.INF CDROOT\I386\DOSNET.INF > NUL FINDSTR /V /B /I /C:"d1,WMS\nspmon.exe" CDROOT\I386\DOSNET.INF>>DOSNET.INF MOVE /Y DOSNET.INF CDROOT\I386\DOSNET.INF > NUL :: compress binary files in I386 IF EXIST CDROOT\I386\WMS\*.* FOR /F "USEBACKQ DELIMS==" %%J IN (`DIR /A-D /OGN /B CDROOT\I386\WMS\*.* 2^>NUL`) DO MAKECAB /D CompressionMemory=21 /D CompressionType=LZX /L CDROOT\I386 CDROOT\I386\WMS\%%J > NUL :: removing files and subfolder IF EXIST CDROOT\I386\WMS\*.* FOR /F "USEBACKQ DELIMS==" %%L IN (`DIR /A-D /OGN /B CDROOT\I386\WMS\*.* 2^>NUL`) DO DEL CDROOT\I386\WMS\%%L > NUL IF EXIST CDROOT\I386\WMS RMDIR CDROOT\I386\WMS /S /Q > NUL[/code][list] [*]MDAC problem (missing file not in i386 during install) [/list][code]:: Updating dosnet.inf FINDSTR /V /B /I /C:"d1,mdac.cat" CDROOT\I386\DOSNET.INF>>DOSNET.INF MOVE /Y DOSNET.INF CDROOT\I386\DOSNET.INF > NUL[/code] WindowsUpdate reports "Security Update for Microsoft Data Access Components (KB832483)" as not installed[list] [*]MSXML3 SP5 update is no longer needed (included in rollup) [/list]

Update Rollup 1 for Windows 2000 SP4 was released June 28, 2005. This update rollup contains a list of security-related updates produced for Windows 2000 between the release of Windows 2000 SP4 and April 30, 2005. @tommyp, have you started to work on the integration of the rollup. it will save us alot of time to use rollup package instead of > 50 "Security Update for Windows 2000" Fixes.

First, i believe your question is more "Device Drivers" related than "Unattended Windows". Maybe a moderator can move this thread in "Device Drivers". Second, what's the brand of your USB HID devices. Checks the Manufacturer support web site and download the latest drivers set for your hardware (you will need and inf file and the associated sys and dll files) for Logitech hardware, we can download a full installer (setup.exe), install it on a test box and then pickup the needed files from %ProgramFiles%\Logitech\WinXP or something similar... I think your can find a solution by adding the drivers from the manufacturer instead of using generic Windows drivers (input.inf, kbdhid.sys and mouhid.sys) with the method and tool described in this thread: Unlimited number of drivers + keeping the drivers. I have solved a problem very similar on a Microsoft Windows XP embedded (component-based Windows XP variant with special added functions) FSC Futro D100 ThinClient. Logitech Kbd/Mice Cordless USB Receiver install problem Before finding the solution, it was necessary for me to plug a PS/2 keyboard and PS/2 mouse to click Next when my USB receiver was plugged.

Thanks for the clarification. Just received a new french WinPE 2005 OPK CD. I have checked the \WINPE\WINPESYS.INF and new registry keys value and data are added: ;; XP SP2 Specifics;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; [AddReg.5.1.2] HKLM,"Setup\AllowStart\DcomLaunch" HKLM,"ControlSet001\Services\DcomLaunch","Description",0,"%REMOTE_PROCEDURE_CALL_LAUNCHER_DESCRIPTION%" HKLM,"ControlSet001\Services\DcomLaunch","DisplayName",0,"%REMOTE_PROCEDURE_CALL_LAUNCHER_SERVICE%" HKLM,"ControlSet001\Services\DcomLaunch","ErrorControl",0x00010001,1 HKLM,"ControlSet001\Services\DcomLaunch","Group",0x00000000,"COM Infrastructure" HKLM,"ControlSet001\Services\DcomLaunch","ImagePath",0x00020000,"%SystemRoot%\system32\svchost.exe -k DcomLaunch" HKLM,"ControlSet001\Services\DcomLaunch","ObjectName",0x00000000,"LocalSystem" HKLM,"ControlSet001\Services\DcomLaunch","Start",0x00010001,2 HKLM,"ControlSet001\Services\DcomLaunch","Type",0x00010001,32 HKLM,"ControlSet001\Services\DcomLaunch\Parameters",,0x00000012 HKLM,"ControlSet001\Services\DcomLaunch\Parameters","ServiceDll",0x00020002,"%SystemRoot%\system32\rpcss.dll" HKLM,"ControlSet001\Services\Rpcss","DependOnService",0x00010000,"DcomLaunch" I hope it will solve the diskpart issue with the newest WinPE OPK 2004 & 2005 CDs. You can release an intermediate release (build 200?) with only small changes which do not requires too much work: It's not really necessary as most users works on regular Windows. If the file is missing, it's just as easy as copying it in our %Windir%\system32 folder.

Ok, starting to play with the tool. @all Basically, Justin-Credible has made a nice tool to achieve the method described Deploying Windows XP, Using the Windows PE Booting from a Windows PE CD (or DVD) which contains a copy of the operating system source files. and allows customization of the operating system source files (unattended install + adding OEM Drivers) and a nice GUI front-end. have put a lot of time to make it I have checked the "View Build Details" to debug the build. You cannot use BartPE: "AutoInstall CD-ROM Builder v2.2" uses the MSFT tools located in the \WINPE folder of the "WinPE OPK CD" to build a new bootable CD. My first build fails because "AutoInstall CD-ROM Builder v2.2" searchs for Factory.exe and Netcfg.exe in the \I386 folder of the "WinPE OPK CD". On my "WinPE OPK CD", both exe's are located in \TOOLS\X86 and in \I386\SYSTEM32 The "AutoInstall CD-ROM Builder v2.2" use xcopy.exe. If you're running a Lite flavor of Windows on your box, checks this command line utility has not been removed... @Justin-Credible Feature request: Section Interface: Small Banner Image can you add Windows 2003 Section Interface: we can configure "Bootup text" (loader prompt in TXTSETUP.SIF) can you add configure "NoGUIBoot" How to boot the Windows Preinstall Environment from an RIS server by using PXE-enabled clients Question:Section Drivers > Drivers Used During Install (Mass Storage Devices) Are these drivers integrated to $OEM$\TEXTMODE in AI\SOURCE\I386 (OS Source)and WINNT.SIF/UNATTEND.TXT relevant section or Are these drivers integrated to I386\SYSTEM32\DRIVERS and relevant section in TXTSETUP.SIF(WinPE) How to add unsupported or updated third-party mass storage drivers to a customized WinPE CD or both? If i add a specific mass-storage driver not included in the original Windows source CD, i need it both in WinPE to have access to the drive connected to the controller during boot and in Windows source CD to allow unattended install on the drive. Notes: (from the help file) AutoInstall CD-ROM Builder uses the Windows PE 1.2 image builder engine which has a known bug when using a Windows XP SP2 or Windows 2003 Server SP1 disc to build it. This bug prevents the Disk Partition command line tool (diskpart.exe) from being able to run, which will render your DiskPart scripts unusable. It is recommended that you use a regular Windows XP (or XP SP1) or a regular Windows 2003 Server disc to build your AutoInstall CD.CD. @Justin-Credible This problem has been solved by Bart when building BartPE CD with Windows 2003 Server SP1 or Windows XP SP2 binaries dcomlaunch plugin FAQ #17 Maybe can you add the needed reg data and values to the hives when building WinPE?