lightsout

So who voted for the CCC anyway?

I think you are spot on with that! I'll do some digging on those articles and see if I can't find a solution. Thanks!

Ok, I removed bts_dp_finish.cmd. And yes, both ha10kx2k.sys and ha20x2k.sys are both present in the drivers directory as expected really!. My Audigy still doesn't work mind, as I said above, I think it requires a custom driver. Or there is something in that driver it needs as well.

Oh yes, I know they both had conditions. The condition only seemed to be that certain .ini files existed in the driverpacks, so they were always going to pass. Anyway, that goto does the job perfectly! Sadly, it didn't fix the problem, although I have found a fix... it only seems to work when I use Gateway's Audigy driver (it is a Gateway system of course): ftp://ftp.gateway.com/pub/hardware_suppor...ive/7513081.exe It also changes what it appears as within device manager, as "Creative SB Audigy" instead of "Creative Audigy Audio Processor (WDM)". So I'm not sure if it is a custom chip or not. If you have any ideas, I'm happy to hear them, otherwise I suspect you won't wish to include this driver just for my benefit so I could modify my drivers install to copy it manually!! Although I suspect even with this driver present, it'd still go and use the newer Creative drivers anyway. Doh.

Well isn't one problem that this: and this: Both get run - they seem to update the WDM driver. Although I'm not sure what their behaviour is with regards to downgrading drivers if a newer one is already present. I've added the setupapi.log for your pleasure as well, ZIP'd otherwise it'd be huge. Creative's drivers baffel me sometimes! set.zip

Hi! I'm having some problems with the Audigy soundcard in some Gateways I've got. I'm using the latest driverpacks as of this moment. Everything appears to work ok, and the volume icon appears on the taskbar. There are several odd things: 1. The "Sound And Audio Devices" Control Panel. On the "volume" tab, I can't alter the device volume. Nor can I alter the speaker configuration. 2. The "Creative Audio Control Panel" is installed, but when I click it pops-up a message saying "The Creative Audio Driver is not installed". 3. The file "ha20x2k.sys" file is present in c:\windows\system32\drivers. This is from the BTS Sound DP A, and from the CR\1 directory which is for the Creative X-Fi sound card. Look at the WDM inf file, it does match my HWIDs! Looking at BTS_Driver_Finish.cmd, my system runs both of these commands. Is this meant to be? Does anyone have any ideas about this? Even deleting the X-Fi driver didn't help. Any ideas anyone? HWIDs for reference:

*sigh* just missed it down the bottom of the page: http://www.msfn.org/board/index.php?showtopic=68557

Hey, Using Macromedia's licensing - http://www.macromedia.com/licensing/distribution/ - I'm doing unatteneded installs of Flash 8.0.24 and Shockwave 10.1.0.011. For Flash I use "install_flash_player_active_x.msi" and it works great. Installs unattended and flash works. For Shockwave, I use "sw_lic_full_installer.msi" and it also installs great. Sadly everytime I visit a webpage with Shockwave on it, IE pop-ups with "Click To Run ActiveX Control on this webpage" box in the middle of the window with just an "OK" button in it. If I OK it, then Shockwave displays it anyway. So I presume it is missing it's ActiveX Control or something like that. Or is a security issue, but turning my security right down hasn't helped. Any ideas anyone? Cheers!

I'm with Fencer here.... stlang.dll is in system32. sttray.exe isn't present. stacgui.dll is also in system32. My sound scheme is fine, although I'm using SMS OSD so it is likely a very different method!

Likewise, I think the CP will be less resource intensive and so will be a better option. Also, it will make the driverpacks smaller!

Isn't that a problem of missing the correct mass storage drivers? Does your motherboard have an IDE mode you can use for your SATA ports?

You could go to a Linux style model.... ok, yeah, I know this is a Windows forum! Basically Linus maintains the current "official" tree of Linux. Everyone submits their patches to him (via some trusted maintainers of various sections) and he decides what goes in and when it is released. So in essence, you'd remain in full charge but other people would make changes and submit them to you.

