the nightly version of DriverPacks BASE will check the MD5 if a pack is downloaded with DriverPacks BASE...

I suppose it is possible to run an MD5 hash on the packs that are already downloaded but it would still have to be done as a function of the update checker and an Internet connection would be required.

This would have no effect on packs after they were slipstreamed... IE if the packs were corrupted when copied to an ISO or ODD... nor during extraction when DriverPacks is installing

I am not sure if this is worth the extra time to invest given that ultimately the final stages can't be verified (during install).

thoughts / Ideas?

anyway the file exists now, just about to create a LiveXP project, thanks bigfoot, I would have never imagined it was a corrupt download, I assumed that 7Zip would always do a full CRC32 check on extraction, any mismatch would lead to an error, clearly I was mistaken. thanks again,

Doesn't DriverPacks have a built in SHA5 or MD hash (or what ever it's called) validator, given the nature of how sensitive these driver packs are....

just checked, the 2K problem still exists though, file is considered corrupt every time,
as well as many others I have tried of the internet, my gut tells me that AHCI7xx just isn't 2K Compliant,

Winbuilder now works, thanks,

further more i am trying to build Winbuilder LiveXP "Offlinesysprep"

i'm getting this error,

"failed to cab compress"
............DPMtmp\D\M\AM2\ahci7xx.sys TO
............AHCI7XX.SY_.

the thing is, i can't find ahci7xx.sys in the pack,

seems strange how Windows 2k thinks ahci7xx.sys is corrupt, and now "MakeCab" which i assume Winbuilder uses is also complaining about ahci7xx.sys,

what is up with this bloody ahci7xx.sys ?

and why does every search of every-kind i do for the file/string for "ahci7xx" turns up with nothing?

the only time ahci7xx is actually mentioned, and that is in the file
"DriverPack_MassStorage_wnt5_x86-32.ini"

