You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by mr_smartepants
Welcome to DriverPacks.net! 
Unfortunately, your post tells us next to nothing useful.
Please read the "read before you post" linked in my signature, then post back with the following info:
DPs_BASE.log
DPsFnshr.log (if possible)
HWIDS
Lucky for you, I'm in the process of updating our dpms at this very moment. Would you be able to test for us?
Thanks. Have a great day!
I've never tried it with XP. But installing Win7 via USB was a real eye-opener. Speed, speed, speed!
I would love to try it with XP. I came across a utility a few months back and downloaded it, but never got the time to try it out.
I can't even remember the name of it now...lost in the wasteland my download folder has become!
Indeed. That is a VERY old system you're emulating there. PentiumII no less!
Yes, the intel drivers are finicky with those old HWIDs. We stepped back from the cutting edge for stability's sake.
I added links to previous nightly/final builds. 
Good job.
Agreed. We need to maintain a strict "chain of custody" rule. From the manufacturer to us. Driver warehouses (like station-drivers or others) should only be used WHEN THERE IS NO OTHER ALTERNATIVE.
Digital signatures can be faked, or worse.
We have to remember that our packs are used in enterprise environments as well as for personal use.
The second our DriverPacks become compromised, we loose all credibility from our users. I, for one, value our integrity above all else.
There's a new DriverPack Chipset & MassStorage 100804 in the testing FTP.
You got email!
There's too many differences between your txtsetup files to know what's wrong.
amdide1.sys=1,,,,,,3_,4,1,,,1,4
That shouldn't be there with the current version.
Make sure you delete the QSC folder between dpms versions.
DP_CardReader_wnt5_x86-32_802 folder W/2 and DP_Misc_wnt5_x86-32_100725 folder W2 - identical!
That's because the contents of the cardreader Third Party DriverPack were merged with misc. The cardreader Third Party DriverPack is obsolete now.
The text above shows the drivers loaded OK. CCC wouldn't be installed if the drivers were not installed also. But there's something wrong with the driver installer file .inf so a service isn't starting properly which is causing your "yellow exclamation point" in device manager.
I'll try to take a look at it, but I'm working on fixing MassStorage now and it's consuming all my time!
Got the logs. Seems like everything installed OK. Weird.
#I123 Doing full install of "PCI\VEN_1002&DEV_71D5&SUBSYS_12421043&REV_00\4&2D404BB6&0&0008".
#E360 An unsigned or incorrectly signed file "c:\d\g\a\dps_1.inf" for driver "ATI MOBILITY RADEON X1700 " will be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not contain digital signature information.
#I121 Device install of "PCI\VEN_1002&DEV_71D5&SUBSYS_12421043&REV_00\4&2D404BB6&0&0008" finished successfully.Right. So for XP, some of the drivers are stored here: C:\WINDOWS\system32\drivers\ with the .inf files stored here: C:\WINDOWS\inf\
The original driver.cab file is stored here: C:\WINDOWS\Driver Cache\i386\
Drivers downloaded from WU/MU are here: C:\WINDOWS\SoftwareDistribution\Download\
Well, true to a point. Each version of windows had a different way of caching drivers. Each has a "driver store".
They only get loaded to RAM when needed. But they do take up HDD space until purged.
Some hardware vendors have an SDK (software development kit) that contains the tools and documentation to make the correct software hooks and calls to interface with the hardware. But most are closed to driver development as these are closely guarded secrets.
If you're building your own hardware, then you are the best one to know how it works and what to do with it.
I'm guessing this is for a school project, so by answering your questions, we would be cheating you from a valuable learning experience.
Always do DriverPacks BASE LAST just before finalizing the .iso.
Nlite does not slipstream drivers good at all. Make sure you slipstream the DriverPacks using DriverPacks BASE. You can leave nlite open at the "build ISO" stage, run DriverPacks BASE, then build the .iso after DriverPacks BASE is done.
DriverPacks BASE makes modifications to the system so that if unsigned drivers are used, the warnings are ignored. So all will be well.
When you finish your disc, if there are problems, then we'll want to see the following log files:
DPs_BASE.log (found in the same folder as the DriverPacks BASE application and DriverPacks)
DPsFnshr.log (found in the target system C:\Windows\DPsFnshr.log after install is complete)
setupapi.log (found in the target system C:\Windows\setupapi.log after install is complete)
There's already a 100802 but it has a typo in the .ini. I'm uploading a new 100803 tonight after testing.
Good to know! Thanks for the report.
It always helps to have many eyes.
To quote Linus Torvalds: "Given enough eyeballs, all bugs are shallow".
The v9.1.2.1007 refers to the PACKAGE version. The individual drivers have version #s all over the place.
Yes, it's probably a corrupted download. Flush your cache and try the download again.
Or try hashcheck to check the md5 hash.
Good to know. If you ever get the HWIDs, PLEASE post them.
Use the stable 1007.
Well, I was hoping it was fixed in the 1007 final.
I only grab the drivers from the official OEM. I only monitor station drivers to get a heads-up on current status. I RARELY get the drivers from there.
There are newer versions of the Intel drivers out there, but they're beta.
I'll bet DGP is pulling their data from station drivers. Not the best source.
DriverPacks.net Forum » Posts by mr_smartepants
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.097 seconds, 5 queries executed ]