Search options (Page 36 of 99)

we still have to find out wether frequenzy ticked ON and TXTmode and mass storage when he integrated.

LOL.
cdob had suggested to remove V4 alltogether. That were many blanks.
The Point is this this. V\4 in Older pack 7091 used single HWID for TXTmode even while the INF supported more than that.
When the new driver was introduced, the full list got back in.
I could just as well only remove PCI\VEN_1106&DEV_0591

25 INF have &CC_010

Hi,
Windows XP does not really support AHCI out of the box.
http://en.wikipedia.org/wiki/Advanced_H … _Interface

NVidia is one of the most difficult driver suppliers because they use same names and re-use HWIDs across different chipsets.
Speed tests I read show no real improvement compared to SATA with sigle drives (Far as I know, the chip is often set to RAID-mode for a single drive.)
With a single drive, why do you need hot-plug capability?

JSe?

Are you really sure you can delete IB4?
Dou you have the machines to run tests on with the IB4 and IB5 drivers gone from the pack?
When I included the second AACSAS some time ago, I had to make sure that the systemfiles were different, and that I do not use duplicate HWIDs in TXTmode. (Which means I cannot have any duplicate HWID in masstorage.INI if the duplicates are for SAME operating system...)

Yesterday I looked at the HWIDs of IB4 and ADB because you claim IB4 can be left out.
ADB is newer and has newer systemfile versions, but it does NOT list the HWIDs I find in IB4.

I want to know if somebody here CAN test in IBM machines that use the driver in IB4?
Had the systemfiles been SAME, I could add the INF, or merge INFs.
(The CAT would not sign all the HWIDs though.)
However, they are not same, and I would like to find out if a merged INF will work when we use the newer version to support the 'older' HWIDs.
The current situation makes me think that IBM's controller has OEM modifications, for which they have to use their "own" subsys.
If I knock together a testpack, it will only be for volunteers that have the AACSAS hardware.

Hi OverFlow,
if you find the time, you could try that.

@ all readers.
Maybe you want to test TXTMODE detection only.
For a TXTmode only detection TEST, you can omit winnt.sif before slipstream, or use a NON-FULL unnatended that will NOT fully automatically repartition/format so that you can escape out of setup once you saw that it would allow you to format.

Hi,
in this case, it is not used for PnP.
It is used for TXTmode only.
There are a few drivers which do use those tags in PnP driver.

At the moment, I am at a loss.
I need to find out if we can just have the RAID version in TXTmode, and not use an INI section for NON-raid while we leave the IDE-Base mode in the pack for PnP purposes.
The subsys in silicon drivers seldom had duplicated subsys in the raid/non-raid drivers, and having to switch around sections in the INI is not fun.
(One could also wonder if that duplicate I seem to remember was on purpose?)

icp_windows-x86_xp_2000_b15317_cert
This driver has references to non-existing files? ( to wit, naacsas.sys, and naacsas.dll )

Thanks for the report.

new testfile

link pulled
_nightlies/DP_MassStorage_wnt5_x86-32_8024.7z

\L1 added INTEL (lsi) megaIDE
updated \M marvel (with driver from Intel)

mode tags in S5

moved [V] to original position in INI (V3 was and is still disabled for TXTmode.)

new in 8024
a few File name conversion fixes for windows 2000/server 2003
IDE Base mode 'tags' in S4 removed

Hi,
I will look if this one can help us eliminate some of its variant buddies.

DP_MassStorage_wnt5_x86-32_8024.7z is ready

fixed; windows 2000 had a case of case sensitivity for LSI_SAS.case
fixed, windows 2000 had a case of case sensitivity for FASTTX2k.sys
fixed; megaINTEL,   aargh, 9.3 That was stupid of me.
fixed; windows 2003 had a case of case sensitivity for cpqcismm.sys
fixed; no more CC_0101 in S4 (I listened)