I used a modified (NIKKA with Sata-v2) and clean version of XP, none of them works.
Bluescreen (0x000000a5) appears while loading the driver installer, before shows partitions.
Plugged into the motherboard there is only one HDD, DVD, and nothing more.
All options do I have for Legacy and IDE.

Pozdrawiam/Regards
xpeu89

Zitat von Fernando im Beitrag #212

---

Zitat von xpeu89 im Beitrag #211

---

I used a modified (NIKKA with Sata-v2) and clean version of XP, none of them works.

---

The best source is a clean XP SP3 image.
Another idea: Hit F5, when you are prompted to hit F6. Maybe you can choose the correct ACPI support option.

Since I succeeded with the installation of Windows XP with integrated "Universally modded" Intel RST driver v11.2.0.1006 onto my Z97 system running in AHCI mode, I am pretty sure, that it should work for you as well.

---

You were right, F5 does the trick, I focused on only on:
ACPI Multiprocessor PC
ACPI Uniprocessor PC
Advanced Configuration and Power Interface (ACPI) PC

At the bottom of the list was the "Standard PC" and it moved installations.
Thanks a lot for your time and help. ;)

Pozdrawiam/Regards
xpeu89

Update on the "F5" Trick with W2k on modern hardware:
* Hit "F5" when Setup shows to hit "F6"
* W2k will show a list. On some modern hardware you will only see a few possibilities with the option "Standard PC", "MPS" and "other".
* Don´t choose "Standard PC" first. Scroll up to see the other possibilities. Don´t choose "ACPI Multiprocessor" or "ACPI Uniprocessor". Choose "ACPI-PC".
A) W2k will tell you if your BIOS is not compatible with ACPI with a BSOD message (this is only shown when choosing ACPI-PC, not shown with ACPI Multi- or Uniprocessor-PC) OR
B) Setup will show the harddisk for installation.
Now, A) Shut down the computer or B) Hit F3 to shut down the computer.
* Repeat setup with "F5".
* If you had A) before, choose "Standard PC" for installation.
* If you had B) before, choose "ACPI-Multiprocessor-PC"

Hello Fernando,
in reply to post 208 (w2k ACPI problem):
I found out that NTDETECT and NTLDR in combination with ntoskrnl is true for up and running system. On every startup, windows loads ACPI table from bios to see if it changed since last startup. In txtmode setup, things are more complicated. There is a "mini kernel" loaded and usetup.exe in combination with ntdetect and ntldr do the decision about ACPI. Usetup makes two directories and copies files into it. The first directory is used for loading hal and drivers (phase 1 of txtmode setup), then, when "setup is starting windows 2000" message is shown, protected mode is entered (phase 2 of txtmode setup). I don´t know exactly, if in phase 2 the mini kernel is used again or if ntoskrnl does it yet.
Phase 1 cannot be the problem, because setup will decide that the system supports ACPI. But when entering phase 2, setup doesn´t find the startup device any more in ACPI mode. The same effect occurs if I want to change HAL from Standard-PC to ACPI-PC on up and running system.
NTDETECT.COM cannot be the problem, because XP original file is used.
NTLDR cannot be the problem, because XP original file is used.
Problem files could be HAL.DLL and NTOSKRNL.EXE, or this mini kernel file from which I did not find out the name.
What could I try to let w2k find the start device after changing the HAL on up and running system? The system hangs on acpitabl.dat. Perhaps there are some registry or other tricks to get it solved after installation?

Hello.