Well I've done that. I'm just getting the "Fatal Error" everytime I call setup.exe with either ENFORCECACHE=1 in the setup.ini or passed as an argument to the installer. When I just install Office 2003 without SP2 slipstreamed, then it installs the cache just fine. So it seems to be an issue with the slipstreaming of the SP2 service pack. And yes, I'm still using a CD image that has been slipstreamed to SP2.

I've just been trying to do this... using this tip http://www.appdeploy.com/tips/detail.asp?id=76 I created a CD image of Office 2003 with SP2 integrated into it. Now, I've got the enterprise setup and when I run it with ENFORCECACHE=1 it doesn't run and I get a fatal error. The thing is, when I use a reference Office 2003 (no SPs integrated) it works just fine. So I presume it gets upset with the presence of SP2 in the install. Did anyone ever resolve this issue?! Cheers.

And one more important point - each mass storage driver MUST have a txtsetup.oem according to the WinPE docs. I suspect this will stop the mass storage driver packs from working, although if you do get it working then let me know!

My auto generated one says this: And in the system32 directory there is a directory called "MassStorageDrivers" which has a directory in it for each of the above drivers. From what you said, they are directly in the system32 directory instead of the "MassStorageDrivers" directory. Might be a good idea to stop/start binlsvc to ensure the RIS service notices... I'm not sure if that does make any difference tho.

I'm in total agreement, it is fairly easy to do it to be honest!

Bashrat - close this topic please. I found a nice hacky fix - I delete c:\windows\system32\nv4_disp.dll when I restore the image, and then Windows re-detects the driver from the driverpacks fine. No problem!

Yeah, it is a bit stupid that you need the section head without any options otherwise it ignores it! I deploy from a single core machine to a dual core PentiumD without issue. XP can handle swapping between the UP & MP ACPI HAL automatically from what I've read.

I did try using RISult to create a custom WinPE but it didn't work at all. The mass storage drivers kept triggering stop errors. To add LAN drivers, you just need the .sys & .inf in the i386 directory. Stop and start binlsvc. From mass storage, hmm, tricky. I used the OSD CD Deployment wizard in SMS and gave it a path to the txtsetup.oem for the storage drivers I needed. I then copied the contents of the CD over the RIS area. I don't know of a way to automate this, as it does do something interesting things from what I can tell. I'd suggest you create a custom CD with some added mass storage drivers and see how it differs from the normal CD layout. If you find a way, I'd be interested tho

Out of interest, are we talking WinPE because you are using SMS OSD?

Did you edit the sysprep.inf like I suggested before? You can tell if you have, as sysprep will take 20-30 minutes to run before the machine shuts down and is ready to image. Both of those machine should use the same HAL, so I'd more likely to think it is a mass storage driver problem rather than anything else. Cheers. PS - Thanks Phogoff, I've got a workaround but I'll keep that in mind!

It seems the present of sthda.ini points to the other I*.INI files depending on the HWID. Then the stacgui.cpl, sttray.exe & stlang.dll are required from the contents of the I*.INI files. Thanks! I had the same problem with the Intel 945 boards.... device manager is ok, but the sound itself doesn't work. These files need to be added to C:\D\S\S\U and then it'll work. We need Bashrat to add it to the normal driverpack tho. Does that explain it? Cheers!

Ensure your sysprep.inf is like this: The second bit is important, otherwise it has no affect! Re-image the machine and try again with a new WIM image. Personally, I keep a ghost image of my reference machine before I run the SMS image capture as it sysprep's the reference machine - this way makes it easier to restore the reference PC to the correct state. If you have the wrong mass storage drivers or HAL, then you'll see the problems you describe. I suspect it is mass storage in your case, due to the "basic" HAL the reference system has.

I would suspect it wouldn't work, as drivers change over time. For example if some extra SATA drivers were added, your system would not be aware of them. I'd re-build the whole image.