[MadBoy]

Okey the problem isn't with drivers. The problem seems to be with detecting the devices without drivers. Can you post me screenshot of your device manager where it is clearly visible you have device without drivers or with special icon next to it?

[Kingskawn]

I made a new install and this is the log. Done with the same xml

[11:57:11] - =================== START - PCX - START =================== 
[11:57:11] - [INFO] Started program on computer PCX.
[11:57:11] - [INFO] Detected system is Windows XP x32 Service Pack 2.
[11:57:11] - [DRIVERS] Directory with drivers (Z:\) exist. Continuing...
[11:57:11] - [DRIVERS] Using NEW method of drivers instalation. Good Luck!
[11:57:11] - Discovering basic information about all system devices..
[11:57:12] - [DEVICES] Simple Information gathering took 0.99 seconds.
[11:57:12] - Discovering advanced information about all system devices..
[11:57:17] - [DEVICES] Advanced Information gathering took 5.19 seconds.
[11:57:17] - Cleaning up devices list from non-essential devices...
[11:57:18] - [DEVICES] Cleaning Devices took 0.18 seconds.
[11:57:18] - Building up simple devicelist...
[11:57:18] - [VIEW] Drawing simple device view took 0.57 seconds.
[11:57:18] - Building up advanced devicelist...
[11:57:20] - [VIEW] Drawing advanced device view took 1.7 seconds.
[11:57:20] - [VIEW] Building up error devicelist...
[11:57:20] - [VIEW] Drawing error device view took 0.06 seconds.
[11:57:20] - [DRIVERS DB] Running PREPARE DATABASE function. Please wait...
[11:57:21] - [DRIVERS DB] Ending PREPARE DATABASE function. Execution time was 1.28 seconds.
[11:57:21] - [DRIVERS] Running SEARCH & MATCH function. Please wait...
[11:57:21] - [DRIVER] Device => PCI\VEN_8086&DEV_2572&SUBSYS_02871014 Driver Path => NOT FOUND in DB
[11:57:21] - [DRIVERS] SEARCH & MATCH function found 0 matching drivers
[11:57:21] - [DRIVERS] SEARCH & MATCH function found 1 drivers that have no match. Oh dear..
[11:57:21] - [DRIVERS] Execution time for SEARCH & MATCH was 1.39 seconds.
[11:57:22] - [SEARCH] Removing duplicate entries from INF list.
[11:57:22] - [DRIVERS] Setting path into registry using RegistryDevicePath method.
[11:57:22] - [DRIVERS] Drivers path (%SystemRoot%\inf;) was successfully set into registry.
[11:57:22] - [DRIVERS] Drivers path (Z:\) with 0 was successfully set into registry.
[11:57:22] - [DRIVERS] Device Path in registry currently has 17.
[11:57:22] - Removing unknown hardware from system.
[11:57:22] - Removing hardware ID: PCI\VEN_8086&DEV_2572&SUBSYS_02871014&REV_02\3&61AAA01&0&10
[11:57:22] - Unknown devices were removed successfully.
[11:57:22] - [INFO] Enabling Window Managing Wizard
[11:57:22] - Forcing system to detect Plug & Play Devices.
[11:57:23] - System is now detecting and installing drivers for your hardware. Please wait!
[11:57:41] - System has now finished installing drivers for your hardware. Enjoy!
[11:57:41] - [INFO] Disabling Window Managing Wizard
[11:57:41] - Reseting registry DevicePath to default.
[11:57:41] - =================== END - PCX - END ===================

It seems that it can't find PCI\VEN_8086&DEV_2572&SUBSYS_02871014 which is the graphic card (Intel® 82865G). I'll try this driver! that I found on Intel site

This post has been edited by Kingskawn: 05 December 2008 - 06:08 AM

[MadBoy]

Quote

11:57:20] - [DRIVERS DB] Running PREPARE DATABASE function. Please wait...
[11:57:21] - [DRIVERS DB] Ending PREPARE DATABASE function. Execution time was 1.28 seconds.
[11:57:21] - [DRIVERS] Running SEARCH & MATCH function. Please wait...
[11:57:21] - [DRIVER] Device => PCI\VEN_8086&DEV_2572&SUBSYS_02871014 Driver Path => NOT FOUND in DB
[11:57:21] - [DRIVERS] SEARCH & MATCH function found 0 matching drivers
[11:57:21] - [DRIVERS] SEARCH & MATCH function found 1 drivers that have no match. Oh dear..
[11:57:21] - [DRIVERS] Execution time for SEARCH & MATCH was 1.39 seconds.
[11:57:22] - [SEARCH] Removing duplicate entries from INF list.
[11:57:22] - [DRIVERS] Setting path into registry using RegistryDevicePath method.
[11:57:22] - [DRIVERS] Drivers path (%SystemRoot%\inf;) was successfully set into registry.
[11:57:22] - [DRIVERS] Drivers path (Z:\) with 0 was successfully set into registry.

