You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by Wim Leers
Check out Helmi's second suggestion. It may save you some time 
It's very easy to create your own 3rd party DriverPack. If you can do RIS installs, then this is a laugh.
EDIT: may I ask you what company you work for? Drivers for biometric devices and HDD shock protection systems are completely unknown to me! You can contact me through mail if you prefer to not put it in public.
As I've said in the bugtracker, this device:
PCI\VEN_10DE&DEV_026C&SUBSYS_CB8410DE&REV_A2\3&267A616A&0&81: PCI Deviceis a USB controller, which should be supported by the drivers included in SP2.
@Helmi:
2006-08-22 12:44:13 : <CLNP> The cleanup has already taken more than 10 minutes, because C:\D\A\G\T\Display.lnk' is locked by a process. The cleanup has been ended.
2006-08-22 12:44:13 : <CLNP> Added new value to the RunOnce key in the registry: the cleanup of the 'C:\D' directory will be retried (through CLI, not through the Finisher) after a reboot.That's the reason why it did not finish But as you can see, it will be deleted after the next reboot. It's very strange though: none of the control panels was installed, so I wonder why that file is locked...
And I'll try to reproduce your KTD problem with the same setting.
@coreytk: Darn! STILL some typo's in the DPsFnshr.ini! My bad... will fix it asap.
Hey if i go devices manager - Nvidia nForce Serial ATA controller properties - Drivers -update driver - fine one driver - then unpack your DP - then UNTICKED "Show compatible hardware" it show me 2 listing for the 590/570/550 SATA controller .666 & .667
with the Raid Class controller with show compaitble hardware TICKED it shows 2 version again 5.10.2600.666 & 667 this where i would say it's getting confused,......
i have so screen shots but i cant work out how to upload them if u want to have a look just let me know
ps this was all done on 6.08.5
I'm not sure I understand what your point is... Please clarify!
This problem is solved in the DriverPack Sound B 6.08.5. Note that this would occur in very specific, rare circumstances.
See bug #212. It's already solved in 6.08.5.
Topic closed.
Ah darn... stupid that I only see it now. I'll fix it in the next update!
EDIT: submitted the issue: issue #218
No more RAID problems either?
6.08.5 has been released and it should be working now, though testing is still necessary. According to jagod it's working now 
I guess that is indeed due to your overclocked system ... never seen anyone have that BSOD yet!
OK, don't forget to report back
Huh? You should only have ONE log entry and you should have gotten NO warning at all... THIS is strange 
Probably a typo, then. Will fix it in the next update.
Changelog
- 0000217: [GUI] When using nightly for newer version than the currently released one, the currently released one is still detected as newer (BashratTheSneaky)
- 0000207: [DriverPacks Finisher] ATI Catalyst Control Center installed but not working, due to typo's in DPsFnshr.ini (BashratTheSneaky)
- 0000212: [GUI] After selecting valid location, when using back/next buttons, the GUI becomes a mess (BashratTheSneaky)
- 0000189: [GUI] AutoIt Error while creating second ini file for multiboot. (BashratTheSneaky)
- 0000214: [slipstreamer] Non-standalone version of 7zip included, which results in many errors during slipstreaming (BashratTheSneaky)
Known issues
-multibootDisc support is UNTESTED. Please test so I can make the necessary improvements and bugfixes.
-nForce 3 LAN not yet working, DriverPack LAN update on the way...
-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
-Documentation later! Just use it as-is now. It's all pretty self-explanatory...
-You NEED DriverPack MassStorage 6.08, if you want to use DriverPack MassStorage. Older versions are NOT compatible.
OK, the decision is final.
I will be using a CMS that's very comparable with the one at http://unattended.msfn.org/ , in fact it will be of the same author (for those of you who know the 'celebs' of the MSFN forum, it's Alanoll who wrote it!). We're working on it right now.
This means I've chosen for the 'wiki with permissions' concept. You won't notice it's a wiki, though you can submit new pages and changes to existing pages. But they will need my approval before they will be published. It's the best of all worlds: if you think some point is not clearly explained, you can submit the changes you think are necessary. But spammers won't get a chance either.
A PDF version of the guide will also be available. It may not be equally good as a .chm file, but this one is platform independent (Vista will be using a different help file format). And we've got to be realistic: the documentation won't be nearly as big as the one of PHP or so, so the need for a .chm file is also much lower.
Well... compress ONE of them and then compress BOTH. Using 7zip of course. Tell me what the difference in file size will be... A few KB probably.
Though I must admit that I did not scan for these differences. It was to be expected of course. But this definetely can save about 13 MB off of the required space if you use method 1. Will implement this in the next update! Thanks!
Hey Bâshrat the Sneaky if i unzip the massstorage DP, replace the the 590SLI drivers with nF4 drivers, and repack would that work for the time being???
Also fyi Im using "5.10.2600.667" instaed of the "5.10.2600.666" drives all around at the moment and they seam to work fine
So instead of this:
RAID Class controller 5.10.2600.667 1/5/06
RAID SATA raid contoller 5.10.2600.666 24/4/06
... you're now using this:
RAID Class controller 5.10.2600.667 1/5/06
RAID SATA raid contoller 5.10.2600.667 1/5/06
... right?
I've pulled 6.08.4 back, because there were some critical issues with it. They're actually minor errorsm but cause major problems for you, the end-user
6.08.5 will be put online tonight!
Fixed now.
There seems to be a major problem with 6.08.4: the included 7z.exe seems to be NOT working! That would also be the cause for this problem...
This topic is closed now.
I already AM handling this. I'm using 2 drivers, also for textmode setup!
Please post your HWID so I can find out if I have assigned a HWID to the wrong driver.
Changelog
- 0000211: [GUI] when no DPs_BASE.ini present, keep the standard "disc" instPlatform, select a valid location: the GUI isn't updated accordingly (BashratTheSneaky)
- 0000203: [translations] Polish translation updated (dziubek)
- 0000209: [slipstreamer] KB913425 (portcls.sys) has been replaced by KB921401 (BashratTheSneaky)
- 0000210: [GUI] [M1]: when creating OemPnpDriversPath, lots of log messages instead of ONE (BashratTheSneaky)
- 0000191: [slipstreamer] Critical error while trying to slipstream multiboot (BashratTheSneaky)
- 0000197: [translations] Slovenian translation updated (amitri)
- 0000137: [slipstreamer] New version of 7z.exe: 4.42 (BashratTheSneaky)
- 0000152: [GUI] whenever you view the details of an OS inside a multibootDisc, the overview page is not correct (wrong platform, settings, etc) (BashratTheSneaky)
- 0000206: [translations] Bulgarian translation updated (chertoianov)
- 0000204: [translations] Spanish translation Alt + P in KTD settings used twice (ricktendo64)
- 0000189: [GUI] AutoIt Error while creating second ini file for multiboot. (BashratTheSneaky)
- 0000192: [GUI] Clear Location path after changing from disk mode to multiboot or vice-versa. (BashratTheSneaky)
- 0000160: [translations] If you select Turkish language, DriverPack Base crashes (KenanBalamir)
- 0000179: [GUI] GUI messed when from multibot changed to disk. (BashratTheSneaky)
- 0000201: [DriverPacks Finisher] error: Windows Cannot Find '-s' (BashratTheSneaky)
- 0000143: [translations] German translation updated (Helmi)
- 0000199: [DriverPacks Finisher] [KTD] flaw that triggers error: "[Settings]\KTD has an invalid value: ...", which disables KTD always (BashratTheSneaky)
- 0000198: [translations] Polish translation updated (jagod)
- 0000194: [translations] Fixed Spanish translation of Siginet (Windows version detection) on the About page (ricktendo64)
Known issues
-multibootDisc support is UNTESTED. Please test so I can make the necessary improvements and bugfixes.
-nForce 3 LAN not yet working, DriverPack LAN update on the way...
-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 KB913425 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! I'm try to find a decent conversion method.
Remarks
-Documentation later! Just use it as-is now. It's all pretty self-explanatory...
-ONLY THE GUI IS TRANSLATED. The strings in the slipstreamer are to be followed, the code is already there!
-You NEED DriverPack MassStorage 6.08, if you want to use DriverPack MassStorage. Older versions are NOT compatible.
Then this is very strange behaviour. IF you have used DriverPack CPU, then the Finisher should have filtered the exception for the AMD X2 CPU. Please post your DPs_BASE.ini and DPs_BASE.log to verify that you have selected DriverPack CPU to be slipstreamed.
Don't forget the [ code ] tags
You're only using DriverPack LAN, is that correct?
Sorry for the delay.
I verified that these drivers do not support Windows Server 2003. And Creative does not provide any! This is not bad behaviour by Creative though: it's quite normal that a server OS isn't supported by an audio driver, since a server isn't built for that purpose.
I could make the necessary driver hacks to let it install, but I won't guarantee you that it will be stable. Would you like to test it?
Ah yes, now I remember... while I was cleaning up DPsFnshr.ini, I found an error related to this one. It should be working in the latest nightly. You could test that, maxximum
Test it by doing this:
-extract DriverPack CPU (ONLY this one) to C:\
-extract DPsFnshr.7z to C:\
-copy DPsFnshr.ini to C:\
-START the Finisher, and post your DPsFnshr.log here.
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.069 seconds, 5 queries executed ]