Search options (Page 9 of 99)

Answer= no.

I don't want to google your machine. (and then try find what we do not have)

You have it, but you did not provide detail.
We do not provide solutions by machine type and do not have a database per machine type.
We can add drivers, but we ask that you help us determine what we have to add.

you could be lucky.
a regular may take interest.
If not, you will have to help us help you.

Hi LeV,

it would be eXtra work to remove languages. (Looking at a driver's install routine is work. I see some in which it is a hopeless task, as each language has its own INI and each INI is actually referenced in main INF, or the INF is poking a INI which is calling other INI.)
DriverPacks experts and team members are not infallible, but we usually know what can break a driver.

I also think we have to get size out of the picture.
There was never a rule of making it as small (DISC burn limit) as possible.
USERS reQuested it be as small as possible, but more oft than not, that was not the smartest solution.

MY ideal is:
A small enough memory footprint with the Least conflict. (mass)
Everything, with no conflict. (all other, and mass)
Stable drivers before the latest.

this is not my idea, but ours. Jeff, Erik, Hans and all other team members agree to stable.
Conflicts are hard to find. (How on earth could machine coders use same routines for widely different hardware, and get WHQL certified when they submitted the driver..)
Instability in a driver (by its own) is a nightmare to us.
I have seen a site boasting they can give you the perfect driver.
I cannot say we have the perfect set, and we do not boast we have that set.
We help you by filtering. A good many conflicts were eliminated in the last two years.
You (members/team/testers) help us by telling us what works, and what doesn't.

I've been busy outside DriverPacks. While I was not focusing, I could see a wider perspective.
I think I still fit in that picture, and regret I have a real life project stealing a lot of time.
(house remodelling)

Hi
I'll answer you with a question.

if we had to have this for txtmode, how could a Method one slipstream see the hard disk?
(M1 does not use "fakesetup" at all.)

the Jmicron driver supplied by gigabyte does behave different than the reference driver by Jmicron.
I will probably have to add the gigabyte version, and then edit the reference driver?

there was some forum group effort behind this, I suppose.
Is this open source?
Is this in alpha stage? (the topic title may have to be changed.)

As an aside; and FWIW, I think that releases of WAIK and DPinSt and inhouse/published tools to work with 2008 made developments like this possible.

I figure our admins want to know this up front.
Is this in autoIT?
will you help us improve it (not jut plug it).

I know this Sounds like a Cold shoulder, but I would LOVE this functionality.
I just don't know how DriverPacks will grow and what turns we'll have to take.

we have a few developments going and they would go to x64.
but XP x64 was not in the picture. (vista x64 is)

@DriverPacks, we was hounded by people craving for space on their CDR and x64 drivers were pruned out.
And, imho, there is nobody here who has access to all original drivers (we often do not know if there ever were x64 present in a set.)

The consent (in my point of view)  to date is that 64 for vista is definately not pruned, and x64 for XP shall not be edited out when we update.
(which would bring back X64 for XP whenever there is a review of a driver that had it.)

JakeLD?
please test that 807a for D4 of which you said you NEED it.

the generics clashed with iastor 55 and an LSi.

[[ I know it was not for XP/ and 2003 only]] but samlab had issue

S.A.D. makes us happy
I can tell you it worked as promised on different occasions, and I timed it against a older personal built 'method one supreme'.
(if you read about the short short.. good)

SAD ported to fast media wins.
DVD are slow.

SamLab, I have always wondered why your HWID dump list always scrolls off and does not have all the info about the found HWIDs.

have you removed languages from the source with Nlite?

807a
official intel AHCI and ICH9R updated
Jmicron updated
replaced Via drivers with WHQL signed (full and original content of hyperion 5.18a)
(which is not an update.)

addon to official intel AHCI driver for XP,
highpoint drivers for server
adaptec SAS drivers updated
adaptec SAS driver added (generic HWID removed)

one or two of those machines will also run extended beta tests on online armor and other software.
I was allowed to test, was given keys, and don't want to let down that project.
(stable product for XP/2003 only, can be had free or paid. The beta is adding vista support and new features)

I was also comparing SAS and MBaM, avast and AVG, avira and kaspersky, and still do betas for adaware and IE8.1 and liveonecare (and so on..--)

Thank you for the report.