Lucius Snow

Do you run Sound_Control_Panels.cmd from cmdlines.txt? Does that work? You should run both from GUIRunOnce or from RunOnceEX... Yes i do. The few times i had to install, it worked. Anyway the drivers are installed before cmdlines.txt get executed.

Does Graphics_Control_Panels.cmd have to be run at at the same stage as Sound_Control_Panels.cmd (so in cmdlines.txt) ? Thanks.

Just configure Media player classic as you want, save your mplayerc.ini and copy it over the original by a batch file in your Unattended CD.

Realtek A3.69 are out

VIA drivers also have control panels (because I couldn't remove them). That might be the case for some, yes. But please be honest: how many of us use TVout and stuff on a videocard that is not an ATI or nVidia one? Me, with my Matrox G450 dual head But yes, ATI and nVidia are the most important. It was just a question anyway

Only Ati and nVidia have their control panel installed, does it mean that for others we won't get access anyway to the advanced options (like TV output) by going through the "Advanced" button in the display property page of Windows ?

Check out Backrex Outlook backup : http://www.backsettings.com/outlook-backup.html

I used that one. Very good software.

What will change from your current packs ? Will Pyron's method still work with it ? Thanks again for your work Cheers

Try : Nircmd.exe infobox "please insert wpi cd#1 into the cdrom drive F:"

I think you can do something like that with nircmd tool : http://www.nirsoft.net/utils/nircmd2.html#using

HD audio Realtek R1.14 are out

No you didn't say so, but I feel guilty for every problem with my DriverPacks, even if it's not at all my mistake... Don't ! You do a great job and everyone here agrees on it ...

Alright, cheers. I'll let it go like this ... I hope we'll find a true solution someday though.

Of course it's not your mistake. I never said so. I'm just saying we shouldn't consider that BSOD as fixed because it is not. It's still a known issue that we have to investigate in ...

I'm not 100% sure but i suppose the "RD /Q /S" is done after calling Sound_Control_Panels.cmd because i got the control panels installed many times using Pyron's method.

Well, as you know the same problem occured with method 2 (so OemPnPDriversPath isn't concerned). I DO have several people who confirmed everything to be working fine with Method 2... That's the strange thing about it, but hey, maybe they were just using some older versions of my DriverPacks, in which the OemPnpDriverPath of method 1 still had that error.... Bart of borg and Jeff had the BSOD with the latest pack. Fixing it by getting the drivers from the constructor isn't a solution. That's what they did though. But for people who use their Unattended CD on several machines for a deployment, it becomes very complicated. On my side, i DID have the BSOD as well and using method 2. It was an older version of your pack. When i integrate your packs to my CD, i only get the .7z files, decompressed them and repacked into a Drivers.7z that the fake setup.exe decompressed ... You say the fix was to change the OemPnpDriverPath path. But i've never used that (like everybody who uses method 2). So how could that fix work for us ?

I've got the same problem The auto-it script didn't work here. Isn't there any other solution ? Thank you.

Joyeux anniversaire !

I don't ...

It's a known bug. However, the hotfix is properly installed. It should be fixed in the 1.0.6 version.

Drivers 5.1 are out

Well, as you know the same problem occured with method 2 (so OemPnPDriversPath isn't concerned).

Ahhh so they're the same. Fair enough, that'll make less hotfixes.

You are Double Posting! lol !