Fencer128

I think it's now pretty well established that the problem lies within the pack I wouldn't think that there's any need to post more confirmations. Andy

Hi, Turns out that apart from the driver issues with the board, the board also had a hardware issue. The board has been replaced and now happily RIS builds. However, above advice concerning drivers still applies. NOTE: Intel have recently released their 10.3 PROSet drivers. They have not yet released the "full pack" that contains the specialised RIS INF files though. As soon as they do I'll test them and let you know whther the driver problems that plagued this board with the 10.2 driver version have been fixed. Cheers, Andy

Hi Bashrat, In case you still had any doubts over the who gets this problem, I get the 'corruption' error too and I always build from fresh source. Cheers, Andy N.B. Using the workaround above has fixed the problem for me too.

Hi, RISult v1.1.6 now available. Didn't quite finish the necessary work in RISult 1.1.5 to get it working with DP Base 6.03.4. Now fixed. Cheers, Andy

Hi Bashrat, Sorry to mention the Sigmatel thing again but there's one more entry you forgot to delete from ...finish.cmd: MD "%ProgramFiles%\Sigmatel\C-Major Audio\WDM" The line above is unecessary as the Sigmatel driver INF file creates this folder itself. No manual creation is necessary. I've been testing it this way and everything works fine. Thanks for putting out the DPB update so quickly, Andy

Hi BTS, I'll check the reg changes - though I've been working off of 6.03.3 (and in fact have just downloaded 6.03.3 to check) and those INI file copy statements are still present for the ...finsh.cmd :DPSB4 section. I think they may still need deleting Cheers, Andy

Hi, I don't know about a utility that will take your exisiting install and package it up as an unattended ISO (except, as you've already pointed out, Ghost). I suspect that if you want a stand alone bootable ISO that installs windows + tweaks + applications (which is what I think you're after) then you'll need to create one from the source CD, and not from your current Windows installation. I suggest you visit this related site: http://unattended.msfn.org/unattended.xp/ Good luck Andy

Hi Bashrat, Intel have updated this driver from V2 to V6. I did a compare and there are some differences in some of the INI files. Please can you update at some point? You can download from: http://downloadfinder.intel.com/scripts-df...sional〈=eng Thank you for persisting with this. *** Please also see my post in the DP Base thread concerning changes to paths *** Cheers, Andy

Hi, Just checked my program files folder, and the INI files you specify for the Sigmatel driver in the ...finish.cmd are present when a previous DP base was used. As such, you can delete the following lines: MD "%ProgramFiles%\C-Major Audio\WDM" . . . COPY /Y %C%S\U\I3.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I3B.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I3BX.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I5.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I5B.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I5D.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I5D2.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I5D3.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL COPY /Y %C%S\U\I5_WHQL.INI "%ProgramFiles%\C-Major Audio\WDM" > NUL I also noticed that you had a couple of path errors: MD "%ProgramFiles%\C-Major Audio\STACGUI" COPY /Y %C%S\U\sttray.exe "%ProgramFiles%\C-Major Audio\STACGUI" > NUL COPY /Y %C%S\U\stlang.dll "%ProgramFiles%\C-Major Audio\WDM" > NUL Should read as below when "\Sigmatel\" is included: MD "%ProgramFiles%\Sigmatel\C-Major Audio\STACGUI" COPY /Y %C%S\U\sttray.exe "%ProgramFiles%\Sigmatel\C-Major Audio\STACGUI" > NUL COPY /Y %C%S\U\stlang.dll "%ProgramFiles%\Sigmatel\C-Major Audio\WDM" > NUL Let me know if you need any more info. I'm now going to try a build with the modified BTS base (paths corrected and INI file copies removed). EDIT: Built PC using above changes, and although CP applet installed and working, still no default sound scheme selected. I suspect that means that this is beyond the remits of the driver packs. I have also tried with the newset drivers (please could you update for next release? - see below), but same result. I will keep searching for a workable solution, but the remedy may lie outside the driver packs. Thank you for all your time and effort. *** Please also see my post in the Sound forum concerning new drivers *** Cheers, Andy

Hi Bashrat, Thanks for the experimental update to deal with the Intel Sigmatel applet . I will test this on Monday. One thing I did notice from looking at ...finish.cmd is that you've set a copy for the various driver INI files to the ...\WDM folder. These files were already being copied to that folder in the previous Sound B pack (due to the associated driver INF file). As such, I suspect that the copy statement in ...finish.cmd is an unecessary duplication. Anyhow, I'll test it for sure on Monday and let you know. Thanks for your efforts, Andy

Hi, Yes - you are right. On checking, my cleanup.cmd deletes that folder also. Cheers, Andy

Hi Bashrat, Sorry - maybe I wasn't clear in my posts (there were quite a few!). When the DriverPack is applied as is now, sttray.exe is not present after build has completed. When the Intel driver is downloaded and the installer is run manually: sttray.exe is never present in system32. It is only ever present in the above folder if the driver is manually installed via it's setup.exe Hope that makes it clearer. Cheers, Andy

.In a hurry so I'll keep it short The answer to the above question is - yes. Good luck, Andy

Hi, No problem - I have more time because I automate with RISult . RISult does not compile a SIF file - it does however edit the default "ristndrd.sif" file present in the "i386\templates" folder of your RISETUP image to add two entries to the [GUIRunOnce] section. As such, you will need to manually edit your ristndrd.sif file to include the above autologon entries, should you wish to use them. Cheers, Andy

Hi, I've seen this problem myself - and not just with RIS/RISult. It has been mentioned on the BTS forums. My solution is that I add an extra: command11=cleanup.cmd to the [GUIRunOnce] section of the SIF file. The cleanup.cmd I create just deletes the "%SystemDrive%\D" folder. This works for me. Sorry I can't be more specific. Cheers, Andy

Hi Bashrat, Please can you update Intel's PROSet drivers to v10.3? You can get them from here: http://downloadfinder.intel.com/scripts-df...ystems〈=eng Thanks, Andy

Can I check: Are you trying to update a file set that you previously slipstreamed driver packs into, or are you starting over with a new fresh source CD? What method are you using? Cheers, Andy

Hi, Assuming you're using RISETUP images (I can't recall if you do right now) I think you can narrow it down to one of the following: 1. You recopied the RIS files to the server but forgot to restart the BINLSVC 2. You have accidentally deleted/replaced the drivers in the i386 folder of the RIS image and now they are not present/don't work. 3. The RIS build has become corrupted and you need to delete it and recopy the files to the sever again (do you keep a mirror? 4. You have added so many drivers to i386 that the client/server connection times out after the BINLSVC has been restarted whilst the server is recompiling the PNF files. Solution is to try again in this case. There's probably something else but I can't think of it right now. Good luck, Andy

