Bâshrat the Sneaky

Sorry for the late reply. Could you please post your HWID? This is of the greatest importance in order to solve this issue.

Hi Bashrat, you asked me for the driver files back in May (I think) after you released the last version of the driverpack, remember ? Yes, I own a M-Audio delta card, the driverfiles are located inside the temp directory after installation. I did not find any other way to extract them from the archive but they are the genuine drivers from the M-audio site, you can trust me on that I hope you will integrate them into the driverpack ! Bye, Alex Ah, I see! I was already wondering how the h*** I got them out of their setup the previous time... The updated drivers have of course already been included. BTW, I checked the %tmp% dir (as well as several others), I did find a data1.cab, but there were no driver files inside...

I'd say: build a fresh UWXPCD w/ just the DriverPacks, nothing else. If that works, you can restart again, but first add the other things you want to include. EDIT: I forgot about this: 23 November, 2 days after you've opened this topic, I've released DriverPacks BASE V5.11.6. This version solves several bugs in M3. And if you need more information about the methods used, check the tutorial at www.uawiki.org!

I INCLUDED the 4.4.2.0 version!!!

For the BartPE side of this story, you should post on a BartPE forum, not here, since I don't know anything about that... Please try an older version of DriverPack LAN and see if the problem persists. It might be a bug in the driver!

Delayed to tomorrow. Upload is too slow...

@midiboy: that's against my policy. But since your readme and the one I got after installing the drivers (which is something I never ever do with some exceptions... this is one of them). Don't forget to tell me how you got the drivers out of the archive! I think you own such a device @RogueSpear: all yourrequests have been implemented. @gilesw: also your request has been implemented.

Which version of DriverPack Sound A were you using?

Probably this error is fixed in the updated 1.27 driver, which is included in the about-to-be-released DriverPack Sound A V5.11.1. Let me know if it isn't the case.

;ICH7 - Kinnereth (DC)LOM/(1)+LOM/(2)LOM Mobile/(3)+ Mobile %PCIE100EMBLOM.DeviceDesc% = XP_D110K.ndi, PCI\VEN_8086&DEV_27DC That should cover your HWID. This comes from "e100b325.inf". Odd that it doesn't work... :s Try if Windows XP finds & detects the .inf file I just quoted. (Extract DP LAN and let Windows search for "an updated driver".)

I didn't want to add these drivers because they might prove to be unstable: there must be SOME reason why Marvell took them offline. But since it works for a newly added device, it should still work for the rest too. I'll update DriverPack LAN.

Man that rig SUCKS! I wish *sigh Happy birthday, ripken204!

This was already planned for the C++ version of the DriverPacks... OF COURSE this is a needed/wanted feature!

@maxximum: try the DriverPacks that will be released later tonight. They include updated Graphics drivers. That should work just fine. (Note that DriverPack LAN has been updated recently, with five different nForce ethernet drivers: that might solve some problems too!)

Probably it's something else that's causing the in-game performance drop

Then WHY doesn't it install :s EDIT: does it also find CX_27345.inf?

Included in DriverPack Chipset V5.11.2. Request implemented, topic closed.

That means it impossible to update the driverpacks, cause thats what caused it As I told you yesterday, start again from scratch. You must understand that it's not up to me to dig out this problem if there are other possible causes.

Try nLite www.nliteos.com

I need more information!

1. The most important rule. Search to make sure your question/problem/error hasn't been answered/solved already. If you can't find ANYTHING, you can continue to step #2. 2. Use the correct tag for a new topic. Available tags: ERR | <stage_in_setup>:<error_code> <on_this_hardware> - if it's an EXPLICIT error, i.e. you have some sort of 'error code' or an 'error description'. FAQ | ... - if it's a question. MISC | ... - if it doesn't fit anywhere else. PROB | ... - if it's something that's not working as it should. REQ | <new/updated>:<device_name(s)>:<updated_driver_version> - if it's a request: a new or updated driver. Please add a direct download link. Please DON'T add a description of the device: that's useless.Note: the smileys indicate which 'Topic Smiley' you should use.3. Provide enough information. Post at least these: A list of the DriverPacks you're currently using, along with their versions.Your HWIDs. Use save_hwids.exe to find them.Post the order in which you've created your UWXPCD; e.g.: nLite > RVM UpdatePacks > BTS DriverPacks.Anything that YOU think that could be useful information to find an answer to your questions/errors/problems.If everyone would apply the above rules, I'd have more time for actually maintaining the DriverPacks, instead of having to spend a significant amount of time into moderating these forums (which is required, if I want to keep track of things).About all those closed topics Don't take it personal when a topic has been shut down all of a sudden. The only reason I do it, is to keep track of things. Closed topics = solved problems/answered questions/implemented requests. Thanks for your understanding. Bâshrat the Sneaky

Download link isn't working anymore. Googling for the version number gives ZERO results. Please contact me if you have the file on your HDD.

Included in DriverPack Sound A V5.11.1, which is not yet released. Request implemented, topic closed.

Odd! It seems you're right. The driver was indeed not yet included. This driver has been included in DriverPack Sound B V5.11.1, which is not yet released. Request implemented, topic closed.

This driver has already been included into DriverPack Sound B, since V5.11 of that DP. Please post the HWID of the device in question, so I can check if this device is truly not yet supported.