Bâshrat the Sneaky

I guess that will be part of Computers History in the year 2025!

It *could* have to do whethere you (dis)connected the PC's to the network. Seen that before... Odd but true...

As long as they are WHQL certified, it should work. But where can you find WHQL signed beta drivers? That would definetely amaze me...

You MUST have done something wrong. But don't worry, if everything goes well, there will be a new version of DriverPack Sound available tomorrow (V5.03)

It's possible indeed. But you need a relative new motherboard for it... (and the money for a expensive USB stick)

This seems to work:- Download the .exe - Make sure your C:\Documents and Setting\[username]\Local Settings\Temp is empty - Start the exe and wait for the 'Welcome' screen to appear. - Copy the contents of the Temp folder to a safe location. - Cancel the setup. I tried this on the driver downloaded from the link you posted and I now have a folder containing a bunch of inf, cat, dll, cpl, ... files. ← Thanks Guess what? I just wanted to post the exact same thing! But you've beaten me by time

Site is back online. Probably it has been a DoS attack, at least that's what my hosting provider says. Edit: I read that e-mail wrong: it was a DDoS attack, so I can't do anything about it...

It's not the DriverPacks's server that has exceeded bandwidth, but the site server. (ok, this server also includes the DriverPacks BASE, but that isn't causing that much traffic). The DriverPacks are hosted at 3 different servers. And I'd rather not see that everyone's providing mirrors. Then it will become to difficult for me to generate some revenue through ads. (ads will return, yes) However, I think I'll change my hosting, the one I'm currently using has apparently a quite large down-time :'( Sorry, and thanks for your understanding...

I know... Site should be online again tonight. My hosting provider will hear *SOMETHING* from me :angry:

@iwod: I have done some research on how to add support for the ATI mobility and FireGL series. Here are my conclusions: In general you only have to do two things: add the file atioglgl.sys and editing the .inf file. Editing the .inf file is no problem. But what about adding this atioglgl.dll file? If I just 'add' this file, just like that, then there will be (theoretical, don't have the ability to test it IRL) a version conflict... Now we're lucky: it's only used by the FireGL series. So I can add Mobility series support to the regular ATI drivers, while I'll have to add the special FireGL drivers separately. So far the theory Now let's hope it will work in reality as well... EDIT: Well it seems Omega does the trick WITHOUT the atioglgl.dll file. Then I should be able to do that too!

Because I cannot verify the integrity then. And... again???

Someone requested support for the M-Audio sound cards. Unfortunately I have to say that this will be impossible, because I cannot get any driver file out of their setups. Yes, that's right, they only provide installers, which cannot be extracted, AND I can't find any related driver files after the installation... If anyone can come up with a solution, I'll add them. Here's one example driver: http://www.m-audio.com/index.php?do=suppor...download&ID=394

Nope. The fix has been posted before. 1) Open the RUN_ME.cmd file. 2) Search for this code: DEL /Q txtsetup.oem and remove that code. (TWO LINES with this code!) 3) Save the file. 4) Done.

Download 7-zip from www.7-zip.org (freeware). Install it. Right-click the folder to compress > Add To archive > Set it to Ultra compression > Start. Wait (will take some time for DP Sound). Done! Or you could just wait for the next version. (should be available within a couple of days)

You say 'I have configured the inf file'. Which file do you mean by that? I hope you mean the dosnet.inf file?

I guess it's really a requirement that I write an extended tutorial Will do that soon. @moesasji & buletov: thanks Finally it's working as it should @all: Got some bad news: somehow my bandwidth limit got exceeded. I think this is because of the bug in the UpdateChecker in V5.09. (or V5.08, dunno, doesn't matter). So my site is currently unreachable. Should be up tonight (as soon as I've had contact with my hosting company)

@moesasji: Well... sorry to disappoint you... But there never have been (critical) errors on VMWare So I guess... that your report is useless . Nevertheless... thanks! @Astalavista: saw your PM first, so please check your inbox! @A|lex: are you SURE you placed all Driverpacks in the folder 'DriverPacks'? You did NOT change the structure of the DriverPacks BASE, NOR did you change the names of the DriverPacks, I may hope?

@buletov: check page 34 of the General Discussion topic: I've posted a fix. @jeff: thanks for your bugreport! I think you're getting a BSOD because of the siside driver. Will be removed in DP MassStorage V5.03. You can fix it manually by doing this: 1) remove all siside related entries from I386\txtsetup.sif 2) delete I386\siside.sy_

Hehe thanks m8 EDIT: of course I already completed that fix, that's why I was so fast (did it yesterday evening...)

I've attached a fixed version of Sound_Control_Panels.cmd. Now it should work just fine. (Tested and works here...)

@Kamil: thanks! @RBCC: you will get an error @fluid: sorry, can't say...

EDIT: irrelevant content Check out manual fix #2 in this post!

@mextrom: you MUST have been using DP MassStorage, cause that's the only way it could have appeared. If not... well... then we've got another bug here... Did you include any MassStorage drivers yourself? Are you SURE you're using a clean txtseup.sif, so one that hasn't been edited by my batchfiles? (Just check its properties, if the date of last change is in 2005, then you aren't using a clean one.) But normally the original one should have been recovered automatically.

Probably you haven't read it, but I planned to remove that driver, untill I found a newer version of it, so I thought the problems would be fixed then. Well... apparently not, so I'll remove it Well, as you say yourself, it's only required for the winnt32.exe initiated installation. Currently I had not yet added support for that (however I should ). Thanks for listing everything here Will be added as well! I already tried with an older version of nvatabus.sys on my nForce 2 system, without sucess. But for me the problem is solved now, simply by removing my HardwareID (it wasn't listed in the txtsetup.oem either...). Earlier in this post I already confirmed I'd reove the siside.sys driver. The 3ware problems are fixed (no more problems during setup), but it's not yet confirmed working. Please confirm if you can! Thanks, Phoenyx!

@Garak: I'll post a fixed version today and I'll need everyone who uses a nForce-based motherboard to test it for me!