Bâshrat the Sneaky

Can somebody point me to this driver? I've been searching for it FOR TWENTY MINUTES without any result! EDIT: it seems that this is a PHY, which means that it's just a PHYsical layer (interface), for the onboard nForce 3/4 Gb LAN logic... Am I right? This is the first time that I've seen this...

What I think? Someone is REALLY obsessed by UA

Open the .inf file in a text editor, go to the SourceDisksFiles section; you need all the files listed here.

If you don't know which files to use, please first read the guide!

That's why it's a teaser I haven't planned everything in detail yet... which is why such a general description was more in place! P.S.: closed the announcement topic, added this topic, so I could add updates.

Ghost82 is correct. 64 bit versions will not come before version 5.07 (that's July), because my exams start in 3 days and last till the end of June.

I agree, partly. The very fact you're posting that remark lets me know that you have 256-512 MB RAM. Any higher amount takes VERY long to write to the HDD, so long that you'll prefer not to use hibernation!

Not as far as I know...

If you really want to send it: please 7zip it using the Maximum setting or so. That should reduce the size to 100-150 MB. Additionally, use the split volume function to split them to multiple 10MB archives. Then mail them to my gmail account (can be found in my profile). If you'd rather not send this huge amount of data (at least for me it'd be huge to send... I've only got .5Mb upload), a list of supported printers would be ok too. I just checked HP's site and I must admit that their site isn't too bad to download drivers.

eh... you MUST be kidding! That 'devices not installed in device manger' thingie, did that occur in VMware? If yes, I'm afraid I'll have to punch you in the face! Shame on you!

I wonder the .inf files need no hacking in that case?

I strongly doubt this will solve the problem... At least until anyone else could confirm it?

Eh.... how many MB's are all full packages together? I'd prefer the full packages.

Hmm I did not notice that one. All the other 4153 Device IDs are brand-specific... I guess adding it would still be the solution...

a) All but one problems have been solved; the remaining problem will be addressed in the upcoming update. B) No. Your RunOnceEx.cmd could be named ANYTHING, and how in the world would I find out in which file your ROE entries are stored? That's why I'm adding a ROE batch file from myself. And yes, it should indeed be listed as first in the cmdlines.txt file, that IS that one problem that will be fixed in the upcoming update. c) KtD: the drivers will be kept after the installation finishes, i.e. IN Windows. If you add new hardware or replace the current one, the chance is VERY high that you already have a driver for it: it automatically integrates into Windows. It has nothing to do with your UWXPCD itself. And be a bit realistic... how can many hundreds of drivers possibly fit into 6 MegaBytes???

3rd of June 2005 I'm sure many of you have noticed how many times my website (BTSunattended.net) - the 'mekka' for DriverPacks - has been down. I am - just as you are - very annoyed by this issue. In order to avoid this in times coming, I've decided to switch host - as my current host cannot meet its promises concerning uptime (and speed too, actually). "A teaser? A DriverPacks teaser? What the f*ck could that be?", I hear you wonder. Well, I won't go into details but I'll tell you this: this project will walk a more professional path in the (not so far) future... You can post comments here.

Feel free to comment the announcement here.

Yes! At least, if you also use DriverPack MassStorage! I hope you understand now.

The name of that folder doesn't matter - in fact it is different for every user, it's just an example name. So you DON'T have to rename your XPCD_SP2 folder!

Something like: Options > Settings > Automatic-updates: OFF Just search your settings page and you'll find it... If not: use the built-in help!

I strongly agree with MDGx. Maybe we should remove this 'time limitation' and change it into 'depending on number of posts'. I guess these 'abuses' were mainly made by newbies?

M2 wouldn't work for network installations, that's true. But I hope you now that winnt.exe only supports 1024 characters in the OemPnPDriversPath, while all DriverPacks together use ~3600 characters if I remember well, which implies not all drivers would be detected....

eh.... That's an odd behaviour! It should compress ALL files except for the .inf and the .cat files... But apparently it removed some??? Are you using the latest version?

Before I need HWIDs, I need to know what soundcard it is EDIT: moved to DriverPacks General Discussion, that forum is more appropriate.

Then you misread: the $OEM$ folder is NEVER there by default. Possible exceptions: an OEM installation disc or an (illegal) _custom_ Windows XP _retail_ disc.