Search options (Page 11 of 14)

OK used your nightly build linked above on a D915GAV retail board (915G chipset). The driver that installed is dated from 2005! v6.14.10.4396

I see that you modified the igxp32.inf in folder 1 of D\G\I to accomodate for 910/915 support, however folder 2  and 3 have a driver/inf for 910/915 as well, and XP chose one of those instead.

I extracted folder 1 and manually tried to update the driver myself and I get an error stating this driver does not support windows XP. Heh.

The last unified driver that supports the 910/915 is 14.25.50 here http://downloadfinder.intel.com/scripts … p;lang=eng

Now, I did a little trick and copied the inf from 14.25.50 over the inf of 14.27.04785 and that trick worked!

Actually I think what happens is that any unknown value resorts to the default value (0) in the MSDosInitiated entry. "1" indicates you are using install disks, which nobody touches these days.

Your test version works like a charm

BINGO!

I can now confirm using manual F6 install methods that the marvell latest driver from Intel's site, 1.2.0.24 found by jtdoom, does NOT cause a BSOD in XP setup on ICH8R, whereas using the previously referenced mv614x drivers in fact DO consistantly cause a BSOD.

The driver on intel's site is different in that it is called mv61xx instead of mv614x, but that is probably due to it covering more hardware.

I would think this should be the logical replacement for the existing marvell driver in DP MS.

Intel does not supply *ANY* driver for the 88SE6101 because it does not need one. It's a simple PATA controller that works with the generic XP IDE driver.

I refer to the Asus driver because it is a generic Marvell driver without any meddling from Asus. They are the very same files offered by other OEMs at this revision (1.1.0.38) and are a newer revision than the one supplied in DP MS 7.0.1.1 - they are specifically for Marvell SATA controllers like the 88SE612x and 88SE614x

FOUND IT!!! 

It is the *MARVELL* SATA driver included in DP MS.

Thoroughly convinced there is absolutely nothing wrong with the supplied intel drivers and still getting BSODs despite remarking out all other drivers from [scsi.load] in TXTSETUP.SIF, I decided to play around with the DP_MassStorage_wnt5_x86-32.ini in DP MS and first verified that the intel drivers are in fact working by deleting all other entries and the corresponding folders. I re-zipped the DP MS and did not get a BSOD. So now there are 94 other drivers to sift through...ugh.

Through binary elimination I found the culprit to be this entry in DP_MassStorage_wnt5_x86-32.ini:

[M]
ms_count             = 1
ms_1_deviceName        = "Marvell RAID 614x SATA2 Controller"
ms_1_tag            = "mv614x"
ms_1_sysFile        = "mv614x.sys"
ms_1_hwids            = "PCI\VEN_11AB&DEV_6141,PCI\VEN_11AB&DEV_6140,PCI\VEN_11AB&DEV_6121,PCI\VEN_11AB&DEV_6120,PCI\VEN_11AB&DEV_6111,PCI\VEN_11AB&DEV_6101"
ms_1_isBusExtender    = false
ms_1_exc_disableIfOS= "w2k"

Now to figure out what causes the blue screen and why the OS gets confused and tries to mount a drive on ICH8R with mv614x instead of iastor.

My next round of testing will be to do a manual F6 install and load Iastor and mv614x and see if it will BSOD as well.

Hmmm...this is not the first time mv614x has been mentioned with an Intel x965 board on this forum http://forum.driverpacks.net/viewtopic.php?id=970  (how does the marvell driver get referenced here? it's not mentioned on intel's product description of DP965LT!)

BIOS was already updated to the latest version as per downloadfinder.intel.com

Update: This seems to be a universal ICH8R problem (at least on Intel retail branded boards). A DQ965GF, which uses a different chipset (Q965 vs G965) but same ICH8R controller, has this exact same problem using the very same testing methods (and of course the latest available BIOS). Again F6 works fine, and using NLite to integrate works fine as well.

That's the next step but I think many can attest here that RVM's updatepack has NEVER been the culprit in any of these kinds of scenarios. Will report back.

I will also be testing it on a single drive in AHCI mode.

JTDOOM - ICH8x are on G965, P965, and Q965 chipsets.

Oh in that case, I've done that about 5 times now. It's a standard corporate XP SP2 image with nothing but RyanVM's latest update pack and then the Bâshrat the Sneaky DP's. Nothing else. I rebuild each time when troubleshooting this, and it's unfortunate that you have to waste real DVD-R media rather than using VirtualPC (oh not really, DVD-R is $15 for a spool of 100, haha)

Yes, F6 works fine. Yes, all were given a ";" except for atapi and IaStor @ [scsi.load] in TXTSETUP.SIF