You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 49 of 77)
DriverPacks.net Forum » Posts by Wim Leers
Topics by Wim Leers User defined search
Posts found [ 1,201 to 1,225 of 1,914 ]
@larciel: please post your DPs_BASE.ini and DPsFnshr.ini. I think you've added a trailing semi-colon, which should not exist. But the DriverPack Sound B should have deleted it anyway... But still: please post these files, it'll be helpful to track down the issue. KTD will work fine though: it's just an aesthetical error.
@benners: That's true. I should have done THIS a while ago, but forgot about it:
From the announcement... wrote:New tutorial for 3rd party DriverPacks!
The directory structure of 3rd party DriverPacks has changed a little! Please update your 3rd party DriverPacks so KTD can be applied on it!
RogueSpear wrote:The PITA part of what I was describing is the sheer number of hwids associated Microsoft and Logitech devices. And of course all the testing to make sure it's working.
haha 
That's why I won't add those drivers until the larger part of the process is automated 
Several hundreds. WLAN alone was at the FIRST release >250 drivers. Sound B contains 70-120 drivers. LAN contains >100. I'd say somewhere between 550 and 750.
Once the whole system is automated, it'll be easy to tell the exact number. But at THIS time, it's very hard to give you the exact number.
If you had read the comments, you'd see it's not the best method:
-it only works for issues you add AFTER you've made the changes
-it's a global setting: each user cannot set his own timezone.
As I've said, we'll have to wait for this feature to be included in one of the next releases.
RogueSpear, I told you ANY hardware-related exceptions could be handled by the DriverPacks Finisher, here's the proof
You'll have to find the switches for the setup yourself, but here's the new section you should add to the DPsFnshr.ini:
[wnt5_x86-32__1000__D]
tagFiles = 0
tagFile1 = "%SystemDrive%\dvdramsetup.exe" ; UPDATE THIS ENTRY
+hwids = 1
+hwid1 = "IDE\CDROMHL-DT-ST_DVDRAM_GMA-4080N"
-hwids = 0
+infFiles = 0
-infFiles = 0
commands = 1
command1 = "%SystemDrive%\dvdramsetup.exe -silentswitches" ; UPDATE THIS ENTRY
It MUST be there. If the DriverPacks Finisher failed to write that new value to the registry, it would have thrown an error.
From these files:
/I386/eula.txt
/I386/pidgen.dll
I doubt this is the DriverPack Sound B... Please post your DPs_BASE.log.
Changelog
- 0000227: [translations] Swedish translation added (Deaaaaaas)
- 0000226: [DriverPacks Finisher] Double quotes still in DPsFnshr.ini (BashratTheSneaky)
- 0000225: [translations] Italian translation updated (orei)
- 0000216: [translations] Spanish translation updated (ricktendo64)
- 0000222: [slipstreamer] M1: warning that OemPnpDriversPath is too long while it's NOT (BashratTheSneaky)
- 0000221: [DriverPacks Finisher] A couple of wrong quotations in DPsFnshr.ini (BashratTheSneaky)
- 0000218: [slipstreamer (API mode)] AutoIt error when started in API mode (BashratTheSneaky)
- 0000219: [translations] German translation updated (Helmi)
Known issues
[FIXED] -nForce 3 LAN not yet working, DriverPack LAN update on the way...
-installing onto an nForce 3/4/5 mass storage controller results in a BSOD
-installing onto a Sillicon Image SiI3112 SATALink/SATARAID results in a BSOD
-When you've got a certain Windows XP version (not isolated to a specific one yet), then the original svcpack.inf file is encoded in UCS-2 Little Endian. Whenever you use DriverPack Sound A, KB888111 and KB921401 will be slipstreamed and then svcpack.inf will have to be updated. But Windows fails to convert the original encoding to ANSI, and the result is a CORRUPT svcpack.inf! A solution is at hand! Check issue #142 at the bugtracker for detailed information.
Remarks
-You NEED DriverPack MassStorage 6.08, if you want to use DriverPack MassStorage. Older versions are NOT compatible.
Download
I'd suggest this: write a script that automatically installs the setup. And then add an exception to DPsFnshr.ini that detects whether your DVD RAM drive is present. Voila..
Now we'll have to detect it... so please download save_hwids.exe (check my sig) and edit save_hwids.cmd, delete everything and then copy/paste this:\
devcon find * >> hwids.txt
Now send me that file. It'll be too large to attach here.
@jagod: thanks for pointing me to these typo's! But please post this in the betas forum next time
Well... obviously the KB888111 hotfix is installed correctly, so that can't be it.
Hardware conflict, then?
-> move to other PCI/PCI-E port: impossible, is onboard audio...
-> conflict with OTHER hardware?
That BlueTooth controller and webcam are built-in, I assume? Please download the driver that Sony delivered with your laptop and let me know if that works.
Of course that's safe As long as it's the 7zip format it's fine. And keep the same directory structure, of course!
Nope. That won't matter. Then please modify save_hwids.cmd to also report HDAUD devices. It's very easy, the script is just a couple of lines...
Use
instead of
Please post your DPsFnshr.log. The HDAUD hwids are included there, save_hwids.exe doesn't do that.
If it is the modem device that does not work, you can ignore it btw.
You can trust me when I say that that that is a trusted method, it's been working for well over a year now. The CABbed file is renamed, but the internal filename remains unaltered, so Windows will still use iastor.sys!
It's very odd that it isn't working...
Changelog
new
- added 2 Conexant HP drivers
- Sigmatel Toshiba driver
- added 2 SoundMAX ASUS driver
updated
- C-Media AC'97 driver from 06/29/2004,5.12.01.0045 [UDA 045] to 04/12/2005,5.12.01.0048 [UDA 048]
- M-Audio Delta series driver from 04/08/2005,5.10.00.5051 to 10/06/2005,5.10.00.5052
- Sigmatel HDA driver (universal) from 03/20/2006,5.10.4991.0 to 07/27/2006,5.10.5143.0
- Yamaha DS-XG series: added additional .inf files to support more devices
Known issues
-none
Remarks
-none
Download
@coreytk: do a search for '__D-G-A' and remove every complete section in the section name of which it is found. Simple as that.
@Helmi: the cleanup problem is now solved too. See my last post here.
I've changed the behaviour of the DriverPacks Finisher now. From now on, it will only try to recursively delete a directory, and if that fails it will immediately write a new value to the RunOnce key in the registry to retry it one more time after a reboot.
The problem with the double D cannot be reproduced. Did you repackage DriverPack MassStorage, Coccinelle? The 'length exceeded warning'-bug is now fixed.
P.S.: your beautiful pictures of the environment you live in remember me each time why Belgium is such a miserable country... drooooooling for such a beach! 
I'm sorry to disappoint you, but those ARE the original files. The date has changed solely because they have been copied once. But please feel free to compare the MD5 checksums. They'll be identical. I am using the right version. I've compared the drivers in detail to avoid problems/mistakes.
By the way, your hwid is this one: PCI\VEN_8086&DEV_24DF. That hwid is not supported by the driver in D\M\I... but it is by the one in D\M\I\O, so it CAN'T have installed the newer driver!
What was the exact error/BSOD you had when booting?
You'll have to tell me which IBM desktop/notebook you use (product name). I can't find the driver with just the hwid...
Is already fixed in 6.08.6 nightly.
@jtdoom: 
very attentive! I'll try to reproduce this...
Argh.... that sucks! Thing is that it seems to have installed the wrong driver (since the driver file 'ha20x2k.sys' was found, which should not be the case), although the device name is correct (that device name is NOT present in that incorrectly installed driver).
When you have reinstalled Windows, please also post your setupapi.log file, which can be found in %systemroot% (probably that will be C:\WINDOWS).
Posts found [ 1,201 to 1,225 of 1,914 ]
DriverPacks.net Forum » Posts by Wim Leers
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.065 seconds, 5 queries executed ]