Search options (Page 65 of 99)

Thanks just the same.

I don't know if we are going to delete drivers because this, but you know what you had to do, and it worked.. so you can use the disk you made.

This has been an option since a few months now, because Bâshrat the Sneaky got the INIs in the packs so his public can use it to make adjustments.
There is no handbook on How to do this, but there are a few great posts about this already.
Bottom line is, you did it, and other will have to.

It will happen that you replace a driver with one for your particular BIOS version of a chip, and edit the INI so it contains the HWIDs your driver lists.
When you do that, make sure there are no other drivers with same HWIDs in the INI, and let us know you had to do this.
Same device, different BIOS, customised pack.
I've made one today.. it happens to be a SiL image.. whaddacoincidence..

Hi
I just lost the entire post I wrote..

I'll rewrite..

if you cannot Flash or don't want to flash all affected machines..
then you have to un7zip a copy of Mass storage DriverPack
(use a copy..)
Then replace D\S\4 content with the content of the older driver
3x12_13670_x86_logo.zip

Then edit DriverPack_MassStorage_wnt5_x86-32.ini
Get to section S-4 and replace with

[S-4]
ms_count=1
ms_1_deviceName="Silicon Image 3112 OLDBIOS Controller"
ms_1_tag="si3112"
ms_1_sysFile="Si3112.sys"
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_31121095,PCI\VEN_1095&DEV_3112&SUBSYS_34238086,PCI\VEN_1095&DEV_3112&SUBSYS_311215D9,PCI\VEN_1095&DEV_3112&SUBSYS_B0021458,PCI\VEN_1095&DEV_3112&SUBSYS_01661028,PCI\VEN_1095&DEV_3112&SUBSYS_81E8104D,PCI\VEN_1095&DEV_3512&SUBSYS_35121095,PCI\VEN_1095&DEV_3512&SUBSYS_01661028,PCI\VEN_1095&DEV_3512&SUBSYS_35121014,PCI\VEN_1095&DEV_3512&SUBSYS_02B71014,PCI\VEN_1095&DEV_3512&SUBSYS_B0021458,PCI\VEN_1095&DEV_3512&SUBSYS_81E8104D,PCI\VEN_1095&DEV_3512&SUBSYS_820B104D,PCI\VEN_1095&DEV_3512&SUBSYS_145A1462,PCI\VEN_1095&DEV_3512&SUBSYS_001F6409,PCI\VEN_1095&DEV_3512&SUBSYS_9003104D,PCI\VEN_1095&DEV_3512&SUBSYS_35121A5F,PCI\VEN_1002&DEV_436E&SUBSYS_436E1002,PCI\VEN_1002&DEV_4379&SUBSYS_43791002,PCI\VEN_1002&DEV_437A&SUBSYS_437A1002"
ms_1_isBusExtender=false

Save.
Then select DriverPack_MassStorage_wnt5_x86-32.ini and the D folder.
7zip it, it will propose to use DP_MassStorage_wnt5_x86-32_7071.7z
Don't do that, change that name.
When I made a tiny pack for the oldBIOS version of this chip, I called it
DP_MassStorage_wnt5_x86-32_7072_SiL_OLDBIOS.7z
(Higher Version, and distinctive telltale txt.)
(The Tiny one I made only has the changed files and INI.)

Test the pack you made on an affected machine.
Good luck

Hi
I wanted to reply yesterday, but real life did get in the way..
There is home improvement going on, plus a call for a PC/printer malfunction.
(it was a long day.)

At the drivers page your link gets us to, they mention different BIOS.
Now.. Which BIOS does it have?
(Look for that while the PC starts up. Or use an advanced system info gathering tool.)

The problem with these BIOSes is that you may not be able to update it.
The Flashtool is NOT meant for Onboard controllers.

