Bâshrat the Sneaky

They're both very easy, as the DriverPacks BASE does all the hard work for you... But if you use M2, you can simply copy the new archives and copy the new control panels batch file. (exception: DP MassStorage)

I'm back Reading everything now (****... typing feels so strange... haven't touch a keyboard in two days ) @codejunkie: fixed. @BAM & erik_demon: Checked and indeed it was missing in the list of to be deleted files... Will be fixed in the next version. DOH I had posted a very long reply here, but your posts kept coming.. Eventually it appeared that you had solved it by yourself... I will include the %SystemDrive%\D removal at the end of the CPLs batch file then! @imdos: ****. I think this is some special case again. But please try this first: *disconnect* your network card and then retry the installation. I think this might make the difference! (Someone once, long ago, reported that this fixed his (similar) problem.) @Vid0: If you keep on posting so cynical, you'll get cynical answers. The 'EXIT', 'is it necessary', well... this is my way of writing batch files, if you don't like it, rewrite them for yourself. IF you want to criticise me, then do it the RIGHT way. First of all, tell me in WHICH DriverPack you found such files. Second of all, SEARCH better. The .gid ARE removed, learn to search! Not to mention.. 'damaged LAN drivers'? LOL You think files with an underscore in their extension are damaged? They're CABBED then, that doesn't mean they don't work. Well, if this *were* true, ok, but it isn't... There are no CABbed files *anymore* in DriverPack LAN... Are you too lame or did you take the effort to download the newest DriverPack LAN? And yes, there seem to be 9 *.pbd files in DriverPack WLAN. But couldn't you just tell me that on *nice* way? And then again the 7zip version... No, I didn't include the newest version. But that was rather because of lack of time than out of ignorance. And I can *assure* you that there is no difference you will notice between 4.16b and 4.18b (yes, you also didn't post the newest version... (it was already out when you posted it)). Your second post is more reasonnable, so I'll answer reasonnable. What changes did you made? And what debugging script? Thanks for those 2 bugs, looked over them @glent: on what hardware configuration is that? ... oh problem is fixed @laza: I have the EXACT same problem. But as this problem does NOT exist for others, it must be caused by nLite or RyanVMs updatepack. (Yes, I just started using them too, but now I'm seriously thinking of going back :s) It seems very unprobable to me that it's being caused by RyanVMs updatepack, so I suppose it's an error of nLite?

If I kept them for after installation that would be better for new hardware added right? Othwise id be using XP's base drivers. > of course If I did method2 (which I have seen does not use winnt, or doesnt have to) how would I be able to keep updating it, is it basically the same thing? >Keep updating it? Then you'll have to extract the DriverPacks each time and first delete the old one. Of course this can be automated too, but that's not the goal: if you add new hardware, you should in fact reinstall Windows and at the same time it will run faster again (fresh installs are almost (yes, there are exceptions) faster.) Also should I keep 2 versions of my uA cd a non driver installed one and a driver installed one? >Not necessarily, but it will never hurt, if you get what I mean

Why would you need to reinstall all your extensions? Only a few got upgraded for use with FF 1.03...

DriverPack WLAN V5.04.4 Download And the requests a few posts higher have not YET been included, because a lack of time

BTS DriverPacks BASE V5.04.11 Download Fixed: everything stated in this post Enjoy a really stable edition of my DriverPacks I'll be on a trip of 2 days to Germany (nach Köln, Koblenz und Bonn), so I won't be here to respond to your questions. See you guys saturday!

You TOTALLY misunderstood me. If drivers only used for installation => method 2 is the space-saver. If drivers are kept AFTER the installation => method 1 is the space-saver. What do you mean? They're included in DriverPack Graphics A, including their control panels. No problem there. The DriverPacks BASE handles all this. (that's the 'back-up of winnt.sif made' etc. and the 'previously slipstreamed [method 1] DriverPacks removed' etc.)

Workstation not loaded... what kind of error is that? Is it rather exceptional or rather common?

Well, then it's related to your system or internet connection, I'm afraid! You just installed a new system or updated to newer drivers?

huh? You're the first one EVER to say this... Are you sure you didn't make any modifications? Are you sure the archives are INTACT? (use 7-zip and apply the 'test archive' function on them)

Can't do anything about it ATM... It's been working for some... I could post them on other servers... if someone would offer me some nice bandwidth unlimited servers. (i.e. university or ISP webspace) ATM they ARE on a university server. I have absolutely no clue why it isn't working as it should anymore!

The OEM folder should stay where it is. If you want to move this as well, you will have to make alot of edits!

Method 2 is definetely space-saving. That's the most important pro. Also it is modular. Method 1 might be better when you are planning to keep the drivers, because it takes less space than method 2 (all drivers uncompressed). This is only useful when you want to KEEP the drivers.

I don't use any of them, but IMO drivers should be 'universal', i.e. useable on all Windows versions. Even better would be if they would also be completely cross-platform: also useable on Linux, Mac OS X and others. But then I'm living in a dreamworld. Well, let's face facts: drivers are NOT universal and ... time is money

Huh? It's working here... Which browser are you using?

First of all: of course it went just fine in VPC (or even in VMWare, doesn't matter), because it EMULATES SOME hardware NOT YOUR hardware! Maybe you would care to tell us how you're installing (from CD, from network, using RIS, using winnt.exe/winnt32.exe) AND what modifications you made to your txtsetup.sif and dosnet.inf?

OemFilesPath is more common when you're installing from a networkshare. Apart from that, it's not used often.

No problem mate! (typied )

Nope

You got a typo's to, erik_demon: Their => there mentiod => mentioned B) And yes, I knew about that last one.

OK, this is what I should fix: 1) automatical removal of $OEM$\$1\DP folder (is now updated to D, but forgot legacy support... :blink) 2) a visible WARNING that says you should put it in a folder without spaces in the path! 3) fix the bug in DP WLAN: shortcuts instead of actual files (this is the case for only 1 out of the more than 250 drivers) 4) deleting presetup.cmd properly (only the case when you use M2, keep drivers) 5) anything, guys?

And that line is wrong... it should be 'D' instead of 'DP'. Is that an original quote?

Those lines are quite old... I doubt you're using the latest DriverPacks BASE?

Double post, bledd... Why couldn't you? It's just so that not all drivers are included in the DriverPacks: those who are already in Windows XP are left out!

This is very possible... You're the second one to report this, so in fact it's even probable. Anyone who's having problems, please test this!