751

(11 replies, posted in Windows 7 Discussion)

You are very welcome.

PS:  Did the link above your last post to the most up-to-date drivers yield working drivers for Win2k8 ?
       I am unable to download it to confirm.  All i see from the "intel.downloadmirror" is the message "Service Unavailable".  If you see the same message, perhaps it would be best to try again later.

752

(11 replies, posted in Windows 7 Discussion)

Please post some information in the relevant "Vista/7 LAN" section in a new topics such as:

[REQ] LAN - Intel 82579V Gigabit Network Connection

This way, whomever works on the Vista/7 (etc) LAN packs can impliment a solution.

Thank you for sharing this information.  smile

PS:  see http://downloadcenter.intel.com/Detail_ … pkw=82579v  big_smile

753

(11 replies, posted in Windows 7 Discussion)

Once again, a search of PCIDEVS.txt within Ray Hinchcliffe's SIV & Halfdone Development's UnKnownDevices returns:

82579V Gigabit Network Connection

754

(11 replies, posted in Windows 7 Discussion)

That is not a LAN device, AFIK.
sorry, i updated my previous post before realizing that you had responded.

755

(11 replies, posted in Windows 7 Discussion)

Using rh-software's SIV or the UKD utility, linked below, the following adapter is demystified:

0BDA:0129=Realtek USB 2.0 Card Reader

It does not exist in the 3rd-Party CardReader DriverPack, yet.

After you find your driver on Realtek.com.tw, please post a link in a new topic in the "3rd Party Vista/7 DriverPacks" group with a title like this:

[REQ] CardReaders x86 x64 - Realtek

This way whomever works on that pack can easily add that driver(s).

One might want to be careful if that's sensitive data being plugged in.  Just in case.
http://www.theregister.co.uk/2012/12/12/smart_tv_pwned/

OverFlow wrote:

"I could have made the same argument for video cards... if a video card has an issue it can make anything happen, including cause your floppy to fail. A bad video card can make it "anything can happen day". I have fixed some VERY obscure issues by swapping out the video card... believe it or don't."

I'm there now.  I haven't refurbed this system for over a year; Maintenance overdue.  Same with my refurbed P/S; it could use some upgrades internally.

2 P/S', now 3 in a row; ordinarily wouldn't one say that if the floppies work on other systems that it would have to be one of Mobo, P/S, or cable, possibly damage on or to the mainboard.  Video seemed too far upstream. If supported, one could use a 8M (or is it less?)  PCI Video card for testing puposes (decade+ old-school).  That BIOS battery has the most favorable risk/reward ratio (reset load Optimized BIOS defaults imm. after).

