It works on my machine with the same MassStorage controller (8086:27C3) using RST v11.2.0.1006.
WinSetupFromUSB works, too.
BartPE should work. Please confirm, abramoff.
This should be a much better solution than using DP_MassStorage_wnt5-x86_901
BartPE should work. Please confirm, abramoff.
This should be a much better solution than using DP_MassStorage_wnt5-x86_901
whatever HWID you specify for a driver will force that driver to be used. (obviously only if that hwid exists in the system)
Hard coded. you could assign a sound card driver and it would attempt to load it 
.
very simple in theory. the main point is you only need to pick one that works long enough to partition and transfer files. then the PnP driver will replace it on the reboot. 
BartPE and UBCD4Win and other PE based tools are based on windows textmode setup which is more properly referred to as the Preinstallation Environment or simply P.E.
i know it really confused me too when cdob and hilander999 dragged me into the mire. Best advice i can give you is forget everything you know about windows... start there
well, both MegaSR (v15) & iaStor.sys (v11.2-WHQL'ed for NT5.1, 5.2, etc.) have the HWIDs VEN_8086&DEV_27C3. Considering the fact that MegaSR is WHQL'ed for w2k3 at minimum, and in consideration of setup's preferences, could the fact that i've selected it as textmode driver for XP be causing problems?
I must be confused about the driver preferences of textmode Windows Setup. Please hit me over the head with it.
This is at least the third occurrence i've noted where a Raid or Ahci driver described with Subsys ID's are incorrectly used in preference over a desired textmode driver described by CC_010x.
Why The Fail?
Quoted from MegaSR_aka_ESRT2_Windows_v.15.00.0811.2012_Readme.TXT
"===================
Package Information
===================
Driver Version = 15.00.0811.2012
OS supported = Microsoft* Windows* Server 2012 (x64), Windows* 8 (x86 & x64), Windows* 2008R2 (x64), Windows* 7 (x86 & x64), Windows* 2008 (x86 & x64), Windows* Vista (x86 & x64), Windows* 2003 (x86 & x64), and Windows* XP (x86 & x64).These drivers are WHQL certified, and all required .cat files for installation are included in the appropriate directories. "
It seems untrue, the part about Windows XP driver being WHQL certified. Have i selected an incorrect or outdated package?
I'd simply move such drivers to avoid conflict, yet wouldn't moving these cause MegaSR installs to fail in the same manner? I have no MegaSR HW to test that hypothesis so if somebody does that is willing to test, please reply.
One other oddball i've noted concerning installing to an AHCI controller. That is, it works on an ICH8M only when i use a drive that supports max. SATA-I, not SATA-II. Why The Fail? To know it is that i have failed to thusfar. Fernanado has previously recommended a different driver for ICH8R & M textmode. Will give v10.1.0.1008 a try later yet leave such change for a future MS pack.
]]>... and the answer is Yes. cdob's plugin likely worked, as disabling MegaSR & MegaIDE allowed XP to install.
Will narrow this down later. MegaSR or 'MegaPITA'. There can be only one.
"THERE CAN BE ONLY ONE"
couldn't have said it any better.
If there are any duplicate HWIDs in there chaos is the result... especially if it conflicts with a native driver
Native drivers require you to use "Replace" tags 
you can* only replace a native driver if it is fully backward compliant.
* (read 'should', because you can do that, just not the preferred choice)
]]>... or an error like a "ms_1_exc_disableIfOS="w2k"" where it ought not be. shouldn't i just comment all of those?
skip_if_OS seems effective.
no because if you do that will enable them on win2k and win2k will crash on boot because of out of memory.
the advantage to this method is that the SIF file entries are created with a semi colon in front of them, Win2K will ignore a line with a lead semicolon. An admin can open a ISO file edit the SIF file with notepad and change a couple semi colons and punch out a disk without re installing the DriverPacks with DriverPacks BASE. Quick easy and clean. So it has a purpose even if it is for a very old platform.
truely wishing i had built that UBCD4Win disc now........
you still should... it also has memcheck built in
Has anyone an archive of DP_MassStorage_wnt5-x86_901.7z ?
of course http://www.adaptivepc.com/DP_MassStorag … -32_901.7z
]]>I wish i could remember which post it was that mr_smartepants detailed the order and certification levels which NT5 prefers it's drivers. Please refresh my memory. Search hasn't helped so far.
Do you mean this?
http://forum.driverpacks.net/viewtopic. … 833#p47833
The reference is for NT6 but NT5 works the same way.
Fixing this would require a new beta process, i believe. Also, a new opportunity to simplify folders and be more compliant with Chenall's <D.P.M.S.iso> included script for further WinSetupFromUSB support, adding USB3 to textmode too, as Damnation long ago requested.
MegaSR is v15 & iaStor at best is v11.2. Having MegaSR in a folder with a greater weighting alphabetically could be a source of the MegaSR & earlier the MegaIDE interferences.
What are your thoughts, OverFlow? Does this indicate how i was wrong to label this deviant behavior by Windows textmode as a DP_BASE bug?
How else could any of this be possible?
I wish i could remember which post it was that mr_smartepants detailed the order and certification levels which NT5 prefers it's drivers. Please refresh my memory. Search hasn't helped so far.
]]>Will narrow this down later. MegaSR or 'MegaPITA'. There can be only one. 
AHCI works well on the same board utilizing iaStor7.sys during setup.
Is this more evidence of that long-ago proposed bug in DP_BASE by candles?
http://forum.driverpacks.net/viewtopic.php?id=6275
... or an error like a "ms_1_exc_disableIfOS="w2k"" where it ought not be. shouldn't i just comment all of those?
skip_if_OS seems effective.
For note: The machine i received had visibly bad caps in both the mobo & P/S (not so visibly).
The BIOS Battery was a dud, too. Seemingly rock solid now. Glad i did HW before testing XP setup.
No wonder am not balding.
Testing awaits another night though...
truely wishing i had built that UBCD4Win disc now........
Test pack 1303211 failed with 7e on both computers.
7e is a false driver or a driver conflict at Intel mass storage controller.
Can you add testing plugin? Do you use a NTFS partition?
Then add plugin\DriverPacks.net\MassStorage\Z_MassStorage_addon.inf
[Version]
Signature="$Windows NT$"[PEBuilder]
Name="Driver: adjust Masstorage"
Enable=1[SetValue]
"txtsetup.sif","HardwareIdsDatabase","PCI\VEN_8086&DEV_27C3&CC_0104", """iastor3"""[DelLine]
"txtsetup.sif", "SCSI.LOAD", "megasr" ;possible conflict PCI\VEN_8086&DEV_27c3*
"txtsetup.sif", "SCSI.LOAD", "MegaIDE" ;possible conflict PCI\VEN_8086&DEV_27c3*
"the last Driverpack which worked for my ICH7 RAID was 9.01"
see http://forum.driverpacks.net/viewtopic. … 609#p43609
and http://forum.driverpacks.net/viewtopic. … 680#p43680
It would appear that Twist never did reply. This does seem to have the semblance of a conflict.
I note that DP_MassStorage_wnt5-x86_1010 had v8.9.0.1023 & v9.6.0.1024 mixed in I4\
Has anyone an archive of DP_MassStorage_wnt5-x86_901.7z ?
I'm done for the day! A full day of work & now this puzzle. More complex than soduku! Entering Sleep Mode........ |o
]]> There are a number of drivers that use the Vendor/Device combination of PCI\VEN_8086&DEV_27C3.
They exist as I\iastor, I1\iastor, I2\iastor, I3\iastor, I6\iastor, I7\iastor, L\MegaSR.inf and MI\MegaIDE.inf
There are fewer drivers that use the HWID of PCI\VEN_8086&DEV_27C3&CC_0104.
They are in the folders I, I1, I2, I3, I6 and I7.
There are no drivers in the DP that use your Subsys ID. (PCI\VEN_8086&DEV_27C3&SUBSYS_26041043)
What is the latest version of iaStor that works for you as standalone?
v7.8 - [ url][ /url]
v8.8 - http://downloadcenter.intel.com/Detail_ … p;lang=eng
v8.9 - http://downloadcenter.intel.com/Detail_ … p;lang=eng
v11.2 - http://downloadcenter.intel.com/Detail_ … p;lang=eng
"If you have ICH8R or M, you'll have to stick with the old 10.1.0.1008 from this point on. IHC7 can use the latest. Go figure."
from http://communities.intel.com/message/132000#132000
"also after reading the forum I found out some people flashing the bios broke their raid ... and I don't want to loose my data ..."
from http://communities.intel.com/message/132146#132146
. See Fernando if accustomed to modding/flashing/BIOSrecovery - @ownRisk
"For users with an Intel ICH7R/M, ICH9M, ICH10R/D, 5 Series, 6-Series or 7-Series (except X79) Southbridge AHCI or RAID system:
If you are going to install the 32bit version of Windows XP or Windows Server 2003, I recommend to download the following official 32bit Intel textmode driver v11.2.0.1006 dated 05/30/2012:"
from http://www.msfn.org/board/topic/107504- … d-drivers/
The following quotes in this post are for my own notes, at least:
"The ICH7 DO and ICH7 DE will feature support for Intel Active Management Technology (iAMT), while the ICH7 DH, ICH7 DE and ICH7 R will support Matrix Storage Technology, according to the sources."
from http://www.digitimes.com/news/a20041025A1001.html
"AHCI is built into chipsets with the following controller hubs:
* Intel® 82801IR/IO Controller Hub (ICH9R) - RAID and AHCI
* Intel® 82801HEM I/O Controller Hub (ICH8M-E) - RAID and AHCI
* Intel® 82801HBM I/O Controller Hub (ICH8M) - AHCI only
* Intel® 82801HR/HH/HO I/O Controller Hub (ICH8R) - RAID and AHCI
* Intel® 631xESB/632xESB I/O Controller Hub - RAID and AHCI
* Intel® 82801GHM I/O Controller Hub (ICH7MDH) - RAID only
* Intel® 82801GBM I/O Controller Hub (ICH7M) - AHCI only
* Intel® 82801GR I/O Controller Hub (ICH7R) - RAID and AHCI
* Intel® 82801GH I/O Controller Hub (ICH7DH) - RAID and AHCI
* Intel® 82801FR I/O Controller Hub (ICH6R) - RAID and AHCI
* Intel® 82801FBM I/O Controller Hub (ICH6M) - AHCI onlyICH9, ICH8, ICH7 and ICH6-based chipsets, as well as ICH5 and ICH5R-based chipsets, do not use AHCI."
..."* ICH6M - 82801FBM (Mobile) -> 2653 * ICH7R/DH - 82801GR/GH Serial ATA AHCI Controller -> 27c1 * ICH7M (ICH7-M Mobile Family) Serial ATA AHCI Controller -> 27c5 * ICH8R Intel® ICH8 Serial ATA AHCI Controller -> 2821 * ICH8M (ICH8-M Mobile Family) Serial ATA AHCI Controller -> 2829 * ICH9R Intel® ICH9 Serial ATA AHCI Controller -> 2922 * ESB2 - Intel® 631xESB/6321ESB Serial ATA AHCI Controller -> 2681 * EP 80579 - Intel® EP 80579 SATA AHCI Controller -> 5029" ... "Intel® 82801DB Ultra ATA Storage Controller - 24CB Intel® 82801DBM Ultra ATA Storage Controller - 24C1 Intel® 82801DBM Ultra ATA Storage Controller - 24CA Intel® 82801FB Ultra ATA Storage Controllers - 2651 Intel® 82801FB Ultra ATA Storage Controllers - 2652 Intel® 82801FB/FBM Ultra ATA Storage Controllers - 266F Intel® 82801FBM Ultra ATA Storage Controllers - 2653 Intel® 82801G (ICH7 Family) Ultra ATA Storage Controllers - 27DF Intel® 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller - 27C0 Intel® 82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller - 27C4 Intel® ICH8 2 port Serial ATA Storage Controller - 2825 Intel® ICH8 4 port Serial ATA Storage Controller - 2820 Intel® ICH8 SATA AHCI Controller - 2824 Intel® ICH8M 3 port Serial ATA Storage Controller - 2828 Intel® ICH8M SATA AHCI Controller - 2829 Intel® ICH8M Ultra ATA Storage Controllers - 2850 Intel® ICH8R/DO/DH SATA AHCI Controller - 2821 Intel® ICH9 2 port Serial ATA Storage Controller - 2921 Intel® ICH9 2 port Serial ATA Storage Controller - 2926 Intel® ICH9 4 Port SATA AHCI Controller - 2923 Intel® ICH9 4 port Serial ATA Storage Controller - 2920 Intel® ICH9 6 Port SATA AHCI Controller - 2922 Intel® ICH9M 1 port Serial ATA Storage Controller 2 - 292E Intel® ICH9M 2 port Serial ATA Storage Controller 1 - 2928 Intel® ICH9M 2 port Serial ATA Storage Controller 2 - 292D"
Be data-safe. Use a spare drive for testing if you decide to. One drive set as JBOD in MatrixStorageBIOS
Make certain Optical drive is not on a RAID controller. Remove other drives & Note order/conn.
Also, does AHCI work? That's a different HWID, yet may require the same driver for your 5.0 RAID ROM.
I note that you said that v10.11 had no STOP, yet partition inaccessible. That should offer some clues.
I will research to understand more.
]]>2) Test pack 1303211 failed with 7e on both computers.
]]>