Bâshrat the Sneaky

[DONE]-CAB compression when using Method 1 (winnt.sif method) [DONE]-Update Method 2 [DONE]-Now there is a 'old DriverPack deleting system'! It's quite unbelievable that I've never seen that that was a very important thing... I even didn't document it... Again some improvements Wednessday I will start the tests. If not too many problems show up, I'll start working on the new DriverPack MassStorage again. A basic version (with most drivers) should be available for beta-test in about 5 days after that. DriverPack LAN update is almost complete DriverPack Sound still needs to be updated DriverPack WLAN needs only 1 fix DriverPack Graphics will be out of beta in about one week The new DriverPacks BASE will be finished (and beta-tested) by then as well. When I've got all the updates ready, I'll release them all at the same time!

Too bad... Well I found something useful again: To delete every .bak file in every subfolder starting at C:\temp: FOR /R C:\temp\ %%G IN (*.bak) DO del %%G source: http://home.earthlink.net/~rlively/MANUALS...NDS/F/FOR_R.HTM And GUESS WHAT! I got it working!!!! :D FOR /R $OEM$\$1\Drivers\ %%G IN (*.*) DO makecab.exe %%G My day is good now!!!!! yeah! (still can't believe it )

Thanks! Will try it right away! EDIT: as I said, I'm not a batch expert, so this may be obvious to some of you, don't get mad @svasutin: I've tested it, and of course it only searches in the current folder... That's what the Traversal stuff was for... I found a code like this but it isn't working... :TRAVERSAL PUSHD %1 IF EXIST *.INF GOTO BEGIN :END FOR /R %%I IN ('DIR /AD /OGN /B') DO ( CALL :TRAVERSAL %CD%\%%I ) POPD GOTO TRAVERSAL :BEGIN for /F %%J in ( *.* ) do makecab.exe %cd%\%%J GOTO END

I think he just wants to know which abbrevation stands for which manufacturer... And yes, of course I've got such a list, but I thought it was included... Not then... I've attached a small html file that contains all the info you need Remark: I will rebuild the entire DriverPack MassStorage soon, with another method, which will make this file useless then... EDIT: Right-click and 'Save as'/'Save target as'

I would not know... but probably it will just work. First you'll have to get the drivers out of the exe file, try WinRAR or 7zip to do that. (Extract the exe file) Then search for any inf files in the extracted folders. Then integrate them using the guide. But my question: WHY would you buy/use that program if you still want to use the separate drivers... Just use the exe file, if you don't want to, you shouldn't buy that program imo... If you don't know what hardware is in your system, use Everest Home Edition to determine your hardware, then download the newest drivers yourself!

They *do* exist, but not for all WLAN cards. And because you're saying you've got a 108 Mbit WLAN card, I'm afraid there's no such driver available for that card. I've only seen it (IF I remember well ) for older WLAN cards...

Voila Quite often that's the problem

@RogueSpear: thank you very much for your useful comments! @rgreen83: we'll see about that Anyone else who thinks it is NOT good to split DriverPack Graphics?

Just to let you guys know, here are the changes to the DriverPacks BASE: [0%]-CAB compression when using Method 1 (winnt.sif method) [DONE]-Change in batch files structure: all unified! [10%]-Update Method 2 [DONE]-Automatically insert the OemPnPDriversPath into winnt.sif [DONE]-Automatically edit winnt.sif to install Graphics/Sound Control Panels [DONE]-Reducing number of steps. (to only THREE steps!) [DONE]-Improving updater [DONE]-Choose which DriverPack you'd like to use. (you don't have to use all of them!) Some extra explanation about the updatesystem: from now on, you will only need the DriverPacks BASE, no more separate file downloading! The updater gets the newest version of DriverPacks BASE and installls it automatically! Of course you can also download it manually and apply it... Going to my bed now... Cya guys tomorrow!

I'd start using batch files to accomplish all that... like this: ROBOCOPY "%UserProfile%\My Documents" "%SystemDrive%\Back-Up" "*.*" /E /COPY Note that you have to download ROBOCOPY separately and you have to place it in %SystemRoot%\system32. Google for it and you'll find it. Of course you can also use COPY and/or XCOPY, but ROBOCOPY is alot better AND easier.

I don't think it's finished yet

The omega drivers is only a modified INF I think? All DLLs are same?just asking... That's possible... I'll investigate that later this week... Yup, old CPL is good. The new CCC package based on .net seems not needed at the moment - plus, including the .net driver will not allow auto-detection based on INF (oempnpdriverspath) like we do currently. Well, the auto-detection wouldn't be the problem! There's no such thing as a '.Net driver' . It's just the CCC that's .Net... So I'd only have to edit the Graphics_Control_Panels.cmd file and add the installer... But that takes some MORE space, which I don't want

Hmmm.... I don't know... Most users prefer the old CPanel. For the moment I don't want to remove it. Maybe if several people ask this. I'm sorry... But what I AM thinking of is the following: splitting DriverPack Graphics in two: ATI and nVidia separated, since they have more frequent updates. How do you guys feel about that?

Oh, but I DID include the WDM drivers if they were available! And if I remember well, I found those for Matrox' G450! Or do you need a control panel to apply them?

VIA drivers also have control panels (because I couldn't remove them). That might be the case for some, yes. But please be honest: how many of us use TVout and stuff on a videocard that is not an ATI or nVidia one?

FINALLY beta2 upload has completed... Please test and let me know the results. Next beta should include support for ATI mobility...

I'm not going to include the official and the Omega drivers, that's absolute madness... I'll see how to figure it...

Erm? Aren't those included in the regular Radeon drivers???

I was wondering if anyone could help me with the cab compression for method 1... -folders must be searched recursively, each file must be cabbed. (makecab) I think the following pieces of code might be useful :TRAVERSAL PUSHD %1 IF EXIST *.INF SET OemPnPDriversPath=!OemPnPDriversPath!;%CD:~3% FOR /F %%I IN ('DIR /AD /OGN /B') DO ( CALL :TRAVERSAL %CD%\%%I ) POPD for/f %%F in (*.*) do makecab /D CompressionType=LZX /D CompressionMemory=21 %%F Unfortunately I do not have the knowledge to combine them... (No, I'm not a DOS expert, not at all...)

Did you include the 925 chipset drivers? That might be the problem...

Hmmm... Maybe this is some kind of error that only shows up in particular circumstances... I don't know... But what I DO know, is that I'm totally rewriting the batch files, to simplify it both for the end-user and for me... So that bug should be fixed in the next release. All you have to do is makecab all .sys files of DriverPack MassStorage and put them in the i386 folder

Or you could simply use the method described in official guide. That would be silent as well, AND system (hardware configuration) independant

Well, then you *must* have done something wrong... Are you using a multiboot CD/DVD?

I'm working on a big update & facelift of the batch files. CAB compression when using Method 1 WILL be included

Hey, thanks to all I guess I'll move to SAV Corporate again... ZoneAlarm Security Suite is pretty good, but I don't use the firewall anyway (and no, neither I'm using the Windows XP firewall )