Manually update the driver in Windows Device Manager
(Update Driver - Install from Disk - Don't Search - Have Disk).
  Ensure any important data is backed up first.
Restart Windows.

If that doesn't work, uninstall that driver using Add/Remove Programs.
Manually try the drivers (Device Manager)one at a time in DP_SoundB_wnt5_x86-32_1111\D\S\I or I8, Im, In, or Ip.

Texas Instruments USB3 xHCI Host Controller/Hub

updated to {DriverVer=11/26/2012, 1.16.2.0} WHQL'ed for Vista & Win7 (x86 & x64)
here --> http://www.ti.com/lit/sw/sllc423d/sllc423d.zip  big_smile

Texas Instruments USB3 xHCI Host Controller/Hub

updated to {DriverVer=11/26/2012, 1.16.2.0} WHQL'ed for XP, & 2k3
here --> http://www.ti.com/lit/sw/sllc423d/sllc423d.zip  big_smile

edit:  note that an updated driver is now in DP_MassStorage.

Any progress?  We have not forgotten about you.  I vow to keep my replies short, if you want.

Sadly, i have been remiss in my duties, though.  An updated link was posted for the "nV test pack".

mr_smartepants wrote:

"We should be pointing nvidia users to this thread and when they find a DriverPack MassStorage test pack that works on their system, use that instead of the main pack for that one system."

Beware, there are 18 of them.  Start with #13 & #14.  Those do contain your RAID's HWid's, unlike the others.

Please reply with your machine's preference.  That might end up in the main pack.

761

(12 replies, posted in Other)

China may have their own ""Chappa'ai" soon.
http://www.pakalertpress.com/2012/12/02 … ding-here/
Sorry about the link, just replace the "*" in the word h*ll. roll

"Indeed, O'Niel."

I did something similar to the MassStorage.ini modification and resulted with the same textmode pre-partitioning "iastorA.sys could not be found".  Ref. http://forum.driverpacks.net/viewtopic. … 149#p50149
The funny thing is that now that xp textmode is referenced in MS.ini, the iastorA.sy_ compressed file was included this time in i386.

Mind you, this test was on an abortive install attempt on intel hardware much more aged.

Here's my [I4] section:

[I4]
; 3.2.0.1126 
ms_count=2
ms_1_deviceName="Intel C600 SATA AHCI-RAID RST Enterprise"
ms_1_tag="iaStorA"
ms_1_sysFile="iaStorA.sys"
ms_1_hwids="PCI\VEN_8086&DEV_2826&CC_0104,PCI\VEN_8086&DEV_1D02&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k"
;
ms_2_deviceName="Intel C600 SATA RAID RST Enterprise"
ms_2_tag="iaStorS"
ms_2_sysFile="iaStorS.sys"
ms_2_hwids="PCI\VEN_8086&DEV_1D60,PCI\VEN_8086&DEV_1D61,PCI\VEN_8086&DEV_1D64,PCI\VEN_8086&DEV_1D65,PCI\VEN_8086&DEV_1D68,PCI\VEN_8086&DEV_1D69,PCI\VEN_8086&DEV_1D6A,PCI\VEN_8086&DEV_1D6B"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k"

  After renaming the iastorA.sys executable to .sys.exe, i used Silurian Software's InspectExe to look at the list of Imports for the file itself which revealed a dependancy on ntoskrnl.exe's RtlGetVersion function.

Apparently, that is an OS version check.
  Long story short, it doesn't seem to like XP, yet apparently works great on 2k3 for at least one member.
  Ref. http://forum.driverpacks.net/viewtopic.php?id=5883

It does appear that this issue has been ongoing.
  http://forum.driverpacks.net/viewtopic.php?id=5960   http://forum.driverpacks.net/viewtopic.php?id=6051

I'm inclined to restrict this section once again to 2k3 & simply add the driver referenced much earlier in this topic by Caleb37.  I did find two seperate OEM links from ASUS for the same RSTe driver which included an RST folder.

  One has to wonder what effect that would wreak upon 2k3 users, though.  hmm

Efforting....to wait for a response or three.  Please hold.

Here is an excerpt from the release notes for RSTe_Drivers_GUI_CIM_CLI_3.5.1.1009_2012.10.08.zip
which updates "I4".

"==========================
Supported RAID Controllers
==========================
This download provides support for the Intel(R) C600/C222/C224/C226 chipsets on both AHCI Capable SATA Controller and SATA/SAS Capable Controller in Intel(R) Rapid Storage Technology Enterprise (RSTe) mode. 
 
Please verify that this package has been tested with the RAID device you have chosen to use by checking the drivers web page for your controller 
at [url]http://support.intel.com[/url].

===================
Package Information
===================
Package Version = 3.5.1.1009
The iaStorA driver version is 3.5.1.1008
The iaStorS driver version is 3.5.1.1008
The iaStorA Win8/Win2012 driver version is 3.5.1.1008
The iaStorS Win8/Win2012 driver version is 3.5.1.1008
OS supported = Microsoft* Windows 2012 (x64), Windows 8 (x86 & x64), Windows 2008R2 (x64), Windows 7 (x86 & x64), Windows 2008 (x86 & x64),
                          Windows Vista (x86 & x64), Windows 2003 R2SP2 (x86 & x64)

==========
Attention!
==========
This release resolves Standby Immediate issue with SSD's.

==================
Known Restrictions
==================
1. SAS features are enabled on SATA/SAS Capable Controller if appropriate Intel(R) RAID C600 Upgrade Key is present in the system.
2. RAID 5 is no longer supported by SATA/SAS Capable Controller when SAS features are enabled.
3. Boot through expander is not supported in legacy mode at this time.
4. MPIO Load Balancing in RAID Mode is unsupported
5. A SAS Wide port spanning SCU0 and SCU1 is not supported.
6. Plugging both SCU into the same expander is not supported
7. Some WD 6G SAS drives (S25/S35 family) are not supported
8. POST messages are displayed only if more than one drive is attached.
9. Performing a RAID Migration/Rebuild may not result in all of the appropriate LEDs blinking correctly.
10. A manual verify/repair may be required after an unexpected shutdown with running heavy I/O on a RAID volume.
11. RAID volume names should be less than 16 characters."

Quoted from:  http://downloadmirror.intel.com/21752/e … readme.txt

In addition:

It would appear that DP_MassStorage_wnt5_x86-32_1209\D\M\L
   does not actually conflict with VEN_8086&DEV_2826&SUBSYS_84EF1043
as that specific HWid is not present in MegaSR.inf.

Not even with the updated files in DP_MassStorage_wnt5_x86-32_1212b2
(under constuction - MegaSR now WHQL'ed for 2k3, XP-OK though non-WHQL'ed;
      DriverVer=08/11/2012,15.00.0811.2012).

"==================
Known Restrictions
==================
1. Intel(R) ESRT2 based on Intel(R) C600 chipset does not support UEFI functionality. A UEFI driver is planned/expected to be made available post-launch, but there will be no GUI available in UEFI for configuring arrays.

2. The on-board SATA/SAS Capable Controller does not support ODD devices.No Optical Devices should be connected to the SATA/SAS controller at any time (ODD devices are not supported in any mode), but the onboard AHCI capable ports do support ODD devices (in all modes).

3. RAID 5 feature is enabled only if the appropriate Intel(R) RAID C600 Upgrade Key is present in the system. 

4. A RAID 5 logical drive can recover from a single drive failure by reconstructing missing data from the data and parity contained on the remaining drives. The assumption underlying this ability is that the data in the remaining drives is consistent. This assumption becomes invalid if there is a power loss during write operation(s). If there is a loss of power during a write operation, data inconsistencies may occur because data and parity writes may have completed only partially. After subsequent reboot the logical drive has inconsistent data on that particular stripe. If a drive were to fail at this point, missing data (for the inconsistent stripe alone) cannot be reconstructed from remaining drives. To correct an inconsistency, the drivers starts a back ground initialization (BGI) at reboot. While BGI is in progress, the inconsistent stripe(s) are vulnerable to drive failure. One way to avoid this window of vulnerability is to run check consistency on the logical drive using the BIOS utility. Another way is to prevent an unplanned shutdown (e.g. using UPS).

5. The LITE-ON SH S752K model CD/DVD ROM device does not respond to 0x55 & 0x51 MMC commands properly. The device hangs when these commands are issued multiple times. The driver resets the device when it hangs; but the reset adversely affects DVD burning. This behavior can be consistently observed using K3B DVD burning software. K3B aborts DVD writes when 0x55 is failed and device is reset.

6. RAID 5, by its very nature, cannot tolerate double failures. The double failure can be a combination of a single drive failure and either additional drive failures or an unplanned power failure in the RAID system. Unplanned power failures can include but be not limited to, loss of power source or an unusual system shutdown. Unplanned power failures while there are medium errors on the drives is also considered as a double failure condition.

7. Multiple drive failures would result in a data loss condition. A single drive failure combined with any additional unplanned failure can cause loss of data integrity. To avoid loss of data integrity for the power failure case, it is highly recommended to provide an uninterrupted power supply to the server to protect the RAID 5 subsystem during the event of a degraded or rebuilding state. Medium errors on the disks, combined with an unplanned power failure can also cause loss of data integrity, but this occurrence would be very unlikely.

8. Hotplug limitation in runtime 
If the user pulls out or plugs in a drive when the Intel(R) ESRT2 OpROM has completed its execution, and before the OS driver is loaded (like DOS shell, or AHCI?Ctrl-M screen, etc), the OpROM's runtime code displays a message and force reboot the system to avoid configuration losses or data corruption. 

9. Maximum two storage controllers supported 
If the user tries to enable SATA/SAS Capable Controller and AHCI Capable SATA Controller in Intel(R) ESRT2 mode concurrently, and then inserts any external storage controller (for example, a Hardware RAID adapter), the last controller in the boot sequence might not be able to POST. 

10. Windows installation limitation in RAID Mode: 
If Windows installation is done on a drive connected through the AHCI capable SATA Controller, make sure SATA/SAS Capable Controller is disabled in BIOS. After completion of installation, the SATA/SAS Capable Controller can be enabled in BIOS. If both controllers are enabled in Intel(R) ESRT2 mode, the installation may fail.

11. BIOS communicates the presence/absence of specific Intel(R) RAID C600 Upgrade key (RKSATA4R5, RKSATA8R5, RKSAS4R5 and RKSAS8R5) using configuration data on disk (DDF) and through device registers from BIOS. If driver does not read a valid DDF, it will disable R5 creation. The driver may not see valid DDF if (A) user does not configure using BIOS Ctrl+M; or (B) if no drives were present at the boot time and all the drives were hot-inserted after OS is booted. In both cases, the user must create an initial configuration using BIOS Ctrl+M utility."

Quoted from http://downloadmirror.intel.com/20963/e … Readme.TXT
I only posted that to aid my wondering if the ven_8086&dev_2826&cc_0104 hardware/drivers have similar limitations.
If i see similar notes for that, i will post it.

The driver in I4 is restricted in MS.ini to 2k3 only.  Is that the real issue?
Would unrestricting XP textmode for that driver be another solution, despite being an RSTe driver?
ASUS does claim that your hardware is designed to be able to run RSTe (and RST as you have noted).

I will proceed based upon that deduction.

It would be interesting to see if the "BIOS" does indeed contrain the necessary modules and versions of modules to properly support this, as noted by Fernando.

New uEFI BIOS released by ASUS yesterday for P9x79 Deluxe.
  http://www.asus.com/Motherboards/Intel_ … /#download

  Fernando has some interesting things posted concerning firmware.
http://www.win-lite.de/wbb/board208-spe … extracted/

Fernando wrote:

"Users with an Intel C600 (e.g. X79) Series SATA RAID Controller will get TRIM into their SSD RAID0, if they are able to use an actual Intel RST driver(s)/RAID ROM combination v11.x.x.xxxx (precondition: the mainboard manufacturer offers a BIOS containing such Intel RAID ROM version)."
  Quoted from: http://www.station-drivers.com/forum/vi … =74#p16818

I acknowledge that this is going on a bit of a tangent, so if neither is relevant then please disregard.
I'm not advising "modding" your uEFI BIOS.  Posted to inform, not as advice.

Whoops; i missed your comments OverFlow.

"IDK why you were not immediately pointed to this thread..."

That was "my bad".

I can see your former rant in the context of an IT person under stress.  No harm; no foul.
You are correct that i wasn't helpful in assisting you to create a speciallized pack.
My time and resources, like the DriverPacks, are being stretched thin.

I venture to add support to the main NT5 MassStorage pack.  That is my focus, and rightfully so.
  Does there exist any interest?

A contribution to the forum would be welcome, if it pleases you.  This does not need to necessarily be a financial contribution.
The moderators here know what it is that is needed.

we work with OEM links here only.  station-drivers.com, Fernando"EsNumeroUno", MSFN.org, and win-lite.de are good guys too, yet we have an audience to consider and therefore will not use them other than to guide research.
http://driverpacks.net/well-known-users

D'oh!  BIOS battery is a distinct possibility, considering it's age.

I thank you for your clarity.  It would appear that i've only updated the RST C600 series AHCI drivers for Win2k3.

As for including Fernando 1's work; that can only be done with his expressed permit, including the approval of the DriverPacks moderators.  I would do no less than to credit him in any relevant changelog, as well as in this Forum.

Can you post an OEM link to the "iastor" driver in question?

5-year warranty on P/S?

However; the motherboard could be the "weak link", as warranty is limited to 3 years.  Probably easiest to check the mobo for any sign of leaking or bulged capacitors.

I calculate from your listed power-on usage, a total "ballpark" figure of 23400 hours.
Assuming that the capacitors were originally meant for 2000 hours @ 105°C, this would work out to approximately 32000 hours @ 65°C.  If the power fluctuates in the building it is in, that figure would be reduced.

I would guess that you could have a year of usage left in it, yet i am uncertain.  I lack much information specific to your computer's issues.  The brand and series of capacitor will effect those calculations also.  Bear in mind that electrolytic capacitors can fail without any outward sign, although nowhere nearly as common.  Damaged components usually are found nearest the most significant thermal-zones.  A non-contact infrared thermometer has been a guide to me for finding how bad a thermal zone can get.  I do this during a "memtest" to evaluate a "close-to" worst-case scenario.

Back to BIOS; if the system exhibits "instabilities" or "failure", that is not a good circumstance to update the BIOS.  Call it a "last-resort", perhaps, on a setup with a minimum of components?

  Using SLI?  If so, use a low-powered card of the same chipmaker (optional) for testing.

PS:  Looking at the comments on newegg concerning that BFG (defunct?) P/S, of those whom have experienced failure, a large percentage have experienced catastrophic failure, at least according to their claims.

PPS:  That "claim" of 1000 Watts could be another example of corporate "free-speech".  Think of how HDD/SDD/etc. manufacturers henke with their math in defining a "Gigabyte", or a "Terabyte".   1000 Watts may have been a theoretical maximum, not a real-world maximum.

saynotobfg wrote:

"Power supply internals are GARBAGE, may explode if pushed
Won't put out anywhere near 1000w
probably 1000 PEAK... and that is a stretch"
Quoted from:  http://www.newegg.com/Product/Product.a … llFullInfo

This does seem like an extreme opinion ordinarily disregarded.  It would be interesting to see some high-res pictures of the internals on that puppy to confirm or deny.

Don't go opening it if you are not familliar with the risks and how to alleviate those risks.

To me, "modular" can equal "voltage drop".  Avoid use of these connectors if the ends become discolored.

"however, this doesn't work when you choose TEXTMODE through nLite after trying to install DP's."

True, this is not a good way to go, it will corrupt your source.

To debug your installation, restrict your drivers to Chipset & MassStorage.
I like avoiding integrating WLAN to avoid "chatty" hardware, but that's just me being moi.
I use RVMi to integrate updates, addons, & & DP_BASE to integrate drivers, as recommended by the moderators here.  I build my Iso's with IMGburn (i have to install it with internet disabled to prevent Ask toolbar from resolving my geographical location, even before displaying an EULA).
nLite should be ok to build & burn, yet that software is no longer supported by it's author (nor DriverPacks, iirc).

"  It should be OK to run HWid's in another Windows operating system (temporary install).
Simply ensure that HWid's is run with the drive(s) set up as RAID0."

I need some HWid's to guide me.  Odds are, the newer drivers are already included in the latest betas of DP_Chipset & DP_MassStorage.

I assume that both connector-ends are indeed polarized.  That is to say, they only fit on one way, with pin1 matching the marked end.

tattooed_pariah wrote:

"All the pins are straight, this ribbon cable only has two connectors, one on either end. If I boot off the Support CD it will format a floppy for the F6 RAID drivers."

  That seems to imply that the floppy is at least powered; so much for me thinking that one end may be backwards.  One thing about those cables;  there are a few lines that are reversed close to one end.  That is the end that should go to the floppy drive.  What does ScanDisk make of the finished disk?  Does it find bad sectors?  Can you update it with files from D\M\N5?

  You said that you have the latest BIOS update installed, if i remember correctly.
Beware as improperly applied BIOS updates can "brick" your board!
It could be that the drivers on the SupportCD are not compatible with the latest MediaShield RAID BIOS (should be included in the Motherboard's BIOS).

"I'd like to think it's good"

  If the power supply has more than 2000 total hours on it shine a flashlight in to the case of the P/S to see if you can see any capacitors bulged on the top, especially closest to the mobo cables.  The mobo though, if older than the P/S, would be more likely to have these.

  For examples of what you are looking for, see:  http://www.badcaps.net/pages.php?vid=5
  I'm not saying that this is your issue, i only mention it as a possibility.  If you had an audio amplifier with a malfunctioning power supply, you wouldn't expect it to sound well.  Likewise, a computer powersupply can cause instabilities that can be difficult to predict.

It is all a process of elimination, including Sherlock Holmes' "deductive reasoning".
That is, using known good hardware to diagnose &/or debug unknown hardware.
Get that "Moriarty" Focker!  You are a Pariah here, only in name.

Thank you for joining the forum, Caleb37smile

  The latest MassStorage DriverPack is still in beta.

  In the mean-time, could you please post your HWid's (linked in my signature below) so that it may be verified that x79 support is included.
  It should be OK to run HWid's in another Windows operating system (temporary install).
Simply ensure that HWid's is run with the drive(s) set up as RAID0.

  Does the system's manufacturer not have a page listing drivers, especially an "F6-floppy" disk?  Are you installing through USB by any chance?

Aha, i was wrong.  Your RAID driver is probably in
DP_MassStorage_wnt5_x86-32_1209\D\M\N5

Thanks, mr 'pants!

from MassStorage.ini:
[N5]
; From nForce 15.26 DriverVer=11/12/2008,10.3.0.46
ms_count=1
ms_1_deviceName="NVIDIA nForce 630 SATA/RAID"
ms_1_tag="nvgts6r"
ms_1_sysFile="nvgts6r.sys"
ms_1_hwids="PCI\VEN_10DE&DEV_0558,PCI\VEN_10DE&DEV_0559,PCI\VEN_10DE&DEV_055A"
ms_1_isBusExtender=true
ms_1_exc_disableIfOS="w2k"

No dice so far for the other controller.  hmm