Search options (Page 10 of 64)

Hello, and welcome to the DriverPacks forum.     

Note that the Intel RST driver you attempted to slipstream requires Windows Server 2008 minimum.  That is, it is not meant for NT5.
Please post your HWID for that controller.  The error you may have seen in that build may have been something like "iStor is corrupted".

Perhaps integrate a newer "nightly" build of DP_MS (Note that contrary to the first post in this topic the changelog in the pack is up-to-date.  Do read the "Known Issues" in the changelog.)  You should only require the main pack, and not the 3rd-party intelide-pciide packs linked in that reply.

Also, some brief info on how you created your build may be helpful ( incl. media/ROMdrive type).  Note that we only support integration via DP_BASE.  There are some wonderful tutorials around here &/or the main site.

We appreciate feedback.  Help us to help you and others too!

I'll upload & post link for that & other missing 3rd-party packs when i can.
Thanks, cheche!

Be careful what you wish for, Outbreaker!
  The hunter may become the prey.

  Wireless Routers can also be affected by the OpenSSL bug "HeartBleed".  Presumably, that would include routers with firmware built between early 2012 and April 7th, 2014.

This also includes software that utilizes OpenSSL in a Windows environment, even though Windows itself is not specifically indicated as vulnerable to this bug.

Add this to the WPA2 vulnerability, and that 11 on a ten-scale may in-effect actually be somewhere around an 18 on a ten-scale!
  Of course, that is only in light of these two specific recent revelations and cannot include that which we are not yet aware of.

It also highlights how the assumption that open source makes such bugs unlikely in the long term is not necessarily true.
  One does wonder how many bugs remain unofficially discovered or patched where Security By Obscurity prevails.

There may yet be another small set of updates officially released by Microsoft for NT5 in the near future.
  That dealing with updated Certificates, as well as the many that have and will soon be Revoked.
    Wondering if this is at least one reason the March 2014 Certificates update was yarded by MS.  (don't know if NT6 update pulled too)

I wonder if Deutsche Bank properly fixed this yet, which allegedly is still using their old certificate.     
  Business should be booming now for Certificate Authorities, yet one wonders how proactive they all were.
    A chain will eventually break at it's weakest link if overloaded.

I see now how dencorso gauged success in his post.  It installed OK.  That doesn't necessarily mean that it didn't have the same (Code 10) problem.

Unfortunately, it would seem that there is little hope that this driver can be made to work for that hardware then.

There are some possibilities that remain.
   1.  One would be that there might be some registry entries missing, or other differences between the NT5 driver and that for Win7/8.x
   2.  Another could be that somewhere in the files that these drivers are referencing are tied to specific HardwareID's (HWID's).
   3.  It is also possible that there are distinct hardware differences between the officially supported Haswell Graphics Adapters and the ones included in my modified .Inf file.  Perhaps a newer stepping or revision?

It is most likely that only possibility 1 can be implemented in these driver packs, as possibility 2 would likely violate Intel's Terms in the license.  Possibility 3 would make any mod next to impossible, other than for Intel themselves.  Also, we don't use modified executables as a matter of firmly established policy.  Only modified .Inf files are permitted for inclusion in the DriverPacks.

erkange, please post a link to the post above over at MSFN for their usage.

  I will update the test pack later to include the experimental 5445 version.
    It must be removed from the DP_Graphics_B package, even though the other HWID's included in the mod have not yet been tested as far as i know.  5449 will be a little tricky to add yet not impossible, as it is not WHQL'ed & shares HWID's with Gen3.

If or when you have some spare time, i would be grateful if you would agree to test our AHCI driver mod for that chipset.
  Anybody that contributes to solutions will be credited in changelogs.

Did the HD Audio mod also install with a (Code 10)?

I compared those files (igcodeckrng700.bin, igvpkrng700.bin, igcodeckrng750.bin and igvpkrng750.bin) utilizing Nir Sofer's HashMyFiles.
  They are bit-identical in all three packages (5441, 5445, 5449).

Perhaps dencorso could enlighten us as to how success was acheived with that method, and what his graphics adapter Hardware ID (HWID) is.
  I am not a member of MSFN, so am not able to ask there.

Here is the test pack which includes mods for 5441 & 5449 -->  DP_HaswellTest.7z
  It is meant for manual installation via Device Manager.
Start - Run - devmgmt.msc - Display adapters - Intel VGA - Driver tab - Update Driver - No, not this time - Install from a list - Don't search. - have disk
    Also included is the mod for HDMI Audio.

