Search options (Page 154 of 213)

Your Idea is sound but is not as easy to make work as it is to describe.

"I believe the registry changes need to be in the master image prior to running sysprep in order for it to be a valid test."

I agree... let us know and well see what our options are from there...

RE - make the system look in the 620 folder first, then the 755

break signing on the 755 by deleteing the cat file this will lower its PnP "rating"
this will likely force the 620 to be 'prefered' to the 755.

you alternately can tweak the INI's list of HWID's, which will also break signing

the main problem is when chipset driver and LAN drivers load you are temporarily disconnected from the server and your drivers.

1 winnt32.exe is not supported - we use a custom setup.exe with method 2.

It calls presetup.cmd and then calls setuporg.exe which is the original windows setup.exe that we renamed. It is neccessary to do this in order to allow presetup.cmd to extract the drivers to the local machine ( C:\D\ ) BEFORE hardware detection begins.
put another way - The original setup.exe (setuporg.exe) is called by our dummy setup.exe after the packs are extracted and their location is added to the registry.

2 Setup cannot copy xxxxxxx.xxx
Enough said... self explanatory

Try the search feature of our forum this is well documented in several places already
try searching on the keyword RIS or look around in the Universal Imaging forum
otherwise i will be forced to repeat myself... repeat myself... again...  lol

have a great day

I was suggesting that you make your own 3rd party DriverPack -
but i was under the impression you already had one that did work for you.

instructions for that are here --> http://forum.driverpacks.net/viewtopic.php?id=279

if you need help i will be here...

Welcome aboard and we're glad your here

see autoimage by roguespear

he uses DriverPacks with ris... and it works great.

a popular setup here is this

RyanVM
nLite
DriverPacks
WPI (Windows Post Installer)

Laptops quite frequently will only work if installed with the OEM providers drivers.

We extensively use reference drivers
what if we had to use every individual nvidia manufacturers drivers in the packs  (they would be twenty times the current size)

the problem is Laptop manuracturers will normaly drasticaly mod thier chips (to reduce power consuption or heat... wahtever)

the best solution is to make a 3rd party DriverPack that includes your specific laptops driver.

it is the manufacurers fault / error if a given device will not run a reference driver correctly.
if we tried to support every laptop available then our packs would be ten gig instead of 300meg 

Laptops are a PITA i suggest that you create a 3rd party DriverPack for this driver and call it a day.
If we get a lot of requests for this particular one it may eventually end up in a main pack.
that is not likely because it will then cause conflicts / issues for the drivers that we do include.

if you are able to figure out why the included (reference) driver fails we may be able to make an exception in our packs to address it. IE there is a setup.exe that runs in addition to the driver that will make the reference driver work.
then we could test to see if it is needed and run it.

you will need to tell us since we don't have this laptop ourselves to play with...

let me know if i can help in any way

you're always a welcome sight here! We miss you and many of the other founders of this and other great UXP projects.

I understand as much as anyone that we (me, you, Wim, Signet, Ryan, ect) only have so much time for volunteer work.

It is truly awesome when you stop by, even if it is only briefly. you're a hero in my book sir!

Thanks for your kind words, and my best wishes for you.

Jeff

the native driver IS the original driver by 3com - where do you think MS got it from...

Since the windows drivers work and are already integrated there is no need for them to be redundantly included in the DriverPacks.
(this also reduces the size of our packs)
the driverpacks are a supplement to the included drivers not replacement for them.
that is the way the DriverPacks were designed and the way they are intended to be used.
This is normaly not an issue becuse most of these drivers are for support of legacy hardware.
IE most of the included drivers have not been updated in years and probably never will be again.

We have a saying where I'm from "if it ain't broke, don't fix it"...

you can remove the native drivers if you wish, but you will also be giving up support of the hardware that they cover.
(like the 3c905 series NIC)

normally adding driverpacks will make that key over 6000 characters

yay! good bye tent! hello bed and shower!

Glad your home safe and thanks for everything you do.

PS now you can check out that page i set up for you