The bad thing about this is [11:57:21] - [DRIVERS] Execution time for SEARCH & MATCH was 1.39 seconds. It's way too small unless there's not much drivers there. Can you confirm that the drive Z was mapped without problem? And that there are drivers dir structure for that device?

With regards,

MadBoy

[Kingskawn]

MadBoy, on Dec 5 2008, 03:19 PM, said:

The bad thing about this is [11:57:21] - [DRIVERS] Execution time for SEARCH & MATCH was 1.39 seconds. It's way too small unless there's not much drivers there. Can you confirm that the drive Z was mapped without problem? And that there are drivers dir structure for that device?

With regards,

MadBoy

Yes, the share is mapped without problem and the folder is 30mb big with 14 folders in it. I made it as little as possible to avoid any problems. In the driver share are only drivers needed for that machine nothing else.
If I install manually from device manager the driver (PCI\VEN_8086&DEV_2572&SUBSYS_02871014) it get installed.

[MadBoy]

Kingskawn, on Dec 5 2008, 03:21 PM, said:

MadBoy, on Dec 5 2008, 03:19 PM, said:

The bad thing about this is [11:57:21] - [DRIVERS] Execution time for SEARCH & MATCH was 1.39 seconds. It's way too small unless there's not much drivers there. Can you confirm that the drive Z was mapped without problem? And that there are drivers dir structure for that device?

With regards,

MadBoy

Yes, the share is mapped without problem and the folder is 30mb big with 14 folders in it. I made it as little as possible to avoid any problems. In the driver share are only drivers needed for that machine nothing else.
If I install manually from device manager the driver (PCI\VEN_8086&DEV_2572&SUBSYS_02871014) it get installed.

Okey, what if you go and create the Drivers DB manually first (from the menu) and see if the filedb created has been created with a lot of hw_ids (and one of them is your gpu)?

[rparret]

hello,

i have just tested your program and here is my comments :

the old method works fine the new one (with the database) doesnt work.

My objective is to make a network repository of all drivers. These are being installed during the first boot.

My image is sypreped with latest network and mass storage drivers but i lose a lot of time reimage it each time an new driver is availlabe or updated.

I have already tested driverforge and both programs have the same problem : used on local pc, evrything is fine and fast but when drivers are located
on a network drive, perfomances are very bad.

Your approach of creating a driver database with device id is great but doesnt seems to work in my case.

my database consist of more than 24000 different id, when checking at them i have notice the following :

* hardware_database.db : PCI\VEN_8086&DEV_2930,\c\I\xp\ich9smb.inf

hardware.log : [09:55:01] - [DRIVER] Device => PCI\VEN_8086&DEV_2930&SUBSYS_02111028 Driver Path => NOT FOUND in DB

but in the ich9smb.inf here what i have found

%PCI\VEN_8086&DEV_2930.DeviceDesc% = NO_DRV, PCI\VEN_8086&DEV_2930

so i suppose the driver is not installed with your process because the id is not found. But the more surprising is this inf file is working when using the hardware wizard manually.

i will be glad to help you improving this masterpiece of software so dont hesitate to ask if help is needed

[MadBoy]

You may be right that the NEW db doesn't always work. I'll test it and hopefully fix this. Probably has some minor mistake with correct matching.

[jinkazama]

Madboy, your application works on Windows Vista? Driver detect is the same? I have Vista DP and i'ld try
P.S. i'm waiting for news about your work... do you think you'll update this software or you abandon it?
Thank you

[MadBoy]

jinkazama, on Jan 29 2009, 02:42 AM, said:

Madboy, your application works on Windows Vista? Driver detect is the same? I have Vista DP and i'ld try
P.S. i'm waiting for news about your work... do you think you'll update this software or you abandon it?
Thank you

Don't think it will work on vista without modifications. As for updating/abandoning. Well i have big project at work in C# about 42k lines now and will be like at least 60 so i'm preety busy. I love this software so i wont abandon it just yet, just it's hard to find time to work on it atm.

[djfufo]

Hi, my english is very bad , i´m from argentina, i can´t make it work, i change the lenguage in the hardware wizard part of the settings but still not working, somebody help me, thanks

[MadBoy]

djfufo, on Mar 5 2009, 03:34 PM, said:

Hi, my english is very bad , i´m from argentina, i can´t make it work, i change the lenguage in the hardware wizard part of the settings but still not working, somebody help me, thanks

Which particular features doesn't work? All ? Just the Hardward Wizard "Next" pressing button or which exactly? Can you paste some logs? Can you past conifg file?

[xpboy24]

Hey MadBoy, I'd just like to say that I personally love your program. I've been looking for something like this for quite some time and fond yours to be the easiest to use (not requiring a huge script).

My only problem with it revolves around the Found New Hardware Wizard.

I use the OLD method cuz I could never really get the New method to work and Old does what I want it to do. I'm running this on english XP machines.

