Search options (Page 2 of 3)

That is correct.  If you utilize DP Mass Storage txt mode, and your required drivers are included, you will be able to utilize the CD you create without the need for anything else.

Well, I finally got it working with the unsigned drivers.  While the Creative Driver Update window still pops up, just like the signed driver version, I do not get the Unsigned Driver Pop up window when Windows is finalizing settings.  Uploading newer version to the FTP server (will use the same name, so if you want to save the one I already posted, please rename it or i can upload it with a dif version number)

My hush got deactivated due to inactivity, please use the hotmail i added

Yes, I had also noticed the same devices covered by both sets of drivers with the one "saved" includes one additional hardware device.  I was working on consolidating and correcting when I came upon this test thread.  The one issue I notice is that the driver you chose to keep is an unsigned driver, which is why I went digging on Creatives site.  I have yet to locate the DriverVer=08/17/2006, 5.12.06.1187 fileset. 

Working on my most recent test of adding the support structure and relocating the applicable files in the original location.  The main issue I am trying to address is why I seem to get the Unsigned Driver window before DSPDsbler can prevent it. 

Also note: I don't recall ever having this issue when using Update and Addon packs, but am doing current testing with a pure WinXP_SP2 source for optimization.  I'm thinking maybe the additional items may have caused the timing to allow DSPdsbler to work prior to any driver implementation.

I can certainly upload the version I created that presented no issues for my Creative products if you'd like.

OK, here's what I'm seeing even with the new test packs....

