kickarse

v4.5 is out! Check the change log for all the changes!

Same thing happened for me but can't reproduce this behavior. All other functions of the app seem to work fine other than those mentioned above. kickarse is working on a new update to address these issues and add additional options no i had never used or uninstalled DF install, v44 is the first one i use. But here is a funny thing, before posting this message, i doubleclick on driverforge.exe again and vala, it didnt open. (tried many times with double clicking DriverForge.exe) i put it in E:\1 folder with a name DriverForge.exe, and no it didnt open. i also observed taskmanager, in taskm, DriverForge.exe shows up for a second (or less) and disappears. BUT as my main purpose is using this utility in livexp/bartpe, there never a problem like that yet. (i made many many test with them), this only happens when using my os. Maybe this bugy is about 2003x64 i am using so sometimes it works in 2003x64 and sometimes it doesnt work. (ps: i know this is not for x64 environment, i double click it just to see gui) if i find a method to reproduce the problem, i will inform. hahaha, at the end of this message, before i press send, i double click on DriverForge.exe and it started (driverforge.ini was deleted in previous trials) . for a solution lets say, if it doesnt start, delete driverforge.ini (maybe not necessary) and deal with other things for a while, than try to start DriverForge.exe again. Every once in a while it doesn't unload itself properly from memory and I don't know why. Amalux has the link to the new test version. If you want it Lance let me know. I haven't tested in x64 or 2003 so I'm unsure as to what processes are crashing. We'll see if I can change this error checking code I have that checks to see if it's already running. That seems to have been the issue in previous versions with it not starting up again. A couple things 7zLoc and DriverExtract are now called Compressed_Driver_Location and Uncompressed_Driver_Location, so 7zloc and Driverextract won't work in versions coming. Both can use CD\ to specify the current folder DriverForge is being run from. The Uncompressed_Driver_Location can use option None to specify no driverpacks. The new option is to use Windows native installation process using syssetup.dll or use HWPNP. It's possible I have a HWPnP command line error. Update_All_Hardware is now Use_Windows_Method_For_Driver_Install, setting Y or N. I'm working on v4.4.4 so I'll turn that error checking off. I've also updated the changelog.

Possibly at some point. But I wanted to make sure it worked first before I added additional functionality. I updated the post at boot-land. Is it just the image Amalux?

Phew! Are you going to re-screenshot for boot-land?

v4.4 is up! It's easier to setup and less convoluted.

Any updates on this?? Thanks!

What does vista use if you don't mind telling? I would love to add the ability for my DriverForge program to install for both systems.

v4.3 is up and available for download. It has an internal driver import function now. So hopefully no errors!

I think you should ask in the Pro-S hardware thread http://www.msfn.org/board/Drivers-Instalat...tag-t70209.html You'd probably get more of a response...

Ahh, I'm not sure why but I'm planning on rewriting the driver import/scanning function instead of using a third party tool. The program won't allow you to slipstream your drivers onto a cd. You can use nlite for that though. Or bashrat's driverpacks.

Can you search your computer for the file syssetup.dll and let me know it's full path?? And possibly send me your 2k version of the syssetup.dll file?

It's also possible that the user your trying to use is cached in the system somehow. So a restart and login as a different user will fix that.

The file from MS also has the same CRC, SHA1 and MD5 as the files from Softpedia and MajorGeeks.

Careful Witt you might be banned for posting a link...

I wonder if Softpedia will be forced to take down hosting of SP3 RTM?? Anyways, that version is legit. Installed, WinVer gives a build 5512. MSInfo32 gives a Version 5.1.2600 Service Pack 3 Build 2600. Just the same as Paul Thurrott's screen shots. OH, and a great program for hashes is called Hash Tab http://beeblebrox.org/hashtab/

windowsxp-kb936929-sp3-x86-enu.exe size 331,805,736 bytes crc32 c411a9da md5 bb25707c919dd835a9d9706b5725af58 sha-1 c81472f7eeea2eca421e116cd4c03e2300ebfde4 All that info is correct, well at least with the file I have... There's already an update for SP3 http://www.microsoft.com/downloads/details...;DisplayLang=en

Release to Manufacturers, there'll surely be a leaked copy somewhere. I still don't understand why they torture us peons.

I've only tested in XP. I don't know if it'll work on 2000. Can you print screen the error??

Just use the options [AutoInstall] ShowDevMgr=Y [Driver] 7zRoot=Y 7zRootLoc=Path\To\Driver\Folder ... DriverExtract=%systemroot%\Drivers 7zLoc= I would suggest that if you're going to delete the drivers that you put them in a folder other than %systemroot%\INF . Because it'll delete the folder %systemroot%\inf . The program would be on the CD-Rom and the folder for the compressed drivers would be in a the same folder as the program. So %cdrom%\DriverForge\DriverForge.v4.1.2.exe and %cdrom%\DriverForge\CompressedDriversFolder I have to redo the drivers location approach. It's a bit convoluted and confusing. Soon it'll be just 7zRoot and 7zLoc, and DriverRoot and DriverExtract, nixing 7zRootloc and DriverRootLoc.

That's seems like a nice program! However, there are two other options also available... http://www.msfn.org/board/DriverForge-v412...er-t110783.html and http://www.msfn.org/board/Drivers-Instalat...hod-t70209.html

I don't see why not, it should work fine.

Yeah I fixed that issue. If you select to delete drivers then it'll revert it back to whatever was there before.

That should work. Or you could try @systemdrive . And yes to your first question.

v 4.1.2 (more of an interim to more gui changes) out!

Sorry i've been out of touch with the internet. I'll get to this tomorrow. I'm off to sleep.