its in a great big text box... how can you miss it???

mr_smartepants wrote:

@echo off
START %systemdrive%\D\SAD2\DP_Install_Tool.cmd

227

(7 replies, posted in Other)

it's not spam, that is our system. Once it gets added a mod or admin will re-title your post with [IMP]lemented. big_smile

it has been my experience that a usb3 attached thumb drive disappears during setup, and must be removed and replaced to launch setup, otherwise it will insist that it can not find setup files. (did you try looking where these files came from... Duh!)

it has been easier for me to just fly with usb2 speeds, not sure how the disappearing drive issue gets fixed yet.

Thanks old friend,

I keep trying to get my ass in gear around here, free time has been like platinum for me. the way you are doing it is the traditional way. Grouping them may make sense given the huge amount of drivers that need updated.

Wana take a crack at putting a NT6 pack or two together?

thanks for reporting what needs added that helps a lot!

Jeff

thanks again!

231

(11 replies, posted in Windows 7 tools)

Let us know what works for you, the DriverPacks team, members and lurkers alike may all benefit from your experience big_smile

232

(11 replies, posted in Windows 7 tools)

Yes I have seen it.

I tend to take a more hands on approach.

233

(5 replies, posted in Vista / 7 DriverPack Mass Storage)

We are going to be updating these packs soon. Which way do you think is better?

234

(11 replies, posted in Windows 7 tools)

answered in my first post.
let me elaborate:

Use DISM to add ONLY Chipset and Mass Storage (and USB3?) drivers to your source. They are small packs.
(I put them right in my install and boot WIM files of every install i have)

SAD - Stand Alone Driver installer
put SAD (with NT6 DriverPacks) on the source (to be cloned) drive.
Call SAD from setupcomplete or whatever.
SAD will only install drivers that are required per machine.
(This is what you said you wanted... and that is what it does... reread last line)
Delete SAD from setupcomplete or whatever

