No, that will not solve your current problem.
alright, i guess thats it for me and xp.
thanks for your help though
I am sorry, that I couldn’t really help you to get XP successfully installed onto your Intel 8-Series Chipset Mobile system. There are too many possible reasons for the failure.
Nevertheless I want to let you know, that it is difficult, but at least possible to get Windows XP installed onto an up-to-date Intel 8- or 9-Series chipset system.
Side note:
Because I wanted to be sure, if it works or not, I have recently tested myself the XP installation onto my Z97 chipset AHCI system. After a lot of failed tries and BSODs at the beginning of the XP installation I succeeded at least, but it took me a lot of time to find the right way. Meanwhile I have layed down some of my experiences into the start post of this thread.
@ all users with an Intel 8- or 9-Series Chipset AHCI system:
To make it easier for you to estimate the problems you may get by trying to install Windows XP and to avoid unneeded mistakes during the preparation and installation, I have added some special remarks and tips for users with an up-to-date hardware configuration into the start post of this thread.
Good luck!
Fernando
.
You cannot install Windows XP without a so-called "TEXTMODE" driver file named txtsetup.oem. The latest Intel RST driver with such file is v11.2.0.1006.
Btw: I have tried to create a txtsetup.oem file for newer Intel RST driver versions, but the XP installation failed with all my test packages.
Intel has never released
That is the latest Intel Chipset Device Software Set version with XP support, but regarding the INF file dates the latest package is the v9.3.2.1020. All files of the v9.3.2.1020 "All" folder are dated 02/27/2014, whereas the files of the v9.4.4.1006 are dated 08/01/2013.
Nevertheless there will be no big difference, because the date of the INF files say nothing about the date of their creation by Intel.
@Fernando :
I got Intel(R) 8 AHCI working with Windows 2000 on new ASUS Laptop R752LD (see Page 12). I used extended Kernel from blackwingcat. It makes no difference if Intel AHCI 11.2 (modded by Fernando) or Intel AHCI 8.9 (from blackwingcat) are used. The "jumping point" was ACPI. Windows 2000 seems not to understand BIOS, and this can cause setup to hang on "setup is starting windows 2000", before showing the harddisk. From this I followed a problem with iastor. But when hitting "F5" and choosing "Standard PC", iastor works fine, shows the harddisk and installs windows 2000 without problems. Now I would need tools to check if really BIOS is the problem. Can you give advice how to go on?
Greetings from Austria, Joe
@ Joe1962:
Hello Joe,
thank you very much for your contribution, which is very interesting and helpful for all users, who want to get an old Windows OS like Windows 2000 installed onto a brandnew Intel chipset system.
Just to avoid any misunderstandings: When you wrote "Intel(R) 8 AHCI", you probably meant your "Intel 8-Series chipset system running in AHCI mode". Is this correct?
This is an important find.
Since the "normal" users don’t know anything about blackwingcat and his "extended Windows 2000 kernel32.dll", it would be fine, if you could write a short guide about where to get and how to insert it into the W2k image.
I am not sure, if I will be able to help you with this. What sort of tools do you mean?
Thanks again!
Fernando
@ all:
If you want to know more about blackwingcat’s "extended W2k Kernel", you may look into >this< thread.
To avoid misunderstandings:
Yes, it is Intel 8 Series chipset system running in AHCI mode (there is no IDE compat mode available in bios).
To get more deep with extended kernel:
Blackwingcat, the japanese guru for windows 2000 has released two fantastic tools for windows 2000:
1) Extended core: hal and ntfiles are replaced with xp compatible ones, so driver sys files from xp (also some from vista) will work in windows 2000. This extended core files can also break processor (up to 12 processors) and memory limits (yes, I saw 8GB ram in w2k x86!!). Extended core is the one I integrated into slipstream cd (hfslip)and used for installation on new ASUS laptop.
2) Extended kernel: this is for applications; you can run firefox, google chrome etc on windows 2000.
+English source version: fortunally, there is no guide or tutorial needed to get these integrated. Blackwingcat produced a HFSLIP DVD, which you can download from his website (use: google: blackwingcat, extended kernel DVD); only the source windows 2000 CD has to be copied into the downloaded folders, then an burnable iso file is created (similar to nlite, which is used often here). Windows 2000 original CD must be english version.
+German version Windows 2000: a little bit more tricky for now, but blackwingcat announced a german version of extended core and kernel DVD coming soon. The advantage of the DVD: there are a lot of drivers and applications integrated which were ported to w2k from XP by blackwingcat, for example PCIE card reader, wireless network dev etc.
Problem with ACPI / Tools question: I really have no idea, why XP can recognize acpi correctly in the very first phase of txtmode setup and w2k cannot. if you press "F5" in XP installation when setup shows "press F6", it will show acpi mode as possible for installation. In w2k, it will only show "standard PC". That this may result from BIOS incompat with w2k was an idea of blackwingcat. So I think, there are two possibilities to get ACPI working in w2k exkernel installation:
a) examination of bios to see if there are incompatibilities -> mod bios -> installation
b) examination of txtmode setup (comparison of w2k and xp acpi and bios detection) -> take some components from xp and integrate in w2k txtmode setup -> installation
For a) and b) my knowlege is not sufficiant, because I never did edition or modding of bios components. Also for b), I don´t even know which files are loaded on "setup examins hardware configuration of the computer". So I thought perhaps you could help and give advice how to go on.
What I did yet: I used biosinfo.inf from XP, I modified txtsetup.sif and eliminated all really "OLD" devices which are not needed for installation. No success.
Greetings, Joe
@ Joe1962:
Hello Joe,
thank you very much for your detailed statement and instructions.
Since the ACPI problem at the beginning of the W2k installation has nothing to do with the topic of this thread, I suggest to move the last posts into Integration of Intels AHCI/RAID drivers into an XP, W2k or W2k3 CD thread, which I just have renamed for this purpose.
If you agree, I will put a link to your last post into the start post of the related thread.
According to my knowledge the original RTM version of Windows XP ("Gold" edition = SP0) and even the SP1 version of Windows XP doesn’t work properly. That is why I recommend within my guide to take a later XP version (SP2=minimum) as source for the Windows XP installation.
This is an important remark, which I will add into the start post of Integration of Intels AHCI/RAID drivers into an XP, W2k or W2k3 CD thread.
Regards
Fernando
Hello Fernando,
of course I agree with your suggestions how to place / link my posts. I am happy that some of the informations were helpful for other people. And - I did not realize this before - the F5 hit can show if modded intel drivers OR acpi problems are the reason for BSOD /Hang in the beginning of setup - a kind of "diagnostic tool".
Now I have running w2k with "standard PC" on ASUS R752LD and performance is still fast. I have LAN, WLAN, Intermediate lan/wlan drivers, Sound, Graphics (Intel 7 and nvidia graphics will not work even on XPSP3, but VESA from AnaPa can be used instead of standard VGA - Resolution: 1600x900x32 is possible in W2k with this trick). Problem is only Card Reader (installed, but yellow exclamation mark), because Card Reader AND LAN are controlled by the same hardware interface. But also XPSP3 did not like this, and when installing the driver for CARD reader, LAN disappeared from dev manager. Second problem is w2k floppy controller, it is present with yellow exclamation mark and I cannot get rid of it (but this is not really a problem, since this laptop does not have a floppy).
So I could use my "Standard PC" W2k system, but I want it to be done "really", and the beginning is w2k with ACPI on this laptop, because in standard mode I cannot have more than 1 core and 3,3GB Ram.
ACPI: Do you know which files are responsible when setup shows "setup is examing your hardware" in XP and w2k? TXTSETUP.sif , Biosinfo.inf and acpi.inf are used later, and 90% same content in XPSP3 and W2k, I think they will not have effect on this - is this true or wrong? Where can I find information about this? With google I did not find anything.
How do you consider the idea to make the bios compatible? Blackwingcat wrote to me, that I should try another BIOS and w2k could work properly in ACPI Multiprocessor mode. My BIOS version is APTIO setup utility 2.15.1236 / AMI BIOS Version 306 / VBIOS Version 2175.T15X550.007. And I saw you are experienced with bios and bios modding.
Greetings, Joe
Meanwhile I have moved the related posts into this thread and renamed the titles of the posts.
AFAIK it is the file NTDETECT.COM (in combination with the files NTLDR and NTOSKRNL.EXE).
I found it >here<.
I am sorry, but I cannot help you regarding the modifcation of system BIOS components.
Hey,
It is possible to install XP SP3 on Asus Z97-A?
I added the nlite driver Devid = 8c82 and I still have a blue screen 0x00000a5.
I installed from CD and USB, IDE mode, legacy mode, uefi off, when they have to show drives, screen of death.
Regards/Pozdrawiam
xpeu89
@ xpeu89:
Welcome at Win-RAID Forum!
Yes, it is not easy due to the modern chipset, but should be possible.
This indicates, that it is not the integrated driver, which caused the BSOD.
At what stage of the installation did you get the BSOD?
Have you used a clean (untoched) Windows XP image as source?
Did you unplug all unneeded storage drives before starting the XP installation?
According to my experience it is the best, if you
a) set all BOOT options within the BIOS to "LEGACY" and
b) boot off a CD running in IDE mode.
Regards
Fernando
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
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.
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.
Ok, I’ll try tomorrow, thanks for the quick reply.
Pozdrawiam/Regards
xpeu89
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?
@ Joe1962:
Thanks for your contribution regarding the ACPI settings via F5 at the beginning of the OS installation.
To make it easier for the users to find your tips, I have just updated the chapter "Additional advices for the later OS installation" within the start post of this thread.
Your findings and thoughts regarding the Setup processes during the textmode phase of the OS installation are very interesting as well!
Since I am not an expert regarding this special topic, I cannot help you with this. Nevertheless I am very interested in the results of your further investigations.
Another story, which may be interesting for you:
Recently I tried to make newer Intel RST(e) AHCI/RAID drivers of the v12 series usable for a Windows XP/W2k3 installation. Since all these Intel AHCI/RAID drivers with a higher version than v11.2.0.1006 natively don’t have a TXTSETUP.OEM file, I have tried to create such file myself. At least I was able to get a modded variant of the 32bit Intel RST(e) textmode driver v12.9.4.1000, which seemed to work. That means, that I was able to integrate it as textmode driver into a Windows XP image by the tool nLite. Unfortunately the later XP installation onto my Z97 system failed with the message "Setup couldn’t find the file iaStorA.sys", although this file was present even within the i386 folder. Then I tried to integrate the driver by using the tool XP-Isobuilder, but got the same result. At least I tried to integrate the textmode driver manually, but during the XP installation I got the message, that there was an error within the TXTSETUP.SIF file. I gave up my tests in July, because I didn’t have the needed time.
Since you seem to be a person, who may be able to find out the reason for the XP installation failure, I attach 2 different test versions (1 with, 1 without SCSI filter driver) of a 32bit Intel RST(e) textmode driver v12.9.4.1000.
If you should have any idea, please let me know it. Thanks in advance!
EDIT 1:
Due to a leak of my personal memory I didn’t remember the exact error messages I got during my textmode driver tests done in July. That is why I have corrected the last part of my post.
EDIT 2:
Today I have done a new test with the re-modded Intel RST(e) driver v12.9.4.1000 (without iaStorF.sys) by integrating it manually into a Windows XP SP3 CD using the $OEM$/WINNT.SIF method. The start of the XP installation worked fine, but as soon as the loading of the integrated Intel AHCI driver was shown by the Setup, I got again the message, that the file iaStorA.sys could not be found. I don’t know the reason for this message and how to prevent it.
Special 32bit RSTe AHCI & RAID drivers v12.9.4.1000 mod by Fernando.rar (285 KB)
Special 32bit RSTe AHCI & RAID drivers v12.9.4.1000 re-mod by Fernando.rar (271 KB)