Fencer128

From my own experience - in a pure MS environment this is going to be your only way of achieving what you want without upgrading hardware. As mentioned above, it is usually more sensible (unless all of your 1500 clients have this problem) to purchase a cheap PXE capable NIC and to add it to PCs that are currently not able to PXE boot. My only reservation is with Realtek hardware . I've personally had bad experiences in the past and would recommend 3Com or Intel instead. Cheers, Andy

Hi Bashrat, I've been involved in a discussion in the "Sound B" thread about the Sigmatel 9220/9221/9223 driver stored in the D\S\S\U folder of DriverPack_Sound_B. It seems as if it needs some more files in order for the install to work correctly. This has been tested by myself and others to solve the main issues. Those files are located in the Intel Desktop Board\Audio\DISK1\WDM folder of the the extracted driver folder tree. The driver files can be downloaded from: http://downloadfinder.intel.com/scripts-df...sional〈=eng *** Could I also make a request to include the notification area driver applet in the install section in BTS_DPs_Finish.cmd? The reason I ask is that I will soon be building many of these machines, and I fear that without the applet I will need to log on to and manually select the "Default" windows sound scheme for each and every build. *** Thanks, Andy

Hi, So - I addded the contents of the: C:\Program Files\Intel Desktop Board\Audio\DISK1\WDM Folder to the C:\D\S\S\U DriverPack folder and now sound is installed correctly. The only caveat is that no sound scheme was selected by default. However, once I did select the default sound scheme all was well. I suspect that installing the notification area applet for the driver may fix this small issue as it includes some autodetect code that runs when speakers, etc. are plugged in. I imagine that this might also trigger the sound scheme to be selected too. As I build many such machines unattendedly I will see if Bashrat will consider adding the applet install to the Sound B part of BTS_DPs_Finish.cmd. I'll post the request seperately in the main Sound fourm. Cheers, Andy

I'm glad someone voiced that, as Bashrat probably has a lot of work on at the moment in his real life . What would really be nice is if everyone who posted "Is it ready yet?" downloaded the pack in question - modified it to include their new needs and then learnt about the whole process so that they could appreciate the amount of time, effort and testing that must go into assimilating multiple driver updates many times per month. Maybe then it would lower the post count around here. If I need an update then I'll alter the packs myself until it is included, by request, into a later official pack version. Andy

Hi Bashrat, Could you possibly add drivers for the SMC 1211 series of NICs to your next release? Current (and I suspect last) version is 1.33.0711.2001. The driver download is here: http://www.smc.com/index.cfm?event=downloa...ARTNUMBER=false Thank you, Andy

Why don't you give it a go? Andy

Hi, "Seemingly" is the key word there! Cheers, Andy

Hi, I agree with you on Intel, though as long as you stick with cards and don't rely on on-board solutions you should be ok at the moment... *fingers crossed*. I've never had an issue with 3com cards and RIS so I can also heartlily recommend them too. Interesting observation about the MS - 3Com RIS boot partnership - never knew that. Cheers, Andy

Hi nerd-light, If you want more help on your issue then you'll have to provide more specific details on what exactly you did with nLite. If the information in your previous posts is accurate then using nLite must be the cause of your issues. Cheers, Andy

Hi, Well from experience I can say that 3com cards seem to go well, and Intel ones too. I use the Intel PRO/1000 series cards personally without issue. Best to stay away from Realtek. Marvell and Broadcom work, but sometimes require a few tweaks to do so. Hope that helps, Andy

Hi, Yep, fragbert is definately right. Device manager looks fine but no sound device present. I've attached my HWID - though I don't think this is the specific issue. It could possibly be due to a recent change in the driver. I notice that the driver name is: Audio: Sigmatel 9220/9221/9223 [5.10.4866_XP32_XP64_MCE_2K_V2.EXE] Cheers, Andy EDIT: Had a look at the post below and it sounds good. hwids.txt

@Fragbert Ok, will definately check on Monday as this is a big issue for me. Thanks for the heads up. I am using that BIOS revision too. Cheers, Andy

@Fragbert I am happily using the current BTS sound packs to successfully install sound on our Intel D945GTP motherboards. I'll check this out for sure on Monday morning and post the result (thinking about it all I did was check device manager, which looked ok, I haven't actually tried the sound yet...) Cheers, Andy

