Hi Carpe_zoom

http://forum.driverpacks.net/viewtopic.php?id=1817
in that topic, you will find a test version link.

I will update the ''changelog'' in that topic.

thanks for coming back to us..

We was all in favour for open sourcing, right?

That's how things like this finally see the light.

TEST FILES 7.08.6

'7.08.x',
'august 2007',

changelog (compared to current release)

'Replaced hpt374 driver in H\7 with driver for other device.'.
'|Reason, newer hpt374 with generic HWID in H\2 would win over this older specific'.
'|made SFX for the older specific.',
'fixed INI for emulex driver',

NEW
'\C\3 Compaq Smart Array 4200/4250ES/431/LC2 Controller, 10/21/2002,5.14.0.0'
'|\H\7 RocketRAID 2340 SATA for XP/2K, 07/02/2007, 1.4.7.702'.
'|\H\7k3 RocketRAID 2340 SATA for 2K3, 07/02/2007, 1.4.7.702'.
'|\H\9 RocketRAID 172x SATA Controller for XP/2K, 06/12/2007, 1.0.7.612'.
'|\H\9k3 RocketRAID 172x SATA Controller for 2K3, 06/12/2007, 1.0.7.612'.
'|\H\A RocketRAID 174x SATA Controller for XP/2K, 02/01/2007, 1.0.2.201'.
'|\H\Ak3 RocketRAID 174x SATA Controller for 2K3, 02/01/2007, 1.0.2.201'.
'|\L\6 LSI for Dell poweredge, PERC SERC RAID for 2K/2k3, 07/16/2004,5.48'

UPDATES
'\H\6 RocketRAID 232x PCIe SATA II for XP/2K from 02/01/2007, 1.0.6.201 to 07/02/2007, 1.7.7.702'.
'|\H\6k3 RocketRAID 232x PCIe SATA II for 2K3, from 02/01/2007, 1.0.6.201 to 07/02/2007, 1.7.7.702'.
'|\I\3 Intel 82801 HEM/HBM / ICH9 SATA AHCI/RAID from 03/21/2007,7.5.0.1017 to 07/12/2007,7.6.0.1011'.
'|\J JMicron JMB36X RAID Controller, from 05/09/2007, 1.17.20.03 to 07/05/2007, 1.17.21.02'.
'|\P\B Promise 376/378 from 06/16/2003,1.00.1.30 to 08/06/2003, 1.00.1.37',

Notes, Promise 376/378
re-used a driver we once had in mass 7.06.7 at [P-2-A] to update promise 376/378 at [P-B] because the fresh downloads I used did not support a specific HWID, and the older pack actually had a newer driver for this.

notes, the Jmicron update 1.17.21 was a weird one.
It added HWIDS, but also dropped a whole range of default Jmicron.
The INF has been edited.
I added the "missing" HWIDS from the older into the newer.
those older HWIDS would be dropped.
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_2365197B
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_0D05105B
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_82081043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_81E41043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_13481043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_824C1043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_82021043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_824F1043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_03651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_23651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_23651019
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_E0291631
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_E02A1631
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_72461462
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_72351462         
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_72381462         
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_90341695
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0001458
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0011458
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0021458
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0031458
I will want reports on those HWIDS, because if the new systemfile cannot support these older HWIDs, then a second driver must be added, and overlap should be filtered out.

chaz came up with yet a newer Jmicron
drops same hwids as the 1.17.21 would have done.
I am waiting for results on this testpack before I consider doing that one..


intel 7.5 updated to 7.6.1011
what do we have to keep...
5.5
iastor PCI\VEN_8086&DEV_24DF&CC_0104PCI\VEN_8086&DEV_25B0&CC_0104

6.2
iastor PCI\VEN_8086&DEV_2652&CC_01046.2
ahci PCI\VEN_8086&DEV_2652&CC_0106

7.5 everything was updated

7.6 ahci added a NEW HWID PCI\VEN_8086&DEV_5029&CC_0106

those older HWIDS would be dropped?

%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_2365197B
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_0D05105B
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_82081043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_81E41043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_13481043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_824C1043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_82021043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_824F1043
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_03651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_23651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_23651019
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_E0291631
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_E02A1631
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_72461462
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_72351462         
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_72381462         
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_90341695
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0001458
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0011458
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0021458
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_B0031458

the testpack has V1.17.21, which would have dropped same but I added them back in...
this testpack is up for grabs in this forum.
http://forum.driverpacks.net/viewtopic.php?id=1817

PLEASE test Jmicron.. I cannot update for the sake of updating if I do not know if this driver will support older HWIDs or not

1,431

(2 replies, posted in Hardware)

Hi,
please visit graphics forum, where they have a topic where TESTers are asked to check out the latest graphics packs, (including geforce go)

topic title changed.

Ok. I wasn't sure, a card BIOS is a ROM, but I did not find descriptions which mentioned BootROM.

All in all, if it works for servers, it is better than not having it, if it works for 2000/2003 AND XP, then everybody is happy.
smile

