You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
check my sig for the RAID HWID tool 
(HINT since you dont have RAID is just an example - open with 7zip winrar winzip ect... )
yes and no... there is supposed to be a standard... but...
based on wether it reports as a 101, 102, 104, 106, whatever
you should be able to determine the mode... In Theory...
You lost me... trying to follow...
I have played a couple of games that use the emulator... there is actaully a daughter card for PhysX much the same way as the old VooDoo cards...
I say if you need it (and it is unlikely that most of our audience will) you can put it in your own 3rd party DriverPack and every one can get waht they want... Perhaps ef we asked mr_smartepants real nice he will even make the 3rd party DriverPack for us?
um... it is solved and Jaak is correct there is a typo...
however the typo did not effect the users results... which were positive...
So the correction is a valid fix and the typo can be corrected by the team when implemented...
and i think Jaak put a nightly up with the correction...
you dont want or need KTD...
you need to integrate mass storage useing syprep (yes just mass storage)
then you can either
use the driverpacks M2 without the call to the finisher. this will leave the \D\ folder and all the finisher files in the root of the drive, and the \D\ folder should already be in the PnP search path (i am not sure if this registry value is cleared with sysprep - but if it is you could just call devpath to repopulate it then when the image is deployed the drivers are used teh finisher is run and the DriverPacks are removed (same as a normal install)
or you can use the SAD Disk option - just run the stand alone driver install after deployment... and then delete it.
Thanks a million!!!
should I specify the KTD location as %SystemDrive%\D instead of the default? NO...!
NEVER SET THE KTD LOCATION TO DriverPacks ROOT (%SystemDrive%\D)
your best option is probably to integrate mass with one of the recomended methos here (for sysprep) and not call the finisher when you do your install (finisher = custom) in this way the drivers are available until needed (target machine) then run the finisher on the target... this does add 1.5 gig to the copy... but it will be deleted right after the deployment. it is not feasable to do this any other way... (what would happen if the LAN driverwere being updated from a network location... boom... same for chipset... there is no way around keeping the drivers local until after deployment. forget about the size and keep your eyes on the prize... a UNIVERSAL image...
Stay on target, you can have small or universal not both... if you want small then use one image per machine...
you might also use the SAD Disc method for driver install instead of the method you are following.
integrate mass per sysprep...
copy a SAD disc (M2) to your image and call it on first boot. in this way the copy is only the 300MB for the compressed packs instead of the 1.5 gig of extracted drivers
perhaps it is thermal failure (clogged CPU fan) or perhaps your ram or video card needs to be Thumbed into the slot...
" I've tried editing the OEM\DP_Install_Tool.cmd "
well the Tool is not used for a M2 install...
so any changes you make there will be ignored, DP_Install_Tool.cmd is for manually installing drivers (a stand alone driver disc)
DriverPacks does not modify your system files... so you can strike that off the list
that leaves either a bad Disc or nLite...
If i were going to guess it would be drivers that are upgrade/replacements for existing windows drivers.
by adding the driverpack you create HWID duplication with native drivers... just a guess.
PS easy test to find out run your hwids list against txtsetup.sif...
Jaak is distracted ATM lol
give us the HWIDs
we need a few details please...
see Read Before you post in my sig for details on what details we need
for example what base and sound pack versions are you useing ? version #s please
and it would be equally important to include your HWIDs with a [REQ]uest to add a driver
again see my signature to get the hwids...
thanks for posting
to be hence forth and forever known as the "krick" FAQ
oddly enough the kricks of the world will never find it...
http://forum.driverpacks.net/viewtopic. … 746#p23746
for some strange reason i decided NOT to sticky this one
I created an XP DVD with a full set of slipstreamed driverpacks.
All of the driverpacks files were extracted into the root of my hard drive and my devices were installed.
but there is still a folder named "D" with the extracted DriverPacks and some other loose files in the root after the install.
What should I do?
For some reason the final step in the DriverPacks process was not called automaticaly
to clean up the remainig files and 'finish' the process just run the DPsFnshr.exe and reboot
um... wrong forum and no mention of a pack version...
moved to universal imaging
ps excellent info Echo_Platoon !
OK i was correct this driver is natively supported by windows xp sp3
this driver should install even if you dont use DriverPacks... I386\viaide.sy_
Are you guys removing any drivers (IE with nlite)...
This hardware is supported directly by windows XP...
so it is probably not a DriverPacks issue
and those HWIDS if you do add them will conflict with existing windows entries in your txtsetup.sif
IE txtsetup.sif = corrupted
so don't add them
My Theory is you guys are removing exitsing window drivers...
DriverPacks appends the existing windows drivers
- You Must still KEEP the naitively included windows drivers...
please try installing windows without DriverPacks and see if it finds them and kindly report the result...
So you're telling me that adding 8 characters to the beginning of the path by putting the loose files in a folder called "~DPTEMP" (7 characters + the slash = 8) is a deal breaker?
YES...
now please stop...
read the msfn tut from cover to cover then come back with your IDEAS...
After you have at least a basic working knowledge of the process...
yes it has to do with path length - you will also notice most of the folders have only one letter names
you want basic questions answered look it up at MSFN... RTFM
and btw i have been in computers since 1968
dumb terminal, acoustic modem, and paper tape off a mainframe
So i could really care less what you think you know...
i started with MS at DOS 1.1 and i still have the OEM pack.
you are not running with the little script kiddies here this is big dog territory...
most of the people here with more than 20 posts manage hundreds or more machines every day.
and i have provided the support for up to 70,000 users in some of my work and had more than fifty agents working for me.
Please put it away, we are neither impressed nor swayed you stand or fall based on this topic...
perhaps you should take a moment and reread it. and think if you had to be the one supporting yourself...
be respectful, answer simple questions, provide required info when asked.
when a Solution is offered in the first responding post please at least TRY it...
say please and thank you and your stay will be pleasant
you are correct there are a lot of b=people useing DriverPacks we have over 32,000 downloads a day
and yet you are the only one who belives he has the right to tell us
that he thinks he knows better than we do what we should be doing and how we should be doing it.
And you dont even have a basic understanding of waht it is we do... LOL
so we get a million downloads a month and your the only one with a problem in three years...
do the math...
Open driverpacks base select all of your options and instead of hitting the Slipstream button with the mouse do this
hold down the ALT key on your keyboard
you will then notice that the first letter after the "&" sign in the word "&Integrar" is the letter I and it is underlined
as you hold down the ALT key you will also notice there is an underline under the letter S in Sair.
now that you can see the "Hot-Keys" (because they are underlined after you hold the ALT key)
Hit the letter S (while still holding the ALT key down) POOF DriverPacks BASE Exits
Hit the letter I (while still holding the ALT key down) POOF DriverPacks BASE Starts Integrar...ing
Each of the buttons in the language file can (and probably should be) assigned a Hot-Key...
Look at the English language pages with the alt key down
Jeff
PS many of us who have been around longer than the mouse like hot-keys 
PSS it is also nice if your mouse is misbehaving
how did you know about 808... i guess Bâshrat the Sneaky is not the only sneaky one
Its still alpha... and only available internaly to team members until it is ready for beta...
um... like the testing team for example...
{waits patiently for the response he knows is comming...}
you may have more luck with asking this at UBCD4Win or 911
wae are still working on provideing lan support
well i am almost positive that the via bus master controler is a standard included MS driver...
am almost equally certain that we have an upgrade for it in the packs
If i have guessed correctly it may not have the proper REplace IF OS tag set or it may be gimped
I am codeing base and i dont want to get too distracted atm...
Hint: this file may have gotten upgraded with sp3...
did you see this post... ? it is in the UBCD4Win forum but it is for s bug in mass storage...
http://forum.driverpacks.net/viewtopic.php?id=2999
Please, if one of you have time, verify my findings and update mass (if you haven't already done it lol )
DriverPacks.net Forum » Posts by OverFlow
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.111 seconds, 5 queries executed ]