changes in this,
[N-TM] added three HWIDs to NVidia TextMode.
Strange..
I got driver for an ABIT mobo, and its oemsetup.txt file lists these HWIDs, but the driver's iNF does not list it..
(Also in that TM driver we have.)
The ABIT's driver is older, so I added the HWIDs to INI only

BUT, look at the one in V1, VIAMRAID from hyperion, in a folder for XP.
That says 07/12/2007, 5.1.6000.562

I have a VIAMRAID from Asus 03/31/2006, 5.1.2600.530
(I know I also have a 5.1.2600.540 someplace.)

Could this be messing us up?
------
The systemfiles for XP/w2k/w2k3 are identical (save for the CATs in 2k3), and vista has different systemfiles.
But all have identical INF.

strange 5.1.6000.xxx  is not valid - it should be 5.1.2600.xxx

there is no NT version 5.1.6000  it's either 2600 for xp, or 3790 for 2K3

A raid version of VIA should NOT (in theory) fight with an IDE driver, but I suspect it does.

note; removed Silicon's 3112 HWID from LSI megasas INI section.
Via sections, see above.

I think it won't solve this thing.
The driver in V4 says 5.1.6000.xxx where old drivers said 5.1.2600.xxx
Maybe XP thinks it is not suitable?

(oops, make that V1 )

i could just be tired and confused... ;P

I made one small change to a generic in the non-pruned .. I added the CC_0101
(all other lines in there had the mode tag and this one was "for all modes")

please note that the drivers themselves got HWID pruned for PnP long ago, and it looks/feels an update caused this mess.

I've looked back at the drivers before the prunejobs were done (I figured pruning was needed, VIA had issues..)
I hope that the bus driver in V4 will work for older hardware supported in V3.
I remember we tried without V3 section, with V3 nullified and with different load orders.

I redid the TXTmode HWIDs for V3 and V4 moments ago, using the non-pruned driver.

[V]
ms_count=1
ms_1_deviceName="VIA RAID"
ms_1_tag="VIAMRAID"
ms_1_sysFile="VIAMRAID.sys"
ms_1_hwids="PCI\VEN_1106&DEV_3349&CC_0104,PCI\VEN_1106&DEV_6287&CC_0106,PCI\VEN_1106&DEV_0591&CC_0104,PCI\VEN_1106&DEV_3249&CC_0104,PCI\VEN_1106&DEV_3149&CC_0104,PCI\VEN_1106&DEV_3164&CC_0104,PCI\VEN_1106&DEV_0581&CC_0104,PCI\VEN_1106&DEV_7372&CC_0104,PCI\VEN_1106&DEV_7353&CC_0104"
ms_1_isBusExtender=false

[V2]
ms_count=1
ms_1_deviceName="VIA ATA/ATAPI HOST CONTROLLER"
ms_1_tag="VIAPDSK"
ms_1_sysFile="VIAPDSK.sys"
ms_1_hwids="PCI\VEN_1106&DEV_4149"
ms_1_isBusExtender=false

[V3]
ms_count=1
ms_1_deviceName="VIA SATA/PATA IDE"
ms_1_tag="VIDEX32"
ms_1_sysFile="VIDEX32.sys"
ms_1_hwids="PCI\VEN_1106&DEV_0571&CC_0101,PCI\VEN_1106&DEV_0591&CC_0101,PCI\VEN_1106&DEV_3164&CC_0101"
ms_1_isBusExtender=false	

[V4]
ms_count=1
ms_1_deviceName="VIA HYPERION SATA IDE"
ms_1_tag="VIBUS"
ms_1_sysFile="VIBUS.SYS"
ms_1_hwids="PCI\VEN_1106&DEV_3149&CC_0101,PCI\VEN_1106&DEV_3349&CC_0101,PCI\VEN_1106&DEV_0581&CC_0101,PCI\VEN_1106&DEV_5287&CC_0101,PCI\VEN_1106&DEV_5324&CC_0101,PCI\VEN_1106&DEV_5337&CC_0101,PCI\VEN_1106&DEV_5372&CC_0101"
ms_1_isBusExtender=true

I want to look at some SiLycon issue before I upload.

The driver in the [V4] folder works for the user when the user already has Windows installed, but when installing Windows with DriverPacks integrated, textmode doesn't pick up the SATA hard drive at all.  The HWID that would be used for this hardware is "PCI\VEN_1106&DEV_0591&CC_0101".  When I went through the INI file for DP_MassStorage_wnt5_x86-32_8021.7z and looked at the [V4] entry "PCI\VEN_1106&DEV_0591&CC_0101" is not listed there at all.

"PCI\VEN_1106&DEV_0591&CC_0104" is in the [V] entry for DP_MassStorage_wnt5_x86-32_8021.7z INI, but the user isn't using RAID at all.

Also, from reading this whole topic and your posts to me, should I just have the user do the skip method or set ms_count=0 for the relevant section(s) in the INI?  If so, I will make sure these changes happen.

PS i am finaly done editing that post

since loading the driver is the problem we DON'T want it to be there

PS i was editing my post when you posted so reread my last
I would be honoured to have your help...

One thing I was wondering, would adding "PCI\VEN_1106&DEV_0591&CC_0101" to the [V4] entry also work in textmode picking up this driver, since this is the correct driver for the hardware?  The current [V4] entry doesn't have it.

Current HWIDs of [V4] entry:

"PCI\VEN_1106&DEV_5372&CC_0101,PCI\VEN_1106&DEV_5337&CC_0101,PCI\VEN_1106&DEV_5287&CC_0101,PCI\VEN_1106&DEV_5324&CC_0101"