Fencer128

Hi, If anyone is interested in using a batch file to automatically integrate RIS risetup installs with RyanVM and/or BTS packs then please check out the following topic: http://www.msfn.org/board/index.php?showtopic=57010 Thanks, Andy

Hi Everyone, I have been having lots of fun recently with RIS, RyanVM update packs and BTS driver packs. The result is that I realised that creating an unattended and fully integrated RIS risetup build that will install on most systems requires many tweaks/steps. Now, given I like a bit of a project (it feeds the geek in me! ) I've spent the past month creating a batch file that does the following: 1. Converts a vanilla risetup i386 file set to fully resemble a CD based file set 2. Edits BTS batch files for unattended use 3. Integrates RyanVM's update packs 4. Integrates BTS's driver packs 5. Edits BTS batch files for RIS install 6. Converts the file set to fully resemble a risetup file set 7. Removes uneeded files I've, rather cheesily, called the file "RISult" - mainly because I can't think of anything better! For anyone that uses RIS on a daily basis, or has tried integrating RyanVM's and/or BTS's packs for RIS manually, this will hopefully prove to be very useful. I have tested this a fair bit but welcome observations and suggestions as I wish to update the file regularly. I have compiled a "to do" and "known issue" list, and will update as I can. To do: - Rewrite RISult using VB Known Issues: - None RISult can be downloaded via: Link removed as now as way out of date. If you need this please PM me. Thanks. Please note, the following information is contained within RISult.cmd and is reproduced below for reference. Please read before use!!! Please BACK UP your system/RIS files BEFORE use! Although this file has been successfully tested, please realise that you use it AT YOUR OWN RISK! This file is FREEWARE and can be used by anyone for any purpose Tested with Windows 2003 Server (Standard and Enterprise) SP1, Windows XP Professional SP2 and RIS Only the BTS method 2, GUIRunOnce, KtD=No configuration has been tested (RISult executes these options by default) Only paths/filenames with no spaces in them have been tested This script assumes that: All initial files come from official, vanilla Microsoft VLP media with latest service pack slipstreamed Risetup.exe has been used to copy up a vanilla Windows XP Professional SP2 CD to your RIS server The i386 folder from the above has been copied to a local directory You have ROBOCOPY installed on your PC (i.e.Install Windows Server 2003 Resource Kit) The USER CUSTOMISABLE SECTION of the batch file below has been edited to suit your system When all is done you will edit or replace the i386\templates\*.sif file yourself You will need to restart the binlsvc service after batch file completion RISult - a batch file for creating RIS compatible integrations Last successfully tested with: RyanVM Integrator Version: 1.2.2 RyanVM Update Pack Version: 2.0.5 BTS Base Pack Version: 6.03.4 RISult would not work without the significant effort of others Please see the CREDITS section within for full acknowledgements Version 1.1.7 (24/03/06) Written by: Andrew M Woodman - AKA Fencer128 (http://www.msfn.org and RyanVM forums) IMPORTANT! - Before continuing Please make sure you have: ECHO 1. Read and understood the statements at the top of the batch file ECHO 2. Edited the "USER CUSTOMISABLE SECTION" at the top of the batch file Please can people test it and let me know how it goes. Good luck! Andy EDIT: RISult has been updated. See included changelog for full details: Download from: Link removed as now as way out of date. If you need this please PM me. Thanks.

Hi, I think the issue is now solved (well a work around corrects it any how!) The problem was not with BTS DPs, it was with RISETUP's creation of 2 intel .sys files. These files were compressed in my RIS i386 folder, but their updated (10.1) and identically named couterparts were uncompressed in the same location. During setup the new .inf file was getting used with the old .sys file and this appears to be the problem. Removing these 2 compressed files solves the issue. Thanks, Andrew

