• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About rsnetto

Profile Information

  • OS
    none specified
  1. Strangely, Intel has withdrawn from P67/H67 support pages. It is still available, but only for Z68 and Q67 boards. For the others, is listed again as "Latest".
  2. After some further tests, I finally discovered the trick. Service Pack 3 is required to install Windows XP on a machine with P67 chipset (and probably H67 too, maybe even Z68). I tested drivers without SP3 and got BSOD. Latest drivers ( with SP3 worked. So if you want to install XP on a Sandy Bridge machine you'll need to integrate SP3 and the Intel drivers. Driver version is not important as soon as they are recent enough, and also is not necessary to "isolate" a specific one, you may integrate the full pack. Again, the SP3 requirement is not mentioned anywhere in the Intel documentation. I'm updating the previous post to reflect the conclusions.
  3. Hello everybody, I've just registered to this forum to tell my experience in installing WinXP with RAID/AHCI in a new Sandy Bridge machine with a P67 chipset, more specifically, an Intel DP67BG board (BIOS v.1900) with Core i5 2500K processor. I have looked for it on the Internet and was unable to find a solution, even here. So I decided to contribute to this topic which seems to be the most important source of information on this subject. This lack of infomation makes me suspect that no one has ever tried to install WinXP using RAID/AHCI with a P67 or H67 chipset. The DP67BG board has 6 SATA ports controlled by the chipset, and an additional eSATA port controlled by a Marvell chip (which I'm not using yet). I was trying to install Windows XP Professional SP2 using an IDE optical drive, connected via IDE-USB external adapter. I tried two different HDDs, one regular SATA and other IDE connected via IDE-SATA internal converter (this proved to be no problem). Following the directions from here and elsewhere, I slipstreamed the latest Intel "floppy" drivers and nothing worked. I always got the infamous blue screen (7B error) at the "Setup is starting Windows" phase of the textmode setup. Then I tried to include only the driver (supposedly) needed, "Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller", and again BSOD at the same point. The only working configuration was to set the SATA interface to "IDE". This happened regardless of the HDD connected. Finally I found a setup that worked. I decided to try RAID, since the board's manual says nothing about AHCI (but has instructions to setup WinXP with RAID) and also an older driver, since I had read there are sometimes incompatibilities with newer drivers. So I obtained a driver set (from AsRock website, since Intel does not provide older drivers) and made a slipstream with only the Desktop/Workstation... RAID driver. I also added SP3. Set the interface in RAID and voilà.... Windows XP installed without flaws. (update: after that I verified that these are the same drivers mentioned on the first page of this topic) However, setting the SATA interface to IDE or AHCI still crashes WinXP on boot. I'm not very worried about because as I read, the RAID mode includes AHCI functionality. Update: I managed to make IDE mode work by enabling the external SATA controller, as it defaults to IDE, it makes WinXP install the "missing" drivers on the next boot. This can be done with any board that has more than one SATA controller. In the meantime, I also tested the modified WinXP installations with a netbook with an Intel 945 chipset (ICH7M). I got BSOD with the unmodified setup and also with only the "Desktop..." driver included, but it worked with the all the (latest) drivers. So I concluded that the setup does not need to have only the specific driver, it is able to pick up the right one in the package. I still have to research what made the "magic" work. I still don't know if it was the older driver (my main suspect), SP3, or both. update: The "magic" was done by Service Pack 3. It seems to be REQUIRED to AHCI/RAID work on Sandy Bridge chipsets. However, ICH7M does not need it. The netboook's BIOS config screen reminds of SP1 instead. Here a summary of the configurations tested: As expected, when the machine is set to IDE, all configurations work. And the untouched WinXP installation always crashes with AHCI set. Including ALL Intel (latest) drivers: Netbook, set to AHCI = WORKS DP67BG, set to AHCI = BSOD DP67BG, set to RAID = BSOD Including only "Intel® Desktop/Workstation/Server Express Chipset SATA AHCI Controller", Netbook, set to AHCI = BSOD DP67BG, set to AHCI = BSOD DP67BG, set to RAID = BSOD Including SP3 and "Intel® Desktop/Workstation/Server Express Chipset SATA RAID Controller", Netbook, set to AHCI = BSOD DP67BG, set to AHCI = BSOD DP67BG, set to RAID = WORKS Including ALL Intel drivers: Netbook, set to AHCI = WORKS DP67BG, set to AHCI = BSOD DP67BG, set to RAID = BSOD Including SP3 and ALL Intel (latest) drivers: Netbook, set to AHCI = WORKS DP67BG, set to AHCI = WORKS DP67BG, set to RAID = WORKS Last but not least, shame on Intel that don't point out the right driver for each board/chipset. They only make only generic driver packages and generic documentation. It would be a minor problem in a "regular" installation using floppies, where one could find the right driver by trial and error easily, but when we need to modify a XP install to include the drivers, it becomes really painful. update: Later I found this topic with a method to put the WinXP setup on a USB drive, it makes experimentation easier by eliminating the need to burn CD-Rs, but it still takes a lot of time.