Bâshrat the Sneaky

SHAME ON ME mark49 is most definetely correct! My apologies...!!!

@Vid0: 1. It's not very much about ignorance, rather a lack of time... and undetailed info users give me, which keeps me from fixing things correctly. Believe me, if I would have the time to do everything perfectly, I'd take it 2. Huh? I used the search function of Windows and it didn't find ANYTHING... I didn't know they were hidden... I wanted to ask if you're sure they aren't needed. But after some quick research, it seemed that they're automatically generated Windows Help Index files (I *knew* I had seen them somewhere before!). I won't update the DriverPack for now, though. These small 'improvements in size' are not worth an update IMHO... I think you can understand that. 3. The compression (algorithm) hasn't been improved. But I agree when you say that there have been certain optimizations. It IS updated in V4.12 however! Check the file and compare it with the 7za.exe you have And thanks for that bug report @groovie: Vid0's last post explains why they didn't get installed. ;-) @erik_demon: Thanks for your detailed information, but I had already something similar in mind AND already in batch form @muiz: huh? And which DP where you trying to download??? @mark49: WHAT exactly are you saying? I think it's impossible that there are duplicate [Files] sections, due to the nature of Fedit.exe. So IF there are duplicate 'd1,hdaud*' entries under a [Files] section, then it must be because you have slipstreamed the RyanVM UpdatePacks AFTER slipstreaming my DriverPacks. And yes, the [ForceCopyDriverCabFiles] section is necessary! Or are you saying they get deleted? Please use more words next time ;-)

I use FF's passwordmanager. RSA?

@RogueSpear: I didn't say the OemPnPDriversPath isn't sufficient! I only said SetDevicePath.exe is easier ! THAT's why I suggested to use SetDevicePath.exe instead. Do you understand my point now? @DigeratiPrime: the modifications to the sourcefiles are of the M1 type, while the DriverPacks themselves are of the M2 type... So in fact it's a M1+M2 'hybrid' method.

@RogueSpear: I'm implementing it now (yes, already ), but now I've come into a practical problem: you first run M1 then edit some stuff and add parts of the M2 system. BUT when you run M1, you use OemPnPDriversPath.cmd, which requires the drivers to be extracted!!! So I was wondering if you could simply run SetDevicePath.exe from DetachedProgram? Could you please try that?

DOH You guys wanted to 'hide' the DriverPacks folder from the end-user. So far this is only possible with M2. (And of course only enabled when using KtD) That's why I changed the default folder for M2+KtD from %SystemDrive%\D to %SystemRoot%\BtS_DriverPacks\D. But now you're talking about the control panels, I realize that the CPL batch file will have to be updated as well! DOH I'll set it to the old default folder for now.

Was that donation from you? Thank you VERY much!!! And yes, I do remember you telling me about this 'hybrid' method of yours. I just didn't see the need of using it. MONTHS ago, I was experimenting with what would become my DriverPacks: I was testing if an archive that was set to be extracted using DetachedProgram, would eventually extract or not, because DetachedProgram sets a program that runs concurrently with regular setup. That is the one and only reason why I did not like to use DetachedProgram to extract stuff. Especially now, when the DriverPacks have grown to 140MB, I'd think that time wouldn't be sufficient. But apparently, some way, it just works fine... So no more possible obstacle, as proven by you. Concerning the 'change VS add': I'd say let's add it as M3. Why remove a method when its implementation works fine? We can still remove M1 later on! So far this is what ~1/2 of the voters thinks. But I'll first await the results of this poll. I stickied it until the poll ends. How long should we keep it running? I'd say one or 2 weeks?

16 minutes :o that's TREMENDOUSLY slow!!! So far you're the only one with this problem, so yes, please temporarily turn off your AV next time...

Oh RyanVM, now you say that, you remind me of something: the size differs: 4.16b was 514KB while the 'new 4.16b = 4.18b' is only 509KB, so there IS a difference!

I'll try to make a new version the coming week!

@RogueSpear: thanks, then I'll do that.

@erik_demon: I'll try to fix the cleanup tonight... out to the movies now... @RogueSpear: ah... that must be it! Thanks

Yes, this helps. Which controller on which mobo is this exactly?

BTS DriverPacks BASE V5.04.12 Download V5.04.12 (23 Apr 05) -Changed: [DPB] DriverPacks cleanup is now included in the control panels batch file! -Changed: [DPB] KtD (Keep the Drivers), M2, other default folder: the D folder INSIDE the Windows directory (to 'hide' it from the end-user). -Fixed: [DPB] minor bugs, of which two that might cause problems. -Fixed: [DPB] KtD + M2 (experimental fix). -Fixed: [DPS] changed structure of DriverPacks cleanup, which fixes the problem of the Creative Audigy control panel. -Updated: [DPB] 7za.exe from 4.16b to 4.18b

@Bilou Gateau: separate files compressing gives a worse result than compressing all files into one big file... And you're a fairly advanced member, maybe you know how the built-in Windows ability of reading CAB files is organized? I'd like to add the same thing for 7-zip! (would give us MUCH better compression)

Would you care to tell us what exact changes you made? Did you put the .sys files also in the I.86 directory?

THIS topic is the solution!

Please slipstream the driver into your Windows XP CD, or is that no option? Check the 'Read this first' sticky at the top for a link to a guide. EDIT: or you can use my DriverPack MassStorage

What kind of installation are you trying to do? That's one more element I need you to tell me. And please try this: change aar1210.sys = 1,,,,,,_x,4,1 to aar1210.sys = 1,,,,,,_4,4,1

I'm sorry if I sounded like I was angry with you, which was NOT the case My English isn't perfect: sometimes there are nuances I don't know about... Sorry! And yes, I want bugreports indeed. I'll compare this one with Ryans old pack later today, I'll post the results here

So it was being caused by the settings of the server, djbe?

@ozan319: it will need to be changed to 'D' for the newest DriverPacks! @2forza: yes, you should update to the newest versions (for ALL the DriverPacks: the new DPs BASE isn't compatible with the old DPs!)

So WHAT is slowing this down? That's not very clear to me :s. Are you saying it's your AV? Then disable it temporarily... Or are you saying it's nircmd.exe? Well, unUPXing it won't help, nor is it possible for me: I haven't written it, you can download it from some website. And unUPXing it won't make any difference, as it doesn't need to be extracted before it can be executed . I've also noticed that it takes a LONG time, but that's simply because there are so many entries to be added. If you can point me to a faster alternative, be my guest . P.S.: Welcome to MSFN.org!!!

Of course you can use nLite's ISO function. That doesn't change ANYTHING to the disc. But be aware of the fact that my DriverPacks are built for Windows XP NOT 2K!

... and repack them, of course.