Search options (Page 162 of 213)

the point is if you dont want an unnatended install delete winnt.sif.

simple...

a gui option to not add a winnt.sif is a reasonable request...

check the attitude at the door bub... you obviously are a noob...

get your facts straight before you start saying harsh things like bug or "now has a major glitch"...

well it would have worked with method 2 but it would not have worked with method 1 with previous base.
obviously something you were not familiar with (smart Alec)

method one has always used these settings
this glitch you describe has been a feature much longer than you have been a user.
i simply made the treatment of the winnt.sif uniform for both platforms.
(these entries have not always been ommitted by M2 either)
there are benefits to having these entries and removing them is simple if you must.

driverpacks is now and always has been intended for unattended installs
and our decisions will continue to be driven by that goal.

I would suggest to you - if you want something you ask nicely

and never attack from a position of weakness
(or in this case having no clue what the previous features of base are)
familiarizing yourself with one small aspect of base
and only having experience with one or two versions
does not magicaly entitle you to make any decisions for us about how we should do things.

-------------- steps down from soap box of 'we don't get paid for this sheet' ----------

i will however put two tallies in the against column for your passionate response

Sysprep is not yet supported... it is a popular topic here...

we will at some point add it as a supported platform...

you may check out the Universal Imaging topic
there are some good tips from a few of our users who do integrate with sysprep.

there is no easy way to make sysprep work with mass storage or drivers in general...
you will discover my disdane for this method as you read...
but feel free to comment or ask questions as you need...
provided you are familiar with the existing content. especialy the stickyed ones.

we are not saints - but we try to be - if given a choice.

I wish OEMs providers had to take DriverPacks training...
if they did unified drivers would be more common
and drivers would be more functional and compatable with their older versions

the points you make are good ones - I agree with your conclusions.
we will still take the high road as long as it presents itself as an option.

the only approved and supported method of integrateing mass storage is with base.

Other methods will not yield the same results - period...  that is why were here.

if you wish to add the rest of the packs with nLite that is your choice...
It's definately not the choice I personaly would make. but it might work fine for you...
the obvious downside to your method is zipped the drivers weigh in at 300Mb
extracted and added with nLite takes up a whopping 1.5Gb. a loss of 1.2 GB on your ISO

if you are aware of all of these things and wish to continue then
nlite all packs includeing mass storage
then run base and select mass storage textmode box ONLY (don't select any of the packs at all)
this will only slipstream mass storage textmode and make no other changes.

then you can create your ISO with nLite.

that is the best option you have with the parameters you provided.

there was  a very strong post about this recently on another forum and i cant remember where now.

a sound card manufacturer was targeting an individual who was hacking drivers to enable features in cards that were available in Vista but not available in XP. They were calling it theft.
It was their position that it was up to them to decide which features were to be supported by their cards. BY enabling features that they chose to disable he was in effect providing free upgrades to their hardware. It was not appreciated and drew a cease and desist order on the author.

So while this can be done it is at the same time a license violation...
We will not be able to tell you how this is done for that reason.

It is my recommendation that you approach the OEM / Provider and request they "fix" their drivers.
(technically they are not broken they are gimped as a marketing ploy)

No he really was ON target overall...
we do need people to post win or loose so we can make DriverPacks rock solid.
without people who post thier hwids we don't have them
(you have to possess the hardware to get the hwids)
We live or die by knowing what devices report what specific HWID's

Thanks for posting yours!

Have you tried just useing the current pack - instead of the one that came with your build?
I belive the included pack is from last year...

I guessed correctly, on the second try

Thanks for the feedback  it makes driverpacks better for everybody.

I updated your title to be more descriptive (see read before you post in my sig)
and have stickied this as i belive it will be a FAQ -

I believe these lines make for a smoother Unattended install so I would like to keep them.
They are simple enough to remove to create a repair disk so i think this can work for everyone as long as everyone is aware of it.

i think if it were causing an issue, someone , would say somthing...

i suspected it would have the same driver issue we see posted...
the included update drivers.

but since we have not heard i sassume it is because of the way we list the hwids in the mass INI

that list is the key to makeing them all play nice together

ps remember PE doesn't load the PnP drivers
they are often the cause of reported issues.
IE after the winpe reboot and 7b bsod - (which never occurs in BartPE)

do  search for PXE or RIS

let me know if you need more help

ps this is a good topic http://forum.driverpacks.net/viewtopic.php?pid=19434

guess i am going to have to check that pesky search engine again
i guess its sleeping on the job again!

try this stickied post in our Frequently Asked Questions Topic...
http://forum.driverpacks.net/viewtopic.php?id=2264
start with the last post then the first one - the rest are optional but helpful

now those posts are all about local disk usage
(that is what we support here "Disk" installs and PE)
but we sometimes deviate a little from the supported platforms if we can accommodate.

this is about accessing a network drive for driverpacks.
http://forum.driverpacks.net/viewtopic. … 190#p20190
that one you may have had trouble finding since it is in the thread linked to the first artical on the home page.

take a look around and see what options are available or seem to make sense to you.
try a few of them (seriously consider at least) and let us know if you get stuck...

PS here is another method
(I belive this method is now oblsolete with the DPInst method available now)
http://forum.driverpacks.net/viewtopic. … 652#p18652

have a great day

Jeff

no news is always the best news ... trust me on that...