Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 



tcpf429

Can't get BWC's AHCI/USB drivers to work on Q87 chipset?

Recommended Posts

Hello, all! 

I've been attempting to install Windows 2000 on a motherboard with a Q87 (8-series) chipset and a Haswell i7-4770 CPU. After downloading tomasz86's Windows 2000 version of HFSLIP, I inserted the following files into these folders:

In HF: UURollup v1.0d, Service Pack 5.1, KB2722913, KB951978 (and any other prerequisite hotfixes I needed to install BWC's kernel extender), plus a bunch of other up-to-date hotfixes from tomasz86's most recent update list.

In HFCABS: The relevant .cab files from the IE 6.0 SP1 installer as per tomasz86's instructions, BWC's AHCI version 8.9b driver, the update.cab file from BWC's Kernel Extender v2.8i, the latest USB Chipset drivers from BWC's Windows Legacy Update (ininst_autol11.cab).

In REPLACE\WIN\SYSTEM32: acctres.dll, url.dll, and wab32res.dll from the IE 6.0 SP1 installer.

Anyways, my problem is that while I've got setup to start (i.e., get to "Welcome to Setup!") in IDE mode, AHCI mode gives a INACCESSIBLE_BOOT_DEVICE BSoD. And in IDE mode, my USB keyboard does not work. Since there is no PS/2 port on the computer, I'm stuck here.

I've tried using other versions of the AHCI driver (8.9d and 8.9f, along with the old 7.6 version), the kernel extender (v2.2), not slipstreaming the USB drivers, not using the other hotfixes... basically everything I could think to change. I also tried disabling every extraneous device I could find in the BIOS, as well as setting USB to Legacy mode. Nothing changed the above errors.

I even tried installing Windows 2000 on another computer, installing all the relevant programs/hotfixes, and writing a Visual Basic script to advance the driver wizards so that they would install the USB drivers when I plugged the hard drive back into the Haswell computer. Even though that worked surprisingly well, the drivers broke when I attempted to install the 9.4 Intel chipset driver BWC linked to on his site--the files install, but the drivers fail to load with Code 10 errors on boot. To fix this problem, I dried three or four other drivers from Windows Legacy Update, but they all had the same problem. Compounding these issues, my video card (NVIDIA GT 620) wasn't detected in Device Manager after I swapped machines.

Obviously, the best solution would be to install Windows 2000 on the Haswell computer in AHCI mode without any hacky fixes. But I would be fine with IDE mode too. 

Do you guys have any ideas as to what I should try now? I'm plumb out of ideas.

Share this post


Link to post
Share on other sites

AHCI v8.9f driver is supported for AHCI.

I think the USB DVD disconnect while Windows 2000 installation.

I complete installed Windows 2000 to haswell Intel NUC , with SATA DVD.

Share this post


Link to post
Share on other sites

Thanks for responding so quickly!

I have been using a SATA DVD drive throughout all my attempts to install Windows 2000. 

I tried testing a new ISO with the 9.8f driver. I also removed the hard disk. However, I still get the same STOP error with AHCI and no USB without it. Should I recheck the non-necessary hotfixes I'm slipstreaming into the ISO? Could they be messing something up?

Share this post


Link to post
Share on other sites

I got the hardware ID from Windows 10: PCI\VEN_8086&DEV_8C02&SUBSYS_309717AA&REV_04

Share this post


Link to post
Share on other sites
On 2017/5/19 at 7:03 AM, tcpf429 said:

I got the hardware ID from Windows 10: PCI\VEN_8086&DEV_8C02&SUBSYS_309717AA&REV_04

Umm...

How about F6 install USB FD ?

Share this post


Link to post
Share on other sites
Posted (edited)

I obtain the message "iaStor.sys is corrupted" in that case. I tried multiple floppies and older versions of the driver with no change.

After looking around a bit more, I think my problem is that I wasn't inserting the driver files in the HFEXPERT folder, so the drivers and kernel extender were not slipstreamed. However, when I tried to fix this, I had no success. (I tried to use your prior instructions for slipstreaming the Kernel extender in the Haswell thread, but there are no HAL or NT* files in the latest version when I extract it). The storage driver does not seem to get slipstreamed when I insert the .inf and .sys files in the HFEXPERT\STORAGE folder.

Edit: The AHCI driver (and presumably the USB one) now appear to be slipstreamed, as I get "iaStor.SYS is corrupted" without using the floppy drive.

How should I integrate the Kernel Extender into HFSLIP?

Edited by tcpf429

Share this post


Link to post
Share on other sites
On Tuesday, May 30, 2017 at 6:48 PM, blackwingcat said:

Umm...

How about F6 install USB FD ?

BlackWingCat did you ever create a SATA AHCI driver for Windows 2000 unmodified standard version?

Share this post


Link to post
Share on other sites
Posted (edited)
On 2017/6/23 at 10:41 AM, 98SE said:

BlackWingCat did you ever create a SATA AHCI driver for Windows 2000 unmodified standard version?

What does it mean unmodified ? :3

http://w2k.flxsrv.org/wlu/wlu.htm

You can get 7.6(for vanilla) and 8.9 (for Extended Kernel Core)

If you use 8.9 on Vanilla, I think that it shows  "iaStor.sys is corrupted"

Edited by blackwingcat

Share this post


Link to post
Share on other sites
On Monday, June 26, 2017 at 5:16 PM, blackwingcat said:

What does it mean unmodified ? :3

http://w2k.flxsrv.org/wlu/wlu.htm

You can get 7.6(for vanilla) and 8.9 (for Extended Kernel Core)

If you use 8.9 on Vanilla, I think that it shows  "iaStor.sys is corrupted"

Windows 2000 Professional no service pack is unmodified. :3

Where is the link to 7.6 SATA AHCI driver for it?  I will test it BWC.

The 'iaStor.Sys is Corrupted" is the normal message I have seen.

Share this post


Link to post
Share on other sites

The 7.6 driver worked on a Penryn processor with a vanilla Professional disk and is running quite nicely. I cannot physically access the Haswell machine for several months yet, but I will take that time to learn more about HFSLIP and hopefully get Windows 2000 working.

Here is the link to BWC's blog post about the 7.6 driver: http://blog.livedoor.jp/blackwingcat/archives/813816.html

Share this post


Link to post
Share on other sites
Posted (edited)
On 2017. 5. 15. at 10:01 AM, tcpf429 said:

Hello, all! 

I've been attempting to install Windows 2000 on a motherboard with a Q87 (8-series) chipset and a Haswell i7-4770 CPU. After downloading tomasz86's Windows 2000 version of HFSLIP, I inserted the following files into these folders:

In HF: UURollup v1.0d, Service Pack 5.1, KB2722913, KB951978 (and any other prerequisite hotfixes I needed to install BWC's kernel extender), plus a bunch of other up-to-date hotfixes from tomasz86's most recent update list.

Just for information, the UURollup cannot be slipstreamed like that. HFSLIP does process it like any other update but the problem is that there are many files in it which have to be either renamed or go to specific folders and HFSLIP just puts all of them as they are into the %systemroot%\system32 folder. There are also many registry settings which have to be applied during the installation process but are not due to the HFSLIP's method of direct update integration. All in all, this will surely result in a broken / half-way integration. On the other hand, you may try to put it in HFSVCPACK_SW1 (still untested though).

I would also strongly suggest not using the USP 5.1 if you follow my updates lists because everything included in the USP should be covered by the lists, and also because the USP installs buggy USB 1.1 drivers.

Edited by tomasz86

Share this post


Link to post
Share on other sites

Ah, that would explain a lot. I had both of those problems at various points of this process. My two working solutions were to either install everything from vanilla SP4 (time-consuming, but fun) or use an HFSLIP image that only required building the iso (the "FullPack" on your website or BWC's ISO creation image) and UURollup+BWC's kernel extensions (much, much faster).

Also, I did get the 8.9 version of the driver working by following BWC's instructions about slipstreaming the driver and by adding the relevant device entry to my storage.ini file.

Share this post


Link to post
Share on other sites
21 hours ago, tcpf429 said:

Ah, that would explain a lot. I had both of those problems at various points of this process. My two working solutions were to either install everything from vanilla SP4 (time-consuming, but fun) or use an HFSLIP image that only required building the iso (the "FullPack" on your website or BWC's ISO creation image) and UURollup+BWC's kernel extensions (much, much faster).

I personally have not really tested mixing UURollup and BWC's kernel like that. On the one hand, UURollup originally had the BWC kernel included, but it has not been updated for a long time which means that the files are older than the ones from the newest BWC kernel releases. This may possibly cause issues. On the other hand, UURollup also installs many other unofficial / 3rd party files that are not covered by the kernel, so it does make sense to use both of them together. All in all, I am not going to tell you not to use them together, although I myself would probably not do it.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×