Fencer128

Hi, Please see forum rules sticky at top of main forum page. Driver requests should be done via new topic. Also, Bashrat probably won't consider beta drivers if he already has included non-beta working drivers, so please do not post them. Andy

Hi, You really should have started a new topic for this, as per forum rules. However, the official link for these 8.48e drivers is: http://www.broadcom.com/support/ethernet_n...loaddrivers.php Cheers, Andy

Hi, It's been so long since I've had a Realtek BSoD that I'd forgotten it was AC'97 and not HDA drivers at fault. With regard to the rest of you post, what I was highlighting is that if a list is created, we should be careful how the list is named/described - as to say "Realtek AC'97 drivers cause BSoD" on one level is correct, but if it were left at that it ignores the cases where SoundMax H/W is correctly installed and no BSoD occurs. In this case you could argue it "does not cause BSoD" (I use all driver packs on hardware containing soundmax, realtek, etc audio regularly without issue now that soundmax drivers are incorporated for most devices). In other words you'd need more than one list IMHO. A list of "always BSoD", and a list of "BSoD under certain circumstances", etc. This way people aren't going to turn around and wonder why drivers that cause BSoD are included in the driver pack, or alternatively request that drivers get added that are deliberately left out due to their over-riding instabilities. I hope that makes more sense! Andy

Hi, This is an interesting suggestion - however it is further complicated by the fact that certain drivers have cross dependencies with non-related hardware or other drivers. For instance, Realtek HDA drivers can cause BSoD if SoundMax hardware is present and suitable SoundMax driver (containing device HWID) is not present (AFAI remember). In this case would you label Realtek HDA drivers as causing BSoD? To avoid unnecessary confusion I suggest that these kind of issues be resolved before such a list is launched, presuming Bashrat is interested. Cheers, Andy

Hi, Pardon my confusion - but what exactly is the problem? Cheers, Andy

I think I've been quite lucky with Realtek compared to most. I used to get the portcls.sys problem, but Bashrat's comprehensive driver support has fixed that. No problems outside of this! 90% of our graphics is on-board 845/865/915 based, the other 10% is split between low end GeForce AGP and ATI X300 PCIe. Andy

Training? Andy

Hi, I'm afraid that it's no longer as simple as that. Most games that run from the CD to enforce copyright through protection mechanisms. As such just changing paths, and these may well be hardcoded into the executable - probably won't work. There are ways to get games running from the HD instead of the CD but some of them are very close to warez efforts and so I wouldn't think this is an appropriate forum in which to discuss them. Before you PM me to ask - I don't know of any specific utilities myself (I don't use them). If you own a legitamite copy of a game you could always try creating an ISO image of it locally and running a virtual CD emulator with copy protection emulation features. Cheers, Andy EDIT: User below is correct. I forgot to add the word "that" to the above line. Most games do run from the HD.

Hi, Try PowerDVD 6. What you need is dynamic range compression. PowerDVD offers this for Dolby Digital I believe. Good luck, Andy

Hi Bashrat, 3ware have updated their 9000 series driver to 2.06.03.042 [9.2.1.1] It can be downloaded via: http://www.3ware.com/support/download.asp? Thanks, Andy NOTE: Please disregard this post as the download is no longer available and may be superceded by a later driver release.

Hi Bashrat, Just to let you know that 3ware have a 9550SX driver 3.00.00.090 [9.3.0.1] available for download. http://www.3ware.com/support/download.asp? Thanks, Andy PS - should have got the post title right with driver [pack]. Will do for other drivers! NOTE: Please disregard this post as the driver has been superceded by a later release.

@muiz Sorry - as soon as 5.11.8 tested ok, I deleted 5.11.7. Andy

@muiz Hi, Can you give some more details please? I do not get that error. I use method 2, no KtD, GuiRunOnce. I use the latest versions of all of the driver packs. My Windows CD had had RyanVM Update pack 2.0.1 pre-integrated into it using the Integrator 1.0.5. Thanks, Andy

Hi, Something's not right with this story - or something's missing. BTW DP Base 5.11.8 is out now. Can you confirm that you used the following in the order outlined below: 1. Vanilla Windows XP SP2 CD files (i.e. no nlite modding) 2. Integrate RVM Update Pack 2.0.1 using Integrator 1.0.5 3. Expand DP Base 5.11.6 and select method 2 for driver pack slipstreaming, making sure you were using latest versions of driver packs you included? (did you keep the drivers? did you use GUIRunOnce or RunOnceEx?) 4. Burnt new CD image without doing anything else other than above. 5. Built PC Cheers, Andy

^^^^ Hi, Sorry I'm unexpectedly busy at the moment. If anyone wants to take this on feel free as I'll not have time until at least the middle of next week. Cheers, Andy

Hi, Riprep images are HAL dependant. RIS checks the HAL type of the machine you're using to view then menu with against the HAL type mentioned in the sif file of each image on the server. If the HAL types mis-match then the image will not be displayed. A classic example is creating riprep images on a hyper-threaded machine and then attempting to deploy them to an older non-hyperthreaded box. Different HAL types -> no images displayed. Good luck, Andy

Hi, Did you search at all? This is a very well covered subject here. Cheers, Andy

Hi, Are you sure that it's only the base pack version that has chnaged between your install working and it not? The symptoms you describe (escpecially the long install time of previous versions) seem to point to a different cause - possibly nlite or RyanVM update pack related (depending on what you use). Please can you confirm that you have only changed the base pack version (along with possibly the driver pack versions also) between when your build worked and now. Thanks, Andrew

Hi, I can't honestly say I have. We have approximately ~400 machines with Intel915GUX (on-board Realtek HDA). I have one as my main work PC for my RIS build work and it gets hammered but is still rock solid. Now, a couple of years ago at home I used to get that particular bluescreen a couple of times a month. Turns out it was my GeForce2 G/C so video is the first thing I tend to associate it with. Cheers, Andy

@RogueSpear Thanks for the info. I'll take a look tomorrow. Cheers, Andy

Sorry - but that's incorrect. Power Users can install some software (that require registry changes), and just about any malware can install via Power User as well. User is a lot better, though as someone pointed out already - if you don't need to play with the registry at all there's nothing stopping you running programs still. If the laptop's only running a couple of applications, you could always use software restriction policies (have a google). THey need a little setting up, but you say there's only one laptop affected anyhow. If you set up automatic updates to "Automatically donload reccommended updates for my computer and install them ..." it will occur in the background if logged on as a local user and no indication will be given by the PC when doing so. Hope that helps, Andy

Now, if I saw that behaviour I could only think it was to do with my unattended install - and not the driver. If the driver wasn't right for the H/W - or the HWID of the H/W was missing from the driver then AFAIK manual installation would not fix the issue. Andy

^^^ That's a relief I'm currently in the middle of extracting and sorting all of the Sony monitor drivers. I'll finish it tonight, get it up on my site, and then update this post to let everyone know it's been done. Cheers, Andy EDIT: DONE. I remembered your Samsung drivers this time muiz

Sorry muiz! Been a bit busy so didn't notice your post. I just downloaded the pack via the link in the initial post - I guess it hasn't been updated with your drivers yet. I updated the original pack I put up to later include GNR and Neovo drivers. I thought I'd let you know in case you wanted to update the file you're currently sharing. Thanks, Andy

Hi, If we're talking stand-alone/workgroup PCs here, then just make your local user accounts members of the "users" group - and not Administrators. Using automatic updates will still install updates if configured correctly, and LiveUpdate should still look after SAV. Members of the "Users" group can't usually install much software/make serious changes to the OS. If these machines are on a domain then the same applies - though you will want to move domain users into "users" and not "power users" or "Admiistrators". Group policy could be useful for configuring automatic updates if you have a domain setup and lots of PCs. Good luck, Andy