Search options (Page 27 of 99)

Hi
welcome to DriverPacks.

a method 1 should not be asking for setuporg.exe.

Wich DPsBase version do you currently use?

thanks.
for Sil 3112R  RAID we currently have 02/01/2007, 1.0.60.0 in the testpack.

for Silicon 3112 IDE compatibility mode we have 04/13/2007, 1.3.68.2

Conclusion,
If you have a series of these machines, you have to put the raid below the IDE, or remove the IDE section [s4].
I will get to WU and update the [S5] driver.

Hi
you post the HWID for sataRAID driver, and the link to the driver is a NON-raid driver.
(; This INF file installs the Silicon Image Serial ATA non-Raid driver for the)

The driver we have for the RAID is located in D\M\S5.
In the testpack I have uploaded this month there are no Bios variants mentioned for this Raid-driver.

--------
(Link killed) DP_MassStorage_wnt5_x86-32_803RC3.7z
This testpack has the following changes when we compare to released mass storage driver pack.

[N-TM] loads after other Nvidia
[N-TM] contains two extra abit HWIDs
INI Fixes by Overflow for server and windows 2000.
INI fix for Symmpi for XP.
INI fix for [N-6] by OverFlow

S8A,  Silicon removed
V3, Via updated

Silicon sections now in THREE blocks so that a user can easily move these around or remove these from INI.
Silicon image load order changed
first softraid, then raid, then base-ide

It does not yet fix AHCI. (an intel driver, we will probably roll back to an older version with same HWIDs.)
-------------
Because there are quite a few changes in INIyou should NOT re-stream an old source.
Use a fresh copy of a source you have not yet used DriverPacks on.
Make another copy of that to fall back to..

Now, if this testpack does not work, I will ask you do the following.
Unpack this testfile.

Open the mass storage.INI, and move section [s5] under all other.
Close, and save changes.
Then recompress. (select INI and D, rightclick to run 7zip.)
7z, ultra, lzma, 256wordLength, compact.
Use the changed file to stream a new copy.

Test.
And if THAT works, I will want to know.

I would also like to know what the DEFAULT setting in the chip's BIOS is.
I've always assumed RAID is the most used default, but in LAPTOPS we see that the chip was set to IDE-mode.

Users can move the sections (and delete them..)
We know that the driver we put last in INI loads last, and for some reason windows setup sometimes decides that this one is the best match..
(despite specific HWIDS..)
So, we have to make people aware that the mass storage DriverPacks IN can be edited to change load order.

We do have FAQ about trimming  mass storage..
------

If you are in a real hurry, you CAN unpack the mass storage DriverPacks, and tell windows to use the driver in D\M\S5.

I would like it VERY much that you test the pack I link to, and if you have to change load order to make it work so be it, but you would learn something, and we will learn something as well.
Please help us help you.
Your first post was thought out and helpful.

OH, Helmi.
Jeff wants me to try something in M2.

I was asked to write something into M2 so it uses the INFs for chipset early on.

Hi Erik,
Long time ago I promised I would put the modem pack though the filtering process, because modem drivers can mess up sound driver install.
I have not forgotten that promise.

HUH... you say you did not select soundpacks?

KTD leaves the decompressed drivers in a windows\drivers subfolder and tells windows where those drivers are located.

I don't mind learning how to integrate some stuff without using Nlite or RVM.
Shoot. I am all ears.

hi
this issue can exist with vanilla dutch, and sp1 dutch sources.
Slipstreamed to sp2, they still have svcpack.in_ which does not convert well.

SP2 dutch, and all english versions, have no issue. The svcpack.in_ in SP2 Dutch lists a few hotfixes, and the file converts well during DriverPacks streaming. (SP2 English lists a few hotfixes too... FAIK, prior to Sp2, there were no real hotfix entries in svcpack.)

Just suppose you are working with a source that was once Dutch vanilla, you can pput a good one from an English in the source, or you unpack it, convert it yourself (This can be done with notepad, actually. When you save as, look at "codering" ), then makecab it, and save a copy for later use in a goodansi folder, for instance.

For one reason or another, the uni2ansi tool in DriverPacks does not always process the file
(unproven theory.. but FAIK, it happens when a WINNT.SIF is present in the source.)

I have also seen that when the file had already been processed by me, or by Ryan's integrator, then there is no issue no more..
just my 2 cents..

Well, RVM once had an advanced option to convert to ansi, and I did that.
I then saw betas which set convert to ansi as default.
It could be that RVM in its current release does not do that by default, and I believe the advanced selection screen for this is gone.

I'll download the latest version.
since you use RVM, and it does not work.. You may have to use notepad to fix the svcpack.in_ file.

Can you link to drivers for those machines?

Dell 745?
and the other is?

note to Jeff; sound B; sigmatel in Z2 had two "super generic" and I disabled them.
Then, for each specific line it also had a generic. I disabled generic 7690.

S_B\S\SM\H\3\smwdmCH4.inf pci\ven_8086&dev_24C5&subsys_0890103C

There is an excell worksheet on FTP.
By the way, the latest testpack should prevent S_A\S\R1\alxau.inf from taking this HWID

Hi
We are working on a much better DpsBase which will clean up older DriverPacks slipstreams a LOT better.

For the time being, when DriverPacks releases a new mass storage pack, you have NO idea what the internal [INI] changes do when you run DpsBase with that new pack over a USED source. You read the tutorial and saw that? Good. When that newer base prevents such mistakes; the pandora tutorial will be rewritten.

For the time being: You can update a previously streamed source when you do not use a new mass storage pack version (because that is most likely to have killer changes on a few drivers in its INI).