Search options (Page 6 of 64)

Quote:  "What goes up, must come down" - "Blood, Sweat & Tears"

Quote:  "Greenland's 'dark snow' climate threat worse than thought
Soot and ash from burning coal, wood and dung speed melting of polar ice"
http://www.cbc.ca/news/technology/green … -1.2776628
2 million hectares burnt in the arctic versus one million in an average year (paraphrased from article)

also see Ontological's "Cesium Sky" series, especially ISS photos.

(These are not necessarily the views of DriverPacks.net and are here for educational purposes only.)

Well, by the time we get there, it would more likely be DP_Misc_Removable_wnt5_x86-32, DP_Chipset_Utils_wnt5_x86-32, DP_Misc_Removable-Utils_wnt5_x86-32 & DP_Misc-Utils_wnt5_x86-32 methinks.
Misc_Removable to include USB, PCMCIA, 1394 (et al?) removable devices (not PCI or PCIe).
Would a DP_cIR-IrDA be too "over-the-top"?

Progressing towards this style of layout for the packs probably causes complications for admin above me here though.  I like the idea of breaking things down to (hopefully) exand capabilities and choice.

Update MassStorage immediately post-Setup via SAD3, is one possibility.
I do my testing with clean untouched source discs (exc. for unattend file & some basic KB slipstreaming like Windows Installer upd or UR1 for 2k) so am not familiar if BASE can update a pre-integrated (via DPs_BASE- version???) source.
It would seem he is avoiding answering where the install disc came from though. 
-------------------
Getting back on topic; I see that Finisher uses devcon, and SAD3 uses Finisher in addition to dpinst.
Would SAD3 benefit from an updated devcon file?

  2k compatibility doesn't appear an issue for devcon.
2k has never worked for me using either SAD3.  I always received an error related to the user account on 2k.
  In addition, the links for the older revisions of SAD2 appear broken.
  For 2k driver updates via the [Nightlies], i assume a SAD disc must be created via DPs_BASE for those packs not integrated with the 2k install disc used originally on the system at focus.

I have other question concerning SAD3 (NT5 & NT6).
Is it best to avoid using SAD3 for DP_MassStorage on a non-new installation, until a system backup is created and verified?  Additional controllers could be added manually with less risk, if i have that correct.

I note this effect too for some hardware combinations.
Didn't think it was an "issue" though, more of a minor "annoyance".

Details would be very helpful, as both OverFlow & mr_smartepants have dutifully noted.

However; once the new device has it's driver installed, then device removed, then plugged into another port, it should simply auto-install the driver.

Note that i only use DPs_BASE to integrate the main driver packs, including MassStorage on a clean and (mostly) untouched xp source before testing.
Since this works for me, it should also be possible for you to repeat such success.

Have added some braille reader drivers into Chipset that exacerbate the bloat.

Looking to make a DP_Misc_Removable_wnt5_x86-32 & DP_Chipset_Utils_wnt5_x86-32 and similar to clean up the packs and ease removable device installation.  Hotkey drivers prolly need go into DP_HID.  A CIR/IrDA pack could also be spun off of Misc.

Chipset appears to be for drivers classed as "System" or "Processor", or for USB Controllers.
All those Removable USB devices in Chipset should go into a Misc_Removable pack, if i have that right.

Does this align with needs for BartPE/UBCD4Win?
Would it be better to release what we have first before making changes that require changes to the main site?

There is a HW detection bug that affects DP_Bluetooth_MS-Misc_wnt5_x86-32_1408061.7z

Will upload the fix when humanely possible.

Updated nVidia driver from v340.52 release (non-WHQL)
Ignore the list of devices supported on the web site.  This supports most devices from the old 8000-series (one new 8xxx series HWID!!!) up to and including HWID's for the newest 800(M)-series, including Quadra, etc.  Check included ListDevices.txt.  Extra files from older 2014 releases, such as nvcuvenc32.dll and nViewProfiles_fromMarch.7z are included in /D/G/N/1/xtras_DP/ for experimental purposes only and are not automatically installed.

for DriverPacks folder:
DP_Graphics_B_wnt5_x86-32_1408051.7z - 233.51 MB   CEBBA9674BA3489D42102611BD6C5EE94BC13D8F

for 3rd party DriverPacks folder:
DP_Graphics_nVidia_GFxp-upd-NET4_wnt5_x86-32_1408051.7z - 103.58 MB   AF287798DF02291621D278C86D32CB8B536644DB
DP_Graphics_PhysX_wnt5_x86-32_1408051.7z - 38.23 MB   F34514237D874D0F3BF371B60C5B0D1DD03D7049

edit: links removed - updated or reposted below.

Added Realtek Wireless 802.11b/g/n/ac USB 2.0 Network Adapter driver in /D/W/RT/3/
  {DriverVer = 01/15/2014,1024.9.1219.2013} 
There are now a total of four drivers included for that hardware, as each has hwid(s) not included elsewhere.

Optional DP_WLAN "3rd-Party" addon:
DP_WLANutils_wnt5_x86-32_1404141.7z - 214.71 MB   BCA18ACAFE26B02368D7BF6EF740C3225EB2771A

Added link for smartversion3 here and for your Gaming x64 pack.

Very impressive!