Search options (Page 107 of 213)

the 3rd party DriverPack ftp site is at everyones disposal... even general dogsbody's lol

thanks for the generous offer, and your time to create it and post.

Jeff

have you tried the DriverPacks already?

what version of base and packs. DPs_BASE.log is prefered.

can you psot the HWIDs of the devices?

links to the known working drivers is considered polite...

please review "Read BEFORE you post" in my signature

Welcome to DriverPacks, we look forward to assisting you.

Have a great day!

Wow those are very cool...

One question...
how did the WYSE terminal sneak in there?
WYSE terminals don't need DriverPacks ... LOL

Please use code tags when appropriate TY

We Add drivers when they are repoerted as missing by a user who provides the links to them.

We can not find drivers for you...

because we do not have the hardware to test to see if they work...
If you find the driver please provide a link to the OEM site.
(not rapid share or other third party host)
Then update your Title to [REQ] and we will then see if it can be added.

you may have some luck googling the compatable HWIDs for your device...
PCI\VEN_1002&DEV_4380&SUBSYS_0184107B&REV_00
PCI\VEN_1002&DEV_4380&SUBSYS_0184107B
PCI\VEN_1002&DEV_4380&REV_00
PCI\VEN_1002&DEV_4380

please read "Read BEFORE you post" in my signature
(IE "all the most recent" is not a valid DriverPacks version description
It also does not describe the options you chose
it also does not tell us what your process was
you failed to mention which XP you tried - home, pro, MCE, OEM, Retail,  or the Service Pack level
[basicaly you told us nothing]
You have provided very little useful info in your very long post )
except for the HWID and you could have put that on a single line

Please pay particular attention to "Read BEFORE you post" number 4

ALWAYS include in your post
- DPs_BASE.log (from the same directory as DPs_BASE.exe)

that will provide most of the missing info i pointed out above
(and is why it must ALWAYS be included)

Welcome to DriverPacks.

Please take a moment to read the
"Frequently Asked Questions" forum (how to customize mass storage is stickied there)
and other stickied posts like the one in 
"Feedback and Support - DriverPacks Base" (READ BEFORE YOU ASK! by Wim Leers - is stickied there)

- testing a driver will be quicker and easier with nLite -
     (don't add any other drivers except the the (Single) mass storage driver you are currently testing
      don't reuse the same copy of your source, Use a clean OEM disc copy each time)

Thank you

now you know why DriverPacks does not support xp 64

NO... ABSOLUTELY NOT you will destroy your source~!

however you can leave nLite open at the make ISO screen while you run DriverPacks and use nlite after DriverPacks to make your ISO.

if you make ANY changes after DriverPacks AT ALL you will have junk

guys... you both have fallen short on this one...

mr_s lets have some details about your process He can't help if he does not know what you did - just venting is not helpful

Muiz we know mr_s is not an idiot... Lets find out how our advanced users can get lost (and agitated), and see if we can make the proper steps more obvious to everyone. returning his frustration doesn't move us in that direction.

Lets all cool off a little and try to show more patience than I normally do

We are a team after all - let's work together!

Thanks a million RogueSpear... So glad you have been around lately!

there should be DSPdsblr.exe, mute.exe, makePNF.exe an INI file for each pack and DPsFnshr.exe with some other files too... all in %systemdrive% (obviously there should be a folder named \D\ with the extracted packs too!

I also assumed that you were useing an unmodified BASE generated SAD folder...
other than the changes mr_smartepants and I suggested.

Please remember the finisher removes all these files so you must look before the finisher runs
IE while the file not found error is displayed

I belive your prloblem is related to these files not being extracted properly. I apologize that i can not figure out why they are not being extracted based on the info provided. however the fact that they are not is a clue that perhaps you can use to troubleshoot further and report. If you think of anything you changed or that is unique to this machine please let us know so we may be of assistance!

Jeff

Thanks for provideing the feedback it helps everybody!

- are we allowed to ask why now -

Attended installs have recieved some interest. Not as much as SysPrep and RIS so they are on the list.

You are Right since i did not disagree i passively agreed