Hi, No, that is not normal. Looks like file permissions on WINNT.SIF aren't allowing you to modify it. Can you check if the slipstreamer works for you on a non-nlited CD source? Cheers, Andy

Hi, It seems to me that you don't have a VLP. You may well have the Retail Upgrade CD instead. Cheers, Andy

Hi Bashrat, The latest Intel Chipset INFs have been released. You can download them from: http://downloadfinder.intel.com/scripts-df...sional〈=eng Version 7.2.2.1007. Cheers, Andy

Hi Quazl, RIPREP is, in my opinion, preferable for building PCs only when you have similar hardware. Specifically it is best when the HAL types of the PCs you wish to build are identical. Now, if you read around this forum you will find threads suggesting methods of altering RIPREP images to get them working on different HAL types, etc. but, in my opinion, it is a bit of a pain to say the least. If you make regular changes to your image (e.g. drivers, hotfixes, etc.) then it's even more of a pain to update. Now, if instead you use a RISETUP image - a flat file image - you can use this on any hardware type. This advantage comes from the fact that instead of merely dropping a binary image onto the hard disk and hoping that it will work with the hardware, a full installation occurs. That is, you get the usual Windows CD-based installation experience (except of course with RIS it's over the network rather than from CD). The main disadvantage with this method is that it takes longer than a RIPREP install. Our 3GHz machines take around 30 minutes from start to finish for a RISETUP install. Given all of the above, I choose RISETUP, the only time I might advise to use RIPREP instead is if you're building a large number of machines concurrently and time is critical. However, for this scenario I would suggest Ghost multicasting is much better than RIPREP anyway. Hope that helps, Andy

Hi, I'm disappointed too - especially since this is their "Stable Platform" and they've had since Novermber to think about a new driver/firmware release. I've seen such behaviour before, though the error I'm getting doesn't hang at the "Starting Windows" (which is most often the case). The last time I had similar problems was with Broadcom drivers about a year or so ago. Broadcom are fine now *touch wood*. Cheers, Andy

Hi, Well - it's now working. The vendor gave us a driver to try - it was the e1e5132.inf and e1e5132.sys from PROSet 10.1. This worked. I suspected that the 10.2 drivers were at fault but until now have not been able to find an archived copy of PROSet 10.1 to try a downgrade. One error I made that should be pointed out is that the onboard ethernet controller is in fact a 82753E and not, as I initially thought, a 82753V. Anyhow - the message is clear, if you use the Intel D945GTP with onboard PRO/1000 PM NIC (82753E ethernet controller) then you must use the drivers from PROSet 10.1 to get it working in RIS with a 2k3 server (other servers untested). Hopefully this will be fixed when v10.3 is released. Last point is that I *still* have an issue of sorts. The RIS build works fine for all machines except the D945GTP based ones. The D945FTP based PCs only build reliably from certain network points... other network points cause an error where just as text mode setup begins the grey bar and "Please Wait..." do not appear and setup hangs indefinately. We don't know whether this is a network hardware preference, link negotiation, latency or some other issue. I'll let you know when I've got more answers. Once again, this only affects D945GTP based machines. Phew! Cheers, Andy

Works for me... Check your browser settings/cache. Cheers, Andy

Hi Guys, Thanks for the replies. I'm still talking with our supplier - as they are now able to recreate our problem in their own test facility. I've so far tried 2 boards, both with negative results. I should say that this is not the same issue as mentioned above (I think - could you be more specific?) I can PXE boot, but just when text-mode setup starts and you get the "Please Wait" - the "Can't find drivers for your NIC" follows shortly afterwards. I don't get to the part where partitioning occurs (yet ) I'll keep you posted. Cheers, Andy

Hi, It appears though your encrypted admin password is annoying RIS. Could you try a plain text password instead? Let me know how it goes. Also, if you need any further instructions just let me know too. Good luck, Andy

Hi, If you want things like text-mode mass storage drivers or control panels to work, then you need to start with a fresh source and re-slipstream the driver packs. Replacing just the .7z files will not be the same as slipstreaming in a lot of cases. Cheers, Andy

Hi, The problem lies with your SIF file (located in the templates folder). Please can you post your SIF file, being careful to first edit out the Windows licence key and administrator password, if present. Cheers, Andy

Hi, RISult v1.1.3 now available. Again, the only change is to get it working with the latest DP Base 6.02.5. Cheers, Andy