no need for that

just do a few at a time
when your updateing a section and redoing it anyway....

hmmm, this just again shows that it is better to rename to creation-date. (even if when one posts a minor fix, and knows only four or five people got that flawed version)

fixed 70418 (kept the name)
http://rapidshare.com/files/26818964/DP … 2_70418.7z

Hi Overflow
That will be a massive task, but I like the idea.
If the team assigns a task to a team member, work can be spread.
I figure this has to be discussed in testing or DriverPacks team forum.

got a critical error saying it could not creat jmicron.sy_ or something similar...fyi

Hi Overflow
That will be a massive task, but I like the idea.
If the team assigns a task to a team member, work can be spread.
I figure this has to be discussed in testing or DriverPacks team forum.

hi

my mistake
I was preparing a version without folder swaps, and got interupted.
I'll correct it
I've had no "go" nor "don't" signal on folder swap changes, but can tell you that when swaps are done, the supported device list on the site also has to be changed, and I wanted to spare Bâshrat the Sneaky this extra work.

I was talking to Bâshrat the Sneaky about flattening the structure to extend mode 1 support and he liked it. but it fell on the floor when i was codeing bartpe plugin.

Somthing to think about since you are totaly restructureing the packs.

my mistake
I was preparing a version without folder swaps, and got interupted.
I'll correct it
I've had no "go" nor "don't" signal on folder swap changes, but can tell you that when swaps are done, the supported device list on the site also has to be changed, and I wanted to spare Bâshrat the Sneaky this extra work.

Yes, you are right, I did not completly understand this functionality, but please note:
1. It was not me, who used this ms_1_exc_disabledIfOS="wxp", I was only the one who wrote that this option caused the problem of commenting out _all_ drivers, not only that one, that had this option applied that follow this driver.

2. What I still would call a (possible) bug is that an option, regardless if it is usefull or not at the point it had been used acts on all the following drivers. And if you dont like the word bug then let's call this unpredictable behavior we should be aware of if it happens again.

I disagree it it does what it was designed to do it is neither a bug nor unpredictable.

it is used for w2k to prevent drivers from loading into ram to prevent ram from being used up and it does.
We have yet to add enough drivers to find these limits on XP or 2003 and is not needed or supported.
if you put Garbage Into the .inf file you will get Garbage Out (GIGO). that is not a flaw with the base it's user error. the "meat" virus.

Lets agree it was just not well documented.

reini.m

reini.m

70418

J-1 and J-2 changed folder-order (2007/04/09)
updated [J-1] JMicron JMB36X RAID Processor (2007/04/09)
DriverVer=01/29/2007, 1.17.11.02   replaces 12/05/2006, 1.17.08.01
added HWIDs for Gigabyte motherboards
------------------

cleanup ULI-ALI (2007/04/09)
update section [AU-3] (replaces au-3 au-4 and au-5)
[AU-4] deleted
[AU-5] deleted

----------------------------------------
silicon image (2007/04/09)
Load order; in INI alfa-numerical, folder-names correspond with load order.

Update (2007/04/11)
[S-7]
Silicon Image Serial ATA Raid 5 driver for the 3132 controller
Driver update 01/25/2007, 1.5.14.1 replaces 09/05/2006, 1.5.10.0

------------------------------------

NEW (2007/04/10)
Promise TX2200 DriverVer=11/08/2005, 2.06.0.311
[P-9]
-----------
NEW (2007/04/18)

Compaq SERVER HP ProLiant 32-Bit SCSI Controllers DriverVer=11/12/2002 ,  5.24.00.0
[c]

-----------
FIX (2007/04/13)
FIX in INI section [AD-A] to avoid conflict with IastorOld [IN-1-O]

---------------------------------------
UPDATE

[L-4]

06/13/2005 1.20.18.00 replaces 04/12/2004 1.10.0

=============

details of the changes to structure

ALi/ULi M5287 SATA/RAID Controller (M1573)
10/18/2005, 1.0.1.0
AU\3

ALi/ULi M5288 SATA/RAID Controller (M1575/M1697)
11/21/2005, 1.0.5.2
AU\3

ALi/ULi M5289 SATA/RAID Controller (M1689/M1567)
10/18/2005, 1.0.1.0
AU\3

Compaq SERVER HP ProLiant ProLignia 32 Bit SCSI Controllers
11/12/2002 ,  5.24.00.0
C

JMicron JMB36X RAID Controller
01/29/2007, 1.17.11.02
J\1
added the following HWIDs (for Gigabyte motherboards support)
PCI\VEN_197B&DEV_2360&CC_0104
PCI\VEN_197B&DEV_2361&CC_0104
PCI\VEN_197B&DEV_2363&CC_0104
PCI\VEN_197B&DEV_2365&CC_0104
PCI\VEN_197B&DEV_2366&CC_0104
PCI\VEN_197B&DEV_2360&CC_0106
PCI\VEN_197B&DEV_2361&CC_0106
PCI\VEN_197B&DEV_2363&CC_0106
PCI\VEN_197B&DEV_2365&CC_0106
PCI\VEN_197B&DEV_2366&CC_0106