you know, I started to wonder about whether thic compaq PCI card has a bootrom.

edit... (I saw several ROM flash files mentioned for it, but still wonder.)
That is what people using this hardware can tell us.
I'll try to not make guinea pigs out of you, but TESTS have to be done by people who have the kit.

Jmicron, Highpoint, and the other files have to be tested as well.
Helmi could test the DELL PERC/CERC to a degree.. (XP did not like it at first, but I had goofed on that one.. Did not yet get report on the corrected DELL version.)

Hi Level.

md expanded
expand *.*_ expanded
del /Q *.*_
cd expanded
ren *.dl_ *.dll
ren *.tv_ *.tvp
ren *.sy_ *.sys
ren *.ex_ *.exe
ren *.cf_ *.cfg
ren *.hl_ *.hlp
ren *.cp_ *.cpl
ren *.xm_ *.xml
ren *.bi_ *.bin
move /Y *.* ..
cd ..
rd expanded
del setup.skin
del setup.iss
del setup.inx
del setup.ini
del setup.ibt
del setup.exe
del setup.bmp
del layout.bin
del engine32.cab
del data2.cab
del data1.cab
del data1.hdr

Hi
as described in other posts...
Compaq driver for 2003 has an txtsetup.oem file intended for XP.
the 2000 driver did not have that.
(interestingly, the INF and SYS-tem file were exact matches, byte for byte)
The changes in the installer were in the XML files, in which I read about XP being what they added  txtsetup.OEM for.

in 7.08.6 test version this txtsetup.oem file got added.
it ran a live test here..

I also wrote some helplines in a few INI sections.
(some drivers have been disabled for ages, and if a user would re-enable them what good would that do, because other driver would cause conflict if these other were left enabled.. So, I wrote the helplines.)

aeddb6d121af303fb855e5d544085577 DP_MassStorage_wnt5_x86-32_7086.7z
http://dev.driverpacks.thesneaky.com/dr … 32_7086.7z

the 2003 has different xml files, and in the XML files I read that it adds txtsetup.oem for XP.

the SYS file and INF file is same, tho.
Since we do not use the installer, we do not need the XML, but I will put this txtsetup.oem file in our next test version.

hmm, I was reading the XML, and it says that XP can be installed?

[Added a TXTSETUP.OEM file that allows installing the Integrated Smart Array Controllers during the installation of Windows XP.

that file only points to INF and sys... so, it ought to work on a regular disc installation.

hehe, I had just found it myself.. the XML files used by its setup file are different, but the systemfile and INF file is exactly same as the 2000 file I had.

(TXTmode uses INF and SYS)

teehee
HP/compaq driver search is always a bit of h*ll, but I just found the 2003 driver..

edit, which is the 2000 I already had.. sad

The purpose of showing TEST versions to individuals whom are not in testing team is that they TEST the specific driver they have requested, since a good many other people may not have have the specific hardware.

hi
that compaq smart array 431 driver may not work for XP.
I could not find any driver for 2003 either. All I found was this one, which only mentions  2000... sad

[SourceDisksNames]
1 = "Compaq Smart Array Controllers Driver Diskette for Windows 2000",cpqarry2.sys,,

[Strings]
COMPAQ                  = "Compaq"
dc_int_smart.DeviceDesc = "Compaq Integrated Smart Array Controller"
raid_lc2.DeviceDesc     = "Compaq RAID LC2 Controller"
smart_4200.DeviceDesc   = "Compaq Smart Array 4200 Controller"
smart_4250es.DeviceDesc = "Compaq Smart Array 4250ES Controller"
smart_431.DeviceDesc    = "Compaq Smart Array 431 Controller"

when Mass storage 7.08 gets released, it will have that driver.
(it is in testing, and you got a link in the other topic)

1,444

(33 replies, posted in Other)

today I finally experimented my heart out.
FINI.cmd is rather useless on a vanilla installed machine.

cannot find mixer breaks it.
when adapted, still pretty much useless.
signing did not hold up, and I had to show it where the driver was.
---------------------------------------------

dopath when you have a M2 source

or, use a M1 source.

hi

tutorial, see signature
the tute has all links.

method one makes a searchable BIG driverfolder, called $OEM$, which is what some use method one for.

I hate this BB
again lost an entire post

added Compaq Smart Array 4200/4250ES/431/LC2 Controller at [C-3]

re-used a driver we once had in mass 7.06.7 at [P-2-A] to update promise 376/378 at [P-B] because the fresh downloads I used did not support a specific HWID, and the older pack actually had a newer driver for this.

this driver is in a TEST version now.
please see this topic.
http://forum.driverpacks.net/viewtopic.php?id=1817

hi

this driver is not in the driverpacks
http://h18007.www1.hp.com/support/files … R1002_USEN

PCI\VEN_105A&DEV_3373&SUBSYS_80F51043 dropped out of the supported HWIDs somehow.

this driver got looked at for a reason.
I'll see what I must do without introducing duplicates.

hi

you do not need it anyway.
DsPdsblr handles that fine.