[MadBoy]

I'm not sure it works thou Haven't been able to test it (only few comps so far). It uses all info i could find on some forums here..

Func DriverSigningOff(); Sets Driver Signing to OFF.
	RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing", "Policy", "REG_BINARY", "00")
	RegWrite("HKEY_CURRENT_USER\Software\Microsoft\Driver Signing", "Policy", "REG_DWORD", "0")
	RegWrite("HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing", "BehaviorOnFailedVerify", "REG_DWORD", "00000000")
EndFunc

Func DriverSigningOn(); Resets Driver Signing to DEFAULT.
	RegWrite("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing", "Policy", "REG_BINARY", "01")
	RegWrite("HKEY_CURRENT_USER\Software\Microsoft\Driver Signing", "Policy", "REG_DWORD", "1")
	RegWrite("HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Driver Signing", "BehaviorOnFailedVerify", "REG_DWORD", "00000001")
EndFunc

This post has been edited by MadBoy: 29 March 2006 - 11:53 AM

[MadBoy]

@donjuan
no need for more testing for now. I know where the problem is. Seems that when devices are removed from device manager by either hand (not 100% sure but think so) or devcon status from Unknown (device with problems: 28) is changed to Device with problems: 01 and is not longer marked as Unknown. So it will take me some time to redo the devcon search function and the whole process of device removal. Hopefully i will get some time at work to do this next version then should be language independant.

[donjuan]

MadBoy, on Mar 29 2006, 01:26 PM, said:

@donjuan
no need for more testing for now. I know where the problem is. Seems that when devices are removed from device manager by either hand (not 100% sure but think so) or devcon status from Unknown (device with problems: 28) is changed to Device with problems: 01 and is not longer marked as Unknown. So it will take me some time to redo the devcon search function and the whole process of device removal. Hopefully i will get some time at work to do this next version then should be language independant.

Thank u very much in advance.Your tool will be very usefull in my opinion, especially for unknown devices in presetup systems.Looking forward to your newer version..

[MadBoy]

@donjuan - I think i fixed it. But it needs testing. Pls report if it works. Check changelog for details. As for presetup stage, as i understand you mean the stage while the windows is still being installed, my program hasn't been tested for that issue so you need to report on that. The thing here is that Devcon isn't used when Unattended is set to On because windows detects new devices by default so doesn't need devcon to do it's job. So it does all the things that non-unattended option without Devcon Remove/Rescan. Plus there's no GUI for unattended mode. I might add it but need some reports how this version works atm.

[MadBoy]

New version is out. I rushed it a bit but thought i would share it before i end up starting a lot of changes to GUI and other stuff. So without further ado...
Download version 0.3.6 (Current with GUI)

Problems to solve:
- Signing of drivers isn't 100% working. Unfortunetly Microsoft implemented it the way it can't be realy done just by registry. Tests shown that also during change from Warn to IGNORE mode (My Computer -> Properties -> Hardware -> Driver Signing) besides standard registry keys that can be found all over the internet this key below also changes. On my computer it has 2 values (one for IGNORE and one for WARN). So unless i'll find a way to fix it.. Bummer. Maybe someone has some nice idea? Each computer has their own diffrent keys so it's not that simple as i seen on other forums in some posts

- HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\PrivateHash 15 CA EF C3 34 E8 C8 78
- HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\PrivateHash 01 32 A3 68 55 C2 D2 00

Problem of signing drivers on unnatended cd doesn't exist because you can set the right value in winnt.sif or sysprep.inf. Or so i have read on Microsoft pages Oh well, we will see..

Possible changes in next versions:
- Option to have copied drivers to C:\Drivers (or other dir you choose) and then using it
as the main driver directory. Mighty be usefull for ppl who like to leave the drivers
on hdd, and for use with pyron's method.
- Completly redo of GUI. As someone said GUI isn't good enough which i knew on begining,
but wanted to have something easy and done fast so i could see the progress going on.
So the project will have new GUI soon. Better, nicer. Maybe special GUI for congfiguration.
- Waiting for other ideas and problems.

Changelog for 0.3.6
- Added REMOVABLE drives to be autodetected (you can use it instead of CDROM or drive letter)
- Added function that will create hardware.ini automagically if there is no hardware.ini present (usefull ;p)
- Added option that opens Device Manager while devices are being removed/detected.
- Added option to use either RegistryDevicePath or SetupCopyOemInf by pyron


Would be nice if someone would give his opinion about this, especially about Driver Signing. Couldn't realy found good solution.

[Scrapple]

MadBoy, on Apr 4 2006, 06:14 PM, said:

New version is out.....

Changelog for 0.3.6
- Added REMOVABLE drives to be autodetected (you can use it instead of CDROM or drive letter)
- Added function that will create hardware.ini automagically if there is no hardware.ini present (usefull ;p)
- Added option that opens Device Manager while devices are being removed/detected.
- Added option to use either RegistryDevicePath or SetupCopyOemInf by pyron


Would be nice if someone would give his opinion about this, especially about Driver Signing. Couldn't realy found good solution.

Thanx, very nice of you to integrate setupcopyoeminf!

[MadBoy]

Np, just report errors New version is there. Little mistake on my side ;/ And can anyone report problem with redetection of devices? I mean like you had to do it manually in device manager to see the process started?

Changelog for 0.3.7
- Fixed multiple Device Manager instances being started

[MadBoy]

Just to keep you guys posted.. i decided to add some screenshot. Not best quality but will give you *HINT* on new features that will be implemented in newest version.

 hardware_0.5.jpg (49.6K)
Number of downloads: 264


New features:
- Full support for 7zip/Rar packed drivers
- Optional backup of c:\Windows\Inf directory before applying drivers
- New look
- Ability to configure .ini file thru GUI (not realy sure i need it but i'll try to implement it if i get time ;p)
- Possibility to copy drivers to for example C:\Drivers for later use (a must to set when using packed_drivers)
- Optional output to log_file (usefull for debugging)
- Optional output_option = Full/Simple - with Full mode on 99% of what's happening including output from external programs will be placed in log. (usefull for debugging but might slow down program a lot)
- Information if Windows require reboot to use drivers or not
- Automatic or Manual start (by pressing button).
- Auto autorun file creator for easy deployment on CD.

Suggestions are welcome as i haven't done everything yet so i can change things. Later on it will be much harder (althought with log window instead of preset GUI it's much easier to change things.

Hope you guys will like the changes in new version. Hopefully out sometime soon.

This post has been edited by MadBoy: 10 April 2006 - 10:41 AM

[xboxhaxorz]

The part about removal of unkown devices is kind of limited. How about i had a driver that was installed but had a ? mark or another driver that had the wrong driver installed. The fact that it resolves unknown devices is great, but usually thats not the case as windows has the drivers for that device already.

[LDST]

So is this project still alive?
I could use this functionality in our corporate upgrade project.
Basically I'm at the point that after the first logon by the user (post Win2k -> XP Pro upgrade finishes), on several types of our HW, the NIC (hardwire and wireless) were not detected properly and are listed as unknown devices. I've been able to prove, via manual method, that uninstalling/removing the unknown devices and doing a new hardware scan will then detect the devices and pick up the driver from the C:\Windows\NLDRV\001 (or 002) folder (I've used nLite to integrate the drivers, works fine). For some reason these drivers are not sensed or found during the device detection phase.
Remember, these are upgrades, not clean installs... Clean installs with the same source set created via nLite works right completely, all drivers found and installed correctly.

So, I need a way to have the upgrade finish installing the right HW drivers...
The basic thought is to:

1. Have a script/batch file fire off from a RunOnce key (which I can't get to work either with an upgrade, but that's another story)
2. Check the registry to ensure the right DevicePath is set or force it to the desired paths (I have this working with a command in a script)
3. Remove all unknown devices (don't know for sure how to do this, but maybe "devcon -remove =Unknown" might work ?? )
4. Re-scan HW to detect the devices and install the right driver (again, I think "devcon rescan" ?? )
5. Reboot the PC

So, anyone out there with some insight on doing this?

[Bâshrat the Sneaky]

What is that 'Problem ID' column about?

[Lost Soul]

this is a great looking app, i think this will come in handy,, keep up the good work

[qwerty009]

Great app, can't wait for next release. Any idea when you might have next vers ready?

This post has been edited by qwerty009: 27 May 2006 - 05:43 AM

[MadBoy]

The project still alive although i kinda stopped developing last few weeks/months due to enormous time i had to spend on other things. It's kinda ready just one little bug that makes the program crash + i need to fix/add minor things but that can be done later on. I kinda stopped developing it due to hardly any interest from ppl (you know, when it's free and you don't see ppl wanting that you don't do it ). Anyway i plan to release it since i noticed few ppl want it so it will come.

@Bashrat:
problem id column is what Device Manager states as device error code. When you go to devices that are unknown or with problems there's always a number next to error that it states. The error list can be found here. Only some "errors" are fixable by just removing device from device manager and are drivers related. Other problems usually are more serious problems that shouldn't and won't be solved just by device removal. But for maybe "future" features i added it to show the problem id number.


@LDST - my program if it would be ready and fully working can do that for you ;p devcon -remove =Unknown is one thing but it sometimes doesn't work as the device may have been marked as "problematic" and not realy unknown. I solved it by doing a lot of reasearch on how devcon works and what changes. So my program usually check for that "problem id" that i explained to bashrat and when it founds the right codes (only 2-3 of them are drivers related) it takes device id and removes them. Then devcon rescan and woila

xboxhaxorz - my first version was only looking for Unknown devices indeed. Problem with it is that after first devices removal they are no longer marked unknown. Also like you stated some device have just drivers problem. Well the new version works diffrently as i stated in this post.

I'll try to release 0.4.* version during this week or so.

Chears!

[MadBoy]

New version out. A lot of changes including hardware.ini so read first post carefully. Ideas, suggestions, bugs are welcome

[Avneet]

am using it but the add hardware wizard things comes up wheer u have to browse for the location of the drivers..

is that normal.. doesnt this program autocmatically scan the folder we define

[Avneet]

bump

[MadBoy]

Yeah, i encountred this problem several times too. Usually it happens when there is more then one driver on CD/Directories that matches the criteria. In cases where things weren't doubled up the Wizard didnt come up.

[Avneet]

umm thast a bumer.. hope this can be fixed.... i dont have copies of the same driver in the DIR.. but many driversfrom the same company.. i think it shud be able to pick up the appropriate driver automatically

This post has been edited by Avneet: 13 July 2006 - 02:31 PM

[MadBoy]

Well it's not realy in power of my program. It's more like windows behaviour. What can be done is to check if there are registry entries that could disable that behaviour or eventually implement, what in autoit3 shouldn't be problem automatic 'click' next next next so user interaction wouldn't be required. I'll have to look at it. I don't realy want to use 'screen interaction' as this won't be 'nice hack'. It will be visible for user which makes the program a bit unproffesional, but it also might be the only way I've seen some drivers getting installed that way, like Toshiba bluetooth which was using similar way to interact with windows questions, but it was ugly to me.

I'll try to see how to fix problem, but i lack time latly since i am in the middle of changing jobs and i have other responsibilities now.