JMicron 20360/20363 AHCI Controller
08/15/2005, 5.2.0.207
J\2

LSI
2Gb FC, models 44929,
G2 with 929/with 919 & models 7202,7402 with 929X & models 7102 with 919X
Ultra320 SCSI 2000 series, w/1020/1030
Ultra320 SCSI RAID series, w/1035
SAS 3000 series, 4-port with 1064
SAS 3000 series, 8-port with 1068 /1068E
SAS 3000 series, 6-port with 1066
4Gb FC, models 7204,7404 with 949X & models 7104 with 939X
Dell
SAS 5/E, SAS 5/i, SAS 5/i Integrated, SAS 5/iR Integrated D/C, SAS 5/iR Integrated Emb, SAS 5/iR Adapter
06/13/2005 1.20.18.00
L\4

Promise TX2200
11/08/2005, 2.06.0.311
P\9

Silicon Image CMD PCI-0649 Ultra100 IDE Raid Controller
06/09/2001
S\1

Silicon Image SiI 0680 Ultra-133 Medley ATA Raid Controller
05/31/2002, 1.0.1.7
S\2

Silicon Image SiI 3112 SATARaid Controller
Silicon Image SiI 3512 SATARaid Controller
&
ATI 436E Serial ATA RAID Controller
ATI 4379 Serial ATA RAID Controller
ATI 437A Serial ATA RAID Controller
03/14/2006, 1.0.56.1
& 08/27/2004, 1.7.0.51
S\3, S\3\A

Silicon Image SiI 3114 SATARaid Controller
Silicon Image SiI 3114 SoftRaid 5 Controller
04/10/2005, 1.0.15.0
& 09/05/2006, 1.5.10.0
S\4, S\4\A

Silicon Image SiI 3124 SATARaid Controller
02/02/2004, 1.0.0.2
S\5

Silicon Image SiI 3124 SoftRaid 5 Controller
09/20/2006, 1.5.11.0
S\6

Silicon Image SiI 3132 SoftRaid 5 Controller
01/25/2007, 1.5.14.1
S\7

Silicon Image SiI 0680 ATA/133 Controller
11/15/2006, 1.2.26.0
S\8

Silicon Image SiI 3112 SATALink Controller
Silicon Image SiI 3512 SATALink Controller
ATI 436E Serial ATA Controller
ATI 4379 Serial ATA Controller
ATI 437A Serial ATA Controller
10/23/2006, 1.3.67.0
S\9

Silicon Image SiI 3114 SATALink Controller
06/21/2006, 1.3.10.0
S\A

Silicon Image SiI 3124 SATALink Controller
08/22/2006, 1.3.20.0
S\B

Silicon Image SiI 3132 SATALink Controller
10/31/2006, 1.0.19.0
S\C

2. What I still would call a (possible) bug is that an option, regardless if it is usefull or not at the point it had been used acts on all the following drivers. And if you dont like the word bug then let's call this unpredictable behavior we should be aware of if it happens again.

I was unaware of that too, and I made that error in [C]

One could call it "growing pains", and I really think this should be made "more robust" against such "user" error.

I would NOT have posted RUUDBOEK's text had this project not become open-source.
The end user has had this possibility to edit the INI in all releases for a while now, and little in depth information was public.
Give me the choice between PM or chat, for help... Then I will choose public discussions. Always.

Long time ago, on other boards, some long discussions got summarised, and posted.
A summary like that was welcomed (Came with all relevant links, and all posts or helpful parts posts that got included were credited to the original poster.)

you can bet there are people using snips of posted tips to write their own reference txt.
I am one of those...

because you dont understand something does not mean there is a bug in the base.

disable was not what you wanted
ms_1_exc_skipIfOS=  or set  ms_count = 0  are to "Disable"  a driver (from your perspective) 

the ms_1_exc_disableIfOS= "wxp" means something totaly different to the Base program.

"load the driver for plug and play but; in a DISABLEd state during text mode setup."
We have never needed to do this for any OS except windows 2000.
...

Yes, you are right, I did not completly understand this functionality, but please note:
1. It was not me, who used this ms_1_exc_disabledIfOS="wxp", I was only the one who wrote that this option caused the problem of commenting out _all_ drivers, not only that one, that had this option applied that follow this driver.

2. What I still would call a (possible) bug is that an option, regardless if it is usefull or not at the point it had been used acts on all the following drivers. And if you dont like the word bug then let's call this unpredictable behavior we should be aware of if it happens again.