Sata drivers for windows 2000

• SATA Adapter Driver for Initio INIC162x chipset (Win98-XP)
• Raid Utility —  For Initio INIC162x chipset
• Linux — SATA Adapter Driver for Initio INIC162x chipset

ITE

Please for the love of god someone better know this.

I have a Sony Vaio VGN-NR498E (look at specs)

I need drivers for the HDD I tried using the driverpacks and correctly put them on with the driverpack BASE.

I think THINK
https://downloadcenter.intel.com/Search … +Driver%22
Applies to my laptop but I have no idea and need someone to find out :S

I seriously am pulling hair out (not really it would hurt) I am mentally though!

And if your in the mood wireless drivers.

But focus on the HDD

Seriously someone please friggin help me.

we need the HWID’s in order to help properly.

your driver is probably in the pack but disabled. the HWID would tell us.

HWID tool linked in my signature

Please post your DPs_BASE.log.
At what point in XP setup does it fail?

First does that tool need to be used on the computer I am installing Windows 2000 on? Because there isn’t an OS on it.

Second I am not using XP hence the title, and it fails when it doesn’t see my HDD..

https://www.dropbox.com/s/zabd6datee3b88m/DPs_BASE.log

Theres the log.

Oops. Sorry.
Yes, the HWID tool needs to run on the affected machine.

Well, we can try to extrapolate the HWID for the drive controller from the Sony XP drivers here:
http://esupport.sony.com/US/p/model-hom … ownloadTab

From the txtsetup.oem file

[HardwareIds.scsi.iaStor_ICH8M]
id = "PCI\VEN_8086&DEV_282A&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH8M]
id = "PCI\VEN_8086&DEV_2829&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH8R]
id = "PCI\VEN_8086&DEV_2822&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH8R]
id = "PCI\VEN_8086&DEV_2821&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ESB2]
id = "PCI\VEN_8086&DEV_2682&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ESB2]
id = "PCI\VEN_8086&DEV_2681&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH7DH]
id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor"

[HardwareIds.scsi.iaStor_ICH7MDH]
id = "PCI\VEN_8086&DEV_27C6&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7R]
id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH7M]
id = "PCI\VEN_8086&DEV_27C5&CC_0106","iaStor"

[HardwareIds.scsi.iaStor_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6R]
id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor"

[HardwareIds.scsi.iaAHCI_ICH6M]
id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor"

A good place to start is to edit the dpms .ini file and change these two sections:

[I2]
; 7.0.0.1020
ms_count=1
ms_1_deviceName="Intel ESB/ESB2/ICH6/ICH7 SATA AHCI/RAID 7.0"
ms_1_tag="iastor2"
ms_1_sysFile="iastor2.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24D1&CC_0106,PCI\VEN_8086&DEV_2651&CC_0106,PCI\VEN_8086&DEV_2652&CC_0104,PCI\VEN_8086&DEV_2652&CC_0106,PCI\VEN_8086&DEV_2653&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

[I3]
; 7.8.0.1012
ms_count=1
ms_1_deviceName="Intel ICH8/ICH9/EP 80579 SATA AHCI/RAID Matrix 7.8"
ms_1_tag="iastor3"
ms_1_sysFile="iastor3.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2681&CC_0106,PCI\VEN_8086&DEV_2682&CC_0104,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_5029&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

…to read…

[I2]
; 7.0.0.1020
ms_count=1
ms_1_deviceName="Intel ESB/ESB2/ICH6/ICH7 SATA AHCI/RAID 7.0"
ms_1_tag="iastor2"
ms_1_sysFile="iastor2.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24D1&CC_0106,PCI\VEN_8086&DEV_2651&CC_0106,PCI\VEN_8086&DEV_2652&CC_0104,PCI\VEN_8086&DEV_2652&CC_0106,PCI\VEN_8086&DEV_2653&CC_0106"
ms_1_isBusExtender=false
;ms_1_exc_disableIfOS="w2k"