Might as well use the entire set of drivers since once the SAD folder is deleted only machine specific drivers will remain.
this will add a huge amount of size to your source, but since you are using a disc duplicator who cares?
The advantage here is any hardware is supported.
the target will not suffer the loss of space after deployment (since we are deleting everything we don't need)
mr_smartepants suggests that if you have a small number of machine types (perhaps they are all DELL) then you could make a custom driver set just for you to put in your SAD folder to save space and time during the copy. (Optional)
The advantage here is space and copy time, but you give up the ability to deploy to a black box.

this will add minimal size to the target with maximum compatibility to any machine (black box).

again same answer as first post use SAD!

PS I love companies that would rather pay me than buy tools... more for me big_smile. You can lead a horse to water...

PSS you could put SAD on a thumbdrive and run it manually after the drive is installed in the target. That's why we call it Stand Alone big_smile.

PSSS Or you could put it on a DVD and use autorun big_smile big_smile. (convenient but slow)

235

(11 replies, posted in Windows 7 tools)

thinking out loud. they have the money to pay techs for lots of hours of time to remove and replace drives.

15 minutes a PC to pull and replace a drive, (being kind). 100 PC's x 15 minutes = 1500 Min.
1500 / 60 = 20 hours or two and a half days work.
not counting the copy time.


So
1 Spend money on labor for three days tech time  (Based on 100 machines).
2 OR Buy Ghost and do the whole job in about an hour.

depending on your actual time, and the cost of that time, it may be an option.
especially if you buy an older version of Ghost online wink
I have used version 8.x (well over ten years old) to copy windows NT6 drives with no issues.

236

(11 replies, posted in Windows 7 tools)

Welcome to DriverPacks.net,

good question, short answer,

Sysprep always seems to have issues, DriverPacks (team / site) does not directly support it, many of our users do. Whether you sysprep and disc duplicate or deploy from USB or disc with an installation image your best bet is to use DISM to add mass storage and Chipset drivers to your  base image and then run our SAD2 script from SetupComplete.cmd or similar for the remaining DriverPacks. in this way the deployment image and the target machine are not bloated with unneeded drivers.

SAD -> first Stickied topic in this subforum. (  Stand Alone Driverpack utility for all OS XP, 2k3, 2k8, Vista, Win7 )

I know you said you can't deploy from server because you don't have one, BUT with Norton Ghost you can do a one to many copy. it's very slick. I have done this with over a hundred machines at a time, and you don't have to take out the HDD's big_smile. simply prepare your master, Boot up from usb, disc whatever and run Ghost Server on the master (this machine is now your server) they do this very slick, you connect all the client machines also with a ghost boot disc or USB. Then they use multicast to deploy, thus there is NO increase in network traffic per machine, 100 uses the same as one, true multicast. Plus you don't have to pull and replace the drives. Just throwing it out there big_smile. (This works even better if you have a large number of identical machines because you can skip sysprep, Ghost automatically fixes the network and machine (ssid) info to be unique for each machine big_smile.

Thanks for the kind words

Jeff

237

(18 replies, posted in Windows 7 Discussion)

Welcome to DriverPacks.net d4rkcell,

We only have one person actively working on the packs ATM. He is almost Done with final updates to the NT5 DriverPacks. They will need less and less if any attention going forward. TechDud believes that NT6 packs may start turning up soon.

You can certainly help by posting HWIDs of missing drivers and links to known working drivers that match that HWID.

In the past we had a team of people updating packs, each one has it's own idiosyncrasies and some people would do certain packs, mrsmartepants was the only one updating all of them for way over a year. And he is the only one besides me that knows how to do them all correctly. Techdud has fought his way through all the toughest packs we have and is ready for the fallout of his first releases (LOL).  With each iteration of NT PnP gets a little better. Back in win 9x days we called it Plug and Pray. NT6 platforms are the best yet and as a result are easier to update without conflicts. = should be updated with very little lead time.

Let us know what is missing and we'll get it in there big_smile

Thank you for the kind words !

238

(12 replies, posted in Universal Imaging)

Do you have the HWIDs from that machine? Rebooting is usually HDD Controller driver but not always.

What version of the packs did you use on that machine.
You tried XP, and Win7 OS's?  list packs for each (versions)

We are getting somewhere now big_smile

HInt check the setupapi.log I assure you there is an error, just because you didn't get a blue screen doesn't mean there was no error recorded. i have suggested this multiple times now.

did you use DriverPacks BASE to add mass storage to your XP source? Was your source(s) clean OEM disc image?
although you have now revealed that you are using xp and 7 32bit, no service pack levels / updates were indicated.
So we STILL don't know what source(s) you are using.

can we get this together. normally we are this far half way through a first post... it would be nice to get all the first post info together before say post 20 tongue

Do you also have a post going at wintoolkit we could refer to? you are really making this painful for us.

239

(11 replies, posted in DriverPack Graphics)

I keep hoping that if i stick around long enough I'll be able to count to ten

there are a couple alternatives. they boil down to two main catagories. Wait and Help.

Nice Work TD!

UBCD4Win IS BartPE... It has just been preloaded with the right combination of plugins to make life SIMPLE.

if you look there is good old PeBuilder... just as expected.

If you can do it with BartPE you can do it more easily with UBCD4Win's version of BartPE.

If you have a workin BartPE plugin for your needs just add it to your buld big_smile.

243

(20 replies, posted in 3rd Party Vista / 7 DriverPacks)

I use [REQ] "in topic subject" as as a search to find things to add... New topic is best bet

many drivers have dependencies, other plugins like HWPnP.

try building BartPE with UBCD4Win, if that works (and i know it does) then you are missing one or more plugins that support your drivers.

Remember it's PE not windows, just because you add something doesn't mean it will work, at least not without doing some preparations first.

UBCD4Win has all the dependencies included and debugged for you, it even includes the DriverPacks plugins already big_smile

PS IDK if 2k3 r2 is compatible with BartPE???  If UBCD4Win fails try 2k3 (not R2)

245

(12 replies, posted in Universal Imaging)

there is a link in my signature. Read BEFORE you post.

check each numbered item off as you add it to your post.

the answers will follow.

you state problem (as outlined in READ BEFORE YOU POST)
IE in a clear manner with versions and steps taken
with the primary info already requested three times.
what failed? when and where.

246

(12 replies, posted in Universal Imaging)

Still no clue as to, what he is doing, or how, on what OS, (or why), One more useless post (not in compliance with RULE 1) and I am going to ban him.

I HATE that.

let me put the shoe on the other foot...

"I have a problem."
"So, how soon can you fix it."

Fix what??? your lawnmower? your cat? your roof?
Sorry i can't fix stupid.
- It's not possible to solve an undefined problem.

i try to look at things from multiple perspectives, Practical is normally a good one.


Really nice link there. i am gonna try that right away LOL.

248

(12 replies, posted in Universal Imaging)

It makes no sense, that was why i asked what he did

let me make it simple for you.

Even with a current OS there is no protection against a zero day threat.
It often takes MS and the Antivirus companies a month to discover threats and update their files and databases.
In MS's case obviously only supported OS's tongue.
which is only partially true, they did just release an out of band update for IE didn't they?

IT's all SMOKE and MIRRORS. MS OS's will always be vulnerable, Currently supported or not.
A secure windows machine does not exist.

I will repeat. Run a good AV. Have a Drive Image with ALL the updates ready to restore it.
User files should always be handled the same way, if you value it back it up.
If it's critical back it up off site too.

This is how every machine is treated, supported or not.

Are you really trying to tell me that just because MS supports an OS that i WON"T get exploited???? REALLY??

Come on, be serious.

Every machine is a target, supported by MS is not at all relevant to any user who either can backup restore or else knows someone who does.

I guess what I am saying is if you NEED to run XP for whatever reason you do so with no more or less risk than any other day on the net. Protect yourself a reasonable amount and know you are gong to take some lumps some day. (And that is different from normal how?)

did you ever get the file i sent you?

if not shoot me an email, from an account that will accept an attachment from me.