Hi Bashrat, Thanks for the reply. I am using the latest LAN driver pack. I am using version 10.1 of the intel proset drivers (I updated all of the intel drivers in the DP from 10.0 to 10.1 by replacing files on a like for like basis) The drivers in the RIS\i386 directory (the ones that are used during text mode setup) are the v10.1 type. I will soon try using v10.0 in i386 to downgrade the text mode drivers to see if this fixes the problem for this platform. I've also just noticed that the hardware is not identical. The working box uses an Intel Pro/1000 MT on board solution. The problem box (although newer) uses an Intel Pro/100 VE on board solution. I will investigate further and if still have no joy will post the necessary hardware details. Regards, Andy

Hi, Thanks for the reply. I imagine that means that there is possibly a problem with the execution of the fake setup.exe when used via RIS with certain NIC/Chipset/Processor platforms then. My integration is standard VLP Win XP Pro SP2 + Ryan (inc. both add on packs) + all BTS packs. Does anyone happen to know who writes the code for the fake setup? Also, could someone point me to the part of the BTS batch file that restores the real setup.exe (I can't see it anywhere)? I would like to know at exactly what part of the installation this occurs as it could be the source of one outstanding issue. EDIT: Appears problem is related to Intel drivers after all, as when 3com card used there is no problem. Not sure why driver works with hardware on one PC and not another. Possible hardware revision problem. Anyhow, I will investigate further - no need to chase up setup.exe after all. Thanks again, Andy

Hi, I'm currently producing a batch file to help people perfoming RIS integrations using RyanVM and BTS packs. One of this issues I'm having concerns the "fake" setup.exe inserted by the BTS pack. Please could someone explain to me: 1. What the need for the fake setup.exe is (what needs to be altered from the standard file)? 2. Where to obtain a newer version of this file, if at all possible or necessary? 3. Whether this file is executed at the end of the first part of the text mode RIS setup (i.e. at the point after the MS drivers have loaded where is says "Setup is starting Windows...")? - I ask because currently on certain hardware platforms (Intel 915GUX, Pro 100/VE, Pentium 541 EM64T capable) the RIS install blue screens directly after this point quoting "unable to initialise network boot". I know it is not a NIC driver issue because other, older platforms (845/865 chipset) with the same NIC hardware and drivers work flawlessly. I appreciate that some of the answers may be unknowns, but any help would be gratefully received. For anyone interested in the progress of the batch file, it's 90% ready. If I can iron out the 2 remaining problems it should be ready to go in a week or so. Thank you, Andy

Hi, My mistake! Well... it's particular to the way I set up my RIS build! Once I's compressed a couple of key files everything worked fine (these files are usually compressed and I needed to expand them to perform some operations on them). Thanks, Andy

Hi, I'm currently using RIS to install a build of XP with Ryan's and BTS's packs slipstreamed. Previously I've not had any big issues - but I've currently got one that has me stumped. The machine in question is an intel 915GUX motherboard. When the text mode setup is executing it gets to loading the Promise MS drivers and hangs with: "File aftx2k.sys caused unexpected error (21) at line 3540 in d:\xpsprtm\base\boot\setup\setup.c" I thought it weas a Promise driver problem so went to remove the offending driver. However, although I see the mention to this file in txtsetup.sif, I can't find it in the "P" folder of the MS pack (nor can I find it in i386). Am I missing something here? I don't believe this problem is particular to RIS builds. EDIT: Should say that there is no Promise hardware in this PC (though there may be on other boxes I build). If anyone has any advice I'd be very grateful. Thanks, Andy

Hi, Thanks for the reply. I'll be sure to grab the latest version of your fedit. Cheers and good luck with the job, Andy

Mis-post. Sorry! Andy

Hi, If I use this: FEDIT -ADD -ONCE -F %BTS%\BTS_DPs_auto.example.cmd -A "%%CD%%\FILES\ROBOCOPY \"%%FOLDER%%\" \"%%UWXPCD%%\" *.* /E %%RS%%" -L "%%RUNFROM%%\FILES\ROBOCOPY "%%FOLDER%%" "%%UWXPCD%%" *.* /E %%RS%%" and insert / before " then I can get the text placed in the correct place. The only small issue remaining now is if it is possible to keep the "" around the variables in the pasted text... EDIT: Escaping the " in the text to be pasted as is done above for the searched for text gets the job done 100% FEDIT -ADD -ONCE -F %BTS%\BTS_DPs_auto.example.cmd -A "%%CD%%\FILES\ROBOCOPY \"%%FOLDER%%\" \"%%UWXPCD%%\" *.* /E %%RS%%" -L "%%RUNFROM%%\FILES\ROBOCOPY \"%%FOLDER%%\" \"%%UWXPCD%%\" *.* /E %%RS%%" Solved! Cheers, Andy

Hi Chad, I think that with a little cunning and what you've developed so far, I may be able to get the job done anyhow. It might be just enough. Thank you for your time, Andy

Hi Chad, I tried it and got: "The system cannot execute the specified program". I don't know if I've done something wrong or if the command line just won't work that way. Thanks again, Andy EDIT: Should have also said, not sure it's that important, but trying the first method you posted also resulted in the "" being missing from around %FOLDER% and "%UWXPCD% that were added to the bottom of the text file. Thanks.

Hi Chad, Thanks for the info. Using the command line you supplied has 2 effects: 1. The correct text is entered into the text file. 2. The text is entered at the end of the file, rather than directly after the line referenced by the -A switch. I suspect this is to do with the way in which fedit parses "%%CD%%\FILES\ROBOCOPY "%%FOLDER%%" "%%UWXPCD%%" *.* /E %%RS%%" with the extra escape characters in it. Now, if the extra %s are removed then the command fails with a syntax error. I guess I still need to work on point 2. Thanks again, Andy

Hi, I'm working on a batch file that alters the contents of a couple of text files as part of its operation. I use the "Fedit" utility (picked it up from Bashrat's Driver Packs) to edit the text. I'm having a problem editing a couple of lines of text that contain escape characters. I do not know if there's an easy way round this, but since my batch file expertise is far more limited than some people's around here I thought I'd try begging! Here is the pertient part of the text file that will be edited: ... %CD%\FILES\ROBOCOPY "%FOLDER%" "%UWXPCD%" *.* /E %RS% ... Here is an example of the type of batch file operation that is causing me hassle: FEDIT -ADD -ONCE -F %BTS%\textfile.cmd -A "%CD%\FILES\ROBOCOPY "%FOLDER%" "%UWXPCD%" *.* /E %RS%" -L "%RUNFROM%\FILES\ROBOCOPY "%FOLDER%" "%UWXPCD%" *.* /E %RS%" The syntax of Fedit expects: FEDIT -ADD -ONCE -F <filename> -A "<line of text>" - L "<line of text>" The operation should result in the text following -L to be added directly underneath the line following -A The problem appears to be the prescence of % and " in the command line. I've tried removing the extra quotes, using /" and /% but nothing works correctly. Does anyone have a way around this? Thank you, Andy