[I3]
; 7.8.0.1012
ms_count=1
ms_1_deviceName="Intel ICH8/ICH9/EP 80579 SATA AHCI/RAID Matrix 7.8"
ms_1_tag="iastor3"
ms_1_sysFile="iastor3.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2681&CC_0106,PCI\VEN_8086&DEV_2682&CC_0104,PCI\VEN_8086&DEV_27C3&CC_0104,PCI\VEN_8086&DEV_2829&CC_0106,PCI\VEN_8086&DEV_5029&CC_0106"
ms_1_isBusExtender=false
;ms_1_exc_disableIfOS="w2k"

Delete the QSC folder in DriverPacks BASE, repackage the dpms archive and integrate into your source again (you can skip all the other DriverPacks for now).

Repackage to..? And how?

Could you detail this process please. I would grateful.

To further irritate you. I can’t find any of that in the txtsetup.oem.

Might be faster if you just uploaded the edited driver. Though if you prefer I am open to learning this.

May i join in?

Here is a thought.  I see you have integrated two DP_Chipset packs.  You need only one.  It is best to use Chipset & MassStorage packs made at the same time.

For starters, if we want Win2000 to work with your notebook, perhaps we should only integrate Chipset and MassStorage for now.  In that effort, i would usually advise using the latest nightlies, here and here.  Later, you will find other updated nightlies in their respective forum topics.

Burn a DVD plus or minus RW.  Disc install will have the greatest odds of success.  RW’s save eWaste.  Use media that your notebook disc drive can read though.  Hold that thought for now until reading the whole post though.

Start with an unmodified Win2000 SP4 disc.  nLite may make your source unusable for integration.  Avoid it’s use for now.  RVMi is preferred.  However; updates are not important now.  Simply getting this working (if possible) is the priority.

I will examine the AHCI on the support page linked by mr_smartepants and attempt to resolve what changes may be necessary.

edit:  unfortunately, from the «readme.txt» for the Intel AHCI controller driver package (INDOTH-12766700-XP.EXE) from Sony, i quote:

Curious, that driver is WHQL’ed including NT5.0 aka Windows 2000.
Only PCI\VEN_8086&DEV_2653&CC_0106 (ICH6M — 82801FBM (Mobile)) is enabled to use that particular driver.

It is actually more likely that the Official DriverPack releases you had tried earlier were more likely to contain references to the driver Sony had officially released for XP.

It may be that the driver mentioned here is not compatible with Windows 2000.  Therefore, you may need an older driver from intel to accomplish your goal.  Version 5.5.0.1035 is a likely candidate.  Does your notebook have a working floppy drive?  If so, use the ‘F6’ method to test.  If that succeeds in «seeing» your HDD, it may be necessary for me to add some stuff to MassStorage.ini for Win2k compatibility.

I would like to assist in ensuring the latest Nightlies are compatible with Win2k.

Please don’t hurt me, admin.  I usually use Hiren’s CD to capture HWID’s under similar circumstances.

Last edited by TechDud (2013-08-10 18:19:57)

UBCD4Win / BartPE is a legitimate way of doing the same thing…

i hope that did not hurt too bad.

detailed instructions are in the FAQ section of our site .

Alright, I already burned a clean copy of windows 2000 sp4. I assumed sp4 for some reason had the sata drivers.

I was wrong.

Regardless I have a working ISO.

But no my notebook is too modern to have a floppy drive.
I don’t even own a floppy disk anymore.

OK, i have modified MassStorage to specify Win2k drivers utilizing folders [ I], [I2], and [IC]

Testing on my Inspiron 1525 with the HWID «PCI\VEN_8086&DEV_2829&CC_0106».
Chose the driver in [I2] (Matrix 7.0) for the majority of HWID’s, despite the warning above from Intel.
  This took some time to weed out the «corrupted file» errors and «insufficient memory» errors.
     (I wonder if having 2GB has anything to do with the memory errors.)
   Long story short, it failed ultimately with «dmboot.sys», a Win2k system file, being deemed «corrupted».

Attempting to find the latest «Matrix 6» driver to base Win2k support upon.

Would this possibly be of interest or help?

http://alter.org.ua/en/soft/win/uni_ata/

That project may ultimately allow NT5 support to be extended to HWID’s not covered by the official drivers.
  Certainly, it cannot be done without approval of both Admin here & Mr. Telyatnikov at minimum.
However; the aim at this present time is simply to properly support official drivers.

It might actually be Matrix 5.7 which is the last official version to generally support Win2k, not simply «Advanced Server».
   https://downloadcenter.intel.com/Detail … p;lang=eng

…efforting

Last edited by TechDud (2013-08-12 07:27:04)

2000 is dead, XP is at deaths doorstep. I don’t think it is important to go to extraordinary measures for support.

We will certainly try to help within the existing structure of the DriverPacks, as always.

thanks for testing and reporting it makes our project better for everyone.

Nice job, again, TechDud

2000 is not dead.

http://www.windows2000.tk/

And Windows XP has a massive popularity I am sure the above could or happen to it.

Of course support will end and the general masses will finally stop clinging to it.

Its alright if the driver can’t be found. Its something I can live without. But disregarding thaaat it shows we are missing sata drivers for 2000 or something.

The one thing that makes NT5 relevant still is Latency.
  Try comparing latency for any MS OS (using tool in sig. — except on the same hardware.
     The difference is often not just «statistically significant», yet vast.
8 may help bridge the vast gap, yet is not yet popular and is comparatively expensive.

This may be part of the reason that XP market share actually increased in July of this year.

As a matter effecting International Security, i implore Microsoft to reconsider the final extended support date for Windows XP.  1/12/2016 is the date that XP Embedded’s extended support is to be nullified.  That would be a logical extension.
   http://support.microsoft.com/lifecycle/ … Windows+XP
Vista is supported until 4/11/2017.

One other factor may be dead or dying Win7+ hardware for which an OEM license is non-transferable (AFAIK).
   This may leave some with the choice between buying another license (expensive plan), «pirating» their own copy of Windows (illegal plan), or rolling back to an OS for which they are legitimately licensed (simple plan).  A choice between Vista and XP may yield predictable results.

Note that it is ill-advised to use Windows 2000 in any networked environment.
  Soon it will be ill-advised to use any NT5 OS in any networked environment.
     «Commander William Adama» of the «Battlestar Galactica» had a simple way of preventing «Cylon» (not to be confused with Skylon) infiltration of any of their computer controlled systems — Don’t Network Them!  That leaves site-security as a prime concern.

OK, i have Matrix 5.7 in the archive, yet testing on unsupported hardware has revealed «insufficient memory for fastfat.sys».  I will attempt to find some supported hardware to test.

edit:  one other thing, should this discussion not be moved to the NT5 MassStorage topic heading?

Last edited by TechDud (2013-08-12 10:51:54)

«the file ntfs.sys is corrupted» errors are plaguing me now, even on «atapi».
Attempting to comment-out drivers in txtsetup.sif.

Windows 2000 IS dead.
http://support.microsoft.com/gp/lifean35

Therefore, DriverPacks support for 2000 has ended also.

Official support for XP ends 8 Apr 2014.
http://www.microsoft.com/en-us/windows/ … pport.aspx

With the «ntfs.sys is corrupted» errors behind me, i have run into more than one major snag.

It would seem that DPs_BASE_1109012 (the version i’m testing with here — with M2.7z mod) does not support Win2000.
The public version DPs_BASE_1006 might support Win2k.

It is working on officially supported AHCI hardware otherwise, though.  Setup completes.
Unfortunately, during initial boot, post-GUI Setup, it bluescreens with Stop $7B — Inaccessible_Boot_Device.

edit:  DPs_BASE_1006 does support Win2k, no bluescreen this time, Desktop instead.

Only integrated Chipset, Lan, MassStorage, & Misc to avoid severely-limited DrvPath.

Anyway, Admin says that i am done.  Pity, i’ve spent a good day of my time on this.

edit2:  I am done.  It works.  XP Setup still works too.  Now what do i do?

Last edited by TechDud (2013-08-17 10:10:04)

Well, what did you do to make it work?  If your changes don’t break anything for XP or other OS, then leave the changes in there.
If it’s fixed, then it’s fixed.  But I wouldn’t waste any more time on 2000 support.

Its not a waste. The link I gave about the unofficial service pack 5.2 was to show there is still a community of people using windows 2000.

Cutting off support for those people seems unneeded and plain stupid to me.

Now if techdud was needed for someplace else or he had to delay other things to do this then It probably would be a waste of time, otherwise if it was his free time, i would say time well spent and much knowledge gained.