Fencer128

Hi, You are correct in your assumption. I am not able to verify your behaviour as I do not have access to that particular hardware. It doesn't sound like a RISult or RIS specific issue though. Good luck, Andy

Hi Bashrat, Having manually run the Intel installer for this driver I can tell you the following file locations: sttray.exe is present in: %SYSTEMDRIVE%\Program Files\Sigmatel\C-Major Audio\STACGUI stlang.dll is present in: %SYSTEMDRIVE%\Program Files\C-Major Audio\WDM %SYSTEMROOT%\System32 The only other locations for this file are the temporary extraction folder used by the Intel installer. I hope this is the information that you require. I am currently testing a build with the *entire* driver file set added into a customised Sound_B DP - I'll post the results as soon as I have them. Cheers, Andy

Hi, The concerns (I think that's a better word than problems from our point of view ) that we have with .NetFW is two-fold: 1. We would need to roll it out to all our existing clients (2000 of them), so that would require a lot of - as yet - unecessary testing and work. 2. If we integrate it into the build we would have to be very sure that everything has integrated correctly (and as yet I'm not convinced that the community has had enough time and experience with the various add on packs to confirm this for our needs) and that we can update the file set with MS patches distributed through WSUS/SMS as and when MS release them (more work to test!). Because of the above we currently disable the ATI CCC from installing on all of our integrated builds. Hope that clarifies the sceptic point of view Cheers, Andy

Hi, I would do a build with only RyanVM Update pack integrated (presuming you're using RyanVM packs!) to check if the issue is related to this - as I've certainly heard of this happening outside of RIS (and therefore do not think it is specific to either RIS or RISult). If you're not using the RVM pack then then try leaving out the BTS packs too. Let me know how it goes. Cheers, Andy

Hi Bashrat, I'll double check for sure - but at the moment I've copied *all* of the driver files to the appropriate Driver Pack folder and the result is that: 1. Device Manager appears correct, but no sound scheme is selected by default. Manually selecting the sound scheme gets everything working normally. 2. No control panel applet is present in the system tray. I originally thought that your view of the panel applet installing via the INF/INI files was correct, but as you can tell from the above, it still does not install . I will look out the location of those files for you tomorrow and report back. I will also give it one last try, copying all of the files again from scratch in case I messed something up previously. I'll post the result here straight afterwards. Please don't do anything until I post as I don't want you wasting your time if the problem gets resolved. If there's no change after this final experiment, then I hope that installing the applet through ...Finish.cmd will solve the problem, as I wouldn't want you going to extra work only to discover the issue remains open. I'm happy to consider other possibilities - but can't think of any at the moment. Thanks , Andy

Hi, Personally I'd like to see the CP, as we don't roll out .NetFW by default. However, I also realise that this is but a temporary step - as I doubt ATI will abandon .NET now they've moved their primary release to it, and at some point in the future they're bound to give up supporting both panels. Given all of this I vote for CCC as although it's a bit of an awkward, painful step - it's something we need to accept and get on with. Cheers, Andy

Hi, The only reason I labelled it "Printers" instead of HP was because initially I created it for my own personal use, and that is almost exclusively HP. Of course, there's nothing to stop it being relabelled as required. Cheers, Andy

Hi, You're right - the snow WAS fun (drove from Cumbernauld to Dundee on Sunday evening). I had a look at your folder structure, and there are a couple of things that you do - that I don't. Since I do not have the problem you do, we can assume that the problem could lie with the extra processes associated with these folders. They are: $$ | |--oemdir | |--Resources | |--System32 | |--dllcache $1 | |--Install | |--Apps | |--dotNet | |--Firefox I will assume that simple file placements should be fine - which leaves the .NET and Firefox installs. I suspect that one or other of these is not terminating or completing correctly and is leaving temp/working files. Could you try building without these to see if you can isolate the problem? If the problem disappears then try with each in turn to see which is causing the issue. If removing them does not fix the problem then we should look at the contents of your .CMD files next. Good luck, Andy

That's it. There are some more elaborate solutions available if you want to restrict access to certain builds to specific AD security groups, but it involves diverging slightly from the default OSC model (creating new OSC files, folders and adapting a few more file permissions). Cheers, Andy

Hi, I realise that the instructions need updating and will be doing that in due course . It does however say: The BTS DriverPack BASE, along with any other optional driver packs you wish to integrate, should be placed within the BTS folder. In the meantime, to cut a long story short, you should have extracted DP Base into the BTS folder: C:\Unattend\RIS --- ¦ ¦--- BTS ¦ You should then place the DPs you want use into the "DriverPacks" folder. Then run "BTS_DPs_Slipstreamer_Vxxxx.cmd", choosing method 2. If you then follow the rest of the RISult instructions everything will be fine. There is no need to do anything else with the BTS files from the perspective of getting it working with RISult. Good luck, Andy

Hi, I've used all of those packs - as well as the latest ones - with Intel (Sigmatel and Realtek) HDA without issue. I have to say that I always integrate RyanVM update pack too. Cheers, Andy

Hi, Given that you're using RISETUP, I really don't know why you're seeing that file - I certainly don't. Could you post a brief synopsis of the contents and paths in $OEM$, as well as any post install scripts that you run. Posting your SIF file could be useful too - so long as you remember to blank your password and product keys. Cheers, Andy EDIT: Changed RIPREP to RISETUP above. I meant it - but rushed my typing

Hi, Do you mean: "What is the best way to allow only certain people to log on to a RIS server through PXE booting?" or "What is the best way to limit access to certain menu options within the RIS menu system once a user has logged on?" Thanks, Andy

Except if it hoses some of the existing working non-7300 systems in the process... Andy

Hi, I've just tested and released RISult 1.1.4 (It need an update to work with the new DP Base 6.03). It definately works fine. It also only works with DP Base 6.03. I suspect that the loop problems you are having are through using the wrong version of DP Base with RISult. So long as you use the latest RISult with DP Base 6.03 everything will be fine. Cheers, Andy

Hi, RISult v1.1.4 now available. Again, the only change is to get it working with the latest DP Base 6.03. RISult will now only work with this version of DP Base. Cheers, Andy

Hi, Can you just confirm - are you using RIPREP or RISETUP images? Thanks, Andy

Hi, Can I just check that you are using the latest version of RISult with DP Base 6.02.5? Anything else will cause that problem. If you still have that problem then I know where the issue will lie and will investigate it for you on Monday Cheers, Andy

@Quazl I was just wondering - why not use AutoRIS or RISult to do this automagically? Cheers, Andy

Hi, If you'd just searched down the screen a little you'd have seen this: http://www.msfn.org/board/index.php?showtopic=62501 Andy

Hi, Just go to Microsoft.com -> Downloads and search for the file... Here is the link to KB912945: http://www.microsoft.com/downloads/details...&DisplayLang=en You will need to validate your copy of Windows to download. Cheers, Andy

Hi Bashrat, The Realtek HDA drivers have once again been updated. You can get vR1.32 from: http://www.realtek.com.tw/downloads/dlhd-2...1&Software=True Thanks, Andy

Hi, From what you've said, I suspect that your company has created several seperate builds or SIF files which oschoice.osc is then displaying giving several install options. e.g. Win XP Win XP + Office 2003 etc. If this is the case then no editing of any OSC file is required. I'll assume these are flat RISETUP images and not RIPREP based. There are now two methods of continuing: Method 1: When you choose one of the options you select a particular SIF file - which if I did it (not that I would do it this way at all!) would have an entry in [GUIRunOnce] something like below for the "+ Office 2003" option: command1=%systemdrive%\reg_add.cmd The reg_add.cmd file would simply contain something like: REGEDIT /S "office_run.reg" and office_run.reg would be the RunOnce registry entry you'd need to import to get office install started. Phew! (you could skip the reg_add.cmd file and insert the command directly into the SIF file, but I find using a batch file easier to manage and less prone to error). Now, as RogueSpear suggested, you'd need the office source somewhere local like a folder on C: Putting it in the $OEM$\$1 RIS folder on the server sounds like your best bet. As well as this you'll need the "reg_add.cmd" and "office_run.reg" files to the same folder. Method 2: Almost the same as method 1 except instead of using [GUIRunOnce] in the SIF file to insert the necessary registry entry, you use a "cmdlines.txt" file located in the $OEM$ folder. This file should just contain the lines: [COMMANDS] "reg_add.cmd" You should again use the same content as method 1 for reg_add.cmd - making sure to place it as well as office_run.reg in the $OEM$ folder. If you had to go about running office in this way then I'd use method 2. Personally I use AD and SMS, but that's not an option for many people because of the expense! (the company pays, not me ) It's late here so I may have made a schoolboy error or two - or simply missed the point altogether Good luck, Andy

@Quazl The DriverPack_LAN will give you the Windows drivers (e.g. when windows has installed the LAN drivers will be installed). The RIS drivers that RogueSpear is talking about are text mode only. They should be placed in the i386 folder (e.g. they are used by RIS during text-mode setup and then abandoned). Without the drivers that RogueSpear is talking about RIS will probably not recognise the NIC and you will not be able to get started on the RIS build. To cut a long story short - you'll probably need both. Cheers Andy EDIT: Doh, seems like I was just beaten to it

Hi, Well, logic would dictate that something else has changed - whether you know about it or not . Have you tried burning another disc? It could be a corrupt disc at best and corrupt source files at worst. Failing that possibly something's happened to Virtual PC. Maybe a reinstall of that would be a good idea if the problem persists. Good luck, Andy