I'm cursed! - if I only well understand meaning of this :[ Change unattended.txt to that what are you used doesn't help. I'm missing something very simple ... I think. What program should execute command to uncompress the driver pack? Command also exist in $winnt$.inf it's anough or is it should be put in other place for running? Any ideas?
tovis > I'm confused a little, that you read my next post (it's also a little mess > with post theme - occasionally we switched to some wierd digest). > I stopped the process before graphical installer and after convert to > NTFS. > I found the compressed "drivers.7z" and whole stuff under directory entry: > c:\$win_nt$.~ls\$OEM$\ > under same directory entry, I have found another > c:\$win_nt$.~ls\i386\$OEM$\ > which is completelly empty!? > I can not realize any signs of running "DetachedProgram" with given > argument which is seem to me should unpack the driver pack, and show for > installer that the apropriate driver is ready for use - this mechanism is > complete dark woodoo for me. > I have also tried using a "pause" command in stead "FOR ..." stuff, > awaiting that process will stuck for wait some interaction - nothing was > happened. I simőply exclude /Q and /c switches suupose that I can see the > commands and used parametes, also cmd window would not closed - no way, > nothing was happen :[ > The only markable difference between your and mine unattended.txt, that al > is this driver unpack stuff placed on different highest inside the > "GuiUnattended" section - I will try! I'm also afraid that I'm using > hungarian version of XP prof SP2 - may be is it a slighly different? > Thanks for your answer and support, I badly need it. > > tovis > >> Unattended.txt is executed in the text portion of the install, which in >> turn sets up the graphical portion of the install of windows. During the >> install process, the installer will download all the files to the local >> hard drive in a random temp folder, this is when the drivers.7z is >> brought down to the local machine. Watch the text portion of the install >> closely, the Drivers.7z file should come down towards the end of the >> install counter. If I remember correctly, it's at about 85% or later. It >> takes a while to bring down since it's really large so you should have >> plenty of time to watch for it. If this doesn't happen, it means the >> setup on the file layout is incorrect and we'll need to check there for >> problems. >> >> If the file comes down and doesn't decompress shortly after the GUI >> portion of the install takes place you know you have a problem, >> somewhere in the unattended.tx because it did not set up the GUI portion >> correctly to execute the command drivers.cmd. >> >> >> Here's a copy of my unattended.txt file fronm the \LIB\ folder. >> >> ; General user information >> [UserData] >> >> [GuiUnattended] >> ; See <http://unattended.sourceforge.net/timezones.html> >> TimeZone=20 >> OEMSkipRegional=1 >> OemSkipWelcome=1 >> DetachedProgram = cmd.exe >> Arguments = "/Q /C FOR /F %? IN ('FINDSTR/B dospath= >> %SYSTEMROOT%\SYSTEM32\$WINNT$.INF') DO (SET %?\&& CALL START /MIN >> %dospath:\\=\%$OEM$\Drivers.cmd)" >> >> [Unattended] >> DriverSigningPolicy=Ignore >> UnattendMode=DefaultHide >> FileSystem=ConvertNTFS >> ExtendOemPartition=1 >> OemSkipEula=Yes >> OemPreinstall=Yes >> ; Needed for XP - see <http://support.microsoft.com/?kbid=294801>. >> UnattendSwitch=Yes >> >> [Data] >> AutoPartition=1 >> MsDosInitiated="0" >> UnattendedInstall=Yes >> >> [Display] >> BitsPerPel=32 >> Xresolution=1024 >> YResolution=768 >> Vrefresh=75 >> >> [LicenseFilePrintData] >> AutoMode=PerServer >> AutoUsers=5 >> >> [Networking] >> InstallDefaultComponents=Yes >> >> >> >> All required files for driver installation are located in the directory >> \os\xpsp2\i386\$oem$ >> >> >> tovis wrote: >>> I've run it again. >>> 1. No sings of starting the uncompress procedure. The screen ubnder >>> equipment/driver installation phase several times were blank, but >>> nothing was running. >>> 2. As it was supposed, it could not mount share without network >>> (driver), >>> when windows started first (and try to install perl). >>> 3. I have restart (as windows wants) and start exploring directories. >>> I have found C:\netinst\unattend.txt as it suppose to be. >>> I have found C:\windows\sysem32\$winnt$.inf where I'm found rows >>> of "DetachedProgram" and "Arguments" in section "GuiUnattended". >>> 4. I do not found any signs of existence of drivers directory >>> I386\$OEM$\ >>> and stuf to get drivers pack. >>> I'm still wondered about command arguments, especially for what >>> directory >>> passed to "CALL START /MIN %dospath:\\=\%$OEM$\drivers.cmd" part. The >>> %dospath, previously set to %SYSTEMROOT\SYSTEM32\$WINNT$.INF, but this >>> is a >>> file - I don't understand :[ Where the drivers.cmd should reside at >>> this >>> phase? All signs point that this command executed, but couldn't find >>> the >>> drivers.cmd, which is suppose (by me) to extract drivers. First I will >>> try >>> to be ensure that this "detached" command is really take controll. >>> >>> tovis >>> >>> >>>> I can not figure out point, when "driver install take place" :( I will >>>> >>> try > to catch it! >>> >>>> Citated "Argument" line is not broken to parts, it's on one line. >>>> Somewhat suspiciouse points (I have do not use so complex batch >>>> programming, as specially on one continouse line), FINDSTR command use >>>> >>> to > be closed by apostroph or "backward apostroph" '`, "/B" closely on >>> FINDSTR > command. >>> >>>> I was using sed to change all long filenames to sorten to 8.3 form, >>>> and >>>> also convert all fiklenames to lowercase (also check the result in >>>> drivers.cmd file). >>>> I thinking about try to put some "pause" command in the drivers.cmd, >>>> to >>>> hang the execution, if the control given to this command ever, and >>>> >>> trying > to debug the command execution - long way to success. >>> >>>> I wanna be charmed :D >>>> >>>> tovis >>>> >>> >>> >>>> The driver install should take place shortly after the prompt for >>>> >>> installing drivers takes place, decompression takes between 5 -20 >>> minutes You'll notice a small drivers.cmd text window that's minimized >>> if everrything is working correctly >>> >>>> the unattended.txt that you show looks ok to me, but it may have >>>> >>> problems if it's line broken on the arguments line try this all on one >>> line >>> >>>> Arguments = "/Q /C FOR /F %? IN ('FINDSTR/B >>>> dospath=%SYSTEMROOT%\SYSTEM32\$WINNT$.INF') DO (SET %?\&& CALL START >>>> >>> /MIN %dospath:\\=\%$OEM$\Drivers.cmd)" >>> >>>> Also are you running on linux?? If so the file names are case >>>> sensitive >>>> >>> so be careful of that. Drivers.cmd is not the same as drivers.cmd if >>> that is the way it's done per your duplication of your file list below >>> >>>> I just thought of something else, you changed the file names to the >>>> >>> correct names per the instructions, make sure that the correct names >>> are >>> also updated in the drivers.cmd file as well. I just checked the >>> original file and it referenced the original file names not the updated >>> 8.3 format ones. That will cause a problem when the drivers.cmd script >>> executes during the grapical install. I think this may be the culprit >>> of >>> your problem. >>> >>>> tovis wrote: >>>> >>>> >>>>> Yes, if you mean these changes: >>>>> [Unattended] >>>>> OemPreinstall=Yes >>>>> ... >>>>> [GuiUnattended] >>>>> DetachedProgram = cmd.exe >>>>> Arguments = "/Q /C FOR /F %? IN ('FINDSTR/B dospath= >>>>> %SYSTEMROOT%\SYSTEM32\$WINNT$.INF') DO (SET %?\&& CALL START /MIN >>>>> >>> %dospath:\\=\%$OEM$\Drivers.cmd)" >>> >>>>> long line batch command. Is there any diffeence where to put these >>>>> last >>>>> >>> one inside "GuiUnattended"? >>> >>>>> But I've really does not seen that window. I'm not sure beacuse I was >>>>> >>> not teasing on it, it is quite a long time this graphical install is >>> running. Would you be a little more precise on what phase it should >>> appear? May be some other script broken? What part of winows setup >>> should be care about this two rows - running cmd.exe on this batch, >>> given as an "argument"? >>> >>>>> tovis >>>>> >>>>> >>>>> >>>>> >>>>>> When you did your setup, did you make the edits to the >>>>>> unattended.txt?? >>>>>> >>> When your install runs you should get a small box about midway through >>> the graphical install portion of XP, this is where the install >>> >>>>>> decompresses and integrates the drivers. >>>>>> >>>>>> tovis wrote: >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> Thanks for quick answer :) >>>>>>> >>>>>>> I'm using instructions from "/Test Nr.1" link, as a result I have >>>>>>> >>> directory structure like this (on my share): >>> >>>>>>> Z:\os\winxpsp2\i386\$oem$ >>>>>>> 15.01.2008 14:31:46 A----- 489.472 7za.exe >>>>>>> 30.01.2008 12:29:58 A----- 341.137.117 drivers.7z >>>>>>> 15.01.2008 14:31:46 A----- 1.336 drivers.cmd >>>>>>> 15.01.2008 14:31:46 A----- 25.088 nircmd.exe >>>>>>> 15.01.2008 14:31:46 A----- 53.248 process.exe >>>>>>> 15.01.2008 14:31:46 A----- 20.992 setupinf.exe >>>>>>> 15.01.2008 14:31:46 A----- 3.584 watchdrv.exe >>>>>>> >>>>>>> Only one exlcusion that I used whole pack in drivers.7z (size about >>>>>>> >>> 783MB). Modify unattend.txt (titles [Unattended] and [GuiUnattended]). >>> What more "integration" you mean - slipstreaming? >>> >>>>>>> Also I'm try to find difference beetween "BTS Driver Packs/Test >>>>>>> Nr.1" >>>>>>> and >>>>>>> "BTS Driver Packs/Addendum" but I see only that test is using only >>>>>>> the >>>>>>> >>> part of drivers - may be I have should try first only the NICs >>> drivers? >>> >>>>>>> tovis >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Did you download the driver packs and integrate them into you >>>>>>>> install >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> source on your server?? >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> You have to follow the directions to the letter from the root >>>>>>>> document >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> above the one you referenced. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> http://ubertechnique.com/unattended/BTS_Driver_Packs >>>>>>>> There are several pieces that you have to download and copy into >>>>>>>> the >>>>>>>> >>> source installation as well. I wrote the addendum after trying to get >>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> this working for a few weeks and getting no where. Once I figured >>>>>>> it >>>>>>> out >>>>>>> it worked like a charm. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Some of the download links mentioned in the original text are >>>>>>>> invalid >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> now, so look at the addendum to get the proper links now. Use the >>>>>>> >>> links at >>> >>>>>>> the bottom of the first post (Download Mirror 1 or Download Mirror >>>>>>> 2) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Depending on what server your running follow directions for that >>>>>>>> server. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> I use a Windows 2003 Server so my guide is Windows Centric, but the >>>>>>> >>> directions you had a link for should do the same thing. >>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>> ------------------------------------------------------------------------ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> Subject: >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> [Unattended] Integration of BTV driver pack problem >>>>>>>>> From: >>>>>>>>> "tovis" <mailer.to...@freemail.hu> >>>>>>>>> Date: >>>>>>>>> Wed, 4 Feb 2009 20:23:52 +0100 (CET) >>>>>>>>> To: >>>>>>>>> unattended-info@lists.sourceforge.net >>>>>>>>> To: >>>>>>>>> unattended-info@lists.sourceforge.net >>>>>>>>> Hi! >>>>>>>>> I'm using unattended 4.8 (release I can not figure out) on Linux >>>>>>>>> server >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> (Debian Lenny). >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> Usuall unattended installation work fine. >>>>>>>>> I can not integrate BTV driver pack, as it described here in the >>>>>>>>> wiki: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> http://ubertechnique.com/unattended/BTS_Driver_Packs/Test_Nr%2e1 I >>>>>>> can >>>>>>> >>> not >>> >>>>>>> find any signs of driver pack copied/installed on path c:\drivers >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> I have no ideas to figure out where is the process is stucking. >>>>>>>>> Any >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> help would be highly apreciated. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>>> tovis >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> -- >>>>>>>> Christopher Rector, MCSE >>>>>>>> Computer Information Specialist >>>>>>>> Southern Illinois University >>>>>>>> School of Medicine >>>>>>>> Department of Ob/Gyn >>>>>>>> 217-545-9182 >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >>> >>> >>> >> >> -- >> Christopher Rector, MCSE >> Computer Information Specialist >> Southern Illinois University >> School of Medicine >> Department of Ob/Gyn >> 217-545-9182 >> >> > > > > > ------------------------------------------------------------------------------ > Create and Deploy Rich Internet Apps outside the browser with > Adobe(R)AIR(TM) > software. With Adobe AIR, Ajax developers can use existing skills and code > to > build responsive, highly engaging applications that combine the power of > local > resources and data with the reach of the web. Download the Adobe AIR SDK > and > Ajax docs to start building applications > today-http://p.sf.net/sfu/adobe-com > _______________________________________________ > unattended-info mailing list > unattended-info@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/unattended-info > > ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
