Bilou_Gateux

I suggest to read my topic here : Removing Internet Connection Wizard from Windows 2000 Professional deployments : It shows a sample batch file to add values in registry key for your IE6SP1 install through cmdlines.txt, you should try to run my iernonce.cmd just after the IE install : sample cmdlines.txt [commands] ".\inst_IE6.cmd"" ".\iernonce.cmd" inst_IE6.cmd executes IE6SETUP.EXE /C:"IE6WZD /S:""#e"" /Q:A /R:N" iernonce.cmd executes IE6SETUP.EXE added keys in Registry RunOnceEx GreenMachine uses this method when integrating IE6 installation via SVCPACK 2KCREATE by GreenMachine

For many Windows users, especially those presently using Windows 2000, Windows XP Home or Windows XP Pro, Netmeeting may already be installed on your computer or at least it will be on your computer's installation disk. If you are curious as to whether or not you have Netmeeting already installed, perform the following: go to the Start button, select Programs, go to Accessories, go to Communication and look for Netmeeting. If Netmeeting is properly installed it should be located in the Communication folder. If you did not locate Netmeeting in the Communication folder perform the following: go to the Start button, go to Find All Files and Folders and type in conf.exe in the edit box and perform a search. If the conf.exe file is not found by executing a search on your computer, it is likely that you will need to get a copy of Netmeeting. You can start Netmeeting by typing conf.exe in the Run command. This will start the NetMeeting Setup wizard. During setup, you'll be prompted to create Desktop and/or Quick Launch bar icons. Where is NetMeeting located in Windows 2000, Windows XP and in Windows Server 2003?

Unattended installation Technical Reference by M$ Very well documented, maybe Admin can add this to Threads of Interest ?

Moved here Removing Internet Connection Wizard from Windows 2000 Professional deployments :

@ECHO OFF SETLOCAL ENABLEEXTENSIONS SET SOURCE= <write the name of the source folder here> SET TARGET= <write the name of the target folder here> IF EXIST %SOURCE%\*.* FOR /F %%J IN ('DIR /A-D /OGN /B %SOURCE%\*.*') DO MAKECAB /D CompressionMemory=21 /D CompressionType=LZX /L %TARGET% %SOURCE%\%%J Take care that all files *.* in the source folder (including the .inf and .cat files) are compressed to target folder. To use the content of target folder for unattended install, .inf and .cat files MUST be uncompressed. use expand to uncompress a file EXPAND Source Destination and delete compressed version driver.in_ and driver.ca_

Using MSCONFIG to Change the Programs Starting Automatically

That's a new one on me. I wonder why ... I'll have to check this out when I get back, but I've never seen the need before. Could it be due to a "flat" install? look at the Tbone2 post. Tbone2 He adds lines to section [FloppyFiles.2] for RAID drivers The position of $OEM$ in the folder tree differs when you install from CD : CDROOT\$OEM$ or from flat or network share : CDROOT\I386\$OEM$ Creating OEM installations for Windows

Just edit \WinXP\UlSata.inf with notepad and you will find the name of your RAID controller. UlSata.inf PCI\VEN_105A&DEV_3373.DeviceDesc="WinXP Promise SATA378 (tm) IDE Controller" you can use method described by Tbone2 to do the works. But you should first write your own dosnetadd.txt and txtsetupadd.txt and write a modified patch.cmd.

