Bâshrat the Sneaky

Could you provide a link, kyor? Bâshrat the Sneaky

@zorro1: That was an error! Please use the Update.cmd to get the newest files - this error has been fixed several days ago! Why not putting the drivers into $OEM$/$1/drivers? Because that's not required for this method! @edmoncu: How you don't see modifications to the i386 folder??? These batch files do it for you! (That's also why the number of steps has been reduced.) Bâshrat the Sneaky

This is definetely a problem of Pyron's method: Thauzar is experiencing the same problem. I don't think it's solved yet, but I do know that it happens for the unhappy _few_... Bâshrat the Sneaky

OF COURSE you don't have to use nLite! That's why there are all these batch files (scripts, whatever)! If this was only to be used by nLite, I wouldn't have made them! Bâshrat the Sneaky

UPDATED 22nd of October 2004 DOWNLOAD

@kyor: Well, I think this has to do something with Service Pack 2. Never heard of any trouble with this driver, and used this one for myself too (got a ASUS A7N8X-E Deluxe with this controller onboard) and it worked just fine... It's possible that SP2 makes the signing of this driver obsolete... Are you sure you disabled the Driver Signing Policy? EDIT: forgot to say: I double checked the drivers: I compared the files from the download and the ones in my DriverPack LAN and they are identical! Bâshrat the Sneaky

You're right. Fixed it, will upload it ASAP! Bâshrat the Sneaky

You can give it a try! I have no experience with this. Bâshrat the Sneaky

LOL for method 1: everything is being extracted for method 2: everything is being renamed... (so you don't have to change this every time!) Bâshrat the Sneaky

No, he's asking if the SiI3112 RAID drivers also work for the SiI3112 non-RAID... And I doubt this, why would they else make different drivers? But if someone could test this? Bâshrat the Sneaky

Well, now I'm confused as well... There are two facts: 1. nLite DOES change the txtsetup.sif file. 2. I didn't change ANYTHING about txtsetup.sif patching and it worked just fine... So my conclusion was that it would be better to use nLite BEFORE the DriverPacks, and I remember RyanVM agreeing with me... :s Bâshrat the Sneaky

how is that? Well.... To determine which driver should be installed, Windows reads out the DeviceID of the hardware. Then it looks for inf files that contain driver information, and when it finds a match it installs the driver that belongs to this inf file. So I think that the DeviceID's of IBM's and ASUS' SoundMAX drivers are identical, which would explain this error. Please remove the Drivers\S\SM\I folder and try again! Bâshrat the Sneaky

I have no problems using nlite after the DriverPack, but if I use nlite before my SATA controller (SiI 3112) is not recognized during setup and also I can not install the drivers from a floppy disk. So my advice is to use the DriverPacks first and nlite afterwards. Nlite will keep the entries to txtsetup.sif, so nothing to worry about. @Bâshrat By the way, thanx a lot for that excellent piece of work That's exactly what I advised , you can find it a couple of pages earlier and in the FAQ.htm file! Bâshrat the Sneaky

Then the problem HAS to be identical DeviceID's... Bâshrat the Sneaky

Huh? What method did you guys use? The problem might be that it uses the IBM SoundMAX driver instead of the ASUS one... I'm at school at the moment, so I can't check it. When I'm home, I'll compare the PnPDeviceID's... Bâshrat the Sneaky

I can recommend you to install it for testing purposes on another partition, or another harddisk! Bâshrat the Sneaky

There's a remark on the first page that tells you this Please read everything nex time! Bâshrat the Sneaky

You DON't have this option... :'( I was hoping there was a hidden option to only install the core of QuickTime or something... Bâshrat the Sneaky

I didn't have ANYTHING yet But I've started today. I will do this DriverPack on my own tempo, and probably I'll release some versions without having all requests fulfilled... But, as you said: better something than nothing! I've started with 3com today, and I've got to say: WOW , soooooo many???? Just wanted to let everyone know: this DriverPack isn't abandonned! Bâshrat the Sneaky

I don't understand what you're saying... Please clarify The Terratec Control Panel that is used with Aureon "Sky" and "Space" is not meant to work with the Aureon "Fun" Version of the Soundcards... So just a hint... I know this.... T_F.exe > cpl of FUN T_SSU > cpl of Sky, Space, Universe Bâshrat the Sneaky

I guess the problem lies in Method 2... But it isn't clear to me what's wrong... I'll post it here when I know more... Bâshrat the Sneaky

same thing on a asus P4S533 board OK, confirmed... But, really, I don't understand why this error is showing up... Could you guys please download the drivers yourself and check if they work then??? http://www.asus.com.tw/support/download/it...P4C800%20Deluxe Bâshrat the Sneaky

I don't understand what you're saying... Please clarify

To the both of you: :o Please post: 1. hardware config 2. the method you've used 3. whether you used nLite or not Bâshrat the Sneaky

Huh? You're giving me a really strange reply When you're using Method 2, there shouldn't be ANYTHING in $1\Drivers, because it uses the DriverPacks in compressed form, please check if there's a OEM (yes, OEM, not $OEM$ !!!) folder, in this folder you should find all the DriverPacks! But HOW did you get $1\Drivers\L ???? Maybe it's a left-over from the old DriverPacks? Bâshrat the Sneaky