Fencer128

Hi, I was right in that removing: <OPTION VALUE="D_OSCHOICEX8632"> fixed a problem (but it was not the complete solution). Now RIS was enumerating the correct folder, but telling me there were no OS contained within. I tracked this problem back to incorrect MS documentation. The guide says: but it should read: If you place your custom folder containing the OS to be enumerated at the same level as "Images", then the SIF files are enumerated. Hope that is clear! Andy

Hi, I've found a mistake in a custom osc file that I think is the root cause of this problem... Basically I'm giving contradictory information as to what screen to move onto once a selection has been made. Two instructions come from having the following on the same page: <META KEY=ENTER HREF="OSCHOICE"> . . . <OPTION VALUE="D_OSCHOICEX8632"> I'll correct this on Monday and post the result. Andy

Lucky you. We have a few hundred Dell Optiplex (and some Dimension ) units here. Whilst they work - they're mostly fine. When they break it can take months to get an engineer on site. The people making the purchase tend to buy the bronze 3 year next day on-site warranty. It's not worth the paper it's written on. If we tell them to buy the gold version they say "but that's really expensive". Deeerrrr. Yeah! - but at least they send an engineer!. This is why we've taken steps to, as often as possible, prohibit Dell PC purchase. Only in very specific circumstances can this go ahead. Now, our preferred supplier has a similar 3 year next day on-site warranty. They do come next day - no arguement - and bring new (and correct!) hardware when they do. No contest. We have a PC down stairs that we spent 3 hours on the phone (one call!) and six months trying to get Dell to send a new PSU. The two times the engineer came out they bought the following parts with them. First time - new CPU. Second time - new IDE cable. They always tell you to "insert the Dell diagnostic CD". Once when we did that, and we had a HD fault, the diagnostic program said "HD ok". Strange since we had disconnected the HD at this point to test!. "If the CD says ok we can't send an engineer!". Another time with a dead PSU we had to get to speak to a super-supervisor at their call centre. Everyone below him wouldn't log a call until we'd run the diagnostic CD.... even though we kept saying the PSU was dead! Whenever we do contact Dell we have a new account manager - no chance to build a relationship due to staff turnover. My boss says that Dell ring him up periodically asking why we won't give them an order. He always outlines past problemas and says that the new supplier is fine - so why would he risk getting burnt again? They never have an answer for him. That's our experience with Dell, so we avoid them like the plague . Cheers Andy

Hi, I agree with you on this. Though, it's relatively easy for me personally to boycott Realtek. It's very difficult to make this happen at my work. As you say, their parts now appear on Intel boards (amongst others) and so long as this is the case, the chances of finding a volume OEM with good support (i.e. not Dell), at the right price, who doesn't use Intel/Realtek is next to zero. I'll make sure to add the goal (i.e. preferred but not essential) of emliminating Realtek from the desired product specification for the next round of contract tender for our PCs though. We already have a requirement to have on-board Intel NICs. Thus all our machines currently arrive with Pro/100 VE and will continue to do so until Intel ship a motherboard we can use with Pro/1000 on-board. Cheers, Andy

Hi, I believe there are already linux implementations of RIS. Please google "Linux RIS" for more info. Andy

Hi, You can select what builds/images users see in the oschoice.osc screen by setting the NTFS read permissions on each images sif file. Denying a user read permission effectively hides it from them so it is not enumerated. This will allow you to stop certain users/groups from being able to access certain images through thr RIS menu system. Cheers, Andy

Good luck, especially if you are going to try enumerating folders other than "Images" for sif files Andy

Hi, Thanks for replying. Firstly, the images are all flat - no riprpep. For the desktop stuff I use RVM and BTS packs - so they are "one size fits all". We use SMS for all our software deployment/auditing and so I'm not conerned with that aspect. Secondly, having 3 different groups of images is only part of the reason I need different image folders. This RIS server is responsible for deploying 3 types of build: 1. Customised XP SP2 (Desktop clients ~2000 on campus) 2. Vanilla XP SP2 (used by our student lab staff to build master ghost images for multicasting ~800 lab machines that require quick and frequent rebuilds) 3. Server 2k3 SP1 (Used by our systems people for server room stuff ~50 machines as far as I know) Ideally each group of people should only have access to their own builds and no-one elses (i.e. no reading/editing/etc). This is the first reason for creating 3 seperate folders. I realise there are other ways to achieve this security by setting permissions on each individual build folder, or by using GPO and META SERVER ACTION but I'd rather do it this way if possible. The second reason is that the way in which people in each group want to use RIS is different. This necessitates 3 seperate osc file paths through to build selection and finally deployment. These are: 1. Choice of OU from particular part of AD schema, no auto install option, display data input screen (Desktop clients) 2. Automatic OU choice from different domain, auto skip to warning screen with single key press. (Student lab) 3. Choice of OU from different part of AD schema again, no display data input (Server stuff). So you can see that I have 3 different paths to accomodate 3 different usages of RIS. There are also seperate builds available to each path/group. Hope that's clear! Andy

Hi, I'm busy trying to tweak our RIS setup here at work. We get 3 different classes of user logging onto the server and I'd like to have 3 seperate image folders containing builds specific to each group of users on my RIS server. RIS has a server-side action that can be used to enumerate folders. Usually this is used in oschoice.osc and has the form: <META SERVER ACTION="ENUM IMAGES"> Allegedly, according to MS (see http://www.microsoft.com/resources/documen...ed_dpl_KEMO.asp) you can change the directory enumerated to be a subdirectory of the usual "Images" folder. However, I can't get this working. It looks like I'm not the only one (see http://groups.google.co.uk/group/microsoft...74a3afceec6023e). All I get for trying is a "The data is invalid" error in the RIS menu. I've tried placing the folder to be enumerated alongside "Images" as well as beneath it. I've tried concatenating the folder name and using the following syntax, but still to no avail: <META SERVER ACTION="ENUM FOLDER"> <META SERVER ACTION="ENUM IMAGES FOLDER"> I have a workaround if this doesn't work out of using the "Images" directory and setting folder permissions for individual builds to give read access to only the appropriate group, but I'd rather do it the way above if possible. Anyone got this working? Cheers , Andy

Hi Bashrat, That time of the month again... https://support.ati.com/ics/support/default...ge&folderID=293 Cheers , Andy

Hi, This site: http://www.uawiki.org/doku.php?id=wxp:ua:d...rpacks:overview Has an article on how to use the driver packs. Andy

@gilesw Hi, Downloaded the new monitor pack. Is there a reason that the Sony drivers I added are missing? Cheers, Andy

Hi, If anyone is really desperate to get an unattended version working, then please take a look at the code in my RISult application (link in signature). The application works unattendedly and so I had to write code to edit Bashrat's files before RISult could execute. All the necessary edits are there if you use: Method 2 No KtD GUIRunOnce Good luck, Andy

Hi, You have raised several issues, some of which could be resolved in future versions if you had created the appropriate topic in the appropriate sub-forum. In order to deal with the other issues it would be best if you could post more detail on how you created your attended install, the order in which you did things (like nlite) and the versions of files used. Thanks, Andy

AFAIK it's RVM then BTS packs. Try that Cheers, Andy

Hi Major, We all make mistakes (I should know ) If you supply us with more information, as per my last post, we'll have a look and see what it is that might be causing your error. Cheers, Andy

Hi, To disable hibernate, you can use these registry settings: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power] "Heuristics"=hex:05,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,3f,42,0f,00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Power] "Heuristics"=hex:05,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,3f,42,0f,00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power] "Heuristics"=hex:05,00,00,00,00,01,00,00,00,00,00,00,00,00,00,00,3f,42,0f,00 Good luck, Andy

Hi, Please do not cross-post. You've already created one topic in this forum on this issue. Creating multiple posts will not result in your problem being investigated any more quickly - in fact it's more likely to do the opposite and put people off helping you! That said, in order to diagnose the problem, we need more information. Can you please post the information contained in the BSoD error message? Please can you also post the hardware specification of the PC on which the install works correctly so that we may compare hardware? Please do this in the other thread that you have started to deal with the issue and not this one. Andy

Hi, This is the driver for the Level One FNC-0103FX and FNC-0104FX NICs. The driver Bashrat has included in his latest pack are the latest available from the manufacturer (inf v5.05). Please could you outline in what way the drivers you suggest as a replacement are different to those currently distributed by the manufacturer? I'm no expert on VMWare's emulated hardware, but are you sure that the system is piscking up the right driver? Could it be that the correct driver is being overlooked and that this is your real issue? Cheers, Andy

@Bashrat I guess I missed it because I try to be too clever!... If I get a problem with a driver, rather than go looking for a list of drivers/hardware with known issues - I'd go straight to the driver pack contents/change log page and find the version number - then I'd go to the maufacturers site and grab the latest if newer available and try that. I'm lucky in that the only real issue I've had is portcls.sys - and that's well documented in threads here, so no need to look anywhere else. Especially, since you handled it by including most SoundMax H/W anyhow. If I really had to have resolved a BSoD issue that was a show-stopper for me, I'm sure I would have got around to the link to your supported H/W list. I guess the only thing that *may* keep people away is that they might not make the link between "supported hardware" and "BSoD". Though, with hindsight, it's blindingly obvious! Cheers, Andy

Hi, My only real thought on this is that maybe the account under which you're running the batch file doesn't have the correct privilege level required to make the attribute changes to the files in question. Maybe the ownership of the files is not correct? Try executing BTS slipstream via "Run As" and use "Administrator". Failing that, try taking ownership of the files in question. Cheers, Andy

LOL That one really did go under my radar. I'll endeavor to put together a list of machines from my work soon to get this going again. Cheers, Andy

Good luck with the exams Bashrat. See you on the other side Andy

@ruudboek Hi, yes that sound good. So long as there is a nice way in the/a list to identify these issues, that's all I was worried about. I wasn't sure how much effort you were willing to suggest for this, so I just wanted to make sure it wasn't going to be an advertised list of driver names with too little supplementary and explanitary information. In that case it may have given the wrong impression about specific drivers under certain circumstances. Cheers, Andy

I'm glad that you've managed to get a handle on this - at least you've discovered that for future purchases ATi might be the better choice for now, even if you're stuck with annoying nVidia issues. I wasn't 100% sure of the nVidia link myself, but you seem to have cleared that up. Good luck, Andy