TOSHIBA Magnia Z310 Maybe these infos may help others msfn members to solve their RAID unattended installs : At the moment, i use M$ recommended method with $OEM$\TEXTMODE folder Directory of D:\XPCREATE\CDROOT\I386\$OEM$\TEXTMODE 26/08/2004 14:48 <DIR> . 26/08/2004 14:48 <DIR> .. 20/06/2002 17:47 8ÿ081 ADPU160M.CAT 03/06/2002 18:17 6ÿ351 ADPU160M.INF 14/05/2002 17:10 92ÿ650 ADPU160M.SYS 19/08/2002 19:49 7ÿ409 MEGA2K.CAT 26/12/2000 15:17 9 MEGAIDE 09/08/2002 14:21 2ÿ624 MEGAIDE.INF 17/06/2002 15:30 100ÿ251 MEGAIDE.SYS 16/11/2000 15:35 1ÿ407 NODEV.INF 25/08/2004 19:03 1ÿ627 TXTSETUP.OEM 29/03/2002 13:33 58 U160DSK1 content of the TEXMODE folder : one device driver image (.sys) file for each RAID component one or more information (.INF) files for each RAID component an optional driver catalog (.CAT) file for each RAID component one text-mode setup information file (txtsetup.oem) in my case ADPU160M.* are Adaptec Ultra160 Family Driver files MEGAIDE.INF MEGAIDE.SYS MEGA2K.CAT NODEV.INF are LSI Logic MegaRAID IDE 100 Driver files MEGAIDE and U160DSK1 are tag files found in the downloaded driver package from the manufacturer. The reference to these files appears in TXTSETUP.OEM file, that's why i keep them although I'm not sure it's needed. some driver packages also contains driver library (.dll ) files but i can't say if they're needed for TEXTMODE install method. D:\XPCREATE\CDROOT\I386\WINNT.SIF [OEMBootFiles] ADPU160M.SYS ADPU160M.INF ADPU160M.CAT MegaIDE.sys MegaIDE.inf Mega2k.cat nodev.inf TXTSETUP.OEM [MassStorageDrivers] "LSI Logic MegaRAID IDE 100 Driver With Backplane Support (Windows 2000)" = "OEM" "Adaptec Ultra160 Family PCI SCSI Controller (Windows 2000)" = "OEM" "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"=RETAIL D:\XPCREATE\CDROOT\I386\$OEM$\TEXTMODE\TXTSETUP.OEM #################################################################################### # #This txtsetup.oem file can be used for unattended installs of Windows 2000 only. # #################################################################################### [Disks] d3 = "LSI Logic MegaRAID IDE Driver",.\MEGAIDE,"" d4 = "Adaptec Ultra160 Family Driver",.\U160DSK1,"" [Defaults] scsi = MegaIDE_NT5 [scsi] MegaIDE100_NT5 = "LSI Logic MegaRAID IDE 100 Driver With Backplane Support (Windows 2000)", MegaIDE adpu160m = "Adaptec Ultra160 Family PCI SCSI Controller (Windows 2000)", adpu160m # This section lists the files that should be copied if the user # selects a particular component option. # # <file_type> is one of driver, port, class, dll, hal, inf, or detect. # See below. # <source_disk> identifies where the file is to be copied from, and must # match en entry in the [Disks] section. # <filename> is the name of the file. This will be appended to the # directory specified for the disk in the [Disks] section to form the # full path of the file on the disk. [Files.scsi.MegaIDE100_NT5] driver = d3, MegaIDE.sys, MegaIDE inf = d3, MegaIDE.inf inf = d3, Nodev.inf catalog = d3, Mega2k.cat [Files.scsi.adpu160m] driver = d4,adpu160m.sys, aic7892 inf = d4,adpu160m.inf catalog = d4,adpu160m.cat [HardwareIds.scsi.MegaIDE100_NT5] id="PCI\VEN_1095&DEV_0649&SUBSYS_0649101E", "MegaIDE" [HardwareIds.scsi.adpu160m] id = "PCI\VEN_9005&DEV_008F","adpu160m" [Config.MegaIDE] value = "", Tag, REG_DWORD, 1 [Config.adpu160m] value = "",tag,REG_DWORD,20

