1,076

(74 replies, posted in Other)

Just download the DriverPack Sound B, download all DriverPacks, extract the DriverPack Sound B, put the DriverPacks in the 'DriverPacks' directory, start the BASE, configure it to suit your needs and click the Slipstream!-button. That's it.

It's only installed when you use DriverPack Sound A currently. But Sigmatel HD Audio was added to DriverPack Sound B so that should be changed... perhaps you did not slipstream DriverPack Sound A? Then that explains this last issue.

1,078

(10 replies, posted in DriverPack WLAN)

muiz3 wrote:

I had 4 pcs this week with all linksys cards in them , they all didnt work ( 3 different cards)
Sometimes i dont have the time to save the drivers and hwids from customers pc's , i'm sure you can understand that wink

Of course I can understand that. But that's not what I ask. I only ask to mention the device's name in a problem report like this one. How would you expect me to fix it, if I don't know with which device there's a problem?

Please post your DPsFnshr.log again, that might help tracking down the cause.

1,080

(19 replies, posted in Other)

fargo wrote:

Maybe I did something wrong the first time! I repeated the process today but did NOT get any DSP window!!! How can I make the DSP windows to show up again?!

Why would you want that? CloseDSP.exe is there to CLOSE the DSP popups... wink

1,081

(3 replies, posted in DriverPack Graphics)

Fragbert wrote:

Isn't linked on the Graphics download page, but adding a "1" to the 608 download url got the 608.1 release. Also, base tells me "Where did you get that?" smile

Argh! The file that contains the current settings wasn't uploaded properly. Sorry!

1,082

(6 replies, posted in DriverPack Graphics)

Probably you can use the same control panel as the one in DriverPack Graphics A! wink You'll just have to use DriverPack Graphics A too and - more important - you'll have to wait for the next update of the DriverPack Sound B until it will be working: I'll have to update the DPsFnshr.ini to reflect these new exceptions!

According to the DPsFnshr.log you just sent me, there's a problem with the second part of the exception:

2006-08-27 15:16:17 : <EXEC> Executing all commands (2) for exception [wnt5_x86-32__0006__D-L-NV-123].
2006-08-27 15:16:17 : <EXEC> 	Executing command 1 of 2: "%SystemDrive%\devcon.exe updateni %DPSROOT%\D\L\NV\123\nvnetbus.inf "PCI\VEN_10DE&DEV_00DF&SUBSYS_E0001458&REV_A2""
2006-08-27 15:16:18 : <EXEC> 		STDOUT: Updating drivers for PCI\VEN_10DE&DEV_00DF&SUBSYS_E0001458&REV_A2 from C:\D\L\NV\123\nvnetbus.inf.
Drivers updated successfully.
2006-08-27 15:16:18 : <EXEC> 	Executing command 2 of 2: "%SystemDrive%\devcon.exe updateni %DPSROOT%\D\L\NV\123\nvnetfd.inf "{1a3e09be-1e45-494b-9174-d7385b45bbf5}\NVNET_DEV*""
2006-08-27 15:16:18 : <ERR>  		! STDERR: devcon.exe failed.

But we can conclude now that the issue is in the exception code and NOT in DriverPack LAN. I will continue working on this issue after I've updated the other DriverPacks.

This is not an official release and will therefore not be included. When it's officially released, it will be added.

1,085

(2 replies, posted in DriverPack LAN)

Perhaps it will be solved automagically thanks to th driver update in DriverPack LAN 6.08.1 (which is not yet online at the moment). Please let me know if the problem persists!


EDIT:
Closed due to lack of reply.

1,086

(1 replies, posted in DriverPack LAN)

Fixed in verion 6.08.1 (not yet online at this moment).

1,087

(3 replies, posted in DriverPack Graphics)

Changelog
updated
- ATI Radeon driver from 07/18/2006, 8.273.0.0 [6.7] to 08/02/2006, 8.282.0.0 [6.8]
- ATI Mobility Radeon & Mobility FireGL driver from 07/18/2006, 8.273.0.0 [6.7] to 08/02/2006, 8.282.0.0 [6.8]
- nVidia GeForce Go 7800/7900 GTX driver from 11/04/2005, 8.1.9.4 [81.94] to 04/25/2006, 8.4.6.3 [84.63]

