| Last online: 02.12.2017
Try this one (21.1): https://downloadcenter.intel.com/downloa...-?product=47620
Checked it by myself, your LAN controller (10D3) is listed there.
Download the file, extract it with 7-zip if you like to check first, then change to the extracted directory.
From there go to: \PRO1000\Winx64\NDIS62
e1q62x64.inf is your file.
EDIT: new link ... even if you product is not listed on the webpage, it is supported. If the setup does not find your adapter, add the INF manually through device manager and Windows should show your adapter only and mark it as compatible.
Thank you for the nice guide.
At last updated 188.8.131.523 to 184.108.40.2064 (each 1,5 MB) on Intel Desktop Board DX79TO. I literally waited YEARS for that. Next step will be rebuilding BIOS 0650 with FITC and Intel ME 8.x. Any ideas how to do this or has anybody yet done this? :-)
Intel ME 8.x on X79 ASUS boards is delivered by BIOS update. Intel told their users there will be no 8.x for DX79xx boards.
Zitat von Fernando im Beitrag #11
[...] If the user wants to know, whether TRIM is active within the target SSD (inside or outside a RAID array), he has to do an appropriate TRIM check (look >here<).
Yes, sorry. You are absolutely right. I just flew over my DOCs and found this. Since I don't have any problems with TRIM anymore (it IS indeed working on my DX79TO with 2x SSDs in Raid0, see screenshot), I forgot you have to check with this tool.
Sorry again for my mistake and the resulting confusion. :-)
EDIT: I use RSTe (Rapid Storage Technology enterprise) driver version 220.127.116.112 now instead of the one described above, if that matters.
Zitat von linkpark007 im Beitrag #1
[...]I have a dx79to Intel motherboard [...]
1, [...] a long time can not be used to update the Intel RST ubu ROM. What should I do to solve this problem
2, I want to enable the x79 raid functionality, I in the BIOS open raid computer installed only a hard drive, through the CD-ROM installed win7 pro, to the installation interface, I by 3.6 rste F6 loading driven, I can see the hard disk, but setup told me "Windows cannot be installed to the disk, the computer hardware may not support booting to this disk. Make sure the disk controller is enabled on the BIOS menu of the computer.
I want the result is that X79 enabled raid, in the RAID 0 can be used under the trim
I did a search through Google, but did not find a suitable solution, Can I get help here? thank you
Hi there. I own DX79TO, too.
I try to explain simple for google translator.
1.) This is not possible without professional knowledge! DX79TO uses RSTe ROM module (enterprise). You want to have RST (without enterprise). You would have to change module within BIOS. DX79TO is NOT an AMI BIOS! You MUST rebuild BIOS with Intel's own tools from scratch! Without knowledge this would take a long time and very possibly destroy your board! (not bootable!)
2.) X79 RAID is possible and already there. Please do this to enable:
Do you have the latest BIOS installed? (version 0650 is latest)
Download BIOS from Intel:
Windows EXE (easy way, will reboot and flash, recommended): https://downloadmirror.intel.com/23825/e...86A.0650.EB.EXE
BIO file only (advanced, if you have the tools): https://downloadmirror.intel.com/23825/eng/SI0650P.BIO
Please get the following things ready on USB before continue:
(I think you will install 64 bit version)
- RSTe drivers: https://downloadmirror.intel.com/25393/e..._18.104.22.1683.zip
Extract and copy the AHCI folder from archive path: \Drivers\x64\Win7_2K8\AHCI\ to your USB drive. The RAID driver is there!
- LAN driver to download drivers after windows install. Get it from: https://downloadmirror.intel.com/18713/eng/PROWinx64.exe
(version: 21.0, x64, new)
- Your Windows 7 CD / DVD
Go to BIOS and set the controller to RAID.
Reboot and press CTRL + I at the RAID screen to setup your RAID 0. Choose stripe size as recommended for your RAID array. I use 128kb stripe size. I have 2x 256GB SSD in RAID0. Use the SATA 3 ports for best speed.
Reboot and install Windows 7.
On hardware screen choose to install a driver.
Choose driver from the AHCI folder on USB.
Your drive should get detected now. You should be able to install successfully on RAID0.
Info: If you use RST drivers (not RSTe!) you are NOT able to install, since RST drivers have no entry for X79 RAID.
I hope this works for you.
Last thing with TRIM: Use this command with ADMINISTRATIVE "cmd" within Windows to check for TRIM:
fsutil behavior query DisableDeleteNotify
If you get "0" as answer = TRIM OK
If you get "1" as answer = TRIM not working!
P.S.: I only check here few times a month. Please excuse me if I do not answer for a long time.
After researching for a while, I found out different things, which could be interesting for other modders, so here we go:
- There are a lot of "Intel ME"-BIN-files around the net. They almost all have been extracted by the FPT tool. FPT seems to give them a fixed size of 1524kb. Since my extracted ROM was only 1304kb I opened the file with some hex editor and searched for similarities. After stripping the "header", which is obviously NOT needed (I have to search again how much space it consumes exactly) and after removing all FF's at the end (filling garbage) I got a ME8 file with about 800kb only!! This file starts exactly like my extracted ME7 file AND IS READABLE NOW WITH FWUPDLCL VERSION 7!!! (which showed version like 65536.xxx before!) But I still don't want to flash it xD
Screenshot of FWUPDLCL showing BOTH firmware versions:
1st try is my backupped ME7 version from my DX79TO
2nd try is the "modded" ME8 file read by FWUPDLCL version 7.x!
3rd try is the "uncut" version of the ME8 file from 2nd try (the "original" one!)! You see the version? :-)
Probably we would be able to upgrade ME7 to ME8 with that!
- If MEINFOWIN shows you "BIOS and GBE config lock = ENABLED" and/or "Host Read/Write Access to ME = DISABLED", but "Local FWUpdate = ENABLED", you only have a chance to update ME with FWUPDLCL (you could "translate" the name to "FirmWare UPDate LoCaL"). FPT will NOT work for you, since it can't temporarily disable the locks.
- It is easy to determine which kind of ME FW you have (1,5MB or 5MB): 1,5MB version is ME only (with a few extra things), 5MB is the full AMT version with remote access and all the stuff bundled. All X79 series mainboards (AFAIK!) only have 1,5MB ME FW.
- ME FW comes as container / capsule. So even if your ME has 1,5MB or 5MB, the real program within could be / is smaller than these sizes. The remaining space is filled with FF's or is occupied from the extraction data from FPT.EXE. If you open a 1,5MB firmware file which has been extracted with FPT.EXE with some hex editor, you will see this at the beginning:
I am at the time I am writing this about 98% sure, this is only garbage (or only needed if you update via FPT.EXE). After removing all stuff which seems to be "header" or "trailer", I got an ME7 file with 613.488 Bytes instead of 1.335.296 Bytes and a ME8 file with 827.952 Bytes instead of 1.560.576 Bytes.
- to be continued! :-)
It has to be done within my system, live, while it is running, so you can't help me. ;-)
But thank you for the offer.
Zitat von Fernando im Beitrag #4
That is why I recommend to post your request >here<.
They can't help me! xD
I am regged there since a few years and they helped me with some other BIOS modding, but they cannot help me with this. One did send me many tools to insert SLICs, but nobody has managed to change modules, yet.
Ah, and don't panik. I know, this "BIOS modding" stuff can be illegal, but I don't want to do anything illegal and I don't want to post illegal content here! I am just searching for the help Intel should give me. But since they don't, I want to learn the stuff myself and "kick their 4$$3$".
Zitat von Fernando im Beitrag #2
Intel BIOSes with the extension .BIO are "disguised" AMI type BIOSes, which have to be switched to a real AMI BIOS. You will need a special tool named BIO2AMI (look >here<). After having done that, you can modify the BIOS by using the appropriate AMI Aptio UEFI MMToool. Once the modification has been finished, the BIOS file has to be reswitched to a .BIO file.
I am sorry, but I will not give you (and will not allow to publish within this Forum) a link to the BIO2AMI tool, because the use is dubious and many Antivirus tools will detect malware within it.
I tried it out, but my BIOS isn't AMI. The tool doesn't find the AMI string within and aborts operation.
... still in need of the config file for IFTC.EXE ...
Zitat von 100PIER im Beitrag #62
So, what are your comments ?
Disable the CSM (Compatibility Support Module) if you have a 100% pure UEFI install of Windows. If you don't, Windows probably won't boot. In this case, just enable the option again and everything will work again like it should. I am very sorry, but my french is somewhat bad, I don't understand the options you expanded within the CSM-menu. Could you translate them into english please?
What is CSM?: CSM is (easy spoken) the ability to use UEFI and the "old" BIOS "side-by-side". Your mainboard offers both and waits what option is taken. If your OS (and hardware) do use "the old method", it will boot without UEFI. If all your OS and hardware is UEFI compatible, you will boot with all UEFI options enabled. But if only one of your hardware parts or your Windows install is NOT UEFI compatible (you installed Windows without UEFI), UEFI will NOT be enabled, nevertheless what you choose in BIOS. In this case, disabling CSM could lead to an unbootable system.
(I tried to explain that as easy as I am able to, so a few things are "not 100% exactly as I described them".)
As Fernando said, disable the "Message Option ROM", so booting will take less time.
Zitat von Fernando im Beitrag #19
Maybe >this< thread will help you.
It HAS to help me ... xD
Did you see the pictures? I wait for almost an hour now, but they don't load completely. I try to refresh the site every here and then, but no luck. :-(
But I saw a picture with Intels FPT tool on this page. *biggrin*
So I was right, let's play with the tool now, muhahaha.
IDDQD (who is wrecking his computer now, so please be patient) ;-)
EDIT: There is no "Abwrackprämie" for computers, no?
Zitat von Fernando im Beitrag #17
This Firmware version is only suitable for systems with an Intel 6- or 7-Series chipset. The Firmware update should be started by running the flash.bat of the subfolder, which suits the OS environment.
If you should run a 64bit Windows OS, you have to execute the flash.bat of the Win64 subfolder.
x79 is not 7-series, no?
this is what this ME_INFO prog showed me after running it:
and this happened after runnning the flash.bat:
So no compatibility here with x79 ....
Zitat von cybersm im Beitrag #13
Hello, What's up.
About these problems with this mobo and after noticing that the 5830 was dead I replaced her for an XFX 6870. All is OK concerning about the video but after testing and testing the dual channel refuses to work properly. When it works a lot of Blue Screens appear randomly. I tested (replaced the G.Skill Ripjaws ) to Corsairs One ( what I use in dual in my Intel PC) and they are also unstable with the AMD PC.
Testing the G.Skyll in my Intel they work well .
So, what I can conclude that the problem is either the CPU or Mobo ( M4A87D). What do you think?
you run DIMMs with very low latencys programmed (CL7!), while JEDEC specs are CL11 for DDR3-1600. I bet your DIMMs voltage isn't "standard" either, right? Probably, the mem controller doesn't provide enough power or sets the values wrong, so if you are able to enter BIOS (with one DIMM?), set the values, which are printed on your sticks MANUALLY. As COMMAND RATE choose "2T" or just "2", that is the "normal" setting. Most boards won't boot with this "uber-clocked" memory, while values are set to AUTO. I had a rare testkit from a big company once, with DDR2-800 DIMMs with 3-4-3-8-2T @ 2,4V. It took me 5 (five!) boards until I got one which booted with those sticks.
Zitat von bwana im Beitrag #1
The bios setup screen in some motherboards has an option to enable UEFI. For example:
As I understand it, UEFI enables quick boot in windows 8 but has little benefit for win7. How does the selection of BIOS vs UEFI impact the use of AHCI vs RAID, if any? Certainly, when modding the OROM and the driver of an x79 chipset, unintended consequences can be disheartening. Does anyone have experience with the behavior of RAID under an OS installed under a traditional bios vs UEFI?
With UEFI, you may boot from drives greater than 2TB (which is a big laugh, because it uses a smaller UEFI partition to boot your x>2TB HDD).
In addition, you get a new "platform", because BIOS is more than 20 years old.
You get an EFI shell as well, but not every manufacturer gives you access to it. It is like CMD within Windows, but with different commands.
Modules / OROMs / etc. are stored in another way. AND you may load them by shell ... if you know the commands ... (i don't!) :-)
and so on ...
found something here about your drive (you two have the same model??):
//I've already seen that some 6Gbps SATA controller and 3Gbps disk misnegotiated on 1.5Gbps until controller was strictly limited to 3Gbps.//
last sentence here!
//The ST2000DL003 also has a four item "installation summary" on its sticker. The wording is nearly identical to the ST31000340AS except that it's missing the sentence "If the drive is not detected, check the 1.5GB jumper" and there's a blank area where Seagate used to have the image of the jumper block. The drive has a jumper block with no jumpers installed. The manual claims this drive can auto-negotiate to 1.5 Gb/s. //
So probably you have a faulty controller? Do you have any "other" controller on your board? JMICRON or something? The ports are usually colored in another color than your main ports. Try to connect the HDD there and try again.
Which firmware is on your HDD? I googled around and heard / read about a firmware bug, which could render the drive useless. It does not get detected in BIOS then ... Probably your errors are warnings like "HEY, DO STH. OR I WILL QUIT FOREVER!" ...
No offense here, but if you want to set up a RAID1 with only 2 HDDs, why don't you go to disk management and setup the two disks as dynamic partitions / mirror set. That would be software RAID1, but the impact on speed versus the onboard "pseudo-hardware-RAID"-controller is minimal til "not measureable". That would ensure, if your board gets broken somehow, you don't depend on the onboard chipset and could use (for example) an AMD chipset and RAID would still be there. I would not say those onboard-RAID-controllers are bad, but if hardware breaks, you have to have another board with the same chipset and stuff to get your RAID back. But with RAID1, that isn't a big problem anyways. :-P
Zitat von Fernando im Beitrag #2
I doubt, that it will work with Intel's .BIO files.
It is NOT for the BIOS files themself, it is for modding the onboard-present BIOS. I did some SLIC modding (I think you know what I mean) in the past with my board (it is genuine Intel) and I found out, there are indeed no tools to mod the BIO files in any way, but the SLIC tool i had (i know where it is offered to D/L if you are interested) inserted the SLIC directly into my onboard BIOS without any flashing required. I still wonder how that is possible, but i reinstalled windows a few times and code stayed there, so it HAS to be permanent. :-)
Would you mind an exchange of knowledge? ;-)
Greetings from a place not far away from you. :-P
Zitat von gpvecchi im Beitrag #45
I did it just now: nothing. It seems that my motherboards completely removes post screen if CSM is disabled; well, this doesn't bother me, it is simply a silly thing, if I want to access bios to overclock, in example...
Hi there. :-)
I have the same thing going on with my PC, but my board is another one (Intel DX79TO). In my BIOS it is written, to get into BIOS again you have to power down the system, wait a few seconds, then press AND HOLD (!!) the power button, until a sequence of beeps appear. Then release the button and wait, until the system presents you the option menu. Select the "Enter BIOS"-option and that's it.
Probably this helps you with your board. Probably it's some new UEFI standard or sth. like that. This does not work with my "Pentium II" with 350MHz. ;-)
EDIT: Did you look in your manual from your motherboard? I know, this is the last advice you want to hear, but this option is written in my manual, too. And I did NOT read it before, too. :-P