Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Russian Federation

Posts posted by iSmart

  1. Thank you very much for your very interesting and substantiated contributions. Your comment is always welcome! :thumbup

    Thank u 4 your work @ http://www.nforcershq.com/forum/1-vt70968.html, man!

    We should stay in contact, because I am still going to create/customize nForce IDE drivers for chipsets, which are not supported anymore by NVIDIA.

    Well, if not in forum, I'm in ICQ when @ work (my local time is GMT + 6), u're welcome— and other great brains of these forums too :)

    …but since this breaks the WHQL stamp, things will be more difficult with Vista and Windows 7.

    Well, hackers will produce some patches for it, I'm sure :)

  2. Does nVRAID BIOS set HardwareID *NVRAIDBUS and *NVRAID20?



    Does nVRAID BIOS v4.24 match *NVRAIDBUS ?

    Does nVRAID BIOS v4.81 match *NVRAID20 ?

    I don't know… Let's ask Sapphire! :)

    Sapphire, what can u say about RAID HWIDs with different NVRAID BIOS version @ your K8NS?

    Hardware support more modes than the official driver.

    http://www.intel.com/Assets/PDF/specupdate/316973.pdf refers a AHCI 8023.

    iaAHCI.inf dosn't match 8023.

    Very interesting PDF, but no "8023" string in it :unsure:

    Story remids to Intel iastor.

    I used PCI\VEN_8086&CC_0106 in the past. And I had to change this concept in the past.

    Do u mean, that was a bad idea? U've tried to use СС_0106 for Intel, but then stopped?

    I don't clearly understand u... Coz of my english, I guess… (and maybe yours too :D)

    Thanks for examples: this show NVidia behave similar.

    Driver nvgts.sys support more modes than *.inf files.

    As I guess, new NV masstor driver supports directly DEVs, but not modes (CCs).

    Strange facts:

    1. BIOS allows choose RAID-mode for controller, and for no one channel.

    2. BIOS takes controller in strange DEV_07F8&CC_0101 state in this case. I guess, DEV_07F4&CC_0106 or DEV_07F8&CC_0104 would be right :unsure:

    Yes, edited *.inf files are fine.

    Thanx! Have u tried it on real PC?

  3. Great forum, great people, great questions.

    1. Is it necessary or useful to list "DEV_560" (= P-ATA Controller of MCP67 boards) within the INF file of any nForce driverpack, although this device cannot use any nForce IDE driver (it needs the MS generic IDE driver PCIIDE.SYS)?

    Not necessary, not useful. I u'll try, u'll get BSOD. I tried :)

    2. Do users with a "fake RAID with no array, but controller in AHCI mode" need to integrate your RAID or your AHCI folder?

    Not necessary, but useful. As I remember (don't have MCP73 at moment), both folders are needed.

    I tried— and it was installed correctly.

    If not integrate, it will be common IDE-mode with common WinXP IDE driver (СС_0101— when WinXP setup, no problem with searching for HDD on textmode stage, no problem with install on graphics stage, and so on).

    If integrate, it will be native AHCI-mode with NVidia NVSTOR driver— and (may be) improved performance.

  4. On "old" NV chipsets (nForce2—MCP61), one DEV can have different CC's for different modes:

    DEV_0267&CC_0101— SATA

    DEV_0267&CC_0104— RAID

    On "new" NV chipsets (MCP65—…), one DEV can't have different CC's for different modes:

    DEV_0550&CC_0101— SATA

    DEV_0554&CC_0106— AHCI

    DEV_0558&CC_0104— RAID

    DEV_0560&CC_0101— PATA

    But there is, at least, one exclusion: see my prev. post (MCP73):

    DEV_07F8&CC_0104— real RAID

    DEV_07F8&CC_0101— fake RAID w/ no array(s)— but controller in AHCI mode! (yes, with CC_0101!)

  5. Thanx 4 your questions.

    I understand:

    old nforce controllers don't use AHCI.

    They are either PCI\VEN_10DE&CC_0101 or PCI\VEN_10DE&CC_0104.

    PCI\VEN_10DE&CC_0106 match all nforce AHCI controllers.

    This includes a PCI\VEN_10DE&DEV_044D&CC_0106. PCI\VEN_10DE&DEV_044D is not part of iSmart nvgts.inf.

    Currently: a new driver may match all nforce AHCI controllers.

    However this may fail in future. A old driver may fail at new hardware.

    U're extremely right. But we live nowadays, not in future.

    PCI\VEN_10DE&CC_0106 is a good idea today, but may fail in future.

    Nvidia may release conflicting drivers.

    As I wrote, my idea with СС_0106 isn't applicable for different AHCI drivers. In future, if NVidia will release AHCI-2 driver, my concept must be revised, back to DEV's again. U're right.

    But it's another future problem, not today's.

    PCI\VEN_10DE&DEV_0ABC match






    The last two examples dosn't exist.

    All new nforce controllers are connected to nvgts.sys.

    This maybe a good or bad idea.

    In normal IDE-mode, u have DEV_07??&CC_0101. U can't install NV masstor driver.

    In normal RAID-mode, u have DEV_07F8&CC_0104. U must install NV masstor driver + NV raid driver.

    In normal AHCI-mode, u have DEV_07F4&CC_0106. U must install NV masstor driver.

    But on MCP73, u can turn on RAID-mode in BIOS for controller, but for no one channel.

    In this case, u have (surprise!) DEV_07F8&CC_0101. U can (surprise!) install NV masstor driver.

    I've edited inf-file for this case.

    PCI\VEN_10DE&DEV_*&CC_* may get more stable results now and in future.

    No doubt.

    iSmart Nvrd32.inf: there are only Raid*20 HardwareIDs.

    Does this refer to old nforce controllers only?






    I guess, it's for old controllers, with no AHCI support. And my practice tell me I'm right.

    Another question:

    Does BIOS or driver set Raid HardwareID?

    I don't understand this question :(

  6. 1. Only AHCI capable nForce chipsets (from MCP65 up) are supported by these nForce IDE drivers.

    Oh yeah.

    2. The drivers contain just the english (US and UK) and russian co-installer DLL files, all others are missing.

    U're right. Not missed but cutted down— I use this pack for install drivers onto PCs in Russia ;-)

    3. Within the NVGTS.INF file there seems to be a mistake within the list of supported HardwareID's (the first lines do not contain the DEV ID).

    No mistake. PCI\VEN_10DE&CC_0106 really works— and works great.

    Just let me explain:

    In fact, we have the one and only driver (any latest, now it's for all AHCI-mode HWID's— so, no need to enumerate all of them with DEV's— just PCI\VEN_10DE&CC_0106— and it's done.

    Note: it's not applicable, if u wanna use different drivers for different AHCI-chipsets (f.e., for best performance or smth. like it)

    4. Very interesting: The modded drivers seem to support even the newest nForce chipsets (newer HardwareID's than NVIDIA's recent driver sets 15.23/15.24/20.08).

    May be, but we can't check it out— no MoBos on newer chipsets on the market ;-)

  7. Hello party people again!!!

    I've just found out very strange thing with these 3112 controllers!

    As ya know, I use Epox RDA3+ for testing. HWID string of integrated 3112r chip is


    Such SUBSYS has the only one 3112r controller, but no one 3112 (sorry my english). So, what's the f***ing problem? I can't understand, why WinXP setup choose 3112 instead of 3112r...

    Again, my guesswork, 3112r has CC_0104 and 3112 has CC_0106. But I have no mobo with 3112. We need ya help, 3112-owners! We need not only your VEN, DEV & SUBSYS codes, but also CC!!! (and maybe REV too).

    3112r on Epox RDA3+ has full code


    If my guess-work is right, we can put right CC's in txtsetup.sif, and it will help WinXP setup choose right driver.

  • Create New...