Maybe the problem is with this syntax Switches in TXTSETUP.SIF , Here's what "1,,,,,,,,,_x,4,0" means txtsetup.sif [SourceDisksFiles] megaide.sys = 1,,,,,,4_,4,1,,,1,4 I will try to change this to [SourceDisksFiles] megaide.sys = 1,,,,,,3_,4,1 Syntax may differ between 2K and XP ? 2K = 4 setup boot disks XP = 6 setup boot disks 3_ = file on 3rd disk in 2K 4_ = file on 4th disk in XP When we launch an install from a flat folder (other partition or network share) rather than boot from the CD, it's a kind of same installation as booting from the 1st disk and then insert 2nd 3rd and 4th ? I have modified the syntax in txtsetup.sif to see if it can solve the problem but it doesn't change anything. Only the other solution (add a line in section [FloppyFiles.2] of dosnet.inf works for me). It's not really a problem for me because i've found the workaround. May be can this info contributes to make XPCreate more versatile and works with all possible cases. The second "problem" i have to solve is to replace the old adaptec adpu160m.sys driver integrated in 2K original CD with a new one and add the new supported controllers (Adaptec Ultra160 ASIC's PCI\VEN_9005&DEV_008F.DeviceDesc = "Adaptec AIC-7892 - Ultra160 SCSI") integrated on my server mobo.

No success @idle.newbie need a clarification about your detached.cmd batch : %CD% where did you set this variable ? Is it the CDROM Drive Letter of the Windows installation CD source i386 and $oem$ ?

Windows 2000 Unattended install of mass storage drivers for HP/Compaq ProLiant Servers As posted here, i think it's not possible to use subdir for each MassStorage Driver answer is probably YES That the method used by HP/Compaq with their SmartStart installation tool.

Here the result of MEGARAID integration with XPCreate. I have built a new install using Windows 2000 Server MUI + SP3 slipstream. I run the installation from the flat CDROOT folder using winnt32.exe After reboot, during the text mode setup, i have this message : the file megaide.SYS could not be found the solution to solve the problem is to manually edit dosnet.inf and add this to section [FloppyFiles.2] d1,megaide.sys That way, megaide.sys is copied from the source CDROOT\MEGAIDE.SY_ to the target C:\$WIN_NT$.~BT\MEGAIDE.SY_

@serialzs I would like to know what does exactly drvz.exe. If it's an autoit script, could you make the code public (turn back the compiled exe to script code) we can alter it to best fit our needs (change the default folder name for drivers).

2KCREATE Using XPCREATE with Windows 2000 Gold + Service Pack 4, one hotfix type 1 (835732) updates files that are located in I386\UNIPROC. After creation of the slipstreamed 2K CD, i have found duplicate files in the CDROOT\I386\UNIPROC folder. KERNEL32.DLL 5.0.2195.6897 KERNEL32.DL_ WIN32K.SYS 5.0.2195.6897 WIN32K.SY_ WINSRV.DLL 5.0.2195.6826 WINSRV.DL_ The non compressed version are from the HF 835732 the compressed version are from SP4 These lines are added to DOSNET.INF [ForceCopyDriverCabFiles] kernel32.dll ntdll.dll win32k.sys winsrv.dll [Files] d1,UNIPROC\kernel32.dll d1,UNIPROC\ntdll.dll d1,UNIPROC\win32k.sys d1,UNIPROC\winsrv.dll In the original dosnet.inf from the CD, files located in UNIPROC subfolder are not listed. I would like my source Cd to be as clean as possible to use nLite to reduce the size of source after XPCreate. PS : The code works fine as is with SP4 slipstream but with SP3 + HF type 1 only slipstreaming instead, i've got a BSOD during install with the file winsrv.dll not found. The problem is related to the reference to this file in dosnet.inf

Registry Console Tool For Windows 2000 - version 2.0 Copyright (C) Microsoft Corp. 1981-1999. All rights reserved REG Operation [Parameter List] Operation [ QUERY | ADD | DELETE | COPY | SAVE | LOAD | UNLOAD | RESTORE | COMPARE | EXPORT | IMPORT ] Return Code: (Except of REG COMPARE) 0 - Succussful 1 - Failed For help on a specific operation type: REG Operation /? Examples: REG QUERY /? REG ADD /? REG DELETE /? REG COPY /? REG SAVE /? REG RESTORE /? REG LOAD /? REG UNLOAD /? REG COMPARE /? REG EXPORT /? REG IMPORT /? The Windows 2000 Support Tools are located in the Support\Tools\ directory of the Microsoft® Windows® 2000 operating system CD. This directory contains directories for a Master Setup Program (Setup.exe) for the Windows 2000 Support Tools that is separate from the Windows 2000 operating system installation. When you run this Setup program, it installs all of the Support Tools from Support.cab onto your computer's hard drive. Important The tools in Support.cab have not been localized: they are written and tested in English only. Using these tools with a different language version of Windows 2000 might produce unpredictable results. Note The tools in Deploy.cab are for deployment/preinstallation purposes only and are not installed when Setup is run. The tools (Setup Manager and Sysprep) in Deploy.cab are localized. The files for the Windows 2000 Support Tools are included as compressed cabinet (.cab) files on the Windows 2000 CD. You can extract individual files from these .cab files. Extract reg.exe from support.cab.

There is a method documented here (unfortunately in French) : W2K SP3 Bootable CD +IE6 +WMP9 +DX9 +Hotfixes + applications The method described use a tool from the ressource kit : sed.exe Example is for Adobe Reader 5 1/ replace the hardcoded letter in setup.iss by %systemdrive% 2/ save the file as setup.txt in the installation folder (where resides setup.exe) and delete setup.iss 3/ create a new file parse.bat type %systemdrive%\winapps\acrobat\setup.txt|%windir%\sed.exe 's/\%%systemdrive\%%/%systemdrive%/g'>%systemdrive%\winapps\acrobat\setup.iss 4/ save in $OEM$ 5/ add the command to your cmdlines.txt [Commands] ".\parse.bat" Hope it may help you and ask more if you don't understand french and would like more help. Will try to translate more... download outils.zip on the link to get tool and examples

OK for the option (show confirmation) set in the ini file. More easy to use than a switch for a program with a GUI.

OK, answered to your previous post : http://www.msfn.org/board/index.php?showtopic=24632

