Hello,

could you please add the "Samsung SyncMaster 941mw" driver to the DP Monitor?

You can find a working driver here.

Hello there,

this is equivalent to this other problem.

I have included the graphics A 806C testpacks in a slipstream Windows XP installation disk using DriverPacks BASE and used it to install the operating system on an HP Pavilon dv6000 laptop. After the installation the display adapter, an "NVIDIA Geforce 8400M GS", is not properly recognized and a question mark over a yellow circle appears in the Device Manager as showed in the following picture:

http://img299.imageshack.us/img299/9062/20080626225327mr5.png

As you can see in the picture above other two devices are not properly recognized. Does anybody know how could I identify them so that then I can look for their drivers? "Periferica sconosciuta" in Italian means "Unknown device" and its properties show this other information: http://img299.imageshack.us/img299/873/20080626234307yj2.png

*** EDIT ***

I tested it on another laptop with a GeForce 8600 GT: the result is the same as above.

I tested DP Graphics A 806C: unfortunately this problem still persists.

mr_smartepants wrote:

DP_Graphics_A_wnt5_x86-32_806C (20080622)
<link pulled>
MD5: 75E77F1459C2376E26ACE06ACB9E3529
Size: 72.7 MB

Eh eh, I have already downloaded them yesterday, I check the nightlies and 3rdparty directories on a daily basis smile In fact I was wondering how come the 806C hasn't been announced... anyway, I am going to test it asap.

OverFlow wrote:

pss Kirge were you have some issue/problem with the old driver? (i didnt think so) http://forum.driverpacks.net/viewtopic.php?id=1139

Yes, the problem was the same for both the official and test pack.

mr_smartepants wrote:

Well, 8.6 is built into the latest nightly (8.06C).  Lets see what pops up during testing.

Cool! I am looking forward to test it smile

Welcome back smile I was wondering whether the upcoming graphics A pack will include the latest Catalyst 8.6...

Catalyst 8.6 drivers have been released. It seems they bring a lot of new features, performance improvements and bug fixes.
http://game.amd.com/us-en/drivers_catal … radeonx-xp
Will they be included in this upcoming version of the Graphics A pack?

If it can be of any help I can post the inf of the modified Catalyst I used.

Thanks OverFlow, I was about to do that smile

Hello,

could you please add the "CMOS Camera D-Max GD-5A35A VT 071213" driver to the DP Webcam?

It's a webcam installed on Asus X53S notebooks, you can find a working driver here.

As temporary solution I have tried to install the Omega Drivers but later I have found out those drivers where causing the standby-hibernation problem.

As alternative solution I downloaded the ATI Catalyst 8.5 Display Driver, patched it with DH Mobility Modder, and used it to update the display adapter driver after the installation. This has both made the display adapter correctly working and did not cause the standby-hibernation problem mentioned earlier.

I have found out the problem was not due to the chipset driver but to the graphics one.

See this topic for the solution.

waleed_wwn wrote:

Ms has released  KB951126

"A multiprocessor computer that is running a Microsoft Windows operating system stops responding on a black screen after you resume the computer from hibernation "

I don't think it's related to that: the Windows XP installation disk which I used has the Service Pack 3 integrated, and the hotfix for KB951126 is included.

newsposter wrote:

What kind of addon cards and/or "off the motherboard" hardware is in your system?
Some hardware just does not like standby/hibernation and will not recover; the result is often a hung system.

This is the list of my hardware generated with PC Wizard, in case it can be of any help. I doubt it's an hardware problem because, as I wrote earlier, when I used the drivers downloaded from the Intel web site the standby and hibernation worked fine.

I have tried again integrating only the following testpack:

+ DP_Chipset_wnt5_x86-32_80604.7z

but the result is unfortunately the same. The system doesn't recover properly from the standby nor from the hibernation: a black screen appears and a shutdown is required to make the system work again.

I have just noticed I actually had two chipset testpacks in the DriverPacks BASE "DriverPacks" subfolder:

+ DP_Chipset_wnt5_x86-32_806A_PUBLIC.7z
+ DP_Chipset_wnt5_x86-32_80604.7z

DriverPacks BASE picked up only the first of the two during the integration.

Ok, here follows a more detailed explanation:

I downloaded the official chipset driver pack and used nLite to integrate it with a Windows XP installation disk (initially I wasn't aware of the testpacks and I wasn't aware of DriverPacks BASE either). The disk didn't work with my hardware because during installation I got the error "Setup did not find any hard disk drives".

After doing a little research I discovered the problem was due to the lacking of the "Mobile Intel 965 Express Chipset Family" drivers in the chipset driver pack, so I downloaded them from the Intel web site  (I saved them here), and integrated them into another installation disk with nLite. Then the installation process went through and was successful.

I had many problems with other devices back then, but I clearly remember the standby and hibernation were working fine.

What else can I do to help you find the problem?

It was too big to copy and paste it here in a message, so I put it here:
http://www.mediafire.com/?icvrigsxbu1

mr_smartepants wrote:

Can you post your DPsFnshr.log?
I need to see how the finisher handles the exceptions.  And I need the HWID.

Sure smile Can you tell me what are and where I can find the "DPsFnshr.log" and the "HWID"?

Ok, I did the installation again (on the same hardware) using the official graphics drivers and had the same problem.

More precisely the first time I used:

+ DP_Chipset_wnt5_x86-32_80604
+ DP_Chipset_wnt5_x86-32_806A_PUBLIC
+ DP_CPU_wnt5_x86-32_80527
+ DP_Graphics_A_wnt5_x86-32_806B
+ DP_Graphics_B_wnt5_x86-32_806A
+ DP_Graphics_C_wnt5_x86-32_806A

+ DP_LAN_wnt5_x86-32_806A
+ DP_MassStorage_wnt5_x86-32_806C
+ DP_Sound_A_wnt5_x86-32_805
+ DP_Sound_B_wnt5_x86-32_805
+ DP_WLAN_wnt5_x86-32_806A

While the second time I used the same drivers except the graphics ones for which I used:

* DP_Graphics_A_wnt5_x86-32_804
* DP_Graphics_B_wnt5_x86-32_804
* DP_Graphics_C_wnt5_x86-32_804

Hi unseen,

I have to say though that the system wasn't affected by this problem when I used the official chipset driver pack, which at the moment doesn't include the drivers mentioned in my first message of this topic, in conjunction with the ones downloaded from the Intel web site.

Jaak wrote:

Can you use the 'older' but official release and tell us if that one works correct or not?

Sure! It's the minimum I can do to thank you for the great job you guys are doing! smile It's also in my own interest.

Last time I did the installation using the official graphics packs I remember the device was also not recognized, but right clicking on it and doing a simple "Update driver...", without providing any location, fixed the problem. I gather the driver was present somewhere among the the operating system files on the hard drive but for some reason was not installed properly during the installation. At that time to create the installation disk I used nLite only though, I didn't use DriverPacks BASE.

I will repeat the installation using DriverPacks BASE with the official graphics packs asap.

Hello there,

I have included the graphics testpacks in a slipstream Windows XP installation disk using DriverPacks BASE and used it to install the operating system on an ASUS X53S laptop. After the installation the display adapter, an "ATI Mobility Radeon HD 2600", is not properly recognized and a question mark over a yellow circle appears in the Device Manager as showed in the following picture:

http://img246.imageshack.us/img246/8343/20080609100729cb0.png

I have tried the chipset and mass storage driver testpacks and everything worked fine, except that the system doesn't recover properly from the standby nor from the hibernation: that is a black screen appears and a shutdown is required to make the system work again. Should I report it in more details somewhere else?

Thanks Helmi. In the end I found out the problem was due to the fact that I used nLite to integrate the drivers. When I used DriverPacks BASE I didn't get that error and everything worked fine.