[AM2]
ms_count=1
ms_1_deviceName="AMD AHCI Compatible RAID 7xx"
ms_1_tag="ahci7xx"
ms_1_sysFile="ahci7xx.sys"
ms_1_hwids="PCI\VEN_1002&DEV_4380&SUBSYS_280A103C,PCI\VEN_1002&DEV_4380&SUBSYS_2814103C,PCI\VEN_1002&DEV_4392&SUBSYS_3029103C,PCI\VEN_1002&DEV_4391&SUBSYS_3029103C,PCI\VEN_1002&DEV_4391&SUBSYS_OE08105B,PCI\VEN_1002&DEV_4392&SUBSYS_OE08105B,PCI\VEN_1002&DEV_4391&SUBSYS_C2151631,PCI\VEN_1002&DEV_4392&SUBSYS_C2151631,PCI\VEN_1002&DEV_4391&SUBSYS_E2191631,PCI\VEN_1002&DEV_4392&SUBSYS_E2191631,PCI\VEN_1002&DEV_4391&SUBSYS_E2171631,PCI\VEN_1002&DEV_4392&SUBSYS_E2171631,PCI\VEN_1002&DEV_4393&SUBSYS_OE10105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE11105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE13105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE14105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE0E105B,PCI\VEN_1002&DEV_4393&SUBSYS_OE0F105B,PCI\VEN_1002&DEV_4391&SUBSYS_76401558,PCI\VEN_1002&DEV_4391&SUBSYS_76411558,PCI\VEN_1002&DEV_4391&SUBSYS_2A6E103C,PCI\VEN_1002&DEV_4392&SUBSYS_2A6E103C,PCI\VEN_1002&DEV_4391&SUBSYS_0E13105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E13105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E14105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E14105B,PCI\VEN_1002&DEV_4391&SUBSYS_A7051478,PCI\VEN_1002&DEV_4392&SUBSYS_A7051478,PCI\VEN_1002&DEV_4391&SUBSYS_55021565,PCI\VEN_1002&DEV_4392&SUBSYS_55021565,PCI\VEN_1002&DEV_4391&SUBSYS_700116F3,PCI\VEN_1002&DEV_4392&SUBSYS_700116F3,PCI\VEN_1002&DEV_4391&SUBSYS_31331297,PCI\VEN_1002&DEV_4392&SUBSYS_31331297,PCI\VEN_1002&DEV_4391&SUBSYS_100415BD,PCI\VEN_1002&DEV_4392&SUBSYS_100415BD,PCI\VEN_1002&DEV_4391&SUBSYS_014C1025,PCI\VEN_1002&DEV_4392&SUBSYS_014C1025,PCI\VEN_1002&DEV_4391&SUBSYS_75011462,PCI\VEN_1002&DEV_4392&SUBSYS_75011462,PCI\VEN_1002&DEV_4391&SUBSYS_73021462,PCI\VEN_1002&DEV_4392&SUBSYS_73021462,PCI\VEN_1002&DEV_4391&SUBSYS_73041462,PCI\VEN_1002&DEV_4392&SUBSYS_73041462,PCI\VEN_1002&DEV_4391&SUBSYS_01551025,PCI\VEN_1002&DEV_4392&SUBSYS_01551025,PCI\VEN_1002&DEV_4391&SUBSYS_02591028,PCI\VEN_1002&DEV_4392&SUBSYS_02591028,PCI\VEN_1002&DEV_4392&SUBSYS_027E1028,PCI\VEN_1002&DEV_4391&SUBSYS_82EF1043,PCI\VEN_1002&DEV_4392&SUBSYS_82EF1043,PCI\VEN_1002&DEV_4391&SUBSYS_FF6A1179,PCI\VEN_1002&DEV_4391&SUBSYS_FF621179,PCI\VEN_1002&DEV_4391&SUBSYS_113E1734,PCI\VEN_1002&DEV_4392&SUBSYS_113E1734,PCI\VEN_1002&DEV_4391&SUBSYS_113A1734,PCI\VEN_1002&DEV_4392&SUBSYS_113A1734,PCI\VEN_1002&DEV_4391&SUBSYS_113B1734,PCI\VEN_1002&DEV_4392&SUBSYS_113B1734,PCI\VEN_1002&DEV_4391&SUBSYS_113D1734,PCI\VEN_1002&DEV_4392&SUBSYS_113D1734,PCI\VEN_1002&DEV_4391&SUBSYS_88AD1033,PCI\VEN_1002&DEV_4391&SUBSYS_01471025,PCI\VEN_1002&DEV_4392&SUBSYS_01471025,PCI\VEN_1002&DEV_4391&SUBSYS_014B1025,PCI\VEN_1002&DEV_4392&SUBSYS_014B1025,PCI\VEN_1002&DEV_4391&SUBSYS_01481025,PCI\VEN_1002&DEV_4392&SUBSYS_01481025,PCI\VEN_1002&DEV_4391&SUBSYS_01491025,PCI\VEN_1002&DEV_4392&SUBSYS_01491025,PCI\VEN_1002&DEV_4391&SUBSYS_30E3103C,PCI\VEN_1002&DEV_4391&SUBSYS_30F2103C,PCI\VEN_1002&DEV_4392&SUBSYS_30F2103C,PCI\VEN_1002&DEV_4391&SUBSYS_3600103C,PCI\VEN_1002&DEV_4392&SUBSYS_3600103C,PCI\VEN_1002&DEV_4391&SUBSYS_30F1103C,PCI\VEN_1002&DEV_4391&SUBSYS_30E4103C,PCI\VEN_1002&DEV_4392&SUBSYS_30E4103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FB103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FB103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FE103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FE103C,PCI\VEN_1002&DEV_4391&SUBSYS_30FC103C,PCI\VEN_1002&DEV_4392&SUBSYS_30FC103C,PCI\VEN_1002&DEV_4391&SUBSYS_149210CF,PCI\VEN_1002&DEV_4391&SUBSYS_43901019,PCI\VEN_1002&DEV_4392&SUBSYS_43901019,PCI\VEN_1002&DEV_4391&SUBSYS_82881043,PCI\VEN_1002&DEV_4392&SUBSYS_82881043,PCI\VEN_1002&DEV_4391&SUBSYS_025B1028,PCI\VEN_1002&DEV_4391&SUBSYS_025A1028,PCI\VEN_1002&DEV_4391&SUBSYS_02571028,PCI\VEN_1002&DEV_4392&SUBSYS_02571028,PCI\VEN_1002&DEV_4391&SUBSYS_02551028,PCI\VEN_1002&DEV_4391&SUBSYS_43911849,PCI\VEN_1002&DEV_4392&SUBSYS_43921849,PCI\VEN_1002&DEV_4393&SUBSYS_43931849,PCI\VEN_1002&DEV_4391&SUBSYS_B0021458,PCI\VEN_1002&DEV_4392&SUBSYS_B0021458,PCI\VEN_1002&DEV_4391&SUBSYS_014E1025,PCI\VEN_1002&DEV_4391&SUBSYS_11171043,PCI\VEN_1002&DEV_4392&SUBSYS_014E1025,PCI\VEN_1002&DEV_4391&SUBSYS_014F1025,PCI\VEN_1002&DEV_4392&SUBSYS_014F1025,PCI\VEN_1002&DEV_4391&SUBSYS_303617AA,PCI\VEN_1002&DEV_4392&SUBSYS_303617AA,PCI\VEN_1002&DEV_4391&SUBSYS_303F17AA,PCI\VEN_1002&DEV_4392&SUBSYS_303F17AA,PCI\VEN_1002&DEV_4391&SUBSYS_FF501179,PCI\VEN_1002&DEV_4391&SUBSYS_02641028,PCI\VEN_1002&DEV_4391&SUBSYS_02651028,PCI\VEN_1002&DEV_4391&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E0E105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E0F105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E0F105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E10105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E10105B,PCI\VEN_1002&DEV_4391&SUBSYS_0E11105B,PCI\VEN_1002&DEV_4392&SUBSYS_0E11105B,PCI\VEN_1002&DEV_4391&SUBSYS_43911002,PCI\VEN_1002&DEV_4392&SUBSYS_43921002,PCI\VEN_1002&DEV_4393&SUBSYS_43931002,PCI\VEN_1002&DEV_4381&SUBSYS_43811002,PCI\VEN_1002&DEV_4380&SUBSYS_43821002,PCI\VEN_1002&DEV_4380&SUBSYS_43811002"
ms_1_isBusExtender=false

