You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by OverFlow
it will only be at %SystemRoot% AFTER presetup.cmd runs, and will only be there until the finisher runs. In my example above the file is copied during that time frame 
.
Yes it will always be in the OEM\bin folder for an m2 install.
It is a little harder to locate there because you may not know in advance what driver letter the ODD will be assigned, so it requires the extra code to perform a search of some kind... .
yes... rootDir="D\3\ATT" needs to be rootDir="D\3"
you are on the right track... and seem to have acquired a basic understanding of the INI structure / functions.
That is awesome news!!!
Thanks for the feedback...
Positive reports are the single most important factor for the release a new pack!
Have a Happy New Year salehyassin!
ps Marked 'Solved'.
Thanks again muiz!
You da man!!!
http://en.wikipedia.org/wiki/ClamWin
In the 1 - 21 June 2008 test performed by Virus.gr, ClamWin version 0.93 detected 54.68% of all threats and ranked 37th out of 49 products tested; the best scored over 99%.[6]
Yup it is a bottom feeder...
But it IS free and Open source and we like both of those things!
However in this case you got what you paid for...
Get a good AV program. There are Good AV scanners available for free!
that looks about right...
I think perhaps he might have meant to do this
exc_1_tagFiles = 3
exc_1_tagFile1 = "%SystemDrive%\ATICCC.ins"
exc_1_tagFile2 = "%DPSROOT%\D\V\ATI\attsetup.exe"
exc_1_tagFile3 = "%SystemRoot%\system32\atidemgx.dll"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 0
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\V\ATI\attsetup.exe /s"You have a copy already??? (confused???)
Um the code posted above would likely fail.
There are no INFs in his 3rd party DriverPack just the exe? (I assume)
Unless he created one named CX_XXXXX.inf and included it in his 3rd party DriverPack folder himself this WILL fail. the +infFiles are probably not needed.
Unless you ONLY want this to install if the target machine has a HWID that can be found in a VALID .inf file found at "%DPSROOT%\D\V\ATI\" and named "CX_XXXXX.inf"
Note "CX_XXXXX.inf" is specific and "CX_?????.inf" is wildcard... 
If I have assumed correctly that this file does not exist then this will ALWAYS fail.
Normaly 3rd party DriverPack are at "%DPSROOT%\D\3\~" but perhaps he did not follow the normal layout.
notes:
Tag Files;
do you really want it to ONLY install IF the ATI Catalyst Control Center is also installed?
I thought he wanted it to ALWAYS install?
If that is true you must remove the "%SystemDrive%\ATICCC.ins" tag
Obviously the setup.EXE itself must be a tag file .
(We can't very well run an installer that does not exist .)
and system32\atidemgx.dll is a good choice to determine if an ati card is installed 
.
the exc_1_command2 which deletes the installer is probably not needed / redundant.
the finisher will delete all files and folders in "%DPSROOT%\D\*.*
Jeff
PS i am curious how you got a copy of Proximus 3rd party DriverPack already... ???
We like dangerous !
Yeah if the finisher runs you should have a %SytemRoot%\DPsFnshr.log. Perhaps the finisher did not run?
show / tell us what you tried? perhaps you are closer than you think .
I agree with Erik, I think you will enjoy this more if it is your own personal success!
But we are ready and eager to support you!
Yeah... you found the log...
But that particular log shows you just opened and closed DP_Base.exe, and did nothing else... LOL...
there is a sub-folder of your BASE install, where we archive the logs to... "\LogFiles\"
when DriverPacks BASE archives them they get date stamped too ...
You will notice that if you do a slipstream the logs contain a lot more info... and are a bit bigger.
- It is not really important right now.
I now have enough info to at least be able to give you a push in the right direction.
Ten posts instead of two... but no real harm was done.
If it fails tomorrow then I may need to see the log from the actual slipstream of DP_MassStorage_wnt5_x86-32_909r6.7z to your source.
Hopefully the "latest version" *(now that you actually have it) will work and that will be the end of this issue...
Best of luck
thanks for helping us to help you!!!
PS It is no bother at all - it is why we are here!!!
(It's 4 AM at my house too - that is why it is quiet enough for me to get something done. LOL)
We have files that are not available from the main pages.
- Only for testing team, or for issues like yours etc...
Our packs go through MUCH testing before they ever get released.
In fact most packs never prove out to be stable enough to be considered for release to the public .
hmm... PCI\VEN_1002&DEV_4391
Is supported by
DP_MassStorage_wnt5_x86-32_901 in folder \D\M\AM2 by ahci7xx.inf
allow me to show you what I mean...
Here is a link to the actual "latest" version
MassStorage 909 Release Candidate version 6
that version is an RC version - it is a candidate for being released, a few good reports from the testing team and users like yourself and it may jsut become a final release!
Give that a try and see if it works and please let me know if that fixes it for you!
Latest final then 9.01
which is about 12 months older than our latest version
Logs clear up lots of questions
its in the folder where you installed DriverPacks BASE
the latest version? from the beta server? latest nightly, or latest release candidate, or latest final? LOL
Which pack version did you use?
Which version of XP,
which type of XP,
What SP level of XP
Please post your DPs_BASE.log it has all that info and more .
I will assume mass 9.01 for the moment .
Merry Christmas to you too salehyassin - Have a happy new year too!
We would like to help you but you have made that quite difficult.
You have to help us to help you. Please!
Looks like you have been around for a while, so you should be familiar with how we do things by now .
"Read BEFORE you post" Link in my signature - Please Read it.
Obviously it is a little too late to read it before you post ,
but perhaps you can still redeem yourself in your second post.
If you create a post that says "I am looking for a driver for"
is specifically listed as a bad thing. 
We simply are unable to find drivers for people, even if we want to.
How the heck are we supposed to know if a driver will work or not????
You are the one with the hardware to test with, not us.
We don't have a secret warehouse containing one of each and every available PC that was ever on the market.
We consider it rude when we are asked to do this, mostly because It not a very well thought out request.
Let me repeat, how can we possibly know if a driver will work without being able to test it?
If we HAD a known working driver we would have already put it in the pack... Right? - Think about this for a second .
Also please consider we may have already added your driver... Since we do not know which DriverPack MassStorage you used it is possible you are using an older one, a newer one may already contain your driver. There may have been an error adding the packs to your source... without your DPs_BASE.log we don't know...
If YOU can find one we don't already have then please submit a link to it and we will gladly add it . We just love to do that!
Please take a moment to submit your HWIDs using the 'HWIDs tool' linked to in my signature.
Then we can at least verify that there either IS or IS NOT supposed to be a driver in the pack to support your hardware.
If you had poked around the forum a little we would already have your HWIDs and DPs_BASE.log in your post above.
They are the minimum requirements for us to properly assist you.
Providing any of the other items listed in read before you post is also quite helpful .
Please help us to help you!
Have an awesome day sir,
and we ARE looking forward to being able to help you.
PS I notice last time you never even came back to follow up on the help Jaak posted you...
Look in the docs folder of your DriverPacks BASE install 'DriverPack_reference_wnt5_x86-32.ini'.
also look at mr_smartepants work in the graphics packs.
As you said... it's just like the ATI control panel. Exactly like it, in fact...
Hint - DriverPack_Graphics_A_wnt5_x86-32.ini file
Merry Christmas to you and your friends and family sir!
It is only used with the KTD function...
If you don't use KTD, and practically no one does, then it would never be used.
The KTD function is deprecieated by SAD anyway.
thanks for reporting it makes DriverPacks better for everyone!
Merry Christmas!
I would confront the man in question.
It may have just been a simple mistake, simply grabbing the wrong card off his bench. In which case he should return / exchange it. If he is actually a thief then he is probably also a liar, but, you may still be able to shame him into coughing it up.
Either way it's worth the risk. You have nothing to loose.
I hope he won't let that guy work on his PC anymore.
Either he is careless or he is a thief either way I would not recommend going back.
Best of luck!
I am not sure what else to do... I am not even sure why it fails...
I wish I had a machine with this (or similar) issue so I could test myself.
the only thing i am sur of is it is certainly related to some difference in process between DPInst.exe and Setup.exe
Edit the DP_Install_Tool.cmd script...
find this line
Start "MicroSoft Driver Pack Installer Tool Running" /wait /separate /realtime /min CMD /C DPInst.exe /c /s /sh /lm /el /sa
add /f
Start "MicroSoft Driver Pack Installer Tool Running" /wait /separate /realtime /min CMD /C DPInst.exe /c /s /sh /lm /el /sa /f
save and test
Answer to riddle: Pumpkin Pi.
Your feedback is more apprecieated than I can possably tell you!!!
Did you use the same script to call dpinst? (at least the same command line and same DPInst.xml?)
IE did you simply replace DPInst.exe with the new one and run DP_Inst_Tool.cmd?
So the issue still exists with sound and video... did you try adding the /f switch?
My daughter hit me with a cute riddle.
"What do you get when you divide the circumference of a pumpkin by its diameter?"
im so sorry.
here is my problem.
the motherboard is my problem. my mother board is acer.
if i change it to asus will it work?ps.
sorry for my numbness
We do understand that English is not everyones primary language.
We understand that if english is not your primary language it may be difficult for you to express yourself.
We still expect that you will do your best to explain the problem, we will not grade you based on grammer.
I would have to ban myself if spelling and grammer were graded here .
At least you have been polite and that buys you a little leeway.
We need Details sir!
- "The motherboard is my problem" Is way to vague. You might as well have posted "My car won't start. Help!"
How did you arrive at the fact the MB is your problem?
What did it do? When did it do it?
Why do you think that it is the problem?
What have you tried so far?
We are still trying to be patient and understanding. Reward our patience by helping us to help you.
LOL...
It's already on the todo list. http://forum.driverpacks.net/viewtopic.php?id=71
Thanks for helping us to help you, it is that spirit that 'drives' the DriverPacks!
recomended title: [REQ] Repair KTD feature please!
PS there are many ways to achieve this same result while you are waiting for me to fix this feature.
I only suggested one of many possable solutions.
IE you may simply extract the packs / folders you want and update the registry key from a script .
Cards seldom die... the resource conflict is a more likely scenario.
If moving it to another slot does not make it show up I would definately try it in another system before assuming it is dead .
Glad to help!
PS Many BIOS allow you to move resources around (Re-Enumerate) that may also help!
Since you did not state clearly what your problem was, we can only assume it is driver related.
If your problem is driver related then the instructions are valid.
If your problem is not driver related then we will delete your Off Topic posts, and contemplate whether or not to ban you based on our Rules and Guidelines.
Is there a reason you are running DPsFnshr.exe before Devpath.exe? Does order matter?
Yes because DriverPacks Finisher resets it to "%SystemRoot%\INF" as part of it's cleanup.
So, if you don't run DevPath AFTER the finisher runs then your DevPath will only include "%SystemRoot%\INF".
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 1.382 seconds, 6 queries executed ]