Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Win2k on Intel Z77

- - - - -

  • Please log in to reply
33 replies to this topic

#26
bluebolt

bluebolt

  • Members
  • 42 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag
Hello,

I set up Windows 2000 Professional on an Intel Z77 motherboard (the Biostar TZ77MXE) and an Intel i7-2700K Sandy Bridge processor. The Biostar Z77 board has Windows 2000 drivers, but only for audio and LAN. Iíve been unable to make the Intel HD 3000 integrated graphics work yet, so for now Iím using a video card. The Intel Chipset Device Software (INF Update Utility) dated 11/06/2012 from the Intel Download Center works with Windows 2000. Once installed, Device Manager correctly shows ďIntel 7 Series/C216 Chipset FamilyĒ under IDE ATA/ATAPI Controllers, and from there I was able to de-list the remaining unknown devices, so that Device Manager has no problem devices now, and the system is working well.


How to remove advertisement from MSFN

#27
AnX

AnX

    ...

  • Members
  • PipPip
  • 153 posts
  • OS:Windows 7 x64
  • Country: Country Flag

Hello,

I set up Windows 2000 Professional on an Intel Z77 motherboard (the Biostar TZ77MXE) and an Intel i7-2700K Sandy Bridge processor. The Biostar Z77 board has Windows 2000 drivers, but only for audio and LAN. Iíve been unable to make the Intel HD 3000 integrated graphics work yet, so for now Iím using a video card. The Intel Chipset Device Software (INF Update Utility) dated 11/06/2012 from the Intel Download Center works with Windows 2000. Once installed, Device Manager correctly shows ďIntel 7 Series/C216 Chipset FamilyĒ under IDE ATA/ATAPI Controllers, and from there I was able to de-list the remaining unknown devices, so that Device Manager has no problem devices now, and the system is working well.


How did you get the Intel MEI driver to work? Which GPU are you using?

#28
bluebolt

bluebolt

  • Members
  • 42 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag
The Management Engine provided by Biostar did not work for Windows 2000, so I downloaded one of those driver-search services (canít remember which), entered my board model, and let it scan my system; it provided a list of drivers to try. The first one on the list worked (and I think the only one), an ASUS MEI, however that figures. This cleared the last problem in device manager (PCI Communications Controller).

Iím using an X600 XT graphics card, for which a Windows 2000 driver is available.

#29
AnX

AnX

    ...

  • Members
  • PipPip
  • 153 posts
  • OS:Windows 7 x64
  • Country: Country Flag

The Management Engine provided by Biostar did not work for Windows 2000, so I downloaded one of those driver-search services (can’t remember which), entered my board model, and let it scan my system; it provided a list of drivers to try. The first one on the list worked (and I think the only one), an ASUS MEI, however that figures. This cleared the last problem in device manager (PCI Communications Controller).

I’m using an X600 XT graphics card, for which a Windows 2000 driver is available.


I modified the .inf of the MEI driver so it runs on Win2K. I copied the XP hardware IDs to Win2k section.

Edited by AnX, 25 March 2013 - 03:28 AM.


#30
bluebolt

bluebolt

  • Members
  • 42 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag

BlackWingCat released a new AHCI SATA driver version 8.9 dated 02/23/2014, purportedly workable with Windows 2000 on the Z77 platform (7 Series / C216 chipset).  I decided to conduct a prelimary test to see if it worked using an Intel Sandy Bridge i7-2700K CPU on a Biostar TZ77A motherboard, and the results look promising.

 

The problem before, when integrating the XP driver, has been the error “iastor.sys is corrupted,” which stops the show early in the installation process, and leaves IDE mode as the only available option.  While I’m still uncertain just how great a performance improvement there is running “true” SATA mode (compared to IDE), this has nonetheless remained a W2K grail of sorts for me.

 

Today I installed Windows 2000 Professional using the USP5.1 HFSLIP package tomasz86 provides, which includes UURollup v11d20130226; this is the best kernel extension option I have for the installation process (after installation I updated to 11d-20140103).

 

I suppose there will still be problems to work through, as this was a cursory test, but the result looks a lot better to me than a blue screen that simply says “The iastor.sys is corrupted.”  Thank you, BlackWingCat.

Attached Files


Edited by bluebolt, 26 February 2014 - 10:49 PM.


#31
blackwingcat

blackwingcat

    Friend of MSFN

  • Members
  • PipPipPipPipPip
  • 716 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag

BlackWingCat released a new AHCI SATA driver version 8.9 dated 02/23/2014, purportedly workable with Windows 2000 on the Z77 platform (7 Series / C216 chipset).  I decided to conduct a prelimary test to see if it worked using an Intel Sandy Bridge i7-2700K CPU on a Biostar TZ77A motherboard, and the results look promising.

 

The problem before, when integrating the XP driver, has been the error “iastor.sys is corrupted,” which stops the show early in the installation process, and leaves IDE mode as the only available option.  While I’m still uncertain just how great a performance improvement there is running “true” SATA mode (compared to IDE), this has nonetheless remained a W2K grail of sorts for me.

 

Hi.

8.9 Driver requires Extended Core.

If you use normal ntoskrnl.exe then you must use 7.6 iastor.sys.



#32
bluebolt

bluebolt

  • Members
  • 42 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag

I've now installed all my software, which went fine in AHCI mode, no hangups or glitches at all there.  The first thing I tried was to rip a DVD disc to the HDD, and found it took twice as long as IDE mode.

 

My initial thought was that I had neglected to set the controllers to DMA mode for the optical drive, but apparently that concept doesn't apply to AHCI, so there was no option for doing so.  I uninstalled the optical drive and rebooted to let the system reinstall it, but it couldn't; the specific drive model is listed correctly in Device Manager, but there is a yellow exclamation mark over it, although this same drive installed fine during the OS installation in AHCI mode.  I uninstalled the AHCI controller and rebooted, but this produced the same result.



#33
bluebolt

bluebolt

  • Members
  • 42 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag

I previously tested using BWC’s AHCI driver version 8.9b.  Now version 8.9c is available, so I decided to re-test, and the results show a definite improvement on my system.

 

As before, the first thing I tried was to rip a DVD disc to the HDD, and found, once again, that it took twice as long as IDE mode.  I used Device Manager to uninstall the DVD drive, as before; but this time, when I re-booted the DVD drive re-installed properly.  I decided to rip the DVD again, and it ripped twice as fast – in other words, about the same as IDE mode.  So driver version 8.9c seems to have fixed the optical drive problem (at least after a reinstallation).  Good news there.

 

Next I ran the following tests:

 

Attached File  AHCI VS. IDE.JPG   173.44KB   1 downloads

 

These comparisons involve very few variables.  I made two separate OS discs:  one with the AHCI driver (integrated using nLite), the other without the AHCI driver.  The only different installation setting was, of course, to the BIOS SATA mode (AHCI or IDE).  I installed the OS on the exact same hardware, in the same way, deleting the old partition and creating a fresh partition of the same size in each instance.  I used a WD Black 2.5” 7200 RPM HDD to save wear and tear on my SSD, and did not overclock.

 

At some point I would like to try these tests again using an SSD, since the main performance advantage ascribed to AHCI is Native Command Queuing (NCQ), which may be nullified when using a solid-state drive.



#34
blackwingcat

blackwingcat

    Friend of MSFN

  • Members
  • PipPipPipPipPip
  • 716 posts
  • OS:Windows 2000 Professional
  • Country: Country Flag

IDE mode has PIO Problem risk.

So I think we had better use AHCI. :)

 

http://support.microsoft.com/kb/817472






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN