cslee Posted April 26, 2004 Share Posted April 26, 2004 I have create a custom unattended mode for WinXP SP1 CD.The $OEM$ is place in the root of the CD (CD-Drive:\$OEM$).I have place the cmdlines.txt inside the $OEM$ folder to execute some command but it seem like doesn't execute at all. Any ideals?P/S: I have enable the OEMPreinstall=Yes in the winnt.sif. Link to comment Share on other sites More sharing options...
killerbee Posted April 26, 2004 Share Posted April 26, 2004 hi,please provide us with more info1. post ur winnt.sif (remove Product key and passwords)2. post ur cmdlines.txt3. post everything that is called from cmdlinescyaKiller Bee Link to comment Share on other sites More sharing options...
cslee Posted April 26, 2004 Author Share Posted April 26, 2004 winnt.sif======;SetupMgrTag[Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes"[unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes TargetPath=\WINDOWS[GuiUnattended] AdminPassword=* EncryptedAdminPassword=NO OEMSkipRegional=1 TimeZone=215 OemSkipWelcome=1[userData] ProductID=AAAAA-AAAAA-AAAAA-AAAAA-AAAAA FullName="CSLEE" OrgName="CSLEE" ComputerName=CSLEE[RegionalSettings] LanguageGroup=7,8,10,11,9[identification] JoinWorkgroup=CSLEE[Networking] InstallDefaultComponents=Yescmdlines======[Commands]"regedit/s regtweak.reg""update.cmd"Please help ,I have try this so many times and the cmdlinex.txt command still not been executed !! Where can I find more information for RunOnce and hotfixes installation cause I have try the way they post to unattended install hotfixes but still could not success . Link to comment Share on other sites More sharing options...
Aaron Posted April 26, 2004 Share Posted April 26, 2004 Bad Command: regedit/s. Put a spacing between the regedit and /s....Is update.cmd in the $OEM$ folder as well? Link to comment Share on other sites More sharing options...
cslee Posted April 26, 2004 Author Share Posted April 26, 2004 I have type the Regedit/s mistakenly.The regedit command is as following:Regedit /s regtweak.reg ( have space between the regedit and /s)Yes,the update.cmd is in the $OEM$ folder as well also.Example======CD-ROM:\I386\CD-ROM:\$OEM$\update.cmdCD-ROM:\$OEM$\cmdlinex.txtCD-ROM:\$OEM$\regtweak.regcmdlinex.txt========[COMMAND]"REGEDIT /S regtweak.reg""Update.cmd" Link to comment Share on other sites More sharing options...
killerbee Posted April 26, 2004 Share Posted April 26, 2004 hi,it need to be cmdlines.txt and not cmdlinex.txtcyaKiller Bee Link to comment Share on other sites More sharing options...
cslee Posted April 26, 2004 Author Share Posted April 26, 2004 ok.it is cmdlines.txt.i have type mistanely.sorry for that.other than that .what can you see from the error that cause the cmdlines.txt not execute. Link to comment Share on other sites More sharing options...
[BM]Crusher Posted April 27, 2004 Share Posted April 27, 2004 can you even use regedit at that early stage?try "REG /IMPORT registry.reg"apart from that, as long as cmdlines.txt is in the $OEM$ folder, and the $OEM$ folder is in the right place, XP setup automatically runs cmdlines.txt and then as long as the .cmd files are in the $OEM$ dir as well, they will executemy guess: you haven't puy your $OEM$ folder in the right place or have used an incorrect syntax to tell winnt.sif where it is Link to comment Share on other sites More sharing options...
yourtech Posted April 27, 2004 Share Posted April 27, 2004 re: OemFilesPath="path"just out of curiosity what would the correct syntax be?The correct syntax isn't mentioned in MY ref.chm either. lol(I'm having a problem loading cmdlines.txt also but via a lan distribution folder)I moved it and put the path excluding the $OEM$ (as ref.chm says wants the location of the folder if it's not under i386) does that mean that if you move it you include or not include the $OEM$ in the path?maybe this'll help the guy/girl who started this thread also Link to comment Share on other sites More sharing options...
csaha Posted April 27, 2004 Share Posted April 27, 2004 It should be cmdlines.cmd and not cmdlines.txtTry and see if it workscsaha Link to comment Share on other sites More sharing options...
[BM]Crusher Posted April 27, 2004 Share Posted April 27, 2004 It should be cmdlines.cmd and not cmdlines.txtTry and see if it workscsahano, it is CMDLINES.TXT definitely!as for the OemFilesPath the correct syntax would be (copied directly from ref.chm)OemFilesPathSpecifies the path to the \$OEM$ folder (containing OEM files) if it does not exist under the i386 folder of the distribution share point.Syntax OemFilesPath =path_to_$OEM$_folder Value path_to_$OEM$_folder Example OemFilesPath = "%SYSTEMDRIVE%\OEM_Files"Comments The path can be a UNC name. Enclose path_to_$OEM$_folder in quotation marks if it is a long file name.For more information about the \$OEM$ folder, if you are a computer manufacturer, see the Microsoft Windows XP OEM Preinstallation Kit (OPK) User Guide. Otherwise, see the Microsoft Windows 2000 Server Deployment Guide.andOemPnPDriversPathSpecifies the path to one or more folders that contain Plug and Play drivers not distributed in Drivers.cab on the Windows product CD.Syntax OemPnPDriversPath = folder_1_on_system_drive[;folder_2_on_system_drive]... Values folder_1_on_system_drive[;folder_2_on_system_drive]... Example OemPnPDriversPath = MyFolder1; MyFolder2Registry subkey HKEY_LOCAL_MACHINE\Software\Microsoft\ Windows\CurrentVersion\DevicePath Comments The folders must contain all the files necessary to install the particular devices: catalog files, .inf files, and drivers.For example, if you have a folder called \Drivers with subfolders called \Audio and \Net, specify OemPnPDriversPath = drivers\audio;drivers\net in the Unattend.txt file. Setup adds:%SYSTEMDRIVE% to each of the folder names the path for each subfolder to the Plug and Play device search path. ImportantThe length of the OemPnPDriversPath entry in Unattend.txt must not exceed 4096 characters. You cannot use environment variables to specify the location of a folder. Always use signed drivers. Signed drivers make the operating system more stable and significantly reduce requests for product support. When using OemPnPDriversPath in Unattend.txt, be sure that the folders are available during GUI-mode Setup or the end user first-run experience. The easiest way to do this is to place the Plug and Play drivers in the \$OEM$\$1 folder. To prevent end users from inadvertently deleting driver folders located at the root of the drive, you can place drivers under the \$OEM$\$$ folder (for example: $OEM$\$$\PnP\Audio).If the drivers are not in the Drivers.cab file on the computer's hard disk or in the location specified by OemPnPDriversPath, Setup prompts the end user for the location of the drivers during the first boot of the machine, before Windows Welcome or Mini-Setup.You can also use the [PnPDrivers] section in Winbom.ini to update drivers on a previously-created image of the installed operating system Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now