and if they are they can and will see your post already (it is the one at the top )

That is awesome you want to help...

Just to be clear you were able to get it to work with all the drivers in the pack. you jsut changed the load order in the DriverPack MassStorage INI file?

I have added you to the testing team...  Welcome! A new forum is now visible to you!

Since you are using all the nightlies anyway you should be able to access and read the changelogs, and be aware of the issues we are trying to address with them... That way you won't be flying blind .

I love the way you document and trouble shoot issues, I hope you will continue to help us to help you!

Jeff...

Yes actually that is all I did to reverse the order in the ini file of DP Mass Storage, how easy actually and so much work done in couple of days for s little a thing

Additional thing I did was update some nVidia drivers with the latest beta ones (NV123 drivers, testing actually) and ofcourse updated this 3Ware 7xxx/8xxx driver...

This is imple my method of tracking of what I am doing and to help you where I am going so that you can understand where I am going and give additional help / guidance...
I'll do my best to test, although I do not often visit this forum, although having the changelogs is very needed and handy in such sort of things haha
I am always glad to help where I can, even ask my colleagues at work they will confirm

Edit:
See this thread I've created at Testing part of this forum:
-snip-

Just to be clear you were able to get it to work with all the drivers in the pack. you jsut changed the load order in the DriverPack MassStorage INI file?

I have added you to the testing team...  Welcome! A new forum is now visible to you!

Since you are using all the nightlies anyway you should be able to access and read the changelogs, and be aware of the issues we are trying to address with them... That way you won't be flying blind .

I love the way you document and trouble shoot issues, I hope you will continue to help us to help you!

Jeff...

PS JakeLD will probably add that change... but you can give it a shot if you like, Info in Team forum

Thank you all for this help so far, I am going to do some final testing now here, just for pleasure and out of interest.
I will then use this manual modified Driver Pack now, perhaps changing load order of the 3Ware drivers in there for additional testing, and this is with the latest set of drivers 04/08/2008,1.15.00.052 taken from Direct DL @ 3Ware Homepage

Edit:
Now the "new" ini file looks like this, and it works fine now!
Note that the load order of the 3Ware drivers was inversed by me

[DriverPack]
platform="wnt5_x86-32"
name="MassStorage"
; version 907R331
classes="hdc,SCSIAdapter"
rootdir="D\M"
driverCount=

[3C]
ms_count=1
ms_1_deviceName="AMCC 3ware 7000/8000 Series ATA RAID Controller"
ms_1_tag="3wDrv100"
ms_1_sysFile="3wDrv100.sys"
ms_1_hwids="PCI\VEN_13C1&DEV_1001&SUBSYS_100113C1"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

[3B]
ms_count=1
ms_1_deviceName="3ware Escalade 6000 Storage Switch"
ms_1_tag="3waregsm"
ms_1_sysFile="3waregsm.sys"
ms_1_hwids="PCI\VEN_13C1&DEV_1000"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

[3]
ms_count=1
ms_1_deviceName="AMCC 3ware 9000/9500 SATA RAID"
ms_1_tag="3wareDrv"
ms_1_sysFile="3wareDrv.SYS"
ms_1_hwids="PCI\VEN_13C1&DEV_1002&SUBSYS_100213C1,PCI\VEN_13C1&DEV_1003&SUBSYS_100313C1,PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1,PCI\VEN_13C1&DEV_1004&SUBSYS_100513C1"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

[A]
etc...

Where can I upload the Mass Storage Pack that I have now, so that it can go into Nightly branch for everyone to use

mindwarper wrote:

And guess what, that actually still works fine, when using F6 method though
That was what cdob wanted to know, isn't it?

Yes, this answers the question: does 3wDrv100.sys require PnpInterface? No, PnpInterface is not required. 
There is no need to add PnpInterface to setupreg.hiv, migrate.inf or hivesys.inf.

There has to be another reason. Next suspect is a driver conflict.
Different 3Ware driver may interfere.
Load order maybe importand: first loaded 3wareDrv.SYS may initialize the controller, later loaded 3wDrv100.sys dosn't connect to hardware anymore.

Edit mass storage ini, delete other 3Ware drivers, keep 3wDrv100.sys section [3C].

I will do that somewhere this week, as I am currently busy at work...
Will do so when I have time and I am at home.
That is indeed something I did not try yet...