My problem is that the Found New Hardware Wizard stops the program from proceeding on automatic (which is the biggest reason I love this). I have to manually cancel out of all fnhw windows and then the program will continue on as it should. Once those windows are gone the program works beautifully. I have all the settings set to what it says on the first page, but is there a way to force all the fnhw closed/push cancel? If this feature could be implemented somehow it would be complete!

[MadBoy]

xpboy24, on Mar 25 2009, 11:09 PM, said:

Hey MadBoy, I'd just like to say that I personally love your program. I've been looking for something like this for quite some time and fond yours to be the easiest to use (not requiring a huge script).

My only problem with it revolves around the Found New Hardware Wizard.

I use the OLD method cuz I could never really get the New method to work and Old does what I want it to do. I'm running this on english XP machines.

My problem is that the Found New Hardware Wizard stops the program from proceeding on automatic (which is the biggest reason I love this). I have to manually cancel out of all fnhw windows and then the program will continue on as it should. Once those windows are gone the program works beautifully. I have all the settings set to what it says on the first page, but is there a way to force all the fnhw closed/push cancel? If this feature could be implemented somehow it would be complete!

Hello xpboy24,

I must say i'm suprised that you want to cancel the window rather then push it thru. From my testing canceling the window wouldn't let the drivers to install properly. You sure it's working as you expect it too?

With regards,

MadBoy

[xpboy24]

Yup. If I use New method no drivers get installed, which is why I prefer Old. But using Old as long as there are NO fnhw windows up, the driver installation will continue on successfully. This becomes a problem in the initial and occasionally when I forget to add a driver for an unknown device or the wrong driver and the fnhw pops up again and thus stops the entire process midstream until I cancel out again. Of course if i'm running it on auto, I might not be paying attention all the time (perhaps initially for testing, but I've occasionally run into some models that are same model # but have 1 different part which causes a redetect), and thus fails.

I've found a workaround which seems to revolve around fnhw's need to use windows update initially. Your program, for me, used to never go beyond the fnhw and I never understood why truthfully (which also meant I never really understood the need for the fnhw section in your xml code either). If I disable "Use windows update for drivers" to never, then your program runs through the fnhw next-next-finish routine. I made a script that currently disables windows update driver check via registry and then re-enables it after driver installation. Is there a way so that Cancel is the first option used? If you say it interferes with the installation, is there a way to so that it chooses the "dont' use" option and then clicks next? I think the problem might be that there's no "default" option that gets automatically highlighted in the initial fnhw use windows update screen.

[MadBoy]

I am aware that new option doesn't work. It works in certain conditions but not for all HW_ID's due to some bug in the code. So it's better to use OLD option. As for the GUI manipulation, i could probably introduce "default" action in config and you would be able to choose either NEXT, NEXT, FINISH or CANCEL. I also want to add the code to set Windows Update off or on depending on user choice in config, and also non-gui option to disable driver signing. The problem is my time latly. I don't want to promise anything as i am extreamly busy at work programming big application. I am taking week off now so i will be off internet for that time. Talk to you when i get back.

[xpboy24]

that's great to hear MadBoy. Enjoy your vacation!! =D

[Zacam]

I notice when set to use compressed, it does not sub-dir scan past provided dir for .7z (or .rar) files.

How possible will it be to implement doing detect for more dirs in defined primary dir to scan them for .7z and .rar?

I need to use compressed drivers, but would like to sub folder them based on name of motherboard.

[MadBoy]

Zacam, on Apr 3 2009, 09:28 PM, said:

I notice when set to use compressed, it does not sub-dir scan past provided dir for .7z (or .rar) files.

How possible will it be to implement doing detect for more dirs in defined primary dir to scan them for .7z and .rar?

I need to use compressed drivers, but would like to sub folder them based on name of motherboard.

Well in my opinion it wasn't needed. You just need to prepare .7z properly. For example create dir structure before packing it (including the mobo names etc) and then pack it. THat way you can put a lot of .7zip files inside one directory without needing subdirs. Then after unpacking you will get the right dir structure.

If it's not sufficient i guess it can be added to TODO list but maybe it will be suffcient tip ?

[Zacam]

Well, I do feel sheepish for not having considered that solution.

I was attempting to make it easier to (if necessary) perform manual re-installs of components, without having to extract an entire motherboard set, but I will see how well this idea tests out.

Thanks for the feedback and the suggestion, I'll let you know how it goes.

**Edit

So, it has gone well. Though, setting some sort of an instruction delay, (if you have it set to delete copied drivers) before it actually restarts the system would be nice, or did I miss something in the documentation?

This post has been edited by Zacam: 06 April 2009 - 02:05 PM

[pSycho-Y2K]

Hey MadBoy

What's the current status of the tool? I would love to see the new features!

This post has been edited by pSycho-Y2K: 29 May 2009 - 01:17 AM