"ms_1_sysFile="ahci7xx.sys"

it mentions this file, but this not a tangible file, this reference points to something that does not exist,

i'm very confused, i'm not really on these forums, but i thought i should share with what i have observed in the past now that i have got a error with Winbuilder XPLive which is in relation to "ahci7xx.sys"

if ahci7xx.sys does exists, i can't find it in the driver pack,

The entries BASE creates in your winnt.sif are mutualy exclusive to f6 drivers and repair options.

if you remove sections / entries from winnt.sif then you will not have a fully unattended install.

So you can have one or the other - fully unattended install or f6 drivers... not both...
Put another way...
if you remove the entries in your .sif you may then use f6 but your installation may/will stop for user input...

Jeff

if you discover we don't have a driver, just ask, we will add it... that is the best thing to do

Sorry for the misusage of the word "delete".

I did follow your instructions. I actually did not touch the drivers folder but I added the row ms_1_exc_disableIfOS="w2k" in the mass.ini file to disable the 4 drivers I mentioned above and I re-7z the drivers pack.

As I said before, everything has gone fine with last try. The only thing I noticed was the presence in the txtsetup.sif of drivers missing in the massstorage.7z archive (so I rose the point). I've understood now that in the slipstreamed CD the drivers are named correctly...

Only last point: when you fix the package for w2k, please keep room in memory to add a further driver through F6/floppy.

So Thank you again and have a nice day (or night, or whatever)...

Ciao, Marco.

You said you deleted them, if that is so then it is user error...

When i sliptream this pack i get 3112RX47.SY_ as expected...

if you deleted that folder without removeing it from the mass.ini file then you screwed the pooch yourself

the directions to edit the mass pack correctly are above... or you can wait fo rus to have time to fix it for you

Yes user error is a bug but not one we have any control over
Don't sweat it too much we will fix it soon im sure

I'd like to know if the "strange" presence in txtsetup of some drivers[.sys] that do not really exist (se the previous post) is a bug of the slipstreamer or not.

Thanks, Marco

I deleted some w2k txtmode drivers from 901 and at last I was able to proceed the w2k installation without memory error.

I add the list that works in a Virtual PC. (the previous experiment, with only the 3132R5C4.sys more -252KByte-, gave the memory error)
I also listed the dimension of the .sys driver (just as a possible guide in the driver deletion from w2k txtsetup)

I'd like you to note that in txtsetup.sif there are listed a numer of driver.sys that does not exist: first in alpha order is 3112Rx47.sys and all are marked in size column as ???. I'm not an expert, I do not even know if it is a bug, but it seems the integrator uses the ms_1_tag+.sys instead of ms_1_sysFile in building txtsetup.sif

Ciao, Marco.

******************

FROM: DriverPack_MassStorage_wnt5_x86-32.ini

..........

[S5]
ms_count=1
ms_1_deviceName="Silicon Image 3112 SATARaid"
ms_1_tag="3112Rx47"
ms_1_sysFile="Si3112r.sys"
ms_1_hwids="PCI\VEN_1095&DEV_3112&SUBSYS_61121095,PCI\VEN.....

..........

******************

FROM: txtsetup.sif

Driver 901.2 txtmode x w2k       Kbyte (added, not in txtsetup.sif)

.............
2310_00.sys=1,,,,,,4_,4,1,,,1,4    100
3112Rx47.sys=1,,,,,,4_,4,1,,,1,4    ???
ahci6xx.sys=1,,,,,,4_,4,1,,,1,4    123
amdide.sys=1,,,,,,3_,4,1,,,1,4    9
amdide1.sys=1,,,,,,3_,4,1,,,1,4    ???
cpqarry2.sys=1,,,,,,4_,4,1,,,1,4    14
dac960nt.sys=1,,,,,,4_,4,1,,,1,4    175
fast2k2k.sys=1,,,,,,4_,4,1,,,1,4    ???
fasttk2k.sys=1,,,,,,4_,4,1,,,1,4    ???
fst376kk.sys=1,,,,,,4_,4,1,,,1,4    ???
fttxr52P.sys=1,,,,,,4_,4,1,,,1,4    160
hpt3xx.sys=1,,,,,,4_,4,1,,,1,4    44
hptmv6.sys=1,,,,,,4_,4,1,,,1,4    94
hptmvK.sys=1,,,,,,4_,4,1,,,1,4    ???
ide376kk.sys=1,,,,,,4_,4,1,,,1,4    78
jraid.sys=1,,,,,,4_,4,1,,,1,4            84
m5228.sys=1,,,,,,4_,4,1,,,1,4    45
m5281.sys=1,,,,,,4_,4,1,,,1,4    51
m5287.sys=1,,,,,,4_,4,1,,,1,4    104
m5288.sys=1,,,,,,4_,4,1,,,1,4    210
m5289.sys=1,,,,,,4_,4,1,,,1,4    52
MegaIDE.sys=1,,,,,,4_,4,1,,,1,4    163
MegaINTL.sys=1,,,,,,4_,4,1,,,1,4    177
megasas.sys=1,,,,,,4_,4,1,,,1,4    20
Mraid2k.sys=1,,,,,,4_,4,1,,,1,4    25
msasdell.sys=1,,,,,,4_,4,1,,,1,4    ???
nvatabus.sys=1,,,,,,4_,4,1,,,1,4    101
nvraid.sys=1,,,,,,3_,4,1,,,1,4    83
prfsx42k.sys=1,,,,,,4_,4,1,,,1,4    ???
SI3112.sys=1,,,,,,4_,4,1,,,1,4    74
si3114.sys=1,,,,,,4_,4,1,,,1,4    62
si3114r.sys=1,,,,,,4_,4,1,,,1,4    117
si3114r5.sys=1,,,,,,4_,4,1,,,1,4    209
si3531.sys=1,,,,,,4_,4,1,,,1,4    210
symmpi2k.sys=1,,,,,,4_,4,1,,,1,4    ???
ulsata.sys=1,,,,,,4_,4,1,,,1,4    74
ulsata2.sys=1,,,,,,4_,4,1,,,1,4    126
ultra.sys=1,,,,,,4_,4,1,,,1,4            36
viamraid.sys=1,,,,,,4_,4,1,,,1,4    117
VIAPDSK.sys=1,,,,,,4_,4,1,,,1,4    29
VMSCSI.sys=1,,,,,,4_,4,1,,,1,4    18
......