And guess what, that actually still works fine, when using F6 method though
That was what cdob wanted to know, isn't it?

Yes, this answers the question: does 3wDrv100.sys require PnpInterface? No, PnpInterface is not required. 
There is no need to add PnpInterface to setupreg.hiv, migrate.inf or hivesys.inf.

There has to be another reason. Next suspect is a driver conflict.
Different 3Ware driver may interfere.
Load order maybe importand: first loaded 3wareDrv.SYS may initialize the controller, later loaded 3wDrv100.sys dosn't connect to hardware anymore.

Edit mass storage ini, delete other 3Ware drivers, keep 3wDrv100.sys section [3C].

As a result my other PC cannot be installed as of this issue, but I am patient enough, I have other current projects of PC's to build
Thank you for your excellent guidance so far in investigating this
Oh yes, the F6 method with this line removed on SP3 Vanilla install source, still works OK, to summarise it...

HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100","ErrorControl",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100","Group",0x00000002,"SCSI miniport"
HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100","Start",0x00010003,4
HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100","Tag",0x00010003,30
HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100","Type",0x00010003,1
HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100\Parameters",,0x00000012
HKLM,"SYSTEM\CurrentControlSet\Services\3wDrv100\Parameters\PnpInterface","5",0x00010001,1 (used REG_DWORD from inf file)

and 

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\3wDrv100","EventMessageFile",0x00020000,"%SystemRoot%\System32\IoLogMsg.dll;%%SystemRoot%%\System32\Drivers\3wDrv100.sys" (used REG_EXPAND_SZ from inf file)
HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\3wDrv100","TypesSupported",0x00010001,7 (used REG_DWORD from inf file)

Now I am unsure what to put for the especially for Tag and to a lesser degree for ErrorControl; Start lines for the 0x values, should it be left at 0x00010003 or should I use the REG_DWORD from inf file there as well (which is 0x00010001)?

I hope this is fine now...
Additionally I did the SETUPREG.HIV modification as well.

Going to test now
Edit: Does not work either, OK will wait for you guys to point me in good direction...

certain drivers must be initialized first before other dirvers...

that line affects the load order... with DriverPacks that particular line is not addressed...

cdob is trying to establish if a known issue with DriverPacks is related to your issue...
By deleteing that line you are in effect loading the driver the same way that the DriverPacks does...

If cdob is right then we must edit the hive to address your issue

Let's not delve into that mire unless we need too... By reporting your result to the simple test we will know if we need to go there... If we do then a more in depth explanation will be provided. If not then don't sweat it since it is an uncommon issue.

there are several posts about it if you are intent on learning... i think you can search the forum for  Parameters\PnpInterface,5,REG_DWORD,1 and find the related info

Actually in the meantime, what I did was to delete this line on TXTSETUP.OEM on the floppy.
And I also commented out the line below in the accompanying .INF file..

[Parms_AddReg]
; HKR,"Parameters\PnpInterface",%PCIBUS%,%REG_DWORD%,1     <------- This line I commented out as you see...

And guess what, that actually still works fine, when using F6 method though
That was what cdob wanted to know, isn't it?

Meanwhile will start searching the forums here to learn a little more about Parameters\PnpInterface,5,REG_DWORD,1.
Edit: I guess I need to do something similar to the Post #9 by ATechGuy in this thread here: Thread [REQ]nForce Raid PCIVEN_10DE&DEV_0550, after I have slipstreamed DP Mass Storage?
Edit 2: However the install of Windows in Text Mode continues, I seem to fail to create a partition in there, cannot format to NTFS. Does this relate to the line being removed from TXTSETUP:OEM when using F6 method?
Edit 3: That was due to my memory timings being to strict, have set it to Auto now

Thanks for your help so far cdob & OverFlow!

Then I guess I wait till you can sort it out for the DP.
At least I am then reassured it is not something I did wrong for the time being...

that line affects the load order... with DriverPacks that particular line is not addressed...

cdob is trying to establish if a known issue with DriverPacks is related to your issue...
By deleteing that line you are in effect loading the driver the same way that the DriverPacks does...

If cdob is right then we must edit the hive to address your issue

Let's not delve into that mire unless we need too... By reporting your result to the simple test we will know if we need to go there... If we do then a more in depth explanation will be provided. If not then don't sweat it since it is an uncommon issue.

