kickarse

Hey guys Df has been depreciated and a new piece of software has been built from the ground up based on my work on FindHWIDS. http://drop.io/wanderingit - click on DriverGeek

Thanks JDarg!

v.5 - 2009-06-12 + Fixed issues with DevicePath registry settings, will revert back to original location previous to DriverForge installation - Removed Pre and Post scripts, users can do that with a batch and automation - Fixed GUI wording + Added an option to add default Windows DevicePath to registry + Made all files install to Temp folder + Fixed edit code to delete all installed temp files I'll be releasing the code shortly.

Yes you would take out what's there now and localize it to your own language. Ability to scan in parent dir sub folders for compressed drivers in said sub folders. I can do that Add it C:\Netint\postinst.js to the Switches part of the section. So Post_Script_Switches=C:\Netint\postinst.js

Don't worry people I haven't forgotten about you all! I've been working on a program called FindHWIDS and haven't had any time to focus on DriverForge. I'll do so soon enough and fix some bugs and add some nice functionality. Please let me know what features you'd like to be added. We'll see if we can't add them for you.

Just so your aware that FindHWIDS v3.2f is out.

I think you guys forgot one... Free Ghost - http://www.fogproject.org I've used it and it's nice, fairly easy to setup for a advanced user. But it's still in its infancy.

That's not actually correct (then again I'm not a lawyer)... The only thing I can find that would stipulate anything about hosting the source is documented at the Terms of Use stating "© you have fully complied with any third-party licenses relating to Your Content, agree to pay for all royalties, fees and any other monies owning any person by reason of any of Your Content that you posted to or through SourceForge.net;" and "For the SourceForge Site SourceForge.net, use, reproduction, modification, and other intellectual property rights to data stored in CVS or as a file release and posted by any user on SourceForge.net ("Source Code") shall be subject to the OSI-approved license applicable to such Source Code, or to such other licensing arrangements as may be approved by SourceForge.net as applicable to such Source Code." But, alas, I'm not going to get into a p***ing match with you, or anyone, over this. And I never once stated I would not show anyone the source. The only thing I stated is that it's not ready for public viewing (in so many words). If anything take it up with SF and GPL. I'm sure they have so much time to worry about my little program built in AutoIT. Have them remove it. I really don't care. I made this program to be useful to people, not to have to worry about this s***, "oh I want the source Mommy! Why can't I have the source!?" Who are you Veruca Salt? Because, that's what it seems like to me. But if you really want it THAT badly and THAT quickly you could always decompile it quite easily. Or you can just pm me your email address.

You do realize that not everything on sourceforge has the code freely available. Nor is it in the contract to host programs on sourceforge. However, certain licensing terms to certain licenses do grant anyone access to source code of certain applications. It was never actually licensed properly btw. Meaning what I stated didn't make it licensed under any known licensing schema. I'm not saying I wouldn't be glad to offer it (besides finding the time to do so properly). But it's not written well and isn't commented at all. Besides my program is little more than a nice batch script for running RunDll32.exe Syssetup.dll,UpdatePnpDeviceDrivers.

It's not currently available A very very old version does lurk around here somewhere.

v4.5.3 is out checks the Read Me for full change log. Added some fixes for Driver Signing Policy and fixing inf locations after running the driver installation.

oh, btw, v4.5.2 is out! Check the help file for INI configuration and usage changes.

That's because that's what your device path was before! If you do driverpacks twice it'll use whatever you had last. Plus, if you didn't have anything in there to begin with it'll add what you scanned as default. At least, that's what I think So if you could test by changing that value to the default value and then run DriverPacks and see what happens that would be great! I think I have it setup so if you aren't using compressed drivers it'll keep the location of the drivers in the registry. However, as you've shown, it's probably better to always revert to the original. That'll be fixed in 4.5.2

oh and v4.5.1 is out

It should set it back to what it was originally. I'll check on that.