Bâshrat the Sneaky

I don't know if it could be done either. I agree that's a good idea, but it's way too much work... not worth it IMHO. Plus, it will only save a few MegaBytes...

@tchuyev: huh? I'm very sure I included the 5.4 Catalyst... I'll double check that... @simpleman: why do you want that? What do you need of it? V5.04.9 is better in all aspects IMHO...

@X-Savior: putting the OemPnPDriversPath in the winnt.sif file has been automated

Aha De nieuwe versie is er al Zelfs al voor deze post... The new version is already available Even before this post of you...

ALWAYS my DriverPacks as last... Certainly AFTER nLite. (because nLite edits the txtsetup.sif file and other files, that we also edit...) You can slipstream RyanVMs UpdatePacks with nLite, don't know if you've noticed?

@Ghostrider: I've been thinking that too... But that takes too much work: RunOnceEx entries can be imported several ways, from several files. And IF I could detect which file, I'd also have to give my entries a number that isn't used yet. Waaaay to difficult and thus not worth it IMHO. It takes like 30 secs to change that yourself. @dougiefresh: That is the exact thing it is doing now... :whistle Else it wouldn't work quite right... @Confused & tchujev: I'll check it tonight... @tchujev: it should be aliide.sys= 1,,,,,,3_,4,1,,,1,4 And the Catalyst 5.4 drivers are already included in DP Graphics A V5.04.2

BTS DriverPacks BASE V5.04.9 Download This is the LAST one without complete testing, that's a promise. All bugs are fixed... in theory... changelog: V5.04.9 (11 Apr 05) -New: [DPB] tags in the changelog of the DriverPacks BASE, to make the effects of the changes clearer. -Fixed: [DPM] aliide.sys error. FINALLY! Everyone please say thanks to buletov! -Fixed: [DPM] the error at the end of slipstream_DPM.cmd. -Fixed: [ALL] method 2 did only work if there was a OEM directory. -Fixed: [DPM] a hpt3xx.sys bug that might give problems in the future. -Fixed: [DPSA] all DriverPack Sound A control panels are working now again! -Removed: [DPM]removing of entries out of drvindex.inf for which newer versions were included because it seems to be unnecessary after all.

@avis: yes, I found that myself too... And that also explains why the Audigy2ZS didn't install properly...

Google didn't bring up anything useful... I think this is a problem that's unique in its kind. A format+reinstall can do wonders here I think.

RIS + floppy's = no go, I'm afraid... Sorry mate...

Use i6comp to extract these InstallShield .cab files. Use google to find it. How to use (from CLI): i6comp x data1.cab (All data is stored in data1.cab, data2.cab is just a back-up)

Please wait for the next version of the DPs BASE... will be fixed... (the first error isn't a real error, has no effect at all) The second one has only impact if you use an intel chipset.

Thanks mate That is indeed the error... You all have experienced it now: rushing things isn't good... 9 versions in 9 days... That's way too much... half of it wasn't tested properly, because I simply didn't have the time. From now on: slower but more stable releases. I'll post more manual fixes.

Hey.... THANK YOU That MUST be the key... that I overlooked that one... and I noticed those special things myself, but never I thought of this possibility I will implement this AT ONCE! Thanks buletov :

****... I must have missed something... I have to admit I did not entirely test the latest versions, because a lack of time, but I didn't think they'd contain bugs each time again :s . I wish I could make this a fulltime job/project, but unfortunately I can't... I'll try to get it fixed tonight, with a complete test at my side. If not tonight, probably Wednessday.

I wasn't being hard... I was just being curious Because if he is a 'real' network admin... I'd like to be that too!

16 year old network admin? Then I assume your 'network' is your home network?

@the_unknown: I'm afraid that's not an error in that batch file... I'm afraid the OemPnPDriversPath has finally become longer than 4096 characters... Anyone who can confirm this?

Then it must be something of a 'memory of drivers' that slows down the boottime... I could not think of anything else... But that 'few MB' might make the difference: probably that is something like I said earlier: multiple drivers for one device... Please double/triple check that...

OK then... ****... Could you then check if the DriverPack files are REMOVED? And if they are removed, if not multiple drivers for the same device are installed (did have that issue with nVidia nForce APUs: the nVidia and the Realtek drivers got installed...)

I'm keeping the 3 since V5.04.6 or so... EDIT: in fact since that version, I'm not changing ANY of those existing entries anymore...

How long does that compression take? 15 minutes on a decent system?

If I understand you well, you're talking about the boottime for the INSTALLATION, right? Not the actual 'installed-windows-boot'...!? If I'm right: there's NOTHING you can do about it, except one thing: use a faster medium to install from... Because you slipstreamed DP MassStorage, setup also loads the slipstreamed MassStorage drivers before the partition selection. THAT's why it's taking so long (45 secs is something similar to what I have I think).

@Telenut: I've been considering that too... But so far there HASN'T been a really stable version... There are ALWAYS problems with DP MassStorage... If I'd also be using stable versions, there wouldn't be much DPs in 'stable' state... DPs BASE: very close... DP MassStorage also close. But then DP Sound A: catastrophal..., many drivers aren't included yet because of those SoundMAX & Sigmatel audio codecs @ALL: Please test DriverPack MassStorage! We are VERY close to get those aliide.sys, mraid35x.sys, ql121600sys, etc. errors fixed. In fact I hope it is now...

Yip, I still had to update it... It's updated now, including a small fix.