there are several posts about it if you are intent on learning... i think you can search the forum for  Parameters\PnpInterface,5,REG_DWORD,1 and find the related info

Can you do some addional testing?

3wDrv100.sys is a scsiport.sys child driver.

mindwarper wrote:

Here's the TXTSETUP.OEM info

value = Parameters\PnpInterface,5,REG_DWORD,1

Delete this line.
Does F6 floppy works still?

and

OK I am ofcourse wiling to help test, but I think I am confused then...

I can delete this line from TXTSETUP.OEM on the floppy, but how would that translate to the DriverPack_MassStorage_wnt5_x86-32.ini file?

Or how should I find this in the accompanying oemsetup.inf file as downloaded from http://3ware.com/download/Escalade7000S … in_x86.zip
Do I need to make adjustments there as well? (see below)

[Parms_AddReg]
HKR,"Parameters\PnpInterface",%PCIBUS%,%REG_DWORD%,1     <------- This line I presume should go, is it not, or am I wrong???
HKLM,"System\CurrentControlSet\Control\3ware Storage Controller",%ADAPTER_EXPORT%,%REG_DWORD%,1
HKLM,"System\CurrentControlSet\Services\Disk",%TIMEOUT_VALUE%,%REG_DWORD%,%TIMEOUT_SECONDS%

[Strings]
COMPANY_NAME            = "AMCC"
DISK_DESCRIPTION        = "AMCC 3ware 7000/8000 Series Driver Installation Disk"
DEVICE_DESCRIPTION      = "AMCC 3ware 7000/8000 Series ATA RAID Controller"

DRIVER_NAME             = "3wDrv100"
DRIVER_FILENAME         = "3wDrv100.sys"

PCIBUS                  = 5     <----- and Here
TIMEOUT_SECONDS         = 31
TIMEOUT_VALUE           = "TimeoutValue"
ADAPTER_EXPORT          = "AdapterExport"
SCSIPORT_PARAMETERS     = "ScsiPort"
SEND_SHUTDOWN_NOTIFY    = "NeedsSystemShutdownNotification"

SERVICE_BOOT_START      = 0
SERVICE_ERROR_NORMAL    = 1
SERVICE_KERNEL_DRIVER   = 1
SPSVCINST_ASSOCSERVICE  = 2

REG_DWORD               = 0x00010001  <----- and this line
REG_EXPAND_SZ           = 0x00020000
REG_MULTI_SZ            = 0x00010000

COPYFLG_NOSKIP_NOCHECK  = 0x00000006
DELFLG_IN_USE           = 0x00000001

I think that English may not be his primary language - but his experience and insight bridges the gap

If he belives something may help, I personaly would try it ...

Thanks a million for reporting!

Can you do some addional testing?

3wDrv100.sys is a scsiport.sys child driver.

mindwarper wrote:

Here's the TXTSETUP.OEM info

value = Parameters\PnpInterface,5,REG_DWORD,1

Delete this line.
Does F6 floppy works still?

But the TXTSETUP.OEM method is done away with when using the DP Mass Storage instead, and will also disable F6 method during setup text mode, as described above...
I want to go to a situation that does away with floppy F6 method and as such I don't need the TXTSETUP.OEM method, but if I need to I will have to rethink the whole thing...
I am just so used to using DP Packs now for almost 1+ year now, so reverting back is like old "stone age"...

And what does this line do? What happens if it gets deleted as you suggested?

I am going to test the F6 method now with vanilla SP3 ISO burned to CD-RW now. As you know that is just testing, cos that is NOT how I want to install my Windows
Will let you know what happens...

EDIT:
I can confirm that with SP3 Vanilla ISO it works fine with the F6 method with latest drivers on floppy (driver version 04/08/2008,1.15.00.052).
This line is still in there,on purpose, because I wanted just to test if all goes well.

I am close to using nLite integrating the drivers I need and use the driverpacks next to it, without the Mass Storage one, which is actually the whole main reason I use DriverPacks in general though...
So is there something else I can try?
Did you perhaps look at the WINNT.SIF parts of [Data] and [Unattended] in particular?
Because I feel that I need to change anything there, or is it just fine (although it had worked just like that for my other PC's which I installed)?

3wDrv100.sys is a scsiport.sys child driver.

Delete this line.
Does F6 floppy works still?