The problem we have is that the driver will list the same HWIDs, but they make changes in the driver for the BIOS variant.
So, it is a different driver.
And we cannot have both, because they cause conflict with each other ((txtmode picks one, and later on, other gets loaded.. bingo.. )

So, I think you will have to look which BIOS it is (do you have a lot of those machines?), then download the right driver (or flash..)
I believe we use the one for latest BIOS, but I'd have to verify this, tho.

If ours is for wrong BIOS (w/i most likely) then you would have to replace it in the pack.

test version pulled

hi
disable SI-1 and SI-2
leave SI-3 enabled because that one has driver for SIS 182

When the update in SI-3 came along, I originally had disabled these two because of the overlap (duplicate HWIDs) in INF files.

This would not work, there are other things like changes to dosnet.inf and txtsetup.sif.
To redo a slipstream takes 15 minutes
unzip,
edit the INI, (you could delete the two entries, but you better simply disable by setting the "drivercount"  to zero in those two.)
save, 7zip the INI and D folder
use it to slipstream over the one you did before. (2 to 3 minutes)
burn CDRW, 6 minutes
test (it is unattended, have a chat with girl at the coffee corner)

http://forum.driverpacks.net/viewtopic.php?id=75

hi
The devices.txt is about 1 meg.

I am curious as h*ll. Where do I find it?

EDIT, the DriverPacks project can benefit if we get a truly reliable database of what is in currently in DriverPacks, and what we have in the collections of drivers we all seem to build.

In the last few months at DriverPacks, I have been trying to get duplicates out where they harm most.
Each and every update can undo hours of work when a dupe is missed.

and... a reliable devices txt could be used for that post vanilla fini stuff, if conflicting drivers are already screened.

VidO,

if you remove these files, do you not see errors in the logs?
The OEM files are still there for reference.
The debug files, well, I don't mind, since these are not referenced in an INF and not likely used by a DLL.
(they don't appear in copyfiles lists..)

the 9x files, I left those in, because they are still referenced to in those INFs.
(now, if people tell me that removal does not break the driver load, they can go, but I am not going to edit them INFs)

Hi

I got really curious about this one and downloaded a whole lot of drivers.

'7.07.2','6 july 07',
'changed foldername P-2-A to P-2-K'.
'removed \SI\1 SiS 180 oldest version.'.
'disabled \SI\2 Sis 180 and stored driver in Selfextracting file',

    'Promise 378/376 issue'.
'compared with new downloads, [P-2] and [P-2-K] was NOT for 378/376.'.
'downloaded new drivers for 378/376'.
'downloaded new drivers for TX4000/S150 TX2plus/S150 TX4'.
'downloaded new drivers for FastTrak S150 SX4/SX4000 Series'
'INI for \P\2 and \P\2\K and \P\2\k3 (08/06/2003, 1.00.0.37)'.

'Silicon Image 3112/3512 BIOS issue, S\4 contains SFXzipped driver for older BIOS'.

    'SiS 180-181 issue: another bad case on HWID overlap'.
'downloaded again, compared SYS again. Concluded that oldest [Si-1] is obsolete'.
'[Si-2] has two HWID also seen in [Si-3] which has four HWID and uses different SYS.'.
((note;  INI/INF: NO overlap (964)-180 [Si-2] and SiS(965)-180/182 [Si-3] DOES NOT WORK'. ))
'made SFXzip files with driverfiles and INI sections, and disabled [SI-2]',

NEW
'\P\2\k3 Promise FastTrak TX4000/S150 TX2plus/S150 TX4 for Win2003 , 08/06/2003, 1.00.0.37'.
'\P\4\K Promise FastTrak S150 SX4/SX4000 Series for W2K, 05/20/2004, 2.00.00.25'.
'\P\4\K3 Promise FastTrak S150 SX4/SX4000 Series for W2K3, 05/20/2004, 2.00.00.25'.
'\P\B Promise FastTrak 376/378 for XP, 06/16/2003,1.00.1.30'.
'\P\B\k Promise FastTrak 376/378 for W2K, 06/16/2003,1.00.1.30'.
'\P\B\k3 Promise FastTrak 376/378 for W2K3, 06/16/2003,1.00.1.30',
'Silicon Image 3112/3512 S\4 contains SFXzipped driver for older BIOS'.

to be done
S\5 oldbios sfx
iastor for lattitude830

Coming up as a TEST version.
masstorage 7072 SFXTEST1

I need to discuss this SFX stuff.. but it can be tested.

Hi
this promise 376 and 378 is a very tough nut, and I think it won't get cracked easily.

They use same generic HWID, and this generic HWID is found in all downloads.
Even TX4000 driver has this 378/376 HWID in it.

1; I read here that a newer driver does not work on an older machine.

2; The drivers have different content in the SYS files for 2000, 2003, and XP
(and the differences are in functions like cache settings.)
3; The HWIDS are same in those with a single HWID for 378, yet different versions do not work?
4; ditto for 376,
5; the HWID for 378 and 376 are same..
------------------

6; Those in [P-2] and [P-2-A] use a same INF for all OSes, and at bottom it says XP where the driver is intended for 2000
(That is not a good thing either, I guess. It gets confusing. )

NOT DONE; Removal of the HWID lines that support 378 and 376 in both INF
DONE; Make [P-2] load for XP, make [P-2-A] load for 2000.
DONE; change OS description in the INF
DONE; add the specific HWID to the INF.

notes
If this still won't work, this proves that newest driver does not support older.
And then you will have to unpack.
Then replace with your driver. XP to [P\2], and 2k to subfolder [P\2\A]
edit out the HWIDS your driver does not support in the INI. [P-2] [P-2-A]
7zip the INI and D folder, and use it for a test.

did the update 7.07 work?