Hi, I'm not sure what you mean about the "sif file included with RISult" as I do not include a sif file with RISult Anyhow, I use auto logon myself. You need the following code present in your SIF file to produce one autologon after build completion: [GUIUnattended] AutoLogon = Yes AutoLogonCount = 1 Obviously you may have other options present under the "[GUIUnattended]" section, but this is all that is necessary for a successful once only autologon. Please let me know how you get on. Cheers, Andy

Hi, Did no one see flying lion's post on page one of this thread? Andy

Hi, Only other thing we can think of here - assuming your folder structure is correct and that the file copy fails exactly where you say it does, is that these files are in use when setup tries to copy them. Can you just confirm that the copy fails during the 2nd batch of file copies (that is with the progress bar on the screen) and not the 1st batch (where it says "Copying Files" at the bottom left of the screen). I know that's not much help (in fact it's probably no help!) but I can't think why else the copy fails. Good luck, Andy

Hi, It sounds as though you are using RIPREP images. RISult certainly doesn't work with this format - only with RISETUP (flat images). I believe AutoRIS is the same. If you have a RIPREP image containing Office 2003 and want to upgrade it you will need to do the following: 1. Install the build on a machine. 2. Add Office 2003 SP2 to the installation. 3. Reimage the PC to create a new RIPREP image containing Office 2003 SP2. You cannot just manipulate the image on the server as far as I am aware. In order to integrate network drivers into your RIPREP images you'll need to follow the methods outlined by Microsoft. Have a search of their site for RIPREP and drivers. In order to integrate Windows hot fixes you'll need to use the "/integrate" switch method. If you search the unattended forum you should find the detail you need. There are plenty of ways of creating an unattended ISO. I prefer using BTS Driver Packs and RyanVM Update packs. Have a search of the "Unattended" forum for more information. A much better way of avoiding all this unpleasantness is to move to a RISETUP image. However, this is not for everyone, particularly if you need to reimage a large number of machines simultaneously (i.e. using multicast type methods) and regularly. Good luck, Andrew

Hi, That's an odd one. Admittedly it's been a while since I used RIPREP (I stick to RISETUP because of issues such as these). I *guess* you're doing everything right - have you tried seaching for updated drivers? Sorry I can't be of more help with this. Maybe RogueSpear or cluberati can shed more light? Good luck, Andy

Hi, I'd have a look at this topic over at Ryan's forums: http://www.ryanvm.net/forum/viewtopic.php?...ug+play+monitor It *may* be something you need to take up over there. Cheers, Andy

Hi, Build has finished. Device manager sound entries are fine. Sound scheme still not selected by default - so no audio output. Manually selecting "Windows Default" sound scheme solves issue. stlang.dll is now only present in: %SYSTEMROOT%\System32 sttray.exe not present at all. I included all of the contents of the extracted Intel driver package this time, but the control panel applet is still not present installed after the build completes. Incidentally, the following folder is present: %SYSTEMDRIVE%\Program Files\Sigmatel\C-Major Audio\WDM It contains all of the INI files from the driver package. I hope that helps to clearly outline the issue. Let me know if you need anything else. Cheers, Andy