kickarse

Your right... I'm stuck in the past!

Big updates to v2.6.3!

Very cool! I'll also try this out. Right now I'm using Mars Installer though.

Update v2.6.2

Update v2.6.1!

I suggest that you DONT integrate SP3 RC1. Wait, just wait, until the final. You'll do more harm than good. There's also the issue with it not supportting HD audio btw (KB88111).

v2.5 Updated! http://www.msfn.org/board/index.php?s=&amp...st&p=728341

V.2.4 Updated! See - http://www.msfn.org/board/index.php?s=&amp...st&p=728341

Geek, why don't you use Pro-S Hardware Installer, it has the features you ask for It's a bit more advanced thou and requires some settings lol... pimp I just built a version to handle removable media detection. So if the program is here at X:\Path\To\Program it will find that it's at X:\ and then you must put in the rest of the location to the drivers, so Path\To\Location\of\Drivers. From the root of the removable drive the program is being run from not relative to the location of the program itself. If you want that use OEM. Still working out some kinks though, like the auto detection of compressed files in the location on the removable drive.

You want it to find if the removable drive folder has compressed (7z files) drivers and if it does extract them to a location on the hard drive and install the drivers from there OR else if it doesn't find compressed (7z files) drivers to install from the cd location?

lol... ok... I'll see what I can do Here's what you can do currently... X:\Path\To\Program\OEM (compressed drivers) But, (and what I'll be adding anyways) What your asking, I think, is that you can specify X:\Path\To\Program\Driver\Folder\You\Set (compressed drivers) X: drive being created on the fly... I can make it so the drive is relative to where it's being run from or relative to the folder and drive it's being run from So one will give X: and the other would give X:\Path\To\Program. I think I am going to do relative to the drive it'll be run from and then you can write in where. I'm guessing your using this feature for the unattended install?

Here it comes Sooner or later you will end up like me Having so many features you can hardly track where is what ;P BTW. Your CHECKFORWIZARD() function isn't the best considering that you hardcoded english title, also WinActive isn't nessecary i think. Also why do you put both 7zip.dll and un7zip.exe into the .exe shouldn't one be enough? It won't uncompress without the 7zip.dll. And the checkforwizard() was made so far only for english. PID's change and two processes are using rundll32. The winactive probably isn't needed but if it steals focus while it's running it'll need to close it. I'm not planning on adding many features or any more after this one requested. There are some that I want to add though. That's why it's called the blunt force driver installer, not the be all and end all. Mostly created for my own use at work. Hey don't you encrypt your code? And are you still using Autoit?

I'll add that option

updated to v2.1!

Nice guide... just curious on if WFPSwitch still works? I haven't needed to use it because of my Nlited cd's and I'm not getting the error post sp3. WFPswitch.exe

DriverGeek v0.5 Beta 1 http://drop.io/wanderingit/asset/splash-01-jpg'>http://drop.io/wanderingit/asset/splash-01-jpg //-- Download --// http://drop.io/wanderingit -- click DriverGeek for the beta download //-- Version History --// v0.5b1 - 2010-04-30 - Beta 1 for public trials //-- Introduction --// DriverGeek was designed from the ground up to be an easy and intelligent driver installation tool; replacing the aging tool DriverForge. It will automatically find and install all hardware drivers based on the driver paths that you select. The current version of DriverGeek will run in all supported x86 Windows operating systems (2000/XP/2003/Vista/2008/7 and PE's based on these); an x64 version will be released in the future but has not been compiled yet. //-- Usage --// To use the program is simple. Edit the dgconfig.ini file to set your configuration and then run the program to install the drivers. The first time you run the program it will create the dgconfig.ini file with all options. It will then open the ini file for you to edit it. Save the ini file when you are done editing. The ini lives in the same root directory as the program. To put it into perspective the only option you really need to supply is for the section [Drivers] and a uncompressed drivers path for the option DriverSearchPaths. The settings below can be configured: [Main] ; Run without prompts and progress even if prompts help, this has not been fully implemented, only for tooltips ; Blank defaults to 0 = No, 1 = Yes RunSilent= ; Reboot after install completes ; Blank defaults to 0 = No, 1 = Yes Reboot= ; Show Windows Device Manager during installation, it will close when driver installs have finished ; Blank defaults to 0 = No. 1 = yes ShowDeviceManager= ; DpInst.exe is used in installing the drivers to the system. If DPInst.exe cannot be found or supplied the ; program will ask if you would like to default to Windows 2000/XP/2003 x86 default driver installation method ; using Rundll32.exe ; The temporary folder for running DPinst.exe from is deleted when the program exits ; Blank defaults to %temp%\drivergeek\bin DPInstPath= ; Accept Software EULA, you must accept the EULA to run the program ; Blank defaults to 0 = No, 1 = Yes AcceptEula= [Drivers] ; Search Paths, multiple paths, or even INF file(s), separated via Pipe symbol ; Environment variables work with this option. DriverSearchPaths=C:\D|C:\Windows\inf ; The software will automatically append the current programs directory your driver search path ; Blank defaults to 1 = Yes, 0 = No ScanScriptDir= ; Search drives found, options are: ; ----> ALL, CDROM, Removable, Ramdisk, Fixed, Network (and Unknown, but shouldn't need to be used) ; The option "All" will take the place of needing to enter the rest of the options and will add all drives found ; You can add one or multiple, separating them with a Pipe symbol ; Blank will not search any "drives" for drivers DriverSearchDrives=CDROM|REMOVABLE|RAMDISK ; Has not been implemented but will allow extraction of compressed drives from the path supplied ; and then extracted and installed from. This feature has not been implemented yet. The extracted drivers ; path will be appended to the DriverSearcPaths option. ; If a compressed drivers path is specified and a extract path is not the program will default ; to extract to %temp%\drivergeek\drivers and will be deleted after drive installation has completed ; If the program cannot extract to any directory extraction will be terminated, if no other driver ; path is specified the program will exit CompressedDriversPath= ExtractDriversPath=

If they are the Realtek HD Audio ones you need the KB888111 installed previously.

It does not yet have the ability to add anything other than ONE 3rd party compressed driver file. I hope to be able to add the ability in the future. However, I have taken over development of this program. I opened a sourceforge.net account for versioning and downloads. I just added support for an unattended installation but I need to get SF.net up and running and I'll load it up there and share the link.

There are actually two main purposes for such a product: 1) Migrate user data and applications from one type of computer system to another without the need to reinstall everything 2) Create an image that works on any type of hardware configuration Cheers Do you have a guide on how to use it?

Same program, we're both working on it. Just he has to be away so I have to get it updated. Just so it's clear, you can use any uncompressed drivers, not just DriverPacks uncompressed. For instance if you've downloaded drivers from Realtek or VIA and put them in the Uncompressed location you can install your own drivers without making a 3rd party driver pack.

Yeah I saw that one... It's crazy that he scripted that whole thing. Hopefully it'll be in the next release as a udf and I really hope it's well documented.

Update! DriverForge v.1.0d Look at the first post for the update! -- Next to be implemented ----- Fully automated DriverPacks installation -- Thanks to AutoIT forums, MSFN.org forums, Vernalex, MadBoy, Wixfigura, 7zip utility, Bashrat Sneaky and his crew and the DriverPacks forums.

MadBoy what XML DOM wrapper did you end up using? Coming along nicely btw!

Also it would be nice to query some foreign server (like driveragent.com ) for the absent drivers, and then download them on-the-fly. Or we could create a special server with driver database for that. All in due time my friend... let's just get the base of this working first.

Care to elaborate? Also How'd you get the icons to show the text to the right of it?