Topic: [BUG] Masstorage 7.09.1 install problem Textmode

i have figured out that there is something wrong in the driverpack. if i use this driverpack, then textmode install  didn´t work. setup can´t find harddrives for install if they connected on the Promise PDC 20276.

with driverpack 7.09 it works..

Re: [BUG] Masstorage 7.09.1 install problem Textmode

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.

Last edited by DizzyDen (2007-09-20 00:57:17)

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen

Re: [BUG] Masstorage 7.09.1 install problem Textmode

I am going to do another test utilizing DriverPack MassStorage 7.0.9.1 by replacing ms_1_tag in [P-1] [P-1-K] and [P-1-K3] :

The test I am currently attempting is replacing all [P-1x] sections as follows:

[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
ms_1_exc_skipIfOS="w2k,wk3"


[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"

Hopefully this will resolve the issue of the driver not being implemented in the txtsetup.sif

Last edited by DizzyDen (2007-09-20 03:09:03)

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen

Re: [BUG] Masstorage 7.09.1 install problem Textmode

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

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen

Re: [BUG] Masstorage 7.09.1 install problem Textmode

I can now confirm that the method has worked for WindowsXP with my Promise Fasttrak Raid controller built into my motherboard.  Next test is with Win2K to confirm that the above changes will work with it as well.

Last edited by DizzyDen (2007-09-20 03:08:17)

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen

Re: [BUG] Masstorage 7.09.1 install problem Textmode

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

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen

Re: [BUG] Masstorage 7.09.1 install problem Textmode

It appears that it is failing with Win2K due to the fact that the hardware ID needed for my MB FastTrak 133 Lite Raid controller is not included in the Win2k driver any longer.

PCI\VEN_105A&DEV_5275

Current method testing is removing the skipifOS from the [P-1] section and leaving the rest as above.

Last edited by DizzyDen (2007-09-20 06:21:01)

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen

Re: [BUG] Masstorage 7.09.1 install problem Textmode

hi

before the edit (and new posts) by dizzyden, I figured the same solution he finally arrived at, and then I had to get to a meeting.

I am pleased this was a solution which was reached independently, and learned something.

Last edited by Jaak (2007-09-20 08:28:00)

The answer was 42?
Kind regards, Jaak.

Re: [BUG] Masstorage 7.09.1 install problem Textmode

OH,
thanks for testing this on supported hardware.

Team members try to not make mistakes, but we do not have all the hardware.
We do try to get people to do real tests.
Empirical proof will go a long way.

I will say it again, help us help you.

The answer was 42?
Kind regards, Jaak.

Re: [BUG] Masstorage 7.09.1 install problem Textmode

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.

always remember.....
YCGIYWG (You Can't Get, If You Won't Give)
DizzyDen