Re: Unable to install XP Pro - BlueScreen!

Ah yes a vigorous discussion containing much research and even fewer
solutions. I attempted the XP w/SP2 disk which also failed in the same
fashion but with a different bluescreen message. I think it said "surrender,
all your base are belong to us" whatever than infers.

My next trick is to install a floppy drive equipped with the SATA drivers.
Then I would expect F6 to function properly. HOWEVER, the drivers Intel
Matrix Storage Manager of Intel G965 Express Chipset, located at
http://www.intel.com/support/chipsets/sb/CS-022768.htm are in .exe form. I
am now trying to find them in their native format in order for Windows setup
to use them.

What a colossal waste of time and a I say "a plague upon yee Hewlett
Packard" for having not a single idea or resource to solve this via chat
support.

--
~ every 100 years, all new people ~


"John John (MVP)" wrote:

The F6 solution wasn't my idea, it was suggest by others, I suggested
that he slipstream SP2 in his installation disk. I don't think that
this is a SATA issue, I think that this is caused by newer PCIe hardware
that the original Windows XP setup doesn't know how to properly handle.
Apparently the OP doesn't want to go the SP2 route so I don't have
much else to add to help resolve the problem. A case of the proverbial
horse being led to water... he'll drink when he is thirsty enough!

Intel has this to say about this pci.sys installation error:

[Quote]

If you are installing Windows XP on an Intel® Desktop Board that
includes PCI Express* support, you must use Windows XP with Service Pack
2, otherwise you may see the following blue screen error during
installation:

***stop 0x0000007E ( oxc 0000005, oxf9a380bf, oxf9e84208, oxf9e834208,
0xe9e83f08
*** PCI.SYS address f9a380bf base at f9a31000, date stamp 3b7d8ssc

If you do not have an installation CD that includes Service Pack 2, you
can create a ‘slipstream’ CD.

[end quote]

http://support.intel.com/support/motherboards/desktop/sb/CS-028426.htm#pcisys

John

Gerry wrote:
John

Another alternative is to acquire a more up to date CD with the updates
already incorporated in the CD (I think it may only need SP1). A
different hard drive is another. Your F6 point is new to me so just keep
the information flow going <G>. The OP is spoilt for choice! Which do
you think is the best solution? Slipstreaming or your F6 solution?



.

Relevant Pages

  • Re: Unable to install XP Pro - BlueScreen!
    ... The quote in the last post had me wondering. ... drivers Intel Matrix Storage Manager of Intel G965 Express Chipset, ... format in order for Windows setup to use them. ... suggested that he slipstream SP2 in his installation disk. ...
    (microsoft.public.windowsxp.general)
  • Re: Unable to install XP Pro - BlueScreen!
    ... The quote in the last post had me wondering. ... drivers Intel Matrix Storage Manager of Intel G965 Express Chipset, ... format in order for Windows setup to use them. ... suggested that he slipstream SP2 in his installation disk. ...
    (microsoft.public.windowsxp.general)
  • Re: Unable to install XP Pro - BlueScreen!
    ... Intel download site is what you're looking for. ... My next trick is to install a floppy drive equipped with the SATA drivers. ... am now trying to find them in their native format in order for Windows setup ... Intel has this to say about this pci.sys installation error: ...
    (microsoft.public.windowsxp.general)
  • Re: A PROGRAM IN XP
    ... Might they have been refering to the Intel Application Accelerator? ... Verifying Installation of the Software ... Windows XP. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: What Does "I386" Mean?
    ... Several years ago, Microsoft envisioned versions of NT and follow-ons for the Intel 386..., DEC/COMPAQ/HP Alpha, etc. I386 was named because that is where Intel 386 - specific software would live. ... versions of Windows) to work at all on XP. ... Apparently, an installation ... For example, when you delete a driver for whatever reason, at the next boot, Windows looks in I386 for the correct driver. ...
    (microsoft.public.windowsxp.general)