Search options (Page 59 of 99)

nope.
These are drivers that were disabled ages ago. They ought to be moved to the SFXminiPacks.

chaz

your links are always broken.

[url=yourlink]thisorthatname[/url]

zalman for jaak

this is a TEST version

intel 7.5 updated to 7.6.1011

show us how you did it, and what issue it solved.
The atapi driver for ITE has a lot of extra HWIDs, but, a lot of overlap.

the raid driver is backward compatible with IDE/atapi, and if we try put atapi in the mass storage INI, there is a good candidate for creating a problem because of version newness.

An example, Via raid currently has viamIDE in the pack, which is NOT in the mass storage INI, but solely for PnP.
Some users liked that, other user reports problem.
Vendors use same HWID for different modes, and when different BIOS settings still show same HWID to TXTmode.. your raid array could go B7.

everyboby here want to avoid BSOD.
you tell us more detail, we may find a workable solution.
we've already established DriverPacks cannot be a universal pack.

aha?
is there a 7.6?

in this set, the CATs can be put back in.

D\S\S\D\3

D\ driverpacks main (where all combine in)
D\S sound
D\S\S sigmatel and nested in there... \d\3

in a changelog, it says folder under root of the pack
root, in this case, D\S

txtsetup.sif line xxxx error solved

XP's native txtmode drivers apparently recognise hard drives

Hi, please note that that INI section was changed later on.
(in build 7.08.1 for testing)

slipstream had created the MRdellK3.sy_, but when setup ran, an error popped up about line xxx (the line referring to Mrdellk3) and setup halted.

Helmi reports that the driver runs his drives in XP, but has an issue in hardware manager, which is telling him it is not intended for XP. (and hibernation cannot work).

Far as I know, you cannot use a USB stick with 7zip.

it cannot create output file

'7.08.1',
link is dead.. see later

another driver would use same drivername.sys, and was set to replace native driver in xp/2k3.

second driver had no HWID duplicates.
the File got renamed, and its INF edited to internally refer to new name.

earlier link is dead.

yes.

Hi

the second part in this already does that.. it uses the 2003 files, and only disables 2000.
ms_2_exc_disableIfOS="w2k"

2000 is in the first part in this driver INI section.
ms_1_exc_skipIfOS="wxp,w2k3"
therefore, XP and 2003 skip it.
2000 is disabled so as to avoid 'out of memory.' ..
if you need this driver in 2000, remove or comment out the line (ms_2_exc_disableIfOS="w2k") and maybe add ms_2_exc_disableIfOS="w2k" to another section that does not have it.
We are probably quite close to the memory error..
(When we got too many enabled not long ago, a member had to manually disable some, then some more, and some more, and told us about his experiences, so we had an idea how many we had to disable and did so..)

right now, when I add a new driver, I always disable it for 2000.