not a reduced wget.exe version but a hacker tool which do his job fine : CMDget.exe - 1.5kb - Downloads a file from a website from user provided parameters ( Example: CMDGet http://illmob.org/trojan.exe c:\>owned.exe ) md5.exe - 15kb - gets the md5 hash of a file small collection of tool i use regularly in a remote shell/cmd prompt CMDget.exe PM sent

@big_gie DevPath.exe is not written to remove values in registry. The purpose is to scan the path given, search for .inf files and add each folder found which contains and .inf file to the key in registry. Nethertheless, at the end of windows Installation, The value for the key in registry is correct according to my PnPDrvrs folder, 7z drivers archives are well unpacked in the subfolders but my OEM drivers are not installed in windows. I believe that Windows installation as already started PnP detection at the time mt39.exe run the command. winnt.sif [Unattended] UnattendMode=FullUnattended DriverSigningPolicy=Ignore NtUpgrade=No ; OemFilesPath= ; OemPnPDriversPath= OemPreinstall=Yes OemSkipEula=Yes OverwriteOemFilesOnUpgrade=No TargetPath=\WINNT Win9xUpgrade=No [GuiUnattended] AdminPassword=* AutoLogon=Yes AutoLogonCount=1 OEMSkipRegional=1 TimeZone=105 OemSkipWelcome=1 DetachedProgram="%systemdrive%\PnPDrvrs\mt39.exe" Arguments="%systemdrive%\PnPDrvrs\default.xml" default.xml <?xml version="1.0" encoding="ISO-8859-2" standalone="no"?> <!-- Note that the new encoding is ISO-8859-2 This will let SOME special characters like accent in french. I think it should work with spanish, german, and other european languages. Please tell me if something doesn't work. --> <mt39 version="0.8.1" testingmode="0" logging="1"> <!-- [MANDATORY] "version" = Your .xml version. It NEEDS to match the program's version [Optionnals] "testingmode" = 1 (default if not present) or 1 mt39 will not execute files but pop you a MessageBox with informations "logging" = 1 (default if not present) or 1 Will launch the logging feature if enabled NOT YET IMPLEMENTED --> <item> <program>%systemdrive%\PnPDrvrs\cmeu0wdm.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <program>%systemdrive%\PnPDrvrs\E100B.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <program>%systemdrive%\PnPDrvrs\iata.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <program>%systemdrive%\PnPDrvrs\IntelINF.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <program>%systemdrive%\PnPDrvrs\nvfs.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <program>%systemdrive%\PnPDrvrs\PSeries.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <program>%systemdrive%\PnPDrvrs\smwdm.exe</program> <arguments>-y /q /r:n</arguments> <hide>1</hide> <wait>300</wait> </item> <item> <!-- Add OEM drivers' location to registry --> <!-- Please see this post: http://www.msfn.org/board/index.php?showtopic=12566&hl=drivers+devpath --> <program>%systemdrive%\PnPDrvrs\devpath.exe</program> <arguments>%systemdrive%\PnPDrvrs</arguments> <hide>1</hide> <wait>300</wait> </item> </mt39> mt39_default.log Sun Aug 15 17:12:16 2004 mt39 version: 0.8.1 XML version: 0.8.1 XML file: C:\PnPDrvrs\default.xml Log file: C:\PnPDrvrs\mt39_default.log Sun Aug 15 17:12:16 2004 INFO: File "C:\PnPDrvrs\cmeu0wdm.exe" does exist, trying to execute... Sun Aug 15 17:12:17 2004 INFO: Program "C:\PnPDrvrs\cmeu0wdm.exe" was executed with arguments "cmeu0wdm.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:17 2004 INFO: File "C:\PnPDrvrs\E100B.exe" does exist, trying to execute... Sun Aug 15 17:12:18 2004 INFO: Program "C:\PnPDrvrs\E100B.exe" was executed with arguments "E100B.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:18 2004 INFO: File "C:\PnPDrvrs\iata.exe" does exist, trying to execute... Sun Aug 15 17:12:19 2004 INFO: Program "C:\PnPDrvrs\iata.exe" was executed with arguments "iata.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:19 2004 INFO: File "C:\PnPDrvrs\IntelINF.exe" does exist, trying to execute... Sun Aug 15 17:12:20 2004 INFO: Program "C:\PnPDrvrs\IntelINF.exe" was executed with arguments "IntelINF.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:20 2004 INFO: File "C:\PnPDrvrs\nvfs.exe" does exist, trying to execute... Sun Aug 15 17:12:25 2004 INFO: Program "C:\PnPDrvrs\nvfs.exe" was executed with arguments "nvfs.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:25 2004 INFO: File "C:\PnPDrvrs\PSeries.exe" does exist, trying to execute... Sun Aug 15 17:12:27 2004 INFO: Program "C:\PnPDrvrs\PSeries.exe" was executed with arguments "PSeries.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:27 2004 INFO: File "C:\PnPDrvrs\smwdm.exe" does exist, trying to execute... Sun Aug 15 17:12:29 2004 INFO: Program "C:\PnPDrvrs\smwdm.exe" was executed with arguments "smwdm.exe -y /q /r:n" and returned the code "0" Sun Aug 15 17:12:29 2004 INFO: File "C:\PnPDrvrs\devpath.exe" does exist, trying to execute... Sun Aug 15 17:12:30 2004 INFO: Program "C:\PnPDrvrs\devpath.exe" was executed with arguments "devpath.exe C:\PnPDrvrs" and returned the code "0" Sun Aug 15 17:12:30 2004 End of execution, exiting... registry export DevicePath=%SystemRoot%\Inf;C:\PnPDrvrs\cmeu0wdm;C:\PnPDrvrs\E100B;C:\PnPDrvrs\iata;C:\PnPDrvrs\IntelINF;C:\PnPDrvrs\nvfs;C:\PnPDrvrs\PSeries;C:\PnPDrvrs\smwdm all my subfolders with .inf files are added to the default value %SystemRoot%\Inf

I agree with (Gely @ Jul 1 2004, 11:43 PM) Maybe make the install confirmation windows (which resume selected settings) optional would be fine ? either use a /s or /silent switch to avoid this, or use a /v or /verbose switch to have a final confirmation before running winnt32.exe would be nice in next release. and a small typo / cosmetic error i've noticed in the settings.ini file [Settings] /unattend: /noreboot: <<<switch don't accept any value, no need of : /makelocalsource: <<<switch don't accept any value, no need of : /syspart:C /tempdrive:c /s:%systemdrive%\winxp\i386 PEXP installer don't care if we use either /noreboot or noreboot: in [settings] in both case check box is selected but if we use /makelocalsource without the : the check box is unselected in winnt32.exe parameters Can you remove this little bug in the next version ?

Freeware shortcut.exe creates shortcuts from the command-line. download shortcut_1.00.zip Shortcut version 1.00 Creates, modifies or queries Windows shell links (shortcuts) The syntax of this command is: shortcut.exe /F:filename /A:C|E|Q /T:target /P:parameters /W:workingdir /R:runstyle /I:icon,index /H:hotkey /D:description /F:filename : Specifies the .LNK or .URL shortcut file. /A:action : Defines the action to take (Create, Edit or Query). /T:target : Defines the target path and file name the shortcut points to. /P:parameters : Defines the command-line parameters to pass to the target. /W:working dir : Defines the working directory the target starts with. /R:run style : Defines the window state (1=Normal,3=Maximized,7=Minimized). /I:icon,index : Defines the icon and optional index (file.exe or file.exe,2). /H:hotkey : Defines the hotkey. /D:description : Defines the description (or comment) for the shortcut. If Query is specified, all arguments except /F are ignored. An argument of /? or -? displays this syntax and returns 1. A successful completion will return 0. Copyright 2000 Marty List COPY, XCOPY, and MOVE Overwrite Functionality Changes in Windows MOVE Moves files and renames files and directories. To move one or more files: MOVE [/Y | /-Y] [drive:][path]filename1[,...] destination To rename a directory: MOVE [/Y | /-Y] [drive:][path]dirname1 dirname2 [drive:][path]filename1 Specifies the location and name of the file or files you want to move. destination Specifies the new location of the file. Destination can consist of a drive letter and colon, a directory name, or a combination. If you are moving only one file, you can also include a filename if you want to rename the file when you move it. [drive:][path]dirname1 Specifies the directory you want to rename. dirname2 Specifies the new name of the directory. /Y Suppresses prompting to confirm you want to overwrite an existing destination file. /-Y Causes prompting to confirm you want to overwrite an existing destination file. The switch /Y may be present in the COPYCMD environment variable. This may be overridden with /-Y on the command line. Default is to prompt on overwrites unless MOVE command is being executed from within a batch script.

If you don't want to install HP bloatware, i highly recommend to use the web download rather than the original CD. For the HP DeskJet 3600 series CD install adds this software : HP Memories disc HP Photo and Imaging Director HP print screen utility and probably other things without any separate uninstall utility... Nethertheless, another problem with the downloadable install. The drivers are not copied in the right path : i can find them in the root of the %systemdrive% instead of C:\Program Files\Hewlett-Packard\hpz\glue which is the right path... My last recommendation is to not install anything and create an self extracting archive to copy only needed files (driver) to the path mentionned before and add this path to the DevicePath in registry. After unattended Windows installation, we may install the printer by 1st plug the usb cable and power on the printer, 2nd power on the box and just click OK to accept installation of new detected hardware.

@mazin original not left ! but disable some features from being installed do not disable PnP detection. I just would like to find a solution that do not need to modify the msi each time HP release a new version of the software package. But it's probably not possible to do it full unattended with the non modified package. Another question, when i use my previous posted method and kill the msiexec process to avoid PnP detection, then go to look in the msi log file, i have found that the solution may be to disable GSI_InitiatePnP: That the process i kill. may it be possible to only disable this action instead of create new switches like the previous msi you have sent to me ? @cyberdiamond I have downloaded a software package from HP for your printer to have a look inside. Do the installation try to detect and install your photosmart printer during the process or do you install the software first and when the installation finish, then (maybe reboot) and plug the cable into USB for automatic detection ?