Bâshrat the Sneaky

Glad it's solved That other, new problem cannot be caused by the DriverPacks BASE. P.S.: keep on posting in this topic if it's related to the same problem, you're doing it right

Do you have a driver of which you KNOW it WORKS? muiz reported the exact same problem!

Set attributes to non-hidden and non-system file.

Check the .inf files... not all devices are supported! I DID notice the extremely close match, but its not close enough

I already posted that 1 , but also didnt work I know you posted it, and I managed to find it back, I included it, but apparently it doesn't work either. At least that's what you tell me. Sad news... again. But maybe (hopefully!) it WILL work for other Hercules Fortissimo cards...

DriverPack Sound B V5.11.1 Changelog: V5.11.1 (30 Nov 05) -Fixed: Hercules Fortissimo drivers should work now. Nobody understands why it didn't work. Someone's drivers seem to work, though. I decided to try it after all. -New: added 1 SoundMAX ASUS driver. -New: added 2 SoundMAX Compaq drivers. -New: support for Trident 4DWave driver. -Updated: M-Audio Delta series driver from 07/08/2004,5.10.00.5047 to 04/08/2005,5.10.00.5051. -Updated: SiS 7012 driver from 11/03/2004,5.10.00.6120 [1.12b] to 11/03/2004,5.10.00.6120 [1.12d] (null update). Download @BigDaddy: please retry with the update above!

BTS DriverPacks BASE V5.11.8 Changelog: V5.11.8 (30 Nov 05) -Fixed: [DPB]: BTS_DPs_M3.cmd: the DriverPacks still didn't get extracted to the HDD. -Fixed: [DPB]: RUN_ME.cmd: added detection of SVCPACK.INF instead of only its compressed variant SVCPACK.IN_. -Fixed: [DPB]: RUN_ME.cmd: multi-boot: KB888111 entries are now added to the [FloppyFiles.1] section of the DOSNET.INF file too, to get it compatible with multi-boot discs. Download Known issues -none

Not able to update today, prolly this weekend.

NOT generic, though an improvement.

It seems we'll have to try a manual install...

Implemented.

@BigDaddy: I'll contact the developer of the ATI Mobility Modder. I guess there are some new requirements with these newer drivers, since this is not a unique problem anymore... @midiboy: The thing is, this is not within my power: -apparently the option to uninstall the drivers only appears when you run the installer; -if I would add support for this (which would definetly be possible), I'd have to break the WHQL signing; -unless I'd detect the driver and then add the uninstall option. But... what's the problem of using the 'update driver' function in Device Manager (or in Dutch: 'Apparaatbeheer')?

muiz, I don't remember if you posted this already, but could you please post that HWID again? EDIT: Sorry for the capitals, but that wasn't yelling, it was just to make sure you READ it. If I write a complete sentence in capitals, it's yelling.

*big hug* JP is one beautiful cat! I almost can't believe he's already 18 years old: I've never seen a cat growing THAT old! Be grateful he was able to spend such a long time on your side and remember the beautiful moments you had with him! A few years ago, I finally was allowed to get a cat. I got him from the moment he was about 3 weeks old (yes, that's a bit too soon). He was like... 15cm in length. Soooo tiny! I named him Zombie. I took care of him. After I had Zombie for about 9 months, he vanished, to never return again... :'(

Server is back online... For a while already...

Does your administrator account lack a password? i.e., did you forget to or on purpose not enter a password in your winnt.sif file? Or maybe there's a typo in that entry? Source

Well... there's a big chance you've messed everything up. What method did you use?

First: my DriverPacks ONLY support Windows XP. Some drivers support both platforms, but definetely not all. But, on request, I make the DriverPacks BASE compatible with Windows Server 2003... which is why I'll also implement your suggestion. EDIT: Implemented, but not exactly as you suggested. I just added another check for the tagfiles, that's easier than restructuring the entire batch file. The difference in speed is neglible.

Second server is back online. Issue resolved, topic closed.

In the future, ALL drivers will be made available, including the ones that are already available on any Windows XP distribution. But for now, very very few users need this, thus I choose to realize more important things first.

I did not take people with an extracted svcpack.inf in account. I had to change ONE character to support this . P.S.: did your file get erased? I doubt that. Only some entries should have been added.

Hmm... you're partly correct. Thought I'd solved it ... not the case... It had to be: %CDDRIVE%\OEM\bin\7za.exe I forgot about those two subdirectories! But as you can see, very little people use it, since this method is broken (though I wonder how it got broken in the first place, when I first added this method, there were relatively many users that used it) and I received so few reports with complaints. Well, it will be fixed tonight after all...!

Hi esp, I only alter some parts of the winnt.sif: only the ones that are truly necessary to get my DriverPacks installed properly. That means I do not alter the resolution setting. If you removed your own winnt.sif and let the DriverPacks BASE create one for you, this setting will NOT be included by default. You'll have to add it yourself. I doubt this can be caused by the DriverPacks, not even by the drivers themselves. 99% sure you've forgotten to set it in your winnt.sif.

Wrong forum. Check the sticky in the Device Drivers forum, section #2]. There you'll find some nice tutorials

Then mail me your driver.... Weird stuff!