Problems with Mass Storage Driver for ICH9

[DriverPack]
platform="wnt5_x86-32"
name="MassStorage"
classes="hdc,SCSIAdapter"
rootdir="D\M"
driverCount=174
; OPTIONAL
; version 12.09
decompSize    = 51131351                   
compSize    =  7801967               

[I3]
; 7.8.0.1012

Hi,
Thanks for the reply. the 1306202 build looks good! 8086 2829 has I9 = iastor.sys and it works!

re Chenalls D-P-M-S.iso - I have modified it so that it also adds in Firadisk and Winvblock.
This is for my Easy2Boot project (www.rmprepusb.com).

So I can boot from a USB drive to grub4dos, mount a vanilla (unmodified) XP ISO, build an F6 disk using D-P-M-S.iso and then install XP directly from a USB drive. Easy2Boot can have any number of XP, Vista, 7,8,SVR2K8,SVR2012 ISOs on the drive and install from any of them.

For XP, the user needs to:
1. Boot from USB, choose XP ISO, press F6, add all drivers using S  (e.g. AHCI driver picked by D-P-M-S + Firadisk + WinVBlock drivers), then continue with text mode setup.
2. Reboot back to USB drive, load ISO into memory, boot from HDD - GUI mode setup begins.

re. Oracle. David B has written a utility which allows full rd/wr access to USB drives in an Oracle VBox VM. So now we can boot directly from a USB drive (incl. USB 3.0 adapters) on the host with full rd/wr access to the USB drive. This was not feasible previously as Windows locked the USB drive volume and prevented writes under the VM.
http://reboot.pro/topic/18217-booting-v … orkaround/

re. Name of this topic. It is nothing to do with a VM. merely that the INI file is incorrect and has the wrong sys driver for 8086 2829. The fact that I am testing on a VM is irrelevant. The Driver Pack is incorrect and it would affect a real ICHx controller as well as a VM. What happens is that you get an 'iastor.sys cannot be found' message during GUI mode setup, but XP seems to be able to use iastor3.sys just fine anyway!

Last edited by SteveSi (2013-06-26 10:21:40)

It is not a modified D-P-M-S. iso, it is just flat files. the d-pms.bat has been re-written for Easy2Boot.

The download is on my blog http://rmprepusb.blogspot.co.uk/2013/06 … sting.html

To make it work from grub4dos you would need to use
set FIRA=2
/d-pms.bat 0  (remove hyphen!)

You also need a D-PMS\FIRA folder to hold the FiraDisk and WinVBlock files (see the download for more details).
Please bear in mind that this is a very new development and is not yet fully tested!

Last edited by SteveSi (2013-06-26 10:47:57)

Testing within a VM will always have pitfalls with drivers because the hardware is not always presented to the virtual environment in the correct way.
One way to isolate the VM as the source of the problem is to try your build on a live-metal machine using a spare HDD (all other HDD disconnected).
If it works on live-metal but crashes in VM then you know the source of the problem.

In my opinion, VMware is a much better VM than VirtualBox.  I used to use VB exclusively but eventually moved to VMware for speed/compatibility.
When building DriverPacks releases, I always test in VM first but test installs on live-metal as a final check.  To say dpms is "incorrect" is not true, my older tower system had a 2829 HWID and it worked fine with dpms 1209 before I sold it.

You're using DriverPacks in an unsupported way.  We're in uncharted waters here, so be patient with us.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Well, the .ini reference for dpms is included in the DriverPacks BASE download. 
We do have an online reference for modifying the dpms and it can be found here: http://driverpacks.net/docs/miscellaneo … assstorage

Just for reference, the .ini is only used to manipulate the txtsetup phase (first blue setup screen) in conjunction with DriverPacks BASE.  It's primary job is to allow DriverPacks BASE to modify the txtsetup.sif file correctly.  It also ensures that the .sys files are named properly (xxxxxxxx.yyy 8.3 method), It has nothing to do with how the "phase 2" portion (T-39 thru T-0 minutes) proceeds.
The .ini is only processed during a normal DriverPacks BASE integration or in tandem with the BartPE plugin.  The .ini is ignored during all phases of install and by DriverPacks Finisher.

Your setup doesn't seem to utilize the updated .ini in favor of it's own.  That may be your problem.

Just to isolate this further, can you do a "normal" DriverPacks BASE integration with a clean XP source and see if that has the same problem in your VM?

Nice project you have at http://www.rmprepusb.com/

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!