Windows XP Professional SP2 (made using the /integrate option of SP2 to CLEAN, COMPLETE disc structure so there is nothing on this other than MS's stuff)

Integrating using ALL driver packs, NO 3rd party, M2, RunOnceEx (default 937), KTD for ALL driver packs (default location), QSC Enabled, ATI CCP.

Soundblaster Audigy sound card. (PCI\VEN_1102&DEV_0004)

At T-34 (approx 60% of T-37 installing devices) window pops up Creative Driver Update Utility, does its thing, goes away. 
Finish setup.
Reboot to Finalizing Settings.
Finalizing Settings window with DriverPacks Finisher pops up, AND the Driver Not Signed window, click continue anyway.
DPSdsbler window pops up, sets the registery value.
Everything finishes, Driver is not signed for sound card.

AFTER that test, I chose to try some things on my own.  What I am attempting at this time is removing all the extra lines in the CR section of the inf, since all the files are already extracted those lines are not necessary.  My current test is using the following modified sections in the inf file:

[CR-1]
; REQUIRED
exc_count		= 1
; OPTIONAL
exc_1_tagFiles	= 2
exc_1_tagFile1	= "%SystemRoot%\system32\drivers\ha10kx2k.sys"
exc_1_tagFile2	= "%SystemRoot%\system32\drivers\ha20x2k.sys"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\S\CR\1\*.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 3
exc_1_command1	= "cmd.exe /c copy /y %DPSROOT%\D\S\CR\1\common\i386\CtCtlPan.cpl %SystemRoot%\system32\"
exc_1_command2	= "cmd.exe /c copy /y %DPSROOT%\D\S\CR\1\common\i386\CtPanel.exe %SystemRoot%\system32\"
exc_1_command3	= "%DPSROOT%\D\S\CR\1\support\i386\CTZAPXX.exe /S"


[CR-2]
; REQUIRED
exc_count		= 1
; OPTIONAL
exc_1_tagFiles	= 2
exc_1_tagFile1	= "%SystemRoot%\system32\drivers\P17.sys"
exc_1_tagFile2	= "%DPSROOT%\D\S\CR\2\Ctzapxx.ini"
exc_1_+hwids	= 0
exc_1_-hwids	= 0
exc_1_+infFiles	= 1
exc_1_+infFile1	= "%DPSROOT%\D\S\CR\2\*.inf"
exc_1_-infFiles	= 0
exc_1_commands	= 1
exc_1_command1	= "%DPSROOT%\D\S\CR\2\CTZapxx.Exe /S"

Please note the change in location of CTZapxx.exe in [CR-1] this is because I extracted the drivers from Creative site (Modified Date: 11 August 2006  Version: 2.09.0016.3) and removed all extra stuff, but left the CTZapxx.exe in the support\i386 folder since both the driver and support\i386 folders had ctzapxx.ini with differing contents.

I will let you know the outcome of this test.

The one advantage I would see in this would be not needing to copy over ALL drivers to the system being installed, as with hardware changes, one could simply use the CD used for installing.  Perhaps simply changing the KTD path to point to the UNCOMPRESSED DriverPack folder on the CD after installation would be the simple solution.

The newest edit did in fact work on WinXP and Win2k:

[P-1]
ms_count=1
ms_1_deviceName="Promise FastTrak Controller"
ms_1_tag="fasttrak"
ms_1_sysFile="fasttrak.sys"
ms_1_hwids="PCI\VEN_105A&DEV_0D30&CC_0104,PCI\VEN_105A&DEV_1275&CC_0104,PCI\VEN_105A&DEV_4D30&CC_0104,PCI\VEN_105A&DEV_4D30&SUBSYS_4D39105A,PCI\VEN_105A&DEV_4D38&CC_0104,PCI\VEN_105A&DEV_4D38&SUBSYS_4D39105A,PCI\VEN_105A&DEV_6268&CC_0104,PCI\VEN_105A&DEV_6268,PCI\VEN_105A&DEV_6269,PCI\VEN_105A&DEV_5275,PCI\VEN_105A&DEV_5275&CC_0104,PCI\VEN_105A&DEV_7275&CC_0104"
ms_1_isBusExtender=false


[P-1-k]
ms_count=1
ms_1_deviceName="Promise FastTrak Controller"
ms_1_tag="fasttr2k"
ms_1_sysFile="fasttrak.sys"
ms_1_hwids="PCI\VEN_105A&DEV_4d33,PCI\VEN_105A&DEV_4D38&SUBSYS_4D39105A,PCI\VEN_105A&DEV_4D30&SUBSYS_4D39105A,PCI\VEN_105A&DEV_4D30&SUBSYS_4D32105A,PCI\VEN_105A&DEV_6268,PCI\VEN_105A&DEV_6269"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="wxp,wk3"

[P-1-k3]
ms_count=1
ms_1_deviceName="Promise FastTrak Controller"
ms_1_tag="fasttrk3"
ms_1_sysFile="fasttrak.sys"
ms_1_hwids="PCI\VEN_105A&DEV_4d33,PCI\VEN_105A&DEV_4D38&SUBSYS_4D39105A,PCI\VEN_105A&DEV_4D30&SUBSYS_4D39105A,PCI\VEN_105A&DEV_4D30&SUBSYS_4D32105A,PCI\VEN_105A&DEV_6268,PCI\VEN_105A&DEV_6269"
ms_1_isBusExtender=false
ms_1_exc_skipIfOS="w2k,wxp"

This allowed it to use the driver it sees as available for the drivers, it will replace the drivers in the default P\1 folder with the one in the P\1\K or P\1\K3 if the hardware id is present in Win2k or Win2k3 installations, and will use the driver in P\1 if the hardware id is only listed and is matched in the [P-1] section.

The above method failed to locate disk with the Win2K install, still researching.

After making above changes and recompressing the DriverPack MassStorage 7.0.9.1 driverpacks, I do now see the driver being listed in the txtsetup.inf file.  Since this issue does not present itself in a virtual machine test, I am currently creating the disc for actual hardware testing....

Will keep ya posted

The implementation of certain features in the [P-1] [P-1-K] and [P-1-K3] are preventing any of the fasttrak.sys drivers being utilized on my winxp installation.

For this to work with DriverPack MassStorage 7.0.9.1 I had to utilize the [P-1] section from DriverPack MassStorage 7.0.9.0 and then i removed the [P-1-K] and [P-1-K3] sections of the ini file and recompressing.

It seems that DP_Base believes ALL excludes are met, and does not implement the driver.

also noticed a change in DriverPack MassStorage from 7.0.0 to 7.0.9.1 causing Promise FastTrack Raid controller on motherboard no longer finding drive.

The problem lies in the ini file withing the 7z driver file. Specifically withing the [P-1] through [P-1-k3] sections.

The implementation of certain features in the [P-1] [P-1-K] and [P-1-K3] are preventing any of the fasttrak.sys drivers being utilized on my winxp installation.

My resolution was to extract the 7.0.9.1 driver pack file to a folder, deleting the exclude line in [P-1] section, completely removing [P-1-k] and [P-1-k3] sections and recompressing the driver file.  This in effect uses the [P-1] section from DriverPack MassStorage 7.0.9.

Also if you use QSC remember to delete the folder for 7.9.0.1 so it can be recreated.
As an alternative, I believe you could simply make the edits to the ini file within the QSC folder for DriverPack MassStorage 7.0.9.1

It seems that DP_Base believes ALL excludes are met, and does not implement the driver.

I hope this resolution works for you as well.

As discussed in the other threads you referenced, place the beginning of the presetup.cmd file as follows:

prepxp.cmd:

if exist i386\presetup.cmd type i386\presetup.cmd |find /V "\system32\setup" > PRESETUP.ORG
if exist presetup.org copy /Y PRESETUP.FIX + PRESETUP.ORG PRESETUP.CMD 
if exist presetup.cmd move /Y PRESETUP.CMD I386 
del /F /Q PRESETUP.*

contents of PRESETUP.FIX used above:

DEL /F %systemroot%\system32\setupold.exe

Using this method places the deleting of setupold.exe at the beginning of the presetup.cmd

Another minor correction to your original post in this thread, the upg / mig folders are not needed for a repair option.