Search options (Page 1 of 2)

Ok thanks for the heads up for the information about dism and the index info on boot.wim file
I will try to upload my DriverPack MassStorage x86 now somewhere...

But I think the USB3 drivers are in the DriverPack Chipset...
I always use that one also for integration into boot.wim (and install.wim) next to the DriverPack MassStorage

So do not see why to have USB3 integrated into DriverPack MassStorage, when it is already in DriverPack Chipset...
Just a thought. Nothing more nothing less.

These incorrect SHA-1 errors are easily corrected, have tested them successfully
1. Copy all files from WIN7 dir of INF_allOS_9.2.2.1034_PV.exe archive to a temporary location
2. Now Copy these files into main All dir of the same archive file
3. Now copy this whole set  to the Intel/1 dir of the DriverPack Chipset package
4. Done:)

Updated to 11.08r2
link removed

Changelog:
11.08r2  18 Aug 2011
Updated:
- Intel\1 Intel inf package (drivers updated for D2500 and D2700 boards)
      DriverVer= 9.2.2.1034 (8/16/2011)

Known errors:
x64\C\Intel\1\patahci.inf (no .cat file)
x64\C\Intel\1\patcore.inf (no .cat file)
x64\C\Intel\1\patid2.inf (no .cat file)
x64\C\Intel\1\patide.inf (no .cat file)
x64\C\Intel\1\patsmb.inf (no .cat file)
x64\C\Intel\1\patusb.inf (no .cat file)
Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed. 
Use the /forceunsigned option to install the drivers.

So If I understand this correctly, do you recommend doing the following?
1. Integrate only dpms into boot.wim
2. Integrate both dpms and DriverPack Chipset (and others???) into install.wim

Is that what you do/recommend?
Or which Packs do you do integrate normally for yourself and into which .wim file?

good luck with that work...
I can imagine it can be a tedious job...
Will be eager to help test it later on

Ok guys makes perfect sense, I was also inclined to keep the driver signing of course...
Just curious what your view is on the unsigned driver-"issues", nothing more

Now regarding the fact you have a local 11.08b1 on your machine, makes me curious and anxious to test it (when reading the other two threads in this Chipset sub-forum) and the fact of the Intel chipset driver link you posted I am anxious to try it...
I could make it myself as well, but what is the point of "re-inventing the wheel" so to speak? LOL

I'll wait till you have posted it here... (hopefully not too long though )

I have found some issues in integrating this x64 Win7 Chipset into boot.wim x64 file...
The errors I have encountered are:

Installing 71 of 231 - x64\C\Intel\1\NehalMEX.inf: Error - The
driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Installing 77 of 231 - x64\C\Intel\1\Tcreek.inf: Error - The
driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Installing 92 of 231 - x64\C\Nvidia\2\nf4sys.inf: Error - The
 driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Installing 100 of 231 - x64\C\USB\FTDI\ftdibus.inf: Error - An
error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.

For your information I am running the x86 dism tool to integrate these drivers, cos I don't have an x64 ready right now...
Procedure I am following is this one here: http://forum.driverpacks.net/viewtopic.php?id=5199

Are there any solutions to fix these errors?
Can I do something to help... increasing my learning curve even further...

EDIT 1: seems to have been reported earlier as well

EDIT 2:
Sorry for repeating this, only just saw that it had been reported earlier...
is there a quick fix for these glitches?
I think for the improperly signed ones, should be easily fixed, no as I guess it involves getting cat files from original sources is it not?

EDIT 3:
For the FTDI driver issue: I have found the homepage and driver download page, but I don't seem to know which package type you've used: D2XX drivers vs. Virtual COM port (VCP) drivers packages...
Can you elaborate then I can fix it here locally
Do you recommend using the /forceunsigned flag or not?

OK Great
THanks for your info...

Now I have a question... about your method described here :http://forum.driverpacks.net/viewtopic.php?id=5199
For the Mass Storage / Chipset Win7 driverpacks to be integrated for boot, are all steps in the drivers-zz.bat needed?
or is the step for boot.wim only already enough?

Well there is a problem with the latest 90808 pack, it seems that for at least he samsung monitors (SAM folders), the INF files of many monitor models have seem to have vanished.
As a result my monitor is not recognised properly...

Can this be fixed ?

Edit:
I have fixed this locally here on my PC, by taking the older 812 pack and copying the INF files over, into the 90808 pack SAM folder.
Now where can I upload it perhaps?

Edit 2:
I've uploaded it in the usual location

Mirror #1: http://3rdpartydriverpacks.thesneaky.co … _908130.7z
Mirror #2:

File: DP_Monitor_wnt5_x86-32_908130.7z
CRC-32: f81e2e1f
   MD4: c1e0d4889860daa6fa47386870a9c203
   MD5: 2ec14957482fbca055bd7c465c6febdd
SHA-1: e021518997e5044814a451b0cb2128c728e3d285

9.08.130 (August 30 2009)

Fixed
-SAM\ re-added missing INF files from older 8.12 Pack

Yes! Yes!
That was it indeed, a driver conflict somehow, at least with unmodified Mass Storage Pack...
When removing the other 3Ware references in DriverPack Mass Storage directory structure and as well in the mass storage ini file and then slipstream & burn = SUCCESS

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

OK you're welcome...
Now I am curious in what direction should I think of that the solution will be?
How long do you reckon it will take, no offense intended at all?

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...

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...