[Muki]

When I install vLited Vista Ultimate with integrated hotfixes and drivers I can see during installation a red window where it is written that there are non valid signatures on some drivers. I can install them or not. But I cannot see which drivers have invalid signatures and why. How can I find out these problematic drivers?

[sp00f]

x64 or x86 ?

[Muki]

It is Vista Ultimate x64.

I can see next screen:
 Figure.jpg (38.33K)
Number of downloads: 23

[Kelsenellenelvian]

OK always make sure the drivers you are integrating are official WHQL drivers with a .cat file included.

[Muki]

Drivers are all official WHQL with .cat files. I used them in my one week older integration project and everything was correct. Only differnce bettween these two projects is that the hotfixes are integrated in the newer one but not in the older.

[browney595]

Ive had a similar problem with the latest one i did just have not had any time to check what the problem could be. What hardware drivers are you intergrating?

[Muki]

INTEL INF v8.4.0.1016 WHQL tryed also v8.7.0.1007.
INTEL RAID v7.8.0.1012
MARVELL NIC v10.57.3.3
ASUS ACPI v1043.4.0.0

Later I will add some more drivers.

[browney595]

Can see one thing the same as on my system which is the Marvel NIC unsure what driver version that intergrated as i am not near that machine at the moment i think it was the base driver included with the m/board i am using

[Muki]

I've found out the problem. I've exchanged INTEL INF sources. The wrong version v9.0.0.1008 WHQL was used. There are two unsigned inf files in that version.

[browney595]

looks like im going to have to dig a bit deeper

[MAVERICKS CHOICE]

No known hack for unsigned drivers in Vista UA atm. But if someone knows a workaround do tell....

[sp00f]

This problem is only in x64 , in x86 drivers integrate fine.

And yes.....we need a hack for this

[browney595]

my drivers are x86

[MAVERICKS CHOICE]

Ive found many x86 drivers that won't integrate properly over the last 18 months or so since Vista's existence..

[sp00f]

I integrate many drivers in x86 and never had this problem.
Only in x64.
Wich drivers have this problem?

I will update my driverpack tomorrow , maybe you can use that one.

[MAVERICKS CHOICE]

sp00f, on Jun 4 2008, 10:11 AM, said:

I integrate many drivers in x86 and never had this problem.
Only in x64.
Wich drivers have this problem?

I will update my driverpack tomorrow , maybe you can use that one.

Thanks Spoof will give em a go.

[NTchrist]

I'm working on my own unattended vista, I am attempting to make a version that i can use to perform re-installations on my computer and on many others (I do a lot of freelance PC-repair) and I have integrated hundreds of drivers, the driver signing holdup is unacceptable. At the moment, I use wpi to open a self extracting .rar to put them where I can at least use them. I considered making the drivers into an .ISO, and using daemontools lite + daemonscript (which I have already integrated) to auto-mount the ISO at install, therefore making "have disk" option much easier for drivers.

[sp00f]

http://www.ryanvm.ne...opic.php?t=6228 not updated yet, but it works.
Will update soon.

[ajua]

i have always used driverspath because of the integration of some drivers not always work as expected. this way i never experienced any issue.

oh, and BTW, i want a hack for unsigned drivers too!