Known issues
- none

Remarks
- Not compatible with the old DriverPacks BASE (pre-6.06)!

Download

I won't add a driver that's specifically optimized for ONE device (and only compatible with that one device), especially not if that device is so extremely rarely used due to its price. Sorry.

Nope it should not. And I need the actual slipstream log, not the log of just starting the GUI...

Please also post your DPs_BASE.ini and DPsFnshr.ini.

1,090

(6 replies, posted in DriverPack Graphics)

Changelog
new
- ATI (Mobility) Radeon pre-9500 driver (no longer supported by the main Catalyst driver since version 6.6)
- PowerVR Kyro & Kyro II driver
- S3 ProSavageDDR (420) driver
- S3 Savage4 (394-398) driver
- S3 ProSavage (370,377) driver
- S3 Savage/MX-/IX (290-299) (AGP & PCI versions) driver
- S3 SuperSavage (584)

updated
- ATI Mobility Radeon M1 driver from 03/27/2001, 5.00.2195.4056 to 06/16/2002, 6.13.10.5796 (kept support for the other device supported by the older driver)
- Intel GMA900, GMA950, GMA3000 driver from 02/07/2006,6.14.10.4497 [14.19.50] to 08/14/2006,6.14.10.4670 [14.24] & 06/02/2006,5.10.00.1014
- SiS UniVGA3 driver from 01/09/2006,6.14.10.3720 [3.72] to 06/29/2006,6.14.10.3750 [3.75]

Known issues
- none

Remarks
- none

Download

I will wait for the next 'official' regular GeForce WHQL driver nevertheless. But when I've updated DriverPack Graphics C, this driver will be chosen over the default driver anyway so you can still be happy wink

Please post your DPs_BASE.log and DPsFnshr.log!

Added the 6.5 drivers to DriverPack Graphics B, which had been planned a long time ago, but got delayed for too many reasons... My apologies!

I've updated the modded .inf files accordingly and now the ATI Mobility Radeon 9200 should be working again, together with all other pre-9500 Mobility GPUs.

EDIT:

@Major: correct on all areas! wink

This device is already supported by the driver in D\G\A\5 (DriverPack Graphics B). Unfortunately your specific HWID was not yet supported. The driver you linked to is newer than the current one so I will customize the .inf file to only use ONE driver, since it's a rarely used driver.

One thing remains unclear. Did you try to install the drivers through the installation utility because NO driver was installed? If not, what was the reason for running the ATI Catalyst setup?

Fragbert wrote:

Well as long as you feel my troubleshooting is worthwhile to continue, I can go ahead try systematically to find the culprit in SCSI.Load

I'll start by remarking one half of the list (keeping iastrold of course) and if it loads properly, then we know that half of the list does not have the culprit, so then on to the other half of the list, then segment that list into halves, and try to narrow down which one is causing this mess without going through a whole spool of CD media smile

Yep, binary searching for the culprit is the best way to do it! wink smile

The setting in the .ini is invalid then. It says "all" while it should be set to "select": because NOT all DriverPacks are selected! I'll notify RogueSpear of this.

Fragbert wrote:
Bâshrat the Sneaky wrote:

The JMicron drivers. I think you only commented ONE of the TWO JMicron drivers during your tests?

I commented out both, the raid and the ahci and still got the error. Are there other jmicron drivers or oem drivers that are similar to jmicron?

Nope. This problem is a real PITA...

1,099

(10 replies, posted in DriverPack WLAN)

Well... all drivers are included now. If you have problems with a specific type, you'll have to let me know it. Saying 'almost all' doesn't help very much, I'm sure you can understand that wink

It wasn't offensive, muiz wink He was just joking (if you doubt that, see the smiley...).

Personal attacks are not tolerated at this forum. If you feel offended, please let that know the other person through mail, but don't start a flame here. This dispute is hereby ENDED.

Helmi is right when he says that the required time matters less when doing an unattended install, muiz is right when he says that it's taking too long. End of story.