Awesome news! Thanks for testing.
Jeff, can we move the new DriverPack Graphics A 9121 to the SimpleCDN server now?
Done!!!
Thanks a trillion Erik!
You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
Awesome news! Thanks for testing.
Jeff, can we move the new DriverPack Graphics A 9121 to the SimpleCDN server now?
Done!!!
Thanks a trillion Erik!
OverFlow wrote:ChiefZeke wrote:How to I download anything? I went to Simple CDN and and found no link to download - just comments about how great they are.
LOL
All DriverPacks are available from links on our home page here at DriverPacks http://driverpacks.net/driverpacks
But the easiest way to do it is just to use the update checker page in DriverPacks BASE
.
That is a quote for the books Jeff. Perhaps a FAQ question
I have to agree...
ChiefZeke has been around for a while... If he had trouble then a noob would have no chance
.
I know much emphasis has been put on the video drivers, but remember the sound doesn't install correctly either from the SAD.
True... And that is how you can help us to help you!
We know that DPInst does not always yield as good of results as Setup.
What we don't know is if we are not using it correctly, or if it simply does not work as well...
I was hoping you could help us find that answer
.
If it is our misuse of DPInst then I would like to make the proper adjustments to our usage.
If it is a failure of DPInst then perhaps we can get MS to fix the bug!
There is a newer version of DPInst available. Perhaps it is already fixed...
here is a link to the new version. http://driverpacks.sytes.net/driverpack … dpinst.zip
(we are distributing ver. 2.01 that link is for ver. 2.1 which was released for Win7 compatibility, but may help us with XP too
)
Would you like to try it for us to see if it is already fixed?
Only someone who is experiencing a failure can determine what will help / or fix our issues. ![]()
You have done everything the way we recommend!!! There is no known issue with your process at all.
Again two possable issues here
1 - Perhaps we have made a mistake.
2 - perhaps it is a bug with DPInst.
Can you please help us to figure it out?
Newsposter already asked the best question...
What AV software provided these results?
Why have you failed to answer him? (too embarrassed)
Have you submitted any of these files to them for confirmation?
Can you post the confirmation email here?
(or better yet their apology for the false positive)
Have you at least confirmed the results with a second AV program? ( I know the answer to this is no...)
Most people believe that their AV is the best, even when their AV is not on a top ten list anywhere.
I have had Four or Five people report viruses in the past, but in every case it was a False Positive.
So I am going to jump the gun here and assume you have not submitted the files for review by your AV provider.
If you had done so then you would already know what we do. There are no virus in our packs.
We just have too many users, using too many different AV programs for a nasty to be able to slip through.
I doubt your AV is better than all of the ones our millions of other users have. ![]()
the more likely scenario is your AV program is junk.
Now I am going to give you 'the speech'.
The only thing worse than a virus is a False Positive.
False positives waste more time than a virus ever would.
- Because you are wasting time trying to fix what is not broken.
Your time has been wasted!
If you're reporting here then lots of your time has been wasted.
Now you have attempted to waste our time as well.
You have been told to delete necessary files that are not infected. How in the world is that helpful to you?
Perhaps next time your AV will delete your Financial Programs data files
.
Please let us know which AV program you are using, so that we may all know which AV that we should not to ever use.
Get on the horn with your AV provider and and waste their time if you must.
My guess is their support is probably about as good as their engine. (sorry)
I would just select a product that works reliably.
It is possble that a different set of command line switches (or .XML entries) will yield success...
But we are not able to test since we don't have a rig that fails... Perhaps this is an opportunity for you to help us?
XML file entrys are here http://msdn.microsoft.com/en-us/library/ms791067.aspx
Command line switches are here http://msdn.microsoft.com/en-us/library/ms790806.aspx
/f command line switch seems like it may be helpful... perhaps not?
tonight when i get home!!!! I can't wait!!!!
I don't believe that devpath HAS to be at the root of the drive for you to do specificaly what you wish...
The DriverPacks Finisher will FAIL if it is not in the Root.
You should be able to write your script so that it expects "%SystemRoot%\devpath.exe".
Just be sure your copy of the files "KTD" is Prior to the finisher deleteing them, and devpath.
The finisher cleans everything up just like normal
.
IE
SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
REG ADD %KEY%\996 /V 1 /D "cmd /c start /wait copy %SystemDrive%\D\3\pack1 %SystemRoot%\D\"
REG ADD %KEY%\996 /V 2 /D "cmd /c start /wait copy %SystemDrive%\D\3\pack2 %SystemRoot%\D\"
REG ADD %KEY%\996 /V 3 /D "cmd /c start /wait copy %SystemDrive%\Devpath.exe %SystemRoot%\D\"
REG ADD %KEY%\996 /V 4 /D "cmd /c start /wait %SystemDrive%\DPsFnshr.exe"
REG ADD %KEY%\996 /V 5 /D "%SystemRoot%\D\Devpath.exe %SystemRoot%\D"I have not tested the above example ![]()
yes devpath is recursive...
If it was locking up in BIOS... it probably was not an issue with the packs anyway...
.
A bad MB or power supply is likely, and faulty hardware is the only reasonable explanation for "It locks up in the BIOS".
So I don't think we will see this issue again
.
The question was...
After you run SAD, do you reboot the computer, at least once?
@Erik - He indicated above that a normal slipstream of the DriverPacks does work
.
@ overflow , yes ibexide.inf contains that hwid
Ahh... I see it now... I was looking in mass storage for it, Now I do see that it is included in Chipset
. I had not looked there.
Glad to see you Muiz!
His HWID is PCI\VEN_8086&DEV_2920
and although the ICH9 driver IS present in the pack THAT HWID is not included... ![]()
Yes was is trying to do all this from XP. now he has win7 x32
@contare
Hmm. Yes your right, if it was included natively we would not have this issue... Duh! blonde moment
.
Do you even have a 64bit processor? (since you did not include your full HWIDs list we don't know...)
DISM will install and run from XP. I am doing this right now. ![]()
Augi,
Putting five identical posts in the Translations Team Forum is considered Spamming the Forum, and Will result in your being banned. Especialy since you are not a member of the translations team. Posting in the wrong forum is considered lame, so is cross posting.
I moved the one post that was in English to the 'other' forum.
I deleted the four that were seemingly in Dutch. We do have a Dutch forum just for that.
We already have a tutorial posted on this site available from the home page.
Most all of us also have a link to our tutorial in our signatures.
You have failed to: Read the rules and guidelines, or Read the tutorials, or use Search, and have spammed the forum.
You have failed to describe what your issue is with any kind of detail that would allow us to answer you intelligently.
You have not provided any of the info in "Read BEFORE you post".
You are not off to a good start.
1) Read "Read BEFORE you post" linked to in my signature.
2) Read the tutorial linked to in my signature.
3) Read the rules and guidelines.
4) Use the "Search" feature of our forum.
5) Make sure you post in the correct forum for your issue.
6) Do not create more than one post per issue.
7) Explain in detail what your issue is.
You might as well have asked us what color the dog is...
- - Exactly! - that makes no sense either!!! - just like your post(s)!
yeah i did not find your HWID in the X64 or x32 Mass pack (PCI\VEN_8086&DEV_2920)
I am trying to determine if that is natively supported in win 7 now...
Um nope it won't help providing the drivers... It will however help with adding them to your install media
.
The only reason i can think of that Muiz did not already add them is because they are not needed
.
IE they are included already. Trying to verify that now ![]()
DON'T HIDE ANY DRIVERS!!!
The Working Driver just might be in the "incompatable" list!
IE Win7 may mark a Vista driver as incompatable, BUT all Vista drivers ARE fully Win7 compatable!
Much as many XP drivers come up with a warning that they are not "Digitaly Signed" but that does not mean they won't work or even that they are not the proper driver...
.
Did you copy the DISM tool to your HDD from windows 7? or are you trying to run it from the DVD?
(you have to have win 7 already installed on a machine to be able to get it the way he describes)
if you do not have win7 installed you must download the WAIK for win7 from MS. (He says this in his instructions)
link to WAIK download http://www.microsoft.com/downloads/deta … laylang=en
Please read the tutorial on DISM by Muiz - http://forum.driverpacks.net/viewtopic.php?id=3716
This explains how to add drivers manually to a Win7 image.
Please note it is neccessary to Mount the WIM and update it to get the neccessary support added to your WIM to enable it to find your HDD.
Muiz has also privided a link to a tool to help simplify the process here - http://forum.driverpacks.net/viewtopic.php?id=4200
(did you extract the drivers from the pack?)
ITE and ICH9 are very common intel drivers, and are included in the packs.
I suspect the driver you need is not a standard Mass storage driver, Perhaps it is a Card Reader? (which would not be included in mass storage or chipset) Since you did not include the full report of your HWIDs we can still only guess...
Did you install from a DVD? Did the installation find your HDD?
Are you trying to install on the same system you are preparing the image on?
or are you useing one to create the image and a second one to install to.
What is the OS you are useing to manipulate your win 7 image.
Is the target a white box or a production machine (IE homemade vs a Dell or HP)
If you want help you are going to have to spill the beans.
We are not psychic and we are not going to play 20 questions with you.
Hi gfxcell,
Could you please include some more basic info so that i might be able to offer some useful help.
Please see Read Before you post in my signature for some ideas.
For example what version of BASE did you use? What version of the DriverPacks did you use? what are your HWIDs?
If you were to include your DPs_BASE.log that would cover displaying all of the DriverPacks versions involved.
The HWIDs tool is linked to in my signature below,
however if you were to include your DPsFnshr.log that would include your HWIDs and some other useful info too.
We may also need your Setupapi.log but let's get the basic info first.
Looking forward to assisting you.
PS I really like GigaByte products (nice MB) and a 5200 was a nice card in it's day too. All in all a very nice machine, even if it is a little old.
Thanks a Million Major!
You are a 'major' DriverPacks Hero in my book!
64 bit drivers are only supported for Vista or Win7. (NT6.x based platforms)
64 bit Drivers are Still NOT supported for Win 2K, Win XP and Win 2K3. (NT5.x based platforms)
It is possible to make your own personal DriverPacks for NT5.x - x64 platforms by using the Microsoft application DPInst.exe.
Does that help / answer your question?
Well done (again) Muiz!
LOL yeah the speed calculation is not very accurate - it is an aproximation
.
Links to file shares will not be considered for adding to a pack, at all.
Please provide a link to the driver on the OEM website if you wish it to be considered.
Thanks a million, again!
It is simply awesome to see new packs released!
Seasons greetings to all!
Merry Christmas, Happy Chanukah...
Best wishes to everyone!
There should be no issue with adding a patch that may or may not be used...
In fact I am going to sticky this so I can remember to add this patch to DriverPacks BASE. Much as we include kb888111 for xpsp2.
I need to add a few patches for 2k3 also.
I've only used KTD for mobile phone drivers and LCD monitor drivers (aka things I know don't have installers and that likely won't be connected at install time, but will likely be connected soon thereafter). This seems simpler having a SAD disc and using that for phones and monitors.
That does seem like one of the best examples of a good reason to use KTD I have ever been presented with
.
I'm not familiar with DevPath.exe. Is that explained somewhere? So if I have a custom script run before the finisher and have it copy the drivers I want somewhere, and run DevPath.exe, then I can skip KTD?
YES!
if you copied your drivers to C:\KTD
devpath C:\KTD
![]()
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.115 seconds, 5 queries executed ]