Search options (Page 27 of 64)

I see that his RAID utility version may give a clue as to what will be successful.
Here is a driver from ASUS's relevant support page --> http://dlcdnet.asus.com/pub/ASUS/mb/soc … _32bit.zip
I have rolled the intel textmode driver back to v5.5.0.1035 for that HWID,
    here --> http://www.mediafire.com/file/hj3u8msor … 1303201.7z

Bear in mind that Voltage is not a reliable indicator of battery health.  I've seen many a coin cell that registered proper Voltage, yet had not the Current capacity sufficient to light even an LED.

Also, hardware from this era can be susceptible to "Capacitor Plague" and other phenomenon.

Ensure the hardware is properly cleaned whilst observing static-control measures.

  Also, best to test with a known-good power supply.
  You may have no idea what little "chamber of horrors" these devices can represent.
  If your P/S has an Aluminum housing, consider tossing it.  That's not fire-rated, AFIK.

I am not saying that it is simply a hardware issue, i only seek to help you rule that out.

  For instance:  I have two identical ICH5R ASUS mobo's.
        One will allow me to install to a RAID array, the other, no.
            Using the same testing platform allowed me to prove that the other had indeed a hardware issue.

Also, use a disc to test, not a USB stick.  Disconnect any and all non-essential peripherals including USB hubs, CardReaders, etc.  (from your HWID's in first post)

oh crud.  If you do replace the [ i] & [i2] sections, delete the space before the i.  I've corrected that above.

After you've taken care of your data, that is.  Please indicate later if it works for you.  I'll post a nightly.

edit:  and here it is -->  *edit:  link removed*

To test a theory, delete ich6id2.inf from your pebuilder plugins\DriverPacks.net folder before building.

Ah, that is something would require "shoehorning" in.  The driver is mentioned in the other post.

Another thought is using v5.5.0.1035 for textmode.  How many ports does that have?

What OS are you basing your BartPE off of?
Oh, that's UBCD4Win?

Also, note what i mentioned in my other reply for PE today.  CR2032's only last a few years or so, depending on grade.

Here's a test MassStorage.ini:
Extract the RC MassStorage to a folder & replace the [ I] & [I2} sections in the ini with the following & then archive it to 7z with 7zip (settings - 7z,Ultra,LZMA,32MB,256,512MB,2) & rebuild your disc:

[i]
; 5.5.0.1035
ms_count=2
ms_1_deviceName="Intel 82801ER/6300ESB SATA-RAID 5.5"
ms_1_tag="iastor1"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24DF&CC_0104,PCI\VEN_8086&DEV_25B0&CC_0104,PCI\VEN_8086&DEV_2652&CC_0104,PCI\VEN_8086&DEV_2652&CC_0106"
ms_1_isBusExtender=false
; ms_1_exc_disableIfOS="w2k"

;Intel ICP Vortex SCSI RAID
ms_2_deviceName="Intel ICP Vortex SCSI-RAID"
ms_2_tag="raidsrc"
ms_2_sysFile="raidsrc.sys"
ms_2_hwids="PCI\VEN_1119&DEV_0000,PCI\VEN_1119&DEV_0001,PCI\VEN_1119&DEV_0002,PCI\VEN_1119&DEV_0003,PCI\VEN_1119&DEV_0004,PCI\VEN_1119&DEV_0005,PCI\VEN_1119&DEV_0006,PCI\VEN_1119&DEV_0007,PCI\VEN_1119&DEV_0008,PCI\VEN_1119&DEV_0009,PCI\VEN_1119&DEV_000A,PCI\VEN_1119&DEV_000B,PCI\VEN_1119&DEV_000C,PCI\VEN_1119&DEV_000D,PCI\VEN_1119&DEV_0100,PCI\VEN_1119&DEV_0101,PCI\VEN_1119&DEV_0102,PCI\VEN_1119&DEV_0103,PCI\VEN_1119&DEV_0104,PCI\VEN_1119&DEV_0105,PCI\VEN_1119&DEV_0110,PCI\VEN_1119&DEV_0111,PCI\VEN_1119&DEV_0112,PCI\VEN_1119&DEV_0113,PCI\VEN_1119&DEV_0114,PCI\VEN_1119&DEV_0115,PCI\VEN_1119&DEV_0118,PCI\VEN_1119&DEV_0119,PCI\VEN_1119&DEV_011A,PCI\VEN_1119&DEV_011B,PCI\VEN_1119&DEV_0136,PCI\VEN_1119&DEV_0137,PCI\VEN_1119&DEV_0138,PCI\VEN_1119&DEV_0139,PCI\VEN_1119&DEV_013A,PCI\VEN_1119&DEV_013B,PCI\VEN_1119&DEV_013C,PCI\VEN_1119&DEV_013D,PCI\VEN_1119&DEV_013E,PCI\VEN_1119&DEV_013F,PCI\VEN_1119&DEV_0166,PCI\VEN_1119&DEV_0167,PCI\VEN_1119&DEV_0168,PCI\VEN_1119&DEV_0169,PCI\VEN_1119&DEV_016A,PCI\VEN_1119&DEV_016B,PCI\VEN_1119&DEV_016C,PCI\VEN_1119&DEV_016D,PCI\VEN_1119&DEV_016E,PCI\VEN_1119&DEV_016F,PCI\VEN_1119&DEV_01D6,PCI\VEN_1119&DEV_01D7,PCI\VEN_1119&DEV_01F6,PCI\VEN_1119&DEV_01F7,PCI\VEN_1119&DEV_01FC,PCI\VEN_1119&DEV_01FD,PCI\VEN_1119&DEV_01FE,PCI\VEN_1119&DEV_01FF,PCI\VEN_1119&DEV_0210,PCI\VEN_1119&DEV_0211,PCI\VEN_1119&DEV_0260,PCI\VEN_1119&DEV_0261,PCI\VEN_1119&DEV_02F6,PCI\VEN_1119&DEV_0300,PCI\VEN_8086&DEV_0600,PCI\VEN_8086&DEV_0601"
ms_2_isBusExtender=false
ms_2_exc_disableIfOS="w2k"

[I2]
; 7.0.0.1020
ms_count=1
ms_1_deviceName="Intel ESB/ESB2/ICH6/ICH7 SATA-AHCI/RAID 7.0"
ms_1_tag="iastor2"
ms_1_sysFile="iastor.sys"
ms_1_hwids="PCI\VEN_8086&DEV_24D1&CC_0106,PCI\VEN_8086&DEV_2651&CC_0106,PCI\VEN_8086&DEV_2653&CC_0106"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

Have you seen the comet?   http://apod.nasa.gov/apod/ap130318.html

...updated Asmedia USB3, and intel Centeron null-drivers.

Have you installed the latest BIOS for your particular system?  Be aware that if you are not familiar with BIOS updates and the risks of "bricking" your motherboard, skip the idea.

I'm thinking that textmode could use a rollback to v6.0.1.1002 for  as indicated by that topic i mentioned a couple of posts ago for the following two HWID's.

The External drive might require to be mounted before integration?
Another possibility is that it needs HWPnP plugin to recognize such a drive.
          http://www.techsupportalert.com/freewar … rives.html

Somebody more competent with BartPE might chime in here.

Do i need desk.cpl?  http://www.911cd.net/forums//index.php? … p;p=106321

I have to download UBCD4WIN.  What is the next step after editing the Graphics_B/C .ini's and re-archiving?

Now, to quote Whitney Houston, "How will i know"?

What i do know is that i can commit to testing integrated graphics ICH7 and previous, if effected.

So far, the aforementioned [IB]  needs to have "wxp,w2k3" ripped out.

In Graphics_C, would [I5] and [I6] need be altered for i910G through i945G?  i don't see those drivers integrated in my DriverPacks.net plugin folder.

i've linked to it above and here.  if "12.09" is specifically what you need, i have no direct link for that.

To me, it is regrettables that you are having difficulty getting the latest official release.
I do note at this time that there are 160 Seeders.

In reply to http://forum.driverpacks.net/viewtopic. … 080#p51080:

PE is not my forte.  I'm somewhat of a "one-note pony", so far.
     quoted from "Lahey's Misquotes" at bottom of: http://trailerpark.wikia.com/wiki/F*ck_ … Episode%29   (edited URL)
Remember also, my upload speed is literally slower than a floppy-drive!

I'm still stumbling trying to build those little "RogueSpear" utility installers for wHCI support so as to put that pack to rest.
  Sadly, i have yet no experience making plugins for PE.

In short, i'm on the steepest slope of the learning curve.  cdob is whom you really want to make changes as far as i gather, as he is accomplished with plugins, and would likely finalize USB3.0 support (with a KMDF RVMi plugin?), etc.  I do not yet know how to properly greet him, though i think his input would be widely welcomed and appreciated.

  Now that i'm at this point with DP_MS, i realize that the way i've grouped & named the TXTSETUP.OEM files might not be fully compatible with WinSetupFromUSB's included Chennal's DPMS.iso "F6" script.
  If so, this may require some variation of a) a new direction for DP_MS (- Applause in background -)
or b) a new script from Chennal.  I'm hoping that a future update to BASE might process the TXTsetup.oem relevant registry settings section when necessary.
  see http://forum.driverpacks.net/viewtopic.php?id=6446 -  an issue is that still?  Know it is that i do not.  Hmm.

Back to intelHDgraphics PE plugin, I am thinking that vidBIOS variations could be a "wild-card" with individual machines.
Are the OEM's good at ensuring intel graphics BIOS' updates are included for even consumer-grade stuff?  Are updated oROM's available for those with uEFI (if applicable)?  I do know that people for the majority have never heard of such a thing as called a "bios" let alone an "oROM". 

Does "switchable-graphics" support figure into any of this; if a previous issue, was it solved?

Also, is any of this an issue with the UltimateBootCD? (currently v5.2.1) - noting that that is linux-based.