[jinkazama]

MadBoy, on Nov 6 2009, 12:49 PM, said:

You can. You have to either use RELATIVE:\Drivers where RELATIVE means that program resides on the same drive that Drivers directory is. Or you can use REMOVABLE:\Drivers which should point to usb pendrive in drivers_directory_path.

I have tried both solutions but always same error
i have all in a directory RELATIVE switch should point to Driver directory...

This post has been edited by jinkazama: 06 November 2009 - 06:05 AM

[MadBoy]

jinkazama, on Nov 6 2009, 01:05 PM, said:

MadBoy, on Nov 6 2009, 12:49 PM, said:

You can. You have to either use RELATIVE:\Drivers where RELATIVE means that program resides on the same drive that Drivers directory is. Or you can use REMOVABLE:\Drivers which should point to usb pendrive in drivers_directory_path.

I have tried both solutions but always same error
i have all in a directory RELATIVE switch should point to Driver directory...

It's incorrect. RELATIVE means it's only RELATIVE disk drive letter so what program is looking at when you have RELATIVE:\Drivers is M:\Drivers. Since you've put it in M:\Driver PRO-S the correct path in .xml is RELATIVE:\Driver PRO-S\Drivers or REMOVABLE:\Driver PRO-S\Drivers.

Btw. I've noticed you have some icon next to it (diffrent icon). May i ask why? :-) Also it seems like nice Icon. Maybe you want to share. If it looks good here I could replace the standard one I am using :-)

[jinkazama]

Here my icon, if you like it you can use for your software.
I've solved, thank you

Attached File(s)

•  pro_s_hardware_installer_2.0.0.25.ico (26.07K)
  Number of downloads: 9

[MadBoy]

Quote

- Updating drivers runs, but does not update. I have in fact updated drivers for Via Rhine Ethernet card but it does not install. The same happens with C-Media Sound.

I found the following: If the .inf has some hardware ID without "&subsys" string it does not install. I had to edit the .inf and add the subsys string, after that it was picked up by the program.
Example:
VEN_1106&DEV_3108
Does not install driver.
VEN_1106&DEV_3108&SUBSYS_31081414 installs fine.
The program should not look at the subsys. Let Windows figure it out. Or else, I would have to edit some of my .infs?

By updating drivers you mean Update All xml entry ? If yes then it doesn't work for simple reason. By using new way of finding drivers it searches for only those devices that have error codes. So if 3 devices have errors, 3 .inf's will get added to registry. I'll think how to make it work better. Probably will have to list all hwids from all devices added to system and then compare that with db and then add that entries to registry. I'll add it to ToDo list.

If it's some other problem you have lemme know and I should investigate.

[MadBoy]

Escorpiom i've just checked your logs further and it seems P&P won't work 100% for you anyway.

This is because of first window having:

[05:17:27] - [WINDOW] DEBUG: Button count:8
[05:17:27] - [WINDOW] DEBUG: Button 1 button_class_nn:[CLASSNN:Button1]
[05:17:27] - [WINDOW] DEBUG: Button 1 button_text:&Sí, sólo esta vez
[05:17:27] - [WINDOW] DEBUG: Button 2 button_class_nn:[CLASSNN:Button2]
[05:17:27] - [WINDOW] DEBUG: Button 2 button_text:Sí, a&hora y cada vez que conecte un dispositivo
[05:17:27] - [WINDOW] DEBUG: Button 3 button_class_nn:[CLASSNN:Button3]
[05:17:27] - [WINDOW] DEBUG: Button 3 button_text:&No por el momento
[05:17:27] - [WINDOW] DEBUG: Button 7 button_class_nn:[CLASSNN:Button7]
[05:17:27] - [WINDOW] DEBUG: Button 7 button_text:Cancelar

which translates to something like check on internet .. i guess to go further you have to pres No por el momento ? or what do you press here ?

[Escorpiom]

Yep Madboy, that's right.
First pops the Internet update wizard, it does that because the system is already connected to the net at that stage.
So first I check the option "No por el momento" and press the button "Siguiente" if I remember correctly.
Then, another option presents itself: Instalar automáticamente el software (recomendado)
Or
Instalar desde una lista o ubicación específica
I select Automaticamente and yes, finally the driver is installed.

There is a registry patch to disable the Internet driver update prompt. I searched for it but only Nlite seems to have that option. My last build does not have that activated.
Would like to get rid of that darn Internet update prompt. Never use that anyway. You might have some tips?

Cheers,
Escorpiom.

[MadBoy]

Manual way to disable searching for drivers on Windows update:

Quote

The required driver is missing when you are installing a device. Windows XP Prompts you to go online and search for the driver using Windows Updates. However, experience tell you that is absolutely useless and will only be adding to your hassle.

Usually a driver is included on a CD provided with the device you have purchased. If this is not the case for some reason, you can always download the software from the device manufacturer's website. Why not disable the unnecessary request to search for drivers when you can install them much faster yourself.

The Go to : "Start > Run" and type "gpedit.msc"(without quotes) and navigate to:

Local Computer Policy > Computer Configuration > Administrative Templates > System

Section on the left pane of the window. Now choose and double click on "Turn off Windows Update device driver search prompt". In the window that appears, chosse "Disable" and apply the settings.

Registry way (can be automated, most likely this will end up in tool as option): http://www.pctools.c...ry/detail/1217/

This post has been edited by MadBoy: 06 November 2009 - 10:36 AM

[Escorpiom]

Madboy, I made a reg entry for that in my reg tweaks file. It will be processed at T-12.

SET KEY=HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
REG ADD "%KEY% /V NoDevMgrUpdate /T REG_DWORD /D 00000001 /F

Will this work to disable the Internet update prompt?

Found the group policy entry also, but manual disabling is not an option I'm afraid.

Cheers,
Escorpiom.

[MadBoy]

I would check if it works when you apply it in windows manually. If it does then it should work at T12.

See if this helps:

Go to Start menu, right-click on Computers and click Properties. On the left sidebar of the System dialog box, select Advanced System Settings. Now navigate to Hardware tab and click Windows Update Driver Settings. Not sure if this exists on Win Xp as i use 7 for now. Lemme know if it's there. If the switch is there try playing with applying the setting in reg.

Seems like vista http://malektips.com...ice-driver.html but might be in XP too, can't find it in 7.

This post has been edited by MadBoy: 06 November 2009 - 11:17 AM

[Escorpiom]

The most annoying ting in computers is the fact that something seemingly easy results to be the opposite - so with this reg fix.
Disabling the windows driver update by Internet is controled by group policy. The reg fix I made has no effect whatsoever.
I did the trick with the hardware tab (yes it is there on XP but slightly different) and the changes made there were put in the registry under group policy.
I cannot export the key, as it is under a special random key, different for each system/user.

Pretty nasty. So far no solution found.

EDIT: Found the correct keys. These are the reg entries.

REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontSearchWindowsUpdate /t REG_DWORD /d 1 /f
REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontPromptForWindowsUpdate /t REG_DWORD /d 1 /f
REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontSearchCD /t REG_DWORD /d 1 /f
REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\DriverSearching /v DontSearchFloppies /t REG_DWORD /d 1 /f

The Internet update wizard died today. Yeah!

Cheers,
Escorpiom.

This post has been edited by Escorpiom: 06 November 2009 - 02:59 PM

[MadBoy]

It's good that you found correct solution. I'll probably add it to the list :-) Also was thinking to add that Hardware Wizard management option for case when it's still enabled. We will see. At the moment I've been playing with C# and Backup Drivers app. Need to find out how things work so maybe i'll release easy to use app to backup all drivers from system.

MadBoy

[Escorpiom]

I haven't had the time to test your latest release in combination with the reg fixes, finished the last XP based system earlier. The wait is now for another "victim" to test the program.

Before pro-s driver installer I was planning to do the method you describe: Backup a complete driverpackage and later on deploy that on another system.
I'm a tech. I work mainly with low budget, integrated hardware and notebooks. The plan was to separate driverpacks based on platform, for example Intel, SiS, Nvidia or Via.
Speed is the main concern, and automated processes will give me more time to do something else. Precious time!
So.....I will be following your inventions. What I like about Pro-S is the xml config. Very simple to setup, yet a lot of options.

I'll report back as soon as I have another system to test.

Cheers,
Escorpiom.

[pSycho-Y2K]

Just wanted to say that your latest release solved all of my problems now! Thumbs up for your impressive work!

[Escorpiom]

I'm happy to report the same, finally all issues have been resolved.
Window managing is done correctly now, making the process totally unattended.

I'm now playing with 7z compression to bring the size down. Decompressed drivers take up a huge space on my
harddisk. Hope it won't slow down the program to much.

Thanks again Madboy for your work on this tool, it is very much appreciated.

Cheers,
Escorpiom.

[Escorpiom]

Madboy, please bear with me. I know I'm a pain but it's all for the better.

I forgot to ask you about the subsys string issue, I had to edit some of the .inf files because they lack the subsys string and then the search&match function does not work.
If no subsys string is specified in the inf, the driver is not installed.
Look at the log file:

[DRIVERS] Running SEARCH & MATCH function. Please wait...
[03:33:41] - [DRIVER] Device => PCI\VEN_8086&DEV_24C6&SUBSYS_53494C21 Driver Path => NOT FOUND in DB
[03:33:43] - [DRIVER] Device => PCI\VEN_8086&DEV_2562&SUBSYS_25621849 Driver Path => NOT FOUND in DB
[03:33:43] - [DRIVERS] SEARCH & MATCH function found 0 matching drivers
[03:33:43] - [DRIVERS] SEARCH & MATCH function found 2 drivers that have no match. Oh dear..

The inf's had only the first part specified:

PCI\VEN_8086&DEV_24C6
PCI\VEN_8086&DEV_2562

