Search options (Page 136 of 213)

UM no... Sorry LOL i thought you were more familiar with the layout

It's in the 'Feature Requests' forum and it is stickied to boot

OK we seem to be picking up momentum... I hear you guys

added to To Do list...

added in DriverPacks BASE ver 8.09

edit the Finisher INI (DPsFnshr.ini) and add this line
DPsRootDel  = "false"

added base ver 8.09

if you rem the echo off line all instructions in the file will be output

the line immediatly preceding the error is the line that is complaining

Once we know which instruction is crying then we can proceed to the 'why'

Try google for noob questions... not here

answer... probably universal extractor and makecab.

I am sorry i put that fast ball right past you... i will switch to slow pitch...

it is a PITA to do what you are asking to do "DONT DO IT". (insert you asking why)
1 you have to manualy script the install of teh driver (rundll32 or api call, Devcon, right click or WhatEver...)
2 and or then you have to use devcon to update or delete the driver
   (some drivers have to be removed then installed)
3 If 2 above is a delete then we must use devcon to update the driver
4 many drivers have control panels or orther software that must be scripted too like Intel proset or similar  software)

all very complex and can fail at multiple steps... Why kill yourself?

we have SAD - Stand Alone Driver installer

It is easy to use SAD
1 Use DriverPacks BASE to create a SAD folder selecting the LAN pack and Method 2 (M2).

thats it... Why make it any harder than that?

just call the DP_INST_TOOL.cmd from a machine you wish to update.

if you dont want the entire pack you could either prune the main pack or make your own 3rd party DriverPack and just "steal" the section of code from the packs INI for your folder (if any) and the driver folder you require, making sure you maintain the layout D\L\*.* and repack with 7zip. (A custom pack for one driver is easy to do but not really neccessary,... unless you feel you must) 

you can lead a horse to water...
let me know if you need anything

Glad we were able to get you up and running...

I am still curious why this happened.
We might be able to avoid this or a similar situation in the future with that answer
I am still hopeing the UBCD4Win Guru's will provide more info as to the 'why'...
this should not have been an issue, yet it was...

I am a hard core individual... (you may have felt some of that energy)

I would not in good concience slipstream a mass storage controler without first slipstreaming the chipset driver that is its foundation... Others may do this and have success with it... not good enough for me. Do it right or Don't do it... chipset must be included and precede mass "anything less would be uncivilized"

SAD M2 - check the home page and the FAQ... (I cant post things any more visibly that those two places!)

if you want to do as you described tehn after you right click install the INF then you must go into device manager and remove teh "unknown device and then right click the list and "Scan for new hardware"
What you did will work you just didnt finish the process

ps if you 'right click install' the INF/Driver before you add the hardware (software preinstall) then you don't have to remove the unknown device. (because it won't be unknown when it is found since you preinstalled the driver )

PSS put another way... Just adding a driver won't cause windows to re-enumerate all the installed devices (thank god!)