Hi, Just to let you know - I'm having exactly the same issue using method 2 and the new RyanVM packs (full + addons + WMP10). I have an Intel 915GUX ALC860 based MB. I suspect it's not to do with the dosnet.inf and txtsetup.inf entries. I always delete the duplicates inserted by the driverpack slipstreamer though. I suspect it's something to do eith the operations carried out on the 888111 files during the execution of RUN_ME.bat. For a start, the detection of whether the 888111 has already been installed will fail as it depends on finding the 888111.cat file. Ryan's packs no longer include this so even though they integrate the patch, the RUN_ME.bat file will not detect this. I remember seeing another thread on this forum concerning this issue. I shall investigate there too. It may just be a simple matter of changing the file used to carry out the detection in the RUN_ME.bat file. To be honest, I haven't yet taken the time to fully understand why the operations in the 888111 files occur in the batch file. When I understand this I'm sure the problem will become obvious. Cheers, Andrew ps Just read on Ryan's forum that he intends to put the KB888111.cat file back into the next version of his pack. I suspect that means that everything will then work fine.

Hi, If you were to update the b57 driver, could you please also update the b44 driver? The latest version is 4.37.0.0 (05/08/2005). It can be obtained from the braodcom site (see link in posts above). Thank you, Andrew

Hi again, Could I please make one other request? To add the new Dell SigmaTel STAC 92xx C-Major HD 5.10.0.4568 A02 driver? It can be found here: Dell SigmaTel Audio driver It is required by my Dimension 9100. Thank you again! Andy

Hi Bâshrat, Before I make a request, can I say how grateful I am that you've gone to the efforts you have to create these driver packs. They make life so much simpler for me (and I guess a lot more people too from reading the forums!) I have a Dell Optiplex 620 that I'm trying to get an unattended install working with. I also have a couple of other machines with different sound hardware on board. Up shot is that I use both sound driver packs to create one cd that I then use to build all my machines. In common with lots of other people, I have experience of the portcls.sys error. In this case on the Optiplex 620. In light of this, I was wondering if you could possibly integrate the newest Dell audio drivers that are now available to support the 620? The link is here: Dell ADI 198x 5.12.01.5246 A23 device driver Currently the older A21 version is included in your driver pack. Thank you for your time and effort - it is much appreciated, Andy

Hi, Thanks for the reply. After the image has been deployed I can quite happily use "Update Driver" in the device manager and point it at a directory specified in the HKLM\...\Devicepath key and it installs without issue. No setup.exe needed. Thanks, Andrew

Hi, The drivers are WHQL signed. There are no native drivers for the video or audio hardware. Excepting the NIC, I do not install any OEM drivers onto the PC used to make the riprep image. As such, I would expect the audio and video drivers to be installed at the very least. Thanks, Andrew

Hi, Thanks for the reply - I had a look at MS knowledge base articles 246184 (How to add thrid-party OEM network adapters to RIS installations) and 314479 (How to add OEM plug and play drivers to Windows XP) and I can't find any reference to dosnet.inf. A quick google search seemed to suggest it was used when applying software updates that use update.exe and not searching and installing drivers. See MSKB 828930 (How to integrate software updates into your Windows installation source files) Thanks, Andrew

Hi All, Here's a quickie for you - I want to deploy a Windows XP riprep image to several thousand clients using a 2003 RIS server. All the clients are PXE bootable (I actually have three different riprep images to encompass all HAL types we use). I use a sysprep.inf file in the c:\sysprep directory of the pc used to compose the riprep image. The sysprep.inf file contains the path to the oem WHQL signed driver files I wish to use: [unattended] OemPnpDriversPath=Drivers\C\I;\Drivers\V\I;Drivers\A\I\845;Drivers\A\I\865;Drivers\A\R;Drivers\L\I\100;Drivers\L\I\1000;Drivers\L\I\XGB The drivers are located in C:\Drivers\... I run riprep to copy the image to the RIS server and update the registry with the driver path from the sysprep.inf file. Excepting the NIC driver, no other OEM drivers are installed (native drivers do not exist for the video or audio). We edit the riprep.sif file accordingly to set the product key, language, resolution, etc. outside of what has been set in the image. When I deploy the image to a client everything is as it should be except for the fact that the OEM drivers are not being used. The .sys and.inf files for each driver are located in the folders specifed within the path. Not all clients use the same drivers and so those included encompass all circumstances. I cannot think what I'm missing and would appreciate any help anyone has to offer. Thanks, Andrew ps - For reasons of system administration I cannot yet gain complete control over group policy - it's a public sector organisation - hence the need for pre-configured riprep images and not RIS CD installs and group policy. pps - I realise that network drivers are a seperate issue and I will deal with those accordingly after tackling this problem. I have already copied the .sys and .inf files to the CD install on the RIS server and into the i386 directory of the image as well as restarting the binlsvc service.