Search options (Page 81 of 213)

Excellent post Welcome.

Try this

[3C]
ms_count=1
ms_1_deviceName="3ware Escalade 7000/8000 ATA RAID"
ms_1_tag="3wDrv100"
ms_1_sysFile="3wDrv100.sys"
ms_1_hwids="PCI\VEN_13C1&DEV_1001&SUBSYS_100113C1,SCSI\Processor_3ware__RAID_7000_8000______"
ms_1_isBusExtender=false
ms_1_exc_disableIfOS="w2k"

and report please!

I thought firewire was natively supported...

Let me know if you get stuck... but should be NP

I take that to mean you verified and redownloaded the pack as I suggested.

Which means NO you did not fix your own problem...

You have provided multple examples of your lack of ability, experience and intellegence.
Yet you can not admit:
You did not follow the given directions.
You did not read the documentation or rules / guidlines.
You did not follow the link to read before you post... even though it was provided multiple times.
You did not respond to any of the multiple requests for simple info.
You did not admit you did not verify the download.
You did not admit redownloading a corrupt pack was the fix.

We can even more clearly see you lack the self esteem and balls required to make such an admission.
We can also see that you are unable to solve even the simplest of issues on your own. (corrupt download)

Sorry about your users. Because they must suffer through with someone as lame as you as thier support. God help them.

(now that is insulting - to your users i mean)

PS I think it is crystal clear which one of us can not read simple words...

Please Search the forum for "Attended setup" Or "Repair", Take a look at Feature Requests... (this topic is sickied there too.)

This is documented in over 50 threads... and this is the second time asked this week.

We do officialy support them... they are just not updated by mr_smartepants

they are just as safe and just as well tested -
They are just as well done as the main packs.
Some of them are done by main team members, others by experienced testers, some by the packs team.

Wim has given me the ability to add them to the main site...
Once we iron out a few wrinkles with the new Metadata format they will appear on the home page with the main packs...

Fear leads to the dark side young skywalker  
So fear not...
give them a whirl...

All of the rest of us do! especially Monitor and MoDem. (and physx)

PS didn't you ever wonder what that silly folder was for in the BASE directory?

you just need to be sure that the SP tag files exist @ Path\I386\..\ Or DriverPacks BASE will report no valid source found.

I belive windows setup will also fail if they are not there .

DriverPacks BASE will refuse to recognize it as a valid source

only files in the I386 are modified... correct...

files at the root like win51 are used to determine the version... correct

the faq is correct you need to copy the windows directory... even though we don't need all of it to be modified just the files in the I386 we do still need the files in the root for OS ID.

let us know what your results are with your tests

please respond to the existing topic / sticky

dont forget to do a normal install to use as a comparison. IE a 'control group'

Thanks and welcome (again) to DriverPacks...

I tried to find that thread yesterday... Its here please post a link to it here when you find it! LOL

if you can't find it i will reinvent the wheel for you the answer was simple and related to changing two lines in PRESETUP.CMD.

I was / am planning on adding it as a feature. For people just like you (and me and most of the rest of us) . 

The down side to this is severe disc fragmentation and the four or so Gig of space required on the target. In most cases this is not an issue but we try to design DriverPacks to work for all cases not just most of them .

Well extracting the drivers you need to a folder and running devpath on it is effective IF...
You keep in mind this will only work for simple devices,
  Not for video cards or chipset or mass storage drivers, for those you must run SAD.
You only want to keep things like monitor, modem, USB and other simple drivers.

So you don't have to run SAD it is just better if you do because it will update all drivers.
BUT... SAD is useless if you leave it on the machine. Presumably all the MB and VID drivers are already loaded with the version on the machine
SAD is most effective after a software first install or if you are a service / bench tech and want to update a machine being serviced. (On a CD or DVD or thumbdrive or or USB HDD or other removable media and last but not least as a network repository)

So truely you do not want or need all the drivers on the target...
just the ones that are likely to be plugged in post install

your users don't usually change out MotherBoards on you do they?