Search options (Page 11 of 213)

Let us know in that thread and here how that works, he just posted it here and we are not familiar with it yet.

If it can force the install in one pass that is very cool, I think i would still reboot after though .

this issue and other related issues are covered extensively in the two how to topics stickied in this forum.
(this has been asked and answered multiple times)

DriverPacks.net itself (the team and the software) does not directly support sysprep. Although fellow users and friends of DriverPacks will respond if they see your post. you should see Read BEFORE you post. also linked in my signature so you can properly update your first post with some useful info. There is no hint as to what you may, or may not have, done as it reads now.  Most noticeably absent is what the target OS [and update level] is???  (that might help ). See if you can't rewrite it in the spirit of rule # 6 from Read BEFORE you post..

hint: Check the setupapi.log file of an affected machine for your cause.

you will have to inject the dirvers into each WIM image separately, since each image is separated how could they conflict?

please read Read BEFORE you post. TY

not enough info to advise.

which version of PE? Who's build / version?
What download? (link maybe)

this isn't the psychic forum.

It's always nice to hear praise, it puts wind in our sails .

That looks pretty cool BP. Going to have to take that for a ride.

I don't think it would be a lot of trouble to put the INF and CAT files in the same stream,
I believe we are already putting the INF in a separate stream now..
What command line do you use for that?
-OOPS... BadPointer already answered that in his other post here:
http://forum.driverpacks.net/viewtopic. … 538#p57538

Are all NT5 and NT6 platforms supported.... or what?

Thanks for stopping by and sharing, it seems pretty awesome from the description.

and thanks for posting a link to us on your page
- Most of the others don't.

Jeff

one or the other.

if it's in the pack then we DON'T want it in the "drivers" folder.

NICE find cdob! Try to add that one driver like this:

http://www.nu2.nu/pebuilder/help/english/drivers.htm

if you drop it into the x:\PEBuilder\drivers\Net\-HereIsGood-
and rebuild

cdob will correct me if that won't work .

The pertinent information was provided above. By you.   (the HWID's)

PCI\VEN_8086&DEV_153A&SUBSYS_220E17AA&REV_04\3&21436425&0&C8: Intel(R) Ethernet Connection I217-LM

seems to be it, even Intel does not support NT5 platforms (officially)
https://downloadcenter.intel.com/Search … on+I217-LM

it's possible a driver could be shoe-horned in place for PE LOL.

google the HWID or description for more info "PCI\VEN_8086&DEV_153A"

you may have to use a PE3 build to get there. NT5 drivers may not ever be available for some new hardware as we move forward.

We will certainly add them if available. Post your HWIDs using the tool in my signature.

yeah there is an order. I just gave it to you.  It used to be plastered every where around here, it's for sure in the tutorial linked in my signature. the examples given in the tutorial are on a very old version of DriverPacks BASE, but are basically all still valid .

To make Unattended install CD:
1 RVMI update XP source to SP3  (unless it's media center then SP2 - {don't use MCE})
   there are some really good addons for RVMI
   - post Servce Pack update packs; All in Ones, AIO; Critical only, whatever
   - other addons can install software like adobe reader or ...
   - some addons tweak registry values.
It's very powerful, and not to complicated - RVMI will even copy your source for you. (never work on original files)
2 if you want to automate a CD based install you can use nLite for only automated install ... nothing else. period.
3 once you are all done, make a copy.
   Add DriverPacks to the copy.
   NO MORE changes are allowed to the copy at this point, your source is complete once you add DriverPacks. ( you made a copy right?)
   If you do make changes after this point I will know, and will ridicule you publicly.
4 MAKE ISO you may use nLite to make the ISO, and nothing else. period. (no more changes remember)

a fully updates source is the best place to start as a possible solution.

HINT: use RVMI to add only SP3 first. use the output as your new source for future updates.
         A clean SP3 source is perfect for UBCD4Win .

boot disk:
grub4dos will let you do that easily... boot disk images, linux, dos, NT, whatever you like. I used it to put bartPE on a second partion.  If you need a working example then please check out Easy2Boot, (the developer is a member here too .)  It demonstrates the power of grub quite well. it's real cool on a thumb drive...