I have a problem installing SATA AHCI Drivers under Windows XP SP2 Professional (32 bit) for the Intel DH77EB. I have slipstreamed the drivers using nLite. Windows Setup seems to detect the HDD, because it formats it. It even copies the installation files and loads the drivers (I saw that while looking at the grey bar at the bottom of the installation screen). After that it restarts the computer (which is the way it's supposed to be), the XP logo shows up in the center of the screen, and after that BSOD with the 7B error.

My configuration:

Intel DH77EB Desktop Board
2TB WD Green Power HDD connected via sata 6GB port - the HDD supports Sata 6Gb/s.
DVD-+RW connected on SATA 3Gb/s port

Drivers slipstreamed: "Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller" and "Intel(R) 7 Series Chipset Family SATA AHCI Controller" downloaded from the Asus website for the Asus P8H77-M board (Version 11.1.0.1006 &11.5.0) - first package on the download page (about 26 MB) - http://www.asus.com/Motherboards/P8H77M/HelpDesk_Download/

No USB devices except mouse and keyboard are attached during installation, and the SATA mode selected in BIOS is AHCI.

My hardware IDs for the Sata controllers which works in IDE mode are:

PCI\VEN_8086&DEV_1E08&SUBSYS_20328086&REV_04
PCI\VEN_8086&DEV_1E08&SUBSYS_20328086
PCI\VEN_8086&DEV_1E08&CC_010185
PCI\VEN_8086&DEV_1E08&CC_0101

for the Intel 7 series/C216 Chipset Family 2 port SATA Storage Controller - 1E08 (I suppose that this is the SATA 6Gb/s controller)


and

PCI\VEN_8086&DEV_1E00&SUBSYS_20328086&REV_04
PCI\VEN_8086&DEV_1E00&SUBSYS_20328086
PCI\VEN_8086&DEV_1E00&CC_01018F
PCI\VEN_8086&DEV_1E00&CC_0101

for the Intel 7 series/C216 Chipset Family 4 port SATA Storage Controller - 1E00 (I suppose that this is the SATA 3Gb/s controller).


I even changed the iaAHCI file, because originally it supported the 1E02&CC_0106 and 1E03&CC_0106 Ids. I have replaced the following lines

PCI\VEN_8086&DEV_1E02&CC_0106.DeviceDesc = "Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_1E03&CC_0106.DeviceDesc = "Intel(R) 7 Series Chipset Family SATA AHCI Controller"

with these ones

PCI\VEN_8086&DEV_1E08&CC_0101.DeviceDesc = "Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller"
PCI\VEN_8086&DEV_1E00&CC_0101.DeviceDesc = "Intel(R) 7 Series Chipset Family SATA AHCI Controller"

and no luck :(


Could you please help me out Fernando? I have been trying to solve this on my own for a week or so (read the whole thread) and can't figure out what's wrong.

Fernando - Thank you for all the help and responses.

In my case, I was not able to use the methods prescribed, but I did manage to use an even older-skool "trick" to get my existing XP Pro 32 OS installed on a hard-drive with 100+ programs to work on a brand new GigaByte Z97X-UH3 motherboard.

First off, my XP install is...10 yrs old...at least. Ive used this same install on 3 previous motherboards, originally installed on a Pentium 2 BM, then PIII, then P4, this will be the 3rd on an i7 4GHz. (by install, I mean I have not re-installed XP for 10 yrs...even though its no longer on its original hard-drive or MB...another old trick which I can share...KEEP your old install from any hard-drive onto brand new hard-drive without needing to Ghost)

The Chipset on my new GB Z97X is of course the Intel 9700 series. The drivers appear to be version 04/03/2014,13.0.3.1001, and the DEV is 8CA2. I have not found a way to force any driver to work, because I havnt found an 8CA2 .inf .cat or any other file...the only way to get that particular driver appears to be an .exe executable install file directly from Intel...they are wising up.

So...How did I get my hard-drive to boot up and run on this new MB? Old-Skool - install a SIGG PCI S-ATA card into my old dying computer with any old SATA hard drive attached, power on existing XP OS and load the SIGG PCI SATA card drivers, power off, now unplug the XP OS from the MB and plug it into one of the SATA slots on the SIGG PCI SATA Card (still installed in the old computer) and boot up...this works almost every time (its worked for me for years on lots of different computers). Play around a few minutes to make sure the system is fine and power off. Take the SIGG PCI SATA card and existing XP OS Hard drive and plug them into the new Z97X Motherboard (Hard drive still plugged into the SIGG PCI SATA card), power on. Boom..it boots up to windows XP, which will find drivers...in my case Windows XP integrated the SIGG card's driver into the Motherboard's SATA controller by itself, I clicked Cancel on all other "new hardware found". I then powered down, unplugged and removed the SIGG PCI SATA card and plugged the existing XP OS harddrive into one SATA slot on the new Z97X MB - and it booted. I now have a 10+ yr old install of XP (with SP3) running on an i7 Z97 motherboard. Of course it only sees 4 or my 16 GB DDR3 ram, but its running.

When I attempted to force one of the Fernandos drivers thru "update driver", such as Chipset 9X...8C82, the new system BSOD's on me, and it wont load the driver from the intel .inf file...but its working nonetheless. Ive tried about 20 different ways...so Im gunna leave it as-is for now. Its working...and far faster than my old set-up.

a little off topic - I also was able to get the on-board Intel 1Gbe Gigabit Network card to work...Intel Specifically states it is NOT supported on XP 32 bit. Yeah, right...how to make that work? Click on the device, "update driver" and Install one of last years 1Gbe Gigabit PCI-E driver and it will magically work...Intel has purposely inserted text and compiled the new drivers .sys and .exe files to detect XP 32 and force a non-install...THANK YOU NOT Intel and the rest of Mfgrs attempting to rail-road users off XP.

btw - I currently work on a SLUG of a Win 7 i5 8GB DDR3 ram station at work...its ****-Slow compared to my P4 2GB XP station at home...only reason im upgrading my P4 at home is the graphics card started failing, and I want a really good card, and a system to last...its 4 yrs old and im sure the MB or socket 775 processor will soon follow suit...

XP simply put, does EXACTLY what it needs to do...why the forcing people to "upgrade" to slower systems MS and Intel? Are you attempting to force people onto slower systems so you can then sell them faster and faster systems? Did we reach a pinnacle of speed on XP to where shear processing was no longer an issue?

At least I got my XP on a new system...and its Blazingly fast...hopefully my experience will help others...always think OutSide the BoX :-)

Thank you for the quick reply, and also the explanation. Last night after a little more messing around, and before seeing your post, I also came to the conclusion (however not 100% sure) that the 8CA2 Device was not the SATA controller.

With your info I now have confirmation.

I attempted almost everything to obtain the .inf for the intel X97 chipset, every avenue led me to executable (not compressed) .exe installation files. Do you mind if I ask how did you find the actual .inf and other driver files for the x97 chipset?

On the actual IDE/SATA controller, I will have to take a look tonight...currently, after fixing the nv4_disp.dll BSOD error, the machine is up and running at what can only be described as Blazingly Fast...seriously...its able to open ACAD 2002 drawings in less than 1 second from a dead start (as in not preloaded and not loaded since previous boot), including all my LISP and compiled menus...in contrast, ACAD 2014 with the EXACT same set of LISP and Menu files takes over 1 full minute to load on my Win 7 64-bit i5 8GB at work.

If Im understanding correctly, I should be able to find the IDE/SATA in the devices with the corresponding DEV 8CXX and the update to one of yours?

As a side note, the XP was originally installed on a ATA66 or 133 controller, but SATA drivers were incorporated when it went to the last P4 MB, thats also when I moved the install from the old ATA to the new SATA HD that its currently on, so the correct SATA and chipset drivers were installed for the old socket 775 board...that entire install actually went without a hicup...its only the new stuff that MS and other MFGR's are purposely trying make NOT work on XP that seem to have issues...guess they need to waste their time on that rather than writing Efficient Code...why only use 5GB space on code when you have 1TB boot drives and you can instead use 50GB of "BloatCode"...haha

What gains, performance or otherwise, will I gain with that over the driver that is currently working (and working rather fast)?

Again, your thread and your help is awesome,

that explains it, I did not attempt installing the .exe file because my system was running so good I didnt want to risk a BSOD. I will attempt to install the exe today after setting a restore point.

Back on-topic...I fully understand the slipstreaming of the AHCI drivers into a fresh XP install;

However, I have So Many programs and settings loaded onto my XP system which relate to my drafting and engineering work that the re-setup of a fresh Install literally takes days to set-up and test to make sure my system works for my work and projects I do (I have a Very large amount of custom programming piggy-backed onto Acad and other Cad programs, as well as supporting programs and set-ups such as Adobe printers with the proper .pc3 setup files) This is why Ive kept my existing install of XP for so long...and its why I have a spare Hard Drive sitting in the computer able to be cold-swapped at any time and I can resume working as if no failure ever happened. All my files are kept on a 3rd hard drive and a USB back up.

That all being said...why does a fresh install with the slip-streamed drivers work, but going into the device manager and updating the generic driver not work? I had read several pages in the thread where people were doing just that, updating the driver to the .inf and .cat & .sys files with the modified drivers to work on XP...or am I missing something from those posts??

Right now I do have the BOIS set to IDE, but it also booted when set up with AHCI...strange no?

Thank you again.