Gaprofitt Posted May 1, 2006 Share Posted May 1, 2006 Hi All,I think I have everything setup correctly with RIS and need some help with theimplementation. I am getting the network driver could not be found for all mymachines. I'm positive i'm doing something wrong with the driver pack integration. I'vetried it on a bunch of Dell optiplex machines, gx260, gx270, gx280 etc all with the same error.I downloaded all the driver packs and placed them in the directory c:\autoris\bts. My imagelocation is on the same server on another drive. Do I need to run any of the other batchfiles before I run the autoris main .vbs file?Here is my ini file.[Paths]RISSERVER=datastore.decostar.decoma.comRISIMAGE=\\datastore\Reminst\Setup\English\Images\WindowsXPRVMEXE=RVM_Integrator_1.2.2.exenLiteEXE=C:\Program Files\nLite\nLite.exeVMwareEXE=C:\Program Files\VMware\VMware Workstation\vmware.exeVPCEXE=C:\Program Files\Microsoft Virtual PC\Virtual PC.exeBTSPATH=C:\autoris\btsBTSDPM=DriverPack_MassStorage_V6031.7z[Options]IntegrateNIC=NODelDefSIF=YesRunRVM=YesRunNlite=NoRunBTS=YesUseWMI=NoOptimize=NoOEM=YesEverything seems to run fine but I don't see any uncompressed drivers anywhere? Where should the included/modified SIF file be stored? Would that go in the templates directory? I think I am just missing a few steps to have this thing running. My understanding from the .ini text info I don't have to run anything with the driver packs except the autoris vbs file.Thanks for the help..Greg Link to comment Share on other sites More sharing options...
RogueSpear Posted May 2, 2006 Share Posted May 2, 2006 You need to decompress the BTS Base file and put your driver packs in the \DriverPacks directory as normal. Basically you want to have the DriverPacks ready to use as though you were going to use them in the intended fashion. So in your AutoRIS.ini file you should have something similar to this:BTSPATH=C:\BTS_DriverPacks_BASE_V6034AutoRIS does indeed perform most of the DP integration on it's own, but I made it grab the mass storage integration batch file, modify it on the fly (to future proof it), and then run that silently. Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 2, 2006 Author Share Posted May 2, 2006 (edited) It is now saying RIS is configured to intergrate the BTS Packs but is unable to locate the working directory. I changed the path to BTSPATH=C:\BTS_DriverPacks_BASE_V6034. The BTS_Driverpacks_base_v6034 is in C:\ and it's also uncompressed. The driverpacks are both in the in the driverpacks directory. I then tried changing it back to my original c:\autoris\bis. The BTS_Driverspacks is here, it's also uncompressed and the driverpacks are in the driverpacks directory. What am I missing?Thanks for your help, I'd kill to get this working.GregAtlanta Edited May 2, 2006 by Gaprofitt Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 2, 2006 Author Share Posted May 2, 2006 (edited) Update...Ok, I have all the driverpacks including the base install pack in c:\autoris\bts and this is reflected in the INI file. However it doesn't seem to work if I put the full path to the base file, I just did it to the directory c:\autoris\bts. I ran autoris.vbs and it completed all the tasks, I now have the compressed driverpacks in the \i386\$oem$ directory on my RIS server partitition? Is this correct? I tried a few systems and still gives me the network driver could not be found. I'm attempting Dell GX 260, 270 etc machines.Thanks for your help,Greg Edited May 2, 2006 by Gaprofitt Link to comment Share on other sites More sharing options...
RogueSpear Posted May 2, 2006 Share Posted May 2, 2006 $OEM$ should be at the same level as i386, not inside it. Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 3, 2006 Author Share Posted May 3, 2006 Been working at this all day, still no luck. When the drivers are slipstreamed into the install, are they uncompressed in a particular directory? I have the whole process working except for the driverintegration. Everything installed including the nic driver I placed into the nic_drivers directory withthe exception of all the other drivers. The vbs file seems to run fine but I feel the driversare not making it into the image.Any thoughts or suggestions? I have tried Nlite also which made me feel like the uncompressing of the drivers is the issue, it will not let me select the 7z files to implement them. Sorry this is frustrating and i'm not having much luck.Greg Link to comment Share on other sites More sharing options...
RogueSpear Posted May 3, 2006 Share Posted May 3, 2006 Integration of NIC and mass storage drivers for bootup in RIS is completely different than integration for the PnP enumeration stage of setup (during the GUI portion of setup). Now I'm not saying this as a slam or anything like that, but based on your previous posts it seems that you haven't read the AutoRIS instructions too thoroughly and you don't have to clear of an understanding of RIS or integrating device drivers. That's fine, we all have to start at the beginning. It was only about a year ago that I was struggling with this stuff too, but reading the instructions would have saved you a little bit of grief here.Now as best as I can tell you're doing most of this right. There should be a file in your AutoRIS directory named RogueSpearAddonsM2_1.3.cab. This is an addon for use with either the RVM Integrator or nLite. It places the files in i386 needed for a Method 2. It also makes changes to your txtsetup.sif and dosnet.inf files. Needless to say it's an integral part of a Method 2 with AutoRIS. Your DriverPack .7z files should be in $OEM$ and it sounds like you have this part down already. AutoRIS will copy WatchDriverSigningPolicy.exe and SetDevicePath.exe to $OEM$\$1. These are also necessary files as part of a Method 2 integration.If all of this stuff is in place, then your driver integration should work as advertised. Keep in mind that the DriverPacks are a project that will never be finished. There is an endless amount of hardware devices out there. So if something doesn't install here or there, that's to be expected. You may have to manually install the device later. I would highly suggest that you do a lot more reading here and over at Ryan's forums. For the most part this stuff isn't too difficult, but there is a lot to know. If you've gotten this far mostly on your own, figuring stuff out, then you should have no problems at all once you've caught up on reading about these things. Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 4, 2006 Author Share Posted May 4, 2006 No problem, I did read the documentation but feel I may be missing one step or overlooking something. How large will the new I386 directory be after integrating all the driver packs? Everything works great with the exception of the driverpacks. I know the drivers for the PC's I am using are included in the driver packs both for mass storage and network card, video, sound etc.. Now I am not running any of the slipstreaming batch files manually, I simply have the 7z files in my c:\autoris\bts directory. I just can't figure out why it's not decompressing them or should this be done manually before running the Autoris .vbs file.Here is a summary with my log file and my .ini file.INI FILE[Paths]RISSERVER=datastore.decostar.decoma.comRISIMAGE=\\datastore\Reminst\Setup\English\Images\WindowsXPRVMEXE=RVM_Integrator_1.2.2.exenLiteEXE=C:\Program Files\nLite\nLite.exeVMwareEXE=C:\Program Files\VMware\VMware Workstation\vmware.exeVPCEXE=C:\Program Files\Microsoft Virtual PC\Virtual PC.exeBTSPATH=C:\autoris\bts\BTSDPM=DriverPack_MassStorage_V6031.7z[Options]IntegrateNIC=NoDelDefSIF=YesRunRVM=YesRunNlite=NoRunBTS=YesUseWMI=NoOptimize=NoOEM=YesLOG FILE03-05-2006 22¦46¦14Log Startup @ 22:46:14 On 03-05-200622:46:14 - Running in Unattended Mode22:46:14 - 22:46:14 - Source Drive = C:\AutoRIS22:46:14 - Destination Drive = C:\AutoRIS22:46:14 - Destination Size = 21021.333007812522:46:14 - 22:46:14 - Starting Integration22:46:14 - Checking Destination For OS Type.22:46:14 - Windows XP Professional With SP2 Found22:46:14 - Clearing any Read Only Attributes.22:46:19 - Extracting RVMUpdatePack2.0.5.cab22:46:19 - MD5 Hash = 35DC41B2986BA996B9993884D0B1D72622:46:21 - Extracting RogueSpearAddonsM2_1.3.cab22:46:21 - MD5 Hash = F5EB9DFAFB3FBFAB1B49D11F2BA07BF722:46:21 - Gathering temp files22:46:22 - Compressing Files22:46:30 - Shifting Stuff Around22:46:30 - C:\WINDOWS\system32\cmd.exe /c xcopy /E /I /H /R /K /Y "C:\AutoRIS\i386\rvmtemp\extracted" "C:\AutoRIS\i386"22:46:33 - Analizing 2 Entry Files22:46:33 - Processing RyanVM Update Pack v2.0.5 Build Date: 04/11/200622:46:34 - Processing RogueSpear's Method 2 Helper v1.3 Build Date: 04/02/200622:46:34 - Editing Sysoc.inf22:46:34 - Adding Components22:46:34 - Editing svcpack.inf22:46:34 - removing obsolete hotfixes22:46:34 - adding ProductCatalogsToInstall22:46:34 - Editing dosnet.inf22:46:34 - Modifying any SP2.cab areas in dosnet.inf22:46:35 - Editing [Files]22:46:36 - Editing txtsetup.sif22:46:36 - Editing [Fileflags]22:46:36 - Editing [WinntDirectories]22:46:36 - Editing [sourceDisksFiles]22:46:36 - Modifying any SP2.cab areas in txtsetup.sif22:46:39 - Processing [EditFile]22:46:40 - obsolete_files Found in entries.ini22:46:41 - Entire .ini Processing Completed in 8 Seconds22:46:41 - Compressing and Moving Edited Files22:46:42 - Beginning Final Integration Steps. This Will Take Awhile.22:46:42 - Processing mmssetup.cab22:46:42 - Expanding mmssetup.cab22:46:42 - Processing entries.ini22:46:42 - Rebuilding mmssetup.cab22:46:44 - Rebuilding mmssetup.cab Complete.22:46:44 - Expanding driver.cab22:47:28 - Expanding SP2.cab22:48:01 - Processing entries.ini.22:48:03 - Rebuilding driver.cab22:53:48 - Rebuilding drvindex.inf22:53:49 - Rebuilding drvindex.inf Complete.22:53:49 - Moving Files22:53:49 - Cleaning Up.22:53:49 - Updating Home and Pro Specific Files22:53:49 - Replacing driver.cab22:53:51 - Integration is at 100%, Cleaning Up22:53:52 - Integration Completed.22:53:52 - Total Integration Time = 457 Seconds[Datastore File][Filenames]RVMUpPck.inf=entries.ini[Components]RVMUpdatePack=ocgen.dll,OcEntry,RVMUpPck.inf,HIDE,7[Remove_Components][ProductCatalogsToInstall]d3dx9_24.cat=RyanVM Update Packd3dx9_25.cat=RyanVM Update Packd3dx9_26.cat=RyanVM Update Packd3dx9_27.cat=RyanVM Update Packd3dx9_28.cat=RyanVM Update Packd3dx9_29.cat=RyanVM Update Packd3dx9_30.cat=RyanVM Update PackKB870981.cat=RyanVM Update PackKB873339.cat=RyanVM Update PackKB883523.cat=RyanVM Update PackKB883586.cat=RyanVM Update PackKB883667.cat=RyanVM Update PackKB884538.cat=RyanVM Update PackKB884575.cat=RyanVM Update PackKB884883.cat=RyanVM Update PackKB885626.cat=RyanVM Update PackKB885835.cat=RyanVM Update PackKB885836.cat=RyanVM Update PackKB885894.cat=RyanVM Update PackKB886677.cat=RyanVM Update PackKB886716.cat=RyanVM Update PackKB887170.cat=RyanVM Update PackKB887173.cat=RyanVM Update PackKB887472.cat=RyanVM Update PackKB887606.cat=RyanVM Update PackKB887742.cat=RyanVM Update PackKB888111.cat=RyanVM Update PackKB888113.cat=RyanVM Update PackKB888302.cat=RyanVM Update PackKB888321.cat=RyanVM Update PackKB889016.cat=RyanVM Update PackKB889315.cat=RyanVM Update PackKB889673.cat=RyanVM Update PackKB890046.cat=RyanVM Update PackKB890463.cat=RyanVM Update PackKB890644.cat=RyanVM Update PackKB890733.cat=RyanVM Update PackKB890831.cat=RyanVM Update PackKB890859.cat=RyanVM Update PackKB890927.cat=RyanVM Update PackKB892489.cat=RyanVM Update PackKB893008.cat=RyanVM Update PackKB893476.cat=RyanVM Update PackKB893756.cat=RyanVM Update PackKB893803.cat=RyanVM Update PackKB894395.cat=RyanVM Update PackKB895961.cat=RyanVM Update PackKB896256.cat=RyanVM Update PackKB896269.cat=RyanVM Update PackKB896344.cat=RyanVM Update PackKB896358.cat=RyanVM Update PackKB896360.cat=RyanVM Update PackKB896422.cat=RyanVM Update PackKB896423.cat=RyanVM Update PackKB896424.cat=RyanVM Update PackKB896427.cat=RyanVM Update PackKB896428.cat=RyanVM Update PackKB896626.cat=RyanVM Update PackKB897338.cat=RyanVM Update PackKB897649.cat=RyanVM Update PackKB897663.cat=RyanVM Update PackKB898439.cat=RyanVM Update PackKB898713.cat=RyanVM Update PackKB898900.cat=RyanVM Update PackKB899271.cat=RyanVM Update PackKB899418.cat=RyanVM Update PackKB899510.cat=RyanVM Update PackKB899527.cat=RyanVM Update PackKB899589.cat=RyanVM Update PackKB899591.cat=RyanVM Update PackKB900485.cat=RyanVM Update PackKB901017.cat=RyanVM Update PackKB901026.cat=RyanVM Update PackKB901122.cat=RyanVM Update PackKB901190.cat=RyanVM Update PackKB901214.cat=RyanVM Update PackKB902149.cat=RyanVM Update PackKB902841.cat=RyanVM Update PackKB902853.cat=RyanVM Update PackKB903234.cat=RyanVM Update PackKB904412.cat=RyanVM Update PackKB904942.cat=RyanVM Update PackKB905213.cat=RyanVM Update PackKB905414.cat=RyanVM Update PackKB905519.cat=RyanVM Update PackKB905749.cat=RyanVM Update PackKB905816.cat=RyanVM Update PackKB906216.cat=RyanVM Update PackKB906232.cat=RyanVM Update PackKB906472.cat=RyanVM Update PackKB906569.cat=RyanVM Update PackKB906650.cat=RyanVM Update PackKB906681.cat=RyanVM Update PackKB906688.cat=RyanVM Update PackKB906866.cat=RyanVM Update PackKB907265.cat=RyanVM Update PackKB907717.cat=RyanVM Update PackKB907865.cat=RyanVM Update PackKB907870.cat=RyanVM Update PackKB908519.cat=RyanVM Update PackKB908531.cat=RyanVM Update PackKB908536.cat=RyanVM Update PackKB908673.cat=RyanVM Update PackKB909441.cat=RyanVM Update PackKB909520.cat=RyanVM Update PackKB909608.cat=RyanVM Update PackKB909667.cat=RyanVM Update PackKB910437.cat=RyanVM Update PackKB910623.cat=RyanVM Update PackKB911262.cat=RyanVM Update PackKB911562.cat=RyanVM Update PackKB911564.cat=RyanVM Update PackKB911567.cat=RyanVM Update PackKB911904.cat=RyanVM Update PackKB911927.cat=RyanVM Update PackKB912024.cat=RyanVM Update PackKB912461.cat=RyanVM Update PackKB912784.cat=RyanVM Update PackKB912812.cat=RyanVM Update PackKB912817.cat=RyanVM Update PackKB912919.cat=RyanVM Update PackKB913296.cat=RyanVM Update PackKB913425.cat=RyanVM Update PackKB913446.cat=RyanVM Update PackKB913538.cat=RyanVM Update PackKB914028.cat=RyanVM Update PackKB914841.cat=RyanVM Update PackKB915428.cat=RyanVM Update PackMSXML3.cat=RyanVM Update Packscripten.cat=RyanVM Update Packxact20.cat=RyanVM Update Packxact21.cat=RyanVM Update Packxinput10.cat=RyanVM Update Packxinput11.cat=RyanVM Update Pack[Obsolete]d3dx9_24_x86=RyanVM Update Packd3dx9_25_x86=RyanVM Update Packd3dx9_26_x86=RyanVM Update Packd3dx9_27_x86=RyanVM Update Packd3dx9_28_x86=RyanVM Update Packd3dx9_29_x86=RyanVM Update PackKB319740=RyanVM Update PackKB842520=RyanVM Update PackKB884868=RyanVM Update PackKB887797=RyanVM Update PackKB888795=RyanVM Update PackKB889527=RyanVM Update PackKB891593=RyanVM Update PackKB891781=RyanVM Update PackKB892090=RyanVM Update PackKB892233=RyanVM Update PackKB892559=RyanVM Update PackKB896062=RyanVM Update PackKB896688=RyanVM Update PackKB896984=RyanVM Update PackKB897574=RyanVM Update PackKB898108=RyanVM Update PackKB899337=RyanVM Update PackKB900387=RyanVM Update PackKB900725=RyanVM Update PackKB900730=RyanVM Update PackKB900808=RyanVM Update PackKB900930=RyanVM Update PackKB902400=RyanVM Update PackKB904706=RyanVM Update PackKB905915=RyanVM Update PackKB907405=RyanVM Update PackKB909095=RyanVM Update PackKB909547=RyanVM Update PackKB910720=RyanVM Update PackMSXML3SP7=RyanVM Update Packxact_x86=RyanVM Update Packxinput9_1_0_x86=RyanVM Update Pack[Removable_Cats][Dosnet_Files]d1,RVMUpPck.inf=RyanVM Update Packd1,archvapp.inf=RyanVM Update Packd1,axaltocm.dll=RyanVM Update Packd1,basecsp.dll=RyanVM Update Packd1,bcsprsrc.dll=RyanVM Update Packd1,cobramsg.dll=RyanVM Update Packd1,d3dx9_24.dll=RyanVM Update Packd1,d3dx9_24.inf=RyanVM Update Packd1,d3dx9_25.dll=RyanVM Update Packd1,d3dx9_25.inf=RyanVM Update Packd1,d3dx9_26.dll=RyanVM Update Packd1,d3dx9_26.inf=RyanVM Update Packd1,d3dx9_27.dll=RyanVM Update Packd1,d3dx9_27.inf=RyanVM Update Packd1,d3dx9_28.dll=RyanVM Update Packd1,d3dx9_28.inf=RyanVM Update Packd1,d3dx9_29.dll=RyanVM Update Packd1,d3dx9_29.inf=RyanVM Update Packd1,d3dx9_30.dll=RyanVM Update Packd1,d3dx9_30.inf=RyanVM Update Packd1,DataStor.edb=RyanVM Update Packd1,guitrna.dll=RyanVM Update Packd1,hdaprop.dll=RyanVM Update Packd1,hdashcut.exe=RyanVM Update Packd1,hdaudbus.inf=RyanVM Update Packd1,hdaudbus.sys=RyanVM Update Packd1,hdaudio.inf=RyanVM Update Packd1,hdaudio.sys=RyanVM Update Packd1,hdaudres.dll=RyanVM Update Packd1,ifxcardm.dll=RyanVM Update Packd1,kbdbhc.dll=RyanVM Update Packd1,kbdiultn.dll=RyanVM Update Packd1,kbdnepr.dll=RyanVM Update Packd1,kbdpash.dll=RyanVM Update Packd1,LgtCkCtl.dll=RyanVM Update Packd1,migisma.dll=RyanVM Update Packd1,migwiza.exe=RyanVM Update Packd1,mmc30.dll=RyanVM Update Packd1,mmc30r.dll=RyanVM Update Packd1,mmcex.dll=RyanVM Update Packd1,mmcexr.dll=RyanVM Update Packd1,mmcfxc.dll=RyanVM Update Packd1,mmcfxcr.dll=RyanVM Update Packd1,mmcperf.exe=RyanVM Update Packd1,MRT.exe=RyanVM Update Packd1,msxml4.dll=RyanVM Update Packd1,msxml4r.dll=RyanVM Update Packd1,msxml5.dll=RyanVM Update Packd1,msxml5r.dll=RyanVM Update Packd1,msxml6.dll=RyanVM Update Packd1,msxml6r.dll=RyanVM Update Packd1,muweb.dll=RyanVM Update Packd1,pintool.exe=RyanVM Update Packd1,qfecheck.exe=RyanVM Update Packd1,scripta.dll=RyanVM Update Packd1,spcustom.dll=RyanVM Update Packd1,spmsg.dll=RyanVM Update Packd1,spuninst.exe=RyanVM Update Packd1,spupdsvc.exe=RyanVM Update Packd1,sysmoda.dll=RyanVM Update Packd1,update.exe=RyanVM Update Packd1,updspapi.dll=RyanVM Update Packd1,verclsid.exe=RyanVM Update Packd1,wups2.dll=RyanVM Update Packd1,x3daud1.dll=RyanVM Update Packd1,xact20.dll=RyanVM Update Packd1,xact20.inf=RyanVM Update Packd1,xact21.dll=RyanVM Update Packd1,xact21.inf=RyanVM Update Packd1,xinput10.dll=RyanVM Update Packd1,xinput10.inf=RyanVM Update Packd1,xinput11.dll=RyanVM Update Packd1,xinput11.inf=RyanVM Update Packd1,xpsp3res.dll=RyanVM Update Packd1,presetup.cmd=RogueSpear's Method 2 Helperd1,setupORG.exe=RogueSpear's Method 2 Helper[WinntDirectories]241=system32\PreInstall\WinSE\wxp_x86_0409_v1242=SoftwareDistribution\DataStore243=system32\en[sourceDisksFiles]RVMUpPck.inf=100,,,,,,,20,0,0archvapp.inf=100,,,,,,,111,0,0axaltocm.dll=100,,,,,,,2,0,0basecsp.dll=100,,,,,,,2,0,0bcsprsrc.dll=100,,,,,,,2,0,0cobramsg.dll=100,,,,,,,111,0,0d3dx9_24.dll=100,,,,,,,2,0,0d3dx9_24.inf=100,,,,,,,20,0,0,d3dx9_24_x86.infd3dx9_25.dll=100,,,,,,,2,0,0d3dx9_25.inf=100,,,,,,,20,0,0,d3dx9_25_x86.infd3dx9_26.dll=100,,,,,,,2,0,0d3dx9_26.inf=100,,,,,,,20,0,0,d3dx9_26_x86.infd3dx9_27.dll=100,,,,,,,2,0,0d3dx9_27.inf=100,,,,,,,20,0,0,d3dx9_27_x86.infd3dx9_28.dll=100,,,,,,,2,0,0d3dx9_28.inf=100,,,,,,,20,0,0,d3dx9_28_x86.infd3dx9_29.dll=100,,,,,,,2,0,0d3dx9_29.inf=100,,,,,,,20,0,0,d3dx9_29_x86.infd3dx9_30.dll=100,,,,,,,2,0,0d3dx9_30.inf=100,,,,,,,20,0,0,d3dx9_30_x86.infDataStor.edb=100,,,,,,,242,0,0,DataStore.edbguitrna.dll=100,,,,,,,111,0,0hdaprop.dll=100,,,,,,,2,0,0hdashcut.exe=100,,,,,,,2,0,0hdaudbus.inf=100,,,,,,,20,0,0hdaudbus.sys=100,,,,,,,4,0,0hdaudio.inf=100,,,,,,,20,0,0hdaudio.sys=100,,,,,,,4,0,0hdaudres.dll=100,,,,,,,2,0,0ifxcardm.dll=100,,,,,,,2,0,0kbdbhc.dll=1,,,,,,_x,2,0,0kbdiultn.dll=1,,,,,,_x,2,0,0kbdnepr.dll=1,,,,,,_x,2,0,0kbdpash.dll=1,,,,,,_x,2,0,0LgtCkCtl.dll=100,,,,,,,2,0,0,legitcheckcontrol.dllmigisma.dll=100,,,,,,,111,0,0migwiza.exe=100,,,,,,,111,0,0mmc30.dll=100,,,,,,,2,0,0,microsoft.managementconsole.dllmmc30r.dll=100,,,,,,,243,0,0,microsoft.managementconsole.resources.dllmmcex.dll=100,,,,,,,2,0,0mmcexr.dll=100,,,,,,,243,0,0,mmcex.resources.dllmmcfxc.dll=100,,,,,,,2,0,0,mmcfxcommon.dllmmcfxcr.dll=100,,,,,,,243,0,0,mmcfxcommon.resources.dllmmcperf.exe=100,,,,,,,2,0,0MRT.exe=100,,,,,,,2,0,0msxml4.dll=100,,,,,,,2,0,0msxml4r.dll=100,,,,,,,2,0,0msxml5.dll=100,,,,,,,2,0,0msxml5r.dll=100,,,,,,,2,0,0msxml6.dll=100,,,,,,,2,0,0msxml6r.dll=100,,,,,,,2,0,0muweb.dll=100,,,,,,,2,0,0pintool.exe=100,,,,,,,2,0,0qfecheck.exe=100,,,,,,,2,0,0scripta.dll=100,,,,,,,111,0,0spcustom.dll=100,,,,,,,241,0,0,spcustom.dll.refspmsg.dll=100,,,,,,,241,0,0,spmsg.dll.refspuninst.exe=100,,,,,,,241,0,0,spuninst.exe.refspupdsvc.exe=100,,,,,,,241,0,0,spupdsvc.exe.refsysmoda.dll=100,,,,,,,111,0,0update.exe=100,,,,,,,241,0,0,update.exe.refupdspapi.dll=100,,,,,,,241,0,0,updspapi.dll.refverclsid.exe=100,,,,,,,2,0,0wups2.dll=100,,,,,,,2,0,0x3daud1.dll=100,,,,,,,2,0,0,x3daudio1_0.dllxact20.dll=100,,,,,,,2,0,0,xactengine2_0.dllxact20.inf=100,,,,,,,20,0,0,xact_x86.infxact21.dll=100,,,,,,,2,0,0,xactengine2_1.dllxact21.inf=100,,,,,,,20,0,0,xact2_1_x86.infxinput10.dll=100,,,,,,,2,0,0,xinput9_1_0.dllxinput10.inf=100,,,,,,,20,0,0,xinput9_1_0_x86.infxinput11.dll=100,,,,,,,2,0,0,xinput1_1.dllxinput11.inf=100,,,,,,,20,0,0,xinput1_1_x86.infxpsp3res.dll=100,,,,,,,2,0,0presetup.cmd=1,,,,,,,2,0,0setupORG.exe=1,,,,,,,2,0,0[Txtsetup_Fileflags]AGT0406.DLL = 16=RyanVM Update PackAGT0406.HLP = 16=RyanVM Update PackAGT0407.DLL = 16=RyanVM Update PackAGT0407.HLP = 16=RyanVM Update PackAGT040B.DLL = 16=RyanVM Update PackAGT040B.HLP = 16=RyanVM Update PackAGT040C.DLL = 16=RyanVM Update PackAGT040C.HLP = 16=RyanVM Update PackAGT0410.DLL = 16=RyanVM Update PackAGT0410.HLP = 16=RyanVM Update PackAGT0413.DLL = 16=RyanVM Update PackAGT0413.HLP = 16=RyanVM Update PackAGT0414.DLL = 16=RyanVM Update PackAGT0414.HLP = 16=RyanVM Update PackAGT0416.DLL = 16=RyanVM Update PackAGT0416.HLP = 16=RyanVM Update PackAGT041D.DLL = 16=RyanVM Update PackAGT041D.HLP = 16=RyanVM Update PackAGT0816.DLL = 16=RyanVM Update PackAGT0816.HLP = 16=RyanVM Update PackAGT0C0A.DLL = 16=RyanVM Update PackAGT0C0A.HLP = 16=RyanVM Update PackBNTS.DLL = 16=RyanVM Update PackCGA40850.FON = 16=RyanVM Update PackCGA40WOA.FON = 16=RyanVM Update PackCGA80850.FON = 16=RyanVM Update PackCGA80WOA.FON = 16=RyanVM Update PackCOURE.FON = 16=RyanVM Update PackCOURF.FON = 16=RyanVM Update PackDOSAPP.FON = 16=RyanVM Update PackEGA40850.FON = 16=RyanVM Update PackEGA40WOA.FON = 16=RyanVM Update PackEGA80850.FON = 16=RyanVM Update PackEGA80WOA.FON = 16=RyanVM Update PackKBDNEC.DLL = 16=RyanVM Update PackMCHGRCOI.DLL = 16=RyanVM Update PackSAPICPL.HLP = 16=RyanVM Update PackSERIFE.FON = 16=RyanVM Update PackSERIFF.FON = 16=RyanVM Update PackSMALLE.FON = 16=RyanVM Update PackSMALLF.FON = 16=RyanVM Update PackSNIFFPOL.DLL = 16=RyanVM Update PackSPEECH.CHM = 16=RyanVM Update PackSSDPAPI.DLL = 16=RyanVM Update PackSSDPSRV.DLL = 16=RyanVM Update PackSSERIFE.FON = 16=RyanVM Update PackSSERIFF.FON = 16=RyanVM Update PackSSTUB.DLL = 16=RyanVM Update PackTSHOOT.DLL = 16=RyanVM Update PackUDHISAPI.DLL = 16=RyanVM Update PackUPNP.DLL = 16=RyanVM Update PackUPNPCONT.EXE = 16=RyanVM Update PackUPNPHOST.DLL = 16=RyanVM Update PackVGA850.FON = 16=RyanVM Update PackVGA860.FON = 16=RyanVM Update PackVGA863.FON = 16=RyanVM Update PackVGA865.FON = 16=RyanVM Update PackVGAFIX.FON = 16=RyanVM Update PackVGASYS.FON = 16=RyanVM Update Pack[Winntsif][Obsolete_Files]GWFSPidG.dll=RogueSpear's Method 2 Helperxact_x86.inf=RogueSpear's Method 2 Helperxacteng2.dll=RogueSpear's Method 2 Helperxinput9.dll=RogueSpear's Method 2 Helperxinput9.inf=RogueSpear's Method 2 Helper[ExtraFileEdits][EditFile][End_Of_Sections_EditFile_Entries_Below][Config INI Used][settings]UpdatePack=C:\AutoRIS\RVMUpdatePack2.0.5.cabAddonPacks=C:\AutoRIS\RogueSpearAddonsM2_1.3.cabSource=C:\AutoRISDestination=C:\AutoRISExternalRun=ParametersRun=IsoFile=IsoBinFile=IsoVolume=IsoExtTool=IsoExtCmd=IsoIntExt=InternalIsoCmdLine=mkisofs[switches]IKnowWhatImDoing=4[AddonPacks]RogueSpearAddonsM2_1.3.cab=C:\AutorisLog Shutdown @ 22:53:52 On 03-05-2006 Link to comment Share on other sites More sharing options...
Judge_MC1 Posted May 4, 2006 Share Posted May 4, 2006 Hey RS, hope the RSI hasn't caused you to many probs... how's the two finger typing going @GaprofittDude, you need to chuck the driverpacks into the C:\AutoRIS\DRV_Packs\DriverPacks folder (or your equiv) so that when the Method 2 BTS scripts run during AutoRIS it can find em, unpack em, and integrate em. Now dont get me wrong... I do think your on the right track... but go back and reread all the info on AutoRIS, Rogue's done a wicked job recently of making it fairly bomb proof.My C:\AutoRIS\DRV_Packs folder looks like this :C:\AutoRIS\DRV_Packs\C:\AutoRIS\DRV_Packs\BTS_DPs_autocopy.example.cmdC:\AutoRIS\DRV_Packs\BTS_DPs_Slipstreamer_V6034.cmdC:\AutoRIS\DRV_Packs\Readme.htmC:\AutoRIS\DRV_Packs\UpdateChecker_V60343.cmdC:\AutoRIS\DRV_Packs\DriverPacks\ <- DriverPacks are in hereC:\AutoRIS\DRV_Packs\FILES\Now this structure was created by running the BTS DP Base and copying to my AutoRIS folder, then copying the driverpacks into the C:\AutoRIS\DRV_Packs\DriverPacks folder. (making the relevent change to the .ini file)Work flawlessly (Thanks Rogue ) with Dell GX110, Dell GX200 (the only Dell's I have lying around at home). We have about 2500 Dell GX270s at work, but sadly they wont let me use AutoRIS or BTS' DriverPacks.... I might borrow a GX270 to test tho Link to comment Share on other sites More sharing options...
RogueSpear Posted May 4, 2006 Share Posted May 4, 2006 (edited) Judge did a way better job of explaining it than I ever could. And yes, typing with one hand and mousing with the same one hand is slowing me down a bit. Especially since Dragon is virtually useless when you're programming.EDIT: Looking back on it, I can see where my previous post would have made for some major confusion. The DriverPack .7z files should end up in $OEM$\$1 in your RIS image after AutoRIS is run. However, you will need for them to be where Judge described when you run AutoRIS. Edited May 4, 2006 by RogueSpear Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 4, 2006 Author Share Posted May 4, 2006 (edited) Hey Judge,Thanks for the Help.. I am assuming your BTS path in your ini file is C:\AutoRIS\DRV_Packs correct? I know Rogue had me pointing to the base pack at one time. I receive an error when pointing to the base pack in the path. It works when I just have c:\autoris\drv_packs in the bts path, however the i386 directory is only 612mb versus the i386-original is 653 mb. I didn't run Nlite to remove anything. It did move the 7z files into the path R:\RemoteInstall\Setup\English\Images\WINDOWSXP\$OEM$\$1. I still think it's not decompressing them, shouldn't this increase the I386 directory and not decrease it in size? I setupthe file structure just like you mentioned. How can I confirm or deny that the files are implemented forpnp detection.Once again I appreciate all the help.. I'm sure you guys get tired of the Autoris noobs.. Thanks,Greg Edited May 4, 2006 by Gaprofitt Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 5, 2006 Author Share Posted May 5, 2006 Hey All,I think I may be on to something. I'm on VPN from my house messing around with this again. I feel like i'm addicted now.. I think I may have it right now. Here is what I did.Renamed my current c:\autoris c:\autorisolduncompressed the original autoris install files to a clean c:\autoris directoryEdited the ini file, created the DRV_Packs directory and the Driverpacks subdirectory and put the packs in place. I then ran the batch file, nothing really looked different during the process except now I noticed on the RIS Server directory under $oem$\$1 I now have a ton of VBS files in here. I didn't have these before. I may be getting excited over nothing but maybe something in my original autoris directory was messed up.The VBS filenames start with 060 and go to 300, I didn't have these before..Can't wait to test it out, hopefully this will fix the issue. If this works I owe you guys a Beer if you are ever in Atlanta for all the help.Greg Link to comment Share on other sites More sharing options...
Judge_MC1 Posted May 5, 2006 Share Posted May 5, 2006 I'm on VPN from my house messing around with this again. I feel like i'm addicted now.. Yup, I was the same when I saw the versatility of the package The VBS files are the bits of AutoRIS that setup your PC during the installation of the OS from RIS (cmdlines.txt equiv) - it's well worth pulling them apart to learn how they tick as there is a wealth of information on how to do "cool sh!t" in them.I think you've prolly sussed it now, but just to make sure we are both on the same page lemme go through the steps I take to refresh my RIS image with AutoRIS.1. Extract the AutoRIS archive to C:\AutoRIS2. Run the BTS DriverPacks base to create the BTS DP folder structure and files3. Copy the BTS DP folder structure to C:\AutoRIS\DRV_Packs and the DriverPack_*.7z files to C:\AutoRIS\DRV_Packs\DriverPacks(at this stage I also copy any addon packs such as RogueSpearAddonsM2_1.3.cab (very important to include this if you want the driverpacks to work) to C:\AutoRIS\Addon_Packs so that I have everything I want to integrate in nLite in one place)4. Edit the AutoRIS.ini file appropriately (yep my BTSPATH=C:\AutoRIS\DRV_Packs)[Paths]RISSERVER=RISRISIMAGE=\\RIS\Reminst\Setup\English\Images\MC1_WINXPNICDRV=C:\AutoRIS\NIC_DriversBTSPATH=C:\AutoRIS\DRV_PacksBTSDPM=DriverPack_MassStorage_V6031.7zRVMEXE=RVM_Integrator_1.2.2.exenLiteEXE=C:\Program Files\!Utils\nLite\nLite.exeVMwareEXE=C:\Program Files\!Utils\VMware Workstation\vmware.exeVPCEXE=C:\Program Files\!Utils\Virtual PC\Virtual PC.exe[Options]IntegrateNIC=NoDelDefSIF=YesRunRVM=NoRunNlite=YesRunBTS=YesUseWMI=YesOptimize=NoOEM=Yes5. Edit the .sif file(s) I want to use (remove any you dont want to use)6. Edit the settings.ini file (see Rogue's Windows XP SP2 Post Install Script Pack for more info - recommended)6. Edit the nlite .ini file I use for nLite (not strictly required)7. Run AutoRIS.vbs and let it do its thing, which it does very well (note: I use nLite but you could just as easily use the RVM_Integrator)That's pretty much it (hope I havent missed anything out... I am writing it from memory). Let us know how you get on mate, if you have any probs attach an archived copy of your ini/sif files from the C:\AutoRIS directory if its not too big - minus any passwords that might be in them .If I am ever in Atlanta I'll hold you to that beer Link to comment Share on other sites More sharing options...
Gaprofitt Posted May 5, 2006 Author Share Posted May 5, 2006 (edited) Finally!! Somewhat of a success. Ran into a few issues listed below. I entered the local admin password into the .SIF file but I encountered this error.Setup was unable to change the password for user account Administrator.And I encountered these two errors.It looks like it is looking for a 3rd party Defrag tool.Windows Script HostScript:C:\150_DefragHD.vbsLine 76Char 4Error: The system cannot find the file specifiedCode:80070002Source=(null)Windows Script HostC:\190_SetNextBoot.vbsLine 133Char 2Error: The system cannot find the file specifiedCode:80070002Source=(null)not sure about this one..Here is line 133, Char 2ws.Run("ntregopt.exe silent /noprogresswindow /reboot"),1,TrueAnother than these issues everything worked like a champ.. Edited May 5, 2006 by Gaprofitt Link to comment Share on other sites More sharing options...
RogueSpear Posted May 5, 2006 Share Posted May 5, 2006 The third party utility usage is described in the script pack thread. I would distribute them with the script pack, probably in the form of an RVM addon, but the EULA for SysInternals just got rather restrictive. In the next Script Pack release and AutoRIS release I'll be setting the 500_Settings.ini file to not use them by default. This way users will have to read the directions and enable them on their own. 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