Search options (Page 7 of 8)

I swear AV technology is practically becoming worthless.

This has long been a limitation of Method 1 and it was one of the original reasons I made the switch to Method 2 a while back.  It had been discussed at one time consolidating some of the folder structure, but combining some folders together would make maintaining the DriverPacks even more difficult than it is now.

If you use all of the official DriverPacks, it far exceeds the limitation, let alone adding in some of the 3rd party DriverPacks.

Ok, that's probably the issue then.  Your source should be copied down to a directory on your hard drive so that the BASE can work with it.

Are you point the BASE at a CD or DVD ?

Patience grasshopper

There is only one mod (that I know of) here and that's Bashrat himself.  Hopefully he's working on new release of BASE to help with some of these issues.

It sounds as though there is a problem with the video adapter and the drivers properly installing during the PnP enumeration phase of setup.  I have a somewhat similar problem with a Compaq nx9010 laptop that has an ATI adapter built-in.  For the time being my solution for that particular machine is to leave out the ATI video drivers and install them manually post setup.

If you could post the hwids from that laptop it may help Bâshrat the Sneaky troubleshoot the problem.

Because when they drop support for a card that means they don't have to do one bit of testing on that card.  There could be some driver programming techniques that they would like to enable in the driver, but if they do it could make the driver not work with older cards.  But mainly, hardware companies would prefer to end support of a product as soon as you pay for it.

OemPnPDriversPath is utilized at T-39 (the very beginning) of the GUI portion of setup.  At this point your NIC has not been installed yet, therefor it cannot access the network to get the drivers.  The "best" way to do drivers w/ RIS is to use Method 2 and just copy down all of the DriverPacks to the system drive.  Method 1 will work just fine, but now you're doing a copy operation on an additional 5,000 or so files.  Much faster to copy a dozen larger files than thousands of tiny ones.

To back tack a little here - During the PnP enumeration of devices you probably notice near the progress bar that it says Installing Devices (or something similar).  The very next thing after that is "Configuring Network".  It's not until that is finished that you have network access.  Cmdlines.txt has full blown Internet access for instance.  I know this for sure as I download files to the target computer during cmdlines.

I made a DP for VMware Workstation V5.5 and it was updated by muiz to support V5.5.1.  It's still available in the 3rd Party DP sticky thread at MSFN.

I wasn't trying to say that you were reporting a bug in your post.  I was just saying that if you run into some problems to try out the install using the original DriverPacks and see if the problem goes away or not before making a bug report.  I don't think there's any problems with what you want to do or with any questions you've asked, just a little misunderstanding is all.

The only suggestion I would have for you is that if you run into some sort of problem with your modified DriverPack, try again with the real DriverPack to see if you still have the problem before reporting anything as a bug.  Also, if you remove drivers from DP Mass Storage and chose to do a mass storage text mode integration, some things could be seriously thrown off.