After adding the entry in the .inf including susbys, it works marvelous.
But you would save me a lot of work if the search&match function ONLY looks at the first part, that is VEN_XXXX and DEV_XXXX
That way I don't have to edit all the inf's.

Can this be done?

Cheers,
Escorpiom.

This post has been edited by Escorpiom: 27 November 2009 - 03:20 AM

[MadBoy]

You shouldn't edit the inf files. Actually i think inf files shouldn't be touched at all as they may break things. I should fix this, as I'm pretty sure it's my fault :-)

[MadBoy]

Escorpiom please get the newest 2.0.0.27 and see if it works for you.

[Escorpiom]

MadBoy, on Nov 27 2009, 04:55 AM, said:

Escorpiom please get the newest 2.0.0.27 and see if it works for you.

Your updates are faster than I can test them
I'm already quite pleased with the program. At the moment I'm using a XP distribution share with integrated LAN and MS drivers.
From ROE a batch is run to map the network drive where all the drivers are. The program hardware installer and hardware.db are also on this network drive.
After the drive mapping, the program runs from ROE. Drivers are installed, program exits and the rest of the programs are installed from ROE.
I do not recreate the hardware database anymore in automatic mode. It takes too long.
If the some drivers are added /updated on the server, or the folder structure changes, I run the program from the server and manually create a new hardware.db.

This way, the whole installation process is completely unattended, while maintenance is easy (integrating hotfixes and some ap from svcpack)
I can easily go and do something else, after a while the system will be ready.

Agreed, editing inf files is not recommended. Hope it won't be necessary anymore with the new version.

I have another request. It is about the "copy driver" option in the XML file. When activating it, it will copy EVERY driver to the local disk specified.
It would be nice that ONLY the drivers needed for that system are copied, not all drivers. You can perhaps do this in combination with the search&match function.

Will test the new version asap and get back to you. Thanks again, nice work!

Cheers,
Escorpiom.

[MadBoy]

Escorpiom,

I do hope you know about map feature in the app itself right ?:-) But i guess you keep the program on share for easier maintenance with newer versions.

As for the copy feature it would be doable but it's not easy. I would need to realy get into .inf files and as you probably noticed my question on this board regarding backing up inf's i'm having a bit of problem with this :-)

[Escorpiom]

Spot on.
I prefer not to copy stuff when it's not needed. It has do be deleted afterwards anyway. And yes, keeping it on the share is easier.
As far as the mapping, it's a neat future but I don't need it.

Today I tested the new version and although I could not verify the subsys issue, came across something else. It's a little difficult to explain, please ask me if you don't understand.
I have the inf from C-media audio driver. It contains a lot of device id's. Will attach the file here.
For some strange reason, the hardware database is limiting the amount of device id's added. Please note my hardware.db is about 10MB at the moment.
For example, VEN_8086&DEV_24D5&SUBSYS_97611849 were referenced in the inf, but did not show in the hardware.db!
Only the first 53 lines from the 24D5 device were added, the rest was ignored.
You can see that the 8086 24D5 section has a lot more entries, I guess more then a hundred in total.
Because of this, the hardware was not installed. Error: Driver path not found in DB.

PCI\VEN_8086&DEV_24D5&SUBSYS_18841019,\Sound\Cmedia\CMI_SIS_VIA_AC97\WDM\CMICHX.INF,cmuda.cat,Unknown,
PCI\VEN_8086&DEV_24D5&SUBSYS_18851019,\Sound\Cmedia\CMI_SIS_VIA_AC97\WDM\CMICHX.INF,cmuda.cat,Unknown,
PCI\VEN_8086&DEV_24D5&SUBSYS_18861019,\Sound\Cmedia\CMI_SIS_VIA_AC97\WDM\CMICHX.INF,cmuda.cat,Unknown,
PCI\VEN_10DE&DEV_006A&SUBSYS_0A171019,\Sound\Cmedia\CMI_SIS_VIA_AC97\WDM\CMNVDA.INF,cmuda.cat,Unknown,
PCI\VEN_10DE&DEV_006A&SUBSYS_0A181019,\Sound\Cmedia\CMI_SIS_VIA_AC97\WDM\CMNVDA.INF,cmuda.cat,Unknown,
PCI\VEN_10DE&DEV_006A&SUBSYS_0A191019,\Sound\Cmedia\CMI_SIS_VIA_AC97\WDM\CMNVDA.INF,cmuda.cat,Unknown,

As you can see, the last line referenced in hardware.db is "PCI\VEN_8086&DEV_24D5&SUBSYS_18861019", after that the Nvidia section starts. But there are a lot more entries in the .inf file!

Either:
- The hardware.db is size-limited (10Mb?) and because of that the number of entries are cut-off
or
- Only a certain amount of entries per .inf file/device id is allowed/added to hardware.db

What could be the issue?

Cheers,
Escorpiom.

Attached File(s)

•  CMICHX.INF (54.43K)
  Number of downloads: 4