Bâshrat the Sneaky

Odd. By the way: the .cat file for ich4id2.inf was also incompletely copied. Fixed in DriverPack Chipset V5.11.1 Bug fixed, topic closed.

What about.... -using Daemon-Tools to mount the .iso and let VMWare use the virtual drive of Windows. -or creating a share, make sure your VMWare has a (bridged) network connection and log on to the share (or FTP or...).

Maybe you should take a look at your server's log... infected with twenty viruses. Or maybe it's your network infrastructure that can no longer handle all the traffic - traffic that's caused by the 20 thousand keyloggers on your pc's. Perhaps it's just your HDD that's dying. Or a process on the server that consumes too much CPU time. Point is: you should give us a *bit* more information. We aren't sorcerors, you know. P.S.: no offence intended. Just wanted to put it the funny way... Well... if you can't laugh...

Hmm... don't have the time at the moment to investigate this problem deeply. Maybe you should look for the cause in YOUR way of using 2 setups from 1 disk. Try multi-boot instead of hacking.

Which method?

LOL, totally forgot about this request. Implemented in DriverPacks BASE V5.11.6, which should be released this weekend. EDIT: Request implemented, topic closed.

1. Tell me what sound card this is. 2. You MUST be doing something wrong. It's impossible that the file doesn't get copied to your I386 dir! Nor is it possible that your dosnet.inf isn't updated. Apparently your SVCPACK.INF doesn't get updated either? But how can your TXTSETUP.SIF file get updated, then? You must be doing something wrong

Then why don't you just submit your problem? Open a new topic in this forum and you'll get help! Supporting all computer hardware IS the DriverPacks' purpose!

Thanks for confirming.

You're doing a network installation, you say. Any chance you copied the wrong dosnet.inf/txtsetup.sif (an older one, unaltered by the DriverPacks BASE) to your distribution share?

@Ruudboek: because the 5.11 nForce 3 drivers were not yet online at the releasedate of DriverPack LAN V5.10.1! @5eraph: MANY USB ethernet controllers are supported! @mickmack: ethernet drivers are NEVER big, unless they come with some (most of the time) useless control panels.

laura, you're also having problems? gilesw, I think this is a limited case. If it weren't limited, I'd have received much more complaints

Hi Teasy, as you can see I've split the topic. The topic where you posted should already have been closed, hence this move. 1. Did you use RyanVM's UpdatePack? If so, which version? 2. Did you use nLite? To do what? 3. In what order did you use my DriverPacks and any of the above?

Here we go.... Problem #1...

Hmmm.... Interesting Any chance you are able to get some DRIVERS out of it instead of an application? I'm just *hoping that somehow drivers are involved and that it's not an application 'in se'. If you can confirm the absence of any drivers (except for the mass storage driver, of course), I'll immediately integrate the VMWare Tools in my DriverPacks.

And with which driver version you did NOT have this problem?

True. But you could delete some of the larger drivers...

hehe you're welcome This one (this version) can simply be copied.

Hey, that's nice! Thanks

Yes. Just go to Device Manager, right click on a device, 'Update Driver', ('No not this time'), 'Install from a specific location (Advanced)', 'Search for the best drivers in these locations:', 'Include this location in the search:', <navigate to the drive where you've inserted the drivers CD> Et voila

The problem is the amount of HWIDs, not the amount of drivers.

Hmmm..... Odd problem. Please retry with a new UWXPCD from scratch. That might fix it...

A very complete answer. Any progress, polopolo? And about what drivers are you talking? If they'd fit into any of the current DriverPacks, I'd add them.

Exactly my point of view. That idea of collecting all HWIDs was also my idea, but it IS very VERY difficult to apply.

Download link fixed.