51

(41 replies, posted in Vista / 7 DriverPack Graphics B)

ATI @ 9.3 now smile

52

(78 replies, posted in Vista / 7 DriverPack Audio)

Realtek HD audio now @ 2.19

53

(73 replies, posted in Vista / 7 DriverPack Mass Storage)

One complaint about Masstorage x64 - even if you do not have a SI controller, a SI control panel applet will be installed regardless. I remove the SI folder completely from integration for now.

54

(39 replies, posted in Vista-Tool)

jfrankli wrote:

Hi Guys,

Any chance this app can work with Vista Enterprise Edition.

I have tried to slipstream drivers into Vista Enterprise and it doesn't seem to work.

I have successsfully slipstreamed drivers into Vista Business so I think I understand the process ok.

I noticed in the readme for the tool that you need to select your image:

1 = Vista BUSINESS
2 = Vista HOMEBASIC
3 = Vista HOMEPRENIUM
4 = Vista ULTIMATE
5 = Vista HOMEBASIC N
6 = Vista BUSINNES N
7 = Vista STARTER
8 = ??
9 = ??

Vista Enterprise doesn't exist. Will it ever?

Use Vlite to consolidate your wim to one instance and you can then just select "1". Or perhaps that's already the case? What does your folder directory look like inside your install.wim?

55

(107 replies, posted in 3rd Party DriverPacks)

RogueSpear wrote:
Fragbert wrote:

As much as I like the concept of a HID pack, the logitech mess still creeps up and makes some setups unusable. 90204 lists v4.7 of setpoint drivers, however my 5500mx revolution combo would yellow mark in the device manager until I manually installed 4.7 from logitech's website. What is so tricky with logitech drivers?

There's two installers with SetPoint, CDDRV_Installer.msi and KhalInstaller32.msi.  Do you think if I made those into exception installers that the problems would then be fixed?  From looking at them myself, I just really don't know.  At this point that only Logitech HID devices I have at the ready are bluetooth mice - and since those need to be paired up post install, everything seems to work flawless.  I am guessing there's a difference when it comes to a directly connected USB device that detects during setup itself.  Anyway the point I'm trying to make I suppose is that I can make the installers and update the DP, but I won't be able to properly test the proposed solution.  If you, or others, are willing to test it out I'm willing to put together the installers.

I'm willing to test, it just wont be as frequent as I like. Thanks.

Updated! Looks like intel is trying to make G45 work better with DXVA.

Updated to driver v6.14.10.5035 from package v14.38.0.5035! Link URL never changed, wierd.

58

(107 replies, posted in 3rd Party DriverPacks)

As much as I like the concept of a HID pack, the logitech mess still creeps up and makes some setups unusable. 90204 lists v4.7 of setpoint drivers, however my 5500mx revolution combo would yellow mark in the device manager until I manually installed 4.7 from logitech's website. What is so tricky with logitech drivers?

muiz wrote:

I have wim's bigger then 4gb, and no corrupt error.

You must not use your own VISTA TOOLS cdimage ISO builder then, because you cant build an iso with a file over 4GB in it.

shahed wrote:
Fragbert wrote:

If you are making a image w/ a wim larger than 4GB you will get a corrupt ISO because of the utility VISTA TOOLS uses to build an ISO.

Thank you fragbert. I did mention this above before, vista-tools and vlite does not support wim files larger than 4gb, and reports corrupt wim.

I think it would be a quick and easy fix for Vista Tools to simply call on the native WAIK iso tool to build ISOs, as it does not have the limitation.

mr_smartepants wrote:

Well, I'll agree that the Vista-Tool needs a lot of work.  Maybe it's a limitation of WAIK since this tool is just a front-end for WAIK.  I've tried three integrations of Vista64 and all three times I've had to scrap the source and try over.  Vista-tool corrupts my install.wim.  And it takes forever!
I can't even get the tool to build an ISO!  Just telling people "works for me" doesn't help anyone.
Sorry Muiz/shahed, but I think I'll stick with vlite for the time being.  At least it works partially.
Sorry for venting my frustrations, but I've just wasted two days on this that I won't get back.

If you are making a image w/ a wim larger than 4GB you will get a corrupt ISO because of the utility VISTA TOOLS uses to build an ISO. To get around this you can use the ISO utility built in WAIK that allows >4GB file sizes or you can use IMAGEX /split to segment your wim into smaller sizes so the older ISO utility in VISTA TOOLS can build the ISO.

Again, dont blame you for not knowing this, the documentation on this bug is practically non-existent. Only those like us, who's goal is to make a fully updated, unattended Vista DVD will we build a wim that large.

Legolash2o wrote:
muiz wrote:

Doesnt Legolash his tool imports addons?

Yes, still in an alpha state though. I have managed to integrate Firefox 3.0.6 smile

Fragbert wrote:
muiz wrote:

The tool works fine here, im using this for a very long time.
So when something doesnt work for you, dont blame us or the tool.
It makes perfect sense to me and many others.
If you can make a better tool, show us.

Now if you could only have application integration tongue There's not a single tool out there that does this correctly (despite claiming they do)

Which tools claim they do?

Your old alpha for one smile You can read more about that here: http://www.wincert.net/forum/index.php?showtopic=4620

Updated link to 6.14.10.5029 from package v14.37.1.5029

64

(6 replies, posted in DriverPack Graphics)

Yeah I know *exactly* what you are referring to in regards to the Dell driver. The driver pushed through Windows Update is an oem of intel graphics specifically for dell and perhaps looks for a specific HWID or other identifier. In my case, the later Intel branded drivers work, but the driver still gets flagged in Windows Update.

muiz wrote:

The tool works fine here, im using this for a very long time.
So when something doesnt work for you, dont blame us or the tool.
It makes perfect sense to me and many others.
If you can make a better tool, show us.

I'll second mr tmservo in that the interface itself is not the most user friendly and there is a steep learning curve (much like all of the unattended vista methods elsewhere). But I'll say this, this is the ONLY tool that flat out works. Mostly due to it staying strictly in the realm of WAIK. I am kind of glad that the documentation is a little sparse because it really forced me to understand WAIK and how updates and drivers are integrated, once that happened everything in Vista-Tool makes perfect sense to me smile

Now if you could only have application integration tongue There's not a single tool out there that does this correctly (despite claiming they do), and I'm already burned from following FireGeirer's guide on app integration whose instructions are no longer valid for Vista SP1 native builds (his guide is a GREAT resource otherwise).

66

(107 replies, posted in 3rd Party DriverPacks)

From what I can tell, the DP will need different revisions of setpoint to cover all Logitech mice (and OEM variants). Royal pain.

67

(88 replies, posted in DriverPack LAN)

Overflow, yes no problem smile

68

(88 replies, posted in DriverPack LAN)

v13.5.1 out, however not official yet. Will update 1st post w/ official link to Intel when it becomes available.

Link to readme notes: http://www.station-drivers.com/telechar … 13.5.1.txt

request updated to v9.1.0.1012

OverFlow wrote:

mass updated ...

and yes newsposter I updated the device list too wink

sorry it was out of date before!

This is what the OP was referring to: http://driverpacks.net/DriverPacks/devices.php?pag=m

Still has 2003 driver info smile

71

(39 replies, posted in Vista-Tool)

shahed wrote:

If you use Vista-tools to integrate drivers, you will not get any driver signature problem. The driver signature problem is not with a modified DVD. But if you used vlite to integrate drivers, then you will get driver signature problem.
Hope this helps..

What does Vista-Tool do to circumvent the unsigned driver prompt?

Updated to v6.14.10.5016. From now on I'm updating this thread with actual driver revisions as opposed to "packages" since the latest package is a number LOWER than last months v14.37, the latest is now v14.36.5.5016. Can Intel be any more dumb??

I'm going to defend the original poster here because he did exactly what a new user should do; before downloading all these packs, see if their hardware is supported and RTFM - and WOW! Can we say that device list is old for mass-storage!?! I wouldnt fault anybody for asking what can be perceived as wasteful questions if they had already referenced the official documentation!

For reference, your hardware uses the common IaStor drivers which have been supported for a long while now. The latest v8.6 I believe is in the latest nightly pack, not sure about the latest (and old) official DP for MS.

74

(39 replies, posted in Vista-Tool)

muiz wrote:

We leave the tool the way it is, we are using this for a very long time now, and it works perfect.

Unless you have x64 and need to manually edit xml files, defeating the purpose of a GUI front end in the first place smile

75

(88 replies, posted in DriverPack LAN)

FINALLY OUT. Had to open an incident with Intel Customer Support tongue

http://downloadcenter.intel.com/Detail_ … ldID=13478

v13.5