• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mark49

  • Birthday

Contact Methods

  • Website URL
  1. i think shoud be PCI\VEN_1095&DEV_3114&SUBSYS_31141095 = "SI3114" PCI\VEN_1095&DEV_3114&SUBSYS_288610F1 = "SI3114"
  2. VIA_RAID_V510A download: and new ids added: id = "PCI\VEN_1106&DEV_3349","viamraid" id = "PCI\VEN_1106&DEV_0591","viamraid"
  3. Realtek RTL8185 PCI/Cardbus 802.11g 54M Wireless LAN Network DriverVer = 07/20/2005,5.103.0720.2005
  4. DriverVer=03/31/2005,
  5. @BTS, maybe i found the solution Through analyse \windows\setupapi.log files, i found the RANK relation between Compatible ID and HWID: normally 's rand is 0x200? , like when driver has NO whql sign ,then rand will be added with 0x8000 or more. so: While the part of PATA driver from NF v6.66/7.13 has NO WHQL sign , when on NF2/3 mobo GUI installation, system will chose MS's pciide.sys driver to PATA (no raid) device, because PCI\CC_0101 from "WINDOWS\inf\mshdc.inf" got high priority then NV's PATA driver! and to avoid BSOD after first rebooting on some NF3 mobo (esp. MSI K8N NEOxxx), i Add this to txtsetup.sif . then test passed ;; MSI K8N Neo2 Platinum nF3 250Gb PATA no Raid PCI\VEN_10DE&DEV_00E5&CC_0101 = "pciide" we can even add PCI\VEN_10DE&DEV_00??&CC_0101 for PATA device on all NF2 mobo , but by so far it seems v6.66/7.13 works good on NF2 mobo then older drivers. I have a idea : the part of PATA driver use the part of v6.53, cause of it has WHQL, the part of SATA/SATA RAID drivers use the part of v6.66 and 7.13, del 6.66 and 7.13 's PATA folders . but i dont konw if 6.53's pata driver is good for NF2 , and when PATA RAID on NF2/3 mobo which one driver will be installed . nvatabus.sys of v6.53 + nvraid.sys of v6.66/7.13 or the same version ?? only can guess when SATA RAID on NF4,will be 6.66 or 7.13
  6. which one driver?
  7. @BTS , i add PCI\VEN_10DE&DEV_00E5&SUBSYS_02501462&REV_A2 = "nvbus5" into txtsetup.sif. and copy nvatabus.sys from v5.10 to \i386 as the name of nvbus5.sys . but it does NOT work , therefor i find another way to solve this problem (BSOD after first reboot) on the mobo
  8. si3124 04/26/2005, WHQL no HWIDS change ----------------------------------------------------------------------------------------- si3124r5 03/31/2005, WHQL add hwid to txtsetup.sif (also .sys entry) PCI\VEN_1095&DEV_3124&SUBSYS_71241095 = "si3124r5" ----------------------------------------------------------------------------------------- @BTS ,a Q: in si3xx4 txtsetup.oem Is it necessary copy SiWinAcc.sys to \i386 and add SiWinAcc.sys = 1,,,,,,4_,4,1,,,1,4 to txtsetup.sif ? or in other words: is SiWinAcc.sys necessary in TXTmode and half part of GUImode?
  9. si3114 update: si3114 05/05/2005, WHQL si3114r 11/02/2004, si3114r5 03/31/2005, WHQL txtsetup.sif PCI\VEN_1095&DEV_3114&SUBSYS_31141095 = "si3114" PCI\VEN_1095&DEV_3114&SUBSYS_B0021458 = "si3114" PCI\VEN_1095&DEV_3114&SUBSYS_003915D4 = "si3114" PCI\VEN_1095&DEV_3114&SUBSYS_31148086 = "si3114" PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_288510F1 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_90181695 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_F642270F = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_100415BD = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_12501462 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_13101462 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_15601462 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_16101462 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_B0031458 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1B711019 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_61141071 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_003515D4 = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1025147B = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1001147B = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_130A147B = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_1C0A147B = "si3114r" ;;PCI\VEN_1095&DEV_3114&SUBSYS_81361043 = "si3114r" //use 3114r5's driver PCI\VEN_1095&DEV_3114&SUBSYS_2A1E103C = "si3114r" PCI\VEN_1095&DEV_3114&SUBSYS_71141095 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_71148086 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_81361043 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_81671043 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_902A1695 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_310215BD = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_052FA0A0 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_104A147B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_104B147B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_B0041458 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_71001462 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_71251462 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_471015D5 = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0C25105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CC1105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CCA105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CCB105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CCC105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CCD105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CCE105B = "si3114r5" PCI\VEN_1095&DEV_3114&SUBSYS_0CCF105B = "si3114r5"
  10. HighPoint RocketRAID 222x SATA from: 05/18/2005, 1.01 update to : 07/11/2005, 1.02 link:
  11. HighPoint RocketRAID 182x SATA from 01/27/2005, update to : 08/01/2005, link:
  12. @Chertoianov, pls use this app to list your hardware's ids
  13. a A8N-SLI Deluxe NF4 SLI 939 , CK804, SATA RAID0 all OK with v7.13
  14. EPOX 8RDA3+,nForce2Ultra400(nForce2SPP)+MCP , SATA disc AU13,nForce2Ultra400(nForce2SPP)+MCP-T , no SATA/RAID At last all OK with v7.13 driver, and with older driver ,such v6.53 ,v5.1... , many problem , even BSOD after first reboot. not test v6.66