Search options (Page 57 of 213)

You must AT LEAST include your DPs_BASE.log, and include proper details.
(See 'Read BEFORE you post' linked in my signature, check off each item as you go.
It was also on the rules page you had to agree to before posting )

IE Am I supposed to guess which of the forty or so versions of DriverPacks BASE you are currently using? I mean it could be an Alpha, Beta, Nightly, RC, official release, current, older, ???...

Did you use M1 or M2? (Neither method copies DriverPacks to the root of the disc BTW.)
Were you slipstreaming Win2K, WinXP or Win2K3?
Did you select only main packs or 3rd party DriverPack too?
did you only select only Mass or all main packs? (or other combo) Was mass textmode enabled?

You might as well have reported "My car won't start. Help!"
The details are obviously to vague to offer any kind of help. I might guess you had no gas in your car only to find out you drive a Diesel .

Help us to help you. Details are the key, 99% of these details are included in your log, which is mandatory for a support post...

YES!
Right!
YES! That Whole [NV8] section removed ...

I think the best thing to do is to add the RIS driver cdob pointed to by adding it to the  <UBCD4Win>\drivers\ folder and not use DriverPack LAN at all (disable or delete the DriverPack LAN plugin... does that work?

I already said that RIS drivers were a better way to go ...

if that works we delete all the NV folders from BartPE by using the mass INI file adding the skipIfOS="wxp,w2k3" exception. (or we could call it a flag... which should have the same effect as removing all the NV folders from the pack ) and add the RIS driver to the pack (NV9 ?)

Sorry about my sabatoge / N8-NV8 typo!

Can you provide a link to a driver that you know works properly for this device?

strange that it reports itself as an ACPI device rather than a USB device
(drivers are installed by HWIDs if the device itself does not report properly that it's a USB device then the device [hardware] is the problem)

Input wnt6-x64 10.02

link repaired

Yeah sound is not yet ready to go...
The UBCD4win team needs to work on the HWPnP plugin before sound will work reliably
that is why the sound packs are somewhat disabled .

the NIC really has me stumped...
In theory if you removed N8 then what i gave you should be close to, or identical to, LAN 8.12.1...
Hmmm... back to the drawing board.

I am working on BASE ATM if one of the PacksTeam doesn't get to it i will take another look at it after i get the DriverPacks BASE bugs fixed !

PS drop by the driverImportPE thread here and give some props. that way others may know it works, and the author can get some props! http://forum.driverpacks.net/viewtopic.php?id=3217

Well we don't need updated drivers... just the old / original ones, they may be still on the site but just not linked anymore .

well it looks like Catc was bought by lecroy and while i had no problem finding the owners manual, drivers were not so easy to find and their site is so slow i got the impression that it is hosted on a dialup modem

here is the link to the owners manual

perhaps an email to lecroy may yield a link to an archive of drivers somewhere .
ftp://catc.com is still live but anonymous access is denied
same for lecroy...

All missing drivers are welcome! The point of our project is to be all inclusive .

I checked and they are in fact missing from the LAN pack.
- I still have to check to see if they are already included in a 3rd party DriverPack...

Thanks for your excellent details and links in your first two posts.
It is rare that I don't have to point a new user to "read before you post"

Very well done! Cudos!

Welcome to DriverPacks.net and have an awesome day!

Jeff

PS We will have to see if we can help you to find some better links... keithm is definately not an OEM or manufacturer source, and driverguide is not really a primary choice either... We only accept drivers from original sources, like LinkSys, Dell, Gigabyte, Nvidia, Intel, ATI, etc...

Good teamwork guys!

Not a bug... More of an undocumented feature   -  Adding the rest of the DriverPacks is NOT supported .
(It is also possible to do this manually from DPs_BASE.INI)

The rest of the packs, especially DriverPack Sound A and DriverPack Sound B, will fail on most hardware. The plugins that the remaining DriverPacks depend on are not mature enough to support them. The UBCD4Win team, especially Hilander999, is working on updating the plugins they depend on so they will work.

I initially wrote the code to add ALL the DriverPacks... and then disabled chipset and sound because they were / are not reliable. DriverPacks.net always chooses / presents options that do not lead to problems. Selecting Chipset and Sound WILL lead to problems .  - Note that selecting chipset will quite likely kill any Nvidia based network card you may encounter . Also note that selecting chipset will not benefit you in any way. IE since mass storage drivers are the text mode versions (not the PnP enhanced mode) they won't run any better (and may kill Nvidia based ones) if the chipset driver is installed. Remember PE uses only text mode drivers (16bit) so the only benefit might be a cosmetic one in device manager. If Highlander finishes updating the HWPnP Plugin that may change... The problem is thousands of lines of registry entries simply do not exist in PE...

PE is NOT a windows OS! its an installation / recovery tool PE = Preinstallation Environment

I would thank you for reporting... except you did not mention whether or not it worked

PS I NEVER said it was not possible.
I said it was not supported and it is not supported.
It's Not supported by us, nor by UBCD4Win nor anyone else .
I would very much like to hear how it works out for you!

True!

I am almost done hashing out the GUI issues with DriverPacks BASE, stay tuned!

BartPE ONLY uses the text mode drivers

And it only uses drivers as they are listed in the mass storage ini