If you require the mod for 5445, it is included in DP_Graphics_B_wnt5_x86-32_1401181.7z, available several posts above in the D\G\I\1 folder.

None of these modified drivers are WHQL'ed, so you will see a warning message about the drivers not being certified during installation.
  Please let us know if it works or not.

No need to apologize, your english is good.

Are you certain you have both 5441 and 5449 packages?
  The download link from Intel is the same for both packages, therefore the older package is no longer available via Intel.
    Check igxp32.inf, it should read DriverVer=03/10/2013, 6.14.10.5441.
      The newer package reads DriverVer=01/30/2014,6.14.10.5449 on line 27 of that file.

I do understand what was advised by dencorso.
  Have you a fresh install of XP on a test machine?
    I will post a package for testing as soon as i can.

Mar. 8, 1987 - Western Washington University http://gallifreybase.com/w/index.php/Li … ted_States
Karen Gillian had not yet been born.

Don't feel so put out.
  I had to wait over 16 years for the new series after meeting Colin Baker at a convention premiering "Trial of a Time Lord".
    Still wish i had retained that signed copy of "Caves of Androzani".
So nice to see Tom Baker reprise the role during the 50th anniversary show sans scarf, even briefly.
     "Never touch ... never trust gimmicky gadgets." - 4th Doctor
Wish they would film an episode or two here in Canada.

Thank you, sir.  I will ensure any comparisons are fair and balanced, with respect to the fact that both are freeware and much volunteer person-hours (years) have gone into their respective creation.  Notes will be taken to be shared at a later date, privately first - then publicly, if agreed at that time.

With respect to OverFlow, try https://web.archive.org/web/20121120174 … .com/forum

          Quote:  "There's no reason to have a plan B because it distracts from plan A." - Will Smith     

For load-testing a CR2032, I use a WiFi finder that uses one such cell.  There are some LED flashlights that use such batteries, too.
  Note that some laptop BIOS batteries use a different prefix such as VR that indicates a rechargable lithium cell.

That is very quotable too!     

Noting what i hope is the manual for that A8N32-SLI Deluxe board (that was a Deluxe, was it not?).
     http://dlcdnet.asus.com/pub/ASUS/mb/soc … LI_Dlx.pdf
  If it was the Deluxe as i suspect, then you likely had not done any pencil mod to it since that would have been unnecessary.

For the nVidia RAID, (quote from manual) "during POST, press <F10> to display the main menu of the utility."  Odd, i would have thought that would be <Ctrl+N>.
  For the Silicon Image 3132 controller, (quote) "during POST, press <Ctrl+S> or <F4>".
    It would seem that one should ensure the configuration is recognized on the controller it was originally installed upon.

  Noting that whatever packs you used for your original installation are the revisions you should probably use for data recovery. 

Be data safe!

It may have been some time, yet try to remember what you did then.  Did you "Load the Optimized Defaults" then?

Also noting that a linux-Live disc might assist in data recovery.
  Note that some RAID arrays may not be recognized or display properly by linux, so if so that is no indication that your array is pooched.  It might be an alternate way to access the data though.  Probably not good to write anything to the array, as it could conceivably corrupt it.

When you have finally solved this puzzle, you might be amazed to note (as i was) that Fernando uncovered that it is possible to use a much later nVidia RAID BIOS v10.0.0.35.

  Of course, this entails modifying the BIOS and flashing the mod.  Not for the faint of heart, or those not prepared to recover from a bad flash or bad mod.  Socketed flash chips can be backed up with a "hot flash".

I only mention these things to expand upon possibilities, not as suggested courses of action.

I look forward to learning from you, as it sounds like you have much to teach.

[Off-Topic]
Oh, the Rock Opera; that was "Tommy".  OK, perhaps this should never be mentioned in any, even abject, comparison with Guilbert & Sullivan.  Live and learn.

    Sadly, my only exposure to Gilbert & Sullivan's H.M.S. Pinafore was in Star Trek: Insurrection (so far).   If you like that science fiction genre too, the following may interest you.  http://www.stanford.edu/group/savoyards … n/node/115
    The opening plot of H.M.S. Pinafore vaguely sounds like the love story from "Titanic".  Was that one source of David Cameron's inspiration (i wonder aloud)?
[/Off-Topic]

Thank you Shane, for the update.

Noting that OEM names being truncated like that is fairly minor.
  I wonder what those "other places" are, though.