[Problem] Integration of Intel's AHCI driver in W2k CD fails

Operating Systems Windows XP/2000/Server 2003
1

Hello,

i want to build a Windows 2000 install-cd with integrated updates and AHCI-drivers. My testing-system is a real C2D-board with ICH9, no VM.
Setup always ended with error-message “The file xxxxx.sys is corrupted” (xxxx depends on driver(s) integrated, with intel-drivers it is “iastor.sys”).


Update: I opened the completed image, it seems the iastor.sys is missing in DRIVER.CAB (find in folder i386), is that right?

Thanks!

2

This error message usually indicates, that the user (or someone else) has integrated a driver with a wrong architecture (32bit/64bit).
A 32bit OS needs 32bit drivers, whereas a 64bit OS only will accept 64bit drivers.
Since a 64bit variant of Windows 2000 doesn’t exist, you should check the architecture of all integrated drivers.

What does this mean? Which specific driver(s) did you integrate?

3

Yes, i read a few times about that problem x32/x64, but i’m absolute sure i downloaded the right driverpackage. These are the links:
From Intel “STOR_all32_f6flpy_9.5.0.1037_PV”: https://downloadmirror.intel.com/18668/e…5.0.1037_PV.zip
And your package “Universal 32bit Intel RST AHCI+RAID driver v11.2.0.1006 mod+signed by Fernando”: https://1drv.ms/u/s!AjMjdZ6bIhRQg_sVgXGGNDO-ypUF3w

I also tried to integrate other AHCI drivers from AMD, nForce, VIA,…only for testing, but i got the same message: “amd_sata.sys/nvgts.sys/viamraid.sys (for example) is corrupted”…
So i guess something is wrong with .sys-files or integration with nLite isn’t correct. I did a similar task few years ago with Windows XP and had no problems with driver integration.

4

That would be more surprising for me than the assumption, that your used source CD contains Windows XP x64 instead of Windows 2000.
To save time you should look into the content of your source CD.

5

It is a Windows 2000 Professional - i used it two times for installation (IDE-Mode) and i can differ between XP and 2k Setup is also showing the well-known bluescreen with “Windows 2000 Setup”.

I used an image from this download: https://winworldpc.com/download/3f4dc3ab…c3-a4e284a2c3a5

Ok, i will try another image from this site…perhaps this one did’t like the drivers.

6

Okay, i tried 3 different images and got always the same failure with corrupted iastor.sys.

Can please someone do the same process and confirm that it works/not works? I have absolutely no idea whats going wrong. Either the driver-files are not W2k-compatible or nLite is processing wrong.

7

Next try:

  • I used XP Iso Builder instead of nLite → same error.
  • Today i integrated the same drivers in an untouched Windows XP Professional image with nLite → that worked, no iastor.sys-error

8

This indicates, that none of the previously loaded/integrated Intel AHCI drivers are usable with Windows 2000.
Tip: Try a much older Intel AHCI driver, e.g. the attached one.

32bit Intel MSM AHCI & RAID driver v7.8.0.1012 WHQL.rar (175 KB)

9

Thanks, but same error again :frowning:

10

Hello eveyone, i’m new to this forum. I’m trying to install Windows 2000 Professional, on a HP laptop. I’ve installed XP just fine with “Fernando’s mod+signed drivers” but with 2K it gives me the “iastor” file corrupted.
Hope someone can help me!
Regards :slight_smile:

P.S. Sorry for my bad english :))))

Immagine 2023-09-04 224504
Immagine 2023-09-04 224504580×625 60.4 KB

11

@Cristi097 Welcome to the Win-Raid Forum!

This message indicates, that you have tried to integrate or to load a 64bit driver into a 32bit OS.
Good luck!
Dieter (alias Fernando)

12

I have the same problem with Dell Ivy Bridge machine, im quite sure that i used right 32bit drivers, i have tried multiple version of them.
There is too many thread around which same problem, from people which know how to integrate drivers and with different drivers packages, even on MSFN where usually people skilled enough to use right drivers and integrate them correctly.

I have tried also UniAta - Universal ATA driver for Windows NT3.51/NT4/2000/XP, last version which has Intel AHCI drivers too and BlackWingCat AHCI drivers - https://win2k.org/blog/2009/04/17/813816/ - use Google translate, i have also tried to load these drivers from the floppy and F6. Im not 100% that made floppy of these right, because floppy could need different file structure tha NLite, but problem is same as with other AHCI drivers so i probably did it right.

Floppy end as with file corrupt message, it seems that Windows 2000 + Windows NT reporting same error for files which are fine for Windows XP.

When i integrate drivers with Nlite, there is line 53 inf error, again same for multiple drivers, in not sure which inf file is even meant, i checked both inf files in IntelAHCI and these is nothing special.

It also seems that there is specific error - 000007 inaccessible boot device with Data center version of Windows 2000, when for other editions of like Professional, Server, or Advanced server its working.
See Help on installation for a recent PC. - Windows 2000/2003/NT4 - MSFN

Other last problem is if its possible install boot Windows 2000 in ATA mode, boot it and somehow install AHCI drivers and reboot switch bios to AHCI mode and boot fine. Im not sure if Hardware ID of controller in ATA mode has the same Hardware ID and its possible to force AHCI driver over ATA controller in PATA mode, yes solution could be temporary add other ATA controller card into machine, but its not always possible.

The last unknow thing for me its if certificate is really needed for Windows 2000, because you cant install it before installation im unsure if inject driver through Nlite will add it into system.

Other 1 more problem to make thing even more complicated and the is ACPI on the modern machines, i used Black Wing cat ACPI driver for Sandy bridge + machine, im quite sure that i have integrated it correctly, if not press F5/F7 and select Standart pc option to bypass ACPI setup always hangs right before target partition is selected.

Here is tutorial which i used for integration new ACPI driver and AHCI drivers:
[GUIDE] How to install Windows 2000 on Intel Sandy Bridge and later with ACPI - Windows 2000/2003/NT4 - MSFN in theory it could be Nlite bug too…

I have tried also inject AHCI drivers through Paragon HDD Managers 2011 to 2017 as its Dissimilar P2P (Physical to Physical machine) HW Adjust but which is usually working for more modern OSes, but *0007 boot Bluescreen persist

There 1 more tool, which could help to make machine bootable again in ATA mode after AHCI experiments - its FixHDC - https://win2k.org/blog/2009/04/17/813816/
Its integrated on Hirens boot cd add - live XP iso under registry tools.

Maybe this could help: