[Flo13]

Hi all,

a few days ago i stated to create a Vista-DVD. Everything works perfect, excepting the follwoin two things:

1. I tried to install a nVidida-Driver for my ASUS V1S Laptop (running with Vista 32 Bit). But it does not work!
Frist I tried to install the current driver from ASUS for the V1S (V7.15.11.5654). And then I tried a driver from LaptopVideo2go.com (Version 163.74 with WHQL and modded INF-File) (V7.15.11.6369). vLite accepted these drivers. They were shown normally as NVIDIA, PNP, Display, [Version], [Date] and [Path]. In both cases (integrated with vLite) Vista started with the Standard-VGA-Driver. If I try to install the drivers in a running Vista, everything works! Also the driver from LaptopVideo2go.com works perfect by normal installation.

Who can help?


2. In Vistas "Problem Reports and Solutions"-Window I get some entries with the Problem "Driversoftware not found". But all of this drivers are installed correctly and the Devices are working. Is this a normal behaviour? I guess that this is a message before Vista used/installed the integrated drivers. Are I am right?

Thanks in advance!

Flo

[nuhi]

1. I heard that these modified INF files are not working with vLite integration. Don't know why yet, hopefully I'll find some that works on my desktop PC with the same issue so that I can fix

2. Exactly

[Flo13]

Hi nuhi,

thanks for your reply.

Just one question...

I already figured that the modified inf-File makes trubble. But I can give no account of it, why it´s the same effect with the normal nVidia-Driver of ASUS (with no modded inf-File). Or do you suppose these nVidia-Drivers from the Laptop-Producers includes a kind of modded inf-Files also?

Thanks!

Flo

[nuhi]

Hm, you know what you should try.
Integrate chipset drivers before graphics drivers.
For example if it's intel then insert all Vista folders from the extracted Intel chipset drivers to be the first on the list for integration, then insert forceware below it.
It could be that laptops need that extra chipset info to detect GPU. A long shot but this method should be used anyway.