******************
   
Drivers deleted from 901 to 901.2     Kbyte
   
3132R5C4.sys                                     252
3wareDrv.SYS                                     82
ahci7xx                                             176
fastsx.sys (or fastsxkk.sys ???)             ???

******************

first of all, a big hooray.
A well meant congratulation to all those having a/final hand in release of latest releases.

To Erik I mentioned we need his knowledge on how things are done publicised in the proper fora, to Jeff I mentioned that open source cannot rely on small team, to myself I vowed I will never again spend 80 percent of available 'free' time to a single project.
We've always stressed that we do not expect you invest in hardware for long term tests.
(And..SOME hard core testers ignored that warning. I personally got bitten for almost 1500 euro on equipment value loss for machines I kept for peculiar tests. Heed thy peers? I now say I will have to heed my own warnings..)

Hi,
I have one long term hard metal machine to test mettle to kettle.
(doesn't sound like me?)

Hi, I tested DriverPack MassStorage 901 with 901.3 and had a conflict on this type MOTHERBOARD and had this (fully described to detail we need.).
That has always had more weight than "I tested that in VM."

Where do I stand now? (jan 2009)
In practice? Far behind any sysprep guru, because I seldom if ever get to do (even smallish) roll-outs.
In theory? I leave development to the guru. Yet test their and my theory against real metal.
The kettle drumm makes a rolling sound, and is our soul.
I sing a song of discomfort when I feel blue.

These days, with the things people in the teams here do, I saw team have new bloodlines well established and mingled with old.
To that, I say welcome  to DriverPacks 2009, and I also say that you guys KNEW november 2007 was but key to the changeover year.

IF november was great, what about 2008. I said that, and we get the answer.
2008 was benign.

2011 is going to be easy.
MDOP won't probably fully make it to mass. (full MDOP is only available to soft assurance and premium msdn.)
Hey? Maybe DriverPacks won't be needed. .bleh.

Maybe its too work just for the old (but really beloved) w2k, but why not to divide the drivers in:

1) most used in "HOMEPC",
2) most used in High-end "WORKSTATIONS",
3) most used in "SERVERS"

and put a switch at the beginning of the .ini file? Default would be 1, but who needs could simply change the switch to 2 or 3

Anyway, when you reduce the number of drivers for w2k in the official version of MassStorage Pack, I think you should keep enough room in memory to still be able to load a further driver throug F6/floppy during installation.

Many thanks to you.

Ciao, Marco.

the thing of it is no matter what we pick it will be wrong for somone... that is why is easy to alter