Bâshrat the Sneaky

I really think that would be easier. How are documents saved of the employees? On a share or on their hdd's?

hmm... That's not quite handy: you'd have to specify which inf file, so it won't be system independant anymore that's true, but u can possibly use this in a domain to write a script that checks the department of the user (or any other info in the domainprofile of the user) and that way identify wich printers the user(s) need. Anyway: a Printerpack would really be a good idea as alot of modern printers are USB-Printers so windows auto-detects them and always tries to install the drivers! (there are even printers on a parallel cable that get detected by windows) OK. Then the DriverPack Printer will only support plug 'n play printers, untill a decent solution has been found.

Why upgrading? Why not back-up settings & documents (which is probably already done) and doing a fresh install?

That command just sets a printer as default printer and renames it to printer1... What about that app?

hmm... That's not quite handy: you'd have to specify which inf file, so it won't be system independant anymore

I'll investigate that one.

Yes, I do. 7zip compression for Pyron's method and CAB compression for the regular method. However this CAB compression is not yet available! However, it should be released tomorrow.

mp4 (aac), wma, mpc, ape, ac3

Congratz! B)

I don't know it exactly but I do know these: 1 star : 50 posts 2 stars: 100 posts (not sure) 3 stars: 250 posts (not sure) .... 7 stars: 1500 posts (not sure) 8 stars: 2000 posts

he doesn't add anything to the dosnet.inf file? I've always been told that was necessary for WinPE... Now this is EXACTLY what DriverPack MassStorage does... except for those dll and sys files. They won't be copied to I386\system32\drivers and i386\system32, but to i386. If you could tell me if there's a 'tagfile', by which I can detect that it's a WinPE/BartPE disc, I'll add support for these.

Just to let you guys know: the new DriverPack MassStorage will keep on using the old method for most drivers. In fact, I think I have a method to determine which method should be used: - IF a driver consists purely of : .inf, .sys, .cat files > use the slipstream method > make it part of the source > the method that was used before - IF a driver contains ALSO: .dll, .exe, .??? files > use the regular method > the txtsetup.oem method > the method that's added in this new version. Another remark on the method that's been used on the previous DriverPacks: RyanVM didn't add different names for each PCI DeviceID (for example the Adaptec drivers: they ALOT devices, with different names). So if a device used a driver A, it was named "controller A". But now this has changed: if a driver A supports devices A.1, A.2, A.3, etc. , these devices will be named A.1, A.2, A.3, etc. ! This may /look/ easy, but it isn't... It's a HUGE work (several of Adaptec's drivers support +-15 of different devices (device ID's > names), which all have to be added one by one in the batch files... It *could* be that I won't be able to finish it today... Then the goal is tomorrow.

Dunno... Please test. I don't have the time ATM.

Yes, you could use the SetDevicePath.exe utlility for that, which is used in Pyron's method. Simply use Pyron's method, but instead of using %SystemDrive% or %CDROM%, use D:\. This means you will have to make sure Windows sees the partition/harddisk you've put your drivers on, as the D: drive!

I knew it! Why would you need an utility? That's only required for Win9x and Win2k, while this DriverPack is meant to be used with Windows XP.... So what special setting can't be set with the Zero Configuration Wizard of Win XP?

I'm afraid NOTHING comes close Maybe that's a nice idea for a new projects: an iTunes installation WITHOUT QuickTime, but WITH the necessary codecs? Good luck!

Method 2 is updated! And method 1 will have CAB compression indeed!

Of course! Without a doubt!

In DriverPack MassStorage V5.02 they will still be there, but they will be updated! I hope this will solve your issue.

I suppose that should be every *month*

Wow! HUGE project! Don't loose the motivation!

Probably there isn't a fix. So I suggest you keep on using the Catalyst 5.1 untill it's fixed. You may want to inform ATI about this issue

Indeed... Because then no installers will have to be executed to apply the hotfixes, they become part of the regular installation!

I hope you are using a conditional installation? (i.e. IF EXIST driver.sys START /WAIT setup.exe /K)

Indeed. But I'll update it soon and automate the editing as well