Search options (Page 25 of 58)

Umm, you do realize the DriverPacks are just for XP x86-32 and not for Vista, right?

If the systems (I presume pre-assmebled and all the same model) came with Vista installed, I'd talk to the manufacturer for a solution to this problem.
It's his duty to supply any drivers for the OS and the HW he delivers...

Otherwise, you could switch to XP and use the DriverPacks on those machines, that is, if you have some 96 XP licences left
(you can also get a "downgrade" from Vista licences at MS!)

You can get it from here.
But, as it says, it's a nightly and I haven't tested it myself yet (holidays and all ), so use it with care.

If you are interested in becoming part of the testing team (and hence test all those nightlies our great team crunches out every so often), send a request to Bâshrat the Sneaky.
There's really not much use in using (more like testing) the nightlies but not giving any feedback.
If there was a serious problem with the current version, the nightly would have been published as a beta.
Usually, you are save to use whatever official version is the latest unless you really need to have an even more recent version for whatever reason

Well, then how comes the UAAHDA drivers aren't installing properly (which is also the reason for the modem failing because soft modems are always connected to the SC)?

Also, if you really were using the DriverPacks, you'd know that we make packs per device class rather than per system, as is your attempt.
It would help a lot more if you split up your pack and posted any missing devices in the approproate sub-forums so these drivers can be added to those respective packs rather than having to integrate a whole new pack just to support one model of notebook.

Probabaly not, but what do you expect us to do about it other than to deprecate them for their actions?

Of course, you could go ahead and litigate them, if you want to, but what are the chances of success in that?
And what is YOUR gain?

If you really want to, I suggest you write an email to one of the companies of which they offer the drivers for sale explaining them the whole situation and hoping their legal department will take care of it.
If it's a big company, it's rather likely they have the means and the money to do so.

If you are lucky, you'll get a "thank you" from the company and maybe even a hardware gift (seeing as it's holiday season and all).

It's your call, but I'm sure we all support whatever actions you take, buddy

And from what I've read, KB888111 has NOT been included...

(I already installed SP3RC1 on my system but since it does not feature a HDA device nor was it a slipstream installation, but a regular one, I cannot confirm this yet).

FWIW, the Vista SP1 RC has also been released to public (don't have link ATM)...

I take it muiz' recent changes are included?

Gotta update that sticky then...

Yay, the Chief is still around!

/waiting eagerly on that new site layout 'n stuff

Should be included, I added a couple of ATi cards during my last update of said pack.

Anyway, the question after the responsibility is hard to answer.
It's "no one" and "everyone" at the same time because the 3rd party DriverPack live by community input so everyone can contribute, however, there is no one officially dedicated to them as in overwatching.

I am trying to keep string together as best as possible but that again requires your work, too!
(For instance, if someone updates a pack but doesn't leave a changelog, the supported devices list will become outdated and confusing pretty soon. If you provide the info on what you did, I am willing to update the devices.htm).

This really is a one for all, all for one project

The Windows XP installation routine is very sensitive towards RAM timings.
This Reboot Cycle of Doomâ„¢ is a common symptom that can even occur if your RAM is not (deliberately) overclocked.
Make sure to select "Safe Defaults" or similar in your BIOS rather than "Optimized Settings" (or such) during installation.
Obviously, make sure to rearrange the booting sequence afterwards so you can boot from your ODD.

You can restore any previous settings once the installation is finished.
This ususally is NOT a sign of defective RAM (though scanning it can never hurt) - I know systems that have and probabaly will continue to run for years without problems, yet they still fail installing XP properly without the safe BIOS options.

PS: You can also check for an updated BIOS version while you're at it.
I know the saying goes about not changing a running system, but yours obviously isn't (why else the (re-)install) plus, more or less recently (five years or so), MoBos tend to be delivered in a rather beta state to the customer so a BIOS update is ususally a routine maintenance task nowadays.

Indeed.
While personally I don't see anything that would keep you from using these files (after all, they aren't ours but belong to their respective companies), there's nothing we can decide here as it's mainly Bâshrat the Sneaky's project.

If you are getting impatient waiting for an answer of him (which can indeed take a while), I'd suggest sending him a mail.

The lack of an answer on this forum does not imply a negative answer nor deliberately ignoring you, please keep that in mind

Must have missed them and never noticed because I don't do BartPE

Will be added in an instant, thanks for the heads up!